Windows 10: VIDEO_SCHEDULER_INTERNAL_ERROR

I keep getting blue screen errors with stopcode in the title. It doesn't seem to correlate with anything. Could someone help me?


Here is the dump file: easyUpload


Here is the analyze:


Microsoft R Windows Debugger Version 10.0.19041.685 X86

Copyright c Microsoft Corporation. All rights reserved.





Loading Dump File [C:\Users\fatma\Desktop\022421-41953-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available





************* Path validation summary **************

Response Time ms Location

Deferred https://msdl.microsoft.com/download/symbols

Symbol search path is: https://msdl.microsoft.com/download/symbols

Executable search path is:

Windows 10 Kernel Version 19041 MP 8 procs Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Built by: 19041.1.amd64fre.vb_release.191206-1406

Machine Name:

Kernel base = 0xfffff807`31c00000 PsLoadedModuleList = 0xfffff807`3282a390

Debug session time: Wed Feb 24 15:30:33.981 2021 UTC + 3:00

System Uptime: 0 days 18:02:58.684

Loading Kernel Symbols

...............................................................

................................................................

................................................................

..

Loading User Symbols

Loading unloaded module list

..................................................

For analysis of this file, run !analyze -v

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: ffffa585d614f960

Arg4: ffff940dc2853c90



Debugging Details:

------------------



*** WARNING: Unable to verify timestamp for win32k.sys



KEY_VALUES_STRING: 1



Key : Analysis.CPU.Sec

Value: 8



Key : Analysis.DebugAnalysisProvider.CPP

Value: Create: 8007007e on DESKTOP-F4GTETJ



Key : Analysis.DebugData

Value: CreateObject



Key : Analysis.DebugModel

Value: CreateObject



Key : Analysis.Elapsed.Sec

Value: 12



Key : Analysis.Memory.CommitPeak.Mb

Value: 78



Key : Analysis.System

Value: CreateObject





BUGCHECK_CODE: 119



BUGCHECK_P1: 2



BUGCHECK_P2: ffffffffc000000d



BUGCHECK_P3: ffffa585d614f960



BUGCHECK_P4: ffff940dc2853c90



BLACKBOXBSD: 1 !blackboxbsd





BLACKBOXNTFS: 1 !blackboxntfs





BLACKBOXPNP: 1 !blackboxpnp





BLACKBOXWINLOGON: 1



CUSTOMER_CRASH_COUNT: 1



PROCESS_NAME: System



STACK_TEXT:

ffffa585`d614f888 fffff807`40533ad0 : 00000000`00000119 00000000`00000002 ffffffff`c000000d ffffa585`d614f960 : nt!KeBugCheckEx

ffffa585`d614f890 fffff807`310fb3bf : 00000000`00000000 ffff940d`c2850000 ffff940d`c28ad8a0 ffff940d`c2850466 : watchdog!WdLogEvent5_WdCriticalError+0xe0

ffffa585`d614f8d0 fffff807`31163cdd : ffff940d`00000000 ffff940d`c2853c90 ffff940d`c2827000 ffff940d`c334fb40 : dxgmms2!VidSchiSendToExecutionQueue+0x12fff

ffffa585`d614fa00 fffff807`3116be8a : ffff940d`c334fb40 ffff940d`c2827000 00000000`00000000 ffff940d`c2869720 : dxgmms2!VidSchiSubmitPagingCommand+0x2ed

ffffa585`d614fb80 fffff807`3116bcfa : ffff940d`c2827400 fffff807`3116bc30 ffff940d`c2827000 ffffda01`9dfb6100 : dxgmms2!VidSchiRun_PriorityTable+0x17a

ffffa585`d614fbd0 fffff807`31f17e25 : ffff940d`beed1080 fffff807`00000001 ffff940d`c2827000 000fa425`bd9bbfff : dxgmms2!VidSchiWorkerThread+0xca

ffffa585`d614fc10 fffff807`31ffd0d8 : ffffda01`9dfb6180 ffff940d`beed1080 fffff807`31f17dd0 00000000`00000000 : nt!PspSystemThreadStartup+0x55

ffffa585`d614fc60 00000000`00000000 : ffffa585`d6150000 ffffa585`d614a000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28





SYMBOL_NAME: dxgmms2!VidSchiSendToExecutionQueue+12fff



MODULE_NAME: dxgmms2



IMAGE_NAME: dxgmms2.sys



IMAGE_VERSION: 10.0.19041.1136



STACK_COMMAND: .thread ; .cxr ; kb



BUCKET_ID_FUNC_OFFSET: 12fff



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

---------



2: kd> lmvm dxgmms2

Browse full module list

start end module name

fffff807`310e0000 fffff807`311c2000 dxgmms2 # pdb symbols C:\ProgramData\dbg\sym\dxgmms2.pdb\78943430616B97561C849D139B8D31C21\dxgmms2.pdb

Loaded symbol image file: dxgmms2.sys

Mapped memory image file: C:\ProgramData\dbg\sym\dxgmms2.sys\EB81CD48e2000\dxgmms2.sys

Image path: \SystemRoot\System32\drivers\dxgmms2.sys

Image name: dxgmms2.sys

Browse all global symbols functions data

Image was built with /Brepro flag.

Timestamp: EB81CD48 This is a reproducible build file hash, not a timestamp

CheckSum: 000E0779

ImageSize: 000E2000

File version: 10.0.19041.1136

Product version: 10.0.19041.1136

File flags: 0 Mask 3F

File OS: 40004 NT Win32

File type: 3.7 Driver

File date: 00000000.00000000

Translations: 0409.04b0

Information from resource tables:

CompanyName: Microsoft Corporation

ProductName: Microsoft® Windows® Operating System

InternalName: dxgmms2.sys

OriginalFilename: dxgmms2.sys

ProductVersion: 10.0.19041.1136

FileVersion: 10.0.19041.1136 WinBuild.160101.0800

FileDescription: DirectX Graphics MMS

LegalCopyright: © Microsoft Corporation. All rights reserved.

:)

 

Video_Scheduler_internal_error on Windows 10

So I spoke to Nvidia they said this is completely a Microsoft issue. They said to follow some steps for windows 7 that didnt work obviously so after many months on the phone with these guys they said it was microsoft issue with the windows 10 software that
seems to be broken.

My question is this Microsoft when are you going to fix this Video_Scheduler_internal_error?

What do I need a video sceduler for?

How does one disable it or remove it?

 

Windows 10, BSOD, VIDEO_SCHEDULER_INTERNAL_ERROR 0x00000119

Hi Dilip,

Thank you for being part of Microsoft Community.

The VIDEO_SCHEDULER_INTERNAL_ERROR bug check has a value of 0x00000119. This indicates that the video scheduler has detected a fatal violation.

I would suggest you to check for any patches or updates pertaining to the game and install them accordingly.

If the issue is pertaining to only this software/game, then I suggest that you uninstall and reinstall the Software/game in Windows 7/8 compatibility mode. Refer to the following article to do the same:

http://windows.microsoft.com/en-US/windows-8/older-programs-compatible-version-windows

Note: The above mentioned steps are also applicable to Windows 10.

Do get back to us for any issues pertaining in the future. We will be happy to help.

 

VIDEO_SCHEDULER_INTERNAL_ERROR from atikmpag with videos and games

When watching Youtube videos or playing games (very frequent with Playerunknown Battlegrounds), I often receive a BSOD with the error VIDEO_SCHEDULER_INTERNAL_ERROR. Playing PUBG, I probably receive the BSOD one out of every three games.

System
---------
Windows 10 64 bit
Intel i5-7500
Radeon RX480
8GB RAM

WhoCrashed Analysis
-----------------------------
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0x4787B)
Bugcheck code: 0x119 (0x5, 0xFFFFE18529174000, 0xFFFFE18529526AD0, 0x35ED4)
Error: VIDEO_SCHEDULER_INTERNAL_ERROR
file path: C:\WINDOWS\system32\drivers\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport Driver
Bug check description: This indicates that the video scheduler has detected a fatal violation.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).

DM Log
----------
Attachment 146296

After reading other posts, I ran a the usually recommended command prompt scans as well.
Attachment 146297

Appreciate anyone who can help me out.