Random BSOD's in Windows 7

Normally I'm pretty good at troubleshooting...but I can't see to get this one figured out.

I've had my new system for about 3 months, and started receiving random BSOD's recently. They started occurring randomly, and didn't begin after any sort of installation, change, or driver update.

My specs are:

Phenom II 955
4GB DDR3 1600 G.SKILL Ripjaws
Gigabyte MA790XT-UD4P
Radeon 5850
500GB Spinpoint F3
CM N520 Cooler
750W Corsair
Windows 7 Home Premium x64

There really hasn't been any sort of pattern to the BSODs. They seem to occur more frequently within a few minutes of a cold boot. A couple crashes also occurred when using the internet or doing some word processing. So far, there have been no crashes whatsoever during gaming or video editing. Sometimes I get a couple per day, and sometimes I only get 1-2 per week.

I've tried various drivers for all of my components (used DriverSweeper to get rid of old drivers) and ran Memtest for about 6-8 hours with no errors. I'm also Prime95 stable and get about 20500 in 3DMark06. I also ran SeaTools to check for HDD problems and the results were fine. CPU temperatures are also acceptable - 30-35c idle, and 50-55c after Prime95.

Here's some screenshots of my blue screens:

Note that they have created NO memory dump files (it's configured to save them). The memory dump always hangs, which I'm assuming can be an issue?

http://i190.photobucket.com/albums/z...0325002258.jpg
http://i190.photobucket.com/albums/z...0329000805.jpg
http://i190.photobucket.com/albums/z...0331001732.jpg
http://i190.photobucket.com/albums/z...0331001735.jpg
http://i190.photobucket.com/albums/z...0405001840.jpg

Any ideas?

Well, that's part of the problem. The memory dumps are hanging on the BSOD, which is resulting in no .dmp files. It's configured properly though the Windows error reporting, but if you see in the screenshots, the dump hangs somewhere between 0-50. My minidumps folder is empty.

Hi -

The bugcheck on all 5 BSODs -

0x1e (0xc0000005,,,) = kernel mode exception; the exception is the 1st parm = 0xc0000005 = memory access violation. Only one lists a probable cause - the Microsoft Win32 subsystem driver win32k.sys, more than likely a default of sorts.

A few things to check re: NO DUMPS situation -
- page file should be on OS drive & set to "system managed"
- Windows Error Reporting system service cannot be disabled
- System crash settings should be set to full kernel memory dump. This setting will produce both a full kernel dump + a mini kernel dump

Full Kernel = \windows\memory.dmp (overwritten each BSOD)
Mini Kernels = \winodws\minidump (new ones created for each BSOD with date in filename)

You say the system is freezing while producing the dumps? Per screenshots, the time elapsed does vary -

Code:

80 secs
0
45
45
50

The second parm (after the 0xc0000005) is the address at which the exception occurred -

Code:

0x96000154b88
0x80002ee2b74
0x80002ecce39
0x80002e95b74
0x800030d7995

Memory addresses 2-5 are close enough that they probably represent the same object .

Here is slideshow for easy viewing -



Default settings are usually 100 secs. Did the Blue Screens freeze at the above times indicated?

Run 2 items, please -

- msinfo32 - save as NFO file
START | type msinfo32 | save w/ default NFO file ext

- DirectX Graphics Kernel Diagnostic report -
START | type dxdiag | bottom-center of screen, click "..64-bit.." | save as text file

Zip the NFO & text file up and attach to your next post.

Regards. . .

jcgriff2

.

Thanks for the response.

Yes, the blue screens froze at the time when I took the pictures. They were stuck at 80, 0, 45, 45, and 50.

I have my msinfo and dxdiag attached.

A few things to check re: NO DUMPS situation -
- page file should be on OS drive & set to "system managed"
- Windows Error Reporting system service cannot be disabled
- System crash settings should be set to full kernel memory dump. This setting will produce both a full kernel dump + a mini kernel dump

Also - forgot to mention, all of this is configured properly.

Hi -

There have been 9 BSODs recorded since 8 January 2010. No further details available from msinfo32 -

Code:

3/2/2010 02:10 WER , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0&#x0
2/27/2010 20:37 WER , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0&#x0
2/27/2010 01:03 WER , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0&#x0
2/26/2010 19:37 WER , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0&#x0
1/9/2010 12:15 WER , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0&#x0
1/9/2010 02:45 WER , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0&#x0
1/9/2010 01:07 WER , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0&#x0
1/9/2010 00:00 WER , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0&#x0
1/8/2010 22:38 WER , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0&#x0

`

You have multiple anti-virus/ malware apps running -

Code:

Avast
Spyware Terminator
Spybot - Search & Destroy
Malwarebytes' Anti-Malware
Microsoft Security Essentials (MSE)

Uninstall ALL of them. Re-boot after each uninstall so that boot and kernel mode drivers can be removed.

Reset the Windows Firewall to default settings, then re-install MSE only.

MSE --> http://www.microsoft.com/security_essentials/


ATI HD audio disabled -

Code:

ATI High Definition Audio Device 
HDAUDIO\FUNC_01&VEN_1002&DEV_AA01&SUBSYS_00AA0100&REV_1002\5&202DA424&0&0001
This device is disabled.

Check Device Manager for red/ yellow flags, specifically audio -
START | devmgmt.msc


There have been at least 175 app crashes since 1 January 2010, including MemDiagV1 -

Code:

4/6/2010 00:57 Windows Error Reporting Fault bucket , type 0
Event Name: MemDiagV1
Response: Not available
Cab Id: 0

Problem signature:
&#x0
4/6/2010 00:56 Windows Error Reporting Fault bucket 864324505, type 5
Event Name: MpTelemetry
Response: Not available
Cab Id: 0

Problem signature:&
4/6/2010 00:44 Windows Error Reporting Fault bucket , type 0
Event Name: MemDiagV1
Response: Not available
Cab Id: 0

Problem signature:
&#x0
4/5/2010 11:42 Windows Error Reporting Fault bucket 864324505, type 5
Event Name: MpTelemetry
Response: Not available
Cab Id: 0

Problem signature:&
4/4/2010 16:38 Windows Error Reporting Fault bucket 864324505, type 5
Event Name: MpTelemetry
Response: Not available
Cab Id: 0

Problem signature:&
4/3/2010 16:10 Windows Error Reporting Fault bucket 864324505, type 5
Event Name: MpTelemetry
Response: Not available
Cab Id: 0

Problem signature:&
4/1/2010 11:39 Windows Error Reporting Fault bucket 1070206357, type 5
Event Name: BEX
Response: Not available
Cab Id: 0

Problem signature:
4/1/2010 00:38 Windows Error Reporting Fault bucket , type 0
Event Name: BEX
Response: Not available
Cab Id: 0

Problem signature:
P1
4/1/2010 00:24 Application Error Faulting application name: Spywareterminator.exe, version: 2.6.9.132, time stamp: 0x4ba8a695
Faulting module name: wpdshext.dll, version: 6.1.7600.16385, time stamp: 0x4
3/31/2010 23:24 Windows Error Reporting Fault bucket 645945708, type 5
Event Name: RADAR_PRE_LEAK_64
Response: Not available
Cab Id: 0

Problem signa
3/31/2010 23:07 Windows Error Reporting Fault bucket 864324505, type 5
Event Name: MpTelemetry
Response: Not available
Cab Id: 0

Problem signature:&
3/31/2010 23:07 Windows Error Reporting Fault bucket 864324505, type 5
Event Name: MpTelemetry
Response: Not available
Cab Id: 0

Problem signature:&
3/31/2010 21:40 Windows Error Reporting Fault bucket 886575229, type 5
Event Name: MpTelemetry
Response: Not available
Cab Id: 0

Problem signature:&
3/31/2010 21:40 Windows Error Reporting Fault bucket 1011508395, type 5
Event Name: MSSecurityEssentials
Response: Not available
Cab Id: 0

Problem s
3/31/2010 21:29 Windows Error Reporting Fault bucket 1011508395, type 5
Event Name: MSSecurityEssentials
Response: Not available
Cab Id: 0

Problem s
3/31/2010 21:29 Windows Error Reporting Fault bucket , type 0
Event Name: MSSecurityEssentials
Response: Not available
Cab Id: 0

Problem signature:&
3/31/2010 21:29 Windows Error Reporting Fault bucket , type 0
Event Name: MpTelemetry
Response: Not available
Cab Id: 0

Problem signature:
&#
3/29/2010 04:44 Windows Error Reporting Fault bucket 643646497, type 5
Event Name: RADAR_PRE_LEAK_WOW64
Response: Not available
Cab Id: 0

Problem si
3/25/2010 03:14 Windows Error Reporting Fault bucket , type 0
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
&#x0
3/25/2010 03:14 Application Hang The program dirt2_game.exe version 1.1.0.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the 
3/25/2010 03:04 Application Error Faulting application name: dirt2_game.exe, version: 1.1.0.0, time stamp: 0x4b598827
Faulting module name: dirt2_game.exe, version: 1.1.0.0, time stamp: 0x4b598827&#x000d
3/25/2010 03:04 Windows Error Reporting Fault bucket 1016032331, type 5
Event Name: BEX
Response: Not available
Cab Id: 0

Problem signature:
3/25/2010 01:15 Windows Error Reporting Fault bucket 1775473211, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:&#x
3/25/2010 01:14 Application Error Faulting application name: EULA.exe, version: 0.0.0.0, time stamp: 0x2a425e19
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exce
3/22/2010 03:25 Windows Error Reporting Fault bucket , type 0
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
&#x0
3/22/2010 03:25 Application Hang The program BFBC2Game.exe version 1.0.1.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the A
3/21/2010 07:25 Application Error Faulting application name: Dwm.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc541
Faulting module name: fraps64.dll_unloaded, version: 0.0.0.0, time stamp: 0x4af24185&
3/21/2010 02:13 Windows Error Reporting Fault bucket 334982663, type 5
Event Name: ScriptedDiagFailure
Response: Not available
Cab Id: 0

Problem sig
3/21/2010 02:13 Windows Error Reporting Fault bucket , type 0
Event Name: ScriptedDiagFailure
Response: Not available
Cab Id: 0

Problem signature:&#
3/21/2010 02:08 Windows Error Reporting Fault bucket 349077275, type 5
Event Name: ScriptedDiagFailure
Response: Not available
Cab Id: 0

Problem sig
3/21/2010 02:08 Windows Error Reporting Fault bucket , type 0
Event Name: ScriptedDiagFailure
Response: Not available
Cab Id: 0

Problem signature:&#
3/21/2010 02:08 Windows Error Reporting Fault bucket 394270863, type 5
Event Name: ScriptedDiagFailure
Response: Not available
Cab Id: 0

Problem sig
3/21/2010 02:08 Windows Error Reporting Fault bucket , type 0
Event Name: ScriptedDiagFailure
Response: Not available
Cab Id: 0

Problem signature:&#
3/20/2010 06:21 Application Error Faulting application name: Dwm.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc541
Faulting module name: fraps64.dll_unloaded, version: 0.0.0.0, time stamp: 0x4af24185&
3/19/2010 02:06 Application Error Faulting application name: Dwm.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc541
Faulting module name: fraps64.dll_unloaded, version: 0.0.0.0, time stamp: 0x4af24185&
3/19/2010 01:32 Windows Error Reporting Fault bucket 1706001020, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:&#x
3/19/2010 01:31 Application Error Faulting application name: dirt2_game.exe, version: 1.1.0.0, time stamp: 0x4b598827
Faulting module name: dirt2_game.exe, version: 1.1.0.0, time stamp: 0x4b598827&#x000d
3/16/2010 12:02 Windows Error Reporting Fault bucket 644829565, type 5
Event Name: RADAR_PRE_LEAK_64
Response: Not available
Cab Id: 0

Problem signa
3/15/2010 05:00 Application Error Faulting application name: Dwm.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc541
Faulting module name: fraps64.dll_unloaded, version: 0.0.0.0, time stamp: 0x4af24185&
3/8/2010 05:51 Application Error Faulting application name: Dwm.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc541
Faulting module name: fraps64.dll_unloaded, version: 0.0.0.0, time stamp: 0x4af24185&
3/8/2010 05:51 Windows Error Reporting Fault bucket , type 0
Event Name: BEX64
Response: Not available
Cab Id: 0

Problem signature:

3/4/2010 05:41 Application Error Faulting application name: Dwm.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc541
Faulting module name: fraps64.dll_unloaded, version: 0.0.0.0, time stamp: 0x4af24185&
3/4/2010 05:01 Windows Error Reporting Fault bucket 643646497, type 5
Event Name: RADAR_PRE_LEAK_WOW64
Response: Not available
Cab Id: 0

Problem si
3/2/2010 02:10 Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
&#x
3/2/2010 00:57 Windows Error Reporting Fault bucket 917024193, type 5
Event Name: RADAR_PRE_LEAK_WOW64
Response: Not available
Cab Id: 0

Problem si
2/28/2010 00:40 Windows Error Reporting Fault bucket 763959273, type 5
Event Name: RADAR_PRE_LEAK_WOW64
Response: Not available
Cab Id: 0

Problem si
2/27/2010 20:38 Application Error Faulting application name: AMD OverDrive.exe, version: 3.1.0.0, time stamp: 0x4ae01c70
Faulting module name: FRAPS32.DLL, version: 3.0.0.10475, time stamp: 0x4af2418c&#x
2/27/2010 20:38 Windows Error Reporting Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
&#x00
2/27/2010 20:37 Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
&#x
2/27/2010 01:21 Windows Error Reporting Fault bucket 992792730, type 5
Event Name: RADAR_PRE_LEAK_WOW64
Response: Not available
Cab Id: 0

Problem si
2/27/2010 01:04 Windows Error Reporting Fault bucket X64_0x117_Tdr:2_IMAGE_atikmpag.sys, type 0
Event Name: LiveKernelEvent
Response: Microsoft Windows Error Reporting
2/27/2010 01:03 Windows Error Reporting Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:&#x000
2/27/2010 01:03 Windows Error Reporting Fault bucket X64_0x117_Tdr:2_IMAGE_atikmpag.sys, type 0
Event Name: LiveKernelEvent
Response: Microsoft Windows Error Reporting
2/27/2010 01:03 Windows Error Reporting Fault bucket X64_0x117_Tdr:2_IMAGE_atikmpag.sys, type 0
Event Name: LiveKernelEvent
Response: Microsoft Windows Error Reporting
2/27/2010 01:03 Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
&#x
2/27/2010 01:02 Windows Error Reporting Fault bucket 327856891, type 5
Event Name: ScriptedDiagFailure
Response: Not available
Cab Id: 0

Problem sig
2/27/2010 01:02 Windows Error Reporting Fault bucket 327856891, type 5
Event Name: ScriptedDiagFailure
Response: Not available
Cab Id: 0

Problem sig
2/27/2010 01:02 Windows Error Reporting Fault bucket 815372315, type 5
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:&#x
2/27/2010 01:02 Windows Error Reporting Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
&#x00
2/27/2010 01:02 Windows Error Reporting Fault bucket 1732283799, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:&#x
2/26/2010 21:48 Application Error Faulting application name: battleforge.exe, version: 1.2.0.0, time stamp: 0x4b869920
Faulting module name: battleforge.exe, version: 1.2.0.0, time stamp: 0x4b869920&#x00
2/26/2010 21:48 Windows Error Reporting Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
&#x00
2/26/2010 21:48 Windows Error Reporting Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:&#x000
2/26/2010 21:46 Application Error Faulting application name: battleforge.exe, version: 1.2.0.0, time stamp: 0x4b869920
Faulting module name: FRAPS32.DLL, version: 3.0.0.10475, time stamp: 0x4af2418c&#x00
2/26/2010 21:46 Windows Error Reporting Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:&#x000
2/26/2010 21:46 Windows Error Reporting Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
&#x00
2/26/2010 20:38 Windows Error Reporting Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:&#x000
2/26/2010 20:38 Windows Error Reporting Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:&#x000
2/26/2010 20:12 Windows Error Reporting Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:&#x000
2/26/2010 20:12 Windows Error Reporting Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:&#x000
2/26/2010 19:48 Windows Error Reporting Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:&#x000
2/26/2010 19:48 Windows Error Reporting Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:&#x000
2/26/2010 19:37 Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
&#x
2/26/2010 19:35 Windows Error Reporting Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:&#x000
2/26/2010 19:35 Windows Error Reporting Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:&#x000
2/26/2010 09:01 Application Error Faulting application name: Dwm.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc541
Faulting module name: fraps64.dll_unloaded, version: 0.0.0.0, time stamp: 0x4af24185&
2/26/2010 03:20 Windows Error Reporting Fault bucket 983485770, type 5
Event Name: RADAR_PRE_LEAK_WOW64
Response: Not available
Cab Id: 0

Problem si
2/25/2010 19:20 Application Error Faulting application name: Dwm.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc541
Faulting module name: fraps64.dll_unloaded, version: 0.0.0.0, time stamp: 0x4af24185&
2/25/2010 05:42 Application Error Faulting application name: Dwm.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc541
Faulting module name: fraps64.dll_unloaded, version: 0.0.0.0, time stamp: 0x4af24185&
2/25/2010 05:31 Windows Error Reporting Fault bucket , type 0
Event Name: AppHangTransient
Response: Not available
Cab Id: 0

Problem signature:&#x00
2/24/2010 23:07 Windows Error Reporting Fault bucket 8650105, type 5
Event Name: PCA2
Response: Not available
Cab Id: 0

Problem signature:
&#
2/23/2010 01:40 Windows Error Reporting Fault bucket 644106094, type 5
Event Name: RADAR_PRE_LEAK_WOW64
Response: Not available
Cab Id: 0

Problem si
2/22/2010 05:33 Windows Error Reporting Fault bucket , type 0
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
&#x0
2/22/2010 05:33 Application Hang The program left4dead2.exe version 0.0.0.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the 
2/20/2010 19:48 Windows Error Reporting Fault bucket 675109619, type 5
Event Name: RADAR_PRE_LEAK_WOW64
Response: Not available
Cab Id: 0

Problem si
2/20/2010 08:48 Windows Error Reporting Fault bucket 643982283, type 5
Event Name: RADAR_PRE_LEAK_WOW64
Response: Not available
Cab Id: 0

Problem si
2/18/2010 06:02 Application Error Faulting application name: Dwm.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc541
Faulting module name: fraps64.dll_unloaded, version: 0.0.0.0, time stamp: 0x4af24185&
2/18/2010 01:02 Windows Error Reporting Fault bucket 327856891, type 5
Event Name: ScriptedDiagFailure
Response: Not available
Cab Id: 0

Problem sig
2/18/2010 01:02 Windows Error Reporting Fault bucket 327856891, type 5
Event Name: ScriptedDiagFailure
Response: Not available
Cab Id: 0

Problem sig
2/18/2010 01:01 Windows Error Reporting Fault bucket , type 0
Event Name: ScriptedDiagFailure
Response: Not available
Cab Id: 0

Problem signature:&#
2/13/2010 18:49 Windows Error Reporting Fault bucket 388111150, type 5
Event Name: PnPDeviceProblemCode
Response: Not available
Cab Id: 0

Problem si
2/11/2010 22:49 Windows Error Reporting Fault bucket 388111150, type 5
Event Name: PnPDeviceProblemCode
Response: Not available
Cab Id: 0

Problem si
2/11/2010 21:16 Application Error Faulting application name: AMD OverDrive.exe, version: 3.1.0.0, time stamp: 0x4ae01c70
Faulting module name: FRAPS32.DLL_unloaded, version: 0.0.0.0, time stamp: 0x4af241
2/11/2010 21:16 Windows Error Reporting Fault bucket , type 0
Event Name: BEX
Response: Not available
Cab Id: 0

Problem signature:
P1
2/11/2010 03:10 Windows Error Reporting Fault bucket 953303865, type 5
Event Name: RADAR_PRE_LEAK_WOW64
Response: Not available
Cab Id: 0

Problem si
2/10/2010 19:09 Windows Error Reporting Fault bucket 643860152, type 5
Event Name: RADAR_PRE_LEAK_WOW64
Response: Not available
Cab Id: 0

Problem si
2/10/2010 05:16 Windows Error Reporting Fault bucket 298455208, type 5
Event Name: PnPGenericDriverFound
Response: Not available
Cab Id: 0

Problem s
2/9/2010 20:42 Application Error Faulting application name: attdrv64.exe, version: 0.0.0.0, time stamp: 0x4947bdb4
Faulting module name: KERNELBASE.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdbdf&#
2/9/2010 20:42 Windows Error Reporting Fault bucket 1384233240, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:&#x
2/8/2010 22:29 Windows Error Reporting Fault bucket 5551255, type 5
Event Name: ServiceHang
Response: Not available
Cab Id: 0

Problem signature:&#x
2/8/2010 22:29 Windows Error Reporting Fault bucket 883929553, type 5
Event Name: StartupRepairOnline
Response: Not available
Cab Id: 0

Problem sig
2/8/2010 22:29 Windows Error Reporting Fault bucket , type 0
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
&#x0
2/8/2010 22:29 Windows Error Reporting Fault bucket 787308587, type 5
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:&#x
2/8/2010 22:29 Windows Error Reporting Fault bucket 787308587, type 5
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:&#x
2/8/2010 22:28 Windows Error Reporting Fault bucket 966055255, type 5
Event Name: BEX
Response: Not available
Cab Id: 0

Problem signature:
&
2/8/2010 22:28 Windows Error Reporting Fault bucket 822918239, type 5
Event Name: BEX
Response: Not available
Cab Id: 0

Problem signature:
&
2/8/2010 21:20 Windows Error Reporting Fault bucket , type 0
Event Name: ServiceHang
Response: Not available
Cab Id: 0

Problem signature:
&#
2/8/2010 21:20 Windows Error Reporting Fault bucket , type 0
Event Name: ServiceHang
Response: Not available
Cab Id: 0

Problem signature:
&#
2/8/2010 21:08 Application Error Faulting application name: Dwm.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc541
Faulting module name: fraps64.dll_unloaded, version: 0.0.0.0, time stamp: 0x4af24185&
2/8/2010 20:44 Application Error Faulting application name: AMD OverDrive.exe, version: 3.1.0.0, time stamp: 0x4ae01c70
Faulting module name: FRAPS32.DLL_unloaded, version: 0.0.0.0, time stamp: 0x4af241
2/8/2010 20:44 Windows Error Reporting Fault bucket 822918239, type 5
Event Name: BEX
Response: Not available
Cab Id: 0

Problem signature:
&
2/8/2010 20:42 Application Error Faulting application name: Dwm.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc541
Faulting module name: fraps64.dll_unloaded, version: 0.0.0.0, time stamp: 0x4af24185&
2/7/2010 02:02 Application Error Faulting application name: AMD OverDrive.exe, version: 3.1.0.0, time stamp: 0x4ae01c70
Faulting module name: FRAPS32.DLL_unloaded, version: 0.0.0.0, time stamp: 0x4af241
2/7/2010 02:02 Windows Error Reporting Fault bucket , type 0
Event Name: BEX
Response: Not available
Cab Id: 0

Problem signature:
P1
2/7/2010 01:44 Application Error Faulting application name: Dwm.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc541
Faulting module name: fraps64.dll_unloaded, version: 0.0.0.0, time stamp: 0x4af24185&
2/7/2010 01:44 Windows Error Reporting Fault bucket , type 0
Event Name: BEX64
Response: Not available
Cab Id: 0

Problem signature:

2/7/2010 00:06 Application Error Faulting application name: Dwm.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc541
Faulting module name: fraps64.dll_unloaded, version: 0.0.0.0, time stamp: 0x4af24185&
2/7/2010 00:06 Windows Error Reporting Fault bucket , type 0
Event Name: BEX64
Response: Not available
Cab Id: 0

Problem signature:

2/6/2010 08:00 Application Error Faulting application name: Dwm.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc541
Faulting module name: fraps64.dll_unloaded, version: 0.0.0.0, time stamp: 0x4af24185&
2/6/2010 07:40 Windows Error Reporting Fault bucket 644219225, type 5
Event Name: RADAR_PRE_LEAK_64
Response: Not available
Cab Id: 0

Problem signa
2/5/2010 12:26 Windows Error Reporting Fault bucket 941731962, type 5
Event Name: BEX
Response: Not available
Cab Id: 0

Problem signature:
&
2/5/2010 12:25 Application Error Faulting application name: chrome.exe, version: 0.0.0.0, time stamp: 0x4b57e078
Faulting module name: FRAPS32.DLL, version: 3.0.0.10475, time stamp: 0x4af2418c
&#
2/5/2010 12:25 Application Error Faulting application name: chrome.exe, version: 0.0.0.0, time stamp: 0x4b57e078
Faulting module name: FRAPS32.DLL_unloaded, version: 0.0.0.0, time stamp: 0x4af2418c&#x00
2/5/2010 12:25 Windows Error Reporting Fault bucket 941058163, type 5
Event Name: BEX
Response: Not available
Cab Id: 0

Problem signature:
&
2/4/2010 22:27 Windows Error Reporting Fault bucket , type 0
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
&#x0
2/4/2010 22:27 Application Hang The program SpybotSD.exe version 1.6.2.46 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the A
2/4/2010 12:29 Application Error Faulting application name: Dwm.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc541
Faulting module name: fraps64.dll_unloaded, version: 0.0.0.0, time stamp: 0x4af24185&
2/1/2010 23:51 Application Error Faulting application name: mcreference.exe, version: 1.6.1.35781, time stamp: 0x48ec16fd
Faulting module name: quartz.dll, version: 6.6.7600.16385, time stamp: 0x4a5bdad
2/1/2010 23:51 Windows Error Reporting Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
&#x00
2/1/2010 23:49 Application Error Faulting application name: mcreference.exe, version: 1.6.1.35781, time stamp: 0x48ec16fd
Faulting module name: quartz.dll, version: 6.6.7600.16385, time stamp: 0x4a5bdad
2/1/2010 23:49 Windows Error Reporting Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
&#x00
2/1/2010 23:46 Application Error Faulting application name: mcreference.exe, version: 1.6.1.35781, time stamp: 0x48ec16fd
Faulting module name: quartz.dll, version: 6.6.7600.16385, time stamp: 0x4a5bdad
2/1/2010 23:46 Windows Error Reporting Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
&#x00
2/1/2010 04:08 Windows Error Reporting Fault bucket , type 0
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
&#x0
2/1/2010 04:08 Application Hang The program left4dead2.exe version 0.0.0.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the 
1/31/2010 23:38 Application Error Faulting application name: Dwm.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc541
Faulting module name: fraps64.dll_unloaded, version: 0.0.0.0, time stamp: 0x4af24185&
1/31/2010 21:42 Application Error Faulting application name: DivX Converter.exe, version: 7.1.0.124, time stamp: 0x4a00e22d
Faulting module name: quartz.dll, version: 6.6.7600.16385, time stamp: 0x4a5bda
1/31/2010 21:42 Windows Error Reporting Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
&#x00
1/31/2010 20:37 Windows Error Reporting Fault bucket , type 0
Event Name: PCA2
Response: Not available
Cab Id: 0

Problem signature:
P
1/31/2010 00:34 Windows Error Reporting Fault bucket , type 0
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
&#x0
1/31/2010 00:34 Application Hang The program dirt2_game.exe version 1.0.0.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the 
1/29/2010 03:48 Windows Error Reporting Fault bucket , type 0
Event Name: AppHangTransient
Response: Not available
Cab Id: 0

Problem signature:&#x00
1/29/2010 03:35 Application Error Faulting application name: Dwm.exe, version: 6.1.7600.16385, time stamp: 0x4a5bc541
Faulting module name: fraps64.dll_unloaded, version: 0.0.0.0, time stamp: 0x4af24185&
1/28/2010 23:41 Windows Error Reporting Fault bucket , type 0
Event Name: AppHangTransient
Response: Not available
Cab Id: 0

Problem signature:&#x00
1/28/2010 04:30 Windows Error Reporting Fault bucket , type 0
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
&#x0
1/28/2010 04:30 Application Hang The program AMD OverDrive.exe version 3.0.2.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in t
1/27/2010 23:32 Windows Error Reporting Fault bucket , type 0
Event Name: PnPDriverNotFound
Response: Not available
Cab Id: 0

Problem signature:&#x0
1/27/2010 23:24 Windows Error Reporting Fault bucket , type 0
Event Name: PnPDeviceProblemCode
Response: Not available
Cab Id: 0

Problem signature:&
1/21/2010 10:14 Windows Error Reporting Fault bucket , type 0
Event Name: PnPGenericDriverFound
Response: Not available
Cab Id: 0

Problem signature:
1/9/2010 12:33 Windows Error Reporting Fault bucket 644840794, type 5
Event Name: RADAR_PRE_LEAK_WOW64
Response: Not available
Cab Id: 0

Problem si
1/9/2010 12:15 Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
&#x
1/9/2010 03:42 Windows Error Reporting Fault bucket 778578452, type 5
Event Name: RADAR_PRE_LEAK_WOW64
Response: Not available
Cab Id: 0

Problem si
1/9/2010 02:45 Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
&#x
1/9/2010 01:09 Windows Error Reporting Fault bucket 644409597, type 5
Event Name: RADAR_PRE_LEAK_64
Response: Not available
Cab Id: 0

Problem signa
1/9/2010 01:07 Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
&#x
1/9/2010 00:00 Windows Error Reporting Fault bucket 883929553, type 5
Event Name: StartupRepairOnline
Response: Not available
Cab Id: 0

Problem sig
1/9/2010 00:00 Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
&#x
1/8/2010 23:48 Windows Error Reporting Fault bucket , type 0
Event Name: AppHangTransient
Response: Not available
Cab Id: 0

Problem signature:&#x00
1/8/2010 22:38 Windows Error Reporting Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
&#x
1/8/2010 22:38 Windows Error Reporting Fault bucket , type 0
Event Name: StartupRepairOnline
Response: Not available
Cab Id: 0

Problem signature:&#
1/8/2010 21:22 Windows Error Reporting Fault bucket 778637179, type 5
Event Name: RADAR_PRE_LEAK_WOW64
Response: Not available
Cab Id: 0

Problem si
1/8/2010 03:41 Windows Error Reporting Fault bucket 720288311, type 5
Event Name: RADAR_PRE_LEAK_WOW64
Response: Not available
Cab Id: 0

Problem si
1/7/2010 20:23 Application Error Faulting application name: Steam.exe, version: 1.0.0.0, time stamp: 0x4aaadaf8
Faulting module name: Steam.dll, version: 2.0.801.572, time stamp: 0x4b678b85
&#x00
1/7/2010 20:23 Windows Error Reporting Fault bucket 966055255, type 5
Event Name: BEX
Response: Not available
Cab Id: 0

Problem signature:
&
1/7/2010 19:57 Windows Error Reporting Fault bucket , type 0
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
&#x0
1/7/2010 19:57 Application Hang The program Steam.exe version 1.0.0.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Actio
1/7/2009 07:54 Windows Error Reporting Fault bucket , type 0
Event Name: AppHangTransient
Response: Not available
Cab Id: 0

Problem signature:&#x00
1/7/2009 06:30 Windows Error Reporting Fault bucket , type 0
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
&#x0
1/7/2009 06:30 Application Hang The program Steam.exe version 1.0.0.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Actio
1/7/2009 06:29 Windows Error Reporting Fault bucket , type 0
Event Name: AppHangTransient
Response: Not available
Cab Id: 0

Problem signature:&#x00
1/7/2009 06:28 Windows Error Reporting Fault bucket , type 0
Event Name: AppHangTransient
Response: Not available
Cab Id: 0

Problem signature:&#x00
1/7/2009 05:07 Windows Error Reporting Fault bucket , type 0
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
&#x0
1/7/2009 05:07 Application Hang The program Steam.exe version 1.0.0.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Actio
1/7/2009 04:20 Windows Error Reporting Fault bucket 778578452, type 5
Event Name: RADAR_PRE_LEAK_WOW64
Response: Not available
Cab Id: 0

Problem si
1/1/2009 08:22 Windows Error Reporting Fault bucket 643646497, type 5
Event Name: RADAR_PRE_LEAK_WOW64
Response: Not available
Cab Id: 0

Problem si

`

FREQUENT CRASHES
- Fraps
- Desktop Window Manager (DWM), which handles graphics
- ATI video
- 14 "Live Kernel Events" - 0x117 = video TDR timeout = the video driver failed to respond in alloted time, but did ultimately reset
- 0x117 just a step below 0x116 BSOD = TDR timeout, but video driver is unable to recover

Check Problem Reports -
START | type view all | "View all problem reports" | 2x-click on line item for additional details

Given the memory test crashing, run memtest86+ -- one stick at a time and alternate the slots.

memtest86+ --> Memtest86+ - Advanced Memory Diagnostic Tool

Use app like ImgBurn to burn ISO to CD --> The Official ImgBurn Website

When was Windows 7 installed?
Was Windows 7 first OS, or upgrade from Vista?

I don't know the reason for no-dump situation at this time. To test dump creation ability, bring up Task Manager and see if you can create a dump file -
- "Processes" tab
- bottom-left of screen "Show Processes from all Users"
- RIGHT-click on any svchost
- select "Create Dump"

Does it complete?

How long after boot does the system BSOD - seconds or can it be hours?

Regards. . .

jcgriff2
.

There have been 9 BSODs recorded since 8 January 2010. No further details available from msinfo32 -

There have actually been about a dozen in the past 1-2 weeks. I'm guessing that they aren't being logged due to the fact that there isn't a memory dump. If I view the "reliability history" from the control panel, they all show up as "Windows was not shut down properly".

You have multiple anti-virus/ malware apps running -

The only one that has been running real-time has been Avast 5.0. Spyware Terminator, Spybot S&D, & MalewareBytes are just scanning utilities that have no running processes unless I choose to run a scan. As for MSE, I just installed it 2-3 days ago to try a full system scan due to the issues I've been having.

I'll try removing Avast & using MSE, but it's detection rate isn't as good as Avast's. Either way, I'll see if that perhaps resolves the issue.

ATI HD audio disabled -

ATI HD audio is only for HDMI, which I'm not using. My audio drivers are for the onboard Realtek codec.

FREQUENT CRASHES
- Fraps
- Desktop Window Manager (DWM), which handles graphics
- ATI video
- 14 "Live Kernel Events" - 0x117 = video TDR timeout = the video driver failed to respond in alloted time, but did ultimately reset
- 0x117 just a step below 0x116 BSOD = TDR timeout, but video driver is unable to recover

I actually got the Fraps issue fixed - it was due to a corrupt installation. As for DWM, most of those occur when I shut down. Occasionally it will pop-up with "DWM is not responding", then Windows initiates the shut-down.

As for the others, I have no idea.

Given the memory test crashing, run memtest86+ -- one stick at a time and alternate the slots.

I ran 10 or so passes of memtest about 3-4 days ago with no errors. I also ran the Windows memory test utility last night, and it passed.

Would testing one stick at a time make a large difference with the memtest results? If so, I'll definitely give it a go.

When was Windows 7 installed?
Was Windows 7 first OS

It's a new PC as of February. Windows 7 was the first and only OS installed.

I don't know the reason for no-dump situation at this time. To test dump creation ability, bring up Task Manager and see if you can create a dump file -
- "Processes" tab
- bottom-left of screen "Show Processes from all Users"
- RIGHT-click on any svchost
- select "Create Dump"

Does it complete?

It creates the dump just fine.

I just changed the Windows error reporting to create a minidump rather than the full kernal dump. I'll see if this makes a difference on the next BSOD, whenever that may be.

How long after boot does the system BSOD - seconds or can it be hours?

It's been almost entirely random. Out of the dozen or so over the past couple weeks, I want to say that about half were within 60 seconds of Windows starting up. The other half happened minutes to hours later.

Oddly enough, no crash has ever occurred during any stressful situation - no crashes during gaming, Prime95, Furmark, 3DMark, Everest, Heaven 1.0, etc. This is what makes me think that it probably isn't a RAM issue. With 10 or so memtest passes, Windows memory diagnostic, and 12+ hours of Prime95 blend...surely at some point a RAM problem would have -likely- caused some issue.

If there are BSODs not being recorded, it is usually due to catastrophic and sudden hardware failure. Windows 7 will fore-go producing a dump file to save itself.

memtest86+ should be run 1 stick at a time and alternate slots as well.

To see if you can escalate BSOD process, verify your 3rd party drivers -

Run --> DRIVER VERIFIER - Windows 7 & Vista

Regards. . .

jcgriff2

.

Thanks for the info. I ran the verifier all day yesterday and didn't experience any BSOD's or crashes. The last BSOD was on the 5th, so I've gone a few days now with no issues. The only change I've made since the last blue screen was disabling the fan control for my CPU fan, so that it always runs at 100%. I can't imagine that was the issue, given temperatures were more than acceptable.

If/when the next BSOD occurs, I'll be sure to post with some details. After some research, it seems that some (very few) people have had issues with dumps not being created on Windows 7 unless the "small dump" option was selected. I changed it to that...so hopefully next time I'll be able to provide the minidump.

Thanks.

J.C. Griffith,
This entire thread has been very helpful and informative. Presently Verifier doesn't like me. Tried it out and I got the gray-lined screen-of-death. Am trying to determine why now. Incidentally, I was having no problems, at least that I was aware of.

If I don't get any smarter, I'll start a new thread and go from there so as not to interfere with the train of thought here.