Ok I started this project 4 years ago and switched to an AMD... immediately got nothing but comp errors. Asked about this here and was told everything from the machine was overclocked (which I wouldn\'t even begin to know how to do) even though it was straight out of the box. Fast forward 4 yrs. Dual core AMD 3000+... again...nothing but comp errors and this is the only project I am having this issue on. Runs fine on my dual intels.

---

You could disable HadAM in the project settings and try one of the smaller model types (HadSM3) first.

HADAM seems to be quite demanding, I managed to trash one of those too where other models run fine.

A number of HADAM3 models on Vista on 64-bit processors have been crashing. It\'s being investigated.

I agree with Ananas, switch away from HADAM3 for the moment. HADSM3 are short, and HADCM3 very long. It might be worth doing a few HADSM3 to start with.

[Edit: In another of your posts you mention a concern that work would be lost if BOINC were uninstalled. That shouldn\'t happen: when BOINC uninstalls it leaves the project data behind. So, if you re-install BOINC to the same place then the work will start again where it left off.]

Ok I started this project 4 years ago and switched to an AMD... immediately got nothing but comp errors. Asked about this here and was told everything from the machine was overclocked (which I wouldn\'t even begin to know how to do) even though it was straight out of the box. Fast forward 4 yrs. Dual core AMD 3000+... again...nothing but comp errors and this is the only project I am having this issue on. Runs fine on my dual intels.

I\'m willing to bet money it\'s Vista. Are you happy with Vista? Or could you go back to Windows XP? If not, then are you running the 32-bit BOINC or the 64-bit BOINC? (Does it say x86 or x86_64?)

Ok I started this project 4 years ago and switched to an AMD... immediately got nothing but comp errors. Asked about this here and was told everything from the machine was overclocked (which I wouldn\'t even begin to know how to do) even though it was straight out of the box. Fast forward 4 yrs. Dual core AMD 3000+... again...nothing but comp errors and this is the only project I am having this issue on. Runs fine on my dual intels.

I\'m willing to bet money it\'s Vista. Are you happy with Vista? Or could you go back to Windows XP? If not, then are you running the 32-bit BOINC or the 64-bit BOINC? (Does it say x86 or x86_64?)

http://boinc.berkeley.edu/download_all.php

vista 32bits => boinc 6 version 32 bits
vista 64bits => boinc 6 version 64 bits

XP 32bits => boinc 5 version
XP 64bits => boinc 5 version 64 bits

---

Thanks for all the replies. To the person who I bet it was Vista. I dont think Vista was out in 04 when I started this project. I am running them happily on Vista on two intels, the AMDs just don\'t like it. The one I attempted to run on this year has 4GB RAM, 1024 dual L2, and two 3000+ processors. Nothing that CPN could throw at me should be too big for the machine.In 04 it was XP SP1.

Again thanks all. I decided to just crunch CPN on the faster dual intel (though not as fast as the AMD) Rosetta on the other intel and keep SETI on the AMD. Though I would really like to dedicate the power of the AMD machine to CPN since the WUs ARE so big.

Forgot I AM running 32 bit Vista on a 64bit capable processor... thinking about upgrading to 64 bit Vista, one reason I just stuck 4GB of memory in her.

---

Thanks for all the replies. To the person who I bet it was Vista. I dont think Vista was out in 04 when I started this project. I am running them happily on Vista on two intels, the AMDs just don\'t like it. The one I attempted to run on this year has 4GB RAM, 1024 dual L2, and two 3000+ processors. Nothing that CPN could throw at me should be too big for the machine.In 04 it was XP SP1.

Again thanks all. I decided to just crunch CPN on the faster dual intel (though not as fast as the AMD) Rosetta on the other intel and keep SETI on the AMD. Though I would really like to dedicate the power of the AMD machine to CPN since the WUs ARE so big.

Forgot I AM running 32 bit Vista on a 64bit capable processor... thinking about upgrading to 64 bit Vista, one reason I just stuck 4GB of memory in her.

Forogt I am running boinc 6.2 for 32 bit Vista as well.

---

That\'s a shame that the AMD\'s don\'t work as well running Vista. I\'ve had very good luck with the AMD Opteron chips, but I can\'t say anything about the new Phenom or Athlon 64 X2.

[I\'m willing to bet money it\'s Vista. Are you happy with Vista? Or could you go back to Windows XP? If not, then are you running the 32-bit BOINC or the 64-bit BOINC? (Does it say x86 or x86_64?)

http://boinc.berkeley.edu/download_all.php

vista 32bits => boinc 6 version 32 bits
vista 64bits => boinc 6 version 64 bits

XP 32bits => boinc 5 version
XP 64bits => boinc 5 version 64 bits[/quote]

I hope this does come off the wrong way, but I have a question about the 64 bit version as well and I\'m a bit confused. I just upgraded my main system to Vista 64 bit over the weekend from XP SP3 (32bit). I\'m running boinc 5.10.45 with einstein attached to this computer. I\'d read somewhere there were problems with Vista and that we needed to install boinc in its own directory. (ie. C:\\boinc or whatever partition) On this box I have einstein attached and haven\'t had any problems. I have another box with Vista 32 bit that is running CPDN and Milky Way. (boinc set in its own directory there as well.

What is the benefit of using 64 bit boinc as opposed to the 32 bit version? I\'ve heard different projects have or don\'t have 64 bit programs. My main system \"Will\" be the only 64 bit OS here and running einstein.(which I don\'t know if they have a 64 bit version or not)

---

The main benefit is a larger address range, for more memory.
It\'s been reported that a small number of projects (count them on the fingers of one hand), do run faster with 64 bit systems, but most don\'t.
This project, for instance, uses 80 bits of resolution, and there is no difference with this for the floating point unit (FPU), in 32 & 64 bit OS.

PS
The \'64 bit\' models here are just 32 bit models wearing a mask and cape so that they appear to be a more powerful 64 bit model.

I am running 6.2 Boinc for Windows for the 32 but system but the HDAM still crashes.... have two slabs running on it now but not happy.....

---

Crashes caused by running the current BOINC 5 version of hadam models on BOINC version 6 is a known problem. They only work on V5.
The V6 models are still in beta testing.

The main benefit is a larger address range, for more memory.
It\'s been reported that a small number of projects (count them on the fingers of one hand), do run faster with 64 bit systems, but most don\'t.
This project, for instance, uses 80 bits of resolution, and there is no difference with this for the floating point unit (FPU), in 32 & 64 bit OS.

PS
The \'64 bit\' models here are just 32 bit models wearing a mask and cape so that they appear to be a more powerful 64 bit model.

Well I got brave and upgraded boinc to the 64 bit version. Lost 2wu\'s with 9+ hours each computing time, but einstein resent them them as well as the others in my cache.

So my next question is - when my sysem hits the scheduler for more work will it then make a determination as to whether or not to send me a 64 bit wu on it\'s own or will I need to use an app_inf.xml file? (provided that the projects support 64 bit wu\'s)

Thanks.....

[edit] I\'m sorry that I am mentioning einstein in this discussion, but I\'m running CPDN on another computer and right now this is a test case to see if I want to change the other system to a 64 bit OS.

---

The only \"64 bit\" models here are slabs. (32 bits in disguise.)
See this page.
So, provided you haven\'t excluded them in your model types selection area, BOINC will automatically send you some.

The only \"64 bit\" models here are slabs. (32 bits in disguise.)
See this page.
So, provided you haven\'t excluded them in your model types selection area, BOINC will automatically send you some.

Thanks Les....

I\'m running slabs on that computer already for the shorter run times. (Less chance of my screwing something up. <smile>

---

Ok here is the latest message for the Slab model I am running on the AMD

8/28/2008 12:38:08 PM|climateprediction.net|Task hadsm3fub_jxym_005962145_0 exited with zero status but no \'finished\' file

What the heck? Should I just give up? I use this comp for work and actually take it offline about 4 hours a day to LINUX live. I always take it off after a save point and shut down properly.

---

Did you do a forum search?
Or look in the READMEs here?

This error message has been around for years, and is talked about all over the boards. If you look in README - Crashes and other problems, you\'ll see it mentioned 4 down from the top.

Just ignore the message.

---

Backups: Here

Thanks for your response.

No, I did not do a forum search and have gone over the readme so many times to try and figure out exactly why my AMD machines keeps crashing WUs, I can\'t begin to count. That must have been something I missed.

Since I had already started this thread I figured this would be a good place to ask.

---

Any chance you could unhide your computers to let us look at the AMD details and the exit codes and messages for its crashed models? Without being able to see the computer, people are bound to give general advice rather than anything specific to your problem.

---

Cpdn news

I think whoever said that the HDAM3 doesn\'t run well on AMD64 was correct... the last two crashed at exactly 36 mins.... Anything else seems to run fine on her. I was just alarmed at the last message thinking I was in for another crash. Thankfully it is running quite smoothly as of now. HAve no idea of what happened with the old computer except that every WU crashed on it. Hadn\'t had a similar problem on any other project. The slab seems to be ticking along.

Thanks a lot!!!

---