I have had this problem on several different PCs with both NVIDIA and AMD cards.
A Post on geforceForums about TDR problems obtains lots of information and often could help me out: forums.geforce.com - Troubleshooting TDR problems
(Sorry for Link to External site / forum
) here the essential Information:
Common issues that can cause a TDR:
Examples of specific TDR causes:
- Incorrect memory timings or voltages
- Insufficient/problematic PSU
- Corrupt driver install
- Unstable overclocks (GPU or CPU)
- Incorrect MB voltages (generally NB/SB)
- Faulty graphics card
- A badly written driver or piece of software, but this is an unlikely cause in most cases
- Driver conflicts
- Another possibility that people tend not to like to hear, is that you are simply asking too much of your graphics card. What I mean by this, is that if you have your settings too high and the graphics card struggles and falls to very low FPS, then something graphically complex occurs, the GPU may not be able to respond and a TDR error may occur
- Some users have experienced TDR errors whilst browsing the web with the 280.xx, 285.xx and 290.xx drivers. Please head to this link to clarify if this is relevant to you - this is quite a specific issue which seems to predominantly affect web browsing as opposed to gaming. There are no categoric fixes but some users have found that changing the power management mode to 'Prefer Maximum Performance' has helped.
Things to check or consider initially in your troubleshooting:
- Conflict with Realtek drivers causing TDR errors
- Driver conflict with Logitech webcam drivers
- Unstable overclock on the graphics card
- Insufficient PSU
- RAM problems (faulty, badly seated or not configured correctly)
- Cleaning out dust resolved issue
- AMD/ATI cards also have TDR problems
- Check for newer driver version or cleanly uninstall/re-install your drivers. Great description of how to do this here (full credit to DJNOOB for this).
- If you have multiple 'GPU tools' like EVGA Precision and MSI Afterburner installed, consider that it is only advisable to have one tool such as this at any one time.
- If the issue is only with a specific game, check for patches.
- If this is a new problem for you, have you just added any new hardware or updated/installed any new drivers? Consider rolling them back.
- Check temperatures. Its important you check these at load, which is generally when a TDR event will occur. Everest Ultimate Edition is a good tool for this, or OCCT's GPU stress test. If things are too hot, you can use tools such as EVGA Precision to increase GPU fan speeds on graphics cards. Cleaning your system of dust can help temperatures significantly. Common sense will normally tell you if something is too hot, but if you aren't sure, the information is generally available online.
- Check that your RAM is running at the correct settings as defined by the manufacturer.
- Remove any overclocks on your system and test with stock clocks. This includes memory, CPU and GPU (even factory OC'd cards). Best to try each separately so you can be sure if one solves the issue.
- Attempt a CMOS reset to return all BIOS settings to default. This is a good hardware troubleshooting step as it also resets the IRQ assignments - you can normally reset the CMOS either through a jumper on the motherboard (see manual), or by disconnecting the mains power and taking out the motherboard battery for 5 minutes. You will likely need to go in to the BIOS after this reset to check the memory timings/voltages are correct, as these will not always do so automatically.
- Run memtest (memtest.org). This should complete with NO errors.
- If you have just installed a new graphics card, check your PSU ratings. Is it providing enough power, and most importantly enough Amps on the 12V rail.
- If you are using SLI, try each card separately to see if the fault lies with one.
- Try graphics card/cards in another computer if you can.
Some of this you already have tried out, other steps might become useful to you.
As side note: While running A VM with VMware Player this error also occured once - only solution which worked, was disabling 3D visualization. Sorry for the long post
, but I hope you can filter something useful out of it.