interim residue sent to server twice?
 

I'm using Prime95 version 29.8 on my new laptop to finish up some partially complete LL tests (from computers I no longer have access to) before switching to 30.3 for PRP. As this is a new computer, I'm running LL double checks first to make sure the system is stable. It has a six-core processor, and one worker is assigned to each core.

I was checking [c]prime.log[/c] when I noticed an interim residue was sent twice:

[QUOTE][Wed Oct 28 20:03:46 2020 - ver 29.8]
Sending interim residue 35000000 for M58797119
Sending interim residue 35000000 for M58797331
Sending interim residue 35000000 for M58797103
[Thu Oct 29 09:05:13 2020 - ver 29.8]
Sending interim residue 35000000 for M58797043
[B]Sending interim residue 35000000 for M58797367[/B]
[Thu Oct 29 12:56:09 2020 - ver 29.8]
Updating computer information on the server
[B]Sending interim residue 35000000 for M58797367[/B]
Sending interim residue 35000000 for M58794581
Sending expected completion date for M58794581: Nov 09 2020[/QUOTE]

Is this supposed to happen under certain circumstances?

Assuming this is not the case, here's the sequence of events that might be useful in reproducing the issue:
[LIST=1][*]Prime95 sends interim residues for three exponents that had passed 35 million iterations[*]Two more exponents pass 35 million iterations and a [C]prime.spl[/C] file is created[*]To conserve power, I put the computer to sleep in the evening[*]The computer reboots in the early morning due to a system update[*]Prime95 sends interim residues for those two exponents after starting back up[*]The remaining exponent passes 35 million iterations and a new [C]prime.spl[/C] file is created[*]Prime95 sends estimated completion times and what is supposed to be one remaining interim residue[/LIST]

I may have found the cause. It's possible that the worker had just passed 35 million iterations when the system rebooted. Windows is supposed to politely ask processes to terminate, but it's been reported that this doesn't always happen.

Prime95 stores interim residues in a [C]prime.spl[/C] file and only sends them at certain intervals. So when Prime95 started back up, the data in [C]prime.spl[/C] was sent to the server, but the worker's progress was rolled back to a point before 35 million iterations. After crossing the threshold again, the interim residue was sent a second time.

It turns out my new laptop sometimes reboots when waking up from sleep. This is apparently an issue with some Windows 10 devices. I should probably open a new thread as this is not a Prime95 issue.

The "Prime95 issue" is why do you put your computer in sleeping mode during P95 is running? :razz: (these two situations are a bit antagonistic, aren't they? hihi - do you intend your computer to sleep during it's idle, or to crunch some numbers?)

[QUOTE=LaurV;565614]The "Prime95 issue" is why do you put your computer in sleeping mode during P95 is running? :razz: (these two situations are a bit antagonistic, aren't they? hihi - do you intend your computer to sleep during it's idle, or to crunch some numbers?)[/QUOTE]

Our electricity costs are already a little high due to heaters. :sad:

Yuck! :yucky:
1. Replace heaters with vees (i.e. Radeon Vii).
2. Profit!