I got this error from this WU:

BAD WU

Edit: I\'ve tried every combination of bbcode tags I can find to get the error code to display. I can\'t quote it and have it display. Please look at the WU itself... I\'m on my 9th edit of the post and am giving up. :P

<core_client_version>4.45</core_client_version>
<message><file_xfer_error>
  <file_name>46ii_100295338_1_1.zip</file_name>
  <error_code>-161</error_code>
  <error_message></error_message>
</file_xfer_error>
<file_xfer_error>
  <file_name>46ii_100295338_1_2.zip</file_name>
  <error_code>-161</error_code>
  <error_message></error_message>
</file_xfer_error>
<file_xfer_error>
  <file_name>46ii_100295338_1_3.zip</file_name>
  <error_code>-161</error_code>
  <error_message></error_message>
</file_xfer_error>
<file_xfer_error>
  <file_name>46ii_100295338_1_4.zip</file_name>
  <error_code>-161</error_code>
  <error_message></error_message>
</file_xfer_error>
<file_xfer_error>
  <file_name>46ii_100295338_1_5.zip</file_name>
  <error_code>-161</error_code>
  <error_message></error_message>
</file_xfer_error>

</message>

and now all further WU\'s error out with:

<core_client_version>4.45</core_client_version>
<message> - exit code -1073741819 (0xc0000005)
</message>

I\'ve tried restarting BOINC and then resetting CPDN on this machine, but I won\'t know for about 10 hours (when communciation is no longer deferred) if it made any difference).

Obviously, the BOINC version, you all can see. The installation is running Einstein@Home as well. I\'m confident the computer is stable (not overclocked, etc.) and well maintained.

Any idea what I can do about this? (I know there are lots of other posts that appear to relate to this problem, but none seemed exactly the same and none seemed to offer any solution or ideas)

---

The secret to posting these errors is to paste, and then edit to change the arrow brackets to square brackets.

The only person I know who has fixed a problem with the error code 1073741819 is <a href=\"http://climateapps2.oucs.ox.ac.uk/cpdnboinc/forum_thread.php?id=3229\"> here.</a> And in his case it appears to have been a graphics card problem.

I\'ve seen reports of error 161, but I\'m not sure what it means.

There are also reports starting to show up that Bern is down yet again.
Have a look in client_state.xml for the model name, and find where the zips are mentioned.
Just before each one is a line about the destination uploader. If it\'s Bern, it will be something like: unib.ch, in which case you\'ll just have to wait until they are back up again.

The secret to posting these errors is to paste, and then edit to change the arrow brackets to square brackets.

Okay, thanks, I\'ll make a point of using a search/replace in a text editor before I post \'em. :)

The only person I know who has fixed a problem with the error code 1073741819 is <a href=\"http://climateapps2.oucs.ox.ac.uk/cpdnboinc/forum_thread.php?id=3229\"> here.</a> And in his case it appears to have been a graphics card problem.

Unfortunately, I\'m sure that\'s not my case. I\'m running BOINC as a service and never display the graphics (screensaver disabled, managed from boincview on another machine)

Have a look in client_state.xml for the model name, and find where the zips are mentioned.
Just before each one is a line about the destination uploader. If it\'s Bern, it will be something like: unib.ch, in which case you\'ll just have to wait until they are back up again.

Okay, I suppose this will be informative as a \'post-mortem\', but the client has terminated/abandoned the run, so it\'s too late to do anything about it now.

I was depressed enough over yet another failed run (my 45th) that I stopped to add up how much processing time was devoted to runs that failed for some reason. 36,032,432 seconds or 417 cpu/days of time that didn\'t produce anything useful. :P I also have 14,189,264.00 seconds towards 2 results that appear to be \'unknown\' though, I think they completed. Thankfully I do at least have 82,252,941 seconds (952 cpu/days) that produced 13 complete runs at least!

\'Tis a bit frustrating to think that 4/5ths of my models are going to error out and therefore nearly 1/3rd of my computing time will be wasted. :\\

---

Well, this is frustrating....

The same computer just got to the end of phase 1 of another sulpher cycle unit and had the exact same error.

Here\'s the result:

http://climateapps2.oucs.ox.ac.uk/cpdnboinc/result.php?resultid=1102562

I can\'t find any reference to what an error -161 is anywhere, but it\'s evidently going to keep happening. :(

Any ideas before I have to take yet another machine off CPDN because it just won\'t run correctly?

---

Sorry, I\'m not able to help you with the 161 error, but it doesn\'t look like an end of phase error as you were 14 trickles into the phase, and the original failure where you were 16 trickles into the phase.

Sorry, I\'m not able to help you with the 161 error, but it doesn\'t look like an end of phase error as you were 14 trickles into the phase, and the original failure where you were 16 trickles into the phase.

Hrmm.... true.

Well, I\'ll make one more check tomorrow to make sure the hardware is working fine, but I checked it with memtest86 and SuperPi after the last failed WU and both completed without so much as a hiccup. Scandisk found no problems, etc.

This is a stock HP/Compaq business desktop... no overclock, nothing but factory original and it\'s only a few months old. This thing runs stable as a rock on anything but CPDN, it seems. :(

---

This is a stock HP/Compaq business desktop... no overclock, nothing but factory original and it\'s only a few months old. This thing runs stable as a rock on anything but CPDN, it seems. :(

I had -1073741819 errors for awhile on one PC. Updated the BIOS and they went away. The BIOS update supposedly fixed some memory incompability...even though Prime95 and memtest ran fine.

Then again, maybe it was some odd software incompatability...

I had -1073741819 errors for awhile on one PC. Updated the BIOS and they went away. The BIOS update supposedly fixed some memory incompability...even though Prime95 and memtest ran fine.

I\'ll check and see if there are any newer BIOS updates beyond what it came with tomorrow.

---

I\'ll check and see if there are any newer BIOS updates beyond what it came with tomorrow.

The only updates beyond what I have are only recommended for some specific hardware issues (none of which apply to this system) and the recommendation is to leave the BIOS I have on the system. Since I take a definite approach of \'if it ain\'t broke, don\'t fix it\', I\'m leaving that alone.

I now see that there are posts over on the other message boards (the CPDN classic ones that I can\'t seem to ever get my account to work on, so I can\'t post to them) about many, many others experiencing this -161 error with suphur_cycles, so I\'m filing this away in the catagory of \"CPDN\'s problem, not mine\".

---

To post on the community board, you have to register there separately.
These boards are at Oxford Uni, and the other is at the Open University at Milton Keynes, about 40 miles to the NE.

Well, now another WU just failed with error code -5 (0xfffffffb).

I\'m going to go nuts if I have to try to figure out the meaning of another error code so I\'m pulling this one off CPDN as well. (Now the 5th machine of 9 that I\'ve had to pull off CPDN because it just won\'t run on them).

The really weird part is that the only machines I have that seem to run CPDN reliably are the 2 that I cobbled together myself. Every single stock PC that I use from Compaq/HP and IBM all error more than they work reliably. All of them run every other BOINC project perfectly and all complete every stress test I throw at them perfectly (Memtest86+, SuperPi and Prime95 torture tests), but they just can\'t seem to do CPDN. :(

---

The really weird part is that the only machines I have that seem to run CPDN reliably are the 2 that I cobbled together myself. Every single stock PC that I use from Compaq/HP and IBM all error more than they work reliably.

hmmmmmmm

maybe not so wierd after all

I think the machines you put together probably use better hardware than the HP/Compaq junk

---

Anyone yet have any idea what these -161 errors are or mean?

I just had another one fail with it:

http://climateapps2.oucs.ox.ac.uk/cpdnboinc/result.php?resultid=1136194

---

Your original post mentioned 4.45
Assuming that this the BOINC version, there is a bug in it.
I posted a long reply to another person about this yesterday.
Rather than re-type it all again, you can read what I said <a href=\"http://climateapps2.oucs.ox.ac.uk/cpdnboinc/forum_thread.php?id=3412\"> here.</a>
Some of it may be useful to you.

Anyone yet have any idea what these -161 errors are or mean?

The -161 errors are not the real problem. They indicate that the application has finished running and BOINC is attempting to upload result files that haven\'t been created.

The -161 errors are masking the real problem, which might be revealed by looking at the stdoutdae.txt and stderrdae.txt files in the BOINC directory.

---

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

Your original post mentioned 4.45
Assuming that this the BOINC version, there is a bug in it.

Thank you for the reply Les, but I\'ve been using the custom compliled 4.45b client since about the 3rd time I had my clients cease processing CPDN due to the \'failure to exit\' benchmark bug, so I\'m sure that\'s not the problem.

I\'m just now opening and looking at the files that Thyme suggested to see what I can find there.

---

The -161 errors are not the real problem. They indicate that the application has finished running and BOINC is attempting to upload result files that haven\'t been created.

The -161 errors are masking the real problem, which might be revealed by looking at the stdoutdae.txt and stderrdae.txt files in the BOINC directory.

No Thyme, I\'m afraid I must disagree... there are no other errors in either of those files that indicate anything beyond exactly what appears in the result that I linked to. Just in case, I\'m copy/pasting (replacing the \'evil characters that won\'t display\' with [ and so forth) the exact output here:

From stderrdae:

2005-11-07 21:37:48 [climateprediction.net] Unrecoverable error for result sulphur_480b_000297275_0 ([file_xfer_error]
[file_name]sulphur_480b_000297275_0_1.zip[/file_name]
[error_code]-161[/error_code]
[error_message][/error_message]
[/file_xfer_error]
[file_xfer_error]
[file_name]sulphur_480b_000297275_0_2.zip[/file_name]
[error_code]-161[/error_code]
[error_message][/error_message]
[/file_xfer_error]
[file_xfer_error]
[file_name]sulphur_480b_000297275_0_3.zip[/file_name]
[error_code]-161[/error_code]
[error_message][/error_message]
[/file_xfer_error]
[file_xfer_error]
[file_name]sulphur_480b_000297275_0_4.zip[/file_name]
[error_code]-161[/error_code]
[error_message][/error_message]
[/file_xfer_error]
[file_xfer_error]
[file_name]sulphur_480b_000297275_0_5.zip[/file_name]
[error_code]-161[/error_code]
[error_message][/error_message]
[/file_xfer_error]
)

and from stdoutdae:

2005-11-07 21:37:48 [climateprediction.net] Unrecoverable error for result sulphur_480b_000297275_0 ([file_xfer_error]
[file_name]sulphur_480b_000297275_0_1.zip[/file_name]
[error_code]-161[/error_code]
[error_message][/error_message]
[/file_xfer_error]
[file_xfer_error]
[file_name]sulphur_480b_000297275_0_2.zip[/file_name]
[error_code]-161[/error_code]
[error_message][/error_message]
[/file_xfer_error]
[file_xfer_error]
[file_name]sulphur_480b_000297275_0_3.zip[/file_name]
[error_code]-161[/error_code]
[error_message][/error_message]
[/file_xfer_error]
[file_xfer_error]
[file_name]sulphur_480b_000297275_0_4.zip[/file_name]
[error_code]-161[/error_code]
[error_message][/error_message]
[/file_xfer_error]
[file_xfer_error]
[file_name]sulphur_480b_000297275_0_5.zip[/file_name]
[error_code]-161[/error_code]
[error_message][/error_message]
[/file_xfer_error]
)

I\'ll swear on as big a stack of bibles as you\'d care to put before me that there is absolutely nothing immediately before, nor after those errors that indicate anything other than the normal operation of the client (pausing, switching, downloading, uploading stuff, etc.)

---

I\'ll swear on as big a stack of bibles as you\'d care to put before me that there is absolutely nothing immediately before, nor after those errors that indicate anything other than the normal operation of the client (pausing, switching, downloading, uploading stuff, etc.)

OK, but that doesn\'t take away the fact that the the error messages are caused by BOINC attempting to upload result files that don\'t exist. Which can only happen if it thinks the application has completed.

---

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