In the last couple of days, I'm getting a large number of computation errors on CPU type tasks (perhaps all of the CPU type tasks are getting this).

It is not stopping the GPU tasks from running, but it does seem to be causing a problem with automatic updates on BOINC Manager, forcing me to hit the update button manually in order to get credit for the GPU tasks which are continuing to execute.

I've rebooted the machine, to no avail, and reset the project, also to no avail. Did the server send out a bad batch of tasks?

The machine in question is running an AMD Phenom II processor with 4 cores. I don't have the model number to hand at the moment. It was running just fine until the last couple of days. I have made no hardware or software changes to the machine during this time. It is running Ubuntu Linux.

I probably should have mentioned that the machine in question is running the 64-bit version of Ubuntu Linux, in case that matters.

In the last couple of days, I'm getting a large number of computation errors on CPU type tasks (perhaps all of the CPU type tasks are getting this).

It is not stopping the GPU tasks from running, but it does seem to be causing a problem with automatic updates on BOINC Manager, forcing me to hit the update button manually in order to get credit for the GPU tasks which are continuing to execute.

I've rebooted the machine, to no avail, and reset the project, also to no avail. Did the server send out a bad batch of tasks?

The machine in question is running an AMD Phenom II processor with 4 cores. I don't have the model number to hand at the moment. It was running just fine until the last couple of days. I have made no hardware or software changes to the machine during this time. It is running Ubuntu Linux.

It has always been problematic running BOTH the cpu AND the gpu workunits from the SAME project on the same pc, that being said the newest version of Boinc, which you ARE using, is the best at handling this. Other than that I can't help you as I do not run the cpu units from here.
Good luck on finding the answer.

I probably should have mentioned that the machine in question is running the 64-bit version of Ubuntu Linux, in case that matters.

One of you machines is complaining about a missing file:

<core_client_version>6.12.34</core_client_version>
<![CDATA[
<message>
process exited with code 22 (0x16, -234)
</message>
<stderr_txt>
execv: No such file or directory

</stderr_txt>
]]>

So a simple reset of the project or better detach and reattach to the project will fix it.

---

Join BOINC United now!

After several days of this problem, and having to manually invoke the update process, all is well.

I had reset the project before, to no avail. But now, everything is suddenly fine.

I had seen the no file error in the past, and have little idea of why the file becomes missing. But all is well now.

I'm glad that it did not require reloading BOINC, or the drivers, or the OS.

If anyone has any insight into these transient problems, and how they fix themselves, I'd certainly like to know.

Thanks.

I've been having problems the last few weeks, myself. PC will just "hibernate" and can't get back into any programs. Have to manually reboot the PC. I'm using the latest BOINC version, and will see about "updating" as noted above.

Originally, I thought it was YOYO, but took everything out and left just the GPU and Moo.

Some of the error messages I found:


<core_client_version>6.12.34</core_client_version>
<![CDATA[
<message>
couldn't start Can't link input file: 2
</message>
]]>

and

<core_client_version>6.12.34</core_client_version>
<![CDATA[
<message>
couldn't start CreateProcess() failed - The system cannot find the file specified. (0x2): -148
</message>
]]>

---

I've been having problems the last few weeks, myself. PC will just "hibernate" and can't get back into any programs. Have to manually reboot the PC. I'm using the latest BOINC version, and will see about "updating" as noted above.

Check to see that Windows did not make any changes during its updates. One of my pc's got the screensaver turned on, I NEVER use those, and I had to turn it off. As far as having to reboot, that is the ONLY way to reset the gpu in Windows.

Aghh! Found out it was a driver conflict issue. I'm running an nVidia 9600 GSO with my 6970. Was working just fine for several months but something went wrong at some point. Gonna have to troubleshoot this but after uninstalling the nVidia drivers, the 6970 is doing fine so far...

---

Aghh! Found out it was a driver conflict issue. I'm running an nVidia 9600 GSO with my 6970. Was working just fine for several months but something went wrong at some point. Gonna have to troubleshoot this but after uninstalling the nVidia drivers, the 6970 is doing fine so far...

Yeah lots of people use both but when upgrading the drivers always remember the companies are competitors, they don't always place nice together! I have now stopped upgrading when I find a version that works for me, ie I am still on version 11.9 of the AMD drivers, even though 12.2 is now out. I do NOT use both AMD and Nvidia in the same machine though, although I do have two machines with dual gpu's in them.