13 replies to this topic

[Thunderbird Anthares]

every now and then my display drivers crash, the problem has been persisting for a long time, over half a dozen both MWO and nvidia driver versions (i keep them up to date)

symptoms: flickering boxy artifacts on frozen screen, serious sound lag/distortion

usually the drivers restart in time for me to continue playing, providing im not killed in the 30 seconds or so of it happening

[Targaryen X]

This might help, I was experiencing an NVidia driver has crashed and recovered message when I exited the game almost every time, this fixed it. Go to your nvidia control panel, under 'manage 3d settings' 'global settings' scroll down to power management mode and set it to 'prefer maximum performance' instead of adaptive. I was also experiencing a video crash in game where the whole screen would freeze and little green and reddish squares would pattern the frozen image, alt tab in and out and it would start working again. Since I changed that setting I no longer get the driver failed and recovered message when exiting and the video freeze disappeared except for one time, for a brief flash of half a second, but recovered without a hitch, no alt tabbing just a quick freeze flash of pattern, then gone and back to normal.Good luck.

[Thunderbird Anthares]

i tried setting it up for mwoclient.exe, will see how that works, thanks for the tip

[Mr Ezzquizo]

same problem

[Durant Carlyle]

ezzquizo, on 20 November 2013 - 09:24 AM, said:

same problem

Have you tried the possible fix provided by Gederix?

[Lord de Seis]

I haven't seen anything, installed the latest driver update from Nvidia yesterday and saw a huge improvement in performance.

[Marvyn Dodgers]

Good comments above, and I have also found it best to avoid Nvidia beta drivers with MWO, try to stick to released drivers.

[SpOoKy777]

Sounds familiar...

This TDR (Timeout Detection and Recovery) error, is known by Nvidia, but mostly ignored when it comes to a solution, their official statement:

https://forums.gefor...ddmkm-stopped-/

If you find a "display" error in your windows event manager which refers to "nvlddmkm.sys"...welcome to my nightmare...

I have this Issue on two different Win 7 rigs...my old system with a Gigabyte GTX 560 Ti and my brand new rig with a Gainward GTX 760 Phantom...in both cases the cards are factory-overclocked...

Best workaround I found was to downclock the cards...
For me Nvidia lost a lot of credit, especially after going through that stuff for the second time...

Edited by SpOoKy777, 20 November 2013 - 09:16 PM.

[Durant Carlyle]

The only time I have ever had this problem is when I first got my new graphics card and was finding out the overclock ceiling for it. If I went too high, it would freeze the game and I would Alt-Tab out and back in again to un-freeze. While I was out of game, it would have the "The display driver has stopped responding and was recovered." error. Of course, that reset the overclock back to factory settings and I would have to finish the game, exit to Windows and go back into EVGA Precision X to re-enable the overclock. Once I found the sweet spot, it hasn't happened since. This was with Prefer Maximum Performance enabled (I've known about that setting for quite some time now). I'm currently at +52MHz on the core and +275MHz on the memory of my EVGA GTX 780 SuperClocked w/ ACX (and that's above and beyond the factory overclock).

If you're having this problem with factory-overclocked cards and it's solved by down-clocking the cards (and you already have Prefer Maximum Performance set), then you have faulty graphics cards and you need to RMA them. Factory overclocks should be 100% stable in every game, but they sometimes have some that pass QA that shouldn't. It's not Nvidia's fault -- it's the specific manufacturers of your cards.

[SpOoKy777]

This problem seems to be more complex...

The "Prefer Max Performance" thing is enabled on both systems...

The GTX 560 was RMA'd back then and came back with the error still happening...nowadays I use the old rig for video/internet only, reverted to the last stable driver (which was 314.07 for me)...and everything is fine...


With my new gaming/working system (GTX 760) I can't go back to that old driver, because its not supported anymore...so I test every new driver coming up from Nvidia...so far no luck...error is still there...

Weird is that I'm able to play hours and hours of Battlefield 4 (ultra settings), no errors...same for FarCry3 and Rage...I can run FurMark all over the place...no errors...

I start MWO or Crysis 2/Crysis 3...play for 10-30 minutes...BAM...driver timed out...same for Napoleon: Total War...thats what I've tested so far...

What I'm trying to say...if both cards are faulty...they shouldn't:

1) ...work fine with reverted drivers...
2) ...work fine randomly with some games (game engines)...

Edited by SpOoKy777, 21 November 2013 - 10:22 AM.

[Durant Carlyle]

It is entirely possible that the games that cause problems are activating functionality of your GPU that the other games are not, or they are working your GPU harder than other games. Just because it works perfectly in one game does not make it functional. The fact that more than one game and engine causes problems indicates that hardware is the problem.

Rolling back to a previous driver likely disables the newest functionality that SHOULD be enabled. Evidently it's this newer functionality that's causing your GPUs to not be getting enough voltage. That's why down-clocking works -- the GPU no longer needs as much voltage while running at a slower speed.

I have seen others on actual hardware forums have to RMA more than once (several times, in fact) to get a fully stable functional factory-overclocked GPU.

[Daemir]

If you are using a 560 card or similar series and experience this error, roll back to driver version 314.22 and stay at those. Those are the last stable drivers that do not produce this error.

[SpOoKy777]

Quote

I have seen others on actual hardware forums have to RMA more than once (several times, in fact) to get a fully stable functional factory-overclocked GPU.

hmmm...thats so damn unconvenient, but I'll try it...I contacted my hardware dealer today...

Quote

[color=#959595]If you are using a 560 card or similar series and experience this error, roll back to driver version 314.22 and stay at those. Those are the last stable drivers that do not produce this error.[/color]

Thats correct...as I wrote, at the moment the 560 system is at 314.07 and stable for what I use it for...so I could go up to the .22 but I prefer to let it where it is...
The new rig with the 760 is what bugs me the most...


But thx for the help so far, guys...I'll post an update if the RMA is done...

[Nothing Whatsoever]

I was having some artifacts on the screen and my drivers crashing with fullscreen with the 650 Ti, the drives are fully updated. And I've set up my NVIDIA 3D settings as suggested here.

What I tried after using those settings was reducing screen resolution and playing in a window. My desktop is currently set to 1600 x 900. The game is set to 1280 x 720.

I might make further tweaks later, but it's working right now for me (and in-game settings, V-Sync is left unchecked, everything is set to Very High and I have PostAA on).



So that could be another workaround to test out.