Yes, it doesn't help. Beside that there are a lot of hosts that I simply can't babysit all the time.
I have only one Linux machine running right now (Linux Mint 19.3, Core Duo with 3GB of RAM), where I don't think I have ever seen this problem.
I have seen this IIRC once on my my Macbook Pro (i7 8T, 8GB RAM, High Sierra), but otherwise across a wider range of Windows hosts, including Windows 7, Windows 8.1 (the very machine I am typing this) as well as Windows Server 2003, besides Windows 10. So I don't think that this is a Windows 10 specific issue, I just mentioned this initially because in the past, some people have been harping about the fact that it might have been an older CPU, or Windows version or not the latest BOINC client. But there doesn't seem to any obvious circumstances when this happens and I usually only notice this when I check the daily stats and notice a larger than usual deviation in the points for a stats update.

Ralf

I have the same problem in one machine with Win10. But rebooting the machine has always helped the problem. The hard disk in the machine is failing and I've think that is the reason.

Same here. On Windows, I always suspect the anti-virus for hanging up work. It may help to exclude the BOINC folders, but that may not stop the real-time monitoring processes from interfering as they inspect the work, or else the communications on the Internet.

You say neither suspending nor rebooting has solved the problem. Have you tried a complete shutdown and then a cold start ?
After the cold start, I would snooze BOINC and see if any unknown processes are running and/or using an inordinate amount of cpu cycles. Then I would suspend every running work unit and only leave the affected one running and then see if it progresses normally as the only one running.
The only other idea that comes to mind is a memory problem which is causing a memory bottle neck someplace.
Cheers