I have been waiting for one wu to be marked done and work credited, checked this morning and it has no been marked validate error. Been waiting since May and the wu number is 611097536 all the others had timed out and machine error yet the one yesterday that had arrived was marked pending, so can someone explain what caused this error

---

Hi, looked it up, this one.

This host.

Most of the results are different, maybe somebody with more knowledge and experience with this can explain it better.
Looks like a problematic WU, anyway, do you have your hosts OC'ed?
Heat related? RFI? I'm lost, too............

Had some problems with my VISTA host (Q6600+GTS250), during an M.S. UpDate, a driver crash occurred.
This host.
Pixels started to get white, until the whole screen was white, a full ReSet/
ReBOOT, was necessary, to end this. This one is also sensitive for heat, too
sensitive.

---

no do not have it oc'ed just run it normally with lunatics optimised version, so why did they do it sl late

---

Application version SETI@home Enhanced v6.09 (cuda23)

is the stock SETI app. Not from Lunatics.

---

Boinc....Boinc....Boinc....Boinc....

It is now showing as a validate error for you Madmac. The last two completed and validated. Guess the SETI validater just doesn't like you for some reason. No, joking aside, I have no idea why yours didn't validate.

---

PROUD MEMBER OF Team Starfire World BOINC

Application version SETI@home Enhanced v6.09 (cuda23)

is the stock SETI app. Not from Lunatics.

Mine is this SETI@home Enhanced Anonymous platform (CPU)
Not the cuda as that machine is 4 years okd plus and does not have a graphics card

---

For whatever reason (unknown) yours returned

Spike count: 0
Pulse count: 0
Triplet count: 0
Gaussian count: 1

The 2 client computers that validated returned

Spike count: 4
Pulse count: 2
Triplet count: 1
Gaussian count: 1

---

Boinc....Boinc....Boinc....Boinc....

And that can come from, stopping and restarting the app. several time for whatever reason. (BOINC switching Projects, for the time set, normal is 60 minutes, I prefer 100)
IMO, it should be the same number, but don't know how this is counted.
The amount of "FLOPS", should also be about the same.

I found out with my 9800GTX+, when it got too hot, it makes the infamous,
Find Triplets in a row or -9 (Result Overflow), the GTS250 has less problems with heat. (But makes errors, too, if it's get too hot!)

FERMI's can run very hot (100C), without making errors, and trying to reduce temps is very much wanted, I should think.

---

And that can come from, stopping and restarting the app. several time for whatever reason. (BOINC switching Projects, for the time set, normal is 60 minutes, I prefer 100)
IMO, it should be the same number, but don't know how this is counted.
The amount of "FLOPS", should also be about the same.

I found out with my 9800GTX+, when it got too hot, it makes the infamous,
Find Triplets in a row or -9 (Result Overflow), the GTS250 has less problems with heat. (But makes errors, too, if it's get too hot!)

FERMI's can run very hot (100C), without making errors, and trying to reduce temps is very much wanted, I should think.

Probably was from switching units between Seti and WCG

---

It is now showing as a validate error for you Madmac. The last two completed and validated. Guess the SETI validater just doesn't like you for some reason. No, joking aside, I have no idea why yours didn't validate.

"Validate error" has the very specific meaning that the Validator couldn't find the uploaded result file. Considering the several cases where storage space ran out since May, or server crashes and such, it is not too surprising that some fraction of uploaded files have gone missing.

The difference in number of signals is unrelated because the lost result was done with an AK_v8 r41 build and had a restart at 55%, it was only reporting found signals after that restart.

                                                                 Joe