STOP CODE · 0x119
VIDEO_
The part of Windows that schedules work for the graphics card found something it could not continue from. The scheduler is Windows' own code, and the one remedy Microsoft gives is about the graphics driver that works with it.
WHAT MICROSOFT SAYS
Microsoft's reference says this bug check "indicates that the video scheduler has detected a fatal violation". Its resolution: "If the faulting module listed in the !analyze output is a video driver, see if updates are available for that video driver from the vendor." Microsoft's display documentation places the scheduler in dxgmms2.sys, which implements the GPU scheduler and video memory manager.
From Microsoft's documentation, linked under Sources. Microsoft wrote its page for this code for programmers; the steps below are the ones it gives everyone else.
TECHNICAL SUMMARY
| Stop code | VIDEO_SCHEDULER_INTERNAL_ERROR |
|---|---|
| Value | 0x00000119 (0x119) |
| Where you see it | At the bottom of the stop screen, and in the System event log after the restart |
| In Tweaky Driver | Stop codes are not read; driver versions are checked |
What causes VIDEO_
- A violation detected by the video scheduler; the first parameter of the stop code identifies which one.
- A video driver at fault: the case Microsoft's resolution addresses.
How to fix VIDEO_
The steps come from Microsoft's guidance, with the reversible ones first. Each one says how to put back what it changed. If Windows cannot start normally, Microsoft's basic steps say to start in safe mode and continue from there.
Write down the stop code and the file the screen names
Microsoft Support says the stop code appears at the bottom of the screen and, when Windows knows it, so does the name of the module that was running. If the screen went by too fast, the command under Check it yourself lists the stop codes Windows recorded, and Event Viewer > Windows Logs > System shows the errors logged around the restart.
To undo: Nothing to undo: this only reads information.
Before you change anything: note the driver and make a restore point
Open the device's Properties > Driver tab and write down the driver provider, date and version. Then select Start, type Create a restore point, open it, and on the System Protection tab choose Create. Microsoft notes that System Protection is not turned on by default; if Create is greyed out, choose Configure and turn it on for the system drive first.
To undo: A restore point changes nothing by itself. To go back later, run System Restore and pick it: Microsoft says it reverts system files, the registry and installed programs, and leaves your personal files alone.
Install the current graphics driver
Microsoft's resolution for this code is to see whether updates are available for the video driver from the vendor. Get the driver for your exact graphics card from its maker, or from the PC maker's support page for a laptop, and install it.
To undo: Open the display adapter's Properties > Driver tab in Device Manager and choose Roll Back Driver, or apply the restore point.
If it started after a driver update, roll the driver back
In Device Manager, right-click the device, choose Properties, open the Driver tab and select Roll Back Driver, then give a reason and confirm. Microsoft notes that you need administrator rights, and that going back to the previous driver often fixes a problem that appeared after an update. The button is greyed out when Windows kept no earlier driver for the device.
To undo: Rolling back is the undo for the update. To return to the newer driver, install it again with Update driver or from the manufacturer's package.
Install the latest Windows updates
Select Start > Settings > Windows Update and choose Check for updates. It is one of Microsoft's basic steps for a stop code that keeps returning, and it is how new versions of Windows' own drivers arrive.
To undo: If the crashes get worse after an update, apply the restore point from the earlier step.
Check Windows' own files
dxgmms2.sys, the file that holds the scheduler, is part of Windows, so there is no separate download for it. Open Command Prompt as administrator and run
DISM.exe /Online /Cleanup-image /Restorehealth, thensfc /scannow. Microsoft says to run DISM first, and that sfc scans all protected system files and replaces corrupted ones with a cached copy.To undo: No undo is needed: the tools only put back Microsoft's version of a damaged Windows file.
If nothing helps, go back to a restore point
Microsoft's last basic step is to restore Windows from a system restore point made before the crashes began, or to use one of its other recovery options.
To undo: System Restore leaves personal files alone; programs and drivers installed after that restore point have to be installed again.
Check it yourself
List the stop codes Windows recorded (PowerShell)
Each entry gives the date, the stop code as a hexadecimal number with its four parameters, and where the dump file was saved. On the test PC, Windows 11 build 26300, this ran without administrator rights. An error saying no events were found means Windows recorded none. This stop code appears there as 0x00000119.
PowerShellGet-WinEvent -FilterHashtable @{ LogName='System'; Id=1001; ProviderName='Microsoft-Windows-WER-SystemErrorReporting' } -MaxEvents 5 | Format-List TimeCreated, MessageList the driver packages installed on the PC
Shows every third-party driver package with its provider, class, version and date, so you can see what was installed around the first crash. Nothing is changed.
cmdpnputil /enum-drivers
What Tweaky Driver can and cannot do here
Driver version checkTweaky Driver does not read crash dumps or stop codes, so it cannot tell you which driver caused this screen. It helps with the step that comes after Windows names a driver: its scan lists every device with the installed driver version and shows whether Windows Update, the Microsoft Update Catalog or a manufacturer package it supports has a newer one, with the source and version in front of you before anything is installed. The scheduler itself is part of Windows and is updated by Windows Update, not by a driver package. A newer driver is no promise that the blue screen stops: the same code can come from hardware or from Windows itself.
Tweaky Driver, the driver checker that shows its sources — free for Windows 10 and 11.
Common questions
What does VIDEO_SCHEDULER_INTERNAL_ERROR mean?
The video scheduler, the part of Windows' graphics subsystem that schedules work for the graphics card, detected a fatal violation.
Is VIDEO_SCHEDULER_INTERNAL_ERROR caused by the graphics driver?
Microsoft's resolution covers exactly that case: if the faulting module is a video driver, look for an update from the vendor. Its page gives no other remedy.
Which file is the video scheduler?
dxgmms2.sys. Microsoft describes it as the file that implements the GPU scheduler and video memory manager for display drivers from WDDM 2.0 on, loaded by dxgkrnl.sys.