Win 7 Ultimate AMD 9150e Quad. Ran concurrent with 3 FAHV. Did not appear to checkpoint until it hit 50%.
03-Nov-2013 13:13:23 [World Community Grid] Computation for task BETA_BETA_9999985_0140_2 finished
03-Nov-2013 13:13:23 [World Community Grid] Output file BETA_BETA_9999985_0140_2_0 for task BETA_BETA_9999985_0140_2 exceeds size limit.
03-Nov-2013 13:13:23 [World Community Grid] File size: 10554096.000000 bytes. Limit: 10485760.000000 bytes

Result Log

Result Name: BETA_ BETA_ 9999985_ 0140_ 2--
<core_client_version>6.2.28</core_client_version>
<![CDATA[
<stderr_txt>
Commandline = projects/www.worldcommunitygrid.org/wcgrid_beta17_7.19_windows_intelx86 -SettingsFile BETA_9999985_0140.txt -DatabaseFile dataset-GDS2771-v1.txt
Initializing
wcg_learn_limit = 750000
Running
[13:42:02]: Computing pass 0
Commandline = projects/www.worldcommunitygrid.org/wcgrid_beta17_7.19_windows_intelx86 -SettingsFile BETA_9999985_0140.txt -DatabaseFile dataset-GDS2771-v1.txt
Initializing
wcg_learn_limit = 750000
Running
[18:40:22]: Computing pass 0
[21:54:10]: Computing pass 1
Commandline = projects/www.worldcommunitygrid.org/wcgrid_beta17_7.19_windows_intelx86 -SettingsFile BETA_9999985_0140.txt -DatabaseFile dataset-GDS2771-v1.txt
Initializing
wcg_learn_limit = 750000
Running
[09:28:33]: Computing pass 0
Run complete, CPU time: 24515.321567
13:13:21 (2648): called boinc_finish

</stderr_txt>
<message>
<file_xfer_error>
<file_name>BETA_BETA_9999985_0140_2_0</file_name>
<error_code>-131</error_code>
</file_xfer_error>

I received one rerun this evening. Two wingmen errored out with the dreaded -131 error, one errored with a confused PC, and one is still running.

One tester recently commented (s)he had no time to babysit the beta tasks received [so why select the program ;?], but for this 'autonomous' restarting it would be of interest to draw a memory/vm usage profile, also to see if the non-BOINC CPU load jumps prior to the task bombing, suspecting it's close to the checkpoint moment when this happens. Tool to use is [gobbled by MS] SysInternals' Process Explorer. Select the task and right click for properties, then select 'Performance' tab for the numbers and 'Performance Graph' for historical CPU and memory loads and I/O [which is when disk/storage accessing is really well visualized, when task is trying to save to disk or pull new data].

Will be doing that on next testing round... tasting pressures to make it a on or before November 16 production launch... a silent one, as is customary, on a Saturday, which would be revelutionary [Something In The Air]

For those incurring restarts or output files that cannot be written, suggest to run the Installer again and choose the 'Repair' option, just in case ownerships of application/task data pieces are not correct. Be sure when you edit anything in the data_dir structure to use admin rights [right click, run as administrator]. Not doing that correct could too change permissions and access rights.

Waiting for an opportunity to get a Beta WU. Haven't gotten one yet - apparently I've just not been in the right place at the right time to get one. Looks like everyone who has gotten one so far has been finding a number of things to fix so the next round will be cleaner. In the meantime I'll continue crunching my FAAH WUs and wait and see if one of these elusive Beta WUs ever pops up on my laptop.

aborted 4 beta with continuous restart. The first 1 minute and 17 seconds (or so) seemed to go ok. Windows 7 4-core machine that has already returned 5,326 WU, which should eliminate the AV as the culprit.

Back to the drawing board