Folding Forum

Issue should be fixed now.

I came across the software Process Lasso on here today, so have it already installed on my Windows machine. I'm just curious if there are any benefits to using it, and how to. I use the Ryzen 3400G to feed my GTX 1650, don't have any performance issues with me using the computer for anything else. ...

What issues was core26 having? I've never experienced any issues with it on Nvidia with OpenCL, Nvidia with CUDA, or AMD with OpenCL. Not seeing CUDA on certain OS hardware combinations. Core folds on CPU if Intel GPU is present. Core fails on certain AMD hardware scenarios. No HIP (not an issue, b...

Correction : v8 client is broken and doesn't make a difference between each "slots" you have configured. So if you have one CPU slot and on GPU one, it will alternatively report returned WUs as CPU and GPU in Recent CPU page. For some reason, Joseph decided that Machine IDs were no longer ...

CUDA_ERROR_ILLEGAL_ADDRESS (700) is usually a GPU or driver reset.

I'm seeing between 25 and 40 million PPD on the H100 I'm running for a couple of days ... the 120M on Lars is probably another example of the level of trust we can have on this site ...

It used to be caused by network devices using aggressive protection (like Deep Packet Inspection) that was altering FAH network packets. Kaspersky and Fritzbox router were well known offenders, but there might more cases where it might happen. There's a post on Discord about Kaspersky : https://disc...

All "dumped" WU by v8 client are reported to (Run 0, Clone 0, Gen 0) of the project. I don't know why Joseph doesn't fix this bug (it's a WS bug as far as I remember), it's been here for a very long time ...

06:44:50:I1:WU269:ERROR:Guru Meditation #6a6fa21db879dcae.47018a7a424ec6e2 (14621.17230) 'aqglezsapduPAa44rC_rXPzXVe-6QMe9WP0YFIHrzrQ/01/dhdl.xvg' 06:44:50:I4:REQ2:> HTTP/1.1 101 HTTP_SWITCHING_PROTOCOLS 06:44:50:E :WU269:Core returned BAD_FRAME_CHECKSUM (112) 06:44:50:E :WU269:Run did not produce ...

This feature made sense when it was designed during the COVID surge. With more compute power available than work, it allowed FAH to get faster returns by shortening the wait before reassigning work.

But it's completely useless now we have more work available than compute power to complete it ...

You are storing your client data to a drive called S:\ ... what is it ?

A friend found a strange workaround on Linux for this, so you might want to try it on Windows too. Find the gpus.json file in s:\ProgramData\FAHClient and delete it. Then restart the client (or reboot the whole system).

Efficiency usually peaks with x60 model of each generation ... it sometimes shifts a little bit toward x70 depending on the costs and power draw.

I discovered that I was able to add new members to the beta testers group, so I tried to add you.

Let me know if it worked.

I also finally added PaulTV and BobWilliams757 !

This project uses a bugged code in OpenMM that prevent it from working well on newer GPUs ... this bug is fixed in core 26, but it has other issue that must be fixed before moving to it. :( If we disable NV species 7, it will also take down high end GTX 1xxx GPUs that are doing fine on this project ...

From a terminal, try : What output do you get ?