Showing results for 
Search instead for 
Did you mean: 

Drivers & Software

Esteemed Contributor III

Graphics driver stopped responding and has recovered....TDR fix

 This issue has a workaround that 'fixes' the problem for most users..

The issue is Microsofts default TDR setting. Basically (simplified) Microsoft has determined that a program which hasn't responded in a given time should be restarted.

TDR stands for Timeout Detection and Recovery. This is a feature of the Windows operating system which detects response problems from a graphics card, and recovers to a functional desktop by resetting the card. If the operating system does not receive a response from a graphics card within a certain amount of time (default is 2 seconds), the operating system resets the graphics card.

Increasing the default TDR setting to 8 seconds gives the graphics card longer to complete its task. How to do that:

Open registry > regedit >  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers. In the box to the right you may or may not see  TdrDelay with a data value of (2). If you see that, double click and change the value from (2) to (8). If you don't see TdrDelay...right click on a open space and create a new Dword and name it TdrDelay . Double click that and set a value of 8. I do not recommend using a 'tool' to reset this value.

Note: The computer must be rebooted after making this change.

Microsoft's explanation and automatic "Fixit" program:

"Display driver stopped responding and has

recovered" error in Windows 7 or Windows Vista

Message was edited by: pat densman

69 Replies
Adept I
Adept I

Re: TDR = Display driver stopped responding and has recovered

Tried this for my problem, didn't work. (It does say for some users, though, so it might work for you, just not for me. :-D)

Esteemed Contributor III

Re: TDR = Display driver stopped responding and has recovered

The 'fix' outlined above does eliminate the most common cause of the TDR error. But there are other circumstances that will cause the error as well. Overclocking, excessive/multiple programs running, and others can result in the same issue. Microsoft furnishes a guide to determining the cause on individual computers. Some parts of it are very technical and users may not feel confident in trying to diagnose.

From the Microsoft article:

The following hardware issues can cause a TDR event:

1. Unstable overclock (CPU, GPU, etc). Revert all and any overclocks to stock settings.

2. Bad sector in memory resulting in corrupt data being communicated between the GPU and the system (video memory otherwise known as VRAM or physical memory otherwise known as RAM).

GPU testing: Furmark, run for ~15 minutes and watch temperatures to ensure there's no overheating and watch for artifacts.

RAM testing: Memtest - Refer to the below:



Download Memtest86+ here:

Which should I download?

You can either download the pre-compiled ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).

How Memtest works:

Memtest86 writes a series of test patterns to most memory addresses, reads back the data written, and compares it for errors.

The default pass does 9 different tests, varying in access patterns and test data. A tenth test, bit fade, is selectable from the menu. It writes all memory with zeroes, then sleeps for 90 minutes before checking to see if bits have changed (perhaps because of refresh problems). This is repeated with all ones for a total time of 3 hours per pass.

Many chipsets can report RAM speeds and timings via SPD (Serial Presence Detect) or EPP (Enhanced Performance Profiles), and some even support changing the expected memory speed. If the expected memory speed is overclocked, Memtest86 can test that memory performance is error-free with these faster settings.

Some hardware is able to report the "PAT status" (PAT: enabled or PAT: disabled). This is a reference to Intel Performance acceleration technology; there may be BIOS settings which affect this aspect of memory timing.

This information, if available to the program, can be displayed via a menu option.

Any other questions, they can most likely be answered by reading this great guide here:

3. Corrupt hard drive or Windows install / OS install resulting in corruption to the registry or page file.

HDD diagnostics: Seatools - Refer to the below:

You can run it via Windows or DOS. Do note that the only difference is simply the environment you're running it in. In Windows, if you are having what you believe to be device driver related issues that may cause conflicts or false positive, it may be a wise decision to choose the most minimal testing environment (DOS).

Run all tests EXCEPT: Fix All, Long Generic, and anything Advanced.

To reset your page file, follow the instructions below:

a ) Go to Start...Run...and type in "sysdm.cpl" (without the quotes) and press Enter.

- Then click on the Advanced tab,

- Then on the Performance Settings Button,

- Then on the next Advanced tab,

- Then on the Virtual Memory Change button.

b ) In this window, note down the current settings for your pagefile (so you can restore them later on).

-Then click on the "No paging file" radio button, and

- then on the "Set" button. Be sure, if you have multiple hard drives, that you ensure that the paging file is set to 0 on all of them.

-Click OK to exit the dialogs.

c ) Reboot (this will remove the pagefile from your system)

d ) Then go back in following the directions in step a ) and re-enter the settings that you wrote down in step

b ). Follow the steps all the way through (and including) the reboot.

e ) Once you've rebooted this second time, go back in and check to make sure that the settings are as they're supposed to be.

Run System File Checker:


Go to Start and type in "cmd.exe" (without the quotes)

At the top of the search box, right click on the cmd.exe and select "Run as adminstrator"

In the black window that opens, type "SFC.EXE /SCANNOW" (without the quotes) and press Enter.

Let the program run and post back what it says when it's done. 

- Overheating of the CPU or GPU and or other components can cause 0x116 bugchecks. Monitor your temperatures and ensure the system is cooled adequately.

- GPU failure. Whether it's heat, power issue (PSU issue), failing VRAM, etc.

The following software issues can cause a TDR event:

- Incompatible drivers of any sort

- Messy / corrupt registry

- Corrupt Direct X -

- Corrupt system files (run System File Checker as advised above)

- Buggy and or corrupt 3rd party drivers. If you suspect a 3rd party driver being the issue, enable Driver Verifier:

Driver Verifier:

What is Driver Verifier?

Driver Verifier is included in Windows 8, 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008, Windows 2000, Windows XP, and Windows Server 2003 to promote stability and reliability; you can use this tool to troubleshoot driver issues. Windows kernel-mode components can cause system corruption or system failures as a result of an improperly written driver, such as an earlier version of a Windows Driver Model (WDM) driver.

Essentially, if there's a 3rd party driver believed to be at issue, enabling Driver Verifier will help flush out the rogue driver if it detects a violation.

Before enabling Driver Verifier, it is recommended to create a System Restore Point:

Vista - START | type rstrui - create a restore point

Windows 7 - START | type create | select "Create a Restore Point"

Windows 8 -

How to enable Driver Verifier:

Start > type "verifier" without the quotes > Select the following options -

1. Select - "Create custom settings (for code developers)"

2. Select - "Select individual settings from a full list"

3. Check the following boxes -

- Special Pool

- Pool Tracking

- Force IRQL Checking

- Deadlock Detection

- Security Checks (Windows 7 & 8)

- DDI compliance checking (Windows 8)

- Miscellaneous Checks

4. Select  - "Select driver names from a list"

5. Click on the "Provider" tab. This will sort all of the drivers by the provider.

6. Check EVERY box that is NOT provided by Microsoft / Microsoft Corporation.

7. Click on Finish.

8. Restart.

Important information regarding Driver Verifier:

- If Driver Verifier finds a violation, the system will BSOD.

- After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will flag it, and as stated above, that will cause / force a BSOD.

If this happens, do not panic, do the following:

- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.

- Once in Safe Mode - Start > type "system restore" without the quotes.

- Choose the restore point you created earlier.

If you did not set up a restore point, do not worry, you can still disable Driver Verifier to get back into normal Windows:

- Start > Search > type "cmd" without the quotes.

- To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.

・    Restart and boot into normal Windows.

How long should I keep Driver Verifier enabled for?

It varies, many experts and analysts have different recommendations. Personally, I recommend keeping it enabled for at least 24 hours. If you don't BSOD by then, disable Driver Verifier.

My system BSOD'd, where can I find the crash dumps?

They will be located in %systemroot%\Minidump

Any other questions can most likely be answered by this article:

Adept I
Adept I

Re: TDR = Display driver stopped responding and has recovered

You asked me to post the SFC results. It stated it found corrupt files but couldn't fix them. Did you want the log as well?

0 Kudos
Esteemed Contributor III

Re: TDR = Display driver stopped responding and has recovered

Well, actually it's not me that asked that. The above is a copy and paste of a MSDN article dealing with this issue. I always have files that are corrupt, but when you look at them (they are the last items in that log) they are for things I deleted like sample pictures, etc. The other errors that were found were fixed. So if you have set the TDR to 8 and fixed all your corrupted files, then see what happens.

Journeyman III
Journeyman III

Re: TDR = Display driver stopped responding and has recovered

Few days ago, I bought a new pc.

Config: i5 4590 3.3 Ghz, Sapphire R9 270 GDDR5, Ram - 8GB DDR3 1600 Mhz, Asus B85M-G, Dell S2240L, OS - Windows 8.1 64bit

Whenever I open km player my screen go black, its  it's freezes for 3-4 seconds! Then a notification popup from the toolbar "Display Driver Stopped Responding and has Recovered"

First I thought that its a problem of km player so I uninstalled it. Then started to  use Windows Media Player! I thought problem is gone!

But still there was a problem. When I saw video on youtube, sometime the display driver crashes happen! Few days ago my screen gone to blue screen and I re setup my windows! But problem is still there!

I don't get crushes while playing game. But while watching video I get this annoying crashed.

SO  what is the problem and what is the solution ?

0 Kudos
Esteemed Contributor III

Re: TDR = Display driver  stopped responding and has recovered

Try disabling hardware acceleration. In IE go to > tools> internet options>advanced> and choose software rendering. Firefox has the same setting under the 'general' tab and chrome has a like setting.

0 Kudos
Adept I
Adept I

Re: Graphics driver stopped responding and has recovered

I started having this problem after installing the latest Windows 10 Pro (64-bit) update. It was that major update to OS, which was a couple of days ago. I had problems earlier with atikmdag.sys -file, which caused BSOD when doing something GPU-heavy. Fixed that according to atikmdag.sys BSOD fixed, now what..?

After updating my OS, it started to throw this same message, "Graphics driver has stopped responding and has been succesfuly recovered" and screen went black for a second.

Drivers were installed according to screen while installing the update to OS.

I searched for a fix, and found many forums and YouTube-videos saying I could fix it by making a registry entry.

This is what I did:

[1] Open registry editor.

[2] Go to "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers"

[3] Make new entry called REG_QWORD (64-bit) if you have 64-bit OS, which I have.

[4] Edit that entry, type TdrDelay, and put value to 8 (hexadecimal)

After doing that, the problem is fixed. Haven't had single error since.

Now some instructions say I should make that entry as a REG_DWORD (32-bit) irregarding what type of OS you have. This post says I should make it as a DWORD.

- Should I change it to DWORD? I don't want to change it because it works perfectly at the moment.

- What that actually does? I don't really know anything about how registry works, I was just following instructions.

- What's the difference between QWORD and DWORD entries? In my current don't need to explain how the whole registry works.

- Should I make both these entries there? Or just the one? I currently have a REG_QWORD TdrDelay 0x00000008 (8)

My system:

Windows 10 Pro (64-bit)

AMD A8-7100 Radeon R5

AMD Radeon R7 M265

Thanks for reading this thru.

Esteemed Contributor III

Re: Graphics driver stopped responding and has recovered

I think I know the article you are referring to (QWORD for 64bit). It was confusing to me when I posted this (2-3 years ago).

Running on 64bit processors does not mean that you have to store all registry values as 64bit. Whether you store the TDR value as a DWORD or a QWORD makes no difference. It is backward compatible. Microsoft has a single program that reads the rather than confusing the issue with a 'either/or' entry, I simplified it by using a DWORD which works for both 64bit or 32bit processors. You can leave your registry entry as is.

Adept I
Adept I

Re: Graphics driver stopped responding and has recovered

Thank you so much for very quick and comprehensive answer.

Because this fixed my problem, does this mean the problem was with GPU timeout or something like that?

0 Kudos