Page 1 of 1
Issues with latest Nvidia drivers - back to 362.00
Posted: Sun Mar 13, 2016 4:39 pm
by RipD
I've been having all kinds of odd problems. Did some research and it appears the versions after 362.00 are having issues. I couldn't get 354.51 to install correctly and Windows 10 had to use a restore point after the install failed. Sticking with 362.00 until I hear things are better.
Re: Issues with latest Nvidia drivers - back to 362.00
Posted: Sun Mar 13, 2016 6:32 pm
by toTOW
Which GPU ?
I'm testing the latest driver (364.51 with Vulkan support) on my 980 Ti / Windows 7 64 bits, and they're doing perfectly fine ...
Re: Issues with latest Nvidia drivers - back to 362.00
Posted: Sun Mar 13, 2016 8:44 pm
by Duce H_K_
If PPD stays the same with 362.00+ versions of Forceware - I just don't see any sense to update 362.00(or even 358.87) to something new.
Re: Issues with latest Nvidia drivers - back to 362.00
Posted: Sun Mar 20, 2016 6:38 pm
by RipD
toTOW wrote:Which GPU ?
I'm testing the latest driver (364.51 with Vulkan support) on my 980 Ti / Windows 7 64 bits, and they're doing perfectly fine ...
GTX 970 for me. Not sure issues are limited to this card.
Re: Issues with latest Nvidia drivers - back to 362.00
Posted: Thu May 05, 2016 11:45 pm
by boolean
No, they aren't. I'm experiencing the same issues with >362.00 versions of Forceware on Maxwell.
They seem to be related to Nvidia i.c.w. Windows 10. I've resurrected my prehistoric W7 64-bit PC from the dead and did some testing after swapping the GFX. No issues or whatsoever.
Re: Issues with latest Nvidia drivers - back to 362.00
Posted: Fri May 06, 2016 9:00 am
by foldy
OpenCL issues are also reported with some BOINC projects with Nvidia driver > 362.00
http://boinc.fzk.de/poem/forum_thread.php?id=1205
I have confirmed that the new Doom 365.19 drivers:
- Do NOT fix the OpenCL/CUDA miscalculations (Internal NVIDIA Bug ID: 200197534)
- DO fix the Poem@Home TDR/crashes (NVIDIA Bug ID: 1754468)
So... If you do any distributed computing involving OpenCL/CUDA calculating, I recommend that you **stick with 362.00** for correct calculations, until the next driver release which should have the miscalculation fix.
Re: Issues with latest Nvidia drivers - back to 362.00
Posted: Fri May 06, 2016 11:04 am
by toTOW
Indeed © ... but as long as FAH works, I'm fine
Re: Issues with latest Nvidia drivers - back to 362.00
Posted: Wed May 11, 2016 4:21 pm
by FldngForGrandparents
I am running two separate workstations dedicated to folding on Ubuntu 14.04. They both have an identical GTX 980 in them. One runs on 361.42, the other 346.96. On a core 21 the older driver seems to perform better. On core 18 the newer driver seems to perform better. I will hopefully have more affirmative information on this once I start parsing the log files.
Re: Issues with latest Nvidia drivers - back to 362.00
Posted: Wed May 11, 2016 8:01 pm
by Nicolas_orleans
I can confirm that on my Ubuntu 14.04 setup, 346.96 is better than 361.42 on core 21 (TPFs are 3-7% higher with 361.42 on my cards). Haven't spent enough time with 361.42 to check core 18. Back on 346.96 for now.
Also, as a remark, 364.19 is unstable with this 14.04 setup / 3.13 kernel (GUI corruption, CPU soft lockups).
Re: Issues with latest Nvidia drivers - back to 362.00
Posted: Wed May 11, 2016 9:52 pm
by bruce
Any comparisons with 352.63?
Re: Issues with latest Nvidia drivers - back to 362.00
Posted: Fri May 13, 2016 10:19 pm
by mmonnin
346.96 is faster than 352.63 in Linux. I had another member at OCN switch to 346.96 from those drivers and saw an immediate improvement. Him and I both have 980Ti cards. I was running a 100mhz lower clock speed with 346.96 and had better PPD numbers. He switched and is now decently better than me. He said 50-75k PPD better just by switching.
Re: Issues with latest Nvidia drivers - back to 362.00
Posted: Sun May 15, 2016 8:47 am
by giganews35
^^^He's right you know. I'm also now at a lower clock 1499Mhz. 346.96 is the golden Linux driver!