I have one computer in my farm of computers which frequently gets zereoed out credits. The work is being submitted in time, and most of the time the claimed credit is in line with the other computers working the same unit which are getting credit.

What would cause this result on one computer only which is otherwise working just fine.

The computer in question uses a Biostar M7VITPRO motherboard with an XP2700 Thunderbird CPU.

---

It might help if you specify which computer you're referring to, you've got a big farm! I did find one with results as you describe, and the validation state of those units was "Invalid". Paul D. Buck's excellent BOINC Owner's Manual says that this means:
****
Invalid
The Result failed Validation and it is not considered to be a valid Result. There are many reasons that can cause this, including the simplest explanation, it did not compare with the other returned Results. Keep in mind that it is possible that those other Participants are wrong and you are right …

But that is why we use a consensus method to test the returned values. When several Results compare within the limits of error, it is most likely that the ones that do compare are correct.
****

I leave it to others to discuss why you might be getting results at variance with others'.

---

> I have one computer in my farm of computers which frequently gets zereoed out
> credits. The work is being submitted in time, and most of the time the
> claimed credit is in line with the other computers working the same unit which
> are getting credit.
>
> What would cause this result on one computer only which is otherwise working
> just fine.
>
> The computer in question uses a Biostar M7VITPRO motherboard with an XP2700
> Thunderbird CPU.

My first question is always, are you over-clocking?

Though your computer seems to be running fine, it may not be.

I looked at your account and of the ones *I* looked at, they are marked as invalid ... which is one of the symptoms of aggressive overclocking ...

---

Paul -- I checked yup -- overclocking (relatively modest -- 166 overclocked to 170). I just reset that back to normal.

Let's see what happens over the next day or so.

Thanks

---

> Paul -- I checked yup -- overclocking (relatively modest -- 166 overclocked to
> 170). I just reset that back to normal.
>
> Let's see what happens over the next day or so.

I am just saying that this is one of the more common symptoms. There may be something else wrong with the system, such as bad memory or whatever.

It may even be a bad CPU ... but looking at your list of computers I sure do envy you (I don't however envu your electric bill) ...

---

I have also seen a problem if you used optimized binaries and don't upgrade them when a new version of SETI comes out. You will still get isssued WU's, but they willa ll get client error on them. See here.

---