• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Nvidia Driver 353.06 Released

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.
 
Eymar said:
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.
Click to expand...

I am running 353.06 Windows 8.1 Pro 64bit and GTX 970 and no crashes in Chrome so far.
 
XiandreX said:
I am running 353.06 Windows 8.1 Pro 64bit and GTX 970 and no crashes in Chrome so far.
Click to expand...

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.?"
 
Eymar said:
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.?"
Click to expand...

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.
 
SteveGrabowski said:
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.
Click to expand...

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:
 
Eymar said:
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.?"
Click to expand...

I will continue to monitor it. Hopefully they tweak this release and iron out the recent bugs. Played a good hour session of Project cars and no issues.
 
XiandreX said:
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:
Click to expand...

I'm worried about general usability of my system. I never had lockups, but using Chrome I'd get the driver crashing every 20-30 minutes when I had Chrome open, so freeze for a split second, blackscreen, driver restarts with GPU-Z showing a quick spike to 100% GPU usage. Seemed like it happened a lot when opening new tabs, especially tabs with flash. For example, I was watching the Warriors-Rockets game the other day with ESPN.com's boxscore page open, and since it refreshes every 30 seconds or so automatically I was getting crashes every couple of minutes. But I never updated Chrome, never updated flash, and these worked great on 350.12 and before, so I'm blaming Nvidia and I'm not going to uninstall Chrome or turn off flash.
 
Driver crashed on me when I opened Firefox, but it seems to be OK now I've disabled hardware acceleration.
 
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."
 
Eymar said:
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."
Click to expand...

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.
 
AdamK47 said:
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.
Click to expand...

Maybe a bug with Precision then, but also had a rock stable system (up to 350.12 drivers) with Titan X SLI, 5930k MSI x99 Plus, 32GB Corsair LPX 2666. Haven't seen a reboot yet with PrecisionX disabled + 353.06(with PX running I was running +225 core, but no voltage boost so max is usually 1379 Mhz (1400 if temps below 70c) with desktop clocks at 800 Mhz (multi monitor setup).
 
I had the crashes with the old driver in Firefox. Using afterburner to overclock and also when I ran the cards at stock I would get the crashing.

There was definitely something wrong with the last drivers, but the bug is fixed in these new drivers for me. No more crashes.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top