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.
[COLOR="#FF0000"]Arg3: fffff88002fe6180, The PRCB address of the hung processor.[/COLOR]
[COLOR="#008000"]Mit diesem Parameter hofft man, an die IRP-Liste zu kommen, da ein
IRP-Aufruf die CPU blockiert.[/COLOR]
Arg4: 0000000000000004, 0.
....
FAILURE_BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
BUCKET_ID: X64_CLOCK_WATCHDOG_TIMEOUT_8_PROC_ANALYSIS_INCONCLUSIVE
[COLOR="#008000"]Hier kommt schon der erste Dämpfer: [B]die Analyse ist nicht schlüssig[/B][/COLOR]
....
[COLOR="#008000"]Den aktuellen Thread abrufen[/COLOR]
0: kd> !thread
GetPointerFromAddress: unable to read from fffff800034ce000
[COLOR="#FF0000"]THREAD fffffa801373c5d0[/COLOR] Cid 0684.08f0 Teb: 000007fffffd7000 Win32Thread: fffff900c1effc30 [COLOR="#FF0000"]RUNNING on processor 0[/COLOR]
[COLOR="#008000"]Der aktuelle Thread läuft aus CPU(Kern) 0, also der ersten CPU.
Im Thread-Vorspann fehlt leider die IRP-Liste, wodurch nicht feststellbar ist, welcher IRP die CPU blockiert [/COLOR]
Not impersonating
GetUlongFromAddress: unable to read from fffff8000340dba4
[COLOR="#FF0000"]Owning Process fffffa80135d3b30 Image: dwm.exe[/COLOR]
[COLOR="#008000"]Der besitzende Prozess ist dwm.exe[/COLOR]
Attached Process N/A Image: N/A
fffff78000000000: Unable to get shared data
Wait Start TickCount 1031570
Context Switch Count 1209422 IdealProcessor: 4 LargeStack
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime 00:00:00.000
KernelTime 00:00:00.000
Win32 Start Address 0x000007fef674f0d8
Stack Init fffff8800ada0c70 Current fffff8800ada0220
Base fffff8800ada1000 Limit fffff8800ad99000 Call 0
Priority 15 BasePriority 15 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5
Child-SP RetAddr : Args to Child : Call Site
fffff880`0ada0298 fffff800`032f68f9 : 00000000`00000101 00000000`00000019 00000000`00000000 fffff880`02fe6180 : nt!KeBugCheckEx
fffff880`0ada02a0 fffff800`032a94b7 : 00000000`00000000 fffff800`00000004 00000000`00002710 00000000`00000800 : nt! ?? ::FNODOBFM::`string'+0x4e2e
fffff880`0ada0330 fffff800`03812895 : fffff800`03838460 fffff880`0ada04e0 fffff800`03838460 00000580`00000000 : nt!KeUpdateSystemTime+0x377
fffff880`0ada0430 fffff800`0329b233 : 00000000`0cce52a8 fffffa80`08da6ad0 fffffa80`08da6ad0 00000000`002f378f : hal!HalpHpetClockInterrupt+0x8d
fffff880`0ada0460 fffff800`032d53bf : 00000000`00000001 fffff8a0`107ec000 00000000`00000101 00000000`00000000 : nt!KiInterruptDispatchNoLock+0x163 (TrapFrame @ fffff880`0ada0460)
fffff880`0ada05f0 fffff800`032d42ed : 00000000`00000000 00000000`00000001 80000002`c898e867 00000000`00000040 : nt!KxFlushEntireTb+0xc7
fffff880`0ada0630 fffff800`032f8850 : 00000000`00000001 fffff8a0`107ea210 00000000`00000001 00000002`c898e000 : nt!KeFlushTb+0x119
fffff880`0ada06b0 fffff800`032af54f : fffff8a0`107ea210 fffff880`0ada0740 fffffa80`135d3ec8 fffffa80`135d3ec8 : nt! ?? ::FNODOBFM::`string'+0xae02
fffff880`0ada06f0 fffff800`032bd8c5 : 00000000`00000001 00000000`0e3d9000 fffff880`0ada0ae0 fffff8a0`107ea210 : nt!MiResolveDemandZeroFault+0x1ff
[COLOR="#FF0000"]fffff880`0ada07e0 fffff800`032bc0b3 : 00000000`00000080 00000000`0e3d9000 fffff680`00071ec8 fffffa80`135d3ec8 : nt!MiResolveProtoPteFault+0x4f5[/COLOR]
[COLOR="#008000"]Das Auflösen eines PTE (PageTableEntry) schlägt fehl. Die Fehlerbehandlung
wird in Gang gesetzt.[/COLOR]
fffff880`0ada0870 fffff800`032abf69 : 00000000`00000000 00000000`0e3d9000 00000000`01bc0b08 fffff880`00000000 : nt!MiDispatchFault+0x1c3
fffff880`0ada0980 fffff800`0329ce2e : 00000000`00000001 00000000`0e3d9000 00000000`003bb901 00000000`049986f8 : nt!MmAccessFault+0x359
fffff880`0ada0ae0 000007fe`f675cf67 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x16e (TrapFrame @ fffff880`0ada0ae0)
00000000`01e4f268 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`f675cf67
....
0: kd> !prcb 0
[COLOR="#008000"]Nur zur Sicherheit noch mal den Prozessor Control Block (PRCB) abgefragt.
Aber auch das bringt kein Licht ins Dunkel.[/COLOR]
PRCB for Processor 0 at fffff780ffff0000:
Current IRQL -- 13
Threads-- Current fffffa801373c5d0 Next fffffa801476e390 Idle fffff8000341fcc0
Processor Index 0 Number (0, 0) GroupSetMember 1
Interrupt Count -- 07af4dad
Times -- Dpc 0001bacd Interrupt 00004c17
Kernel 000a79fa User 00054545