How to trace bsod?

Azuse05

Azuse05

Azuse05

Associate
Joined
24 Apr 2009
Posts
1,940
Location
Aberdeen, Scotland
Changed to mobo and cpu yesterday, as expected it was fine all day. Today it bsod while installing something and then again an hour later.

Could anyone explain (in simple terms :)) where this log file is dumped and how to work out what exactly is causing this because no other components have changed :mad:
 
You could also try:

Start> In the search bar type "Event viewer"

Open Event Viewer> Windows Log> System.

See if you can find any errors in there at the same time as the bsod.

Also, did you do a fresh OS install when you changed the cpu and mobo?
 
Thanks frapple, I'd forgotten about that (because someone has to talk me through it) :) I'll give it a go once I've finished backing things up. My backup had began clicking, then my backup-backup began clicking :(

Oh and theres a few entries in the log
The driver detected a controller error on \Device\Harddisk2\DR2.
Click to expand...
but idk what dr2 means (or which drive windows is identifying as 2.
 
Another blue screen, dump doesn't appear good tbh:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

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+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02c05000 PsLoadedModuleList = 0xfffff800`02e4ae90
Debug session time: Wed Mar 23 23:25:44.010 2011 (UTC + 0:00)
System Uptime: 0 days 0:36:13.555
*********************************************************************
* 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+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Loading Kernel Symbols
...............................................................
................................................................
........................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`7efdf018). Type ".hh dbgerr001" for details
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000096, fffff88008a7d912, 0, 0}

*** ERROR: Module load completed but symbols could not be loaded for cpudrv64.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 ***
*** ***
*************************************************************************
Probably caused by : cpudrv64.sys ( cpudrv64+1912 )

Followup: MachineOwner
---------
 
Always. Actually 3 times in this case. I tend to have bad experiences with asus boards, though I admit I'm not fond of their default 2% oc in the bios. The fact that hardware monitor is listing the -12V rail as -6V and the north bridge (unless I'm mistaken) at an idle temp of 41 doesn't really inspire.

Got a gigabyte coming tomorrow, so we'll see how it goes. Think I'll be retuning this asus tbh :(
 
My friend says asys board are one of the best ones. I have Gigabyte and it is playing up, but it could be my setup.
 
You must log in or register to reply here.
Back
Top Bottom