******************************************************************************** *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 133, {0, 283, 282, 0}
*** WARNING: Unable to verify timestamp for nvstor.sys
*** ERROR: Module load completed but symbols could not be loaded for nvstor.sys
Probably caused by : nvstor.sys ( nvstor+f676 )
Followup: MachineOwner
---------
0: 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: 00000283, The DPC time count (in ticks).
Arg3: 00000282, 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
TAG_NOT_DEFINED_c000000f: FFFFFFFF80C38000
LAST_CONTROL_TRANSFER: from 80f3419d to 80ea9088
STACK_TEXT:
80c347ac 80f3419d 00000133 00000000 00000283 nt!KeBugCheckEx
80c34818 80e3ad24 0039ea6a 0039ea6b 00227702 nt! ?? ::FNODOBFM::`string'+0xead3
80c34884 813bbffe 80c3489c 813b746a ffd01000 nt!KeUpdateTime+0x1d8
80c348a4 813cd60d 80e3ad02 000000d1 80c3497c hal!HalpTimerClockInterruptCommon+0x66
80c348a4 813b746a 80e3ad02 000000d1 80c3497c hal!HalpTimerClockInterrupt+0x199
80c3497c 813b64d4 0000000a 00000000 00000001 hal!HalpTimerStallExecutionProcessor+0x158
80c349c4 816a9676 80c349e0 8169f70e 00000001 hal!KeStallExecutionProcessor+0x14e
WARNING: Stack unwind information not available. Following frames may be wrong.
80c349e0 8169dd87 84bf50d8 00000080 00000000 nvstor+0xf676
80c34a1c 816a1f5f 80c34a40 80c34a3f 00000001 nvstor+0x3d87
80c34a50 816a0f14 849b06f8 849b0000 84bf50d8 nvstor+0x7f5f
80c34ac4 816a234b 84bf50d8 849b0000 00000000 nvstor+0x6f14
80c34ae4 816aaad0 849b0000 00000000 00000001 nvstor+0x834b
80c34af8 816aa7ae 84bf6a08 00000001 00000000 nvstor+0x10ad0
80c34b18 816aa697 816ac934 84bf5008 84bf6d00 nvstor+0x107ae
80c34b34 816ac992 84bf5008 849a10e0 8101530c nvstor+0x10697
80c34b48 816c0c3c 84bf5008 00000000 80c34c68 nvstor+0x12992
80c34b68 80f96d59 849a14d0 849a1028 398a0c36 storport!RaidpAdapterTimerDpcRoutine+0x61
80c34c20 80f969a3 810220c0 80c34c68 8754ea00 nt!KiExecuteAllDpcs+0x1f2
80c34d40 80f21f94 00000000 0000000e 00000000 nt!KiRetireDpcList+0xed
80c34d44 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38
STACK_COMMAND: kb
FOLLOWUP_IP:
nvstor+f676
816a9676 ?? ???
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: nvstor+f676
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvstor
IMAGE_NAME: nvstor.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4e6e9418
FAILURE_BUCKET_ID: 0x133_DPC_nvstor+f676
BUCKET_ID: 0x133_DPC_nvstor+f676
Followup: MachineOwner
---------
