The next error, once the DLLs are in place, is usually 0xc0000374 for memory heap corruption. They'll need to go back to code, and see where they're writing outside the bounds of allocated memory, for that one.

Yes, please take it up with development. David Anderson to be precise, he's the most knowledgeable at this time.

- client: fix divide-by-zero bug in calculation of priority of projects with zero resource share

BOINC 7 uses a completely new method of calculating debt, with a from the ground up newly written scheduler.

So the moment you installed 7.0.11, all previous debt values were forgotten, they're no longer used by this BOINC. So BOINC downloads one task from all the projects that are allowed to fetch work. You can easily set them back to ANT, as it won't do it again.

1/20/2012 08:08:53 | PrimeGrid | work fetch resumed by user
1/20/2012 08:09:27 | Milkyway@Home | Computation for task ps_separation_82_2s_mix0_3_1716631_0 finished
1/20/2012 08:09:27 | Milkyway@Home | Starting task ps_separation_82_2s_mix4_3_1715967_0 using milkyway version 82 (ati14ati)
1/20/2012 08:09:27 | Milkyway@Home | Sending scheduler request: To fetch work.
1/20/2012 08:09:27 | Milkyway@Home | Reporting 1 completed tasks, requesting new tasks for ATI
1/20/2012 08:09:29 | Milkyway@Home | Scheduler request completed: got 1 new tasks
1/20/2012 08:09:34 | PrimeGrid | Sending scheduler request: To fetch work.
1/20/2012 08:09:34 | PrimeGrid | Requesting new tasks for ATI
1/20/2012 08:09:37 | PrimeGrid | Scheduler request completed: got 1 new tasks
1/20/2012 08:09:44 | PrimeGrid | work fetch suspended by user

1/19/2012 21:04:46 | Collatz Conjecture | Sending scheduler request: To fetch work.
1/19/2012 21:04:46 | Collatz Conjecture | Requesting new tasks for ATI
1/19/2012 21:04:48 | Collatz Conjecture | Scheduler request completed: got 1 new tasks
1/19/2012 21:04:51 | Collatz Conjecture | Started download of collatz_2373591143462694791528_824633720832
1/19/2012 21:04:54 | Collatz Conjecture | Finished download of collatz_2373591143462694791528_824633720832
1/19/2012 21:04:54 | Milkyway@Home | Sending scheduler request: To fetch work.
1/19/2012 21:04:54 | Milkyway@Home | Reporting 1 completed tasks, requesting new tasks for ATI
1/19/2012 21:04:56 | Milkyway@Home | Scheduler request completed: got 1 new tasks
1/19/2012 21:05:02 | PrimeGrid | Sending scheduler request: To fetch work.
1/19/2012 21:05:02 | PrimeGrid | Requesting new tasks for ATI
1/19/2012 21:05:04 | PrimeGrid | Scheduler request completed: got 1 new tasks
1/19/2012 21:05:15 | PrimeGrid | Sending scheduler request: To fetch work.
1/19/2012 21:05:15 | PrimeGrid | Requesting new tasks for ATI
1/19/2012 21:05:17 | PrimeGrid | Scheduler request completed: got 1 new tasks
1/19/2012 21:05:27 | PrimeGrid | Sending scheduler request: To fetch work.
1/19/2012 21:05:27 | PrimeGrid | Requesting new tasks for ATI
1/19/2012 21:05:30 | PrimeGrid | Scheduler request completed: got 1 new tasks
1/19/2012 21:05:41 | PrimeGrid | Sending scheduler request: To fetch work.
1/19/2012 21:05:41 | PrimeGrid | Requesting new tasks for ATI
1/19/2012 21:05:43 | PrimeGrid | Scheduler request completed: got 1 new tasks
1/19/2012 21:05:53 | Collatz Conjecture | Sending scheduler request: To fetch work.
1/19/2012 21:05:53 | Collatz Conjecture | Requesting new tasks for ATI
1/19/2012 21:05:55 | Collatz Conjecture | Scheduler request completed: got 1 new tasks
1/19/2012 21:05:58 | Collatz Conjecture | Started download of collatz_2373591165933963684200_824633720832
1/19/2012 21:05:59 | Collatz Conjecture | Finished download of collatz_2373591165933963684200_824633720832

Milkyway@home appears to be down and the message boards are unreachable since 21:15 GMT (British Summertime).
I will run out of work in 3 minutes :-(

With that said, the developers don't know either.
Yet there's one but: Normally you won't see GUI RPC requests showing in your messages, so do you have <gui_rpc_debug> (or <guirpc_debug> in pre-6.11 versions) on in cc_config.xml?

You could disable that (set to zero, or remove the line), save changes and let BOINC read the config file again. At least then you don't see these requests. They don't seem to be harmful either.

<cc_config>
    <log_flags>
    </log_flags>
    <options>
    </options>
</cc_config>

Wed Apr 13 05:42:28 2011 |  | GUI RPC request from non-allowed address 16.2.192.0
Wed Apr 13 06:24:23 2011 | SETI@home Beta Test | Computation for task 07mr11ah.23742.18881.206158430211.14.144_1 finished
Wed Apr 13 06:24:25 2011 | SETI@home Beta Test | Started upload of 07mr11ah.23742.18881.206158430211.14.144_1_0
Wed Apr 13 06:24:31 2011 | SETI@home Beta Test | Finished upload of 07mr11ah.23742.18881.206158430211.14.144_1_0
Wed Apr 13 08:30:08 2011 |  | GUI RPC request from non-allowed address 16.2.193.225
Wed Apr 13 08:58:39 2011 | SETI@home Beta Test | update requested by user
Wed Apr 13 08:58:42 2011 | SETI@home Beta Test | Sending scheduler request: Requested by user.
Wed Apr 13 08:58:42 2011 | SETI@home Beta Test | Reporting 4 completed tasks, not requesting new tasks
Wed Apr 13 08:58:45 2011 | SETI@home Beta Test | Scheduler request completed
Thu Apr 14 09:37:53 2011 |  | GUI RPC request from non-allowed address 16.2.239.33

Anyone have any information about Collatz -- been offline for a day and a half. That project has been very solid for the past year with only a few shorter outages.

Server Status - Good and Bad
The server is up but the work generator is not. That is on purpose. The server reports that the boot drive needs to be replaced which means reinstalling Linux, Apache, MySQL, etc. Unfortunately, that disk also contains the partician for the WUs waiting to be sent out. I won't have time to replace it until this weekend. So, until then, I'd rather be cautious and not generate any new work just in case Mr. Murphy is still hanging around. You should be able to return any completed results in the mean time so your BOINC client doesn't get overwhelmed with the number of workunits it tries to monitor.