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: ffffa68dcb70f860
Arg4: ffffc0836541dc90
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 4109
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 38177
Key : Analysis.Init.CPU.mSec
Value: 640
Key : Analysis.Init.Elapsed.mSec
Value: 178897
Key : Analysis.Memory.CommitPeak.Mb
Value: 83
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
FILE_IN_CAB: dump dosyalar (2).dmp
BUGCHECK_CODE: 119
BUGCHECK_P1: 2
BUGCHECK_P2: ffffffffc000000d
BUGCHECK_P3: ffffa68dcb70f860
BUGCHECK_P4: ffffc0836541dc90
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
PROCESS_NAME: System
STACK_TEXT:
ffffa68d`cb70f788 fffff800`60fb3ad0 : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffffa68d`cb70f860 : nt!KeBugCheckEx
ffffa68d`cb70f790 fffff800`47177b09 : ffffc083`6541a000 00000000`c000000d ffffa68d`cb70f899 00000000`00000003 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffffa68d`cb70f7d0 fffff800`471f4b9d : ffffc083`00000000 ffffc083`6541dc90 ffffc083`64c05000 ffffc083`6ae5a010 : dxgmms2!VidSchiSendToExecutionQueue+0xa99
ffffa68d`cb70f900 fffff800`471fd51a : ffffc083`6ae5a010 ffffc083`64c05000 00000000`00000000 ffffc083`64a87720 : dxgmms2!VidSchiSubmitPagingCommand+0x2ed
ffffa68d`cb70fa80 fffff800`471fd38a : ffffc083`64c05400 fffff800`471fd2c0 ffffc083`64c05000 ffffe680`d2c00100 : dxgmms2!VidSchiRun_PriorityTable+0x17a
ffffa68d`cb70fad0 fffff800`48355855 : ffffc083`590f5080 fffff800`00000001 ffffc083`64c05000 000fa4ef`bd9bbfff : dxgmms2!VidSchiWorkerThread+0xca
ffffa68d`cb70fb10 fffff800`483fe808 : ffffe680`d2c00180 ffffc083`590f5080 fffff800`48355800 000d541d`000e641d : nt!PspSystemThreadStartup+0x55
ffffa68d`cb70fb60 00000000`00000000 : ffffa68d`cb710000 ffffa68d`cb709000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: dxgmms2!VidSchiSendToExecutionQueue+a99
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
IMAGE_VERSION: 10.0.19041.1387
STACK_COMMAND: .cxr; .ecxr ; 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
drive.google.com
