Timeout Detection and Recovery (TDR) errors in Windows 11/10

Download PC Repair Tool to quickly discover & fix Windows errors automatically

One of the almost common GPU-related errors and crashes are referred to equally Timeout Detection and Recovery or TDR errors in logs, Event Viewers, etc. The most common error message y'all might find when this happens is "Brandish driver stopped responding and has recovered" and a BSOD with the stop code Bug Cheque 0x116: VIDEO_TDR_ERROR.In this article, I'll suggest y'all few methods to troubleshoot such errors.

TDR is nowadays in Windows 11, Windows x, Windows 8.1, Windows seven and Windows Vista. TDR attempts to notice problematic situations and recover to a functional desktop dynamically.

Timeout Detection and Recovery (TDR)

According to MSDN, the TDR processes are:

Timeout detection: The Video Scheduler component of the Windows graphics stack detects that the GPU is taking more than the permitted quantum fourth dimension to execute the particular task and tries to preempt this particular task. The preempt operation has a "wait" timeout—the actual "TDR timeout." This step is thus the "timeout detection" phase of the process. The default timeout period in Windows is ii seconds. If the GPU cannot complete or preempt the current task within the TDR timeout, then the GPU is diagnosed as hung.
Preparation for recovery: The operating system informs the WDDM driver that a timeout has been detected and it must reset the GPU. The driver is told to stop accessing memory and should not access hardware later this time. The operating arrangement and the WDDM commuter collect hardware and other state information that could exist useful for postal service-mortem diagnosis.
Desktop recovery: The operating organization resets the advisable state of the graphics stack. The Video Memory Manager component of the graphics stack purges all allocations from video memory. The WDDM driver resets the GPU hardware state. The graphics stack takes the final actions and restores the desktop to the responsive state. Equally mentioned earlier, some older DirectX applications may now render simply black, and the user may be required to restart these applications. Well-written DirectX 9Ex and DirectX ten applications that handle "Device Remove" go along to work correctly. The application must release so recreate its Microsoft Direct3D device and all of its objects. DirectX awarding programmers tin detect more than data in the Windows SDK.

Display driver stopped responding and has recovered

The most common error message you might find is "Brandish commuter stopped responding and has recovered" – also you lot might also become BSOD with the stop code Bug Bank check 0x116: VIDEO_TDR_ERROR.

In that location are a few things that you could do to fix it.

Check your Memory i.e. RAM. If your RAM is failing on you, information technology's quite possible that this is what is causing your Brandish to crash. Check our commodity on how to run Retention Diagnostic Avant-garde Retentivity Diagnostic with Memtest86+. Also, check if the timing and voltage of the RAM are prepare correctly in your BIOS refer to your Motherboard and RAM transmission.
Overclocking your GPU could cause this problem. So if your Overclocking resets the values to default settings and then exam it and see if that fixes your problem.
Corrupted or Bad display drivers. If your display driver is corrupted at that place is a very good chance information technology might be crashing your brandish. Well-nigh of the time only uninstalling and reinstalling it will not resolve your problem. We have to practise a complete Driver Cleanup. You can use NVIDIA and ATL Cards Driver Cleanup .
The other reason is Overheating. While playing games or working with software that uses GPU, your Display carte du jour might become extremely hot and cause the drivers to crash – and end up crashing the whole organisation. Utilize RivaTuner to determine if your display card is overheating. Try to adjust the fan settings and see if that makes any difference. If not I would recommend taking information technology to a Computer Repair store and having them clean the tower to dominion out any grit-related issue.
The next reason could be insufficient ability or a bad PSU. Your Display card needs enough power to office properly and if it does not get enough ability, then the card will misbehave. Use a Power Supply Calculator and make up one's mind you have enough juice to run the system. If you accept plenty juice to run the system then take information technology to the Computer Repair shop and have them examination it with a different PSU.
For avant-garde users, there are methods to enable debugging in the Windows registry.
If all if these steps failed and so more than likely you have a bad brandish menu. If information technology's still nether warranty send information technology for replacement.

Hope these steps helped y'all in resolving TDR-related errors. If you know whatsoever additional steps practise share them with us.

Shyam aka "Captain Jack" is a Microsoft MVP alumnus and a Windows Enthusiast with an involvement in Advanced Windows troubleshooting. Suggestions made and opinions expressed by him here are his personal i's and not of his current employers. He blogs at captaindbg.com.