Since yesterday my computer freezes up completely. No mouse movement, no keyboard and after a reboot it took only a few minutes to completely freeze again.

After some digging around I found out that it was BOINC and to be more precise, as soon as the Setiathome_4.18_windows_intelx86.exe file was started a freeze was the result.

As I suspected a bad file and as I did not have problems before, I deleted the file. BOINC just downloaded a new one and the freezes came back just the same.

Any of you know what can be the problem?

Problem with the filesystem? With the HDD? Memory? Power supply? Graphic card or video drivers??

---

you could try to suspend the Wu that its trying to crunch and see if it still freezes on the next one.

---

Have you tried the newest version of BOINC?

---

Thanks for the advice, will try that...

My BOINC version is 4.45 (always has been). I think that is the newest version

---

Hm, it already chocked on 3 different WU's. Other projects seem to have no problems, just seti. I don't want to reset the project (yet) as I still have two finished WU's in the upload queue...

Will try a reset after the finished WU's are gone.

---

if seti is causing your problems, have you suspended Seti activities? Also, I am assuming you are running a Windows OS. Have you ran defrag and scandisk? It's a long shot, but it can't hurt.

---

Another thing may be something was added to the computer that is conflicting with Seti. Have you recently added any new software/hardware shortly before the freezes started?

---

To truly explore, one must keep an open mind...

try "network activity suspended" under the the "file" menu, then click "exit" under the "file" menu, then reboot and restart. does the issue continue? this will tell you if it's network related, or maybe graphics.

tony

also is this your old machine? 500mhz?

Since yesterday my computer freezes up completely. No mouse movement, no keyboard and after a reboot it took only a few minutes to completely freeze again.

After some digging around I found out that it was BOINC and to be more precise, as soon as the Setiathome_4.18_windows_intelx86.exe file was started a freeze was the result.

As I suspected a bad file and as I did not have problems before, I deleted the file. BOINC just downloaded a new one and the freezes came back just the same.

Any of you know what can be the problem?

I had the same problem with a laptop running Windows 98. I hardly use it and just let it run seti. However if I run another application, say Word, then it was freezing just as you describe. I suspect that the machine is near its processing and memory capacity just running seti. I hardly touch it now and I have not had a repeat of the problem for some weeks. I know that isn't going to be a very useful option for you but it may help in some way. :)

p.s. I also reduced to an absolute minimum other stuff that was loading at startup.

---

if seti is causing your problems, have you suspended Seti activities? Also, I am assuming you are running a Windows OS. Have you ran defrag and scandisk? It's a long shot, but it can't hurt.

You're right, i'm running Windows, did a defrag, and a scandisk. Unfortunately it does not help. Thx for the suggestion though

---

try "network activity suspended" under the the "file" menu, then click "exit" under the "file" menu, then reboot and restart. does the issue continue? this will tell you if it's network related, or maybe graphics.

tony

also is this your old machine? 500mhz?

Nope my old Pentium III 450 Mhz does not have any problems. This is a 2100+ Athlon XP with 1 GB memory.

Thanks for the suggestion on "network". I will try that, so at least I can 'locate' the error a bit better. Do you really think it might be graphics related? I'm not running the screensaver, you know.

---

I had the same problem with a laptop running Windows 98. I hardly use it and just let it run seti. However if I run another application, say Word, then it was freezing just as you describe. I suspect that the machine is near its processing and memory capacity just running seti. I hardly touch it now and I have not had a repeat of the problem for some weeks. I know that isn't going to be a very useful option for you but it may help in some way. :)

p.s. I also reduced to an absolute minimum other stuff that was loading at startup.

Unfortunately this problem occurs with a 2100+ athlon XP with 1 gb memory :-(

---

If you haven't run a spyware stopper type program, you may want to consider it.
I haven't seen it happen to boinc or seti specifically, but I've seen several other programs start locking up or otherwise misbehaving due to some little gem that found it's way onto the computer.

Another thing may be something was added to the computer that is conflicting with Seti. Have you recently added any new software/hardware shortly before the freezes started?

I did install the new catalyst drivers (5.7) for my ATI card recently, but I think I've been running with them for about three weeks before the freezes started...

I've not upgraded to catalyst 5.8 yet.

---

If you haven't run a spyware stopper type program, you may want to consider it.
I haven't seen it happen to boinc or seti specifically, but I've seen several other programs start locking up or otherwise misbehaving due to some little gem that found it's way onto the computer.

I already ran Hitman-pro, but it did not find anything. Nu hits with virusscanner as well...

---

I already ran Hitman-pro, but it did not find anything. Nu hits with virusscanner as well...

There's always booting up in good ol' safe mode with minimal drivers and see if it helps. If it flys right then, quite likely some driver isn't playing nice.

I already ran Hitman-pro, but it did not find anything. Nu hits with virusscanner as well...

There's always booting up in good ol' safe mode with minimal drivers and see if it helps. If it flys right then, quite likely some driver isn't playing nice.

thx, will try that as well. Is there some sort of log-option' in boinc 'so that I perhaps find out until which instruction the computer worked? The only thing I can do after a freeze is a 'hard reset' and I'm not sure where to find any error reports...

---

Is there some sort of log-option' in boinc 'so that I perhaps find out until which instruction the computer worked?

I have about zero experience with the Windows client, all my seti participation has been with Linux, so I'm not sure if this applies directly to Windows.
There is a -redirectio command line option that sends output to a log file.
The lack on an 'n' on the end of 'redirection' isn't a typo, at least in the Linux versions I've run adding the apparent missing 'n' doesn't work. The logs won't show op code debugging, only the messages output by the client. But, it still might hold a clue or two.