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: ffffd5864e643960
Arg4: ffffc207aff7ecd0
Debugging Details:
------------------
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 6109
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-G25IS1E
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 28818
Key : Analysis.Memory.CommitPeak.Mb
Value: 85
Key : Analysis.System
Value: CreateObject
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
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 119
BUGCHECK_P1: 2
BUGCHECK_P2: ffffffffc000000d
BUGCHECK_P3: ffffd5864e643960
BUGCHECK_P4: ffffc207aff7ecd0
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffffd586`4e643888 fffff804`4d773ad0 : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffffd586`4e643960 : nt!KeBugCheckEx
ffffd586`4e643890 fffff804`4dfebba1 : 00000000`00000000 ffffc207`aff7c000 ffffc207`b0029410 ffffc207`aff7c316 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffffd586`4e6438d0 fffff804`4e0530bd : ffffc207`00000000 ffffc207`aff7ecd0 ffffc207`afe7f000 ffffc207`b358b010 : dxgmms2!VidSchiSendToExecutionQueue+0x12761
ffffd586`4e643a00 fffff804`4e05ae8a : ffffc207`b358b010 ffffc207`afe7f000 00000000`00000000 ffffc207`afeb5720 : dxgmms2!VidSchiSubmitPagingCommand+0x2ed
ffffd586`4e643b80 fffff804`4e05acfa : ffffc207`afe7f400 fffff804`4e05ac30 ffffc207`afe7f000 ffffd801`78ccf100 : dxgmms2!VidSchiRun_PriorityTable+0x17a
ffffd586`4e643bd0 fffff804`408a29a5 : ffffc207`afebf380 fffff804`00000001 ffffc207`afe7f000 000f8067`b4bbbdff : dxgmms2!VidSchiWorkerThread+0xca
ffffd586`4e643c10 fffff804`409fc868 : ffffd801`78ccf180 ffffc207`afebf380 fffff804`408a2950 ce3fb1a7`ff3e3ff6 : nt!PspSystemThreadStartup+0x55
ffffd586`4e643c60 00000000`00000000 : ffffd586`4e644000 ffffd586`4e63e000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: dxgmms2!VidSchiSendToExecutionQueue+12761
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
IMAGE_VERSION: 10.0.19041.1124
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 12761
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
---------
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: fffff409023b1960
Arg4: ffff910ddad5d670
Debugging Details:
------------------
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 6734
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-G25IS1E
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 29137
Key : Analysis.Memory.CommitPeak.Mb
Value: 85
Key : Analysis.System
Value: CreateObject
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
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 119
BUGCHECK_P1: 2
BUGCHECK_P2: ffffffffc000000d
BUGCHECK_P3: fffff409023b1960
BUGCHECK_P4: ffff910ddad5d670
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffff409`023b1888 fffff803`38b73ad0 : 00000000`00000119 00000000`00000002 ffffffff`c000000d fffff409`023b1960 : nt!KeBugCheckEx
fffff409`023b1890 fffff803`3960bba1 : 00000000`00000000 ffff910d`dad5a000 fffff409`023b1999 ffff910d`dad5a000 : watchdog!WdLogEvent5_WdCriticalError+0xe0
fffff409`023b18d0 fffff803`396730bd : ffff910d`00000000 ffff910d`dad5d670 ffff910d`daa8a000 ffff910d`df624010 : dxgmms2!VidSchiSendToExecutionQueue+0x12761
fffff409`023b1a00 fffff803`3967ae8a : ffff910d`df624010 ffff910d`daa8a000 00000000`00000000 ffff910d`dad1d620 : dxgmms2!VidSchiSubmitPagingCommand+0x2ed
fffff409`023b1b80 fffff803`3967acfa : ffff910d`daa8a400 fffff803`3967ac30 ffff910d`daa8a000 ffffcf81`f8ecf100 : dxgmms2!VidSchiRun_PriorityTable+0x17a
fffff409`023b1bd0 fffff803`2bea29a5 : ffff910d`dac585c0 fffff803`00000001 ffff910d`daa8a000 000f8067`b4bbbdff : dxgmms2!VidSchiWorkerThread+0xca
fffff409`023b1c10 fffff803`2bffc868 : ffffcf81`f8ecf180 ffff910d`dac585c0 fffff803`2bea2950 ffffe4f0`e8e84d89 : nt!PspSystemThreadStartup+0x55
fffff409`023b1c60 00000000`00000000 : fffff409`023b2000 fffff409`023ac000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: dxgmms2!VidSchiSendToExecutionQueue+12761
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
IMAGE_VERSION: 10.0.19041.1124
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 12761
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
---------
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: ffff8c8b0b643960
Arg4: ffffe50d6c77d750
Debugging Details:
------------------
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 6249
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-G25IS1E
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 41516
Key : Analysis.Memory.CommitPeak.Mb
Value: 85
Key : Analysis.System
Value: CreateObject
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
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 119
BUGCHECK_P1: 2
BUGCHECK_P2: ffffffffc000000d
BUGCHECK_P3: ffff8c8b0b643960
BUGCHECK_P4: ffffe50d6c77d750
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffff8c8b`0b643888 fffff807`458e3ad0 : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffff8c8b`0b643960 : nt!KeBugCheckEx
ffff8c8b`0b643890 fffff807`46cfbba1 : 00000000`00000000 ffffe50d`6c77a000 ffff8c8b`0b643999 ffffe50d`6c77a000 : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffff8c8b`0b6438d0 fffff807`46d630bd : ffffe50d`00000000 ffffe50d`6c77d750 ffffe50d`6b432000 ffffe50d`6ddcd010 : dxgmms2!VidSchiSendToExecutionQueue+0x12761
ffff8c8b`0b643a00 fffff807`46d6ae8a : ffffe50d`6ddcd010 ffffe50d`6b432000 00000000`00000000 ffffe50d`6c73d620 : dxgmms2!VidSchiSubmitPagingCommand+0x2ed
ffff8c8b`0b643b80 fffff807`46d6acfa : ffffe50d`6b432400 fffff807`46d6ac30 ffffe50d`6b432000 ffff9881`b34cf100 : dxgmms2!VidSchiRun_PriorityTable+0x17a
ffff8c8b`0b643bd0 fffff807`370a29a5 : ffffe50d`6b487380 fffff807`00000001 ffffe50d`6b432000 000f8067`b4bbbdff : dxgmms2!VidSchiWorkerThread+0xca
ffff8c8b`0b643c10 fffff807`371fc868 : ffff9881`b34cf180 ffffe50d`6b487380 fffff807`370a2950 000c6b76`ffffffd8 : nt!PspSystemThreadStartup+0x55
ffff8c8b`0b643c60 00000000`00000000 : ffff8c8b`0b644000 ffff8c8b`0b63e000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: dxgmms2!VidSchiSendToExecutionQueue+12761
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
IMAGE_VERSION: 10.0.19041.1124
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 12761
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
---------
4: kd> !sysinfo machineid
Machine ID Information [From Smbios 3.2, DMIVersion 0, Size=2363]
BiosMajorRelease = 5
BiosMinorRelease = 14
BiosVendor = American Megatrends Inc.
BiosVersion = F2
BiosReleaseDate = 07/29/2020
SystemManufacturer = Gigabyte Technology Co., Ltd.
SystemProductName = B450M H
SystemFamily = B450 MB
SystemVersion = Default string
SystemSKU = Default string
BaseBoardManufacturer = Gigabyte Technology Co., Ltd.
BaseBoardProduct = B450M H
BaseBoardVersion = Default string
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: fffffe8aa8e2e960
Arg4: ffffab0a5717d050
Debugging Details:
------------------
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 5890
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-G25IS1E
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 28409
Key : Analysis.Memory.CommitPeak.Mb
Value: 85
Key : Analysis.System
Value: CreateObject
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
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 119
BUGCHECK_P1: 2
BUGCHECK_P2: ffffffffc000000d
BUGCHECK_P3: fffffe8aa8e2e960
BUGCHECK_P4: ffffab0a5717d050
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffffe8a`a8e2e888 fffff804`2c723ad0 : 00000000`00000119 00000000`00000002 ffffffff`c000000d fffffe8a`a8e2e960 : nt!KeBugCheckEx
fffffe8a`a8e2e890 fffff804`2d21bba1 : 00000000`00000000 ffffab0a`5717a000 fffffe8a`a8e2e999 ffffab0a`5717a000 : watchdog!WdLogEvent5_WdCriticalError+0xe0
fffffe8a`a8e2e8d0 fffff804`2d2830bd : ffffab0a`00000000 ffffab0a`5717d050 ffffab0a`56eb9000 ffffab0a`5bbe2010 : dxgmms2!VidSchiSendToExecutionQueue+0x12761
fffffe8a`a8e2ea00 fffff804`2d28ae8a : ffffab0a`5bbe2010 ffffab0a`56eb9000 00000000`00000000 ffffab0a`58208010 : dxgmms2!VidSchiSubmitPagingCommand+0x2ed
fffffe8a`a8e2eb80 fffff804`2d28acfa : ffffab0a`56eb9400 fffff804`2d28ac30 ffffab0a`56eb9000 ffffe101`036cf100 : dxgmms2!VidSchiRun_PriorityTable+0x17a
fffffe8a`a8e2ebd0 fffff804`1cca29a5 : ffffab0a`570c7380 fffff804`00000001 ffffab0a`56eb9000 000f8067`b4bbbdff : dxgmms2!VidSchiWorkerThread+0xca
fffffe8a`a8e2ec10 fffff804`1cdfc868 : ffffe101`036cf180 ffffab0a`570c7380 fffff804`1cca2950 6f2f1b37`7a01ce39 : nt!PspSystemThreadStartup+0x55
fffffe8a`a8e2ec60 00000000`00000000 : fffffe8a`a8e2f000 fffffe8a`a8e29000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: dxgmms2!VidSchiSendToExecutionQueue+12761
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
IMAGE_VERSION: 10.0.19041.1124
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 12761
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
---------
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: ffffab001bfee960
Arg4: ffffe701d4416bf0
Debugging Details:
------------------
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 6139
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-G25IS1E
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 40052
Key : Analysis.Memory.CommitPeak.Mb
Value: 85
Key : Analysis.System
Value: CreateObject
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
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: 119
BUGCHECK_P1: 2
BUGCHECK_P2: ffffffffc000000d
BUGCHECK_P3: ffffab001bfee960
BUGCHECK_P4: ffffe701d4416bf0
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffffab00`1bfee888 fffff801`317b3ad0 : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffffab00`1bfee960 : nt!KeBugCheckEx
ffffab00`1bfee890 fffff801`3329bba1 : 00000000`00000000 ffffe701`d4414000 ffffe701`d442e620 ffffe701`d441449e : watchdog!WdLogEvent5_WdCriticalError+0xe0
ffffab00`1bfee8d0 fffff801`333030bd : ffffe701`00000000 ffffe701`d4416bf0 ffffe701`d4321000 ffffe701`d5a31010 : dxgmms2!VidSchiSendToExecutionQueue+0x12761
ffffab00`1bfeea00 fffff801`3330ae8a : ffffe701`d5a31010 ffffe701`d4321000 00000000`00000000 ffffe701`d43d2620 : dxgmms2!VidSchiSubmitPagingCommand+0x2ed
ffffab00`1bfeeb80 fffff801`3330acfa : ffffe701`d4321400 fffff801`3330ac30 ffffe701`d4321000 ffffd701`d62cf100 : dxgmms2!VidSchiRun_PriorityTable+0x17a
ffffab00`1bfeebd0 fffff801`22ca29a5 : ffffe701`d436a380 fffff801`00000001 ffffe701`d4321000 000f8067`b4bbbdff : dxgmms2!VidSchiWorkerThread+0xca
ffffab00`1bfeec10 fffff801`22dfc868 : ffffd701`d62cf180 ffffe701`d436a380 fffff801`22ca2950 0000004e`0000000e : nt!PspSystemThreadStartup+0x55
ffffab00`1bfeec60 00000000`00000000 : ffffab00`1bfef000 ffffab00`1bfe9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: dxgmms2!VidSchiSendToExecutionQueue+12761
MODULE_NAME: dxgmms2
IMAGE_NAME: dxgmms2.sys
IMAGE_VERSION: 10.0.19041.1124
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 12761
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
---------
