Fix for "Display driver stopped responding" Crash to Desktop

[Zurar]

So I'd been running into this crash completely at random. Most commonly, this would happen the first time I load the game for the day, and then loading after that went fine.

The reason this crash is happening can be due to a couple reasons, but the most likely one is that your settings are set to a slightly higher value than they should be since the game has not been fully optimized, yet. The graphics card is thus overwhelmed by things to load, and the Operating System thinks it has frozen and resets it when really it's just playing catch-up.

If you're like me, you don't mind running the game at as little as 20 FPS as long as the game looks good and the framerate doesn't drop below that, but using settings that result in this may cause the crash when first loading the game. Here's the fix:

Disclaimer: This fix requires a change to the system registry. I am not responsible for people that break their OS because they didn't follow the directions properly or have other issues that cause this fix to not work properly. Use at your own risk!

You can read up some more about this on Microsoft's support site, here: https://support.microsoft.com/en-us/kb/2665946

Note: The above site also provides a "fixitforme" option that should do the scary parts for you.

For those that prefer to edit their registry themselves, here are the directions:

1) Open Regedit
2) Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers
3) Add a new DWord/QWord (32-bit/64-bit) key (if one doesn't already exist with the below name)
Name/Value: TdrDelay
Data value: 3 (or greater, the default is 2)
4) Close regedit and restart you computer

What is this doing? This is changing the timeout delay from the default value of 2 seconds to however many seconds you entered as the data value (recommend not exceeding 10 seconds). This allows your GPU more time to catch up on what it's processing before Windows decides to restart the driver, crashing the game in the process. This will, however, make your screen appear to be frozen for up to however many seconds you entered or until the GPU catches up. If it does not catch up within the delay time, the driver restarts and you crash to desktop.

If your GPU is unable to catch up after 10 seconds, I highly recommend you scan your system for viruses and malware and/or upgrade the hardware or lower game settings.

Hope this helps reduce the number of CTDs everyone gets!

[Vires]

I would like to add that that very support link you posted from microsoft does indeed say to use the QWORD 64bit key for 64 bit operating systems. Not trying to step on anyone's toes here though.

[indig0F10w]

引用自 Vires：

I would like to add that that very support link you posted from microsoft does indeed say to use the QWORD 64bit key for 64 bit operating systems. Not trying to step on anyone's toes here though.

Trying this right now, I made a QWORD with value 3, restarted, disabled overlay in Steam and Raptr. So far so good, no crash.

[Zurar]

引用自 Vires：

I would like to add that that very support link you posted from microsoft does indeed say to use the QWORD 64bit key for 64 bit operating systems. Not trying to step on anyone's toes here though.

Hmm, I don't recall seeing the 2 different versions when I did it on mine the first time, so I may have referenced a slightly different article, orginally. It shouldn't really matter which one you use as long as it's named correctly with the correct value.

The 32-bit DWORD works perfectly fine on my end and I've had several instances where it would have otherwise crashed with the default value due to background programs. That said, it wouldn't hurt to use the one suggested for your OS. I've edited the original post to reflect this. Thank you for pointing that out.

[indig0F10w]

引用自 indig0F10w：

引用自 Vires：

I would like to add that that very support link you posted from microsoft does indeed say to use the QWORD 64bit key for 64 bit operating systems. Not trying to step on anyone's toes here though.

Trying this right now, I made a QWORD with value 3, restarted, disabled overlay in Steam and Raptr. So far so good, no crash.

Doesn't work, I will try setting the value to 5.

[Rugged]

引用自 indig0F10w：

引用自 indig0F10w：

Trying this right now, I made a QWORD with value 3, restarted, disabled overlay in Steam and Raptr. So far so good, no crash.

Doesn't work, I will try setting the value to 5.

Hey i know this thread has been dead for a while, but did you end up finding a solution?

[indig0F10w]

TL;DR install TDR Manipulator, set first option to Disabled, test and you may be happy.

Not really... I kinda gave up recording with crapware known as AMD Gaming evolved/Raptr. Last thing I did was installing TDR Manipulator from http://www.wagnardmobile.com/forums/viewforum.php?f=8
Instructions for use are here: https://forums.geforce.com/default/topic/694754/geforce-drivers/tdr-manipulator-v1-1-02-23-2014-/

"Recommended usage:
For the most common users, simply Disable the first option."

[Ric]

i know its an old post but im having this problem now, running win10 64 tryed to put the new QWORD but still have same problem... also tryed to put setting to low to see if it goes better but i had few crashes anyway..
does that tdr manipulator do something different from creating the key or its the same thing?
should i try to use the 32bit version of the key?

running old 7970 ghz edition card..but its only the last couple month im having this issue

[indig0F10w]

Uninstall AMD bloatware called Raptr. AFAIK it should work with no crashes. Also, try latest drivers but the culprit remains Raptr.

[Ric]

no raptr installed and latest driver up

[indig0F10w]

Then you can try drivers version AMD Crimson Edition drivers v17.3.2. I have this version and I can record video without any crashes or problems on Windows 10 x64 v1607. If this doesn't help I'm out of suggestions :(