*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa8006a60010, fffff88003c2d198, ffffffffc00000b5, a}
*** 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+139198 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8006a60010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88003c2d198, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc00000b5, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 000000000000000a, Optional internal context dependent data.
Debugging Details:
------------------
FAULTING_IP:
nvlddmkm+139198
fffff880`03c2d198 4055 push rbp
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`02eb2928 fffff880`03a5d000 : 00000000`00000116 fffffa80`06a60010 fffff880`03c2d198 ffffffff`c00000b5 : nt!KeBugCheckEx
fffff880`02eb2930 fffff880`03a5cddb : fffff880`03c2d198 fffffa80`06a60010 00000000`00000000 fffffa80`0a0f3010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`02eb2970 fffff880`045abf07 : fffffa80`06a60010 00000000`c00000b5 00000000`00000000 fffffa80`0a0f3010 : dxgkrnl!TdrIsRecoveryRequired+0x273
fffff880`02eb29a0 fffff880`045d5bd4 : fffffa80`00000000 00000000`004ebca7 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`02eb2a80 fffff880`045a72d5 : fffffa80`0a0f3010 fffffa80`00000000 00000000`004ebca7 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0xd0
fffff880`02eb2ab0 fffff880`045d3e7a : 00000000`00000000 fffffa80`0a384910 00000000`00000080 fffffa80`0a0f3010 : dxgmms1!VidSchiScheduleCommandToRun+0x1e9
fffff880`02eb2bc0 fffff800`02b2e34a : 00000000`029c54f6 fffffa80`0a101760 fffffa80`066ae890 fffffa80`0a101760 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`02eb2c00 fffff800`0287e946 : fffff800`02a09e80 fffffa80`0a101760 fffff800`02a17cc0 00000000`00000004 : nt!PspSystemThreadStartup+0x5a
fffff880`02eb2c40 00000000`00000000 : fffff880`02eb3000 fffff880`02ead000 fffff880`02eb26b0 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nvlddmkm+139198
fffff880`03c2d198 4055 push rbp
SYMBOL_NAME: nvlddmkm+139198
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5116d804
FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
Followup: MachineOwner
---------
2: kd> lmvm nvlddmkm
start end module name
fffff880`03af4000 fffff880`0459c000 nvlddmkm T (no symbols)
Loaded symbol image file: nvlddmkm.sys
Image path: nvlddmkm.sys
Image name: nvlddmkm.sys
Timestamp: Sun Feb 10 05:13:08 2013 (5116D804)
CheckSum: 00A90CB0
ImageSize: 00AA8000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
