I'm a new user and would like to contribute to the project but can't as program will not run due to error in executable. I get this error:

Error signature

AppName: hadsm3um_4.04_windows_intelx86.exe AppVer: 0.0.0.0 ModName: hadsm3um_4.04_windows_intelx86.exe
ModVer: 0.0.0.0 Offset: 0044b1b9

Any suggestions as to how to fix this?

-gunnersfan_us

I forgot to mention I'm running Win XP Pro with SP2 on an Athlon XP 3200+

-gunnersfan_us

How much RAM? Do you OC your machine?

---

<img src="http://boinc.mundayweb.com/one/stats.php?userID=444&amp;trans=off">

Just like you said, it looks like something you downloaded is corrupt or missing. You have a couple of options:

1) doing a project reset should force a re-download.

2) delete the downloaded files one by one followed by a project update to force download of that specific file. I'd start with hadsm3um_4.04_windows_intelx86.exe then each of the hadsm3 zip files and finally the model zip file.

---

"The ultimate test of a moral society is the kind of world that it leaves to its children." - Dietrich Bonhoeffer

Gareth,

You got it. Overclocking was the problem. I have an Atlon XP 3200+ which has a multiplier of 11. I discoved I got an unlocked chip and have been running at 12.5 for some time without any troubles.

Thanks for the tip.

-gunnersfan_us

They do recommend participants don't OC their machines whilst running BOINC. If you have to OC your chip, just make sure your RAM can run at the same speed, that you have adequate voltages and most of all, you invest in an adequate cooling solution for the chip.

From 11 to 12.5 is not actually a huge OC (if I read you right), unless your RAM or PSU isn't up to scratch. Remember, when you drive the clock up, you drive the FSB (Front Side Bus) speed up too. So your RAM has to be able to run at this new FSB frequency.

I'm just glad I could be of service.

---

<img src="http://boinc.mundayweb.com/one/stats.php?userID=444&amp;trans=off">

&gt; From 11 to 12.5 is not actually a huge OC (if I read you right), unless your
&gt; RAM or PSU isn't up to scratch. Remember, when you drive the clock up, you
&gt; drive the FSB (Front Side Bus) speed up too. So your RAM has to be able to run
&gt; at this new FSB frequency.
&gt;

The way I read it was that he was running at 12.5x200 (2.5 GHz) instead of 11x200 (2.2GHz). A 300 MHz OC at the top end of the AthlonXP line is quite a bit, unless you have really good cooling, although I know a lot have gotten XP-M's higher.

&gt; The way I read it was that he was running at 12.5x200 (2.5 GHz) instead of
&gt; 11x200 (2.2GHz). A 300 MHz OC at the top end of the AthlonXP line is quite a
&gt; bit, unless you have really good cooling, although I know a lot have gotten
&gt; XP-M's higher.
&gt;
Now you put it that way... I see what you mean. That is quite a hefty OC now I see it in MHz!! Give it to me in MHz... I'm useless with clock multipliers.

One of the things I said was cool is king! My CPDN box has a 1900+ Athy under the hood with cooling spec'd for a 3000+ (same socket design). I don't OC my boxes, but I do believe that cooler components last longer.

---

<img src="http://boinc.mundayweb.com/one/stats.php?userID=444&amp;trans=off">