That sounds like the known Microsoft Task Scheduler bug:-
"Every hour, the Task Scheduler service schedules tasks to be run over the next hour in a schedule window. If the start time of a task coincides with the end of the current schedule window and with the beginning of the next schedule window, then the task may be scheduled two times. In this situation, the task is scheduled at the end of the current schedule window and again at the beginning of the next schedule window."There is a Microsoft article & hotfix available here:-
http://support.microsoft.com/kb/2461249/en-us?sd=rss&spid=14019As there probably aren't too many users across the world that run scheduled tasks every minute while the PC is switched on, it appears that Microsoft has chosen not to include this fix in their general auto-update system.
Deleting & recreating the logging task at say 30 seconds past the minute may help to 'shift' the records of tasks scheduled to run within a given 1 hour window as a workaround.
I used to see the same issue on my W7 system, but I downloaded & applied the hotfix which acted as a permanent cure.
Older versions of
HG612_stats.exe would leave behind the
ONGOING-ISRUNNING files.
The later versions now record these instances in the log you posted & delete the files.
Any remaining
ONGOING-ISRUNNING files nowadays act as a warning that something else had caused
HG612_stats.exe to exit early or that it is 'stuck', needing manual intervention to end its process via Task Manager.
Most times, the 'other' running instance is allowed to continue & harvest/record the stats accordingly.
However, as there is only a split second between each instance starting, both instances can occasionally be deleted, especially if some other program has slowed the PC down. e.g. an anti-virus program hogging a lot of CPU resource.