1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 00000000, A single DPC or ISR exceeded its time allotment. The offending
component can usually be identified with a stack trace.
Arg2: 00000501, The DPC time count (in ticks).
Arg3: 00000500, The DPC time allotment (in ticks).
Arg4: 00000000
Debugging Details:
------------------
DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x133
PROCESS_NAME: System
CURRENT_IRQL: 1c
ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
DPC_STACK_BASE: FFFFFFFF801E2000
LAST_CONTROL_TRANSFER: from 813add5e to 813641a4
STACK_TEXT:
801e1ab0 813add5e 00000133 00000000 00000501 nt!KeBugCheckEx
801e1b1c 81317c7d 00147ff6 00000002 00000000 nt! ?? ::FNODOBFM::`string'+0x301dc
801e1bcc 8120c2be 8121bdef 81209c02 000000d2 nt!KeClockInterruptNotify+0x7d
801e1bd0 8121bdef 81209c02 000000d2 8382eb9c hal!HalpTimerClockIpiRoutineCommon+0x6
801e1bd0 812ffa9d 81209c02 000000d2 8382eb9c hal!HalpTimerClockIpiRoutine+0x1cb
801e1d24 81296eab 8a8c01d8 0000000c 8a8c02b4 nt!KiInsertTimerTable+0x29d
801e1d48 81a4570d 008c01b0 ffffffff ffffffff nt!KeSetTimer+0x5b
801e1d60 81a45a18 8b7000e8 8f9ce858 00000000 ndis!ndisQueuePeriodicReceivesTimer+0x51
801e1d9c 81a3d3c2 00000000 00000000 00000001 ndis!ndisQueueDpcWorkItem+0x146
801e1e18 812afa96 8f9ce9d4 8f9ce858 00000000 ndis!ndisInterruptDpc+0x240
801e1ed0 812af693 801e1f18 00000000 8a8c02bc nt!KiExecuteAllDpcs+0x216
801e1ff4 813794ae 8a1c7d08 00000000 00000000 nt!KiRetireDpcList+0xf3
801e1ff8 8a1c7d08 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2e
WARNING: Frame IP not in any known module. Following frames may be wrong.
813794ae 00000000 00000023 011b850f bb830000 0x8a1c7d08
STACK_COMMAND: kb
FOLLOWUP_IP:
ndis!ndisQueuePeriodicReceivesTimer+51
81a4570d 5e pop esi
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: ndis!ndisQueuePeriodicReceivesTimer+51
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: ndis
IMAGE_NAME: ndis.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 53904c46
IMAGE_VERSION: 6.3.9600.17199
BUCKET_ID_FUNC_OFFSET: 51
FAILURE_BUCKET_ID: 0x133_DPC_ndis!ndisQueuePeriodicReceivesTimer
BUCKET_ID: 0x133_DPC_ndis!ndisQueuePeriodicReceivesTimer
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x133_dpc_ndis!ndisqueueperiodicreceivestimer
FAILURE_ID_HASH: {ecb20391-c476-9ab0-cad9-35a4b4cb253c}
Followup: MachineOwner
---------
1: kd> !dpcs
CPU Type KDPC Function
Failed to read DPC at 0x8a9dfdf4
1: kd> !timer
ffdf0000: Unable to get shared data
1: kd> !analyze -hang
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 133, {0, 501, 500, 0}
Scanning for threads blocked on locks ...
8144f138: Unable to get value of ExpSystemResourcesList
Probably caused by : ndis.sys ( ndis!ndisQueuePeriodicReceivesTimer+51 )
Followup: MachineOwner
---------