My host 46925 suddenly has the 9.somethng WUs ps_constrainted_82_2s_4 and gs_constrainted_82_2s_4 invalidated. I've been OC'ing this host a bit but can't think of why only these WUs are affected. Anyone else got these invalidated too?
I'll try running one without OC'ing in the meantime.
[edit] gotta ca(t)ch(e) one first ofcourse and I don't really feel like trashing a perfectly OK cache...

I have many invalidated wu on different hosts.
Host 79041 one of then. crunch on gpu.
radeon 4850, cpu and gpu at stock speed.
windows 7 32bit, catalist 9.5


Host 102639 crunch on cpu.

changing client from 0.19 to 0.20 not help.

I've been getting quite a few of these "invalid" WUs also.

Travis has posted that he has fixed the problem with that set of work units.

But, I'm still getting a few as of this morning.

---

Travis posted this in the 11th.
However on my host these units were from the 12th around 20:30 UT till this morning around 07:30 UTC.
Just this single host, my other hosts got non of these units.
Seems to be fine now though, guess it was sorted out.

I've just started getting about 20% invalid WUs in the last few hours. Never had many at all before. HD 4770 GPU.

My CPU rig is getting 100% invalid WUs (both opti 0.19 and 0.20), and my GPU is validating OK on 0.20 but has not got work for the last 3 hours. ;((

---

Go away, I was asleep

I have many Invalid WU with new 0.20 application (astronomy_0.20_SSE3.exe by Gipsel) with old 0.19 SSE 4.1 was all ok.

http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=104404259
http://milkyway.cs.rpi.edu/milkyway/workunit.php?wuid=102275165

And many others WU, have some one same problem with 0.20 app ?

I have many Invalid WU with new 0.20 application (astronomy_0.20_SSE3.exe by Gipsel) with old 0.19 SSE 4.1 was all ok.

http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=104404259
http://milkyway.cs.rpi.edu/milkyway/workunit.php?wuid=102275165

And many others WU, have some one same problem with 0.20 app ?

As mentioned here there are a lot of broken WUs around lately. All application versions will create invalid results with those WUs. That it happend as you switched to the new application versions is just coincidence.

Michs explicitly stated above that he experienced those errors first while still running 0.19 and updated only after that to see if 0.20 does better, but it can't given those faulty WUs.

I'm getting INVALID results now too, just a few, but I've not noticed any b4 yesterday. Now there seems to be at least a couple new ones every time I check.
;-(

---

I've just started getting about 20% invalid WUs in the last few hours. Never had many at all before. HD 4770 GPU.

Solved for me anyway. This was the BOINC message I was getting:

Milkyway@home 9/14/2009 1:35:24 PM Output file de_constrainted_82_2s_5_228058_1252953073_0_0 for task de_constrainted_82_2s_5_228058_1252953073_0 absent

Seems it was caused when I switched to BOINC v6.10.4. Going back to v6.10.3 solved the problem.

I am also getting invalid WUs. Never happened to me before, never happens to me on any other project. MW should solve this fast... two of those work units took 150 mins each, which could gracefully be used for my rosetta or my WCG. Anyway, hope they solve that soon, I like this project and I wouldn't want to leave it behind :(

As posted on the front page..."Let me know if you're having any issues with the *_6 workunits."

I did find one workunit of the *_6 variety that was given the dreaded "invalid" label.

Travis might need to do a little more tweaking to get it all straightened out.

A whole lotta wasted CPU cycles the last couple of days.

---

As posted on the front page..."Let me know if you're having any issues with the *_6 workunits."

I did find one workunit of the *_6 variety that was given the dreaded "invalid" label.

Travis might need to do a little more tweaking to get it all straightened out.

A whole lotta wasted CPU cycles the last couple of days.

Using CPUs I have to agree - see here

---

Go away, I was asleep

On my CPU only rig which is the one giving all the invalid WU results, on the _82_2s_6_ WUs, despite seemingly doing a normal amount of crunching, I am trying an experiment.

I am looking at the MW WU cache for _82_2s_6_ work and aborting them. There seems to be a large number of _82_3s_6_ WUs as well, but I am leaving these alone.

My proof of the invalid work will be if the Account results for that rig show no more invalid results posted.

---

Go away, I was asleep