René,

That particular error code has shown a few times in relation to several things:

CPU throttle on BOINC: Set to 100%
Screensaver / Graphics: Don't use it.
Security Software: Latest definitions of e.g. an AV wrecking havoc. Brand?
Project Pre-empting - Set the option 'Leave in Memory', when suspended (some BOINC race condition that showed in 5.2 and 5.4)

There's no telling at this time what the commonality is, but setting any of the above if different could be helpful in eliminating a cause.

Have not encountered one myself yet and in fact, one just completed on a C2D on WXP SP2, Avast, no antispam or Software firewall and the above setting immediately validated.

faah1567_ d253n094_ x2AZ8_ 03_ 0-- Valid 05/13/2007 16:37:10 05/17/2007 10:25:18 6.87 71.6 / 75.6

Sekerob

Added: Have 5 in queue of FA@H and all have 1 or 2 returned with a Pending Validation status which is positive..... jobs not producing an error on the client side.

faah1569_ d257n664_ x2AZ8_ 00_ 0-- In Progress 05/15/2007 00:28:36 05/24/2007 00:28:36 0.00 0.0 / 0.0
faah1593_ apv_ x2O4K_ 73T_ 06_ 2-- In Progress 05/16/2007 06:23:57 05/25/2007 06:23:57 0.00 0.0 / 0.0
faah1593_ apv_ x2O4P_ 11I_ 06_ 2-- In Progress 05/16/2007 06:34:21 05/25/2007 06:34:21 0.00 0.0 / 0.0
faah1593_ atz_ x1KJ7_ 53L_ 09_ 1-- In Progress 05/16/2007 14:57:02 05/25/2007 14:57:02 0.00 0.0 / 0.0
faah1593_ atz_ x1OHR_ 50L_ 01_ 1-- In Progress 05/16/2007 20:15:23 05/25/2007 20:15:23 0.00 0.0 / 0.0

Looks like something changed on the 16th or from those faah1593xxxxx... here's the first 1593.


Errors are local events, but the higher number of 'Inconclusive' indicates different. I hope the HR (Homogeneous Redundancy distribution) is not acting up following a bug that Ady(webb) stumbled on (mix of work of Windows + Linux, which should not happen except for HPF2). I only run Win OSses.

Edit: Have notified knreed / technicians and suspended the remaining 3 with 1593 in the series to see what comes off the remaining '1569' or any higher numbered that may come thru in the queue.

Suggest you do. The thing with BOINC 5.8 is that even suspended jobs are counted towards the total buffered work setting, thus you might see a reduced queue size until resolved. Do not abort.... for the inconclusive it might just be a validation issue. If work turned 'error' BEFORE quorum was complete, the job is likely lost....

Let's see what comes thru the percolator.... 'doppio forte' for me

Added: If on a small queue 1-2 days, increase it to 3 days and hit update in the client to get a bit more work. Not higher as BOINC 5.8 is quirky with work buffering and the 'slob' factor, as someone called the 1 day standard safety margin within the Work Fetch policy for the 5.8 series.

Hi Sekerob,

I see exactly the same on all BOINC FAAH items. This one below is especially interessting:


Workunit Status

Project Name: FightAIDS@Home
Created: 05/14/2007 03:10:00
Name: faah1593_apv_x1KJ4_55R_04
Minimum Quorum: 3
Initial Replication: 8


Result Name Status Sent Time Time Due /
Return Time CPU Time (hours) Claimed/ Granted BOINC Credit
faah1593_ apv_ x1KJ4_ 55R_ 04_ 7-- In Progress 05/17/2007 09:47:36 05/26/2007 09:47:36 0.00 0.0 / 0.0
faah1593_ apv_ x1KJ4_ 55R_ 04_ 6-- Inconclusive 05/17/2007 01:30:25 05/17/2007 09:36:54 1.67 22.7 / 0.0
faah1593_ apv_ x1KJ4_ 55R_ 04_ 5-- Inconclusive 05/16/2007 23:27:22 05/17/2007 01:19:43 1.76 17.8 / 0.0
faah1593_ apv_ x1KJ4_ 55R_ 04_ 4-- Inconclusive 05/16/2007 14:41:39 05/16/2007 23:15:57 4.13 20.7 / 0.0
faah1593_ apv_ x1KJ4_ 55R_ 04_ 3-- Inconclusive 05/16/2007 09:10:24 05/16/2007 14:38:15 3.21 15.2 / 0.0
faah1593_ apv_ x1KJ4_ 55R_ 04_ 2-- Inconclusive 05/15/2007 20:45:39 05/16/2007 05:02:43 3.73 18.3 / 0.0
faah1593_ apv_ x1KJ4_ 55R_ 04_ 1-- Inconclusive 05/15/2007 20:41:26 05/16/2007 00:56:16 1.77 27.0 / 0.0
faah1593_ apv_ x1KJ4_ 55R_ 04_ 0-- Inconclusive 05/15/2007 20:37:40 05/16/2007 09:04:20 3.01 14.6 / 0.0

I have Linux running.

A bit of a lame question maybe but how do I do that? I can't find that option anywhere.