I just had 5.70 crash on one of my machines. What is worse, it brought up a dialog box indicating a thrown and uncaught exception. This dialog box effectively stopped BOINC. All exceptions should be caught at the topmost level, and used to generate an error message that is sent back to the project.

---

BOINC WIKI

hello,
4 WU this day - application version 5.70
3 Ok, but 1 "Compute error" : [url=https://ralph.bakerlab.org/result.php?resultid=573411]https://ralph.bakerlab.org/result.php?resultid=573411[url]

---

application version 5.70

Work Unit https://ralph.bakerlab.org/result.php?resultid=573239
<file_xfer_error>
<file_name>1FAB_BOINC_MFR_ABRELAX_2143_43_3_0</file_name>
<error_code>-161</error_code>
</file_xfer_error>

I just had 5.70 crash on one of my machines. What is worse, it brought up a dialog box indicating a thrown and uncaught exception. This dialog box effectively stopped BOINC. All exceptions should be caught at the topmost level, and used to generate an error message that is sent back to the project.

I had one of these too with 1otf__BOINC_SYMM_FOLD_AND_DOCK-1otf_-foldanddock__2186_3_0.

---

Had 3 fail, each for a different reason

code -161 transfer error (completed 35 decoys)
exit code -1073741819 Unhandled Exception Error
code -119 Download Error

Hope this helps

---

wu error - exit code 1 (0x1)

I happend to be looking at grafics when it went wrong.

It suddenly went to model 0 (maybe 1) step 0 and then exit.

Anders n

---

t405 got hung up on Win/XP. BOINC showed about 90 min of runtime, task manager showed no CPU going to the task. Exited and restart BOINC. Now the task shows more then 6hrs in to a 24 hours runtime preference. So, it would seem BOINC lost track of it several hours before it stopped getting actual CPU time.

Seems to be running normally at the moment.

---