BOINC itself must ALWAYS be suspended and exited from BEFORE allowing ANY OS update.

But there hasn't been any "short" models for months, so there's no risk of crashing one.

BOINC itself must ALWAYS be suspended and exited from BEFORE allowing ANY OS update.

But there hasn't been any "short" models for months, so there's no risk of crashing one.

Why do you say that? What are the consequences of not suspending and exiting BOINC? It should just resume tasks successfully from their last checkpoints, and that seems to work fine for almost of my projects, I think.

If there's a BOINC problem, I'd like to know about, so please explain a bit further.

Thanks.

Why do you say that? What are the consequences of not suspending and exiting BOINC? It should just resume tasks successfully from their last checkpoints, and that seems to work fine for almost of my projects, I think.

If there's a BOINC problem, I'd like to know about, so please explain a bit further.

My understanding is that the error is caused by incomplete writes to the hard disk.Though, recently I followed the suspend, exit strategy and still lost 4 tasks on one machine. If a write is incomplete but BOINC thinks it is complete because it has gone to cache and the the shutdown process stops the write completing then when BOINC tries to resume the data doesn't make sense and it crashes.

Even if my understanding is completely wrong, doing this seems to reduce the percentage of model crashes when I do a kernel update on my two computers.

Strangely, hibernating the computer I am typing on doesn't seem to crash tasks.

I agree that in an ideal world the code would be more resilient and allow a roll back to a previous checkpoint but don't know what would be involved in making that the case.

“Hibernating” and “Sleep” both leave the task in memory. As long as there is no interruption to the power supply even for a second, then there should be no problem when the computer is reawakened.

---

So after Winddows 10 Creative Update, I am getting this error too. Has it STILL not been solved by BOINC?

I have reset the project. Hopefully this will solve the issues once new work units are downloaded in around an hour.

It is the only solution I can think of.

Hope it helps someone.

Regards,

Marque

---

So after Winddows 10 Creative Update, I am getting this error too. Has it STILL not been solved by BOINC?

I have reset the project. Hopefully this will solve the issues once new work units are downloaded in around an hour.

It is the only solution I can think of.

Hope it helps someone.

Regards,

Marque

EDIT:

After new work units completed downloading, I end up with the same error. I have deleted the entire project and re-joined it again. If this does not sort out the problem, I will have to abandon this project. :(

Regards,

Marque

---