Windows 7: BSODs FTW

Davidxtux · 04 Jul 2010

Background.. built a custom PC June 14 2010.. shortly after started getting BSODs. Made sure all drivers were up-to-date.. ran several different system tests including memtest for 14 hours. No problems detected... and thats it.. file is attached per captains instructions.

Ran Burnintest for 11 hours day before last... and no crashes

zigzag3143 · 04 Jul 2010

Quote: Originally Posted by Davidxtux

Background.. built a custom PC June 14 2010.. shortly after started getting BSODs. Made sure all drivers were up-to-date.. ran several different system tests including memtest for 14 hours. No problems detected... and thats it.. file is attached per captains instructions.

Ran Burnintest for 11 hours day before last... and no crashes

You have as many different causes as crashes. When that occurs it is invariably hardware. Please use these instructions to find out what that means and what to try. http://www.sevenforums.com/crash-loc...-what-try.html

I also note that you have sptd.sys loaded (either daemon tools, or alcohol) it is frequently a cause of BSOD's and should be removed

Ken

Bug Checks

Code:

Bugcheck code 000000C5
Bugcheck code 000000FE
Bugcheck code 000000C2
Bugcheck code 000000D1
Bugcheck code 0000000A
Bugcheck code 0000000A
Bugcheck code 00000109
Bugcheck code 0000000A
Bugcheck code 0000001E
Bugcheck code 00000109
Bugcheck code 0000003B
Bugcheck code 00000050
Bugcheck code 0000000A
Bugcheck code 000000D1
Bugcheck code 0000003B
Bugcheck code 0000003B
Bugcheck code 00000050
Bugcheck code 00000024
Bugcheck code 000000FE
Bugcheck code 00000050

System Uptime

Code:

System Uptime: 1 days 11:17:10.000
System Uptime: 0 days 0:46:40.399
System Uptime: 1 days 2:01:57.009
System Uptime: 0 days 0:36:10.153
System Uptime: 0 days 0:07:21.085
System Uptime: 3 days 6:07:58.712
System Uptime: 3 days 6:49:39.086
System Uptime: 1 days 8:48:05.563
System Uptime: 0 days 12:39:58.607
System Uptime: 0 days 5:46:00.001
System Uptime: 0 days 10:29:03.812
System Uptime: 0 days 16:15:58.177
System Uptime: 0 days 3:26:06.541
System Uptime: 0 days 0:27:54.451
System Uptime: 0 days 6:40:53.061
System Uptime: 0 days 14:42:00.393
System Uptime: 0 days 0:34:56.755
System Uptime: 0 days 4:12:07.632
System Uptime: 0 days 0:59:15.035
System Uptime: 2 days 16:31:16.083

Analysis

Code:

BugCheck C5, {fffffa000746ece8, 2, 1, fffff8000340b90d}
Probably caused by : cng.sys ( cng!GatherRandomKey+22c )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck FE, {6, fffffa8003eb05b0, 43787254, 0}
Probably caused by : sptd.sys ( sptd+424ce )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck C2, {7, 1097, f9089db3, fffffa8006f98330}
Probably caused by : ntkrnlmp.exe ( nt!IoRemoveIoCompletion+262 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck D1, {fffff880064dd8c9, 2, 0, fffff88004e12f22}
Probably caused by : wg111v3.sys ( wg111v3+12f22 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck A, {67697575, 2, 1, fffff80002e80275}
Probably caused by : sptd.sys ( sptd+424ce )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck A, {fffff900c28e8000, 2, 1, fffff80002ec9fa2}
Probably caused by : tdx.sys ( tdx!TdxIssueQueryAddressRequest+2a3 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 109, {a3a039d89812e6ed, 0, 82add4834cfdaad9, 101}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck A, {0, 2, 1, fffff80002e8ea70}
Probably caused by : ntkrnlmp.exe ( nt!KiProcessExpiredTimerList+110 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 1E, {ffffffffc000001d, fffffa80075bc2df, 2, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiDispatchException+1b9 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 109, {a3a039d898a21660, 0, 4229b9792ff42adf, 101}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 3B, {c0000005, fffff960000410bb, fffff88009376d00, 0}
Probably caused by : win32k.sys ( win32k!bttfdMapFontFileFD+17 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 50, {fffff87fd4c78927, 1, fffff88003ffd0d7, 5}
Probably caused by : atikmdag.sys ( atikmdag+3ba0d7 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck A, {0, 2, 1, fffff80002ed488c}
Probably caused by : win32k.sys ( win32k!DEVLOCKBLTOBJ::vClearRenderState+71 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck D1, {20, 2, 0, fffff88004323ee1}
Probably caused by : sptd.sys ( sptd+424ce )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 3B, {c0000005, fffff96000162ba2, fffff88001fa90d0, 0}
Probably caused by : win32k.sys ( win32k!TimersProc+142 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 3B, {c0000005, fffff80002fbe0f3, fffff880095c0b90, 0}
Probably caused by : ntkrnlmp.exe ( nt!ExFreePoolWithTag+43 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 50, {fffff8a00cac2780, 0, fffff880043b0b5b, 0}
Probably caused by : dxgmms1.sys ( dxgmms1!VidMmTerminateAllocation+3f )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 24, {1904fb, fffff88006cd11e8, fffff88006cd0a50, fffff80002eb8d16}
Probably caused by : Ntfs.sys ( Ntfs!NtfsCacheCoherencyFlush+5b )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck FE, {8, 6, 6, fffffa800528c640}
Probably caused by : usbfilter.sys ( usbfilter+3c82 )
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨
BugCheck 50, {ffffffff8b000201, 1, fffff960000f4036, 5}
Probably caused by : hardware ( win32k!xxxGetInputEvent+62 )

Davidxtux · 04 Jul 2010

Daemon tools which is uninstalled. The case is adequately cooled and I've performed quite a few 'burn in' and/or 'stress tests' and have never crashed during or right after these tests. The BSODs normally occur when idle. The few I do get is either when gaming or running streaming videos (with hardware accelerator on and off). I monitor the GPUs temperature closely while gaming and never had a shut-down due to heat. I have noticed exactly what you are saying about the reasons being random. I installed a vanilla version of 7 without updating any drivers and while the system is very slow it will not crash. Once I start updating with either recommended drivers or the most up-to-date drivers is when the BSOD's start occurring.

The system is at stock currently and even while having the whole system over-clocked the BSOD's do not slow down nor increase. They just seem to be occurring.

I did run windows xp 64bit on a seperate hdd and not a single crash of any kind. The system also appeared to be running faster and much more stable. Temperatures were lower system-wide and using much less resources running the same programs as windows 7. So what I can concur is my issues seem to be exclusive to windows 7 and my hardware drivers.

What I have done and crashes have still occurred:
Remove all graphic cards and ran on board vga with windows 7 driver and then up-to-date drivers.

Tried both sticks individually and then replaced both sticks.

Replaced CPU.. replaced power supply.. replaced motherboard.. replaced radeon 5770 2 times and then gts 250 two times. used a plethora of different drivers. cleanly uninstalling previous versions. Overclocked, underclocked, and stock.

Additional info:
The system normally doesn't run more then 12 hours without a crash and normally no dump or report is saved.

Jonathan_King · 04 Jul 2010

Be sure to run this SPTD installer/uninstaller to remove SPTD completely: DuplexSecure - Downloads

Davidxtux · 04 Jul 2010

SPTD is correctly removed and the service no longer there.

Jonathan_King · 04 Jul 2010

Great, let's watch and see if the BSODs stop now.

Davidxtux · 04 Jul 2010

Could a single service be causing random hardware and system services crashes?

Jonathan_King · 04 Jul 2010

Sure, anything is possible. A Microsoft service should not cause BSODs, but third-party programs can.

Davidxtux · 04 Jul 2010

And another BSOD.. check included file for information.. just completely random.. system was idle at time of crash

Capt.Jack Sparrow · 05 Jul 2010

Quote: Originally Posted by Davidxtux

And another BSOD.. check included file for information.. just completely random.. system was idle at time of crash

Hello !!

I was looking your Event Logs found something interesting that might be the issue.

Code:

Event[4]:
  Log Name: Application
  Source: Windows Error Reporting
  Date: 2010-02-03T03:26:49.000
  Event ID: 1001
  Task: N/A
  Level: Information
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: 37L4247E29-32
  Description: 
Fault bucket , type 0
Event Name: PnPGenericDriverFound
Response: Not available
Cab Id: 0

Problem signature:
P1: x64
P2: PCI\VEN_1002&DEV_68B8&SUBSYS_29911682&REV_00
P3: 
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

------------------------------------------------------------------------------------------------

  Log Name: Application
  Source: Application Error
  Date: 2010-02-03T01:21:02.000
  Event ID: 1000
  Task: Application Crashing Events
  Level: Error
  Opcode: Info
  Keyword: Classic
  User: N/A
  User Name: N/A
  Computer: Mojo-PC
  Description: 
Faulting application name: Setup.exe_XFX Graphic Card Installer, version: 2.0.0.0, time stamp: 0x4912c2a6
Faulting module name: Setup.exe, version: 2.0.0.0, time stamp: 0x4912c2a6
Exception code: 0xc0000005
Fault offset: 0x00007372
Faulting process id: 0x99c
Faulting application start time: 0x01caa4990d9ecca7
Faulting application path: D:\Setup.exe
Faulting module path: D:\Setup.exe
Report Id: 4cdb3eb5-108c-11df-a584-4487fc5026a0

win32k!NtUserEnumDisplayDevices+0x98 and win32 is related to your Display

And the PCI\VEN_1002&DEV_68B8&SUBSYS_29911682&REV_00 is

Code:

Device name: ATI 
Device ID: PCI\VEN_1002& DEV_68B8&  SUBSYS_29911682& REV_00\4& 1591CBDA& 0& 0008
Class: {4d36e968-e325-11ce-bfc1-08002be10318}
Version: 8.702.0.0

So uninstall the existing Driver for ATI and download a fresh Driver from manufacturer's website.

Then download the latest driver for your Logitech USB Keyboard because few crashes are pointing to

Code:

USB\VID_046D&PID_C315&REV_2800 - input.inf

Then Start | Under search type in CMD | Right Click and Run as administrator | SFC /SCANNOW

because few system files (Software Protection Platform Windows Plugin) are shown corrupted so run the repair will fix it.

Hope this helps,
Captain

Windows 7: BSODs FTW

BSODs FTW problems?