*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa8006469010, fffff8800492aa74, 0, 2}
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+11aa74 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8006469010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800492aa74, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.
Debugging Details:
------------------
FAULTING_IP:
nvlddmkm+11aa74
fffff880`0492aa74 4883ec28 sub rsp,28h
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`0370d9c8 fffff880`03ce5cbc : 00000000`00000116 fffffa80`06469010 fffff880`0492aa74 00000000`00000000 : nt!KeBugCheckEx
fffff880`0370d9d0 fffff880`03ce59c6 : fffff880`0492aa74 fffffa80`06469010 fffffa80`04fefd50 fffffa80`06622010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`0370da10 fffff880`03d8cf07 : fffffa80`06469010 00000000`00000000 fffffa80`04fefd50 fffffa80`06622010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`0370da40 fffff880`03db6b75 : 00000000`ffffffff 00000000`00000ba9 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`0370db20 fffff880`03db52bb : 00000000`00000102 00000000`00000000 00000000`00000ba9 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`0370db50 fffff880`03d882c6 : ffffffff`ff676980 fffffa80`06622010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`0370dbf0 fffff880`03db4e7a : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`055a5768 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`0370dd00 fffff800`02d28166 : 00000000`05806744 fffffa80`04fe5620 fffffa80`03fd1040 fffffa80`04fe5620 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`0370dd40 fffff800`02a63486 : fffff800`02bfde80 fffffa80`04fe5620 fffff800`02c0bc40 00000000`01980000 : nt!PspSystemThreadStartup+0x5a
fffff880`0370dd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nvlddmkm+11aa74
fffff880`0492aa74 4883ec28 sub rsp,28h
SYMBOL_NAME: nvlddmkm+11aa74
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4c6d3530
FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
Followup: MachineOwner