SETi Crashing constantly

[barbary]

Alll of a sudden I am constantly getting windows up on the screen saying seti-3.08-...exe has created an error do you wish to send an error report to Microsoft.

I'm getting it all the time and it's killing production. Not to mention that sometimes I get this message but if I have another app running then it causes the machine to lock or blue screen.

I assumed that this has been caused by an automatic update as that is the only thing that would have changed on the machine over the past two weeks.

I came on here expecting to see lots of people complaining about it but nothing so is this just me?

If so it's not likely to be a hotfix is it.


Anyhelps people greatly received as at the moment I am having to stop running SETI on this mchine so I can get some work done.

 

[amdxborg]

I'm not sure what the problem can be, but you should definitely consider running the CLI ver 3.03 as described here. For me it was almost twice as fast as ver 3.08!

 

[barbary]

It was running 3.03 version when this first started.

 

[JWMiddleton]

Hey Barbary!

Could it just be the system? I have a box that I ran for over 3 years and it ran like a champ! It started acting up recently. I tried all kinds of things, to include reloading windows. David suggested I try a new PS, I did and now it will not even boot. I looked closely and found a buldging Cap very near the PS connection. I can only assume it was going and that the other PS pushed it over the edge.

Good luck with it!

John

 

[lobadobadingdong]

you might try checking your temps with speedfan as well, it's possible your heatsink has gotten full of dust causing your processor to overheat.

I'd also suggest trying a fresh install of your seti folder in case it's just a matter of your files becoming corrupted.

 

[barbary]

If it was an older machine I might go with that . My dual 1.7 has given up the ghost after about 3 years good service in a very hot room.

This thing is 6 months old and in an Air conditioned room.

Anyway it's only Seti that has this problem. I can run product compiles that Max the machine out all day and it never crashes or blue screen or errors.

It has to be SETI nothing else is popping up error messages.


I found a hotfix from the 13/1/05 which is roughly when this started. i have uninstalled it but am still getting the problem.

 

[Starrider]

I had one machine with the same problem, turned out to be a bad work unit causing the problem.

 

[Unforgiven]

could also be a bad stick of ram. try running memtest and see if anything comes up.

 

[cakin]

it was a stick of ram that got me also

 

[Coolkid]

Originally posted by: Starrider
I had one machine with the same problem, turned out to be a bad work unit causing the problem.

I've just had the same problem myself...

 

[emjem]

I had a problem when I increased Client Priority to "High"

 

[barbary]

Now I have seen one bad work unit before and have been able to refresh it and get a new one.

So last night I dumped all 600 units on the machine and got 600 new ones same thing.

I've also tried running it in isolation. It seems that certain work units are causing it to crash but I'm getting loads of them. It does point at something has changed on the machine.

If it was anything to do with the hardware I'm sure I'd be seeing crash's in other apps. When I do product builds the machine is far more stressed than by Seti becasue the hard drives heat up to boiling point and it uses over a gig of ram instead of 256Mb like when it's running four SETI's.

 

[Unforgiven]

why dont you do some testing on a smaller cache of units than 600? are you using seti driver? if so, i had some serious issues with trying to cache over 40 units at a time using seti driver where i would get huge system slowdowns when it was switching from one workunit to another.... im not so sure that downloading a cache of 600 units is the best way to troubleshoot a problem. start with 5 units and try to successfully crunch those and move up from there.

 

[Wiz]

I've seen several posts here and elsewhere where people had trouble with large cache's

If you run seti cli alone - no seti driver etc do you still have the crashing?

 

[barbary]

I don't use seti driver.

If I just run seti in a single directory allowing it to get new WU and continue sooner or later SETI crashes.

 

[Assimilator1]

Hi mate! ,longtime no see!

I hear what your saying about other proggies not crashing the rig ,only SETI ,but it could still be a partial hardware failure.Its possible that SETI is using some part of the CPU/mbrd/RAM that other programs don't ,anyway I have seen a rig crash when running SETI but was otherwise ok (at least for a few days or so).It turned out to be RAM ,I'm not saying it is on yours but I would say you can't rule out a h/w problem at this point.

Time to swap out gear I think ,starting with RAM

Btw v3.08 CLI is about 15% slower than 3.03 on normal AR WUs

GL