Recently upgraded computer, getting BSODs often. Never during gaming?

[bBananasGoMoo]

SO recently (in November) i upgraded my CPU, mobo, and ram, and have been getting many BSODs. my new CPU is the amd bulldozer 8 core, and since its been known to have some problems, i updated my bios to the latest available (a beta bios). That fixed my steam games giving BSODs. now i randomly get BSODs every once in a while (every week or two) but the last few days I have gotten a BSOD every day. I have disabled C1E state on my bios, and that made it so I don't BSOD while watching embedded youtube videos. I also installed the Windows bulldozer hotfix, which made my pc faster.

Then I noticed something special about my BSODs - they only seem to happen while I am doing something not very resource intensive, like web browsing. It never happens while I am playing a game. So i thought it might be a driver having issues with state changes of my CPU. I disabled C6 state in my BIOS just in case, but that didn't seem to help much.

So now I'm here asking what you guys thing is the problem. Any help is appreciated.

Thanks,
-BGM

PS: Dump attached, as requested by the announcement thread for this forum.

 

[usasma]

MSINFO32.nfo file is corrupted (not unusual). Please do this:

- Go to Start and type in "msinfo32" and press Enter
- When the utility opens, save a copy of it as an .nfo file, and another copy as a .txt file
- Zip them up and upload them with your next post

Daemon Tools (and Alcohol % software) are known to cause BSOD's on Win7 systems due to the sptd.sys driver.
Please uninstall the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration): DuplexSecure - FAQ

AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center.
Please uninstall the AMD OverDrive program.
If it's the stand-alone app, uninstall it via Control Panel...Programs...Uninstall a program
If it's in the AMD VISION Engine Control Center, you can uninstall it using the AMD uninstall tool (or uninstall the entire AMD VISION Engine Control Center application through Control Panel

If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.

Otherwise, I'm suspecting a hardware problem. Please try the free hardware diagnostics here: Hardware Diags

BSOD BUGCHECK SUMMARY

[font=lucida console]
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\012212-27580-01.dmp]
Built by: 7601.17730.amd64fre.win7sp1_gdr.111123-1510
Debug session time: Sun Jan 22 17:56:02.285 2012 (UTC - 5:00)
System Uptime: 0 days 1:57:05.456
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
BiosVersion = F8d
BiosReleaseDate = 11/25/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\012112-22542-01.dmp]
Built by: 7601.17730.amd64fre.win7sp1_gdr.111123-1510
Debug session time: Sun Jan 22 00:23:21.152 2012 (UTC - 5:00)
System Uptime: 0 days 6:47:41.181
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExit+245 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x1
PROCESS_NAME:  Steam.exe
FAILURE_BUCKET_ID:  X64_0x1_SysCallNum_1_nt!KiSystemServiceExit+245
Bugcheck code 00000001
Arguments 00000000`74da2e09 00000000`00000000 00000000`00000000 fffff880`0c82eb60
BiosVersion = F8d
BiosReleaseDate = 11/25/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\012012-21247-01.dmp]
Built by: 7601.17730.amd64fre.win7sp1_gdr.111123-1510
Debug session time: Fri Jan 20 03:11:59.910 2012 (UTC - 5:00)
System Uptime: 0 days 8:22:37.019
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
BiosVersion = F8d
BiosReleaseDate = 11/25/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\011112-38875-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Jan 11 15:52:06.678 2012 (UTC - 5:00)
System Uptime: 0 days 0:17:14.802
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000019 00000000`00000000 fffff880`009eb180 00000000`00000001
BiosVersion = F8d
BiosReleaseDate = 11/25/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\122711-24429-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Wed Dec 28 02:14:24.095 2011 (UTC - 5:00)
System Uptime: 0 days 5:59:37.250
BugCheck D1, {fffffa8809213b30, 9, 0, fffff88008d9050a}
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
Probably caused by : dxgmms1.sys ( dxgmms1!VidSchiProcessIsrCompletedPacket+8a )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_dxgmms1!VidSchiProcessIsrCompletedPacket+8a
Bugcheck code 000000D1
Arguments fffffa88`09213b30 00000000`00000009 00000000`00000000 fffff880`08d9050a
BiosVersion = F8d
BiosReleaseDate = 11/25/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\121811-22401-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Dec 18 03:47:20.035 2011 (UTC - 5:00)
System Uptime: 0 days 0:54:18.190
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  QuestViewer.ex
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000019 00000000`00000000 fffff880`032fb180 00000000`00000006
BiosVersion = F6
BiosReleaseDate = 08/31/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\121711-20904-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sun Dec 18 02:43:46.957 2011 (UTC - 5:00)
System Uptime: 0 days 1:10:48.097
Probably caused by : ntkrnlmp.exe ( nt!ExfAcquirePushLockExclusive+d0 )
BUGCHECK_STR:  0x1E_c0000005
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  CivilizationV_
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_nt!ExfAcquirePushLockExclusive+d0
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`0387998b 00000000`00000000 00000000`00000f8d
BiosVersion = F6
BiosReleaseDate = 08/31/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\121711-37019-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Dec 17 21:10:29.838 2011 (UTC - 5:00)
System Uptime: 0 days 0:00:33.994
Probably caused by : ntkrnlmp.exe ( nt!KiKernelCalloutExceptionHandler+e )
BUGCHECK_STR:  0x1E_0
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x1E_0_nt!KiKernelCalloutExceptionHandler+e
Bugcheck code 0000001E
Arguments 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000
BiosVersion = F6
BiosReleaseDate = 08/31/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\120611-27268-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Tue Dec  6 20:32:10.399 2011 (UTC - 5:00)
System Uptime: 0 days 1:34:38.554
Probably caused by : hardware ( nt!PoIdle+588 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x50
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_IP_MISALIGNED
Bugcheck code 00000050
Arguments ffffffff`ffffff8b 00000000`00000000 fffff800`038d4507 00000000`00000000
BiosVersion = F6
BiosReleaseDate = 08/31/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\120211-28704-01.dmp]
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Debug session time: Sat Dec  3 01:14:08.455 2011 (UTC - 5:00)
System Uptime: 0 days 0:05:15.610
Probably caused by : ntkrnlmp.exe ( nt!KeWaitForSingleObject+132 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0x3B
PROCESS_NAME:  plugin-contain
FAILURE_BUCKET_ID:  X64_0x3B_nt!KeWaitForSingleObject+132
Bugcheck code 0000003B
Arguments 00000000`c000001d fffff800`038e26e2 fffff880`0e0abff0 00000000`00000000
BiosVersion = F6
BiosReleaseDate = 08/31/2011
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  
  [/font]

 

[bBananasGoMoo]

so, i'm generating the msinfo32 again right now. I uninstalled daemon tools yesterday, but i had to manually remove the driver myself, haven't restarted yet but I will.

I stopped overclocking my CPU earlier today, but that last BSOD was after I stopped overclocking. I don't overclock my GPU.

I just want to mention I got my GPU about a month before my other parts, and I had no BSODs until i installed my new CPU/motherboard/ram

also I've run memtest about a month ago and it resulted in no problems.

EDIT: just restarted, no more SPTD.

 

[usasma]

The sptd.sys driver is well-known for it's BSOD's. Monitor for further BSOD's now that it's gone.

The MSINFO32.nfo file is still corrupt. As I said previously, this isn't unusual - that's why I requested a copy of the report saved as a .txt file. But hold off on it now - unless you get another BSOD.

 

[bBananasGoMoo]

The sptd.sys driver is well-known for it's BSOD's. Monitor for further BSOD's now that it's gone.

The MSINFO32.nfo file is still corrupt. As I said previously, this isn't unusual - that's why I requested a copy of the report saved as a .txt file. But hold off on it now - unless you get another BSOD.

oh, sorry, i'll save it as a txt in a sec.

also, I can open the NFO directly using notepad, just drag and drop. unless you've tried that?

also another note is I only seem to get one BSOD per day max.

 

[usasma]

Nice trick about drag and drop into Notepad. Real difficult to read tho'. I'll hold off reading it (I have serious eye problems) unless you get more BSOD's.

 

[bBananasGoMoo]

Nice trick about drag and drop into Notepad. Real difficult to read tho'. I'll hold off reading it (I have serious eye problems) unless you get more BSOD's.

sure, thats fine. I'll report if there's another BSOD.

also i have a feeling that if it's a hardware problem, its not my HDD, because then it would be BSOD'ing randomly, not just during light processing.

 

[bBananasGoMoo]

so its been a couple days and my computer seems much better so far. I won't mark this solved until I don't have a BSOD for about a month tho, just in case.