• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

Driver Has Stopped Responding - Nvidia Driver Crashes

Yeah I it can't be a coincidence. They did something to un-gimp Kepler based cards and now Maxwell has problems.

Still no fix since 350.12, I am surprised tbh. Thought Nvidia would have done something by now.

Could they have separate drivers for different architectures. To maximise performance per architecture?

Hi,

Not strictly true at all (if at all). A lot of happy Maxwell owners without issues myself included. Neither me or Whyscotty and a few others have had grief with these builds. So it's specific to configurations not specficallly Maxwell cards
 
Hi, there are other reasons you could be getting TDR events? There weren't many complaints on 350 branch. That's the problem when everyone chips in, they assume everyone is having the same issue.

I am not sure why I could be on this driver, I am running stock clocks on my 980 so nothing has changed there. I have set AB to 7000 refresh rate but now most the time I just have it shut down so no monitoring software is running.
I get no crashes on google chrome just on games and anything that puts a load on the GPU.

The crashing is much less than on the newer drivers but it is still not right.

Shame tbqh :mad:

EDIT: I am going to try the 350.05 "hotfix" driver next as this one had a hot fix for a direct X error on Battlefield hardline
 
Last edited:
Hi,

Not strictly true at all (if at all). A lot of happy Maxwell owners without issues myself included. Neither me or Whyscotty and a few others have had grief with these builds. So it's specific to configurations not specficallly Maxwell cards

I'm not having a major issue with my 980's, I've had some crashes in Witcher 3 but not often at all. Latest drivers are fine so far.

Andi.
 
I hope I dont get that. I have been playing with my Zotac 980Ti since early yesterday and not a single crash haha. Probably jinxed myself now though lol. I didn't realise how much Gsync adds to the gaming experience and no more Vsync needed. It was a nightmare on my 290X and kept stopping for no reason at all in the middle of a game and tearing uggggg.
 
This may be completely off base, and mere conjecture, but could this be AIB specific? How is the relationship nowadays between EVGA and Nvidia?
Is Nvidia known to treat its AIBs differently due to a non public spat by penalizing them for not toeing the line?
 
Last edited:
After grueling weekend with my new GTX 980 Ti, I find that , with so many crashes, it needs a new BIOS to opperate properly. The EVGA Precision KBoost can keep it rock steady...no crashing computer or CTDs.
This is really important to me, as I saved up for 2 years to buy this card , only to find it fundamentally defective , but easily remedied. A new driver will never fully fix it any more than it did for the GTX970 cards. It is the throttling that crashes it. Please get the word out..please! It is the only way to get Nvidia to respond quickly.


Urg :(:o:(
 
Hi,

Not strictly true at all (if at all). A lot of happy Maxwell owners without issues myself included. Neither me or Whyscotty and a few others have had grief with these builds. So it's specific to configurations not specficallly Maxwell cards

Not really sure what you're saying here.

What I was saying is that could Nvidia have a tier of drivers for separate architecture. Rather than bundling it all in together.

I.e a Kepler driver that gets the most from Kepler.

And a Maxwell driver that gets the most from Maxwell.

Obviously a functional driver for either architecture would be most welcome at this point.

Regarding crashes, any driver since 350.12 is causing a range of instability across Nvidia hardware. They obviously do not know the cause yet as there is still no fix.
 
well i am going to try the driver that have been released today. im still on 350.12 and will be going to 353.30

will report back in an hour or so if crashes happen, if they dont i will report back tomoz.
 

Yup, and it could also explain why none of the reviewers are prepared to talk about the elephant in the room "DRIVER TDRs"... lol

This theory is as good as any, considering we have had no response from Nvidia on this issue.

By the way OP, tks for suggesting some of the tweaks, I think these did help some folks. :)
 
Last edited:
Had no issues since changing polling rate to 5000(AB) on the last few releases. :)

Hope I've not tempted fate :D

Yeah, it worked on one of my set ups which is great
, but unfortunately not on another.

It is definitely a driver related issue to state the obvious. 5 out of 6 of my Nvidia cards are EVGA , and one is an Asus Titan. I haven't yet tested the Asus Titan separately, or I could flash Asus bios on the EVGA Titan cards, but that's a lot more hassle to try and isolate the issue.. May be I will give it a go when I get some time .
 
Last edited:
1 hour and 30mins since my last post, been playing a game with chrome open and i have not had a crash since.

now i will try it with hardware acceleration turned on.
 
Last edited:
1 hour and 30mins since my last post, been playing a game with chrome open and i have not had a crash since.

now i will try it with hardware acceleration turned on.

D1craig, it can take anything from 15mins up to a week. Some people it's been fine since the first 353.06 release and is only happening now.
 
been playing games for 30 mins and always had chrome open, not one crash so far.


D1craig, it can take anything from 15mins up to a week. Some people it's been fine since the first 353.06 release and is only happening now.
well for me it seemed to happen very quick and very often. but i always have chrome open when gaming so if its still bad it will happen soon enough.
 
Back
Top Bottom