Nothing to worry about - just the system reverifying your machine

Oh, I see. So it happens with FAaH because that project uses single validation.

I'm glad someone else asked, so that I could learn, too!

Probably spread over multiple devices, else I'd really be getting worried, though with a hexcore that absolute rate will likely be a bit higher too.

:D

Inconclusive is just indication that a random re-verification is requested by the server logic for the ZERO REDUNDANCY (ZR) tasks if a small subset (maybe 10%) was computed correctly to maintain a high degree of confidence when in the other 90% the clients are allowed to do it alone, without wingman. FAAH/HFCC are such distributions.

Your "other projects" usually are QUORUM 2, which means ALL tasks require 2 copies to be computed at the minimum. What do you think is more efficient, purely from a computational load perspective? Wish all were ZR, but most require and absolute bit for bit verification since these results often go into reference databases that other scientists consult from around the world. Can't have results that the uncontrolled volunteer computer sends back with an occasional quantum bit pointing the wrong way.

In that case there is maybe something suspect with your computer. There are several benchmark/QA's build into the ZR tasks. If any of these do not match the benchmark/QA references (one that was tested ad nauseam to produce a gold standard), then the task is automatically rechecked. Then when the wingman (one of a known stable host) is matching, they are both okayed.

Now what's different to your computer... hmmm "faster PC" ... OCing / Undervolting and such like (?) can create minute timing differences, not enough to matter for a quorum 2 run, but not good enough for a ZR. Regardless of you having pushed hardware or not, suggest you run a dustbunnies cleaning session and do some system testing (memtest86 e.g.) as if some intermittency is building, it eventually breaks permanently.

edit: spelling gremlin removed