Folding Forum

Power usage grows exponentially as voltage is increased to hit higher clock speeds. By limiting power you're avoiding the worst part of the efficiency curve. This article has a table showing FPS at various power limits on RTX 2080 Super that correlates with your results. Here's a graph for an RTX 40...

Before reinstalling, first try deleting GPUs.txt. There should be an entry in the Start menu for "Data Directory" that should launch File Explorer. Delete GPUs.txt from that folder and then restart your computer. Please re-post the log if it doesn't detect the GPU as supported.

Missing credit for project:16462 run:10 clone:4 gen:29 completed Dec 26.

What GPU and Windows version was this? Have other GPU work units run successfully?

You can try disabling any security software or firewalls that could be slowing the download or interfering with unpackaging. If you can bypass your router and connect your modem directly to the PC, that might help as well.

No, it has not. GPU does not fold any more. The WU has expired, and the client doesn't care. Instead, it thinks that the expiration is in 2^64 seconds. I cannot manually reject the WU, and so GPU folding is no longer possible for me. You can remove the work unit by right clicking and pausing the sl...

You mean that running just 1 slot with 12 threads might get higher PPD than 1 slot with 24 threads? Whats would be the reason for not using all the HT? FAHCore_a8 does a better job of keeping execution units busy than FAHCore_a7. Spawning and syncing the extra threads that use HT might be slowing t...

It looks like the issue is fixed and was some kind of compatibility problem of the WU with the amd graphics firmware. After upgrading first Linux kernel from buster-backports 5.6 to 5.7 and then firmware-amd-gpu from buster-backports 20190717-2~bpo10+1 to 20200619-1 from testing, the problem vanish...

I really wonder how we could get enough statistics around that... the client doesn't track driver version, I assume? The client knows the driver version but I don't believe that the FAHCore places that information in the error report. That would potentially be an enhancement for the FAHCore. On Win...

You're log shows Windows so go to Start and type Command Prompt. Then type the following and press Enter tracert 143.89.243.111 To copy the result, right click the window, click Select All, and press Enter to copy to your clipboard. When posting, you can remove the first couple hops that contain you...

Those bits took a long time to arrive from Hong Kong at 0.07 mbps! The server might be busy or your ISP might not have a good peering relationship with the transit provider. Can you do a traceroute to 143.89.243.111 and see if anything looks amiss?

At the moment I have two of these WUs, one standing at 110kPPD and using about 10% CPU, the second standing at 545kPPD and using about 26% CPU. I remember that also earlier WUs coming out at about 100kPPD took about 10% CPU (looked for that, since I wondered whether just CPU load is blocking, but d...

Things get even more confusing. In the moment I have four 16918 WUs on the system, two of them run at approx 105kPPD (16918,147,83,11 and 16918,84,91,5), one at 497kPPD (16918,133,23,14), one at 767kPPD (16918,64,21,11). So it can not be only the system setup with four Radeon VII, it somehow has to...

Here is the output of rocm-smi -a. GPU 0 and GPU2 have been paused, GPU 1 and GPU 3 are each running 16918 WUs at a little over 110000PPD. rocm-smi is a just moment in time but the reported numbers are interesting. Temperature: GPU 1 and 3 are warmer fclck/socclk: GPU 2 and 3 are higher Average Gra...

Here is the part of science.log. I pasted from the beginning of the file, so that the setup is visible. The CPU is running a WU on 12 of the 24 cores, so plenty of free capacity on the CPU. The PRCG is 16918,124,3,9. Four other WUs from the same series are currently running with similar performance...