Folding Forum

This WU failed for everyone who tried to run it. It may be a bad task or it might have been expected to fail by design.

https://apps.foldingathome.org/wu#proje ... =49&gen=35

Post the latest log output, preferably with a period of time without FAHControl running to see if that is what causes the error 97. Also post the current config.xml contents.

From posts by others with the "Receive error: 997" problem, it may be caused by running FAHControl and might not be a real problem that prevents folding. The log file you posted showed it attempting to get a connection to the assign1 and assign2 servers, but was failing due to the proxy on...

In FAHControl on the Proxy tab, uncheck "Enable proxy configuration" https://foldingathome.org/support/faq/installation-guides/configuration-guide/?lng=en If it's not checked and the proxy-enable v='true' line is still showing in the log output, it may be confused. You can try checking it,...

Monitoring the CPU temperature would show if it's reducing the boost due to hitting 100C. A large CPU cooler will allow the system to boost higher for longer. With a 13th gen CPU, you will want to use a tool like Process Lasso (https://bitsum.com/) to keep the FahCore process using only the performa...

I haven't used cpulimit on the folding app other than testing it briefly to see that is appeared to work as expected. So I don't know if it causes any problems with long term use. I think you should test it and report back.

Not sure how you are evaluating folding speed. The points per day will vary up and down and takes time to stabilize after starting a work unit and varies from one project to another. A utility such as HWiNFO will show if the CPU is overheating and the boost frequency is being throttled or if the pow...

The github project's documentation describes how cpulimit works:

https://github.com/opsengine/cpulimit

The control of the used CPU amount is done sending SIGSTOP and SIGCONT POSIX signals to processes.

It seems to pause and resume the process for short intervals.

Could see if the problem also happens under Linux. That might show if it's a Windows problem or a hardware problem. Performance may be better on Linux than Windows anyway. At least on GPU work units, Linux performance is better most of the time. The LAR Systems database doesn't split CPU stats by OS...

Someone else who previously had this error 997 and an AsRock X470 motherboard reported that a BIOS update fixed the problem. If you don't have the latest AMD chipset drivers, you could also try that. Hope you mean the OS is Windows 10 Pro for Workstations in order to support multiple sockets and tha...

What's wrong with SiDock from Russia? Some may have issue with supporting a project based in a country where its citizens don't sufficiently protest the war and war crimes against Ukraine. Then there is the Russian government and the Russia-based Internet Research Agency's history of cyberattacks a...

Each project has its own timeout and deadline set. Timeouts vary from 1-7 days and deadlines vary from 2-10 days. https://apps.foldingathome.org/psummary See the FAQ at https://foldingathome.org/support/faq/running-foldinghome/?lng=en These times can be viewed using FAHControl while processing a wor...

The cpulimit command can restrict CPU use by percentage. It might also be possible using cgroups, but I haven't tested that.

Example to limit to 50% CPU on a 32-thread system:

My systems are plugged into a Kasa/TP-Link KP115 energy monitoring smart plug. It pairs with a phone app that shows realtime power use and also keeps a total of kWh used over the last 7 or 30 days. Before that I used a Kill A Watt which failed catastrophically and melted after less than a year, then...

More than once recently I've seen WUs that are stuck at 99% for a long time. The log shows the progress stop between 92-98%. Then if it's paused and resumed, it restarts at 92-98% and will then finish. The most recent one is Project: 12414 (Run 8, Clone 1, Gen 21) that stopped and restarted at 92%.