Folding Forum

I just ran the tool on Windows 10 platform and couldn't see the client using any GPU cycles. On contrary, it seems to be using CPU. Expected behavior?

PS: NVIDIA drivers are installed on the system for games. Some troubleshooting reveals I/O rate is super high while using the CPU cycles.

You have to change what you are looking at when using Task Manager to see GPU load. Not a Windows folder, but others have posted here that you have to change to look at Compute and CUDA for a nVidia GPU.

Another option is to use a tool such as GPU-Z that reported the load information more directly.

Unfortunately, Windows is a graphical friendly platform and this forum does not allow to embed images in the posts otherwise I would have showed you the analysis from Process Hacker as well as Task Manager. I navigated specifically to the FAHClient.exe process running on the system to monitor the resource usage. I can only see CPU clock cycles and lots on I/O wight. No GPU cycles are being used by this application.

FAHClient is not the process that does the folding calculations. It handles downloading WU's and folding cores, and uploading of the results. In addition FAHClient starts and stops the folding cores that do the processing.

The processes you need to be looking at are named FAHCore_nn, where currently nn can be A7 for CPU folding, and 21 or 22 for GPU folding.

If you have a default install, then you will have a folding slot defined in the client for GPU folding and another for CPU folding. It is possible that one or the other is not active, FAHControl or the Web Control will display what slots you have and what they are working on.

You are correct. From the default install, FAHCore_nn does not seem to run on a Windows 10 platform system. I just see FAHClient which in turn seems to be using CPU.

Not sure if we need this behavior for default installations. Let me know what I can do on my end to resolve this.

06:59:37:************************* Folding@home Client *************************
06:59:37: Website: https://foldingathome.org/
06:59:37: Copyright: (c) 2009-2018 foldingathome.org
06:59:37: Author: Joseph Coffland <[email protected]>
06:59:37: Args:
06:59:37: Config: <none>
06:59:37:******************************** Build ********************************
06:59:37: Version: 7.5.1
06:59:37: Date: May 11 2018
06:59:37: Time: 13:06:32
06:59:37: Repository: Git
06:59:37: Revision: 4705bf53c635f88b8fe85af7675557e15d491ff0
06:59:37: Branch: master
06:59:37: Compiler: Visual C++ 2008
06:59:37: Options: /TP /nologo /EHa /wd4297 /wd4103 /Ox /MT
06:59:37: Platform: win32 10
06:59:37: Bits: 32
06:59:37: Mode: Release
06:59:37:******************************* System ********************************
06:59:37: CPU: Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
06:59:37: CPU ID: GenuineIntel Family 6 Model 158 Stepping 9
06:59:37: CPUs: 8
06:59:37: Memory: 15.96GiB
06:59:37: Free Memory: 10.69GiB
06:59:37: Threads: WINDOWS_THREADS
06:59:37: OS Version: 6.2
06:59:37: Has Battery: true
06:59:37: On Battery: false
06:59:37: UTC Offset: -7
06:59:37: PID: 1520
06:59:37: CWD: C:\Program Files (x86)\FAHClient
06:59:37: OS: Windows 10 Enterprise
06:59:37: OS Arch: AMD64
06:59:37: GPUs: 0
06:59:37: CUDA Device 0: Platform:0 Device:0 Bus:1 Slot:0 Compute:6.1 Driver:9.1
06:59:37:OpenCL Device 0: Platform:0 Device:0 Bus:1 Slot:0 Compute:1.2 Driver:388.57
06:59:37: Win32 Service: false
06:59:37:***********************************************************************
06:59:37:<config>
06:59:37: <!-- Folding Slots -->
06:59:37:</config>
06:59:37:Connecting to assign1.foldingathome.org:8080
06:59:37:Updated GPUs.txt
06:59:37:Read GPUs.txt
06:59:37:Trying to access database...
06:59:37:Successfully acquired database lock
06:59:37:Enabled folding slot 00: PAUSED cpu:3 (not configured)
06:59:37:Enabled folding slot 01: PAUSED gpu:0:GP106BM [GeForce GTX 1060 Mobile 6GB] (not configured)
06:59:37:ERROR:Exception: Failed to register systray icon: Unspecified error
07:00:38:Saving configuration to config.xml
07:00:38:<config>
07:00:38: <!-- Folding Slots -->
07:00:38: <slot id='0' type='CPU'/>
07:00:38: <slot id='1' type='GPU'/>
07:00:38:</config>
07:00:38:Set client configured
07:00:38:WU00:FS00:Connecting to 65.254.110.245:8080
07:00:38:WU00:FS00:Connecting to 65.254.110.245:8080
07:00:38:WARNING:WU00:FS00:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
07:00:38:WU00:FS00:Connecting to 18.218.241.186:80
07:00:39:WARNING:WU00:FS00:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
07:00:39:ERROR:WU00:FS00:Exception: Could not get an assignment
07:00:39:WU00:FS00:Connecting to 65.254.110.245:8080
07:00:39:WARNING:WU00:FS00:Failed to get assignment from '65.254.110.245:8080': No WUs available for this configuration
07:00:39:WU00:FS00:Connecting to 18.218.241.186:80
07:00:39:WARNING:WU00:FS00:Failed to get assignment from '18.218.241.186:80': No WUs available for this configuration
07:00:39:ERROR:WU00:FS00:Exception: Could not get an assignment

That's due to overloaded servers