Folding Forum

To avoid 13420 until the next sprint with new project numbers, you could block connections to 18.188.125.154. This would avoid repeatedly thrashing work units but it might take longer to get work. Can you run roc-smi and post the output when one of your GPUs has a 16918? You could try running two sl...

I don't have a high core count machine to test on, but this is my theory: At 16 and 32 threads, the OS is preempting FAH more often than when there is 1 physical core free. In the 17-23 range, 1 of 17 (5.8%) to 7 of 23 (30.4%) of threads are bouncing around taking CPU time from 16 threads allocated ...

16900-16919 except 16918 have low atom counts, i.e. less than 15K. If it was one of those other projects, it would be explainable since the Radeon VII is wide with a large number of shaders. Can you go to science.log in the work folder and post this section? Stream copied, deserializing... Checking ...

Technically speaking, this is a legitimate addrress which could be on your LAN. It doesn't belong to Windows or Apple. The unanswered question is why is it appearing when the GPU you've attempted to configure is unsupported. The GPU is supported based on Device ID but OS X is not. When the client r...

Did you try pausing CPU folding when you had one of these slow work units?

I have FAHCore_A22 at below normal priority, and FAHCore_A07 at idle. Only 6 of 8 threads are assigned. Good, that should leave enough CPU time available for FahCore_22.exe. 13416 writes to disk 10x more frequently than 13418. Is the FAH work folder on an SSD? Do you observe any CPU time used by an...

Are you running CPU folding as well? Some work slower 1341x work units use more CPU time on AMD GPUs. Increasing the priority of FahCore_22.exe or reducing the number of cores allocated to a CPU slot may improve performance.

Since 2020-07-21T01:25:46Z it's taken 2-5 attempts to get a CPU work unit on Windows for cpu:2. Several of the servers listed as down on the server status page were hosting CPU projects, listed as GRO_A7 in the project types column.

The last part of your log shows an assignment to 3.133.76.19, which only shows as having CPU work on psummary. Have you tried deleting and recreating the slot?

without shutting down rosetta a 13416 finished OK on the RX5500. another 13416 is now running on the RX5500 and the frame times are back into the 6 minute range. i don't know if they tweaked it or it's just the natural variation in these WUs. clearly though looking back thru HFM i can see that i've...

Exception access violation appears to happen at 5% intervals, which would be around when a checkpoint is written. Did you try to view any of the files in the work folders using another application? Perhaps the core didn't close a file properly when the 25% checkpoint was written so subsequent checkp...

p17201 - max 4x4x4 - PME load 0.17 2 = 2x1x1 3 = 3x1x1 4 = 4x1x1 6 = 3x2x1 8 = 4x2x1 9 = 3x3x1 12 = 4x3x1 16 = 4x4x1 18 = 3x3x2 20 = 4x4x1 16 + 4 PME 21 = 4x4x1 16 + 5 PME 27 = 2x3x3 18 + 9 PME 32 = 3x4x2 24 + 8 PME 40 = 4x4x2 32 + 8 PME 42 = 4x4x2 32 + 10 PME 44 = 3x4x3 36 + 8 PME 45 = 4x3x3 36 + 9...

HannuN, thanks for the reports! Could you include the project number for the most recent occurrence?

As a ~10M point a day folder, I'm about ready to jump ship I'm so frustrated. I have 29 clients and a good % of those are running 54 cores. I've been seeing the issue with 58 cores as well. Today has been horrible for this issue. It's just been getting worse over time. I wish the client would adjus...

Can you post the contents of science.log? It would be in C:\Users\Frank\AppData\Roaming\FAHClient\work\##\01\

You could try a different GPU driver version to see if that has any effect.