*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa8012306010, fffff8800598b010, 0, d}
Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** 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+13b010 )
Followup: MachineOwner
---------
5: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8012306010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800598b010, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 000000000000000d, Optional internal context dependent data.
Debugging Details:
------------------
FAULTING_IP:
nvlddmkm+13b010
fffff880`0598b010 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`06d94928 fffff880`04ec1054 : 00000000`00000116 fffffa80`12306010 fffff880`0598b010 00000000`00000000 : nt!KeBugCheckEx
fffff880`06d94930 fffff880`04ec0ddb : fffff880`0598b010 fffffa80`12306010 00000000`00000000 fffffa80`0ebcf010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`06d94970 fffff880`04f67f13 : fffffa80`12306010 00000000`00000000 00000000`00000000 fffffa80`0ebcf010 : dxgkrnl!TdrIsRecoveryRequired+0x21f
fffff880`06d949a0 fffff880`04f91d50 : fffffa80`00000000 00000000`004a3fca 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`06d94a80 fffff880`04f632e1 : fffffa80`0ebcf010 fffffa80`00000000 00000000`004a3fca 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0xd0
fffff880`06d94ab0 fffff880`04f8fff6 : 00000000`00000000 fffffa80`0ea9a7f0 00000000`00000080 fffffa80`0ebcf010 : dxgmms1!VidSchiScheduleCommandToRun+0x1e9
fffff880`06d94bc0 fffff800`03730ede : 00000000`fffffc32 fffffa80`0ec08060 fffffa80`096c66f0 fffffa80`0ec08060 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`06d94c00 fffff800`03483906 : fffff880`032a5180 fffffa80`0ec08060 fffff880`032b00c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`06d94c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nvlddmkm+13b010
fffff880`0598b010 4055 push rbp
SYMBOL_NAME: nvlddmkm+13b010
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 518fe8f9
FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
Followup: MachineOwner
---------
5: kd> lmvm nvlddmkm
start end module name
fffff880`05850000 fffff880`06331000 nvlddmkm T (no symbols)
Loaded symbol image file: nvlddmkm.sys
Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
Image name: nvlddmkm.sys
Timestamp: Mon May 13 01:09:45 2013 (518FE8F9)
CheckSum: 00AB6DED
ImageSize: 00AE1000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4