| Previous | Next |
| DXGI_ERROR_DEVICE_REMOVED | DXGI_ERROR_DEVICE_RESET |
DXGI_ERROR_DEVICE_HUNG
DXGI_ERROR_DEVICE_HUNG reports that the graphics device stopped responding after badly formed commands were sent. Microsoft classifies this as a design-time issue: the application should investigate and correct the command stream rather than treat it as a normal retryable rendering delay.
How to investigate
- Retrieve the device-removed reason before destroying the device and retain the failing frame or command-list boundary.
- Enable the Direct3D debug layer and, where applicable, GPU-based validation or DRED in a development build.
- Reduce the workload to the last successful draw or dispatch, then validate resource states, descriptor lifetime, synchronization, and shader inputs.
Recovery is still necessary
The affected device is unusable and must be recreated, but recovery should not replace root-cause analysis. A repeatable DXGI_ERROR_DEVICE_HUNG strongly points to invalid application GPU work rather than a network or windowing failure.
Microsoft: DXGI error codes · Microsoft: D3D12 debug layer and DRED
Looking for a different code? Search another status or error code.