I have just restarted my secondary pc after a year’s absence and I’m seeing many WUs crashing with the above exit code, mostly after a few seconds. (So far no WUs have successfully completed but a couple are running ok).

The system is a Ryzen 9 3900 with 16gb ram and 256gb nvme running Ubuntu 22.04 and Boinc 7.18.1.

My first guess is memory, maybe fuzz on the connectors but I thought I’d ask if anyone had had similar problems?

I have just restarted my secondary pc after a year’s absence and I’m seeing many WUs crashing with the above exit code, mostly after a few seconds. (So far no WUs have successfully completed but a couple are running ok).

The system is a Ryzen 9 3900 with 16gb ram and 256gb nvme running Ubuntu 22.04 and Boinc 7.18.1.

My first guess is memory, maybe fuzz on the connectors but I thought I’d ask if anyone had had similar problems?

It's not confined to the SiDock Project so probably a workunit config that works on most systems but not on every one for some reason...I don't know.
https://yafu.myfirewall.org/yafu/forum_thread.php?id=305#1157

Now that thread is from 2018 but I see it on other Projects as well.

I have just restarted my secondary pc after a year’s absence and I’m seeing many WUs crashing with the above exit code, mostly after a few seconds. (So far no WUs have successfully completed but a couple are running ok).

Hello!
Would you try:
1. Project reset;
2. If reset didn't help:
2.1. Get multiple tasks;
2.2. Suspend network activity immediately after that;
2.3. After errors occur, copy files with names like _1 and _0 (if present) into separate directory and post it (or link to download) here. Perhaps, these files will contain a clue.

Thank you for participation!

I have just restarted my secondary pc after a year’s absence and I’m seeing many WUs crashing with the above exit code, mostly after a few seconds. (So far no WUs have successfully completed but a couple are running ok).

Hello!
Would you try:
1. Project reset;
2. If reset didn't help:
2.1. Get multiple tasks;
2.2. Suspend network activity immediately after that;
2.3. After errors occur, copy files with names like <task_name>_1 and <task_name>_0 (if present) into separate directory and post it (or link to download) here. Perhaps, these files will contain a clue.

Thank you for participation!

I shut down the pc, removed the memory and cleaned the connectors, reseated the memory and restarted. Since then it’s run clean overnight so I think it was just that the machine had been sitting unused for too long.

The WUs that are running should complete soon and I’ll confirm when they do.

I have just restarted my secondary pc after a year’s absence and I’m seeing many WUs crashing with the above exit code, mostly after a few seconds. (So far no WUs have successfully completed but a couple are running ok).

The system is a Ryzen 9 3900 with 16gb ram and 256gb nvme running Ubuntu 22.04 and Boinc 7.18.1.

My first guess is memory, maybe fuzz on the connectors but I thought I’d ask if anyone had had similar problems?

It's not confined to the SiDock Project so probably a workunit config that works on most systems but not on every one for some reason...I don't know.
https://yafu.myfirewall.org/yafu/forum_thread.php?id=305#1157

Now that thread is from 2018 but I see it on other Projects as well.

Thanks, that was exactly the stderr output I was seeing but it looks clean now.

The WUs that are running should complete soon and I’ll confirm when they do.

This is good news! Thank you for notice!

The WUs that are running should complete soon and I’ll confirm when they do.

This is good news! Thank you for notice!

The next 6 WUs have all finished clean in just over 24 hours with several more about to finish. Happy days :-)

The WUs that are running should complete soon and I’ll confirm when they do.

This is good news! Thank you for notice!

The next 6 WUs have all finished clean in just over 24 hours with several more about to finish. Happy days :-)

WOO HOO!!! You may have just solved a problem since the beginning of Boinc!! I sure hope so anyway!!! You should get that adde4d to the Wiki page of Boinc errors.

The WUs that are running should complete soon and I’ll confirm when they do.

This is good news! Thank you for notice!

The next 6 WUs have all finished clean in just over 24 hours with several more about to finish. Happy days :-)

WOO HOO!!! You may have just solved a problem since the beginning of Boinc!! I sure hope so anyway!!! You should get that adde4d to the Wiki page of Boinc errors.

If you point me at it I'll update it :-)