It happens to me sometimes that my monitor suddenly stops working, then goes back on and folding@home GPU client says:
- Code: Select all
[13:15:59] Completed 74%
[13:16:05] Run: exception thrown during GuardedRun
[13:16:05] Run: exception thrown in GuardedRun -- Gromacs cannot continue further.
[13:16:05] Going to send back what have done -- stepsTotalG=10000000
[13:16:05] Work fraction=0.7403 steps=10000000.
Apparently something went wrong. That can happen sometimes. The problem is that this always happens when I start a task that uses the GPU, for example start a 3d-game or play a video. Therefore I don't think it is necessary for folding@home to stop working on the workunit and send back the unfinished work. I think it would work fine if, when something like this happens, folding@home would go back to the last saved state of the workunit and try again before giving it up. As long as I don't start other applications that use the GPU, folding@home works fine, always. Also it always goes wrong when those applications are starting up, not while they are already running. That means there is nothing wrong with the work units. They can actually be finished. Gromacs can cantinue further. I think valuable work is being wasted by returning these work units unfinished, while they could have been finished if the client didn't give it up so quickly.