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: 000000000000a000, The subtype of the BugCheck:
Arg2: ffff950f66e7e000
Arg3: 0000000000000002
Arg4: 0000000000000003
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 3187
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 32747
Key : Analysis.IO.Other.Mb
Value: 9
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 11
Key : Analysis.Init.CPU.mSec
Value: 578
Key : Analysis.Init.Elapsed.mSec
Value: 37659
Key : Analysis.Memory.CommitPeak.Mb
Value: 171
Key : Bugcheck.Code.DumpHeader
Value: 0x119
Key : Bugcheck.Code.Register
Value: 0x119
Key : Dump.Attributes.AsUlong
Value: 8
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
FILE_IN_CAB: 031023-8593-01.dmp
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_CODE: 119
BUGCHECK_P1: a000
BUGCHECK_P2: ffff950f66e7e000
BUGCHECK_P3: 2
BUGCHECK_P4: 3
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffffd8a`52a375c8 fffff805`86f65685 : 00000000`00000119 00000000`0000a000 ffff950f`66e7e000 00000000`00000002 : nt!KeBugCheckEx
fffffd8a`52a375d0 fffff805`8a645d98 : ffff950f`66e80002 ffff950f`3f959800 ffff950f`3f959808 ffff950f`3f959810 : watchdog!WdLogSingleEntry5+0x3b45
fffffd8a`52a37680 fffff805`8a705852 : ffff950f`66eee001 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms2!VidSchiResetHwEngine+0x3b8
fffffd8a`52a37830 fffff805`8a6d512b : ffff950f`66e80000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms2!VidSchiResetEngines+0xaa
fffffd8a`52a37880 fffff805`8a6a7c9f : 00000000`00000000 00000000`00000000 00000000`00537b8f 00000000`00989680 : dxgmms2!VidSchiCheckHwProgress+0x2d44b
fffffd8a`52a37900 fffff805`8a60b689 : 00000000`00000000 ffff950f`66e80000 fffffd8a`52a37a39 00000000`00000000 : dxgmms2!VidSchiWaitForSchedulerEvents+0x37f
fffffd8a`52a379d0 fffff805`8a6b3a95 : ffff950f`6a542000 ffff950f`66e80000 ffff950f`6a542010 ffff950f`66e76900 : dxgmms2!VidSchiScheduleCommandToRun+0x309
fffffd8a`52a37aa0 fffff805`8a6b3a0a : 00057c24`00000000 fffff805`8a6b3940 ffff950f`66e80000 00000000`00000080 : dxgmms2!VidSchiRun_PriorityTable+0x35
fffffd8a`52a37af0 fffff805`6e40f5b7 : ffff950f`64e42040 fffff805`00000001 ffff950f`66e80000 0005a6a0`000582d8 : dxgmms2!VidSchiWorkerThread+0xca
fffffd8a`52a37b30 fffff805`6e62e2e4 : ffffa900`19100180 ffff950f`64e42040 fffff805`6e40f560 0001fc58`0005beb4 : nt!PspSystemThreadStartup+0x57
fffffd8a`52a37b80 00000000`00000000 : fffffd8a`52a38000 fffffd8a`52a31000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34
SYMBOL_NAME: dxgmms2!VidSchiResetHwEngine+3b8
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
IMAGE_VERSION: 10.0.22621.1391
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 3b8
FAILURE_BUCKET_ID: 0x119_a000_VIDSCH_RESET_HW_ENGINE_SUSPEND_dxgmms2!VidSchiResetHwEngine
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {95884248-9389-91d4-05c4-d0b1411f9702}
Followup: MachineOwner
---------
