I think I've fixed the problem with workunits all being marked invalid. Let me know if newly reported workunits are validating ok.

---

The one cuda work unit I just reported validated. Good work.

Are those units already marked as invalid lost, or will you do a re-validating?

Best regards Bent

The one cuda work unit I just reported validated. Good work.

Are those units already marked as invalid lost, or will you do a re-validating?

Best regards Bent

Theres a chance they might get revalidated, but i'm not quite sure.

---

You have my feelings. Let us just pray :-) Bent

I noticed that many of the work units now only allow a maximum of one error before the work unit is rejected. That seems to be a bad idea due to the number of people with outdated graphics drivers (causing some ATI/AMD work units to fail) and those with optimized applications that will generate validate errors because they still upload results with file uploads, where the validator no longer looks.

As from 07:33 UTC no more invalids.
Thank you!

Still have wu's marked as invalid.

I have had a load just "aborted by project"

I agree with Jesse, the current situation could use some improvement.

While looking at recent results I noticed you became quite generous with "initial replication". I've seen 4 and 6. Out of these only 1 error (due to an old app or whatever) already triggers the WU being marked invalid. Sorry, but this is stupid if you've got 5 perfectly fine and agreeing results together with that error. Take the results which are good, give them credit and never mind the error.

MrS

---

Scanning for our furry friends since Jan 2002

I got @~50% per WU an aborting computing error with all the WUs from today :/
There must be something wrong :(

Edit:
I saw now in errorreports on website from two of the WUs:

Maximum elapsed time exceeded

hum? after ~4 Minutes? Timeline is 15.5. not today in 4 minutes.. ^^ Dont have a 5990 or something to get this finished in this time ^^ Need 7-13 Minutes depending on Type of WU

---

DSKAG Austria Research Team: http://www.research.dskag.at

Don't know if this is related, but all wu on my dual 5870s error now.

I have a 6950 and the same problem, every WU end with Computation error.

-every tasks from my dual ATI 4890 GPU are in error today.
-my CPU Tasks are ok.


best regards

Same here, all my GPU WUs (4850) end in Computation Error. Just watched one and they only get about half way.

All of my workunits running on the GPU are currently being aborted - automatically, with diagnostics similar to the following:

07/05/2011 16:07:31 Milkyway@home Starting de_separation_10_3s_fix20_1_142549_1304780731_0
07/05/2011 16:07:31 Milkyway@home Starting task de_separation_10_3s_fix20_1_142549_1304780731_0 using milkyway version 62
07/05/2011 16:09:09 Milkyway@home Aborting task de_separation_10_3s_fix20_1_142549_1304780731_0: exceeded elapsed time limit 96.990841
07/05/2011 16:09:10 Milkyway@home Computation for task de_separation_10_3s_fix20_1_142549_1304780731_0 finished

I guess this is another screw-up?

As you can see, the unit was aborted after about a minute of the astronomic time, due to "exceeded elapsed time limit". Evidently the "elapsed time limit" is being set wrongly.

---

I have lots of error while computing now, just powerd the rig.
Wingman have almost all errors with same WU's.

---

Greetings from,
TJ

Guess I'm one of the lucky ones. I have very few of these invalid or error wus. Most of them are cancelled by server.

I don't use any app_info, cpu and only have one backup project which doesn't use cpu as well. BOINC Version 6.10.60, catalyst 11.3, 7 Pro X64SP1.

Also, I downclock the memory within official limits unlike the unofficial one in MSI AB. If i downclock more than 1/2 of the initial memory amount, than at some point, the driver causes BSOD.

Hope the info helps.

I think you are lucky indeed. All my wingman have errors so a lot of people have them.
I haven't made any changes to settings of cards, cpus and so on. No tweaks no overclocks or downclocks, and till today all was running like a train, a fast train.

---

Greetings from,
TJ

Travis, not clear that this is fixed yet. I did a project reset and the first unit went to a computation error.

What I will do from this side is update to the most recent (11.4) ATI drivers -- been running 11.2. After that I'll try again.

---

OK - looks like the problem is not resolved.

I'm running 6.10.58

I installed the current 11.4 ATI drivers

I then did a project reset.

I got computation errors (after about 33% complete) -- on a Windows XP as well as a Win 7 - 64 bit, both workstations have HD 4850's -- not over clocked.

So for now, I figure the issue which showed up in the past day, is on the MW side of things.

I figure to watch the news here but for now, I will push over to Collatz.

---