Fix VIDEO_SCHEDULER_INTERNAL_ERROR 0x119 in Windows 11

VIDEO_SCHEDULER_INTERNAL_ERROR, or stop code 0x00000119, means the component of Windows that manages graphics work has detected a fatal violation by the graphics driver. The scheduler is not the thing that broke; it is the thing that refused to carry on.

That distinction matters, because it tells you where to look. This guide explains what the video scheduler does, how to read the one parameter that names the exact violation, and how to repair the graphics stack.

PAGE CONTENT

• What the Video Scheduler Does
• Read Parameter 1 to Identify the Violation
• Fix 1: Clean-Install the Graphics Driver
• Fix 2: Stop Overclocking the Graphics Card
• Fix 3: Rule Out a Hardware Fault
• Fix 4: Remove Conflicting Overlays and Acceleration
• Fix 5: Repair Windows and Update Everything
• FAQs About Stop Code 0x00000119
• Back Up and Restore Windows with Qiling Disk Master

What the Video Scheduler Does

The video scheduler is the part of Windows that decides how work reaches the graphics processor. It owns the command queues, it creates and tracks the fence objects that keep the processor in step with the card, and it arbitrates between the graphics driver and the hardware engines. Almost every frame you see has passed through it.

Because the scheduler holds that position, it can verify what the driver tells it. When a driver reports something the scheduler can prove is impossible, such as a fence identifier that does not exist or a command it claims to have submitted but did not, the scheduler stops the machine rather than let corrupted work continue to the display.

Microsoft describes this stop code as the video scheduler having detected a fatal violation, and that wording points directly at the driver. In practice the triggers are narrow, and they all sit in the graphics stack:

• A graphics driver with a genuine bug in how it reports or submits work
• A driver that is correct for one card but installed on another, or a mixed driver set
• An unstable overclock or undervolt that makes an engine fail to respond
• A failing graphics card, power supply, or overheated component
• Third-party overlay and capture software injecting code into the graphics path

Read Parameter 1 to Identify the Violation

Only the first parameter is useful here, and it names the exact violation. If you open the crash dump, the same value is shown as the bug check argument. The common values are:

• 0x1 — the driver reported an invalid fence identifier
• 0x2 — the driver failed when submitting a command
• 0x3 — the driver failed when patching a command buffer
• 0x4 — the driver reported an invalid flip queue length
• 0x5 — the driver faulted a system or paging command
• 0x6 — the driver reported a null adapter mask on a multi-adapter GPU
• 0x7 — the driver reported VSync on a render-only adapter
• 0x8 — the node causing a reset did not have its corresponding bit set
• 0x9 — the driver failed on a cancel command
• 0xA — the driver reported an invalid, out-of-range aborted fence
• 0xB — the driver failed a SetVidPnSourceAddressWithMultiPlaneOverlay command
• 0xC — the driver's page fault flags indicate a fatal hardware fault
• 0xD — the driver reported incorrect page fault flags in a DMA fault interrupt
• 0xE — the driver reported VSync for a plane index beyond the maximum overlay planes
• 0x10 — an unexpected interrupt arrived after an engine reset

Every one of these describes the same relationship: the driver told the scheduler something that could not be true. That is why the repair path is largely the same whichever value you see, and why the graphics driver is the first thing to replace.

Fix 1: Clean-Install the Graphics Driver

Step 1. Download the current driver from the graphics vendor for your exact model, or from the laptop maker if you are on a notebook, where only the validated build is supported.

Step 2. If updating changes nothing, do a clean install instead. Remove the existing driver with a display driver uninstaller while in Safe Mode, restart, and then install the vendor package on the clean system. This removes leftover filter drivers and settings that a normal update leaves behind.

Step 3. If the crashes started right after a driver update, roll back to the previous version in Device Manager and confirm whether the stop code disappears. A regression is the single most common cause of a sudden change in behaviour.

Step 4. Avoid mixing driver sources. A vendor driver layered over a Windows Update driver, or a third-party updater's build, is a frequent trigger for this stop code.

Fix 2: Stop Overclocking the Graphics Card

Step 1. Reset any graphics overclock, undervolt, or custom fan curve back to default. Utilities that adjust voltage are especially likely to produce the engine reset violations listed as 0x8 and 0x10, because an unstable engine is exactly what makes it fail to answer the scheduler.

Step 2. Disable the memory profile in BIOS or UEFI, whether it is labelled XMP or EXPO, and remove any processor overclock. These settings are outside the official specification and their instability can reach the graphics subsystem through shared memory and power delivery.

Step 3. Test at stock settings for several days, then reintroduce changes one at a time. If the stop code returns when a single setting is enabled, that setting is your answer.

Fix 3: Rule Out a Hardware Fault

Step 1. Monitor the graphics temperature under the workload that crashes. Sustained overheating causes engines to stop responding, which the scheduler reports as a violation.

Step 2. Look for visual artefacts before the crash, such as flickering, coloured lines, or a black flash. Artefacts followed by a stop code are a strong sign of failing memory on the card itself.

Step 3. Confirm the power supply is adequate for the card. If the card uses two power connectors, run separate cables from the power supply rather than daisy-chaining a single cable, since a voltage dip under load mimics a failing component.

Step 4. Reseat the card, clean dust from the cooler, and check that the card is fully seated in its slot. If the machine uses a riser cable, test without it, because an unstable riser produces intermittent faults of exactly this type.

Step 5. If you have integrated graphics, run on them for a few days. If the stop code disappears without the discrete card, the card or its power delivery is implicated.

Fix 4: Remove Conflicting Overlays and Acceleration

Step 1. Close or uninstall overlay software. Game overlays, capture and streaming suites, RGB and monitoring tools, and frame rate counters all inject code into the graphics path and are a recognised source of scheduler violations.

Step 2. Disable hardware acceleration as a test. In a web browser this sits under the system or performance settings; in media players it may be called hardware decoding or video acceleration. Turn it off, restart the app, and retest.

Step 3. Re-enable each item one at a time. If the stop code returns with a single tool switched on, keep that tool disabled or replace it.

Fix 5: Repair Windows and Update Everything

Step 1. Open Command Prompt as administrator and repair the component store, then the protected system files:

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

Step 2. Install all pending Windows updates, then look under the advanced options for optional driver updates and the DirectX and vendor runtime components that some games and media applications require.

Step 3. Update the system firmware and the chipset drivers from the PC or motherboard maker, since these control how the graphics slot and its power are managed.

Step 4. Run a full malware scan. A compromised graphics component is unlikely, but it is worth excluding before you consider replacing hardware.

FAQs About Stop Code 0x00000119

Is this always the graphics driver?

Almost always. The scheduler only stops the machine when the graphics driver reports data it can prove is wrong, so the driver is either the fault or the messenger for an unstable card.

How is this different from VIDEO_TDR_FAILURE?

VIDEO_TDR_FAILURE means the driver failed to respond within the time limit and Windows tried to reset it. This stop code means the driver reported impossible information instead. Both point at the graphics stack, and the repair steps overlap heavily.

It only happens while watching video or playing a game. Why?

Because that is when the affected engine and its command path are under load. The fault exists all the time, but it becomes fatal only when the specific engine is exercised.

Can a monitor or a cable cause it?

Very rarely. A bad cable or monitor normally causes a signal loss, a flicker, or a blank screen rather than a scheduler violation inside the operating system.

Will resetting Windows fix it?

Only if the cause was a corrupted system component. A reset reinstalls the same graphics driver and does nothing about overheating, an unstable overclock, or a failing card, so the stop code usually returns.

How do I confirm the problem is solved?

Run the same workload that used to crash for several days. This stop code is often intermittent, so a single clean session proves very little.

Back Up and Restore Windows with Qiling Disk Master

Fixing a graphics fault means Safe Mode sessions, driver removals, and hardware changes, and any of those can leave a machine that will not start. Create a full system backup before you begin. Qiling Disk Master handles both the backup and the restore.

• Free Download
• Windows 11/10/8/7, 100% Secure

Part 1: Create a Full System Backup

Step 1. Install and open Qiling Disk Master. On the home screen, open "Backup and Recovery" and choose "System Backup". This option automatically includes Windows and the hidden boot partitions, so you do not have to select them one by one.

Step 2. Check the source. The disk where Windows is installed and its system partitions are already ticked for you. If you only need your personal documents, run a separate "File Backup" task instead.

Step 3. Click the destination box and choose where the image should be saved. Use an external HDD or SSD, a NAS, or any drive other than the one Windows is installed on, and make sure it has enough free space.

Step 4. Review the task summary and click "Proceed". Wait until the progress bar reaches 100%. Do not unplug the drive or turn off the PC while the backup is running.

Part 2: Restore Windows from the Backup

Step 1. Open Qiling Disk Master again, go to "Backup and Recovery", and select the recovery option. Your backup images are listed, so pick the one you created before the changes began.

Step 2. Choose the target disk or partition. Normally you restore to the original system disk. If the drive was replaced, select the new disk instead, and the restore rebuilds Windows together with its boot partitions.

Step 3. Preview the restore plan, click "Proceed", and confirm the warning. The PC restarts to finish the job, and Windows comes back exactly as it was on the day the image was created, with your files and programs intact.

Conclusion

VIDEO_SCHEDULER_INTERNAL_ERROR means the Windows video scheduler caught the graphics driver reporting something that could not be true, and stopped the machine instead of letting corrupted work reach the display. Parameter 1 names the exact violation, but the answer is nearly always in the graphics stack. Update or clean-install the graphics driver first, roll it back if the crashes started after an update, then remove any overclock or undervolt. If the fault persists, check temperatures, power delivery, seating, and the card itself, and exclude overlay software and hardware acceleration before you consider replacing hardware.

Protect your PC with Qiling Backup—create a system image before your next troubleshooting step.

Related Articles

• Fix VIDEO_TDR_FAILURE BSOD in Windows 11
  The other half of the same story: the driver stops responding in time instead of reporting impossible data. Read both before you replace a card.
• Screen Freezes but the PC Keeps Running: Causes and Fixes
• Computer Keeps Crashing When Playing Games: How to Fix It
• Blue Screen When Playing Games: Causes and Fixes
  Load-dependent graphics faults show up first in games. This guide walks through the settings and hardware checks in the same order.
• Windows 11 Keeps Crashing? 8 Proven Fixes
• Fix THREAD_STUCK_IN_DEVICE_DRIVER (0xEA) in Windows 11