Uh... If they check the results on a second machine that happens to experience the same problem as the first machine...

NOT the way to do valid science.

Fortunately, I stopped caring a long time ago. Perhaps I should just stop donating the cycles? I probably could have won a Bitcoin lottery by now if I had chosen that scam over the hope of helping research.

Oh yeah. Just checked and found two more. I should check the other Windows 10 machines, but why care? (And haven't seen much evidence of concern from the new managers of WCG.)

Can one of the users who are experiencing this issue please try the following:

Let us know what you currently have the setting "Use no more than: X% of processor time" set to. Then change that to 100%. See if that makes the issue go away.

Also - please go into log options and select app_msg_send - watch for the issue to re-occur and then post the messages from this log.

I am working with a user via the support box where it appears that the suspend and resume messages sent to throttle CPU usage are not being processed fast enough and so the boinc client keeps killing and restarting the research app which causes it to continually restart from the last checkpoint. This only occurs every few minutes but it is enough to prevent it from making progress.

Seems to work!

@Felix - thanks for trying that change and letting me know that running it at 100% did in fact allow it to run to completion.

I would appreciate it if other users who experience the long running tasks could follow the steps I outlined above so that we could confirm that this is what is going on. Thanks.

shanen0, can't you try that for just one work unit on one core like I did? I generally prefer lower settings as well, but knreed needs some help to solve the problem.