*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 119, {1, 1137d, 1137e, 1137e}
Unable to load image \SystemRoot\system32\drivers\mctkmd64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for mctkmd64.sys
*** ERROR: Module load completed but symbols could not be loaded for mctkmd64.sys
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 : dxgmms1.sys ( dxgmms1!VidSchiVerifyDriverReportedFenceId+ad )
VIDEO_SCHEDULER_INTERNAL_ERROR (119)
The video scheduler has detected that fatal violation has occurred. This resulted
in a condition that video scheduler can no longer progress. Any other values after
parameter 1 must be individually examined according to the subtype.
Arguments:
Arg1: 0000000000000001, The driver has reported an invalid fence ID.
Arg2: 000000000001137d
Arg3: 000000000001137e
Arg4: 000000000001137e
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x119
PROCESS_NAME: System
CURRENT_IRQL: 6
LAST_CONTROL_TRANSFER: from fffff8800153e22f to fffff80003a92d00
STACK_TEXT:
fffff800`05daa6a8 fffff880`0153e22f : 00000000`00000119 00000000`00000001 00000000`0001137d 00000000`0001137e : nt!KeBugCheckEx
fffff800`05daa6b0 fffff880`04574eb9 : 00000000`00000000 00000000`0001137d 00000000`00000000 00000000`0001137e : watchdog!WdLogEvent5+0x11b
fffff800`05daa700 fffff880`045751e6 : fffffa80`087bc000 fffffa80`06d2aba8 fffffa80`000011ac fffffa80`06eb0000 : dxgmms1!VidSchiVerifyDriverReportedFenceId+0xad
fffff800`05daa730 fffff880`04574f76 : fffffa80`0001137d fffff800`05daa930 fffffa80`087bc000 fffffa80`08498000 : dxgmms1!VidSchDdiNotifyInterruptWorker+0x25e
fffff800`05daa780 fffff880`0447c13f : fffffa80`06cb6040 fffff880`0f329d98 fffffa80`06eb0000 00000000`00000000 : dxgmms1!VidSchDdiNotifyInterrupt+0x9e
fffff800`05daa7b0 fffff880`0fed92cc : fffff880`0f329d1d fffff800`05daa9a0 00000000`00000000 00000000`00000000 : dxgkrnl!DxgNotifyInterruptCB+0x83
fffff800`05daa7e0 fffff880`0f329d1d : fffff800`05daa9a0 00000000`00000000 00000000`00000000 00000000`00000000 : mctkmd64+0x82cc
fffff800`05daa7e8 fffff800`05daa9a0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nvlddmkm+0xb5d1d
fffff800`05daa7f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff800`05daa9a0
STACK_COMMAND: kb
FOLLOWUP_IP:
dxgmms1!VidSchiVerifyDriverReportedFenceId+ad
fffff880`04574eb9 c744244053eeffff mov dword ptr [rsp+40h],0FFFFEE53h
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: dxgmms1!VidSchiVerifyDriverReportedFenceId+ad
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgmms1
IMAGE_NAME: dxgmms1.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce799c1
FAILURE_BUCKET_ID: X64_0x119_dxgmms1!VidSchiVerifyDriverReportedFenceId+ad
BUCKET_ID: X64_0x119_dxgmms1!VidSchiVerifyDriverReportedFenceId+ad
Followup: MachineOwner
---------