I tried to read .dmp file as follows:
i386kd -z c:\Windows\Memory.dmp

Dumpcheck too throws up similar errors:
dumpcheck c:\Windows\Memory.dmp

Then I get these errors:

=========================================================================
Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [c:\WINDOWS\MEMORY.DMP]
Kernel Complete Dump File: Full address space is available

Symbol search path is: C:\WINDOWS\symbols\
Executable search path is: C:\WINDOWS
*** ERROR: Symbol file could not be found. Defaulted to export
symbols for ntkrn
Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
Debug session time: Wed Aug 29 11:43:57.906 2007 (GMT+5)
System Uptime: 0 days 1:50:41.502
*** ERROR: Symbol file could not be found. Defaulted to export
symbols for ntkrn
Loading Kernel Symbols
.................................................................................
Loading User Symbols

Loading unloaded module list
..............
ERROR: FindPlugIns 8007010b
*******************************************************************************
*
*
* Bugcheck
Analysis *
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7E, {c0000005, b9678000, f7a37bb8, f7a378b4}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*** WARNING: Unable to verify timestamp for w2k_kill.sys
*** ERROR: Module load completed but symbols could not be loaded for
w2k_kill.sys
*** WARNING: Unable to verify timestamp for mssmbios.sys
*********************************************************************************
***
*** Your debugger is not using the
correctsymbols ***
***
***
*** In order for this command to work properly, your symbol path
***
*** must point to .pdb files that have full
typeinformation. ***
***
***
*** Certain .pdb files (such as the public OS symbols)
donot ***
*** contain the required information. Contact the group
that ***
*** provided you with these symbols if you need this command to
work.
***
*** Type referenced: mssmbios!_SMBIOS_DATA_OBJECT ***
***
***
***********************************************************************************
***********************************************************************************

[3 repeatations of the above block within asterisks]

Probably caused by : w2k_kill.sys ( w2k_kill+1000 )

Followup: MachineOwner
---------
========================================================================

I had installed these:

Windows XP SP2 x86 Retail Symbols (c:\Windows\Symbols):
[http://msdl.microsoft.com/download/symbols/packages/windowsxp/
WindowsXP-KB835935-SP2-slp-Symbols.exe]

Debugging Tools for Windows 32-bit Versions:
Previous Release version 6.6.7.5 - July 18, 2006
[http://msdl.microsoft.com/download/symbols/debuggers/
dbg_x86_6.6.07.5.exe]

And my system specs are:

MS Windows XP Professional
Version 2002
Service Pack 2

AMD Athlon 64 Processor

I have set the following environment variables:

_NT_EXECUTABLE_IMAGE_PATH to C:\Windows
_NT_SYMBOL_PATH to C:\Wndows\Symbols

--------------------------------------------------------------------------------------------------------------------------------------------

Where have I gone wrong in setting up my debugging environment?

Re: Errors reading crash-dump file using i386kd by Maxim

Maxim
Wed Aug 29 08:46:29 CDT 2007

Set up WinDbg to automatically download symbols from MS. This is done by
.symfix command.

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@storagecraft.com
http://www.storagecraft.com

"rup" <sauparna.palc@gmail.com> wrote in message
news:1188394269.079474.270250@y42g2000hsy.googlegroups.com...
> I tried to read .dmp file as follows:
> i386kd -z c:\Windows\Memory.dmp
>
> Dumpcheck too throws up similar errors:
> dumpcheck c:\Windows\Memory.dmp
>
> Then I get these errors:
>
> =========================================================================
> Microsoft (R) Windows Debugger Version 6.6.0007.5
> Copyright (c) Microsoft Corporation. All rights reserved.
>
> Loading Dump File [c:\WINDOWS\MEMORY.DMP]
> Kernel Complete Dump File: Full address space is available
>
> Symbol search path is: C:\WINDOWS\symbols\
> Executable search path is: C:\WINDOWS
> *** ERROR: Symbol file could not be found. Defaulted to export
> symbols for ntkrn
> Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
> Product: WinNt, suite: TerminalServer SingleUserTS
> Built by: 2600.xpsp_sp2_gdr.050301-1519
> Kernel base = 0x804d7000 PsLoadedModuleList = 0x805531a0
> Debug session time: Wed Aug 29 11:43:57.906 2007 (GMT+5)
> System Uptime: 0 days 1:50:41.502
> *** ERROR: Symbol file could not be found. Defaulted to export
> symbols for ntkrn
> Loading Kernel Symbols
>
...............................................................................
..
> Loading User Symbols
>
> Loading unloaded module list
> ..............
> ERROR: FindPlugIns 8007010b
>
*******************************************************************************
> *
> *
> * Bugcheck
> Analysis *
> *
> *
>
*******************************************************************************
>
> Use !analyze -v to get detailed debugging information.
>
> BugCheck 7E, {c0000005, b9678000, f7a37bb8, f7a378b4}
>
> ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
>
> ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
>
> *** WARNING: Unable to verify timestamp for w2k_kill.sys
> *** ERROR: Module load completed but symbols could not be loaded for
> w2k_kill.sys
> *** WARNING: Unable to verify timestamp for mssmbios.sys
>
*******************************************************************************
**
> ***
> *** Your debugger is not using the
> correctsymbols ***
> ***
> ***
> *** In order for this command to work properly, your symbol path
> ***
> *** must point to .pdb files that have full
> typeinformation. ***
> ***
> ***
> *** Certain .pdb files (such as the public OS symbols)
> donot ***
> *** contain the required information. Contact the group
> that ***
> *** provided you with these symbols if you need this command to
> work.
> ***
> *** Type referenced: mssmbios!_SMBIOS_DATA_OBJECT ***
> ***
> ***
>
*******************************************************************************
****
>
*******************************************************************************
****
>
> [3 repeatations of the above block within asterisks]
>
> Probably caused by : w2k_kill.sys ( w2k_kill+1000 )
>
> Followup: MachineOwner
> ---------
> ========================================================================
>
> I had installed these:
>
> Windows XP SP2 x86 Retail Symbols (c:\Windows\Symbols):
> [http://msdl.microsoft.com/download/symbols/packages/windowsxp/
> WindowsXP-KB835935-SP2-slp-Symbols.exe]
>
> Debugging Tools for Windows 32-bit Versions:
> Previous Release version 6.6.7.5 - July 18, 2006
> [http://msdl.microsoft.com/download/symbols/debuggers/
> dbg_x86_6.6.07.5.exe]
>
> And my system specs are:
>
> MS Windows XP Professional
> Version 2002
> Service Pack 2
>
> AMD Athlon 64 Processor
>
> I have set the following environment variables:
>
> _NT_EXECUTABLE_IMAGE_PATH to C:\Windows
> _NT_SYMBOL_PATH to C:\Wndows\Symbols
>
> -----------------------------------------------------------------------------
---------------------------------------------------------------
>
> Where have I gone wrong in setting up my debugging environment?
>


Re: Errors reading crash-dump file using i386kd by rup

rup
Sun Sep 02 21:40:58 PDT 2007

Thank you. Pointing the debugger to download symbols from the MS
server has solved it.