2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
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: fffff88486d7a860
Arg4: ffffe4871b8ede90
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2843
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 13998
Key : Analysis.Init.CPU.mSec
Value: 202
Key : Analysis.Init.Elapsed.mSec
Value: 2629
Key : Analysis.Memory.CommitPeak.Mb
Value: 75
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
BUGCHECK_CODE: 119
BUGCHECK_P1: 2
BUGCHECK_P2: ffffffffc000000d
BUGCHECK_P3: fffff88486d7a860
BUGCHECK_P4: ffffe4871b8ede90
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffff884`86d7a788 fffff807`6ff43ad0 : 00000000`00000119 00000000`00000002 ffffffff`c000000d fffff884`86d7a860 : nt!KeBugCheckEx
fffff884`86d7a790 fffff807`86498399 : ffffe487`1b8eb000 00000000`c000000d fffff884`86d7a899 00000000`00000007 : watchdog!WdLogEvent5_WdCriticalError+0xe0
fffff884`86d7a7d0 fffff807`86514bcd : ffffe487`00000000 ffffe487`1b8ede90 ffffe487`1b7eb000 ffffe487`23c47010 : dxgmms2!VidSchiSendToExecutionQueue+0xa99
fffff884`86d7a900 fffff807`8651d54a : ffffe487`23c47010 ffffe487`1b7eb000 00000000`00000000 ffffe487`1a06c6e0 : dxgmms2!VidSchiSubmitPagingCommand+0x2ed
fffff884`86d7aa80 fffff807`8651d3ba : ffffe487`1b7eb400 fffff807`8651d2f0 ffffe487`1b7eb000 fffff807`52f9d100 : dxgmms2!VidSchiRun_PriorityTable+0x17a
fffff884`86d7aad0 fffff807`57e55485 : ffffe487`1b846380 fffff807`00000001 ffffe487`1b7eb000 000fa4ef`bd9bbfff : dxgmms2!VidSchiWorkerThread+0xca
fffff884`86d7ab10 fffff807`58002cc8 : fffff807`52f9d180 ffffe487`1b846380 fffff807`57e55430 003e9999`9a000000 : nt!PspSystemThreadStartup+0x55
fffff884`86d7ab60 00000000`00000000 : fffff884`86d7b000 fffff884`86d74000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: dxgmms2!VidSchiSendToExecutionQueue+a99
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
IMAGE_VERSION: 10.0.19041.2311
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: a99
FAILURE_BUCKET_ID: 0x119_2_
DRIVER_FAILED_SUBMIT_COMMAND_dxgmms2!VidSchiSendToExecutionQueue
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {9a11bf9c-270e-962e-7a82-3efdab93c10e}
Followup: MachineOwner
---------