• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

FAH v7 issue

Toconator

[H]ard DCOTM January 2026
Joined
Jul 8, 2005
Messages
878
Ran into a weird issue while running FAH. I'm still using v7 as it integrates well with HFM.net and has been in use on all my boxen for years . After getting my shiny new 5060Ti (primarily for folding) and running it for a couple weeks I decided to update the Geforce driver to the latest 581.57 . The GPU then became disabled in FAH and I couldn't find a way to get it going. Tried going with the slightly older 581.08 driver with no success. Rolling back to 576.88 which is what I updated from fixed the issue. I did run FAH v8 for about a week but I dislike the lack of control thru HFM.net and being required to login with an account, etc. Just a heads up, newer Geforce drivers break FAH v7.
 
Base on available evidence and community reports, you can be confident that newer NVIDIA 581.xx drivers break GPU functionality in Folding@home v7. The issue appears to stem from driver-level changes in CUDA or OpenCL handling that v7’s outdated GPU core cannot interpret properly, causing the GPU slot to be disabled. Rolling back to version 576.88 restores compatibility because that driver still supports the older compute interface FAH v7 expects. Until FAH v7 receives an update (which is unlikely given its age), the best solution for those relying on HFM.net integration is to remain on 576.88 or another known-stable version.
 
Is v7 a 32-bit app? If so, then NVIDIA 5000 series GPU drivers don't support 32bit after a certain point I think. Not sure if this applies here or not.
 
Base on available evidence and community reports, you can be confident that newer NVIDIA 581.xx drivers break GPU functionality in Folding@home v7. The issue appears to stem from driver-level changes in CUDA or OpenCL handling that v7’s outdated GPU core cannot interpret properly, causing the GPU slot to be disabled. Rolling back to version 576.88 restores compatibility because that driver still supports the older compute interface FAH v7 expects. Until FAH v7 receives an update (which is unlikely given its age), the best solution for those relying on HFM.net integration is to remain on 576.88 or another known-stable version.
Update: after a recent Windows 11 Update which forcibly replaced the 576.88 driver with version 591.86 FAHv7 is working fine. Haven't tried any newer drivers than that but those boxen are primarily folding anyways so no need. Fold on folks
 
Update: after a recent Windows 11 Update which forcibly replaced the 576.88 driver with version 591.86 FAHv7 is working fine. Haven't tried any newer drivers than that but those boxen are primarily folding anyways so no need. Fold on folks
Why not give a test run on FAH v8 client? https://foldingathome.org/guides/v8-5-client-guide/.

I used it in the past two annual FAH challenges and generally I like the interface and it keeps the completed work unit history (project id, credit and run time). If you have multiple computers running at the same time, you can see the work unit history for all the running PCs.
 
I can log into the web v8 and access any of my machines all on one interface. I can view logs, start and stop work, configure clients. Anything you can do locally, you can do from the web app. I hated it at first too. It made no sense, and I couldn't use HFM.net. Now I don't miss HFM.net at all. Dig around in that v8 client, it is far more flexible than you think.
 
Back
Top