Page 1 of 1

FahCore_17 - Information & Unresolved Issues

PostPosted: Thu Nov 21, 2013 12:23 pm
by PantherX
Please note that since the release of FahCore_17 to Full F@H, there have been few reported cases of possible issues with FahCore_17 which weren't caught in any of the previous testing. This makes sense since there are several supported GPUs and previous testing could only accommodate so many. This thread attempts to provide a list of unresolved FahCore_17 issues so that the developmental team can view these issues and hopefully fix it in the next release. Aside from issues, you will find some additional information regarding FahCore_17

Officially Supported GPUs
AMD -> HD 5000 Series or higher
Nvidia -> GTX 400 Series (Fermi) or higher

Officially Supported Platforms
Windows 32-bit -> AMD, Nvidia
Windows 64-bit -> AMD, Nvidia
Debian/*buntu/Mint 64-bit -> Nvidia (you may need to set client-type to advanced)

Issues For AMD GPUs
1) FahCore_17 Version 0.0.52 crashes on a system while FahCore_17 Version 0.0.49 works fine. (Confirmed)

2) viewtopic.php?f=88&t=25246 (Unconfirmed)
FahCore_17 fails after a minute with ERROR:Win32: 0xc0000005: Exception access violation

3) viewtopic.php?p=252393 (Unconfirmed)
FahCore_17 fails with exception: Error invoking kernel execFFT: clEnqueueNDRangeKernel (-55)

Issues For Nvidia GPUs
1) viewtopic.php?f=61&t=25222 (Confirmed)
FahCore_17 Version 0.0.52 crashes on a system while FahCore_17 Version 0.0.49 works fine

2) viewtopic.php?f=80&t=25887 (Confirmed)
FahCore_17 Version 0.0.52 crashes on Nvidia Maxwell GPUs.

Common Troubleshooting Tips
1) Make sure that you are using current WHQL Drivers from AMD ( or Nvidia ( Nvidia Driver 331 Series may result in PPD loss on GK104 GPUs so 327.23 is recommended instead. Investigation is ongoing into this matter.

2) Make sure that the error isn't due to unstable overclock. Please note that a stable overclocked GPU while gaming doesn't mean it is stable while folding.

3) Make sure that the GPU is operating within reasonable a temperature zone. GPU-Z ( for Windows. PSensor ( for Ubuntu.

4) On Windows, upgrade to the latest FahCore_17 Version 0.0.52. Finish all WUs, exit FAHClient, locate the cores folder (default is %AppData%\FAHClient or %ProgramData%\FAHClient) and create a backup of it before deleting it. Restart FAHClient to automatically download the latest version. Alternatively, set your GPU Slots to Finish and once done, locate the folder FahCore_17.fah in the cores folder and delete it after making a back-up of it. If for some reason the new version fails, restore the old version and report it here on the Forums along with the log files.

Future Plans (subjected to change)
1) Attempt to fix FahCore_17 slow-down with latest Nvidia Drivers
2) Support Nvidia Maxwell GPUs
3) Attempt to fix low PPD issues on low-end GPUs
4) Native support for Debian/*buntu/Mint 32-bit with Nvidia GPUs
5) Native support for AMD GPUs in Ubuntu (waiting for stable drivers from AMD)
6) Support CUDA on Nvidia GPUs (waiting for JIT compiler from Nvidia)

Please DO NOT post your issues here. Create a separate thread for your issue in either the AMD (viewforum.php?f=81) or the Nvidia (viewforum.php?f=80) Forum. You may post here with a link to your thread and a brief description of what the issue is. If found to be a valid issue, it will be included in this post.

Thanks to bruce, Joe_H, P5-133XL & 7im who helped compile this list. Thanks for those donors who reported their issues.

Re: FahCore_17 - Information & Unresolved Issues

PostPosted: Wed Mar 19, 2014 10:17 pm
by PantherX
I have updated the first post to include the FahCore_17 issue on Nvidia Maxwell GPUs.

Please note that a temporary solution is to run v6 GPU Client ( since you can successfully fold FahCore_15 WU on Nvidia Maxwell GPUs. You can have V7 and v6 installed simultaneously on the same system. However, this workaround is limited to Windows only. Linux users will have to wait until development has released a fixed FahCore_17 version. Please note that there isn't any ETA as to when this issue will be resolved so please wait patiently.

Re: FahCore_17 - Information & Unresolved Issues

PostPosted: Thu Mar 20, 2014 8:11 am
by Kurtis200200
For our nvidia + linux community, it's worth nothing that the GeForce 600 series and below runs best on the 304.xx Legacy Driver series (64-bit link; 32-bit users should use this link instead.)
Edit: it appears that the 64- and 32-bit links are crossed in the above post. This is such because Nvidia itself has crossed them. As such, I'm reluctant to merely switch the links around in case they change in the future, and wanted to leave this notice instead.

Re: FahCore_17 - Information & Unresolved Issues

PostPosted: Sat Apr 05, 2014 4:21 pm
by ilkyest
on arch linux, 304xx driver are available with (pacman -S nvidia-304xx)

On linux, you should install nvidia-opecl to be possible folding on GPU... without it you will receive "bad working unit" without folding any
Code: Select all
17:22:22:WARNING:WU01:FS01:FahCore returned: UNKNOWN_ENUM (127 = 0x7f)

Re: FahCore_17 - Information & Unresolved Issues

PostPosted: Thu Dec 31, 2015 5:56 am
by Muhanada Klee

I just wanted to ask if it was compatible with INTEL HD 3000?


Re: FahCore_17 - Information & Unresolved Issues

PostPosted: Fri Jan 01, 2016 1:39 am
by Joe_H
Muhanada Klee wrote:Hello,

I just wanted to ask if it was compatible with INTEL HD 3000?


No. As listed in the requirements for the folding software, a nVidia or AMD-ATI GPU is required for GPU processing of folding WU's. The implementation of OpenCL is not usable yet on integrated Intel video.