In my stats, all results for cp show \"Client Error\" in the outcome column (except of course the on ein progress). Some have stderr <core_client_version>4.25</core_client_version>
<message> - exit code -1073741502 (0xc0000142)
</message>
others have different error messages. Why would I want to spend processing time if the result is garbage?

---

Hi Joe

Obviously you don\'t want to waste your time. Cpdn is the toughest of all the boinc projects to crunch because the work units are so big and last so long.

Have a look at the cpdn php discussion forum (the middle one of the 3 forums) and in the very first section, about 4 threads down, you\'ll find that Crandles has posted a sticky about the meanings of many of the error codes with links to more info and ideas about possible solutions.

If all else fails and you still want to stay with cpdn, you can crunch classic cpdn instead of boinc cpdn. You can\'t share classic with other boinc projects, but it has big advantages for machines that don\'t get along with boinc cpdn - it runs at about the same speed, you get visualisation, and it is very stable ie hardly ever crashes. You get to the download through the Open University course link on the left hand menu of the cpdn main page.

---

__________________________________________________

Have you read the <a href=\"http://www.climateprediction.net/board/viewtopic.php?t=2124\"> maintenance</a> info, and the <a href=\"http://www.climateprediction.net/board/viewtopic.php?t=2126\"> tests</a> info?

Mo.v: I knew that cpdn uses a lot of resources to process one package, the more the reason of my first question. I also participate in einstein@home and seti@home.

The forum post you mentioned points in the right direction. I updated my client und see what happens...(I also ran the 4.25 before).


I\'ll get back here as soon as I know more.

---

mo.v: A client updet seems to have solved the problem. Thank\'s a bunch for the hint.

---