Could somebody please check out this work unit 1248606781 . A weird thing happened . I suspended seti for a few minutes and when I restarted it I got a computation error my and screen stoped working then came back on after a couple of seconds without the background . A few seconds later it came back . 1 GPU unit waiting to run and had scheduled something but now only says waiting to run 1 unit computation error and 2 more GPU units started up . I'm wondering if it was just a glitch and others have reported this happening to them .

---

linkable that'd be http://setiathome.berkeley.edu/result.php?resultid=3004725733

Exit status 194 (0xc2) EXIT_ABORTED_BY_CLIENT

,
Googling this There has been some discussion on boinc dev of client abort after finish happening back around March, and looks unresolved. As you are using a newer build, I would suggest signing up to boinc forums, and gathering some more information for them as they request (which may require sending some logs, running with some additional logging or debugging flags enabled)

Jason

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

Sorry Jason this is probably a stupid question but are you talking about signing up to the Luantics web site ?

---

Sorry Jason this is probably a stupid question but are you talking about signing up to the Luantics web site ?

No, Boinc ( http://boinc.berkeley.edu/dev/. ) In essence, the weird error task you linked to shows successful completion by the science application (x41g, last third party public Release) & that it handed back control to the Boinc (client), via boinc_finish, which summarily killed the completed task for reasons unknown. The Boinc client needs to not do that ;) [Edit: or at least a reason might be nice]

Jason

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

thanks Jason for your help but it has only happened 1 time . There is nothing in the event log . I suspected something else mite have happened so unless it happens again i'll try something else and then I can cross out what I think my have caused it

---

Actually, I've seen a similar error where when the Seti project is resumed from being suspended with active GPU tasks one of them may abort for some mysterious reason. If I recall right, it hasn't happened since I installed 7.0.64 of Boinc.

Since seeing this, I avoid suspending the project when there are GPU work units active. I let them complete first.

Never a problem with CPU work units however.

However in my case, the display continued to work through this. The display doing that might be a driver crash followed by recovery.

---

It´s happens here too when a GPU task is running and stoped for some time and you run a game for example (something that heavely use the GPU) and the GPU task is restarted after that. Seems like something corrupt the GPU memory/task or the driver. But that not allways happening so it´svery dificult to replicate.

---

It´s happens here too when a GPU task is running and stoped for some time and you run a game for example (something that heavely use the GPU) and the GPU task is restarted after that. Seems like something corrupt the GPU memory/task or the driver. But that not allways happening so it´svery dificult to replicate.

Jb hi good to see you at seti we talked on the Einstein pages some time ago .

I don't play games on this machine so it would not be that for me .I have found a few things in the windows event logs that may explain it but unless it happens again i'll say nothing . Don't wish to look like a fool . You might check your windows event logs next time it happens and then contact me and we will compare logs

---