*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa80077d04e0, fffff88010518630, ffffffffc000009a, 4}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+ade630 )
Followup: MachineOwner
---------
3: kd> lmvm nvlddmkm
start end module name
fffff880`0fa3a000 fffff880`1072e000 nvlddmkm T (no symbols)
Loaded symbol image file: nvlddmkm.sys
Image path: nvlddmkm.sys
Image name: nvlddmkm.sys
Timestamp: Wed Oct 03 00:21:13 2012 (506B3099)
CheckSum: 00CD4613
ImageSize: 00CF4000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80077d04e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88010518630, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.
Debugging Details:
------------------
FAULTING_IP:
nvlddmkm+ade630
fffff880`10518630 ?? ???
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`045abb88 fffff880`0492a000 : 00000000`00000116 fffffa80`077d04e0 fffff880`10518630 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`045abb90 fffff880`048fd867 : fffff880`10518630 fffffa80`09f2f000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`045abbd0 fffff880`04929e0f : 00000000`ffffd84d fffff800`05244080 fffffa80`077d04e0 00000000`0000000f : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`045abc80 fffff880`04837ec1 : fffffa80`0b2cc010 00000000`00000080 00000000`00000000 fffffa80`09f2a010 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`045abd00 fffff800`0371ee5a : 00000000`0465464c fffffa80`09f4a610 fffffa80`06cacb30 fffffa80`09f4a610 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`045abd40 fffff800`03478d26 : fffff800`035fae80 fffffa80`09f4a610 fffff800`03608cc0 00000012`0ef51000 : nt!PspSystemThreadStartup+0x5a
fffff880`045abd80 00000000`00000000 : fffff880`045ac000 fffff880`045a6000 fffff880`045ab610 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nvlddmkm+ade630
fffff880`10518630 ?? ???
SYMBOL_NAME: nvlddmkm+ade630
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 506b3099
FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
Followup: MachineOwner
---------