I had now several errors after 100% of run time.
I run Windows 7 Pro 64bit-Version, regularly updated,
with BOINC 6.10.58.
This is really worrying me since I see no ambition to solve the problem and to prevent waste of CPU time.
Someone shoultd take care of these errors.
Otherwise I will switch my support to another project, e.g. Orbit@home
http://orbit.psi.edu/
which are preparing a continous work flow.
.
Greetings from Germany
This is the error log I got if it is interestful for someone:
---------------------------------------------------
de_11_3s_5_1624669_1287011067_0
Workunit 165870716
Created 13 Oct 2010 23:04:33 UTC
Sent 13 Oct 2010 23:08:11 UTC
Received 15 Oct 2010 9:54:10 UTC
Server state Over
Outcome Client error
Client state Compute error
Exit status 0 (0x0)
Computer ID 36391
Report deadline 21 Oct 2010 23:08:11 UTC
Run time 64182.047852
CPU time 61837.85
stderr out

<core_client_version>6.10.58</core_client_version>
<![CDATA[
<stderr_txt>
<search_application> milkywayathome separation 0.4 Windows x86 double </search_application>
<search_application> milkywayathome separation 0.4 Windows x86 double </search_application>
08:46:16: Checkpoint exists. Attempting to resume from it
08:46:16: Successfully resumed checkpoint
<search_application> milkywayathome separation 0.4 Windows x86 double </search_application>
08:47:52: Checkpoint exists. Attempting to resume from it
08:47:52: Successfully resumed checkpoint
<search_application> milkywayathome separation 0.4 Windows x86 double </search_application>
10:20:14: Checkpoint exists. Attempting to resume from it
10:20:14: Successfully resumed checkpoint
<search_application> milkywayathome separation 0.4 Windows x86 double </search_application>
12:32:14: Checkpoint exists. Attempting to resume from it
12:32:14: Successfully resumed checkpoint
<search_application> milkywayathome separation 0.4 Windows x86 double </search_application>
00:58:53: Checkpoint exists. Attempting to resume from it
00:58:53: Successfully resumed checkpoint
<search_application> milkywayathome separation 0.4 Windows x86 double </search_application>
01:30:01: Checkpoint exists. Attempting to resume from it
01:30:01: Successfully resumed checkpoint
<search_application> milkywayathome separation 0.4 Windows x86 double </search_application>
08:40:26: Checkpoint exists. Attempting to resume from it
08:40:26: Successfully resumed checkpoint
<search_application> milkywayathome separation 0.4 Windows x86 double </search_application>
08:58:18: Checkpoint exists. Attempting to resume from it
08:58:18: Successfully resumed checkpoint
<background_integral> 0.00038145296112767295 </background_integral>
<stream_integrals> 2071.16984597103830000000 131.92731575300087000000 1256.65717726212050000000 </stream_integrals>
<background_only_likelihood> -3.34374771164868490000 </background_only_likelihood>
<stream_only_likelihood> -4.45245440164837800000 -4.27248055218941230000 -4.03461018482904970000 </stream_only_likelihood>
<search_likelihood> -3.08315627675478290000 </search_likelihood>
10:47:39 (17864): called boinc_finish

</stderr_txt>
<message>
<file_xfer_error>
<file_name>de_11_3s_5_1624669_1287011067_0_0</file_name>
<error_code>-161</error_code>
</file_xfer_error>

</message>
]]>

Validate state Invalid
Claimed credit 288.599509748006
Granted credit 0
application version MilkyWay@Home v0.40

There is already a post for that with the last post given 15 hours ago so no need to open another thread.

http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=1969

The admins are aware of the problem which was also stated in the last news here

http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=1975#42844

And I am very tired of reading threatening posts of "getting my crucnhcing machine into another project". Well, this is a GPU project and although i dont mean to ignore cpu crunchers, your power output is little compared to gpus. I only myself contribute 4x5870 running at 940 core. Calculate what that output equals to how many amount of cpus?

Have patience, remember when there were consequtive server out of work issues couple of months ago? Even at that time, people havent threatened the project like this. Simply, they stated the disappointment and set backup projects.

So, if you dont want to contribute, take your little core2duo cpu and....crunch

You could still run the nbody simulation with is cpu only for now and double your credits in a short time :)

I tried another run and it came out o.k.
Thanks for fixing this error.
Greetings from Germany
Dr.Mabuse