I have a lot of problems with Exit 0 status no finished file (Windows running boinc 6.2.18)

I had a Windows Vista Dual core running on 80% and got a lot of exit0 errors.
Another Windows XP Dual core running on 70% also exit0 errors.

The 1e computer is now on 100% it has a good fan. I think that solves the errors. But it is not ideal.
The 2e computer is set to 50% proc and 100% Cpu. That should result in one core working 100%?
But not ideal as is leaves some cpu time lost.

An exit0 error task restarts by restarting the computer and probably by restarting the task. Some users say this is not a serious error but in most cases I saw that the task was completed and uploaded but got strange results and the tasks where rejected.

Is there any other way to get the tasker to work as I want it to? Without the exit0 errors.

By coincidence I sent off a question to the developers about this subject, I'm waiting for an answer. For the moment it would seem as if the lockfile is left in a state where it cannot be written to anymore, which has the application retrying and retrying until BOINC gives up. Why it does this while throttling specifically, I don't know.

You could try another work-around, being to exit BOINC, go to the affected project's slot and delete the lockfile. You may have to change permissions on it to do so. Then restart BOINC and see what it does.

When you reboot it does delete the damaged lockfile as well, in some 99% of the cases.

---

By coincidence I sent off a question to the developers about this subject, I'm waiting for an answer. For the moment it would seem as if the lockfile is left in a state where it cannot be written to anymore, which has the application retrying and retrying until BOINC gives up. Why it does this while throttling specifically, I don't know.

You could try another work-around, being to exit BOINC, go to the affected project's slot and delete the lockfile. You may have to change permissions on it to do so. Then restart BOINC and see what it does.

When you reboot it does delete the damaged lockfile as well, in some 99% of the cases.

What I have seen is a lot of stange result on these task, completed with 0 points. So retrying does not always work.
I also have some single core machines (Windows XP) without any problems on 100%, 70%. One 24/7.
It can't be a virusscanner problem?
I ruled out: C:\program files\boinc\;c:\programdata\boinc\;c:\users\boinc_master\ from scanning.

It can't be a virusscanner problem?

It can. Or anything else holding the lockfile in place.

---

Fred, can you please contact David Anderson about this on davea at ssl dot berkeley dot edu ? He'll have some specific questions for you and possibly a client to test run with.

---

Fred, can you please contact David Anderson about this on davea at ssl dot berkeley dot edu ? He'll have some specific questions for you and possibly a client to test run with.

I Will

Fred

OK, do know that David lives in California, so he won't react to emails before 15:00h our time (not that I have seen lately anyway). Give him time to wake up. :-)

---

Or anything else holding the lockfile in place.

In such case, Sysinternals' Process Explorer sould reveal it. Actually their Handle should be sufficient to find it.

Peter