EVGA

Drivers 376.09/.19/.33 still no fix for FaH [Edit: Fixed with Core21 v0.0.18]

Page: 123 > Showing page 1 of 3
Author
DutchForce
CLASSIFIED Member
  • Total Posts : 2360
  • Reward points : 0
  • Joined: 2006/12/04 14:25:44
  • Location: Netherlands
  • Status: offline
  • Ribbons : 52
2016/11/28 10:42:16 (permalink)
The new NVidia driver 376.09 WHQL released today still has no fix for FaH (Core21 WUs fail on Maxwell/Pascal GPUs).
So driver 373.06 WHQL is still the latest good working driver for FaH.
 
See NVidia forum post of Manuel Guzman:
Official 376.09 Game Ready WHQL Display Driver Feedback Thread (released 11/28/16)
 

villageidiot182 said:
Any Updates on Folding@Home?
------------------
 
ManuelGuzman:
We still have not resolved this issue.

 
 
EDIT:  Update December 5,
 
NVidia released new drivers 376.19 WHQL today, but still no fix for FaH.
See NVidia forum post of Manuel Guzman:
Official 376.19 Game Ready WHQL Display Driver Feedback Thread (Released 12/5/16)
 

MammothJerk said:
Any update on the F@H WU problems?
-----------------------
 
ManuelGuzman:
No fix in this driver for that issue. It is one of our top priority bugs though.

 
See also this post of Manuel Guzman:
Official 376.19 Game Ready WHQL Display Driver Feedback Thread (Released 12/5/16)
 

bb30994 said:
@Manuel: Do you have enough information to reproduce the F@H problems?
 
I do not see it listed as an Open Issue.
----------------------
 
ManuelGuzman:
Yes.  We just have not yet narrowed down the root cause.

 
EDIT-2:  Update December 14,
 
NVidia released new drivers 376.33 WHQL today, but no fix for FaH yet.
See NVidia forum post of Manuel Guzman:
Official 376.33 Game Ready WHQL Display Driver Feedback Thread (Released 12/14/16)
 

silverpulser said:
Has the issue with Folding@home been addressed?
---------------------------------------
 
ManuelGuzman:
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.

 
See also an update from NVidia posted by Scott:
Got word from NVIDIA and this issue they are working on.--UPDATED 12/14
 
scott@bjorn3d
12/14 Update

Hey Scott,

Our efforts to get a resolution out by 12/14 has run into some roadblocks. The change suggestion we made for OpenMM needs more tweaks and our driver side workaround is close to being done but not complete yet. We plan to post a hotfix driver to unblock the Folding@Home users as soon as we have a workaround to share (within the next few days).

We’ll keep you posted.

Regards,
Team NV

 
EDIT-3: 
Changed thread title to:  "Drivers 376.09/.19/.33 still no fix for FaH [Edit: Fixed with Core21 v0.0.18]"
NVidia first fixed this with the Hot Fix Driver 376.48 and later Stanford fixed it with the New Core21 v0.0.18.
post edited by DutchForce - 2017/02/16 09:19:11


 
Folding Rig: Lian-Li PC-P50 | Corsair HX850 | MSI 890FXA-GD70 | AMD X4-965 BE | GTX980 Ti SC & GTX1070 SC
#1

81 Replies Related Threads

    drougnor
    CLASSIFIED Member
    • Total Posts : 2721
    • Reward points : 0
    • Joined: 2006/07/18 05:57:59
    • Location: FL USA /Affiliate MCK692UUS /Assoc HPW7E9T81P8KCCH
    • Status: offline
    • Ribbons : 18
    Re: Driver 376.09 still no fix for FaH (Core21 on Maxwell/Pascal GPUs). 2016/11/28 11:14:59 (permalink)
    I'm wondering if the better question to start asking is if they actually KNOW what the issue is . . .


    #2
    HK-Steve
    CLASSIFIED Member
    • Total Posts : 2253
    • Reward points : 0
    • Joined: 2015/04/06 08:46:57
    • Location: Switzerland
    • Status: offline
    • Ribbons : 2
    Re: Driver 376.09 still no fix for FaH (Core21 on Maxwell/Pascal GPUs). 2016/11/28 11:24:28 (permalink)
    So that is now the 4th update, and still broken.... Crazy

     


    #3
    rjohnson11
    EVGA Forum Moderator
    • Total Posts : 85620
    • Reward points : 0
    • Joined: 2004/10/05 12:44:35
    • Location: Belgium
    • Status: offline
    • Ribbons : 75
    Re: Driver 376.09 still no fix for FaH (Core21 on Maxwell/Pascal GPUs). 2016/11/28 12:01:03 (permalink)
    Just to let everyone know that I've spoken with NVIDIA. They are still aware of this and still investigating/working on it. Sorry but that is all the info I have at the moment.

    AMD Ryzen 9 5950X,  Corsair Mp600 Pro M.2 2TB, 128GB DDR4  Crosshair VIII Hero, Asus RX 6900 XT Associate Code: H5U80QBH6BH0AXF

    #4
    Torell
    Superclocked Member
    • Total Posts : 244
    • Reward points : 0
    • Joined: 2009/04/27 19:30:24
    • Status: offline
    • Ribbons : 0
    Re: Driver 376.09 still no fix for FaH (Core21 on Maxwell/Pascal GPUs). 2016/11/28 12:27:47 (permalink)
    rjohnson11
    Just to let everyone know that I've spoken with NVIDIA. They are still aware of this and still investigating/working on it. Sorry but that is all the info I have at the moment.




    thanks for asking and keeping us in the loop




    #5
    scott@bjorn3d
    SSC Member
    • Total Posts : 688
    • Reward points : 0
    • Joined: 2006/11/20 04:37:19
    • Status: offline
    • Ribbons : 2
    Re: Driver 376.09 still no fix for FaH (Core21 on Maxwell/Pascal GPUs). 2016/11/28 13:03:31 (permalink)
    It is freaking amazing how these guys can't find someone that knows how to write drivers!!  They are getting as bad as AMD.
     


    #6
    Chris21010
    FTW Member
    • Total Posts : 1659
    • Reward points : 0
    • Joined: 2006/05/03 07:26:39
    • Status: offline
    • Ribbons : 9
    Re: Driver 376.09 still no fix for FaH (Core21 on Maxwell/Pascal GPUs). 2016/11/28 15:12:29 (permalink)
    i blame bloatware. they cram too much crap into "drivers" nowadays and not simply work on creating a useful driver. its like installing off CD's back in the hay day where it would give you a ton of useless crap and not just the driver.


    #7
    MrEnigma
    New Member
    • Total Posts : 90
    • Reward points : 0
    • Joined: 2016/04/13 08:36:57
    • Status: offline
    • Ribbons : 1
    Re: Driver 376.09 still no fix for FaH (Core21 on Maxwell/Pascal GPUs). 2016/11/29 05:57:20 (permalink)
    Chris21010
    i blame bloatware. they cram too much crap into "drivers" nowadays and not simply work on creating a useful driver. its like installing off CD's back in the hay day where it would give you a ton of useless crap and not just the driver.




    Agreed


    PC Build (early 2009 - gaming only)
    Antec Twelve Hundred - Win10 x64
    eVGA X58 SLI - Core i7 920 (bumped to 2.80GHz) - 6GB DDR3-1066
    WD Black 640GB/7200RPM - Samsung 850 EVO 500GB SSD

    Asus GTX 1060 OC (3GB) - HT Omega Striker 7.1 - Asus VH222H 21.5"
     
    Workhorse (gen. purpose)
    Mid-2011 Mac Mini (2.3GHz i5) - Dell S2715H 27"
    #8
    drougnor
    CLASSIFIED Member
    • Total Posts : 2721
    • Reward points : 0
    • Joined: 2006/07/18 05:57:59
    • Location: FL USA /Affiliate MCK692UUS /Assoc HPW7E9T81P8KCCH
    • Status: offline
    • Ribbons : 18
    Re: Driver 376.09 still no fix for FaH (Core21 on Maxwell/Pascal GPUs). 2016/11/29 07:53:51 (permalink)
    Either way, there's a distinct cut off that they can use as an A:B test - Drivers before this point worked, drivers after don't - What is the change that happened at that point and WHY is it breaking things? 

    I know Nvidia won't divulge the inner workings of their drivers to protect their IP, but at least a high level acknowledgement that they've at least narrowed it down that far and are trying to reconcile the change in a way that will let F@H use the hardware to it's fullest would be a great deal more info that 'We're working on it'.
    d


    #9
    DutchForce
    CLASSIFIED Member
    • Total Posts : 2360
    • Reward points : 0
    • Joined: 2006/12/04 14:25:44
    • Location: Netherlands
    • Status: offline
    • Ribbons : 52
    Re: Drivers 376.09 and 376.19 still no fix for FaH (Core21 on Maxwell/Pascal GPUs). 2016/12/05 09:59:45 (permalink)
    NVidia released new drivers 376.19 WHQL today, but still no fix for FaH.
    See NVidia forum post of Manuel Guzman:
    Official 376.19 Game Ready WHQL Display Driver Feedback Thread (Released 12/5/16)
     

    MammothJerk said:
    Any update on the F@H WU problems?
    ------------------------
     
    ManuelGuzman:
    No fix in this driver for that issue. It is one of our top priority bugs though.

     
    Edit:
    See also this post of Manuel Guzman:
    Official 376.19 Game Ready WHQL Display Driver Feedback Thread (Released 12/5/16)
     

    bb30994 said:
    @Manuel: Do you have enough information to reproduce the F@H problems?
     
    I do not see it listed as an Open Issue.
    ----------------------
     
    ManuelGuzman:
    Yes.  We just have not yet narrowed down the root cause.

    post edited by DutchForce - 2016/12/05 14:59:06


     
    Folding Rig: Lian-Li PC-P50 | Corsair HX850 | MSI 890FXA-GD70 | AMD X4-965 BE | GTX980 Ti SC & GTX1070 SC
    #10
    notfordman
    Omnipotent Enthusiast
    • Total Posts : 9940
    • Reward points : 0
    • Joined: 2007/08/09 23:52:23
    • Location: In a van, down by the RIVER!!!!!!!!
    • Status: online
    • Ribbons : 25
    Re: Drivers 376.09 and 376.19 still no fix for FaH (Core21 on Maxwell/Pascal GPUs). 2016/12/05 10:24:08 (permalink)
    Thank you Dutch! I have a dream.....One day we can have a driver that folds and lets you play BF. 
    #11
    bcavnaugh
    The Crunchinator
    • Total Posts : 38123
    • Reward points : 0
    • Joined: 2012/09/18 17:31:18
    • Location: USA Affiliate E5L3CTGE12 Associate 9E88QK5L7811G3H
    • Status: offline
    • Ribbons : 276
    Re: Drivers 376.09 and 376.19 still no fix for FaH (Core21 on Maxwell/Pascal GPUs). 2016/12/05 10:47:24 (permalink)
    Now 6 Drivers later and we still have this issue.
    Maybe it is time for NVIDIA to announce they no longer going to support Stanford and their Folding @ Home Projects.
    Let's hope this does not happen over on the BOINC side as well. 
    post edited by bcavnaugh - 2016/12/05 10:53:28

    Affiliate Code: E5L3CTGE12 & Associate Code: 9E88QK5L7811G3H  NoDarkSkies


     
    #12
    ipkha
    CLASSIFIED Member
    • Total Posts : 2297
    • Reward points : 0
    • Joined: 2015/02/10 21:01:40
    • Location: Indiana
    • Status: offline
    • Ribbons : 6
    Re: Drivers 376.09 and 376.19 still no fix for FaH (Core21 on Maxwell/Pascal GPUs). 2016/12/05 16:17:10 (permalink)
    I wish they'd drop it in the open issues in the docs.


    #13
    Ali Man
    iCX Member
    • Total Posts : 260
    • Reward points : 0
    • Joined: 2012/08/01 12:13:06
    • Status: offline
    • Ribbons : 0
    Re: Drivers 376.09 and 376.19 still no fix for FaH (Core21 on Maxwell/Pascal GPUs). 2016/12/05 20:14:13 (permalink)
    One thing I know about Nvidia is that if it's not an issue of the big boys, then it's not a issue at all.
     
    This tells a lot about a company which I think is really ****ty. I've actually had personal experience when I contacted Nvidia for an internship program and got no response. And after sending an email to the CEO, was it 'partially' acknowledged. Long story short, I bet that chinese dude has no clue about this.
     
     
    #14
    DarKSeeD
    Superclocked Member
    • Total Posts : 231
    • Reward points : 0
    • Joined: 2007/07/17 08:56:20
    • Location: Sighisoara, Romania
    • Status: offline
    • Ribbons : 0
    Re: Drivers 376.09 and 376.19 still no fix for FaH (Core21 on Maxwell/Pascal GPUs). 2016/12/05 23:51:03 (permalink)
    Hmm. I get BAD WORK UNIT only when using Core 21!  All other Core units worked properly.

    Gizas! what a mess  



    My Affiliate Code: H9P4U2TDJV  
    #15
    scott@bjorn3d
    SSC Member
    • Total Posts : 688
    • Reward points : 0
    • Joined: 2006/11/20 04:37:19
    • Status: offline
    • Ribbons : 2
    Re: Drivers 376.09 and 376.19 still no fix for FaH (Core21 on Maxwell/Pascal GPUs). 2016/12/06 02:41:15 (permalink)
    Well so far my contacts at NVIDIA has gotten no where on this issue.  I pulled my last try card this morning in a e-mail, will see if that helps.
    post edited by scott@bjorn3d - 2016/12/06 02:42:39


    #16
    ipkha
    CLASSIFIED Member
    • Total Posts : 2297
    • Reward points : 0
    • Joined: 2015/02/10 21:01:40
    • Location: Indiana
    • Status: offline
    • Ribbons : 6
    Re: Drivers 376.09 and 376.19 still no fix for FaH (Core21 on Maxwell/Pascal GPUs). 2016/12/06 08:01:13 (permalink)
    These kind of issues are hard to track down. Games with lousy optimization and weird graphics code are bad enough. But trying to fix cuda/OpenCL is even worse. The big money needs those code paths to be extremely robust, which is why the long wait is concerning. These are the critical code paths that the supercomputers built with Tesla and Quadro need to be error free and the fact that the most advanced core 21 units from F@h fail is concerning. It is also possible that this is a bug in the core 21 code as well, which makes this a PITA for any group of developers/bug hunters.


    #17
    bcavnaugh
    The Crunchinator
    • Total Posts : 38123
    • Reward points : 0
    • Joined: 2012/09/18 17:31:18
    • Location: USA Affiliate E5L3CTGE12 Associate 9E88QK5L7811G3H
    • Status: offline
    • Ribbons : 276
    Re: Drivers 376.09 and 376.19 still no fix for FaH (Core21 on Maxwell/Pascal GPUs). 2016/12/06 10:37:58 (permalink)
    ipkha
    These kind of issues are hard to track down. Games with lousy optimization and weird graphics code are bad enough. But trying to fix cuda/OpenCL is even worse. The big money needs those code paths to be extremely robust, which is why the long wait is concerning. These are the critical code paths that the supercomputers built with Tesla and Quadro need to be error free and the fact that the most advanced core 21 units from F@h fail is concerning. It is also possible that this is a bug in the core 21 code as well, which makes this a PITA for any group of developers/bug hunters.



    I would agree, But they are the ones who Broke It.
    It is not like Core 22 came out and having driver issues.
    Core 21 has been out to long for a driver issue to have started.
     

    Affiliate Code: E5L3CTGE12 & Associate Code: 9E88QK5L7811G3H  NoDarkSkies


     
    #18
    maveric191
    New Member
    • Total Posts : 52
    • Reward points : 0
    • Joined: 2011/01/16 15:37:13
    • Status: offline
    • Ribbons : 0
    Re: Drivers 376.09 and 376.19 still no fix for FaH (Core21 on Maxwell/Pascal GPUs). 2016/12/10 03:17:26 (permalink)
    bcavnaugh
    It is not like Core 22 came out and having driver issues.
    Core 21 has been out to long for a driver issue to have started.



    It could be that the newer drivers are less tolerant to errors in the core 21 code that may have been there from day 1 and just haven't been caught up till now.

     

     
    #19
    bcavnaugh
    The Crunchinator
    • Total Posts : 38123
    • Reward points : 0
    • Joined: 2012/09/18 17:31:18
    • Location: USA Affiliate E5L3CTGE12 Associate 9E88QK5L7811G3H
    • Status: offline
    • Ribbons : 276
    Re: Drivers 376.09 and 376.19 still no fix for FaH (Core21 on Maxwell/Pascal GPUs). 2016/12/10 09:50:48 (permalink)
    maveric191
    bcavnaugh
    It is not like Core 22 came out and having driver issues.
    Core 21 has been out to long for a driver issue to have started.



    It could be that the newer drivers are less tolerant to errors in the core 21 code that may have been there from day 1 and just haven't been caught up till now.


    See Post Got word from NVIDIA and this issue they are working on. Back to Pointing Fingers at each other.

    Affiliate Code: E5L3CTGE12 & Associate Code: 9E88QK5L7811G3H  NoDarkSkies


     
    #20
    notfordman
    Omnipotent Enthusiast
    • Total Posts : 9940
    • Reward points : 0
    • Joined: 2007/08/09 23:52:23
    • Location: In a van, down by the RIVER!!!!!!!!
    • Status: online
    • Ribbons : 25
    Re: Drivers 376.09 and 376.19 still no fix for FaH (Core21 on Maxwell/Pascal GPUs). 2016/12/10 10:20:23 (permalink)
    Thanks for the info Bcav! All I want for Christmas is a driver that works [for both]. 
    #21
    bcavnaugh
    The Crunchinator
    • Total Posts : 38123
    • Reward points : 0
    • Joined: 2012/09/18 17:31:18
    • Location: USA Affiliate E5L3CTGE12 Associate 9E88QK5L7811G3H
    • Status: offline
    • Ribbons : 276
    Re: Drivers 376.09 and 376.19 still no fix for FaH (Core21 on Maxwell/Pascal GPUs). 2016/12/10 10:22:13 (permalink)
    For me it is not an issues (ATM) as I do not play any game that needs a newer driver than 373.06

    Affiliate Code: E5L3CTGE12 & Associate Code: 9E88QK5L7811G3H  NoDarkSkies


     
    #22
    valkyriesII
    SSC Member
    • Total Posts : 863
    • Reward points : 0
    • Joined: 2009/05/12 17:23:37
    • Location: Washington
    • Status: offline
    • Ribbons : 2
    Re: Drivers 376.09 and 376.19 still no fix for FaH (Core21 on Maxwell/Pascal GPUs). 2016/12/10 11:08:50 (permalink)
    Yeah, it is pretty much like:
     
    FAH: Your driver broke our stuff.
    NV: No, we fixed some bugs and made some improvements. You were running into a bug and doing it wrong. You are trying utilize this bug as if it was a feature and need to fix it on your side.
    FAH: It worked in the previous version driver so you need to fix it.

     
    I see this quite frequent in software with finger pointing dragging out issues out longer than they need to be. Someone just needs to step up and fix the issue. At the end, it is the end user that suffers. Hopefully, it will be fixed soon.
    #23
    drougnor
    CLASSIFIED Member
    • Total Posts : 2721
    • Reward points : 0
    • Joined: 2006/07/18 05:57:59
    • Location: FL USA /Affiliate MCK692UUS /Assoc HPW7E9T81P8KCCH
    • Status: offline
    • Ribbons : 18
    Re: Drivers 376.09 and 376.19 still no fix for FaH (Core21 on Maxwell/Pascal GPUs). 2016/12/10 12:35:03 (permalink)
    bcav - That older post isn't a response to the latest nVidia info we have. If it was something they'd released yesterday, then I'd see it that way.

    Honestly, NVidia is doing it the right way - As valkyriesII said, it looks like NVidia uncovered a previously hidden bug, quite accidentally most likely, and has give the information over and is also willing to provide a way for things to go back to the way they were for those of us who are folding. Kind of a 'No Harm, No Foul' patch.
     
    I'm now really curious to see if that NVidia optimization would improve PPD for us, if the OpenMM bug IS patched. . .
     
    d


    #24
    bcavnaugh
    The Crunchinator
    • Total Posts : 38123
    • Reward points : 0
    • Joined: 2012/09/18 17:31:18
    • Location: USA Affiliate E5L3CTGE12 Associate 9E88QK5L7811G3H
    • Status: offline
    • Ribbons : 276
    Re: Drivers 376.09 and 376.19 still no fix for FaH (Core21 on Maxwell/Pascal GPUs). 2016/12/10 12:59:03 (permalink)
    drougnor Yes I do know, But is why is Folding @ Home Not saying anything at all.
    I will stop posting about the last 6 Drivers Failing and allow once more for them to correct the OpenMM bug.
    post edited by bcavnaugh - 2016/12/11 10:14:03

    Affiliate Code: E5L3CTGE12 & Associate Code: 9E88QK5L7811G3H  NoDarkSkies


     
    #25
    drougnor
    CLASSIFIED Member
    • Total Posts : 2721
    • Reward points : 0
    • Joined: 2006/07/18 05:57:59
    • Location: FL USA /Affiliate MCK692UUS /Assoc HPW7E9T81P8KCCH
    • Status: offline
    • Ribbons : 18
    Re: Drivers 376.09 and 376.19 still no fix for FaH (Core21 on Maxwell/Pascal GPUs). 2016/12/10 13:58:51 (permalink)
    It's likely the same reason we have to pull teeth for any information at all - They're still just now starting to really focus on communications when that is something they should have tried to focus on over a decade ago. They have a LOT to learn and adapt to.
     
    d


    #26
    kougar
    CLASSIFIED Member
    • Total Posts : 2720
    • Reward points : 0
    • Joined: 2006/05/08 10:11:19
    • Location: Texas
    • Status: offline
    • Ribbons : 17
    Re: Drivers 376.09 and 376.19 still no fix for FaH (Core21 on Maxwell/Pascal GPUs). 2016/12/10 16:11:00 (permalink)
    valkyriesII
    Yeah, it is pretty much like:
     
    FAH: Your driver broke our stuff.
    NV: No, we fixed some bugs and made some improvements. You were running into a bug and doing it wrong. You are trying utilize this bug as if it was a feature and need to fix it on your side.
    FAH: It worked in the previous version driver so you need to fix it.

     
    I see this quite frequent in software with finger pointing dragging out issues out longer than they need to be. Someone just needs to step up and fix the issue. At the end, it is the end user that suffers. Hopefully, it will be fixed soon.




    Aye. Just ran into this whole mess two days ago, really hope they get it sorted out before everyone bails for the holidays. Six weeks is an absurd length of time for it to persist.


    Have water, will cool. 
     
    Don't forget to use an Associate Code at checkout for extra savings! Associate Code: FWBXGF17CKOMCIV
    #27
    ipkha
    CLASSIFIED Member
    • Total Posts : 2297
    • Reward points : 0
    • Joined: 2015/02/10 21:01:40
    • Location: Indiana
    • Status: offline
    • Ribbons : 6
    Re: Drivers 376.09 and 376.19 still no fix for FaH (Core21 on Maxwell/Pascal GPUs). 2016/12/10 20:18:32 (permalink)
    6 weeks isn't that much time in the grand scheme of things. I'd say it's about right for a bug hunt this size. The lack of empathy on the OPENMM coders part is about right for open-source projects like that. It's odd how all the boinc projects only use a few percent cpu load to synchronize their OpenCL and CUDA tasks while folding tasks use up the whole CPU core. I'd be surprised if Stanford fixes this by March of next year. It will now depend on OpenMM code being updated, followed by Folding core 21 being updated to use the fixed version, and the project updating their implementation to the latest core21 code. We just don't know how tight the integration actually is.


    #28
    DutchForce
    CLASSIFIED Member
    • Total Posts : 2360
    • Reward points : 0
    • Joined: 2006/12/04 14:25:44
    • Location: Netherlands
    • Status: offline
    • Ribbons : 52
    Re: Drivers 376.09/.19/.33 still no fix for FaH (Core21 on Maxwell/Pascal GPUs). 2016/12/14 11:20:44 (permalink)
    Just to keep this thread updated,
     
    NVidia released new drivers 376.33 WHQL today, but no fix for FaH yet.
    See NVidia forum post of Manuel Guzman:
    Official 376.33 Game Ready WHQL Display Driver Feedback Thread (Released 12/14/16)
     

    silverpulser said:
    Has the issue with Folding@home been addressed?
    ---------------------------------------
     
    ManuelGuzman:
    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.

     
    See also an update from NVidia posted by Scott:
    Got word from NVIDIA and this issue they are working on.--UPDATED 12/14
     
    scott@bjorn3d
    12/14 Update

    Hey Scott,

    Our efforts to get a resolution out by 12/14 has run into some roadblocks. The change suggestion we made for OpenMM needs more tweaks and our driver side workaround is close to being done but not complete yet. We plan to post a hotfix driver to unblock the Folding@Home users as soon as we have a workaround to share (within the next few days).

    We’ll keep you posted.

    Regards,
    Team NV

    post edited by DutchForce - 2016/12/14 11:25:18


     
    Folding Rig: Lian-Li PC-P50 | Corsair HX850 | MSI 890FXA-GD70 | AMD X4-965 BE | GTX980 Ti SC & GTX1070 SC
    #29
    bcavnaugh
    The Crunchinator
    • Total Posts : 38123
    • Reward points : 0
    • Joined: 2012/09/18 17:31:18
    • Location: USA Affiliate E5L3CTGE12 Associate 9E88QK5L7811G3H
    • Status: offline
    • Ribbons : 276
    Re: Drivers 376.09/.19/.33 still no fix for FaH (Core21 on Maxwell/Pascal GPUs). 2016/12/14 14:23:12 (permalink)
    I think that their are 4 or 5 Treads on this issue now.
    I'm getting confused now on what Thread I am on.

     
    post edited by bcavnaugh - 2016/12/14 14:25:43

    Affiliate Code: E5L3CTGE12 & Associate Code: 9E88QK5L7811G3H  NoDarkSkies


     
    #30
    Page: 123 > Showing page 1 of 3
    Jump to:
  • Back to Mobile