| Previous | Next |
| STATUS_VDM_DISALLOWED | STATUS_INSUFFICIENT_RESOURCE_FOR_SPECIFIED_SHARED_SECTION_SIZE |
STATUS_HUNG_DISPLAY_DRIVER_THREAD
This belongs to the WDDM timeout-detection path
STATUS_HUNG_DISPLAY_DRIVER_THREAD is tied to a nonresponsive display-driver path. In WDDM, Timeout Detection and Recovery (TDR) monitors GPU execution and attempts to recover when work takes too long. Windows can reset the graphics stack so the desktop continues instead of immediately forcing a system restart.
The useful distinction is between a transient recovered timeout and a repeating hang caused by the same workload, driver path or hardware condition. TDR documentation describes a default timeout-detection period and a recovery sequence involving the graphics scheduler and display miniport driver. The status name does not identify whether the root cause is shader workload, command submission, firmware, power, memory or a driver synchronization defect.
Collect before changing TDR settings
- Display adapter and complete driver package versions, including user-mode and kernel-mode components.
- The application or GPU workload active at the first timeout and whether the same operation reproduces it.
- Display/TDR events, crash dumps and any vendor GPU fault information from the same incident.
- Evidence of repeated recoveries; Windows can escalate after multiple GPU hangs within a time window.
Microsoft documents TDR registry keys primarily for driver development and testing. Increasing a timeout can hide a slow or deadlocked path and should not replace diagnosis of the operation that stopped making progress.
References
- Microsoft: WDDM timeout detection and recovery
- Microsoft: TDR registry keys for testing and debugging
- Microsoft: Thread synchronization and TDR
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.