BSOD 321 (VIDEO_ENGINE_TIMEOUT_DETECTED): causes and diagnosis

Status / error code:		Category:

Constant name:
Source:		Operating System:
Description: Windows detected a timeout in a GPU video engine rather than a general 3D engine.

Could be also:
Constant	Type	OS
ERROR_DEVICE_UNREACHABLE	Win32 error	Windows

Previous	Next
STORAGE_DEVICE_ABNORMALITY_DETECTED	VIDEO_TDR_APPLICATION_BLOCKED

VIDEO_ENGINE_TIMEOUT_DETECTED

Video engine timeout for VIDEO_ENGINE_TIMEOUT_DETECTED

VIDEO_ENGINE_TIMEOUT_DETECTED is bug check code 0x00000141. This bug check is related to GPU engine scheduling and timeout detection. It differs from generic video memory or scheduler corruption because the timed-out unit is the video engine path, such as decode, encode, or copy/video processing work.

How to read it in a dump for VIDEO_ENGINE_TIMEOUT_DETECTED

Correlate with media playback, video decode/encode, browser hardware acceleration, or GPU compute/video workloads.
The TDR context, GPU scheduler state, and display miniport driver are key evidence.
Driver version and firmware can matter more than the application that submitted work.

What to check for VIDEO_ENGINE_TIMEOUT_DETECTED

Update or roll back GPU/display drivers in a controlled test.
Check whether disabling hardware acceleration changes the failure pattern.
Collect TDR, DXGKRNL, and display miniport information from the dump and event logs.

References for VIDEO_ENGINE_TIMEOUT_DETECTED

Dump evidence for VIDEO_ENGINE_TIMEOUT_DETECTED

For VIDEO_ENGINE_TIMEOUT_DETECTED, preserve the complete dump, the four bug-check parameters, the exact Windows build, loaded-module list, and the event timeline immediately before the stop. AllStat summarizes the condition as “VIDEO_ENGINE_TIMEOUT_DETECTED”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.

Analysis order for VIDEO_ENGINE_TIMEOUT_DETECTED

Run WinDbg !analyze -v, then inspect the documented meaning of each VIDEO_ENGINE_TIMEOUT_DETECTED parameter instead of relying only on the probably-caused-by line.
For VIDEO_ENGINE_TIMEOUT_DETECTED, find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with video / engine / timeout / detected.
For VIDEO_ENGINE_TIMEOUT_DETECTED, keep third-party filter, security, storage, graphics, and virtualization drivers in the module inventory; removing evidence before dump analysis can obscure the responsible path.

Do not repeatedly reboot a machine affected by VIDEO_ENGINE_TIMEOUT_DETECTED before collecting the dump and event logs. For VIDEO_ENGINE_TIMEOUT_DETECTED, recovery actions should follow the component identified by the stack and parameters, not merely the symbolic stop-code name.

Dump evidence for VIDEO_ENGINE_TIMEOUT_DETECTED

Analysis order for VIDEO_ENGINE_TIMEOUT_DETECTED

Run WinDbg !analyze -v, then inspect the documented meaning of each VIDEO_ENGINE_TIMEOUT_DETECTED parameter instead of relying only on the probably-caused-by line.
For VIDEO_ENGINE_TIMEOUT_DETECTED, find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with video / engine / timeout / detected.
For VIDEO_ENGINE_TIMEOUT_DETECTED, keep third-party filter, security, storage, graphics, and virtualization drivers in the module inventory; removing evidence before dump analysis can obscure the responsible path.

Looking for a different code? Search another status or error code.