Game Crash: Open GL TDR Error

[Moving McTarget]

When I launch the game, I get the Team 17 logo and start to hear some crazy coil whine, my GPUs increase in temp by 20 degrees and then the game crashes with a TDR error (more info: http://nvidia.custhelp.com/app/answers/detail/a_id/3633).

I have never heard a noise come from my computer like I did when I launched this game, even loading benchmark applications like firestrike will not replicate the noise that came from my rig when I launched this game… Quite concerning.

Any information on this would be greatly appreciated.

[76561198103597845]

Hey Moving McTarget,


That sounds like very odd behaviour.
Could you please follow the steps on the page linked below and link your DxDiag information:

• http://steamcommunity.com/app/260330/discussions/0/558754260588086082/

(Please feel free to upload the DxDiag onto a free text hosting site rather than submitting through the website)

Once I've got this, I'll take a look and see if there's any reason for a conflict.


Thank you,
BenTeam17

[Moving McTarget]

Thanks for the fast reply, please find the DxDiag information you requested via the following link:

http://pasted.co/2444f0dc

If you require any additional information, please let me know. I will await your response prior to performing any additional troubleshooting.

Cheers

Matt

[76561198103597845]

Hi again Moving McTarget,

Thanks for sending over the DxDiag, your machine is a monster. Grats :).
It doesn't look like your spec is an issue but the DxDiag has highlighted the following file as the fault: nvoglv32.DLL

There are a few reasons that this (Bex c0000409) crash might occur.
First off I'd like to know the following info:

• Your Antivirus software
  
• The version of your chosen Antivirus software
  
• Whether you have this issue with any other applications or games
  
• The exact TDR error message you recieve (the link you provided doesn't work for me)

Thank you,
BenTeam17

[Moving McTarget]

Hi Ben,

Thanks for the reply and the compliments :)

It wasn’t a cheap setup but it was more than worth it… its all housed in a Corsair Obsidian 900D and its soon to be watercooled. Should look good when its done.

Sorry about the link, it just seems that steam could not interperate the entire link, when I copied and pasted it into edge, it worked fine. I have pasted the content of the link at the bottom of this post.

I would also like to point out that I have managed to get the game running twice, so it appears that the issue is now intermittent, the only change I have made to my system was the latest NVidia update (Version: 359.06). I’m not sure if this would have been what improved ithe issue, as it was only a game ready update for Just Cause 3 and Rainbow Six: Siege.

I am only using Windows Defender at this point, as far as versions go it only provides definition versions the version for both virus and spyware definitions are both 1.211.2133.0

No other applications/games are exhibiting the same behavior. Some older games fail to launch but I’m sure that’s due to them just being old. None of them put the graphics cards under extreme load like what’s happened in this case. It gives the GPU’s an absolute hiding, they both spike up to 100% utilization and the temps increase by about 30 degrees within a few seconds.
This is one of the reasons that I reached out to you guys, just on the off chance that someone out there might have the same problem and end out breaking something by continuously trying to launch the game without actually knowing what’s going on.

If you need any more information please let me know

Cheers

Matt



OpenGL message “TDR detected”
Answer ID 3633 | Published 02/20/2015 08:04 AM | Updated 02/20/2015 10:59 AM
I have seen this Event Log Message:
A TDR has been detected.
The Application must close.
What does it mean?
If you received this message from an application (on a pop up message or in the Event Log), the application was unable to continue rendering because the Microsoft Windows imposed time limit (TDR) was exceeded. This is normally the case when the workload sent to the Graphics Card is greater than what the graphics card can process in the normal timeout of two seconds.
You can find more information in this page:
http://msdn.microsoft.com/en-us/windows/hardware/gg487368.aspx
How can this be fixed?
Two possible solutions to try would be:
1. Reduce the graphics workload if possible, such as rendering to a lower resolution or with less detail.
2. Increase the timeout to allow more time to complete the really tough rendering parts. Microsoft provides the information on how to modify the Windows Registry to achieve this.

[76561198103597845]

Hi again Matt,


Thanks for getting back to me with all of this information.
Sorry for the delayed response, your thread got pushed back by some others and temporarily lost.

I've had another look into this and have a few more ideas.
First off, the .dll causing this is part of the NVidia drivers that you have installed.
If for any reason this is causing a conflict, cleanly installing the latest driver should help.
Please install the latest drivers - 361.91 (WHQL):

http://www.nvidia.co.uk/download/driverResults.aspx/98951/en-uk

Performing a clean install should remove any old drivers cluttering up your machine.
After running the install though, please manually track down any old drivers and delete them.
Note: You might need to refer to NVidia support for exactly where drivers are kept and how to remove them safely.

Next, please make sure that you undo and changes made with the 'Set launch options...' tool in Steam and opt out of the current Steam Beta if you're participating.

If none of this has worked, I'll have to pass it on to the team to try and reproduce.
Please let me know how you get on.


Thank you,
BenTeam17