Have you checked cpu temp etc. Later Athlon mobo's have protection cct to protect cpu when overheated.
Does it boot and run if you suspend Boinc?
Have you tried any other high cpu programs like Prime95 etc

Have a look in Paul's Wiki How Too Guides

Andy

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.

The reason for no 'n' on the end is because it is really Redirect IO (Redirect Input/Output) not Redirection.

Sorry for hijacking this thread. Just thought that the Scarecrow might want to know.

---

Sorry for hijacking this thread. Just thought that the Scarecrow might want to know.

heh... well don't I feel silly now. Makes perfect sense. Thanks for pointing that out. I'll get around to reading the manual real soon now. :)

I get the same symptom when I overclock close to the edge.
If your cpu temp is ok under load you could try, if your motherboard has this feature, to raise the Vcore and se if that makes the problem to disappear.

---

Have you checked cpu temp etc. Later Athlon mobo's have protection cct to protect cpu when overheated.
Does it boot and run if you suspend Boinc?
Have you tried any other high cpu programs like Prime95 etc

I'm really suspecting the COP (CPU Overheat Protection)now. Last two days it was very warm (about 28 degrees inside) so that might explain why I have this problem and did not experience it before.

Need to find that utility that tells me the CPU temperature...

---

I get the same symptom when I overclock close to the edge.
If your cpu temp is ok under load you could try, if your motherboard has this feature, to raise the Vcore and se if that makes the problem to disappear.

What exactly would raising the Vcore imply?

---

I get the same symptom when I overclock close to the edge.
If your cpu temp is ok under load you could try, if your motherboard has this feature, to raise the Vcore and se if that makes the problem to disappear.

What exactly would raising the Vcore imply?

when you overclock your cpu it runs hotter by raising your Vcore you can get your cpu to run a little cooler but never raise your Vcore more than .025 volts above stock or you risk frying your CPU.

---

I'm really suspecting the COP (CPU Overheat Protection)now. Last two days it was very warm (about 28 degrees inside) so that might explain why I have this problem and did not experience it before.

Need to find that utility that tells me the CPU temperature...

You could try Everst Home Edition but there are several more. You may even have one on the mobo CD.

Andy

---

I get the same symptom when I overclock close to the edge.
If your cpu temp is ok under load you could try, if your motherboard has this feature, to raise the Vcore and se if that makes the problem to disappear.

What exactly would raising the Vcore imply?

Take a look at your manual to se if there is an option of alter the voltage for the cpu in BIOS. In my case I can change the Vcore up to 1.725 V and are currently running my Athlon 3000+ Venice at 2700 MHz, Vcore 1.625V and cpu temp under load is 47 C, original setting is 1800 MHz and 1.4V. But remember that you should only try this if your cpu temp is whit in the normal.

James! you have got this totally wrong, you ad heat to the cpu by raising the Voltage but if you manage to keep the cpu cool you might be able to clock it to a higher level.

Tomas

---

I get the same symptom when I overclock close to the edge.
If your cpu temp is ok under load you could try, if your motherboard has this feature, to raise the Vcore and se if that makes the problem to disappear.

What exactly would raising the Vcore imply?

Take a look at your manual to se if there is an option of alter the voltage for the cpu in BIOS. In my case I can change the Vcore up to 1.725 V and are currently running my Athlon 3000+ Venice at 2700 MHz, Vcore 1.625V and cpu temp under load is 47 C, original setting is 1800 MHz and 1.4V. But remember that you should only try this if your cpu temp is whit in the normal.

James! you have got this totally wrong, you ad heat to the cpu by raising the Voltage but if you manage to keep the cpu cool you might be able to clock it to a higher level.

Tomas

by raising voltage you lower amperage and lower the temp or so I was told

---

I would not say that I am a pro on this James but if you raise the voltage and watch the cpu temp the numbers speaks for it self. If I got this right a cpu is build up by 2 different transistors PNP & NPN and you can 'burn in' your cpu by raising the Vcore and maybe underclock to cep it cool while running a cpu intensive program for a couple of days. After that you might be able to run the cpu at a higher clock rate while using a lower Vcore than was possible at the beginning. What actually happens during the burn-in time is that the tolerance on one type of the transistors is lowered and on the other one it is raised but in total the tolerance is raised.

Tomas

---

You should not have to up the voltage to a processor running at stock speed. All you will be doing is adding heat - witch could be the culprit here.

Does it lock up IMMEDIATELY after you run SETI, or does it take a few good seconds?

If you can get into your computer's BIOS, there is usually a "PC Health" section that will show you current voltages, temps, ect. If you know your board's manufacturer and model, you can usually download a utility that will let you see thoes figures from within Windows itself.

---

--
"Life moves pretty fast. If you don't stop and look around once in a while, you could miss it." - Ferris

I'm really suspecting the COP (CPU Overheat Protection)now. Last two days it was very warm (about 28 degrees inside) so that might explain why I have this problem and did not experience it before.

Need to find that utility that tells me the CPU temperature...

You could try Everst Home Edition but there are several more. You may even have one on the mobo CD.

Andy

Thanks, I lost the CD that came with my motherboard and could not find the utilities that were on the CD on the ASUS website. This should be a good alternative. Interesting that SETI seems to suffer more from a 'hot CPU' than other projects...

---

You should not have to up the voltage to a processor running at stock speed. All you will be doing is adding heat - witch could be the culprit here.

Does it lock up IMMEDIATELY after you run SETI, or does it take a few good seconds?

If you can get into your computer's BIOS, there is usually a "PC Health" section that will show you current voltages, temps, ect. If you know your board's manufacturer and model, you can usually download a utility that will let you see thoes figures from within Windows itself.

Actually, I reset the project and now SETI is running again. I did not(yet) encounter freezes, but the temperature in my house is down a few degress as well, so this might be related.

When I did have the freezes, it froze just a few seconds after the reboot was complete, BOINC was started and the SETI project was starting work on a WU. When I was quick enough to suspend the SETI project, BOINC started another project and I had no freeze...

---

I would not say that I am a pro on this James but if you raise the voltage and watch the cpu temp the numbers speaks for it self. If I got this right a cpu is build up by 2 different transistors PNP & NPN and you can 'burn in' your cpu by raising the Vcore and maybe underclock to cep it cool while running a cpu intensive program for a couple of days. After that you might be able to run the cpu at a higher clock rate while using a lower Vcore than was possible at the beginning. What actually happens during the burn-in time is that the tolerance on one type of the transistors is lowered and on the other one it is raised but in total the tolerance is raised.

Tomas

It seems that I should not try overclocking before I can run SETI in normal circumstances, doesn't it.

---

Even if you don't know much about your motherboard, this utility can probably tell you what you need to know about your temps:
http://www.majorgeeks.com/download337.html

---

I have had this happen to me on my AMD 3200 XP+ and I have found that is usually after I overclock, you need to find the sweet spot for speed and temperature and that can take some tweeking, as for raising core voltage and I could be wrong, if you overclock the cpu will try to draw more power and this in itself will generate heat if it is trying to pull more power than what is avalable, that said if you raise the core voltage by say .025 volts the power is there to be used so the heat generated is proportional, (warning overclocking can reduce the life of your CPU and other components of your computer overclock at your own risk).

Thats my experience anyway.

It seems that I should not try overclocking before I can run SETI in normal circumstances, doesn't it.

No. In your case you should take a look at your cpu temp first. If everything looks normal you could then try to raise the Vcore, that might stabilize your computer.

---

No. In your case you should take a look at your cpu temp first. If everything looks normal you could then try to raise the Vcore, that might stabilize your computer.

OK, installed speedfan and it seems my CPU temperature becomes 81,5 degrees when running BOINC. It's a Athlon XP 2100+ running at 1733MHz. I don't know if it is near any CPU Overheat Protection (COP) treshold.

---

OK, installed speedfan and it seems my CPU temperature becomes 81,5 degrees when running BOINC. It's a Athlon XP 2100+ running at 1733MHz. I don't know if it is near any CPU Overheat Protection (COP) treshold.

81.5 sounds very high... bad CPU fan? Some other heat problem? I would expect that chip, unless seriously overclocked, to be down around 50. MAYBE 60. But I have no experience with 2100s, someone else may have other ideas.