World Community Grid - View Thread - WinXP Clock Alignment causes HPF2 Segment Restart

Set the clock of the OS at 22:04:24 as it was running 2 minutes fast from the one at time.nist.gov. Right when forcing the alignment, the HPF2 jumped back a segment as did its CPU time and generated following log entry in BOINC:

06-07-18 22:04:26|World Community Grid|Task za114_00135_2 exited with zero status but no 'finished' file
06-07-18 22:04:26|World Community Grid|If this happens repeatedly you may need to reset the project.
06-07-18 22:04:28|World Community Grid|Restarting task za114_00135_2 using hpf2 version 507

After this the WU progressed normally.

I'd disabled the system clock auto-alignment with the internet, which is maybe the reason never seeing this error type before. It may be a reason why more are having problems believing they have a faulty WU and abort. According a post at BOINC Wiki it is though normal 'to be expected' behaviour ....to Quote:

The most common cause I've found on CPDN is the windows time sync. Doesn't do it on my machine, but many people on the forums experience it when Windows does it's automatic sync (or if they manually request a time sync)...........The few times I have had this message it was cause by another program (a P2P in my case) locking up the CPU for a short time, causing the Boinc to time out on its communication to the client software. The WU completed and reported properly.

The Unofficial BOINC Wiki has an extensive coverage: Result '(result)' exited with zero st...o 'finished' file

Likely any software utility that synchronises the system clock with the internet, (multiple times) daily / weekly, is causing this, the source not immediately obvious as these adjustments normally would only be a few seconds if automated. Dont know if UD agent suffers same event, no log to proof of course.

Be warned!