Confusing BSoD

A

aegdall

New member
Joined
Jul 2, 2012
Posts
3
I've run into a BSoD I can't track down an answer to. As it has happened on multiple machines (same configuration, same install dates, same network) I have blamed the environment, ie. networking, but after replacing switches, cabling, etc. I'm still seeing the crashes. Attached are the results of the jcgriff2 BSOD collection App and a few dump files, the newest occuring during an attemted perfmon /report. I have been unable to complete the perfmon /report.

Machine Info:
OS - Windows 7 x64 OEM
1 Year old system
OS has never been reinstalled
CPU: i5-2400
MB/GPU: Intel DH67BL Motherboard using onboard graphics
PS: Inwin Z589T Chassis with 350W Power Supply
WhiteBox system - no specific model
 
Hi -

There were 27 BSODs - going back to March 2011.
25 - 0x101 = CPU hang
2 - 0x119 = Video related; Intel video named (both were March 2011)

Some of the dumps were VERIFIER_ENABLED, yet no 3rd party driver was named. This points to hardware failure.

You mentioned other systems with similar BSODs?
Are they all the same hardware manufacturer?
Was the same image of Wiindows 7 installed on all?

Regards. . .

jcgriff2


`


BSOD SUMMARY

Code: 
[font=lucida console]
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\020312-11575-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Fri Feb  3 15:31:30.840 2012 (UTC - 4:00)
System Uptime: 8 days 0:43:05.395
BugCheck 101, {31, 0, fffff880009ea180, 1}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  PresentationFo
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000031 00000000`00000000 fffff880`009ea180 00000000`00000001
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\030212-13915-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Fri Mar  2 10:55:30.548 2012 (UTC - 4:00)
System Uptime: 8 days 23:41:16.414
BugCheck 101, {31, 0, fffff88002f64180, 2}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000031 00000000`00000000 fffff880`02f64180 00000000`00000002
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\030512-16660-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Mon Mar  5 15:56:54.792 2012 (UTC - 4:00)
System Uptime: 3 days 5:00:22.801
BugCheck 101, {31, 0, fffff88002f64180, 2}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000031 00000000`00000000 fffff880`02f64180 00000000`00000002
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\030812-11154-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Thu Mar  8 16:10:51.133 2012 (UTC - 4:00)
System Uptime: 3 days 0:07:20.105
BugCheck 101, {31, 0, fffff880009ea180, 1}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  QBW32.EXE
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000031 00000000`00000000 fffff880`009ea180 00000000`00000001
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\031212-13462-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sat Mar 10 15:12:02.862 2012 (UTC - 4:00)
System Uptime: 1 days 23:00:50.750
BugCheck 101, {31, 0, fffff880009ea180, 1}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  PresentationFo
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000031 00000000`00000000 fffff880`009ea180 00000000`00000001
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\041112-11060-01.dmp]
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Wed Apr 11 16:41:44.415 2012 (UTC - 4:00)
System Uptime: 9 days 7:36:37.766
BugCheck 101, {31, 0, fffff880009eb180, 1}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000031 00000000`00000000 fffff880`009eb180 00000000`00000001
BiosVersion = BLH6710H.86A.0076.2010.1115.1959
BiosReleaseDate = 11/15/2010
SystemManufacturer =                                 
SystemProductName =                                 
MaxSpeed:     3100
CurrentSpeed: 3093
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\043012-10639-01.dmp]
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Debug session time: Mon Apr 30 10:21:05.662 2012 (UTC - 4:00)
System Uptime: 3 days 22:36:52.744
BugCheck 101, {31, 0, fffff88003165180, 2}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  QBW32.EXE
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000031 00000000`00000000 fffff880`03165180 00000000`00000002
BiosVersion = BLH6710H.86A.0076.2010.1115.1959
BiosReleaseDate = 11/15/2010
SystemManufacturer =                                 
SystemProductName =                                 
MaxSpeed:     3100
CurrentSpeed: 3093
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\050112-14804-01.dmp]
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Debug session time: Tue May  1 10:52:20.938 2012 (UTC - 4:00)
System Uptime: 1 days 0:27:15.022
BugCheck 101, {31, 0, fffff88003165180, 2}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  QBW32.EXE
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000031 00000000`00000000 fffff880`03165180 00000000`00000002
BiosVersion = BLH6710H.86A.0076.2010.1115.1959
BiosReleaseDate = 11/15/2010
SystemManufacturer =                                 
SystemProductName =                                 
MaxSpeed:     3100
CurrentSpeed: 3093
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\050212-16660-01.dmp]
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Debug session time: Wed May  2 09:46:18.604 2012 (UTC - 4:00)
System Uptime: 0 days 22:50:38.533
BugCheck 101, {31, 0, fffff880031d7180, 3}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  EXCEL.EXE
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000031 00000000`00000000 fffff880`031d7180 00000000`00000003
BiosVersion = BLH6710H.86A.0076.2010.1115.1959
BiosReleaseDate = 11/15/2010
SystemManufacturer =                                 
SystemProductName =                                 
MaxSpeed:     3100
CurrentSpeed: 3093
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\051412-17253-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Mon May 14 15:46:10.210 2012 (UTC - 4:00)
System Uptime: 2 days 12:35:18.385
BugCheck 101, {31, 0, fffff88003165180, 2}
*** WARNING: Unable to verify checksum for win32k.sys
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000031 00000000`00000000 fffff880`03165180 00000000`00000002
BiosVersion = BLH6710H.86A.0076.2010.1115.1959
BiosReleaseDate = 11/15/2010
SystemManufacturer =                                 
SystemProductName =                                 
MaxSpeed:     3100
CurrentSpeed: 3093
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\051712-15397-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Thu May 17 11:14:07.777 2012 (UTC - 4:00)
System Uptime: 0 days 1:58:31.942
BugCheck 101, {31, 0, fffff880009eb180, 1}
*** WARNING: Unable to verify checksum for win32k.sys
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000031 00000000`00000000 fffff880`009eb180 00000000`00000001
BiosVersion = BLH6710H.86A.0076.2010.1115.1959
BiosReleaseDate = 11/15/2010
SystemManufacturer =                                 
SystemProductName =                                 
MaxSpeed:     3100
CurrentSpeed: 3093
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\060812-18267-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Fri Jun  8 11:52:41.814 2012 (UTC - 4:00)
System Uptime: 2 days 0:14:20.594
BugCheck 101, {31, 0, fffff88003165180, 2}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  QBW32.EXE
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000031 00000000`00000000 fffff880`03165180 00000000`00000002
BiosVersion = BLH6710H.86A.0076.2010.1115.1959
BiosReleaseDate = 11/15/2010
SystemManufacturer =                                 
SystemProductName =                                 
MaxSpeed:     3100
CurrentSpeed: 3093
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\061212-11840-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Tue Jun 12 13:46:34.214 2012 (UTC - 4:00)
System Uptime: 1 days 4:39:53.933
BugCheck 101, {31, 0, fffff880009eb180, 1}
*** WARNING: Unable to verify checksum for win32k.sys
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000031 00000000`00000000 fffff880`009eb180 00000000`00000001
BiosVersion = BLH6710H.86A.0076.2010.1115.1959
BiosReleaseDate = 11/15/2010
SystemManufacturer =                                 
SystemProductName =                                 
MaxSpeed:     3100
CurrentSpeed: 3093
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\062012-15038-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Wed Jun 20 09:19:04.976 2012 (UTC - 4:00)
System Uptime: 6 days 6:09:53.304
BugCheck 101, {31, 0, fffff88003165180, 2}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000031 00000000`00000000 fffff880`03165180 00000000`00000002
BiosVersion = BLH6710H.86A.0076.2010.1115.1959
BiosReleaseDate = 11/15/2010
SystemManufacturer =                                 
SystemProductName =                                 
MaxSpeed:     3100
CurrentSpeed: 3093
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\062612-12885-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Tue Jun 26 16:07:49.503 2012 (UTC - 4:00)
System Uptime: 4 days 7:32:46.545
BugCheck 101, {31, 0, fffff880009eb180, 1}
*** WARNING: Unable to verify checksum for win32k.sys
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000031 00000000`00000000 fffff880`009eb180 00000000`00000001
BiosVersion = BLH6710H.86A.0076.2010.1115.1959
BiosReleaseDate = 11/15/2010
SystemManufacturer =                                 
SystemProductName =                                 
MaxSpeed:     3100
CurrentSpeed: 3093
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\062912-14882-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Fri Jun 29 10:18:39.538 2012 (UTC - 4:00)
System Uptime: 2 days 17:44:51.142
BugCheck 101, {31, 0, fffff880031d7180, 3}
*** WARNING: Unable to verify checksum for win32k.sys
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000031 00000000`00000000 fffff880`031d7180 00000000`00000003
BiosVersion = BLH6710H.86A.0076.2010.1115.1959
BiosReleaseDate = 11/15/2010
SystemManufacturer =                                 
SystemProductName =                                 
MaxSpeed:     3100
CurrentSpeed: 3093
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\070212-10732-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Mon Jul  2 10:08:53.566 2012 (UTC - 4:00)
System Uptime: 1 days 12:50:26.584
BugCheck 101, {31, 0, fffff880009eb180, 1}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_VRF_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000031 00000000`00000000 fffff880`009eb180 00000000`00000001
BiosVersion = BLH6710H.86A.0076.2010.1115.1959
BiosReleaseDate = 11/15/2010
SystemManufacturer =                                 
SystemProductName =                                 
MaxSpeed:     3100
CurrentSpeed: 3093
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\070212-17394-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Mon Jul  2 20:19:23.316 2012 (UTC - 4:00)
System Uptime: 0 days 10:09:34.526
BugCheck 101, {31, 0, fffff880009eb180, 1}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_VRF_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000031 00000000`00000000 fffff880`009eb180 00000000`00000001
BiosVersion = BLH6710H.86A.0076.2010.1115.1959
BiosReleaseDate = 11/15/2010
SystemManufacturer =                                 
SystemProductName =                                 
MaxSpeed:     3100
CurrentSpeed: 3093
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


	    
             
       [color=#000033]J. C. Griffith, Microsoft MVP (jcgriff2)[/color]   
             
           [url=https://mvp.support.microsoft.com/profile/Griffith][color=#000055][u]https://mvp.support.microsoft.com/profile/Griffith[/u][/color][/url]   

           [url=https://www.sysnative.com][color=#000033][u][url]www.sysnative.com[/url][/u][/color][/url]
             
           [url=http://jcgriff2.com][color=#000055][u][url]www.jcgriff2.com[/url][/u][/color][/url] 


¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨


  
[/font]
 
Thank you for the quick reply.

Both machines are custom builds with identical hardware. Originally they were built with DH67BL motherboards that had the defective 6 Series Intel chips and months later were swapped out. The OS load was not from an image but individually done on each machine. The only other components in the system are 2 sticks of Kingston or Crucial RAM, a WD or Seagate SATA HDD and a SATA DVDRW. I was afraid we were still looking at some hardware issue and question if the replacement (new mind you) motherboards may have some other issue even though we never experienced failure from the originals as we weren't using the last SATA channel. I think I'll get replacement CPU's and motherboards for both faulting machines.

Would an inline upgrade/repair install be in order based on the logs showing no driver issues? Could there still be OS corruption or the dumps being recorded possibly show that the OS is working perfectly and we should blame the hardware completely at this point?

-Adam


jcgriff2 said:
Hi -

There were 27 BSODs - going back to March 2011.
25 - 0x101 = CPU hang
2 - 0x119 = Video related; Intel video named (both were March 2011)

Some of the dumps were VERIFIER_ENABLED, yet no 3rd party driver was named. This points to hardware failure.

You mentioned other systems with similar BSODs?
Are they all the same hardware manufacturer?
Was the same image of Wiindows 7 installed on all?

Regards. . .

jcgriff2


`


BSOD SUMMARY

Code: 
[FONT=lucida console]
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\020312-11575-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Fri Feb  3 15:31:30.840 2012 (UTC - 4:00)
System Uptime: 8 days 0:43:05.395
BugCheck 101, {31, 0, fffff880009ea180, 1}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  PresentationFo
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000031 00000000`00000000 fffff880`009ea180 00000000`00000001
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\030212-13915-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Fri Mar  2 10:55:30.548 2012 (UTC - 4:00)
System Uptime: 8 days 23:41:16.414
BugCheck 101, {31, 0, fffff88002f64180, 2}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000031 00000000`00000000 fffff880`02f64180 00000000`00000002
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\030512-16660-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Mon Mar  5 15:56:54.792 2012 (UTC - 4:00)
System Uptime: 3 days 5:00:22.801
BugCheck 101, {31, 0, fffff88002f64180, 2}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000031 00000000`00000000 fffff880`02f64180 00000000`00000002
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\030812-11154-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Thu Mar  8 16:10:51.133 2012 (UTC - 4:00)
System Uptime: 3 days 0:07:20.105
BugCheck 101, {31, 0, fffff880009ea180, 1}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  QBW32.EXE
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000031 00000000`00000000 fffff880`009ea180 00000000`00000001
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\031212-13462-01.dmp]
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Debug session time: Sat Mar 10 15:12:02.862 2012 (UTC - 4:00)
System Uptime: 1 days 23:00:50.750
BugCheck 101, {31, 0, fffff880009ea180, 1}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  PresentationFo
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000031 00000000`00000000 fffff880`009ea180 00000000`00000001
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\041112-11060-01.dmp]
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Debug session time: Wed Apr 11 16:41:44.415 2012 (UTC - 4:00)
System Uptime: 9 days 7:36:37.766
BugCheck 101, {31, 0, fffff880009eb180, 1}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000031 00000000`00000000 fffff880`009eb180 00000000`00000001
BiosVersion = BLH6710H.86A.0076.2010.1115.1959
BiosReleaseDate = 11/15/2010
SystemManufacturer =                                 
SystemProductName =                                 
MaxSpeed:     3100
CurrentSpeed: 3093
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\043012-10639-01.dmp]
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Debug session time: Mon Apr 30 10:21:05.662 2012 (UTC - 4:00)
System Uptime: 3 days 22:36:52.744
BugCheck 101, {31, 0, fffff88003165180, 2}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  QBW32.EXE
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000031 00000000`00000000 fffff880`03165180 00000000`00000002
BiosVersion = BLH6710H.86A.0076.2010.1115.1959
BiosReleaseDate = 11/15/2010
SystemManufacturer =                                 
SystemProductName =                                 
MaxSpeed:     3100
CurrentSpeed: 3093
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\050112-14804-01.dmp]
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Debug session time: Tue May  1 10:52:20.938 2012 (UTC - 4:00)
System Uptime: 1 days 0:27:15.022
BugCheck 101, {31, 0, fffff88003165180, 2}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  QBW32.EXE
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000031 00000000`00000000 fffff880`03165180 00000000`00000002
BiosVersion = BLH6710H.86A.0076.2010.1115.1959
BiosReleaseDate = 11/15/2010
SystemManufacturer =                                 
SystemProductName =                                 
MaxSpeed:     3100
CurrentSpeed: 3093
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\050212-16660-01.dmp]
Built by: 7601.17790.amd64fre.win7sp1_gdr.120305-1505
Debug session time: Wed May  2 09:46:18.604 2012 (UTC - 4:00)
System Uptime: 0 days 22:50:38.533
BugCheck 101, {31, 0, fffff880031d7180, 3}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  EXCEL.EXE
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000031 00000000`00000000 fffff880`031d7180 00000000`00000003
BiosVersion = BLH6710H.86A.0076.2010.1115.1959
BiosReleaseDate = 11/15/2010
SystemManufacturer =                                 
SystemProductName =                                 
MaxSpeed:     3100
CurrentSpeed: 3093
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\051412-17253-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Mon May 14 15:46:10.210 2012 (UTC - 4:00)
System Uptime: 2 days 12:35:18.385
BugCheck 101, {31, 0, fffff88003165180, 2}
*** WARNING: Unable to verify checksum for win32k.sys
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000031 00000000`00000000 fffff880`03165180 00000000`00000002
BiosVersion = BLH6710H.86A.0076.2010.1115.1959
BiosReleaseDate = 11/15/2010
SystemManufacturer =                                 
SystemProductName =                                 
MaxSpeed:     3100
CurrentSpeed: 3093
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\051712-15397-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Thu May 17 11:14:07.777 2012 (UTC - 4:00)
System Uptime: 0 days 1:58:31.942
BugCheck 101, {31, 0, fffff880009eb180, 1}
*** WARNING: Unable to verify checksum for win32k.sys
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000031 00000000`00000000 fffff880`009eb180 00000000`00000001
BiosVersion = BLH6710H.86A.0076.2010.1115.1959
BiosReleaseDate = 11/15/2010
SystemManufacturer =                                 
SystemProductName =                                 
MaxSpeed:     3100
CurrentSpeed: 3093
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\060812-18267-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Fri Jun  8 11:52:41.814 2012 (UTC - 4:00)
System Uptime: 2 days 0:14:20.594
BugCheck 101, {31, 0, fffff88003165180, 2}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  QBW32.EXE
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000031 00000000`00000000 fffff880`03165180 00000000`00000002
BiosVersion = BLH6710H.86A.0076.2010.1115.1959
BiosReleaseDate = 11/15/2010
SystemManufacturer =                                 
SystemProductName =                                 
MaxSpeed:     3100
CurrentSpeed: 3093
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\061212-11840-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Tue Jun 12 13:46:34.214 2012 (UTC - 4:00)
System Uptime: 1 days 4:39:53.933
BugCheck 101, {31, 0, fffff880009eb180, 1}
*** WARNING: Unable to verify checksum for win32k.sys
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000031 00000000`00000000 fffff880`009eb180 00000000`00000001
BiosVersion = BLH6710H.86A.0076.2010.1115.1959
BiosReleaseDate = 11/15/2010
SystemManufacturer =                                 
SystemProductName =                                 
MaxSpeed:     3100
CurrentSpeed: 3093
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\062012-15038-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Wed Jun 20 09:19:04.976 2012 (UTC - 4:00)
System Uptime: 6 days 6:09:53.304
BugCheck 101, {31, 0, fffff88003165180, 2}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000031 00000000`00000000 fffff880`03165180 00000000`00000002
BiosVersion = BLH6710H.86A.0076.2010.1115.1959
BiosReleaseDate = 11/15/2010
SystemManufacturer =                                 
SystemProductName =                                 
MaxSpeed:     3100
CurrentSpeed: 3093
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\062612-12885-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Tue Jun 26 16:07:49.503 2012 (UTC - 4:00)
System Uptime: 4 days 7:32:46.545
BugCheck 101, {31, 0, fffff880009eb180, 1}
*** WARNING: Unable to verify checksum for win32k.sys
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000031 00000000`00000000 fffff880`009eb180 00000000`00000001
BiosVersion = BLH6710H.86A.0076.2010.1115.1959
BiosReleaseDate = 11/15/2010
SystemManufacturer =                                 
SystemProductName =                                 
MaxSpeed:     3100
CurrentSpeed: 3093
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\062912-14882-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Fri Jun 29 10:18:39.538 2012 (UTC - 4:00)
System Uptime: 2 days 17:44:51.142
BugCheck 101, {31, 0, fffff880031d7180, 3}
*** WARNING: Unable to verify checksum for win32k.sys
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000031 00000000`00000000 fffff880`031d7180 00000000`00000003
BiosVersion = BLH6710H.86A.0076.2010.1115.1959
BiosReleaseDate = 11/15/2010
SystemManufacturer =                                 
SystemProductName =                                 
MaxSpeed:     3100
CurrentSpeed: 3093
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\070212-10732-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Mon Jul  2 10:08:53.566 2012 (UTC - 4:00)
System Uptime: 1 days 12:50:26.584
BugCheck 101, {31, 0, fffff880009eb180, 1}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_VRF_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000031 00000000`00000000 fffff880`009eb180 00000000`00000001
BiosVersion = BLH6710H.86A.0076.2010.1115.1959
BiosReleaseDate = 11/15/2010
SystemManufacturer =                                 
SystemProductName =                                 
MaxSpeed:     3100
CurrentSpeed: 3093
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\070212-17394-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Mon Jul  2 20:19:23.316 2012 (UTC - 4:00)
System Uptime: 0 days 10:09:34.526
BugCheck 101, {31, 0, fffff880009eb180, 1}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
DEFAULT_BUCKET_ID:  VERIFIER_ENABLED_VISTA_MINIDUMP
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_4_PROC_VRF_ANALYSIS_INCONCLUSIVE
Bugcheck code 00000101
Arguments 00000000`00000031 00000000`00000000 fffff880`009eb180 00000000`00000001
BiosVersion = BLH6710H.86A.0076.2010.1115.1959
BiosReleaseDate = 11/15/2010
SystemManufacturer =                                 
SystemProductName =                                 
MaxSpeed:     3100
CurrentSpeed: 3093
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``


        
             
       [COLOR=#000033]J. C. Griffith, Microsoft MVP (jcgriff2)[/COLOR]   
             
           [URL="https://mvp.support.microsoft.com/profile/Griffith"][COLOR=#000055][U]https://mvp.support.microsoft.com/profile/Griffith[/U][/COLOR][/URL]   

           [URL="https://www.sysnative.com"][COLOR=#000033][/COLOR][/URL][COLOR=#000033][U][URL="https://www.sysnative.com"]www.sysnative.com[/URL][/U][/COLOR]
             
           [URL="http://jcgriff2.com"][COLOR=#000055][/COLOR][/URL][COLOR=#000055][U][URL="http://www.jcgriff2.com"]www.jcgriff2.com[/URL][/U][/COLOR] 


¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨


  
[/FONT]
Click to expand...
 
Well first of all a lot of your drivers, especially motherboard-related, look pretty old. If you wish, you can start going through installing new updated firmware, BIOS, and drivers for all your components. Uninstall any and all motherboard software if you have installed it - they are gimmicky and very buggy. This includes temp monitor software, "optimizing" software, OCing software, etc. Basically anything not called a driver (this does not include USB drivers).

I personally can't find anything aside from the usual stack trashing for some of the crashes that aren't 0x101. It appears your graphics driver kinda disappeared off the face of the earth spontaneously. This is primarily caused by failing memory, followed by bad mobo or PSU (the fact you're using stock PSU with cases is cause for concern).

Analysts:

Crashdump 031811-15069-01.dmp:

Code: 
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_SCHEDULER_INTERNAL_ERROR (119)
The video scheduler has detected that fatal violation has occurred. This resulted
in a condition that video scheduler can no longer progress. Any other values after
parameter 1 must be individually examined according to the subtype.
Arguments:
Arg1: 0000000000000001, The driver has reported an invalid fence ID.
Arg2: 000000000000adf6
Arg3: 000000000000adfe
Arg4: 000000000000adfe

Debugging Details:
------------------

TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x119

PROCESS_NAME:  System

CURRENT_IRQL:  7

LAST_CONTROL_TRANSFER:  from fffff88002ded22f to fffff80002cc0740

STACK_TEXT:  
fffff800`00b9c768 fffff880`02ded22f : 00000000`00000119 00000000`00000001 00000000`0000adf6 00000000`0000adfe : nt!KeBugCheckEx
fffff800`00b9c770 fffff880`0437feb9 : fffffa80`0664de18 00000000`0000adf6 00000000`00000000 00000000`0000adfe : watchdog!WdLogEvent5+0x11b
fffff800`00b9c7c0 fffff880`043801c3 : fffffa80`072c1000 fffff800`00b9c8d0 fffff880`000011ac fffff800`00b9caec : dxgmms1!VidSchiVerifyDriverReportedFenceId+0xad
fffff800`00b9c7f0 fffff880`0437ff76 : fffff800`00208080 ffffef37`00000004 fffffa80`072c1000 fffff800`00b9cb5c : dxgmms1!VidSchDdiNotifyInterruptWorker+0x23b
fffff800`00b9c840 fffff880`0428713f : fffffa80`0671d480 fffff800`02cc4871 fffffa80`06719000 00000000`00000000 : dxgmms1!VidSchDdiNotifyInterrupt+0x9e
fffff800`00b9c870 fffff880`049a4311 : fffff880`01e44008 fffff800`02e3ae80 fffff800`00b9cc30 fffff880`01e44000 : dxgkrnl!DxgNotifyInterruptCB+0x83
fffff800`00b9c8a0 fffff880`01e44008 : fffff800`02e3ae80 fffff800`00b9cc30 fffff880`01e44000 fffffa80`0701d000 : igdkmd64+0x168311
fffff800`00b9c8a8 fffff800`02e3ae80 : fffff800`00b9cc30 fffff880`01e44000 fffffa80`0701d000 fffff880`00bb4000 : 0xfffff880`01e44008
fffff800`00b9c8b0 fffff800`00b9cc30 : fffff880`01e44000 fffffa80`0701d000 fffff880`00bb4000 fffff880`00000002 : nt!KiInitialPCR+0x180
fffff800`00b9c8b8 fffff880`01e44000 : fffffa80`0701d000 fffff880`00bb4000 fffff880`00000002 0015a350`0000adf6 : 0xfffff800`00b9cc30
fffff800`00b9c8c0 fffffa80`0701d000 : fffff880`00bb4000 fffff880`00000002 0015a350`0000adf6 00000000`00000000 : 0xfffff880`01e44000
fffff800`00b9c8c8 fffff880`00bb4000 : fffff880`00000002 0015a350`0000adf6 00000000`00000000 00000000`00000000 : 0xfffffa80`0701d000
fffff800`00b9c8d0 fffff880`00000002 : 0015a350`0000adf6 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff880`00bb4000
fffff800`00b9c8d8 0015a350`0000adf6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff880`00000002
fffff800`00b9c8e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x15a350`0000adf6


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VidSchiVerifyDriverReportedFenceId+ad
fffff880`0437feb9 c744244053eeffff mov     dword ptr [rsp+40h],0FFFFEE53h

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  dxgmms1!VidSchiVerifyDriverReportedFenceId+ad

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d3fa174

FAILURE_BUCKET_ID:  X64_0x119_dxgmms1!VidSchiVerifyDriverReportedFenceId+ad

BUCKET_ID:  X64_0x119_dxgmms1!VidSchiVerifyDriverReportedFenceId+ad

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

0: kd> !thread
GetPointerFromAddress: unable to read from fffff80002ef8000
THREAD fffff80002e48c40  Cid 0000.0000  Teb: 0000000000000000 Win32Thread: 0000000000000000 RUNNING on processor 0
Not impersonating
GetUlongFromAddress: unable to read from fffff80002e36ba4
Owning Process            fffff80002e49140       Image:         <Unknown>
Attached Process          fffffa80036c6040       Image:         System
fffff78000000000: Unable to get shared data
Wait Start TickCount      51566489     
Context Switch Count      62841629       IdealProcessor: 0             
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime                  00:00:00.000
KernelTime                00:00:00.000
Win32 Start Address nt!KiIdleLoop (0xfffff80002cc8e90)
Stack Init fffff80000b9cd70 Current fffff80000b9cd00
Base fffff80000b9d000 Limit fffff80000b97000 Call 0
Priority 16 BasePriority 0 UnusualBoost 0 ForegroundBoost 0 IoPriority 0 PagePriority 0
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff800`00b9c768 fffff880`02ded22f : 00000000`00000119 00000000`00000001 00000000`0000adf6 00000000`0000adfe : nt!KeBugCheckEx
fffff800`00b9c770 fffff880`0437feb9 : fffffa80`0664de18 00000000`0000adf6 00000000`00000000 00000000`0000adfe : watchdog!WdLogEvent5+0x11b
fffff800`00b9c7c0 fffff880`043801c3 : fffffa80`072c1000 fffff800`00b9c8d0 fffff880`000011ac fffff800`00b9caec : dxgmms1!VidSchiVerifyDriverReportedFenceId+0xad
fffff800`00b9c7f0 fffff880`0437ff76 : fffff800`00208080 ffffef37`00000004 fffffa80`072c1000 fffff800`00b9cb5c : dxgmms1!VidSchDdiNotifyInterruptWorker+0x23b
fffff800`00b9c840 fffff880`0428713f : fffffa80`0671d480 fffff800`02cc4871 fffffa80`06719000 00000000`00000000 : dxgmms1!VidSchDdiNotifyInterrupt+0x9e
fffff800`00b9c870 fffff880`049a4311 : fffff880`01e44008 fffff800`02e3ae80 fffff800`00b9cc30 fffff880`01e44000 : dxgkrnl!DxgNotifyInterruptCB+0x83
fffff800`00b9c8a0 fffff880`01e44008 : fffff800`02e3ae80 fffff800`00b9cc30 fffff880`01e44000 fffffa80`0701d000 : igdkmd64+0x168311
fffff800`00b9c8a8 fffff800`02e3ae80 : fffff800`00b9cc30 fffff880`01e44000 fffffa80`0701d000 fffff880`00bb4000 : 0xfffff880`01e44008
fffff800`00b9c8b0 fffff800`00b9cc30 : fffff880`01e44000 fffffa80`0701d000 fffff880`00bb4000 fffff880`00000002 : nt!KiInitialPCR+0x180
fffff800`00b9c8b8 fffff880`01e44000 : fffffa80`0701d000 fffff880`00bb4000 fffff880`00000002 0015a350`0000adf6 : 0xfffff800`00b9cc30
fffff800`00b9c8c0 fffffa80`0701d000 : fffff880`00bb4000 fffff880`00000002 0015a350`0000adf6 00000000`00000000 : 0xfffff880`01e44000
fffff800`00b9c8c8 fffff880`00bb4000 : fffff880`00000002 0015a350`0000adf6 00000000`00000000 00000000`00000000 : 0xfffffa80`0701d000
fffff800`00b9c8d0 fffff880`00000002 : 0015a350`0000adf6 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff880`00bb4000
fffff800`00b9c8d8 0015a350`0000adf6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff880`00000002
fffff800`00b9c8e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x15a350`0000adf6

While the bad fence id is what triggered the crash, there's something that appears to be of bigger consequence here, and that lies in the callstack. As you can tell, its trashed, which occurs right before igdkmd64 module (intel graphics) appears in the mix. Let's look into this by first disassembling from the return address in the frame above it:

Code: 
0: kd> u fffff880`049a4311
igdkmd64+0x168311:
fffff880`049a4311 ??              ???
                         ^ Memory access error in 'u fffff880`049a4311'

Something's not right here. This should've been preserved in the minidump. Let's see if it's actually a valid address and that the return address in itself isn't bad. We should start by seeing if this address even exists in the range of memory where the intel graphics module is stored:

Code: 
0: kd> lmvm igdkmd64
start             end                 module name
fffff880`0483c000 fffff880`053d4360   igdkmd64 T (no symbols)           
    Loaded symbol image file: igdkmd64.sys
    Image path: \SystemRoot\system32\DRIVERS\igdkmd64.sys
    Image name: igdkmd64.sys
    Timestamp:        Fri Oct 01 17:14:28 2010 (4CA64F34)
    CheckSum:         00B9D8E9
    ImageSize:        00B98360
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

As you can tell, the return address fffff880`049a4311 does in fact lie in the range. Let's look further by actually viewing the data starting at the beginning of the module:

Code: 
0: kd> uf igdkmd64
No code found, aborting
0: kd> dc igdkmd64
fffff880`0483c000  ???????? ???????? ???????? ????????  ????????????????
fffff880`0483c010  ???????? ???????? ???????? ????????  ????????????????
fffff880`0483c020  ???????? ???????? ???????? ????????  ????????????????
fffff880`0483c030  ???????? ???????? ???????? ????????  ????????????????
fffff880`0483c040  ???????? ???????? ???????? ????????  ????????????????
fffff880`0483c050  ???????? ???????? ???????? ????????  ????????????????
fffff880`0483c060  ???????? ???????? ???????? ????????  ????????????????
fffff880`0483c070  ???????? ???????? ???????? ????????  ????????????????

Ah ha. Either some fluke in the minidump generation caused this module's contents to not be retained in the minidump, or the module itself disappeared without a trace. I guess there's a chance it got unloaded by another processor core while this was going on, but unless there was a major issue that caused TDR to kick in and unload it, there's no other reason why the graphics driver would spontaneously unload itself (to my knowledge). I personally have to chalk this up as memory failure. I'm not 100% certain of it from what little and unreliable data minidumps gives us, but this is not expected behavior, even from a minidump.
 
Last edited:
Very useful information. I'm not terribly concerned with the stock PSU as I have roughly 250 of these systems built a year and while we do experience failures here and there, I'd say average replacement is about 5 a year and the power draw for this config is minimal, but I do hear where you're coming from.

The Video Driver issue is where I started a year ago when the Minidumps were pointing to the driver. Updating it, removing it, reinstalling it, etc. didn't seem to help. I believe the memory was swapped at the same time as the motherboard but I'm not going to rely on my own memory so I'll replace the modules before the motherboard and CPUs as it's a lot easier and then if either machine crashes again we'll go full boat, including PSU.

Thank you both for such detailed information, it is much appreciated.

-Adam

Vir Gnarus said:
Well first of all a lot of your drivers, especially motherboard-related, look pretty old. If you wish, you can start going through installing new updated firmware, BIOS, and drivers for all your components. Uninstall any and all motherboard software if you have installed it - they are gimmicky and very buggy. This includes temp monitor software, "optimizing" software, OCing software, etc. Basically anything not called a driver (this does not include USB drivers).

I personally can't find anything aside from the usual stack trashing for some of the crashes that aren't 0x101. It appears your graphics driver kinda disappeared off the face of the earth spontaneously. This is primarily caused by failing memory, followed by bad mobo or PSU (the fact you're using stock PSU with cases is cause for concern).

Analysts:

Crashdump 031811-15069-01.dmp:

Code: 
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_SCHEDULER_INTERNAL_ERROR (119)
The video scheduler has detected that fatal violation has occurred. This resulted
in a condition that video scheduler can no longer progress. Any other values after
parameter 1 must be individually examined according to the subtype.
Arguments:
Arg1: 0000000000000001, The driver has reported an invalid fence ID.
Arg2: 000000000000adf6
Arg3: 000000000000adfe
Arg4: 000000000000adfe

Debugging Details:
------------------

TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x119

PROCESS_NAME:  System

CURRENT_IRQL:  7

LAST_CONTROL_TRANSFER:  from fffff88002ded22f to fffff80002cc0740

STACK_TEXT:  
fffff800`00b9c768 fffff880`02ded22f : 00000000`00000119 00000000`00000001 00000000`0000adf6 00000000`0000adfe : nt!KeBugCheckEx
fffff800`00b9c770 fffff880`0437feb9 : fffffa80`0664de18 00000000`0000adf6 00000000`00000000 00000000`0000adfe : watchdog!WdLogEvent5+0x11b
fffff800`00b9c7c0 fffff880`043801c3 : fffffa80`072c1000 fffff800`00b9c8d0 fffff880`000011ac fffff800`00b9caec : dxgmms1!VidSchiVerifyDriverReportedFenceId+0xad
fffff800`00b9c7f0 fffff880`0437ff76 : fffff800`00208080 ffffef37`00000004 fffffa80`072c1000 fffff800`00b9cb5c : dxgmms1!VidSchDdiNotifyInterruptWorker+0x23b
fffff800`00b9c840 fffff880`0428713f : fffffa80`0671d480 fffff800`02cc4871 fffffa80`06719000 00000000`00000000 : dxgmms1!VidSchDdiNotifyInterrupt+0x9e
fffff800`00b9c870 fffff880`049a4311 : fffff880`01e44008 fffff800`02e3ae80 fffff800`00b9cc30 fffff880`01e44000 : dxgkrnl!DxgNotifyInterruptCB+0x83
fffff800`00b9c8a0 fffff880`01e44008 : fffff800`02e3ae80 fffff800`00b9cc30 fffff880`01e44000 fffffa80`0701d000 : igdkmd64+0x168311
fffff800`00b9c8a8 fffff800`02e3ae80 : fffff800`00b9cc30 fffff880`01e44000 fffffa80`0701d000 fffff880`00bb4000 : 0xfffff880`01e44008
fffff800`00b9c8b0 fffff800`00b9cc30 : fffff880`01e44000 fffffa80`0701d000 fffff880`00bb4000 fffff880`00000002 : nt!KiInitialPCR+0x180
fffff800`00b9c8b8 fffff880`01e44000 : fffffa80`0701d000 fffff880`00bb4000 fffff880`00000002 0015a350`0000adf6 : 0xfffff800`00b9cc30
fffff800`00b9c8c0 fffffa80`0701d000 : fffff880`00bb4000 fffff880`00000002 0015a350`0000adf6 00000000`00000000 : 0xfffff880`01e44000
fffff800`00b9c8c8 fffff880`00bb4000 : fffff880`00000002 0015a350`0000adf6 00000000`00000000 00000000`00000000 : 0xfffffa80`0701d000
fffff800`00b9c8d0 fffff880`00000002 : 0015a350`0000adf6 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff880`00bb4000
fffff800`00b9c8d8 0015a350`0000adf6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff880`00000002
fffff800`00b9c8e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x15a350`0000adf6


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VidSchiVerifyDriverReportedFenceId+ad
fffff880`0437feb9 c744244053eeffff mov     dword ptr [rsp+40h],0FFFFEE53h

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  dxgmms1!VidSchiVerifyDriverReportedFenceId+ad

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d3fa174

FAILURE_BUCKET_ID:  X64_0x119_dxgmms1!VidSchiVerifyDriverReportedFenceId+ad

BUCKET_ID:  X64_0x119_dxgmms1!VidSchiVerifyDriverReportedFenceId+ad

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

0: kd> !thread
GetPointerFromAddress: unable to read from fffff80002ef8000
THREAD fffff80002e48c40  Cid 0000.0000  Teb: 0000000000000000 Win32Thread: 0000000000000000 RUNNING on processor 0
Not impersonating
GetUlongFromAddress: unable to read from fffff80002e36ba4
Owning Process            fffff80002e49140       Image:         <Unknown>
Attached Process          fffffa80036c6040       Image:         System
fffff78000000000: Unable to get shared data
Wait Start TickCount      51566489     
Context Switch Count      62841629       IdealProcessor: 0             
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime                  00:00:00.000
KernelTime                00:00:00.000
Win32 Start Address nt!KiIdleLoop (0xfffff80002cc8e90)
Stack Init fffff80000b9cd70 Current fffff80000b9cd00
Base fffff80000b9d000 Limit fffff80000b97000 Call 0
Priority 16 BasePriority 0 UnusualBoost 0 ForegroundBoost 0 IoPriority 0 PagePriority 0
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff800`00b9c768 fffff880`02ded22f : 00000000`00000119 00000000`00000001 00000000`0000adf6 00000000`0000adfe : nt!KeBugCheckEx
fffff800`00b9c770 fffff880`0437feb9 : fffffa80`0664de18 00000000`0000adf6 00000000`00000000 00000000`0000adfe : watchdog!WdLogEvent5+0x11b
fffff800`00b9c7c0 fffff880`043801c3 : fffffa80`072c1000 fffff800`00b9c8d0 fffff880`000011ac fffff800`00b9caec : dxgmms1!VidSchiVerifyDriverReportedFenceId+0xad
fffff800`00b9c7f0 fffff880`0437ff76 : fffff800`00208080 ffffef37`00000004 fffffa80`072c1000 fffff800`00b9cb5c : dxgmms1!VidSchDdiNotifyInterruptWorker+0x23b
fffff800`00b9c840 fffff880`0428713f : fffffa80`0671d480 fffff800`02cc4871 fffffa80`06719000 00000000`00000000 : dxgmms1!VidSchDdiNotifyInterrupt+0x9e
fffff800`00b9c870 fffff880`049a4311 : fffff880`01e44008 fffff800`02e3ae80 fffff800`00b9cc30 fffff880`01e44000 : dxgkrnl!DxgNotifyInterruptCB+0x83
fffff800`00b9c8a0 fffff880`01e44008 : fffff800`02e3ae80 fffff800`00b9cc30 fffff880`01e44000 fffffa80`0701d000 : igdkmd64+0x168311
fffff800`00b9c8a8 fffff800`02e3ae80 : fffff800`00b9cc30 fffff880`01e44000 fffffa80`0701d000 fffff880`00bb4000 : 0xfffff880`01e44008
fffff800`00b9c8b0 fffff800`00b9cc30 : fffff880`01e44000 fffffa80`0701d000 fffff880`00bb4000 fffff880`00000002 : nt!KiInitialPCR+0x180
fffff800`00b9c8b8 fffff880`01e44000 : fffffa80`0701d000 fffff880`00bb4000 fffff880`00000002 0015a350`0000adf6 : 0xfffff800`00b9cc30
fffff800`00b9c8c0 fffffa80`0701d000 : fffff880`00bb4000 fffff880`00000002 0015a350`0000adf6 00000000`00000000 : 0xfffff880`01e44000
fffff800`00b9c8c8 fffff880`00bb4000 : fffff880`00000002 0015a350`0000adf6 00000000`00000000 00000000`00000000 : 0xfffffa80`0701d000
fffff800`00b9c8d0 fffff880`00000002 : 0015a350`0000adf6 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff880`00bb4000
fffff800`00b9c8d8 0015a350`0000adf6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff880`00000002
fffff800`00b9c8e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x15a350`0000adf6

While the bad fence id is what triggered the crash, there's something that appears to be of bigger consequence here, and that lies in the callstack. As you can tell, its trashed, which occurs right before igdkmd64 module (intel graphics) appears in the mix. Let's look into this by first disassembling from the return address in the frame above it:

Code: 
0: kd> u fffff880`049a4311
igdkmd64+0x168311:
fffff880`049a4311 ??              ???
                         ^ Memory access error in 'u fffff880`049a4311'

Something's not right here. This should've been preserved in the minidump. Let's see if it's actually a valid address and that the return address in itself isn't bad. We should start by seeing if this address even exists in the range of memory where the intel graphics module is stored:

Code: 
0: kd> lmvm igdkmd64
start             end                 module name
fffff880`0483c000 fffff880`053d4360   igdkmd64 T (no symbols)           
    Loaded symbol image file: igdkmd64.sys
    Image path: \SystemRoot\system32\DRIVERS\igdkmd64.sys
    Image name: igdkmd64.sys
    Timestamp:        Fri Oct 01 17:14:28 2010 (4CA64F34)
    CheckSum:         00B9D8E9
    ImageSize:        00B98360
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

As you can tell, the return address fffff880`049a4311 does in fact lie in the range. Let's look further by actually viewing the data starting at the beginning of the module:

Code: 
0: kd> uf igdkmd64
No code found, aborting
0: kd> dc igdkmd64
fffff880`0483c000  ???????? ???????? ???????? ????????  ????????????????
fffff880`0483c010  ???????? ???????? ???????? ????????  ????????????????
fffff880`0483c020  ???????? ???????? ???????? ????????  ????????????????
fffff880`0483c030  ???????? ???????? ???????? ????????  ????????????????
fffff880`0483c040  ???????? ???????? ???????? ????????  ????????????????
fffff880`0483c050  ???????? ???????? ???????? ????????  ????????????????
fffff880`0483c060  ???????? ???????? ???????? ????????  ????????????????
fffff880`0483c070  ???????? ???????? ???????? ????????  ????????????????

Ah ha. Either some fluke in the minidump generation caused this module's contents to not be retained in the minidump, or the module itself disappeared without a trace. I guess there's a chance it got unloaded by another processor core while this was going on, but unless there was a major issue that caused TDR to kick in and unload it, there's no other reason why the graphics driver would spontaneously unload itself (to my knowledge). I personally have to chalk this up as memory failure. I'm not 100% certain of it from what little and unreliable data minidumps gives us, but this is not expected behavior, even from a minidump.
Click to expand...
 
I cross-checked with other modules in the minidump and I'll have to lower my suspicions a bit. It is not assured that in a minidump the data I was looking for was going to be retained. However, given that it's a module that was in the callstack that faulted, it should be present more than other modules that are unrelated.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top