Symbols could not be loaded for win32k.sys

Brilliant! I never would have thought to run it from the .zip itself. Nice find!!

I'll have to test that out, too.

Note that you get a checksum error on win32k when running from unextracted zip.

Also.... only win32k PDB downloads, not win32k SYS symbols.
 
Last edited:
Used the same method, but received different results:
Read More:
 
1 difference...

Code:
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys

I got:
Code:
*** WARNING: Unable to verify checksum for win32k.sys
 
This is way beyond my ability to understand - you need a WinDbg/kd expert
Anyone want to address it to the WinDbg External Feedback folks (email link is from March of 2010)? windbgfb (at) microsoft.com
 
My apologies for my lack of clarity.
I do not mean that the dump files are pointing to the fault. I am saying that the hardware maybe causing the trouble with the changed timestamp and checksum problems you are seeing.
As per post #34 it doesn't appear the the dump file is created/written correctly. Hence causing the trouble with Win32K.sys.
 
Dumpchk can be run to verify the integrity of a dump file.

Command:

cd /d "K:\WinDDK\7600.16385.1\Debuggers"

dumpchk -v -y SRV*a:\symbols*http://msdl.microsoft.com/download/symbols 081612-18673-01.dmp

Output:
Read More:

http://support.microsoft.com/kb/315271
http://technet.microsoft.com/en-us/library/ee424340(v=ws.10).aspx
http://msdn.microsoft.com/en-us/library/windows/hardware/ff560109(v=vs.85).aspx
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top