BSOD (driver caused)?

[Nathaniel Ourfali]

Hello, everyone. I've been having some trouble with BSODs for the past year, ever since I upgraded my computer.

Here's my list of current specs:

Windows 7 Ultimate x64
AMD Phenom II X4 965 (Black Edition)
ASUS M5A78L-M
GeForce 550Ti
Corsair GS600

Now, keep in mind, all this time I thought it was my CPU that was overheating and caused my BSOD, and in fact, in might still be, but I tried everything from swapping the paste to changing the CPU fan, I also swapped the case and put an extra (still small) fan in the case, but no deal. It seems more reliable when it has its case opened, but it still gives me BSODs every now and then.

However, when I had a huge body fan pointed at the CPU, the problem seemed not to happen, so that's why I'm thinking it still is overheating, but I might as well check for driver-caused problems, right?

As a side note, changing the clock settings to anything but 1333GHz or Auto for the RAM seems to make the computer not even start at all, so I have to remove the battery and put it back up to reset the BIOS. Same for the CPU clock.

In any case, I'll be posting the minidump file in this thread. Please forgive me if I'm supposed to post it somewhere else (pastebin, maybe?) or something else, just let me know and I will fix it.

I'm really hoping for help, this PC is used mostly for games and university papers, but I cannot trust it enough to keep my projects safe in here because of these issues.

Here's the minidump log:

Spoiler

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


Loading Dump File [D:\Downloads\012814-36644-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are 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+ *
*********************************************************************
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
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e01000 PsLoadedModuleList = 0xfffff800`0303ee50
Debug session time: Tue Jan 28 04:13:44.474 2014 (UTC - 2:00)
System Uptime: 0 days 0:08:56.988
*********************************************************************
* 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+ *
*********************************************************************
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 50, {fffff90046f10fc8, 0, fffff960000c2ad3, 5}

*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.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 ***
*** ***
*************************************************************************
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
*************************************************************************
*** ***
*** ***
*** 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 : win32k.sys ( win32k+c2ad3 )

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

Thanks in advance.

 

[mironso]

However, when I had a huge body fan pointed at the CPU, the problem seemed not to happen, so that's why I'm thinking it still is overheating, but I might as well check for driver-caused problems, right?

I would pay attention to this sentence. Try reapply thermal paste. Put that fan again, or get a better cooling system for your cpu. As you said, it fixes your problem.

 

[Nathaniel Ourfali]

Try reapply thermal paste. Put that fan again, or get a better cooling system for your cpu. As you said, it fixes your problem.

It's understandable that that might be in fact the problem, but then again, whenever I reinstall Windows I install a LOT of drivers that I'm not even sure if they are the correct ones, I just make sure they are working and I roll with that.

I don't know if the BSOD logs actually help at all, but couldn't it be that win32k.sys or something else but the ventilation problem?

 

[mironso]

Well, installing drivers that are not compatible with win can cause problem(s). But then it will/would cause problem(s) always. You said that when you cool down cpu it stops. Exclude issue one at a time.