WinDbg in Windows 7 Ultimate 64-Bit SP 1

Question

WinDbg in Windows 7 Ultimate 64-Bit SP 1

Anonymous

Hi All,

In reading a crash dump, I am getting errors.

Symbol search path is: *** Invalid ***

****************************************************************************

* Symbol loading may be unreliable without a symbol search path. *

* Use .symfix to have the debugger choose a symbol path. *

* After setting your symbol path, use .reload to refresh symbol locations. *

****************************************************************************

Executable search path is:

*********************************************************************

* Symbols can not be loaded because symbol path is not initialized. *

* *

* The Symbol Path can be set by: *

* using the _NT_SYMBOL_PATH environment variable. *

* using the -y <symbol_path> argument when starting the debugger. *

* using .sympath and .sympath+ *

*********************************************************************

Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2

*** WARNING: Unable to verify timestamp for ntoskrnl.exe

*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144

Machine Name:

Kernel base = 0xfffff80003617000 PsLoadedModuleList = 0xfffff8000385a890

Debug session time: Sun Jul 27 13:16:46.811 2014 (GMT-4)

System Uptime: 0 days 1:41:23.765

*********************************************************************

* Symbols can not be loaded because symbol path is not initialized. *

* *

* The Symbol Path can be set by: *

* using the _NT_SYMBOL_PATH environment variable. *

* using the -y <symbol_path> argument when starting the debugger. *

* using .sympath and .sympath+ *

*********************************************************************

Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2

*** WARNING: Unable to verify timestamp for ntoskrnl.exe

*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe

Loading Kernel Symbols

...............................................................

................................................................

...............................

Loading User Symbols

Loading unloaded module list

.........

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 6, {0, 0, 0, 0}

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

*************************************************************************

*** ***

*** Your debugger is not using the correct symbols ***

*** ***

*** In order for this command to work properly, your symbol path ***

*** must point to .pdb files that have full type information. ***

*** ***

*** Certain .pdb files (such as the public OS symbols) do not ***

*** contain the required information. Contact the group that ***

*** provided you with these symbols if you need this command to ***

*** work. ***

*** ***

*** Type referenced: nt!_KPRCB ***

*** ***

*************************************************************************

Where do I download this information?

I know where to add the Path, but where do I point the path to?

* The Symbol Path can be set by: *

* using the _NT_SYMBOL_PATH environment variable. *

* using the -y <symbol_path> argument when starting the debugger. *

* using .sympath and .sympath+ *

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

2 additional answers

Answer 1

Hello,

Thank you for replying.

The Windows SDK provides tools, compilers, headers, libraries, code samples, and a new help system that developers can use to create applications that run on Microsoft Windows. You can use the Windows SDK to write applications using the native (Win32/COM) or managed (.NET Framework) programming model.

The easiest way to get Windows symbols is to use the **Microsoft Symbol Server**. The symbol server makes symbols available to your debugging tools as needed. After a symbol file is downloaded from the symbol server it is cached on the local computer for quick access.

For more information please refer the link provided below.

Download Windows Symbol Packages

The symbol path specifies locations where the Windows debuggers (WinDbg, KD, CDB, NTST) look for symbol files. For more information about symbols and symbol files, see **Symbols**.

Symbol path for Windows debuggers

For further assistance on Windows Debugger, you can post the issue on Windows Desktop Debugger.

**http://social.msdn.microsoft.com/Forums/windowsdesktop/en-US/home?forum=windbg**

Do feel free to post on Microsoft Community, in case you have any issues while working on Windows.

Answer 2

Anonymous

Hi Andrew E.,

The Memory Dump was from another computer.

But I post because of the lack of Symbols.

How do I format the Path Statements which are missing and where do I get the Symbols and

Symbol loading may be unreliable without a symbol search path?

0 comments

Answer 3

Anonymous

Microsoft has a list of fixes for that error,follow this link for them.

http://social.technet.microsoft.com/Search/en-US?query=ntoskmi.exe&ac=2

0 comments

Share via

WinDbg in Windows 7 Ultimate 64-Bit SP 1

2 additional answers