Bad Woots?

How can you tell if a WU is aborting early due to high-noise?

I’ve just had nine WUs in a row finish early, as in the first eight from 9-17 seconds and the ninth in 11mins.

Worryingly I’d just clocked my XP2000 up a bit more. I ran at 1827mhz for a couple of minutes, long enough to chew through the first eight quick WUs before a BSOD. Clocked back to 1808 and the ninth WU returned in 11 minutes.

I’m too suspicous and cynical to write this off to pure chance, espcially as all the WUs were different ARs.

Are you using any logging apps (e.g Seti Spy)? High noise WUs have a lot of spikes in them but you will also get the same effect from a system overclocked beyond it’s capabilities as it will in effect create false noise.

I had a similar situation recently where every WU was completing in around 80 mins - turned out to be one of the DIMMs had developed a fault.

Best advice I can offer is to run a Prime95 self test that will stress CPU and a little RAM and either Memtest86 or Doc Memory on the RAM.

I reckon it’s cos I’d clocked it A Hertz Too Far.

Question is, if I can return WUs in less than 20 seconds, do I fix it? :devil:

:smackbum: :bondage: :smackbum: :bondage: :smackbum:

… but wait … you might like it! :smiley: