VIDEO_SCHEDULER_INTERNAL_ERROR

Code: 0x119 (281)

As HRESULT:As NTSTATUS:

Parameters

ParameterDescription
0x1Driver has reported an invalid fence ID. (DRIVER_REPORTED_INVALID_FENCE_ID)
0x2Driver failed upon the submission of a command. (DRIVER_FAILED_SUBMIT_COMMAND)
0x3Driver failed upon patching the command buffer. (DRIVER_FAILED_PATCH_COMMAND)
0x4Driver reported an invalid flip capability. (DRIVER_INVALID_FLIPQUEUE_LENGTH)
0x5Driver failed a system or a paging command. (DRIVER_FAULTED_SYSTEM_COMMAND)
0x6Driver reports NULL PhysicalAdapterMask for interrupt raised on multi-adapter GPU. (DRIVER_INVALID_ADAPTER_MASK)
0x7Driver reports display VSync on render only adapter. (REPORT_VSYNC_ON_RENDER_ONLY_ADAPTER)
0x8Driver node that is causing the reset did not have its corresponding bit set. (INVALID_NODE_MASK)
0x9Driver failed on a cancel command. (FAILED_CANCEL_COMMAND)
0xADriver reported an invalid out of range aborted fence. (REPORTED_INVALID_ABORTED_FENCE)
0xBDriver failed the SetVidPnSourceAddressWithMultiPlaneOverlay command. (FAILED_SETVIDPNSOURCEMPO_COMMAND)
0xCDriver PageFaultFlags indicate a fatal hardware fault. (FATAL_PAGE_FAULT)
0xDDriver reported incorrect PageFaultFlags in DMA Page Faulted interrupt. (INVALID_DMA_FAULT_PARAMETERS)
0xEDriver reported VSync for a plane index larger than max overlay planes on GPU. (REPORT_VSYNC_PLANE_OUT_OF_RANGE)
0xFNot used. (FAILED_POSTMPOPRESENT_COMMAND)
0x10Driver reported an unexpected interrupt after engine reset and before OS resumed engine. (UNEXPECTED_INTERRUPT_AFTER_RESET)
0x11Driver reports a suspend context completed fence value which OS has not generated yet. (INCORRECT_SUSPEND_FENCE)
0x12Driver failed to update a native fence monitored value. (FAILED_UPDATE_MONITORED_VALUE)
0x13Driver failed to update the native fence current value. (FAILED_UPDATE_CURRENT_VALUE)
0x400This is an internal OS state error, typically caused by a memory corruption or bad hardware.
0xE00The OS ran out of memory for pre-allocated packets to handle passive flip requests.
0x1000This is an internal OS state error, typically caused by a memory corruption or bad hardware.
0xA000This is an internal OS state error, typically caused by a memory corruption or bad hardware.
0x10000This is an internal OS state error, typically caused by a memory corruption or bad hardware.

Description

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

Important

This article is for programmers. If you're a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.

Resolution

The !analyze debug extension displays information about the bug check and can be helpful in determining the root cause.

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.

See also

Article text from the Windows driver documentation (opens in a new tab), by Microsoft, under the CC BY 4.0 (opens in a new tab) licence.

Associated Modules

ModuleCodeFound inDescription
EventCreate.exe0x11978.11011%1
mispace.dll0x1191011Windows could not determine the file system of volume %1.
ntdll.dll0x11978.11011The device has succeeded a query-stop and its resource requirements have changed.
storagewmi.dll0x1198.11011Windows could not determine the file system of volume %1.
webservices.dll0x11978.11011The characters '%1' cannot be parsed as a bool ('true', 'false', '1', or '0').
5 entries