It happens from time to time for a number of reasons. Mainly it's because the machine was shut down incorrectly or lost power, not in this case though. It also happens if you close folding by using the X, it needs to be closed by Ctl-C.....and sometimes it just happens for no apparent reason. Looking at your log, you need to close down folding and restart as you are in standard loops and it'll take an age like that . I use the -forceasm flag which forces the assembly methods, bypassing the check that folding does on restart. I don't know which file system you use, but NTFS handles improper shutdowns much better than Fat32, probably over 90% recover O.K, with Fat32 its likely to be less than 20%.

A WU or any other intensive process has to be shut down in stages.. first the process halted or paused, then final computations for that stage finalized.. then the data cached. Then the final process steps are written as a hard file. Now the process can be terminated entirely.

Likely a very brief "blip" on the power mains caused a restart.. and any active processes were not recorded. Has happened to me many times!
The PSU in any computer has less than 1/2 second of reserve storage power. Where most electronic devices may ignore this brief "blip", a computer would be affected by it.. and likely restart.
It would also occur if you did a hard reset after a freeze or BSOD.

Pette Broad wrote:It happens from time to time for a number of reasons. Mainly it's because the machine was shut down incorrectly or lost power, not in this case though. It also happens if you close folding by using the X, it needs to be closed by Ctl-C.....and sometimes it just happens for no apparent reason. Looking at your log, you need to close down folding and restart as you are in standard loops and it'll take an age like that . I use the -forceasm flag which forces the assembly methods, bypassing the check that folding does on restart. I don't know which file system you use, but NTFS handles improper shutdowns much better than Fat32, probably over 90% recover O.K, with Fat32 its likely to be less than 20%.

Pete

I'm running Windows Vista with NTFS. Folding is running as a service. I'll have to check on the -forceasm setting, I'm not sure about that at the moment.

There is a termination process that closes all programming and features whenever a reboot or shut-down is enacted.. but not present whenever a power interruption occurs.

If a system is rebooted manually, or automatically by update processes, then there should be no problem with files/programs becoming corrupt. But when very minor power glitches enter the equation, the system will reboot due to loss of stable power.. which only a 'line-tamer' or UPS can alleviate.

Uncommon to note a power "blip" during heavy-use periods.. the lines are loaded, and surges are absorbed into the system (mains). But during light-load periods, very brief surges may cause voltage levels to fall very briefly.. by 20% below normal, which can trigger the PSU to loose its power conversion process.. and loss of mobo power.
If the problem is frequent, then notify the utility company of the incidents.. and request a monitoring recorder on your lines, to gather evidence of those surges that shouldn't be present.

The primary root of the problem isn't from the power mains.. it is in the storage capacity of the PSU's main capacitors. If doubled in capacity, they should have at least one full second of reserve.. virtually eliminating most minor mains glitches.