I ran into a bad WU batch yesterday. Each ran for almost 3 hours and then failed at the very end, with the same error. I had 9 WU across 3 different systems fail this way. Wingmen on each WU are also failing with same error. I finally aborted the 3 I had left from the batch. Other WU from other batches are completing just fine. Lot of wasted CPU with this batch, since they run for 3 hours before failing.

All start with name "TEMP_"

Rosetta Mini 2.16

I keep running out of work on my Q6600. I think I found out why ... Boinc task manager shows that a WU will take 100+ hours of CPU time instead of the <3 hours it actually takes. Thus the manager asks for 400,000 seconds of work and gets one WU.

For some reason when a core finishes a WU and asks for another it gets nothing for a long time thus sitting idle.

Right now 3 cores are running:

Core 1 is 82.4% done at 2 hr 28 min with 1 hr 47 min left
Core 2 is 34.1% done at 1 hr 4 min with 72 hr 3 min left
Core 3 is 15.5% done at 0 hr 34 min with 150 hr 48 min left
Core 4 is idle.

Sounds like your Duration Correction Factor is waaaay off. You can wait for Boinc to fix it, and it will all by itself. Or you can shut down Boinc and manually edit the file client_state.xml. Do this thru notepad or whatever, and go down until you find this Project and the line that says:
<duration_correction_factor>0.705998</duration_correction_factor>
That is a copy of my line, yours will have the numbers be like 70.?????????? or whatever. Change it to 1.000000, save the file and then restart Boinc. Boinc will then use those new numbers and get both new work and recalculate how long it will take to crunch your existing units. If you do a right click on the file name the EDIT option is listed, use that to edit the file. Do NOT change anything else in the file. The line you are looking for is near the top, mine was only 65 lines down from the top.

And a detailled daily stats post!

I noticed that the few times I visited your Forum, it's good info for your Team to see how your doing ...