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: 0000000000000002, The driver failed upon the submission of a command.
Arg2: ffffffffc000000d
Arg3: ffff85063f299a60
Arg4: ffffa8027ef2e2d0
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 3
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-K01TCKK
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 23
Key : Analysis.Memory.CommitPeak.Mb
Value: 71
Key : Analysis.System
Value: CreateObject
ADDITIONAL_XML: 1
BUGCHECK_CODE: 119
BUGCHECK_P1: 2
BUGCHECK_P2: ffffffffc000000d
BUGCHECK_P3: ffff85063f299a60
BUGCHECK_P4: ffffa8027ef2e2d0
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffff8506`3f299988 fffff801`6906419b : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffff8506`3f299a60 : nt!KeBugCheckEx
ffff8506`3f299990 fffff801`6a84abf3 : 00000000`00000000 ffffa802`7ef2b000 ffff8506`3f299a99 ffffa802`7ef2b000 : watchdog!WdLogEvent5_WdCriticalError+0xdb
ffff8506`3f2999d0 fffff801`6a8a8684 : ffffa802`00000000 ffffa802`7ef2e2d0 ffffa802`7f677000 ffffa802`7d8552d0 : dxgmms2!VidSchiSendToExecutionQueue+0x14a03
ffff8506`3f299b00 fffff801`6a8b9ad5 : ffffa802`7e1a0010 ffffa802`7f677000 00000000`00000000 ffffa802`7f6bb810 : dxgmms2!VidSchiSubmitPagingCommand+0x2f4
ffff8506`3f299c80 fffff801`6a8b994a : ffffa802`7f677400 fffff801`6a8b9880 ffffa802`7f677000 00000000`00000000 : dxgmms2!VidSchiRun_PriorityTable+0x175
ffff8506`3f299cd0 fffff800`3132a7a5 : ffffa802`77eb3640 fffff801`00000001 ffffa802`7f677000 ffffffff`ffffffff : dxgmms2!VidSchiWorkerThread+0xca
ffff8506`3f299d10 fffff800`313c8b2a : fffff800`2d5a0180 ffffa802`77eb3640 fffff800`3132a750 ffffffff`ffffffff : nt!PspSystemThreadStartup+0x55
ffff8506`3f299d60 00000000`00000000 : ffff8506`3f29a000 ffff8506`3f294000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a
SYMBOL_NAME: dxgmms2!VidSchiSendToExecutionQueue+14a03
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
IMAGE_VERSION: 10.0.18362.625
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 14a03
FAILURE_BUCKET_ID: 0x119_2_DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {9a11bf9c-270e-962e-7a82-3efdab93c10e}
Followup: MachineOwner
---------
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff8038a96828a, address which referenced memory
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
