Shintaro
Well-known member
I was looking at a crash dump from a Vista system and Windbg threw the following:
Well I downloaded the symbols for x86 SP2. So that is odd?
So I turned on !sym noisy
So it says that the symbols are not in either MS symbol server or my symbol store. Odd?
Therefore !errrec <address> doesn't give a possible culprit.
I am unsure of how to get around this problem with symbols. Or is it impossible because they are Dell's?
Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/...ls*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 6002.18607.x86fre.vistasp2_gdr.120402-0336
Machine Name:
Kernel base = 0x83249000 PsLoadedModuleList = 0x83360c70
Debug session time: Sun Jul 15 05:19:26.491 2012 (UTC + 10:00)
System Uptime: 0 days 2:07:13.332
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, 8eab3020, b6000000, 181}
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
Probably caused by : hardware
Well I downloaded the symbols for x86 SP2. So that is odd?
So I turned on !sym noisy
So it says that the symbols are not in either MS symbol server or my symbol store. Odd?
SYMSRV: c:\symbols\ntoskrnl.exe\4F79A9BE3ba000\ntoskrnl.exe not found
SYMSRV: http://msdl.microsoft.com/download/symbols/ntoskrnl.exe/4F79A9BE3ba000/ntoskrnl.exe not found
SYMSRV: c:\symbols\ntkrnlup.exe\4F79A9BE3ba000\ntkrnlup.exe not found
SYMSRV: http://msdl.microsoft.com/download/symbols/ntkrnlup.exe/4F79A9BE3ba000/ntkrnlup.exe not found
DBGHELP: c:\symbols\ntkrnlpa.exe\4F79A9BE3ba000\ntkrnlpa.exe - OK
DBGENG: c:\symbols\ntkrnlpa.exe\4F79A9BE3ba000\ntkrnlpa.exe - Mapped image memory
DBGHELP: nt - public symbols
c:\symbols\ntkrpamp.pdb\8B8346938BD24632B8896060E508F4032\ntkrpamp.pdb
Loading Kernel Symbols
.
SYMSRV: c:\symbols\halaacpi.dll\49E018D933000\halaacpi.dll not found
SYMSRV: http://msdl.microsoft.com/download/symbols/halaacpi.dll/49E018D933000/halaacpi.dll not found
SYMSRV: c:\symbols\halacpi.dll\49E018D933000\halacpi.dll not found
SYMSRV: http://msdl.microsoft.com/download/symbols/halacpi.dll/49E018D933000/halacpi.dll not found
SYMSRV: c:\symbols\halapic.dll\49E018D933000\halapic.dll not found
SYMSRV: http://msdl.microsoft.com/download/symbols/halapic.dll/49E018D933000/halapic.dll not found
Therefore !errrec <address> doesn't give a possible culprit.
I am unsure of how to get around this problem with symbols. Or is it impossible because they are Dell's?