No progress during first 30 to 90 minutes on Ryzen 3700X, Windows 10

Hi everyone,

I'm a happy cruncher for Einstein@home for quite some time on Windows and Linux. Just a few weeks ago, I bought a new system, a Ryzen 3700X with 32 GB RAM, an NVIDIA 2070 Super, and an Gigabyte Aorus X570 Elite Mainboard. Everything runs perfectly, hardware is checked and no problems could be found. However (topics 1 to 3 are minor issues only, but could be helpful by indicating something - that's why I included them here although they are actually off-topic):

1. As typical, I ran BOINC under Ubuntu 19.10 (will transfer to 20.04 LTS for several reasons) and found that Einstein@Home did not load any workunits for the GPU (it did so for Asteroids@Home, where the GPU worked nicely). However, I only tried for two days, so it could be a mere coincidence that no GPU workunits were downloaded. GPU-workunits for Einstein@Home are, however, loaded and executed under Windows 10. That's why I switched to that OS for the moment.
2. From here on, both Linux and Windows 10 are affected: There are now exactly twice as many workunits active as I have cores (16 to 8). As far as I have read, that is normal and has to do with the Ryzen reporting two threads for each core. I'm not sure whether this is efficient, but I trust the developers here.
3. At first, the CPU-workunits raced up to around 25% progress, only to be reverted back to 0% after 50 minutes to 70 minutes. CPU-time then is 0 as well. I understood from different threads that this is a common behaviour. Is that necessary? I never observed that on my other (Intel) systems.
4. The worst problem: whenever I start calculating (e.g. after booting, or pausing Einstein@Home), there is no progress for around 30 to 90 minutes (today even more, nearly 120 minutes). This is true for all workunits, no matter how far they have progressed or what kind of calculations the do (Gamma-ray pulsar search as well as graviational wave search). CPU-time counts up, but there is no progress. All workunits are affected in the same way. They all need the same time (probably not to the second) until they start. Temperature readings of the CPU show that it does calculate something, but it is clearly below the normal working temperatures at full load. See second edit for a remarkable exception!

Since I often run my system only for a few hours, waiting for an hour or two every time is very annoying. Since both, Windows and Linux, are affected, but not my other computers, there seems to be some issue with that particular computer.

I have no other programs/apps/processes running, just the OS and their typical background load (1% to 4% typically). Asteroids@Home is paused at the moment as otherwise I would never get Einstein@Home calculating. Sorry for using your time and many thanks for every kind of help! Clear Skies,

Guenther

Edit: Just after finishing this post I was so frustrated that I installed something, CPU-load went above 25% and BOINC paused all workunits. A few seconds later, all continued.  Still, after starting BOINC, no workunit of any kind progresses. Many thanks!

Edit: If a workunit reached 89.979% it "get's stuck", thus shows no progress. However, after some time (around 2h), it jumps directly to 100% and thus finishes. Fine. Interestingly, this is also possible if calculations are in the state described in point 4. So for late-stage workunits above 89.979%, point 4 does not apply!