Folding Forum

Has that appeared via Experience? It's not posted to the site yet....

Listed for 980 Ti...
http://www.nvidia.com/download/driverRe ... 3448/en-us

376.33 still not working but there should be a hotfix until christmas.

http://forums.evga.com/Got-word-from-NV ... px#2593454

Finaly a solution that is comming they took their time but great news for the folders

376.33 is working for me. I'm running 2 GTX 1080 FEs yielding ~140k ppd

willdeng wrote:376.33 is working for me. I'm running 2 GTX 1080 FEs yielding ~140k ppd

Folding Core_18 or Core_21 projects? The projects using the first core will work, but those using the second have been exiting with a consistent error for everyone else using version 375 or 376 drivers. That includes a report on 376.33 just a couple posts above.

Joe_H wrote:

willdeng wrote:376.33 is working for me. I'm running 2 GTX 1080 FEs yielding ~140k ppd

Folding Core_18 or Core_21 projects? The projects using the first core will work, but those using the second have been exiting with a consistent error for everyone else using version 375 or 376 drivers. That includes a report on 376.33 just a couple posts above.

Core_21 projects. It was working well initially and some of the jobs actually finished but now I'm getting the same errors you described.

silverpulser said:Has the issue with Folding@home been addressed?



No. Changes in our R375 driver exposed an application bug with Folding@Home. We are trying to get an application side fix but in the meantime, our team is still trying to come up with a driver side workaround. This is close to being done but not yet complete. We'll likely post a hotfix driver as soon as a driver side workaround is available.

Shots fired NVIDIA is blaming folding@home team.

pithos wrote:Shots fired NVIDIA is blaming folding@home team.

As i said earlier, FAH sixed the suggested error but the problem remains. The two teams are working together and any discussion of incremental proposed changes is a waste of effort. Nothing matters until they agree that they've found the fix.

The fact that the hotfix scheduled for today has been postponed for 5 more days means they know there's still work to be done. (See foldy's quote, above)

As a QA analyst who spends a lot of his time sitting in meetings, caught in cross fires between vendors and various groups of developers arguing over where a defect "truly lies," I know how easy and tempting it is to get into the finger pointing/blame game. It can sometimes even be kind've fun to listen to the back and forth, but ultimately, if teamwork prevails, that is the ultimate good. Commit notes and release notes are the best summary of what rises from out of the mire. I for one would be very interested in a post-analysis from both sides. The collaboration we're seeing now is a positive thing, and it may have taken a while, but at the end of the day, it shows that Nvidia understands the value of the project and the importance of their role in it.

willdeng wrote:376.33 is working for me. I'm running 2 GTX 1080 FEs yielding ~140k ppd

Something badly wrong anyway if you're only getting 140kppd from a GTX 1080 as it's what I'd expect if I slightly overclocked my GTX 950. A GTX 1080 should be giving three times that.

snapshot wrote:

willdeng wrote:376.33 is working for me. I'm running 2 GTX 1080 FEs yielding ~140k ppd

Something badly wrong anyway if you're only getting 140kppd from a GTX 1080 as it's what I'd expect if I slightly overclocked my GTX 950. A GTX 1080 should be giving three times that.

Using 373.06, I get 600-700k PPD with 1 GTX1080 and I use the rig it's in all day (with 3 monitors).


*Agreement emphasis added to quote

snapshot wrote:

willdeng wrote:376.33 is working for me. I'm running 2 GTX 1080 FEs yielding ~140k ppd

Something badly wrong anyway if you're only getting 140kppd from a GTX 1080 as it's what I'd expect if I slightly overclocked my GTX 950. A GTX 1080 should be giving three times that.

I missed a zero there, meant to say 1400k or 1.4m ppd. I'm reverting back to 373.06 drivers. 376.33 is making Overwatch crash

SombraGuerrero wrote:As a QA analyst who spends a lot of his time sitting in meetings, caught in cross fires between vendors and various groups of developers arguing ...

That's not uncommon in an inter-company attempts to fix problems. (I've seen it in my company's dealings with customers or vendors.) It always helps when everybody decides to work as a team, no matter who ends up having to work the hardest to resolve the issue(s).

I just installed a Nvidia update to 375.26. right after reboot, FAH GPU failed on two core A21 WUs, then got an A18 WU which it is now processing. Does that imply a (partial??) fix? or not?