SETI question: It causing crash?

Luden

Platinum Member
Jul 15, 2001
2,269
0
0
Hey guys,

I've only been at it for a few days with SETI project, but since I've started my computer has shut off several times. I havnt had this problem before i started, anyone have any ideas?

btw: system specs
AMD 1800, 512mb ram, Xp pro, temp is around 105f, and im using method 2.

Thanks,
Luden
 

Crazee

Elite Member
Nov 20, 2001
5,736
0
76
Are you overclocking? If so you might want to back off a little bit. Seti has a way of exposing when a machine might be a tad past where it should be run.
 

aiex

Senior member
Jul 5, 2001
914
0
0
what crazee said

Basically i have often used seti as a good stress test on new machines, it is very good at showing up floors that would later develope. Have u any idea of what u/it was doing when it shut off?


ALex :D
 

Luden

Platinum Member
Jul 15, 2001
2,269
0
0
I do not overclock and I'm not sure what it was processing when it shut off, I keep it minimized.

-Luden
 

Crazee

Elite Member
Nov 20, 2001
5,736
0
76
Hmm what kind of power supply do you have on the machine? Do you have any programs that are running in the background while Seti is running?
 

aiex

Senior member
Jul 5, 2001
914
0
0
could it be possibly a bad stick of ram? i've had that happen before and seti has shown it up

Good luck

Alex :D
 

Smoke

Distributed Computing Elite Member
Jan 3, 2001
12,650
207
106
Well, your temp is fine. So heat is not the problem though the symptoms point in that direction.

Is this a fairly new system?

Are there other apps running when these shutdowns happen?

We have tons of rigs like yours running the CLI Client so it seems like some component may be the culprit. And of course SETI is pushing it over the edge. :(

If you have any components that can be switched out for test runs you may be able to pin point the problem.
 

Poof

Diamond Member
Jul 27, 2000
4,305
0
0
Look out if you have Crucial RAM. :( I had a machine start doing that about a week ago (ie., suddenly locking up when running SETI, even when not OC'd, after having run just fine for months on end). I need to replace the stick just to confirm though. I've already replaced at least 2 sticks of Crucial in other machines. :() I had heard tell that some bad batches of Crucial had gone out recently, so it may be the luck of the draw.

[EDIT: Even if it wasn't Crucial, it seems that bad RAM will lock you up tight]
 

Smoke

Distributed Computing Elite Member
Jan 3, 2001
12,650
207
106
Poof

Is there a generally accepted ranking of RAM manufacturers? The higher the price, the better the product (Using Price Watch as a yard stick)? Or is it subjective?

I'm sure there are performance differences from stick to stick but I was just interested in an overall ranking.
 

Luden

Platinum Member
Jul 15, 2001
2,269
0
0


<< Hmm what kind of power supply do you have on the machine? Do you have any programs that are running in the background while Seti is running? >>



330 watt enermax, running in the background is usually msn messenger, winamp, callwave.



<< could it be possibly a bad stick of ram? i've had that happen before and seti has shown it up >>



yeah.



<< Is this a fairly new system? >>



About a month old.



<< Look out if you have Crucial RAM >>


:( yes i do, I'll try using some ram testing software. I dont have another ddr rig to test it in.


Thanks guys, I really appreciate your help.

-Luden.


 

Poof

Diamond Member
Jul 27, 2000
4,305
0
0
Smokeball - I know that various tech sites like this one, do tests on different manufacturers' RAM every once in awhile. I think over the years, companies like Crucial and Mushkin and Corsair were known for their QA and better performing chips. A higher price often comes along with this extra quality (due to what they have to do in their manufacturing process, testing, etc.). However, price doesn't always mean a thing if you consider, for instance, the Kingmax Tiny BGA RAM, which is cheaper than the "name" brands but an excellent performer according to reviews and people at forums like these.

I think that in Crucial's case, they may have just had a bad batch. Running DC projects on it like SETI is prone to bring out any problems that the RAM might have and I've been reading a bit too many posts (especially in the CPU/OCing forum) from people who have had to RMA their Crucial over the past 4 - 6 months.. :(