SETI reboots system

[elzmaddy]

I am using the S@H graphical version (which I prefer). I am running a 1.33 AMD TBird, Gigabyte 7DXR, 512MB DDR PC2100, Matrox G550 with Windows XP SP1. I replaced the power supply with an Antec TRUE330W which solved the rebooting problem but it has returned more persistent than before because of S@H. The system will reboot in a few minutes, guaranteed. I am running several processes including Symantec NAV, AntiTrojan, ZoneAlaem, Ad-Watch, MS Outlook, etc. I will try running SETI again with as many things turned off as possible.

 

[minendo]

Are you monitoring your CPU temps at all?

 

[Confused]

Are you overclocking at all?

You may have a bad piece of hardware, which the stress from Seti (or ANY CPU/memory intensive app) could be pushing it over the edge.

I suggest you run Prime95 and Memtest86 to test your system, and memory, for errors.


Confused

 

[MoFunk]

I agree with minenedo. Check your CPU temps.

 

[Smoke]

Systems that reboot, seemingly related to S@H, as you have described are often associated with a FSB setting that is too high.

A system that is OCed to its MAX (tricked out without S@H running) will become unstable when S@H is added to the load.

Is your system overclocked? If so, you might back off slightly and see if that fixes the problem.

If you are not OCing, obviously this advice is useless.

 

[soni]

Try out MemTest86, with settings C-2-3-1-2-0

Let it run a complete test, if it completes its not the RAM (This takes a few hours)

 

[Freewolf]

I was having the same problem and I took off the hs/f fan, removed the cpu and cleaned all the old as2 off then replaced the cpu and hs/f with new as2 and haven't had a problem with it since.

 

[elzmaddy]

Motherboard Monitor says 59C temp with SETI working. No overclocking here. I will give MEMTest a try.

 

[Robor]

As others have said, SETI will push your CPU and RAM harder than under normal operating conditions. A seemingly stable system may be unstable with SETI (or any other CPU/RAM intensive DC app for that matter) running on it.

Hope you get the problem isolated.

 

[Assimilator1]

Yeah it won't be S@H fault directly ,but S@H does heavily load the system ,so if there's a weakness there it may well fail

I recently tried Prime95 myself & it is an excellent stress tester for the CPU/RAM/Mbrd.
I find that if I have overclocked too far it picks it up within 10mins ,I know your not overclocking but it could still pickup a hardware fault.

Btw if you're gonna stick with the GUI S@H then to ensure you get the best out of it you need to have the graphics displayed for as short a time as you can bear.Minimise the window & if its also set as the scnsvr go to screensaver settings in display properties & enable the 'blank screen' & set it to preferable less than 6mins.Doing this will halve WU time!:Q

 

[lane42]

How about a BIOS update, That may Help.

 

[titanmiller]

Make sure you have the most up to date chipset drivers. Downloading new ones have fixed numerious problems for me.

 

[elzmaddy]

I knew it wasn't a heat/stability issue since I used to run SiSoft Sandra stress tests for hours.

... So I booted up into Windows without SETI. Then I killed all processes that are not absolutely necessary, then proceeded to launch SETI. The program continued to run for half an hour or so; system was stable. Then I started to re-launch applications, tray items, etc to look for the problematic process. I got to the point where all processes were re-loaded and SETI continued to work properly. So, basically, the problem is fixed and I have no explanation as to why... heh

 

[TheCorm]

It might have been a conincidence but a rig I was running SETI on kept crashing....I set it to run in Windows 2000 compatibiltiy mode and it was fine (this was with the CLI + Seti Driver combo though...)

Corm

 

[Assimilator1]

elzmaddy
Still would be a good idea to run Prime95 to test your rig,wouldn't take 10mins to do a quick test ,I don't know that SSS would stress test your rig as much as Prime 95 does.
Runs my cpu 2C hotter than SETI on my 2nd rig!:Q