Seti Problem

[titanmiller]

picture of the problem<<<I accedently had the compression set too high

Nearly every morning when I wake up I receive this message. While this message is displayed it just sits there doing nothing (always at around 3% complete) until I press the "do not send" button when it then continues like nothing happened. Checking my setiQueue log, this machines last result was at 12:53AM, it then processed about 3% of the next WU and that message came up therefore causing it to do nothing. So it just sat there until I just checked on it at about 6:50AM having accomplished nothing.
During the day I check its progress with SetiWatch several times per hour, maybe the lack of activity during the night causes it to do this? This machine is overclocked, it has proven itself stable in the past but I guess I shouldn?t rule it out. If it just came up with the message it wouldn?t bother me, but since it stops the progress of the WU it is a bit angering. I lost 6 hours (3 WUs) last night. However the night before It stopped several minuets before I woke up.
I will run scandisk and defrag on it and see if that helps.

 

[conjur]

Is your CPU running hot? Maybe some bad memory?

When I was playing with o/c, in the first few % it seemed when the SETI client really used the cpu and got the temps up. I lowered the o/c and got a better fan and the lockups went away.

Also, try swapping out to some different memory. Is it registered?

 

[titanmiller]

My CPU normally runs around 54ºC, which shouldn?t be too bad for an Athlon.
The more I think about it, it might be my (actually probably is) my memory. I am a bit disappointed with this Corsair XMS memory, it is PC2700 (166mhz) and I have it maxed out at 175mhz. On my next build I'm going for some XMS PC3500.
I'll lower the clock to 170mhz and report tomorrow morning

 

[titanmiller]

I lowered the memory clock to 173 mhz, I guess I'll find out tomorrow if it fixes it.

 

[lane42]

Isn't there something in win xp that turns off that error report.

 

[moonshinemadness]

Yeah, error reporting , Start>Controll Panel> System Properties>Advamced Tab>Error Reporting Button at the bottom click that and disable it

 

[zaph]

XPanti-spy does a nice job of it. its a small proggie, and disables a lot of thing that "phone home" to Microsoft.

XP anti-spy. To see the english page, click the little UK flag

I put this on a disc that is in my setup/repair toolkit, along with adaware, seti, and a few other "vital" apps.

 

[titanmiller]

Thanks for the error reporting tips, I'll use those in place of the lowered memory clock (which might not help anyway)

 

[titanmiller]

So far, so good. It ran last night and this morning it was in good shape.
But what is the number one rule of any experiment?...only change one vairable at a time. So now I dont know if it was the lowered memory clock or the lack of error reporting. But I'm leaning towards the lower memory clock.