the crash I get with 352.86 are gone with this driver
353.06 drivers still has Chrome crash issue (just had 2 restarts in past hour while browsing, no reboot issues with 350.12). I'm guessing issue with Maxwell as Kepler users aren't reporting same issue as far as I know. I'm going back to 350.12.
I am running 353.06 Windows 8.1 Pro 64bit and GTX 970 and no crashes in Chrome so far.
Pretty random and less frequent I think than 352.86. I installed 353.06 yesterday (Win 8.1 Pro 64bit and Titan-X) and didn't have any reboots after a few hours of light browser use, but have 2 today while using Chrome. Nvidia forums are reporting issues as well: https://forums.geforce.com/default/...-driver-feedback-thread-released-5-31-15-/17/
Post 230: "This latest driver update and 352.86 is causing crashes while on Google Chrome for me also. I've had a 970 since November and haven't had a single issue until 352.86/353.06.?"
Crap, I guess I'll wait another month before playing Witcher 3 then and hope Nvidia fixes their drivers by then. The driver crashes were like every 20-30 minutes for me using Chrome on 352.86 with my 970.
Pretty random and less frequent I think than 352.86. I installed 353.06 yesterday (Win 8.1 Pro 64bit and Titan-X) and didn't have any reboots after a few hours of light browser use, but have 2 today while using Chrome. Nvidia forums are reporting issues as well: https://forums.geforce.com/default/...-driver-feedback-thread-released-5-31-15-/17/
Post 230: "This latest driver update and 352.86 is causing crashes while on Google Chrome for me also. I've had a 970 since November and haven't had a single issue until 352.86/353.06.?"
I had the same amount of lockups, but what helped a ton was the following.
I turned off V-Sync in game, with adaptive sync set in control panel.
Not sure if setting 60 fps or unlimited contributed as I alternated between the two.
Ran full screen and not borderless.
I have heard that Afterburner + 352.86 was a problem.
So far 353.06 has been a lot more stable for me, tried stock clocks and run up
to around 1500 core and no issues. :thumbsup:
Just remembered this thread: Why you should not use Afterburner/Precision to overclock Maxwell/Kepler. Turned off Precision and haven't seen Chrome reboot issue yet with 353.06 (only been around 4 hours of use so still monitoring). I will try the solution in that thread:
"Originally Posted by flexy -
By the way there *IS* a solution for those who don't want to or can't mod their bios: Gigabyte OC Guru. It works also with other brand cards since you can specify an "offset" minimal voltage that is applied. This can be used as a workaround to avoid crashes at lower clocks."
I have been using Afterburner to overclock my four Titan X cards. A modest +200 core, +100 memory, and a +50mV (to unlock higher speed steps). I exclusively use Chrome and have never had the cards cause problems with it. Also, since I use 4 cards there are many times when max boost isn't even needed, so the clocks bounce between base and boost (1000MHz to 1400MHz) depending on load. No problems there. The Titan X cards are fantastically stable just as my previous 980s were.
nvidia users have issues with chrome crashing??? yuck