I have been struggling to get any downloaded cp workunits to run on boinc 4.45. I get the same error each time: 9/10/2005 12:07:54|climateprediction.net|Unrecoverable error for result 31mw_000163520_2 ( - exit code -1073741819 (0xc0000005))

and a friendly windows error reporting message. I have attempted to reset the project, to detach and reattach and neither help. After a week or so of this, I decided to create a new account to see if the problem was hardware related - and strangely enough the first wu downloaded and began to compute away without errors. Then I went back to my normal account and tried again - same old error. System details - AMD FX-57, 2GB DDR400, GeForce 7800GTX, WinXP x64, three other boinc projects without problems and no other system gripes at the moment.
Does anyone know what's going on here?

edit

<a href="http://boinc-doc.net/boinc-wiki/index.php?title=Unrecoverable_error_for_result_%27%28result%29%27_%28_-_exit_code_-1073741819_%280xc0000005%29%29">Your answer may be here</a>

Notice that I can get cp to run workunits using another account, so I assume that all of my hardware is good. I just would like to continue earning credits on my \"real\" account. But thanks for the help. Can there be something wrong with my account at cp.net?

---

And I have now tried starting my \"real\" account on another pc - it downloaded and began crunching fine - when I tried on my \"real\" pc it crashed immediately. I have no clue what this problem is.

---

There are now two different types of CPDN workunits, and it may be that your computer cannot run one but will run the other. Unfortunately, BOINC decides for you which one to download.

If the WUs that are crashing are HadSM3 you may be able to persuade BOINC to get a Sulphur unit instead. The main constraint is disk space - BOINC will need to be sure that you have plenty, as a Sulphur unit alone uses 2.5 GB, so you would have to alter your preferences to allocate at least 5 GB for safety. You may need to alter all three relevant settings, and remember to update the project in BOINC Manager when you have done so. Unfortunately, some people have found that for some reason they still get a HadSM3 unit eve though they wanted a Sulphur one, but it is worth a try.

Of course, all this assumes that you are willing and able to take on this much larger task.

---

If the WUs that are crashing are HadSM3 you may be able to persuade BOINC to get a Sulphur unit instead.

Since posting this, I gather that there are no Sulphur units currently on offer. The best option then might be to make the changes to preferences that I suggested and suspend the project for a while on that machine, but resuming when they generate more. Meanwhile, you could be crunching for another project.

---

If the WUs that are crashing are HadSM3 you may be able to persuade BOINC to get a Sulphur unit instead.

Since posting this, I gather that there are no Sulphur units currently on offer. The best option then might be to make the changes to preferences that I suggested and suspend the project for a while on that machine, but resuming when they generate more. Meanwhile, you could be crunching for another project.

I got lucky once and one of my downloaded workunits was a sulphur - with the same crash. This one is really baffling me.

---

we are probably going to recompile all apps using Intel Fortran v.9 and see if that helps -- I\'m trying to use it for the coupled model spinups but I\'ve been set back about a week, so not sure how soon I can get to it (maybe Tolu can get around to it)

we are probably going to recompile all apps using Intel Fortran v.9 and see if that helps -- I\'m trying to use it for the coupled model spinups but I\'ve been set back about a week, so not sure how soon I can get to it (maybe Tolu can get around to it)

Thanks for the heads-up.

---

I also have this problem, but only with sulphur. I have noticed that my Windows P4 HT machines have this problem, the non HT machines do not. Further, the HT machines are set to only use one CPU for BOINC.

---

Looks like there was some kind of conflict with graphic card driver - an uninstall and reinstall of the graphics driver seems to fix the problem. Now I am crunching away sulphurs - thanks for the help

---