Vista - Blue screen of death..

bart123 · 03-05-2009

So yeh, i got some problems with my vista 64 bit pc..

This is what the .dmp file says..
************************************************** *******************
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 D1, {8c, 2, 1, fffffa6002b6e521}

Unable to load image \SystemRoot\system32\DRIVERS\Rtlh64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Rtlh64.sys
*** ERROR: Module load completed but symbols could not be loaded for Rtlh64.sys
***** 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 ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** 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 ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** 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 ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** 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 ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** 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 ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** 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 ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** 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 ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** 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 ***
*** ***
************************************************** ***********************
************************************************** *******************
* 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+ *
************************************************** *******************
************************************************** *******************
* 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+ *
************************************************** *******************
Probably caused by : Rtlh64.sys ( Rtlh64+7521 )

Followup: MachineOwner

I think its something with the tcp/ip because in the logfile it says there are to many tcp/ip connections but im not sure about this..
It also says Softlok.sys has been blocked from loading due to incompatibility with this system. Please contact your software vendor for a compatible version of the driver.

Other pc specs, Q9550 , Asus P5KPL/1600 , Ati radeon 4850...

Thx!

**H2SO4** · 03-07-2009

Try updating Rtlh64.sys - your RealTek NIC driver.

The debugger output suggests functions corresponding to that driver were on the stack of the crashing thread, which is generally reason enough to be very suspicious of the driver in question.

Also, when you're doing this type of analysis with a debugger, it's important to have your symbols set up correctly, otherwise the debugger is limited in what it can do.

Try typing this sequence of commands into the debugger prompt once the dump is open:

.symfix C:\SymCache
.reload
!analyze -v

That should give you a more meaningful automated analysis without all the "your symbols aint right you know. No, really!" warnings

bart123 · 03-07-2009

Updated my network drivers, i think its fixed now..still thanks for ur help and sorry that i didnt post the full log, but i think this was enough to see what was the problem..
Greetz!

03-05-2009	#1 (permalink)
bart123 vista home premium 64 bit 2 posts	Blue screen of death.. So yeh, i got some problems with my vista 64 bit pc.. This is what the .dmp file says.. ************************************************ *************** 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 D1, {8c, 2, 1, fffffa6002b6e521} Unable to load image \SystemRoot\system32\DRIVERS\Rtlh64.sys, Win32 error 0n2 * WARNING: Unable to verify timestamp for Rtlh64.sys * ERROR: Module load completed but symbols could not be loaded for Rtlh64.sys * 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 * * * ********************************************** ******************* ********************************************** ******************* * * * * * 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 * * * ********************************************** ******************* ********************************************** ******************* * * * * * 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 * * * ********************************************** ******************* ********************************************** ******************* * * * * * 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 * * * ********************************************** ******************* ********************************************** ******************* * * * * * 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 * * * ********************************************** ******************* ********************************************** ******************* * * * * * 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 * * * ********************************************** ******************* ********************************************** ******************* * * * * * 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 * * * ********************************************** ******************* ********************************************** ******************* * * * * * 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 * * * ********************************************** ******************* ********************************************** ***************** * 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+ * ************************************************ *************** ********************************************** ***************** * 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+ * ************************************************ ***************** Probably caused by : Rtlh64.sys ( Rtlh64+7521 ) Followup: MachineOwner I think its something with the tcp/ip because in the logfile it says there are to many tcp/ip connections but im not sure about this.. It also says Softlok.sys has been blocked from loading due to incompatibility with this system. Please contact your software vendor for a compatible version of the driver. Other pc specs, Q9550 , Asus P5KPL/1600 , Ati radeon 4850... Thx!
My System Specs

03-07-2009	#2 (permalink)
H2SO4 Win7x64 1,241 posts	Re: Blue screen of death.. Try updating Rtlh64.sys - your RealTek NIC driver. The debugger output suggests functions corresponding to that driver were on the stack of the crashing thread, which is generally reason enough to be very suspicious of the driver in question. Also, when you're doing this type of analysis with a debugger, it's important to have your symbols set up correctly, otherwise the debugger is limited in what it can do. Try typing this sequence of commands into the debugger prompt once the dump is open: .symfix C:\SymCache .reload !analyze -v That should give you a more meaningful automated analysis without all the "your symbols aint right you know. No, really!" warnings
My System Specs

03-07-2009	#3 (permalink)
bart123 vista home premium 64 bit 2 posts	Re: Blue screen of death.. Updated my network drivers, i think its fixed now..still thanks for ur help and sorry that i didnt post the full log, but i think this was enough to see what was the problem.. Greetz!
My System Specs

Similar Threads
Thread	Forum
Blue Screen of Death	Vista performance & maintenance
Blue screen of death!!!! help!!!	General Discussion
Blue screen of death	Vista General
The blue screen of death...	Vista performance & maintenance
BLUE SCREEN OF DEATH	Vista General