Q183282 - FIX: WinDBG Build 5.00.1719 May Not Work with Memory Dumps

FIX: WinDBG Build 5.00.1719 May Not Work with Memory Dumps

Q183282

The information in this article applies to:

Microsoft Platform Software Development Kit (SDK)
Microsoft Win32 Device Driver Kit (DDK) for Windows NT

SYMPTOMS

When you load a memory dump with version 5.00.1719.1 of WinDBG, one of the following error messages appears:

Symbol search path is: *** Invalid *** : Verify _NT_SYMBOL_PATH setting
kd: crash dump initialized [C:\Dump\MEMORY.DMP]
KD: Unable to load debug information for ntoskrnl.exe

- or -

Could not get the KiProcessorBlock address

Version 5.00.1719.1 of WinDBG shipped with the January 1998 release of the Platform SDK. This version can be verified by right-clicking the executable WinDBG.exe, selecting Properties, and checking the file version number.

CAUSE

It has been reported that memory dumps from machines with multiple processors cause this problem.

RESOLUTION

The errors can be generated because of an improper symbols path. To solve this, do one of the following:

Check your symbols path and reset your environment. Possibly the Memory.dmp file is corrupted. Run Dumpchk.exe on this file to verify its integrity.

Uninstall build 5.00.1719,1 by typing the following commands in a command box:
del /s msdbi.dll dm.dll dmkdalp.dll dmkdx86.dll
del /s eecxx.dll em.dll shcv.dll tlloc.dll tlpipe.dll tlser.dll
del /s windbg.cnt windbg.exe windbg.hlp windbgrm.exe
del c:\winnt\system32\imagehlp.dll

NOTE: Imagehlp.dll may be in use on Windows NT machines. To delete this file, you have to stop the Protected Storage service.

Install WinDBG from the October 97 release of MSDN (Build 5.00.1867.1) or install the latest released build from the following Web site:

http://msdn.microsoft.com/developer/sdk/platform.asp

Then restart your computer.

STATUS

Additional query words:

Keywords : kbMSDN kbWin32s kbGrpDSTools
Issue type : kbbug
Technology :