Driver Has Stopped Responding - Nvidia Driver Crashes

wunkley · 8 Jun 2015 at 11:47

I also run afterburner all the time - changed polling rate to 5000 this morning. Will do some testing later on.

I'm currently on the 353.12 drivers by the way (which have been crashing like all the other 353.xx)

triss · 8 Jun 2015 at 12:07

Changed my afterburner to 5000 aswell it was 100, will reinstall the latest drivers tomorrow and see

opethdisciple · 8 Jun 2015 at 12:17

Are these issues occuring because you guys are oc'in your cards and or running apps like aferburner etc?

PaulyD · 8 Jun 2015 at 12:19

Been using 353.00 since yesterday as per your suggestion Neil (previously on 350.12) and been perfect again, 352 and 353.06 were crash central on desktop, didn't try hot fix driver as others reported same issue.

Will wait it out now for the next driver

opethdisciple said:
Are these issues occuring because you guys are oc'in your cards and or running apps like aferburner etc?

I had just got my 980 and was overclocking it for the first time when I had these issues, was when t started happening at stock clocks I knew something was amiss. Googled and found loads of reports + same on here.

Ayahuasca · 8 Jun 2015 at 12:21

opethdisciple said:
Are these issues occuring because you guys are oc'in your cards and or running apps like aferburner etc?

Well we were doing all of that just fine on previous drivers but yes it's looking like a link between Afterburner/Precision X is one cause of the crashes.

After disabling chrome hardware acceleration and setting polling rate to 5000ms in Precision (fan speed changes is 5000ms anyway) I haven't had a single crash on the latest 353.12 hotfix drivers.

opethdisciple · 8 Jun 2015 at 12:25

You have to remember one thing. It's not Nvidia's job, to make sure their drivers work with overclocking software, and it's impossible for them to test stability and compatibility between all the different configurations and combinations of software people could be using to oc their gpus.

Neil79 · 8 Jun 2015 at 12:28

opethdisciple said:
Are these issues occuring because you guys are oc'in your cards and or running apps like aferburner etc?

NO!

I'll say that for the third time this week

Ayahuasca · 8 Jun 2015 at 12:29

Wasn't overclocking software causing it for me though, I removed Precision X and chrome would still crash unless hardware acceleration was disabled.

Lots of others getting crashes without any OC software installed so it is nVidia's job to make sure this is fixed.

StrongSad · 8 Jun 2015 at 12:45

opethdisciple said:
You have to remember one thing. It's not Nvidia's job, to make sure their drivers work with overclocking software, and it's impossible for them to test stability and compatibility between all the different configurations and combinations of software people could be using to oc their gpus.

Given that the two most popular overclocking utilities are branded and distributed by two of their largest ABP's, you would think Nvidia would ensure they had good compatibility.

Having software that essentially gimps normal operations on SOME cards, can't be good for either MSI. EVGA or Nvidia.

Silent_Scone · 8 Jun 2015 at 12:50

Well it won't be long before they figure it out considering they are aware of it. That's if it is even the route of most people's problems. I have no issues on 356.06 with TDR events and PX polling rate at default.

Ayahuasca · 8 Jun 2015 at 12:51

Silent_Scone said:
I have no issues on 356.06

They gave you an unreleased driver? :eek:

Neil79 · 8 Jun 2015 at 13:10

Ayahuasca said:
They gave you an unreleased driver?

No wonder he doesn't have any problems, he's from the future

~>Dg<~ · 8 Jun 2015 at 13:57

you know the most stable recent driver is 344.11 right ?

also most people who get that are oc their cards. check they stable.

Ayahuasca · 8 Jun 2015 at 13:59

350.12 is the most recent stable driver for me (not tried the iCafe ones), not a single crash and that's when I was using my card with a custom bios and a much higher clock as well.

I don't know why you would go all the way back to 344.11 unless you don't play any of the new titles.

Neil79 · 8 Jun 2015 at 14:03

~>Dg<~ said:
you know the most stable recent driver is 344.11 right ?

also most people who get that are oc their cards. check they stable.

Either trolling or didn't read any of the posts above

StrongSad · 8 Jun 2015 at 14:16

~>Dg<~ said:
you know the most stable recent driver is 344.11 right ?

also most people who get that are oc their cards. check they stable.

I think if you read back through, most are not overclocking their cards..... I know I was not.

Silent_Scone · 8 Jun 2015 at 14:57

Neil79 said:
No wonder he doesn't have any problems, he's from the future

LOL 352.86 completely fine -353.06 - Witcher 3 game issues.

Better

?

Neil79 · 8 Jun 2015 at 15:01

Silent_Scone said:
LOL 352.86 completely fine -353.06 - Witcher 3 game issues.

Better ?

353.06 was problematic for me too, 353.00 not so, but strangely they are mobile drivers with desktop support

dml3 · 8 Jun 2015 at 15:02

This issue happens a lot with pirated games. There are litecoin miners in those files. Will cause that "stopped responding" issue 100%

Neil79 · 8 Jun 2015 at 15:03

dml3 said:
This issue happens a lot with pirated games. There are litecoin miners in those files. Will cause that "stopped responding" issue 100%

LOL post of the day, thanks dml3 I needed that