I'm running long runs on this machine and they just cease all activity after 15% or so. Not a computation error, not paused for another higher-priority task, it just stops, but the run time keeps on ticking and it is still listed as running. There is no progress bar change, no GPU activity, no CPU activity. It seems suspending and restarting the task helps temporarily, but that's obviously not a good solution if I have to micro-manage each run like a hundred times. EDIT: Okay, it resumes by itself after 5-10 minutes, only to stop again shortly after.

This one runs the project on a GTX 1050, all going smoothly.

This is the output on the task page for a start-stop WU I ended up aborting, doesn't seem helpful:

It may be that this is related to the thread Problem with Pablo Tasks Specifically from the post that is linked to the end of the thread may provide a solution for you.
____________

Thanks. I did try this earlier, though, in that I checked whether the task would freeze after being suspended due to CPU use. But It continued normally after everything else resumed.

Still, I've set that to no restrictions and will check if it occurs again. The task is now at around 61% and running normally.

mkay, it hasn't happened since and the last task with this issue successfully ran to completion. I now got two tasks running on the same GPU and have an alert set up that tells me whenever the GPU load drops to near zero for longer periods of time. Nothing so far. Perhaps telling BOINC never to suspend tasks automatically really was the solution. Or maybe the multiple WUs.

By the way, what's the current stance on this? I was only getting a GPU usage of ~70% with one task (the 1050 Ti on my Linux machine has ~95%), so I played around with the project config file. Now with two it's up to ~87% and extrapolating the durations there seems to be some improvement indeed. I browsed a few threads here, but most of them were quite old, so not sure if it's recommended nowadays. Thanks.