After 700 million plus -valid- results, it's still the open question why this happens to some. Zero status suggests a momentary system overload, so the task is restarted from last checkpoint, to be sure any corrupt bits can not enter into the output. This restart is allowed up to 100 times after which the task is automatically aborted. The 'reset the project' sometimes works if running since a long time and gunk accumulates in either memory or in the project folder [unlikely though]. A system boot is more effective in this respect to refresh the environment.

Check that nothing in the security software is blocking the app. Also, given the science is -allowed- to run [Elapsed], it may be something else on the assigned thread is running [above lowest priority]. Suspecting this is Windows, hit Ctrl+Shft+Esc to open Task Manager. In there hit the button that shows all processes. Sort on CPU percent or time from high to low and see what's using the cycles.

The project is on it's last leg after nearly 10 years [EOP June 2015]... don't expect any application debugging effort by the programmers at this stage.