Welcome Guest ( Log In | Register )

Outline · [ Standard ] · Linear+

 [Step by Step] How to Analyze BlueScreen Dump, by using Microsoft Windows Debugger

views
     
andythology
post Oct 5 2004, 11:23 PM

潛水員
*****
Senior Member
926 posts

Joined: Jan 2003
From: Kuala Lumpur


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.
------------------------------------------------------------------------------------------
hm.. how to deal with this?
andythology
post Oct 5 2004, 11:32 PM

潛水員
*****
Senior Member
926 posts

Joined: Jan 2003
From: Kuala Lumpur


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

Unable to load image emDevice.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for emDevice.sys
*** ERROR: Module load completed but symbols could not be loaded for emDevice.sys
Unable to load image emStream.sys, Win32 error 2
*** WARNING: Unable to verify timestamp for emStream.sys
*** ERROR: Module load completed but symbols could not be loaded for emStream.sys
Probably caused by : emDevice.sys ( emDevice+a0d4 )

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

kd> .reload
Unable to load image ntoskrnl.exe, Win32 error 2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
-------------------------------------------------------------------------------------
wow..lots of problem. dunno how to fix it.. now, this is how we tell the amateur , intermediate and pro. haha

 

Change to:
| Lo-Fi Version
0.0167sec    0.28    7 queries    GZIP Disabled
Time is now: 5th December 2025 - 12:10 AM