Had a serious lockup on my computer earlier (nothing to do with BOINC, I think). However, BOINC was running in the background at the time.

Everything froze, both the screen and the mouse and keyboard, so I couldn't even do a Ctrl+Alt+Del.

Had to reboot the computer by pressing the Reset button on the tower unit.

Would the BOINC tasks have been corrupted by the PC crash?

Thanks

Tim

Try it out, I would say. Unknown. Not enough information to compute a possible outcome of that question. :-)

---

Would it intelligently check and show me if the tasks were somehow corrupted, or would it just continue blindly?

Can I do anything (such as test them, like carry out a CRC or parity check or something) to make sure it hasn't corrupted them? Or shave off the last 1% or something?

The tasks are 90% the way through. Over 200 hrs of computation on each CPU core.

If the disk they're on is corrupt, you can check it with chkdsk /f (in Windows at least). But other than that, no, there's no way to know if they are corrupt until you start running them again. If there's anything wrong with them, they'll probably go out with an error immediately.

---

They continued running again after the reboot, no errors, but I just wondered if it intelligently checked to see if the last bit of data was bad before blindly continuing.

Thanks

Not of the data on the disk, no. BOINC doesn't know about that either.
It does check for corruption of the client_state.xml file, though. That file is the most important one in the running of BOINC, if it's corrupt, BOINC will automatically switch to the back-up file client_state_prev.xml ... if that one is also corrupt, you're screwed.

But for all these things to happen in a split of a second you first have to start BOINC. There's no way to know from the outside if something went bad. Well, not unless you remember to open up client_state.xml and checked it line by line yourself. ;-)

---