It seems that nobody is reading this thread as no reply from Admin in 2 days. Time to move to another project then.

Isn't there a way to specify the process names which should be throttled?

yoyo

In TThrottle there is a way to add processes to the recognized list.
I tried using it for YAFU sub processes, but failed after an hour of attempts, so resorted to a global throttle of ThrottleStop (which was already installed and ready to go).

I just tried setting BOINC Manager to 75% maximum CPU usage and it is properly throttling gnfs-lasievexxx today as the processes are going gray for split seconds avery few seconds in process manager. (I remember that prior version of BOINC wasn't doing this but my memory is getting older now and might not be reliable).

So BOINC Mgr can throttle YAFU and protect the CPU from overheating and the OP's problem should be solved.

@marsinph, if you set BOINC to use at most 6 cores then you can only run yafu, yafu small composite and yafu-4t. If you made changes to app_config.xml to allow for 16t by setting virtual core count to 16, then 75% of 16 is 12 cores. At 12 virtual cores you are still using all 8 real cores on Yafu, Yafu composite, Yafu 4t and Yafu 8t if you haven't set specific core and thread counts for each work unit.

So if your virtual core count is 16, you need to set BOINC to 37% or change the app_config.xml (or delete it).

EDIT: Forgot this thread was about 4t only. BOINC setting to 80% CPU is working fine for a 4t WU on this laptop as I type this. Using Process Hacker to watch the WU throttling down.

Regarding runtime prediction an percentage which is displayed in BOINC.

At the end the runtime is not predictable. Only a max runtime is predictable. Therefore I give the workunit this max runtime estimation.
But very often the workunit is much faster, only seconds or minutes. This is because we are doing kind of trial factorisation and very often those trials leads to finding a factor and the workunit finishes much faster.
BOINC "learns" from such computations and "thinks" that a workunit needs only a fraction of my estimation. Based on this BOINC shows the percentage of completion. This percentage is NOT done by the yafu application.
If a workunit doesn't find early factors during this trial factorization it has to go the full NFS (number field sieve) way. When BOINC sees that the workunit takes much longer, the percentage increase is slower and slower and might stay longer time at 100%.
During this last phase NFS writes a checkpoint file nfs.dat. This is used for restarting the app and to continue from the checkpoint.
The nfs.dat is roughly update every 45 minutes.

I also had a task with a given duration of some hours (2 or 3 ), then it reached 100%, and did never finishe. after several hours I had to cancel it via GUI :
https://yafu.myfirewall.org/yafu/result.php?resultid=4952792

Could this be some sort of Windows or Windows 10 error?

CoolAtchOk has Windows systems, I have Linux, I have not seem any evidence of freezing taking place.

His computers are much larger than mine and he says running single WUs or multiple work units at once makes no difference. I don't see any errors related to failed work units so they must all complete somehow.

I only run one WU at a time, the only thing I have noticed is that the multithreaded work units often seem to only use a single core but hold all cores (going on final times reported with run time and cpu time the same).
Could this be an issue with Windows not able to get any cpu time for other things it needs to do (basic house keeping), or perhaps it is a memory issue with it being tied up by the WU and not released so Windows can use it.

Not sure about marsinph, don't know if he is using Windows or Linux, if Windows I don't know if Windows 10 or not.

I know I am not really helping but offered help no matter how poor can still be of some help, sometimes.

Conan

I don't see a freeze on 3 different systems (windows7, 10 and Linux) even if I configure 32 cores to use on a system which has only 4. So I assume this has something todo with your system. I do not understand how the system is frozen if yafu didn't consume any cpu as you described above.

Runtime and cputime is meassured by BOINC client.
Don't know how and why it is wrong.
Maybe child and subchild processes are not considered correctly.