Noticed an error in a task a few days ago, https://asteroidsathome.net/boinc/result.php?resultid=530611304
"The operating system cannot run L;��.
(0xc2) - exit code 194 (0xc2)"
Any idea what that's about? Seems to be the only one like it so far, and two other computers did return valid results for that WU, so it's not a problem with it I guess.

exit code 194 = ERROR_ITERATED_DATA_EXCEEDS_64k

I can't verify the work unit because it has already been successfully processed by other hosts, but the issue might stem from the code (AVX512?) or a random system failure on your host.

all of your other tasks (~2200) were valid, so it looks like a random glitch... I have no idea, sorry.

ok, a correction, exit code 194 means EXIT_ABORTED_BY_CLIENT which is raised by the boinc. It's hard to say why the WU has been aborted on your side. You may run out of memory, free disk space, there was an unexpected shutdown or something like that...

Had two more of those on MilkyWay@home since, and looked it up and found a discussion on the SETI@home boards about it 11 years ago: https://setiathome.berkeley.edu/forum_thread.php?id=73704
Just skimmed the first page, but what seemed most relevant was quoted from another thread: "One of the last things an app does before exiting is write an empty "finish file", and that error indicates the app didn't exit within ten seconds after writing that file. I think the error was likely caused by shutting BOINC down after the file was written but before the app had gotten to its usual exit"
In my case, thinking the task was suspended at such an... inopportune time as I was trying to balance the projects. That is assuming that BOINC didn't fix the issue in these 11 years...

There was a change in how long a finish file is allowed to be created and cleared back in 2019. Closed issue. I haven't seen any instance of that bug since then.

---

A proud member of the OFA (Old Farts Association)

Maybe it can still happen if that delay runs in the hours and/or if BOINC or the WU is active during that time, if being suspended in memory would still count it as active in some way?