I recently had an error that caused a temporary points glitch. It was a clock skew error, and increased my estimated points by around 33% while that frame was processing. I was folding only on a single GPU at the time, and as of the next frame the estimated points were back in line.
This was the first time I've ever encountered this error code, and I really have no idea what caused it. The system remained stable and kept folding just fine when it took place. It might be worth looking at your logs to see if you get a similar code.
Code: Select all
23:04:41:WU00:FS01:0x22:Completed 12500 out of 1250000 steps (1%)
23:29:17:WU00:FS01:0x22:Completed 25000 out of 1250000 steps (2%)
23:29:19:WU00:FS01:0x22:Checkpoint completed at step 25000
23:51:36:WARNING:WU00:FS01:Detected clock skew (4 mins 04 secs), I/O delay, laptop hibernation or other slowdown noted, adjusting time estimates
23:51:36:ERROR:Receive error: 10053: An established connection was aborted by the software in your host machine.
23:53:36:WU00:FS01:0x22:Completed 37500 out of 1250000 steps (3%)
00:18:08:WU00:FS01:0x22:Completed 50000 out of 1250000 steps (4%)
But then again it's also very possible that with three top producing cards you are breaking a server or something. The easiest way to fix this would be to send me one of the cards.
Your accurate estimate is about a year's worth of folding on my little integrated graphics Ryzen system. It's great to see users like yourself and dedicate so much in resources.
Edited to add the error code info.