Arg3 is the PRCB of the processor that is stuck. Try doing a !running -ti
and see if you get a call stack for that processor.
-scott
OSR
@OSRDrivers
wrote in message news:xxxxx@ntdev…
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: 0000000000000009, Clock interrupt time out interval in nominal clock
ticks.
Arg2: 0000000000000000, 0.
Arg3: fffff880009b9180, The PRCB address of the hung processor.
Arg4: 0000000000000001, 0.
Debugging Details:
BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_16_PROC
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP
PROCESS_NAME: System
CURRENT_IRQL: d
STACK_TEXT:
fffff880009a9628 fffff800
0172c7fa : 0000000000000101 00000000
00000009
0000000000000000 fffff880
009b9180 : nt!KeBugCheckEx
fffff880009a9630 fffff800
016df077 : 0000000000000000 fffff800
00000001
000000000001312d 00000000
0000000c : nt! ?? ::FNODOBFM::string'+0x4e1e fffff880
009a96c0 fffff8000162b1c0 : 00000000
00000000 fffff880009a9870 fffff800
016473c0 fffff80000000000 : nt!KeUpdateSystemTime+0x377 fffff880
009a97c0 fffff800016d0e13 : 00000000
0655e3a8 fffff800016473c0 00000000
00000000 fffff800016f4474 : hal!HalpRtcClockInterrupt+0x130 fffff880
009a97f0 fffff8000170ae63 : fffff800
01853e80 0000000000000001 00000000
00000000 0000000000000000 : nt!KiInterruptDispatchNoLock+0x163 fffff880
009a9980 fffff800016da39c : 00000000
00000000 fffff880009a9ab8 00000000
00000000 0000000000000000 : nt!KxFlushEntireTb+0x93 fffff880
009a99c0 fffff800016975d9 : 00000000
0000003f 000000000000003f fffffa80
22eac7d0 0000000000000040 : nt!KeFlushMultipleRangeTb+0x28c fffff880
009a9a90 fffff80001697e27 : 00000000
00ba3900 000000000000003f 00000000
00000000 0000000000000000 : nt!MiZeroPageChain+0x14e fffff880
009a9ad0 fffff8000196e456 : fffffa80
3b2dfb50 0000000000000080 fffffa80
3b2df040 cf8b4838558d48f8 : nt!MmZeroPageThread+0x83a fffff880
009a9c00 fffff800016c62c6 : fffff800
01853e80 fffffa803b2dfb50 fffff800
01861cc0 9090909090909090 : nt!PspSystemThreadStartup+0x5a fffff880
009a9c40 0000000000000000 : 00000000
00000000 0000000000000000 00000000
00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
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_16_PROC_ANALYSIS_INCONCLUSIVE
BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_16_PROC_ANALYSIS_INCONCLUSIVE
Followup: MachineOwner
0: kd> .lastevent
Last event: Break instruction exception - code 80000003 (first/second chance
not available)
debugger time: Wed Feb 22 19:13:39.017 2017 (UTC + 8:00)
0: kd> !error
Error code: (NTSTATUS) 0 (0) - STATUS_WAIT_0