Message boards : BOINC client : BOINC is NOT robust against BSOD / lockups
Message board moderation
Author | Message |
---|---|
Send message Joined: 29 Nov 05 Posts: 9 |
X-Plane (8.32 this time) BSOD on the video driver (nv4disp), instead of locking up on the machine. Seems to be about twice a week. the BSOD took out most of BOINC's setings and SETI is back to the currupt banner.jpg thing and LHC's .exe is missing and both LHC and einstein did resets. I managed to get my LHC work copied. BOINC seems to leave the orphaned work in the directories. I found 3 orphaned CPDN workunits. Is there any way I can get these reconnected? and can the dev people make BOINC more robust against hard crashes by bad games and buggy video drivers? |
Send message Joined: 25 Nov 05 Posts: 55 |
A number of people have have problems with CPDN and DirectX in particular. This is something that the project team will need to look into, but they are very busy at the moment on other things. In the meantime, the only protection is to suspend BOINC when playing games like this. There is not much you can do to recover lost work unless you have a backup. Regular backups are worthwhile with CPDN anyway because of the long crunching times. When making a backup, suspend or close BOINC (depending on your method) and backup the whole folder. Restoration from backup isn't a problem with CPDN even if the server state for that unit is flagged as error. However with other projects it is more problematic as those WUs may have been returned since the backup. |
Copyright © 2025 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.