Skip to content
0x00000119VIDEO_SCHEDULER_INTERNAL_ERRORStop codeWidely reported

VIDEO_SCHEDULER_INTERNAL_ERROR (0x119): what it means and how to fix it

Updated Nov 4, 2026 · Checked against Microsoft documentation · How this page is made

Quick answer

This error occurs when the Windows video scheduler detects a fatal issue with your graphics driver or hardware. It is most commonly caused by outdated or corrupted display drivers. Updating your graphics driver is the first step to resolve the problem.

What it means

The VIDEO_SCHEDULER_INTERNAL_ERROR (0x119) is a message from Windows indicating that the component responsible for managing your graphics tasks has encountered a critical failure. Your computer uses a video scheduler to organize commands sent to your graphics card (GPU). When this process fails, the operating system stops to prevent further damage or data loss, resulting in a blue screen. ### Why this happens The video scheduler relies on your graphics driver to communicate correctly with the hardware. If the driver sends invalid data, fails to complete a command, or reports an incorrect status, the scheduler cannot proceed. While this is often a software issue related to the driver, it can also point to physical hardware problems, such as memory corruption or a failing graphics card. The error code includes specific parameters that identify exactly which part of the communication failed, such as a driver reporting an invalid fence ID or a failure during a command submission. These details are primarily used by developers to pinpoint the exact source of the crash.

Common causes

  • Outdated or corrupted graphics card drivers.
  • Hardware instability caused by overclocking.
  • Physical failure or overheating of the graphics card.
  • System memory (RAM) corruption.
  • Insufficient power supply to the graphics hardware.

How to fix it

Safest and most likely fixes first. Readers' answers to "Did this fix it?" reorder this list over time.

  1. Update your graphics driver

    This is the most effective fix if the error is caused by a software conflict or outdated driver.

    1. Visit the official website of your graphics card manufacturer (such as NVIDIA, AMD, or Intel).
    2. Download the latest driver specifically for your hardware model.
    3. Run the installer and follow the on-screen prompts to update your current driver.
    Did this fix it?
  2. Disable overclocking

    Use this if you have manually adjusted your hardware settings to run faster than factory specifications.

    1. Enter your computer BIOS or use the software provided by your hardware manufacturer.
    2. Reset your CPU, GPU, and RAM settings to their default or factory values.
    3. Save the changes and restart your computer.
    Did this fix it?
  3. Check for overheating

    Use this if your computer crashes during intense tasks like gaming or video rendering.

    1. Ensure all computer fans are spinning and free of dust.
    2. Check that your computer case has adequate airflow.
    3. Monitor your hardware temperatures using reliable diagnostic software.
    Did this fix it?
  4. Run a memory test

    Use this if you suspect your physical RAM might be failing.

    1. Type Windows Memory Diagnostic into the search bar and select the application.
    2. Choose the option to restart now and check for problems.
    3. Allow the computer to reboot and complete the diagnostic scan.
    Did this fix it?

Is it just you?

25+ Microsoft Q&A threads discuss this. Most recent activity:

Checked Nov 1, 2026. Refreshed automatically every few days.

Sources

Frequently asked questions

Is my graphics card broken?

Not necessarily. While it can indicate hardware failure, it is much more frequently caused by a driver issue that can be fixed with an update.

Can I fix this by reinstalling Windows?

Reinstalling Windows is rarely necessary. Try updating your drivers and checking your hardware settings first.

Why does this only happen when I play games?

Gaming places a high demand on your graphics card. If the driver or hardware is unstable, the increased workload is more likely to trigger the scheduler error.