http://www.worldcommunitygrid.org/forums/wcg/viewthread_thread,16784

Thanks for your response. Have you tried this suggestion in the link that Rob posted?

Speedy, Rob -- Without listing all the changed I've made to OET, the problem appears to be in interruptions to the GPU operation.
These are usually initiated by my using the cursor, for various reasons, resulting in suspending/resuming of GPU operations.

Note: I've changed, "Work on Graphic Card" from "yes" to "no".
I assume that would force the OET op. onto CPU usage, exclusively.

Perhaps, not.

In any event, it appears that OET should be a CPU op., only.

Note1: Einstein, for example, has GPU applications, and its WU's
can "ride-through" interruptions. Evidently, the nature of OET
is not as forgiving.

Your ideas?

rr967 --

That makes things quite puzzling, then, from this end.

Examples:

1) All movements of the cursor, resulted in an "exit with 0 status"
(e0s) condition. Until I made some changes to my preferences,
GPU statuses would, also, be outputted; they were not
outputted, towards the end of my trouble-shooting exercise.
A loss of %completed time, however, would always result,
with total %completed times increasing only incrementally.

2) Changes to the line position of the OET WU, on the BOINC
Manager "Tasks" window would result in e0s.

3) Outputs onto the BOINC Event Log, by QCN would, often, result
in e0s.

4) Even without user inputs, background (system?/3rd-party?)
programs would cause eos. The exact source of the interruptions
to the OET WU operations remains unknown.

5) As added info., all BOINC folders were exempt from both the
the N360 and MalwareByte anti-virus programs.

Work was optioned to be left in memory, and 100% CPU
usage was made.

In order to get OET1_0000613-xEBGP-F_rig_75964_0-- to
successfully complete, I had to "suspend" all other BOINC/OET
WU's, except QCN. This would free up approx. three of the four
on-board CPU's, in my Dell.

Any ideas, as to the cause(s) for the eos errs.?