There's public API that allows to pause executing code. Also using a debugger (ida,wdasm etc.) you can simply step-in/pause, controlling each loop easily. Oh well, can't wait to get back from holiday and start the machine up.
Well it would help me if you took proper screenshots, the 'old way' means pasting the final screen from aquamark in paint then opening cpuz cpu+ram and gpuz. One screenshot with cpuz/gpuz and one with aquamark score is a no no.
Problem is loops will look irregular, people will report for nothing. I had 70hours with just 7 loops, 3 loops with SPi32 (like 15hrs/loop) and 4 without it ("normal" 4-5hours/loop). Decided to cancel it since everyone is sandbagging it anyway.
Just pray to the lords of electricity that the current power outages stop. This morning I was down to 10% battery on a run that just passed 60 hours.
I want to run a desktop cpu as well, but this really puts me off.