- Software and digital services
- Operating system
VIDEO_SCHEDULER_INTERNAL_ERROR
Windows VIDEO_SCHEDULER_INTERNAL_ERROR on PC: video fault
Risk level
Medium
Proceed carefully and stop if the check is unclear.
Urgency
High
Quick answer
Stop code 0x00000119 means the Windows video scheduler detected a fatal violation in graphics scheduling or GPU operations. Start by checking for an updated video driver from the vendor and inspecting Device Manager for flagged devices.
Safety first
Stop and check this first
- Before any BIOS update or graphics/motherboard hardware change, verify that you have your 48-digit BitLocker recovery key at https://aka.ms/myrecoverykey, in your work/school account (https://aka.ms/aadrecoverykey), or on a saved printout or USB drive.
Safe checks you can perform
- Update or roll back the video driver
- Disconnect new display hardware and test in Safe Mode
- Install Windows updates and keep 10% to 15% free disk space
- Run hardware and memory diagnostic tests
Leave these tasks to a qualified professional
- Do not attempt this professional task: WinDbg !analyze -v inspection of Parameter 1 and the video module
- Do not attempt this professional task: GPU, RAM, and BIOS/firmware verification by a service provider
What a technician must be able to justify
Technician visit
These are the steps they must carry out and show you. Tick them as they work: if steps are skipped, do not accept a part swap.
These are not instructions for opening or handling the equipment yourself. They are the checks that should support a technical conclusion.
WinDbg !analyze -v inspection of Parameter 1 and the video module
What they doA technician opens the crash dump in WinDbg, runs !analyze -v to see if the faulting module is a video driver, and checks Parameter 1 (such as 0x1, 0x2, 0x5, 0xC, or 0xE00) to identify the exact violation.
They must show youthe !analyze -v output naming the faulting module and the hex value of Parameter 1.
In writingthe exact Parameter 1 code, the video driver module named, and the vendor driver version installed.
GPU, RAM, and BIOS/firmware verification by a service provider
What they doWhen Parameter 1 equals 0xC (FATAL_PAGE_FAULT) or 0x400, 0x1000, 0xA000, and 0x10000, or when updated video drivers do not stop the crash, the technician updates BIOS/firmware and tests the graphics hardware and system memory.
They must show youthe hardware and memory diagnostic results along with the installed BIOS/firmware version.
In writingwhether RAM or GPU hardware faulted and what repair or warranty replacement was performed.
Before accepting a part or repair
Nothing has been shown yet. Do not accept a part swap based on the code alone.
Follow these steps
Note: Follow the documented order. An error code identifies the affected system, but it does not prove by itself which part has failed.
Update or roll back the video driver
- Who:
- you, from your normal desktop or from Safe Mode if crashes happen quickly.
- How:
- right-click Start and open Device Manager to check whether the display adapter has an exclamation point (!), then install the latest video driver from the GPU or PC vendor; if crashes began right after a driver update, roll back the driver to the previous version.
- Result that matters:
- fixing video scheduler violations caused by a buggy or mismatched graphics driver.
- If updating or rolling back the video driver stops bug check 0x119, keep that working driver version.
- If updating does not help, try disabling or uninstalling the flagged device in Device Manager or test in Safe Mode.
- Evidence to keep:
- video driver version and release date before and after the change.
Evidence: Stop code error or bug check troubleshooting (IT professionals) · Troubleshooting Windows unexpected restarts and stop code errors · Bug Check 0x119 VIDEO_SCHEDULER_INTERNAL_ERROR
Disconnect new display hardware and test in Safe Mode
- Who:
- you, after shutting down the PC.
- How:
- if you connected a new monitor, dock, adapter, or other hardware before the error, shut down the PC, remove it, and restart; if Windows struggles to stay running, start your PC in Safe Mode to complete the remaining checks.
- Result that matters:
- determining whether newly attached hardware or a third-party startup driver triggers the stop.
- If the PC stays stable without the new hardware or while in Safe Mode, check with the accessory vendor for compatible drivers.
- If restarts continue without extra hardware, proceed to Windows Update and disk space checks.
- Evidence to keep:
- list of hardware removed and whether the system crashed in Safe Mode.
Evidence: Troubleshooting Windows unexpected restarts and stop code errors
Install Windows updates and keep 10% to 15% free disk space
- Who:
- you, with the PC connected to power.
- How:
- go to Start, Settings, Windows Update and select Check for updates; also verify that the system drive has 10% to 15% free space available so Windows can create swap files and perform paging functions.
- Result that matters:
- ensuring current OS graphics fixes are installed and paging resources are not starved.
- If installing updates and freeing disk space resolves the 0x00000119 restarts, monitor normal use.
- If updates and disk space were already fine, run hardware and memory diagnostics next.
- Evidence to keep:
- Windows Update history screenshot and free disk space percentage.
Evidence: Stop code error or bug check troubleshooting (IT professionals) · Troubleshooting Windows unexpected restarts and stop code errors
Run hardware and memory diagnostic tests
- Who:
- you, with all open files saved.
- How:
- run your system's hardware and memory tests to check for RAM or GPU errors that could trigger Parameter 1 values 0xC, 0x400, 0x1000, 0xA000, or 0x10000.
- Result that matters:
- getting an objective test result for physical memory and graphics hardware.
- If any memory or hardware test fails, save the report and contact the PC or GPU manufacturer for service.
- If all tests pass, provide the MEMORY.DMP file to a technician for WinDbg analysis.
- Evidence to keep:
- diagnostic test log or screenshot with the date and result.
Evidence: Stop code error or bug check troubleshooting (IT professionals) · Bug Check 0x119 VIDEO_SCHEDULER_INTERNAL_ERROR
Still not solved
If the error persists, stop here. See what the technician must do and show you.
Where this code applies
A code is meaningful only inside the right product and version context.
Primary scope
- System
- Software and digital services
- Brand
- Microsoft Windows
- Product type
- Operating system
Known code variants
- 0x00000119
- 0x119
- bug check 0x119
- STOP 0x00000119
- stop code VIDEO_SCHEDULER_INTERNAL_ERROR
- VIDEO SCHEDULER INTERNAL ERROR
What it means
Microsoft defines bug check 0x00000119 (VIDEO_SCHEDULER_INTERNAL_ERROR) as a fatal violation detected by the video scheduler. Parameter 1 is the only parameter of interest and pinpoints the exact violation: examples include an invalid fence ID (0x1), a driver failure when submitting or patching a command buffer (0x2 and 0x3) or a system/paging command (0x5), PageFaultFlags indicating a fatal hardware fault (0xC), running out of memory for pre-allocated passive flip packets (0xE00), or an internal OS state error from memory corruption or bad hardware (0x400, 0x1000, 0xA000, and 0x10000). Seeing this code alone never proves that your graphics card or RAM is broken.
Warnings and stop conditions
- Highsource verified
Before any BIOS update or graphics/motherboard hardware change, verify that you have your 48-digit BitLocker recovery key at https://aka.ms/myrecoverykey, in your work/school account (https://aka.ms/aadrecoverykey), or on a saved printout or USB drive.
Evidence: Find your BitLocker recovery key
Symptoms and causes
Probable causes · in order
- Video driver failing on command buffers, fences, or resetsCommon
Microsoft's Parameter 1 table attributes values 0x1 through 0x13 to video driver errors involving invalid fence IDs, failed command submissions, multi-plane overlays, or unexpected interrupts after engine reset.
Evidence: Bug Check 0x119 VIDEO_SCHEDULER_INTERNAL_ERROR
- Memory corruption, exhausted flip packets, or hardware faultPossible
Parameter 1 value 0xC indicates a fatal hardware page fault, 0xE00 means the OS ran out of memory for passive flip request packets, and 0x400, 0x1000, 0xA000, or 0x10000 typically stem from memory corruption or bad hardware.
Evidence: Bug Check 0x119 VIDEO_SCHEDULER_INTERNAL_ERROR
- Pending Windows updates, low disk space, or new hardwarePossible
Microsoft Support advises removing newly added hardware, installing the latest Windows updates, and keeping 10% to 15% free disk space for swap files and system functions.
Evidence: Stop code error or bug check troubleshooting (IT professionals) · Troubleshooting Windows unexpected restarts and stop code errors
Virtual technician
Does VIDEO_SCHEDULER_INTERNAL_ERROR still appear after these checks?
Answer a few questions to narrow down the likely cause and the safest next action. Guidance only - it never replaces a professional.
Sources and technical references
- 1
Stop code error or bug check troubleshooting (IT professionals)
Microsoft · 2026 · official_doc
- 2
Troubleshooting Windows unexpected restarts and stop code errors
Microsoft · 2026 · official_doc
- 3
Solución de problemas de reinicios inesperados y errores de código de detención de Windows
Microsoft · 2026 · official_doc
- 4
Find your BitLocker recovery key
Microsoft · 2026 · official_doc
- 5
Buscar la clave de recuperación de BitLocker
Microsoft · 2026 · official_doc
- 6
Resolución avanzada de problemas para errores de código de parada
Microsoft · 2026 · official_doc
- 7
Bug Check 0x119 VIDEO_SCHEDULER_INTERNAL_ERROR
Microsoft · 2026 · official_doc
- 8
Comprobación de errores 0x119 VIDEO_SCHEDULER_INTERNAL_ERROR
Microsoft · 2026 · official_doc
Was this entry useful?