September 6, 2014 at 19:41 #5246Jonathan078NLParticipant
The first hour I played TF I got the OpenGL error, I used the old BF3 fix but I did something slightly different.
I got an old Nvidia 9600GT with the latest 3.40 driver, and I’m using Windows 8.1 64-bit.
Because I’m using Windows 8.1 64-bit I made a different “64 bit” key: Instead of using the “DWORD (32 bit)” key. I used the “QWORD”(64-bit)” key with exactly the same description as below. After that I played for 6 hours in a row without any crash, So I think it helps to use the right key for the corresponding system you’re using. (32-bit or 64-bit). I hope this helps you fix this error.
This seems to be an old fix used for BF3.
1.Simply go to your registry: Start –> Run –> Type in “Regedit”
2.Go to “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers” and create a key of type “DWORD (32-bit)” or “QWORD (64-bit)” (depending on what system you’re using) and name “TdrDelay” with a value of 10 as Decimal value.
3.Reboot and play 🙂
In a nutshell it gives the GPU 10 seconds to recover/respond vs. 2 seconds (default).
This works for Windows 7, 8 and 8.1
This basically alleviates the “ Display driver stopped responding and has recovered” issue and/or “Display driver nvlddmkm stopped responding and has successfully recovered.” you will only see in the EventViewer.
If you want to learn more about this setting: Timeout Detection & Recovery (TDR)
Check this links:
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.
Before TDR existed, problems of this nature would have resulted in a system freeze and required a reboot of the operating system. If TDR is enabled and you see the TDR error message, “Display driver stopped responding and has recovered,” this means that the Windows operating system reset the display driver.September 6, 2014 at 21:17 #5300jon157ukParticipant
Thanks for that Jonathan, I’ll give it a try.September 7, 2014 at 00:00 #5367killkenny1Participant
Have been experiencing this problem. Will give your method a shot. Thanks for sharing this info, OP.September 7, 2014 at 02:19 #5403Jonathan078NLParticipant
Too bad, I’ve got 2 OpenGL crashes to desktop again, guess I was lucky yesterday 🙁
September 10, 2014 at 22:58 #7115xynixParticipant
- This reply was modified 7 years ago by Jonathan078NL.
All this does it make it wait 10 seconds to drop to the desktop rather than 2. It’s going to crash either way.
- The forum ‘Support’ is closed to new topics and replies.