Unrecoverable error...exit code 1(0x1)

[WindForce]

I'm getting tons of those lately, on my fx-57. 50-60% of the work is going down the toilets, since this error happens ( Murphy's frikin law :stick: ) like 5 minutes before the WU finishes...
Even tried running down the system 3.0 Ghz @ DDR400 , still the same. Started thinking i seriously dammaged something in my rig, when i start noticing same messages in my little boy's PIII as well as some other rigs.
Are you guys getting those? What do you do to minimize dammage?

[shmaa]

Been getting tons of them lately on all our machines... I guess there is nothing you can do but let them run their course :shrug:

For damage control, I would set your WU time to 2 hours. That way, if it does error out 5 minutes before finishing, then you've only lost an hour and 55 minutes (give or take a few minutes).

[WindForce]

Been getting tons of them lately on all our machines... I guess there is nothing you can do but let them run their course :shrug:

For damage control, I would set your WU time to 2 hours. That way, if it does error out 5 minutes before finishing, then you've only lost an hour and 55 minutes (give or take a few minutes).

that's exactly what's happening most of the time...

[Fr3ak]

I had about 20 HBLD wus failing one after the other. Downclocked to under stocks settings and they still failed, so the problem must have been on their side.

[[XC] serlv]

You're not alone. I'm glad you posted this. I'm getting a ton of them on an X2~3800+/DFI RS482 Infinity system I put together yesterday. I thought it was perhaps the build, or the maybe the BOINC install. I uninstalled, then reinstalled BOINC. Same thing.

I have noticed some errors, though not as many, on some previously error free boxes, too

You know, though I'm certainly not throwing in the towel, by any means, I certainly wish these people would get their shiite together. It is frustrating building and tuning these boxes, and paying good money to power them, only to have our efforts wasted.

Me thinks it doesn't bode well for the growth of the project if they are wasting their contributors resources. Repeatedly. Friggin get it right.

[[XC] Duc]

I had 2 of them until now... and they both failed after 31 seconds.

[UCmajewski]

Some other problems we get... that makes me miss d2ol

1) The BOINIC service hates running on Pentium 4's

2) A work unit will eventually get stuck on every machine no matter how stable it is

[chew*]

Hmmm Odd well i can say from my experience that the new update is really harsh on memory. It could be that your memory or OC is just not as stable as you thought it was. I have gotten about 1 error a month thus far.

[UCmajewski]

Hmmm Odd well i can say from my experience that the new update is really harsh on memory. It could be that your memory or OC is just not as stable as you thought it was. I have gotten about 1 error a month thus far.

its defianetly something with the service install that makes it lock/disappear etc. More than once I have had to detach then merge ......... all memory and chips are running bone dead stock.

[mad mikee]

On my wife's puter, seemed like it tried to run 3 instances and this one got tossed in a corner while the other 2 ran :shrug:

[stone_cold_Jimi]

The rosetta@home fora have discussion and other reports of WUs failing or getting stuck at 1%. Apparently they got a BOINC consultant called Rom in a few days ago to sort this out.

I've just started this on a machine I'm about to rebuild, my first WU completed successfully with an unhandled exception happening in it somwhere. But that's a general BOINC thing (FAQ).

[DAK1640]

I had 1 just this morning that ran 10+ hours, racked up 310 points and was only 1% complete. I obviously aborted it, but there goes 10 hours of crunch time.

I guess I'll just have to make my farm bigger to make up for the loss. I will add 2 new comps this afternoon.

[WindForce]

I did a test with my fx-57 today, with fsb @ 205 ( just set the multi to 15 :D ) so it's really not harsh on the memory.
I got the error about 80% of wu's. Some after 1hour 50 some after 10 minutes.
I also tried this week plain stock, still the same.
I also started noticing those erros in other rigs, which aren't overclocked at all.

[stone_cold_Jimi]

I got errors on one instance when pausing the client on the dual core rig. Is that a memory config thing? Happened a couple of times, first one instance then later the other.

[Mr_Slinky]

its alot like the one i started here
http://www.xtremesystems.org/forums/showthread.php?t=91378

also just a side note but how much credit do we get for those ones that get "stuck" i am guessing its based on how much cputime it takes but if anyone actually knows i am sure we would like to see it

[Movieman]

its alot like the one i started here
http://www.xtremesystems.org/forums/showthread.php?t=91378

also just a side note but how much credit do we get for those ones that get "stuck" i am guessing its based on how much cputime it takes but if anyone actually knows i am sure we would like to see it
From what i've seen, you get didley unless you return a fully completed WU.
I submitted over 3000 points that I thought VNS was shorted 2 weeks ago..Have heard or seen nothing..BUT I've left the "nasty, confronting" Dave face in the closet and put on the nice face. On the assumption that over time we all(DPC included) are going to lose points equally I figured it was more important to just let the cards fall where they would and get back to prepping for gluttony at the BBQ!:D