A new, smaller, beta test was sent out a few hours ago, labelled v7.23.

I think it's the same as v7.22, but has extra debugging printf statements to shed light on what is happening around the exit(0)s under Win7-x64.

Check the thread for it before posting anything else here ...
New Beta Test starting Nov 6, 2013 v7.23 [ Issues Thread ]

I did not (yet) receive any 7.23 WUs, but got a few 7.22 ones on both an old laptop running XP, and a I7 laptop running Win7-64. They completed in around 6 hours (originally estimated at 13h). Some have validated OK, others are PV.
I suspended the I7 machine without negative impact on those WUs, whereas in the previous batches this would cause a reset and ultimatey loss of result.

At last, I have received 8 7.22 Betas and unlike the others they are actually doing something apart from restarting - that's progress - thanks to the Techs - something was wrong before....

I have four 7.22's running at the moment - three started perfectly and the elapsed time and to completion times clocked in sync with the progress, the last one however, was a totally different beast - it was quickly up to 0.5% and then sat there for almost 15 mins, with just the times incrementing - first thought was that this was another failure in waiting!! Whilst the other three are at 17, 21 and 36% after 40 mins, the fourth one is only at 8% but at least it has finally passed the 0.5% threshold....
However, I also have a 7.19 and a 7.21 that are back in the old style of running for about 3 mins, no percentage completion and then restart mode (not sure where to report these as there are no specific threads as far as I can see) - and these were received after the version 7.22's!!! Not sure what's going on with the version numbering, but there are certainly WU's out there that still don't run correctly..... and two 7.24's are running perfectly!!

I have BOINC running on a rarely-touched older single core notebook computer, which I check at most once a day, and sometimes don't bother for several days. I noticed one of these beta tasks attempting to run on that PC, and so started checking on it a few times a day.

After two days of it being listed as "high priority" but never seeing it go beyond 0%, I just aborted it in BOINC. But, in fact, the task was still listed as running in Windows' Task Manager, despite it showing as aborted in BOINC. So I ended the task in Task Manager, and then BOINC said "computation error." Not much of a log was uploaded to the queue; all it says is "aborted by user."

If the contents of the BOINC messages log would be useful to you, please reply, and I'll copy it for you. However, all I see is dozens of "restarted" entries.