Link,

Tackleway has some good points. I've been checking the error from my system, less now than before but still coming through. I check the WUs to see what other systems have failed. If I see 4 errors while computing for the work unit, I assume I have no problems with my system. The WU was bad. The failures are across many systems, CPUs, and GPUs.

One recent failure on a "free_3" WU showed an error for an AMD CPU computer, 2 opencl-nvidia computers, and my opencl_amd_ati machine for a total of 4 (WU assumed bad). I've seen many combinations of CPU and GPU failures.

This is NOT a GPU driver issue.

Joe

One recent failure on a "free_3" WU showed an error for an AMD CPU computer, 2 opencl-nvidia computers, and my opencl_amd_ati machine for a total of 4 (WU assumed bad). I've seen many combinations of CPU and GPU failures.

This is NOT a GPU driver issue.

That I've seen too, I even posted an example of such WU in message 55867 in this thread. Tackleway however wrote "all the tasks failures here were processed only by CPU". That's wrong.

I don't think it's a driver issue either, see my post in NC or my message 55867 in this thread.

---

Sorry, maybe you have misunderstood my statement
"all the tasks failures here were processed only by CPU".
was referring to my 4 machines at this location,therefore
it is not wrong as I do not use my GPU's to process for Milkyway.

[/b]

---

Ups... my mistake, sorry.

---

It is possible that the remaining errors are due to outdated BOINC applications or GPU drivers. So far, every erroring computer that I have looked at (which is not all of them) has outdated GPU or BOINC versions.

I'm still looking into the problem, but if you are having errors it wouldn't hurt to update your drivers and/or BOINC app and see if that fixes the problem. Please let us know if it does.

I have tried various different drivers and BOINC versions and things have not improved. With older cards in particular the older drivers tend to be better - faster and more stable. The 7.x versions of BOINC are also crap for this project because the scheduler causes clients to sit idle half the time.

The 7.x versions of BOINC are also crap for this project because the scheduler causes clients to sit idle half the time.

That's usually because v7 needs other cache settings than v6 and older. What do you have set as "Maintain enough tasks to keep busy for at least X days" and "... and up to an additional Y days"?

---

I think they are both set to 1 day. I have tried various setting and it makes no difference. It rarely gets more than about 5 minutes work at a time and when it runs out it sits there doing nothing for ages. Now that there are so many errors it seems to defer for even longer, like several hours. Since these new WUs have started my output is less than half what it was before and this is mainly due to the errors causing boinc to sit idle for hours at a time.

I don't believe that really applies here, if you run more than 1 project Milkyway will soon have no tasks to run. This happens for two reasons, the Milkway limits on the number of tasks a computer is allowed at a time, I get 75 max. and the schedular filling all remaining time with tasks from other projects when Milkway has none available. Other projects attempt to fill the x Days and Y Extra settings but not Milkyway, happens to me regularly and causes a lot of manual intervention where it should'nt be required.

OK
loads of errors still
is there an end in sight ?

i'm running at 270 in my stats for just one machine..

whats happening ?

cheers folks

my error rate is right around 3.5% right now, up slightly from yesterday and the day before...

---

OK, a bit weird I know ...

On this one PC all GPU WU's failed after 4 seconds with Computation Error. Tens of 'em. I sensed this because I was typing stuff on this PC and everything ran much quicker. LOL!

So, checked GPU results - all fails.
Suspended Project.
Cold-booted.

Next GPU WU completed OK.
And the next one.
Anthe next one is currently at +75% ... looks OK now.


HTH, Ray
XP Pro SP3, HD3650 AGP, BOINC 6 12.34, CCC 11.8 (8.881) ... all installed for a looong time on this one PC.

my error rate has risen to 4% (up from 3.5%) in the last 24 hours.

i know there's no way to tell if a WU is bad until it has failed for multiple wingmen...but does anyone have an educated guess as to how much longer it'll be until all these "bad" WU's are flushed out of the system?

---

4.7% here
323 errors in my one machines stats pretty constantly

Please let us know a little more news about these bad units

Also the quorum appears too big, 4 machines have to show the same error before the unit is dumped as far as i can see

the main problem is that once the boinc client has an error computing it is much less likely to keep the cache full, so unless you nurse your machines they sit there with empty caches

a little update would be appreciated :-)

cheers

Hi - sorry guys, I've been hit by job application season and I've been buried. :P

This is a weird error; the binaries haven't been updated since before the last set of stable jobs, but the server code has. The server shouldn't be able to throw bad WU's that behave like these do.

I've found that the "de_separation_22_3s_free_3" WUs seem to be returning unphysical likelihoods; it is possible that this run is responsible for the errors that people are seeing.

Sorry for the inconvenience, we'll try to get this sorted out in the next day or 2.

-Matthew

great,

thanks for the update Matthew

looking forward to the fix...my error rate is now up to %5

---

Matthew,

It's not just the "de_separation_22_3s_free_3" WUs that have problems. Many "de_separation_22_3s_edge_3" WUs are also failing on AMD CPUs, Intel CPUS, Nvidia cards, and AMD cards.

Joe

Matthew,

It's not just the "de_separation_22_3s_free_3" WUs that have problems. Many "de_separation_22_3s_edge_3" WUs are also failing on AMD CPUs, Intel CPUS, Nvidia cards, and AMD cards.

Joe

I very much concur with Mr. Marshals findings !

Regards

John G

John,

Good to get confirmation that others are seeing the same failures.

Thanks,

Matthew, Travis,

I don't know if this is going to help, but instead of pulling my machines off MW, I'm going to reallocated my resources to MW (1 NVidia GTX 560Ti, 3 AMD HD 7950s, and 7 of 14 CPU cores spread across three machines). I'll either help clear out the bad WUs or add to the confusion.

By the way, I haven't seen any failures where my wingmen didn't also have faiures. That brings up a question. If these WUs have bad data or something else wrong how confident are you that the WUs that validate are really good?

Joe

John,

Good to get confirmation that others are seeing the same failures.

Thanks,

Matthew, Travis,

I don't know if this is going to help, but instead of pulling my machines off MW, I'm going to reallocated my resources to MW (1 NVidia GTX 560Ti, 3 AMD HD 7950s, and 7 of 14 CPU cores spread across three machines). I'll either help clear out the bad WUs or add to the confusion.

By the way, I haven't seen any failures where my wingmen didn't also have faiures. That brings up a question. If these WUs have bad data or something else wrong how confident are you that the WUs that validate are really good?

Joe

Thank you Joe...

---