I had this nice little BSOD while playing warhammer online this morning.
I am running an overclock on my I-7 it has been rock solid stable for 6 months though.
Is there any chance this could not be processor related?
Use !analyze -v to get detailed debugging information.
BugCheck 101, {19, 0, fffffa60018b5180, 5}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffffa60018b5180, The PRCB address of the hung processor.
Arg4: 0000000000000005, 0.
Debugging Details:
------------------
BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_8_PROC
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: svchost.exe
CURRENT_IRQL: d
STACK_TEXT:
fffffa60`066486d8 fffff800`024f62e1 : 00000000`00000101 00000000`00000019 00000000`00000000 fffffa60`018b5180 : nt!KeBugCheckEx
fffffa60`066486e0 fffff800`024a021a : fffff800`024393c0 fffffa60`06648800 fffffa60`06648850 fffff800`024393c0 : nt! ?? ::FNODOBFM::`string'+0x34b4
fffffa60`06648720 fffff800`02416d74 : 00000000`00000000 000000e8`5dabe5c6 00000000`00000000 000000e8`5dac1db3 : nt!KeUpdateSystemTime+0xea
fffffa60`06648750 fffff800`024a7e6d : 00000000`331c601c fffff800`025c6680 fffffa80`05ded010 fffffa80`09f7f2a0 : hal!HalpHpetClockInterrupt+0x8c
fffffa60`06648780 fffff800`02475ee5 : fffff800`00000000 fffffa60`06648930 00000000`00000000 00000000`00000008 : nt!KiInterruptDispatchNoLock+0x14d
fffffa60`06648910 fffff800`0271db3f : 00000000`00000000 fffffa60`06648ca0 00000000`00000000 fffffa60`06648a20 : nt!KeFlushProcessWriteBuffers+0xc9
fffffa60`06648960 fffff800`024a6173 : fffffa80`09f7f2a0 00000000`00013880 ffffffff`fffe7960 00000000`00000000 : nt!NtQuerySystemInformation+0x117f
fffffa60`06648c20 00000000`77765dda : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0133eff8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77765dda
STACK_COMMAND: kb
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
Followup: MachineOwner
---------
I am running an overclock on my I-7 it has been rock solid stable for 6 months though.
Is there any chance this could not be processor related?
Use !analyze -v to get detailed debugging information.
BugCheck 101, {19, 0, fffffa60018b5180, 5}
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000019, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: fffffa60018b5180, The PRCB address of the hung processor.
Arg4: 0000000000000005, 0.
Debugging Details:
------------------
BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_8_PROC
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: svchost.exe
CURRENT_IRQL: d
STACK_TEXT:
fffffa60`066486d8 fffff800`024f62e1 : 00000000`00000101 00000000`00000019 00000000`00000000 fffffa60`018b5180 : nt!KeBugCheckEx
fffffa60`066486e0 fffff800`024a021a : fffff800`024393c0 fffffa60`06648800 fffffa60`06648850 fffff800`024393c0 : nt! ?? ::FNODOBFM::`string'+0x34b4
fffffa60`06648720 fffff800`02416d74 : 00000000`00000000 000000e8`5dabe5c6 00000000`00000000 000000e8`5dac1db3 : nt!KeUpdateSystemTime+0xea
fffffa60`06648750 fffff800`024a7e6d : 00000000`331c601c fffff800`025c6680 fffffa80`05ded010 fffffa80`09f7f2a0 : hal!HalpHpetClockInterrupt+0x8c
fffffa60`06648780 fffff800`02475ee5 : fffff800`00000000 fffffa60`06648930 00000000`00000000 00000000`00000008 : nt!KiInterruptDispatchNoLock+0x14d
fffffa60`06648910 fffff800`0271db3f : 00000000`00000000 fffffa60`06648ca0 00000000`00000000 fffffa60`06648a20 : nt!KeFlushProcessWriteBuffers+0xc9
fffffa60`06648960 fffff800`024a6173 : fffffa80`09f7f2a0 00000000`00013880 ffffffff`fffe7960 00000000`00000000 : nt!NtQuerySystemInformation+0x117f
fffffa60`06648c20 00000000`77765dda : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0133eff8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x77765dda
STACK_COMMAND: kb
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
Followup: MachineOwner
---------