tr.msi.com
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: ffffa78b8f030960
Arg4: ffffd68cb806df70
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 8062
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 52710
Key : Analysis.Init.CPU.mSec
Value: 1234
Key : Analysis.Init.Elapsed.mSec
Value: 116096
Key : Analysis.Memory.CommitPeak.Mb
Value: 77
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: ffffa78b8f030960
BUGCHECK_P4: ffffd68cb806df70
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffffa78b`8f030888 fffff806`251b3ad0 : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffffa78b`8f030960 : nt!KeBugCheckEx
ffffa78b`8f030890 fffff806`292cb3cb : 00000000`00000000 ffffd68c`b806b000 ffffa78b`8f030999 ffffd68c`b806b000 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffffa78b`8f0308d0 fffff806`29334b6d : ffffd68c`00000000 ffffd68c`b806df70 ffffd68c`b6f95000 ffffd68c`bceb8520 : dxgmms2!VidSchiSendToExecutionQueue+0x1306b
ffffa78b`8f030a00 fffff806`2933cd1a : ffffd68c`bceb8520 ffffd68c`b6f95000 00000000`00000000 ffffd68c`b8008620 : dxgmms2!VidSchiSubmitPagingCommand+0x2ed
ffffa78b`8f030b80 fffff806`2933cb8a : ffffd68c`b6f95400 fffff806`2933cac0 ffffd68c`b6f95000 ffffc500`4bec0100 : dxgmms2!VidSchiRun_PriorityTable+0x17a
ffffa78b`8f030bd0 fffff806`15517e85 : ffffd68c`b6f98280 fffff806`00000001 ffffd68c`b6f95000 000f8067`b4bbbdff : dxgmms2!VidSchiWorkerThread+0xca
ffffa78b`8f030c10 fffff806`155fd2a8 : ffffc500`4bec0180 ffffd68c`b6f98280 fffff806`15517e30 a70fd71d`0448dc80 : nt!PspSystemThreadStartup+0x55
ffffa78b`8f030c60 00000000`00000000 : ffffa78b`8f031000 ffffa78b`8f02b000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: dxgmms2!VidSchiSendToExecutionQueue+1306b
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
IMAGE_VERSION: 10.0.19041.1140
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 1306b
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
---------
