I'm not a geek but I'm not totally helpless, nevertheless, I have no clue what to do to to clear the fact that my Milkyway@home has computational errors. Any suggestions to get things right - or should I go to another project?

I'm not a geek but I'm not totally helpless, nevertheless, I have no clue what to do to to clear the fact that my Milkyway@home has computational errors. Any suggestions to get things right - or should I go to another project?

If you select the tasks link from your account page and then select one of the error tasks, left hand most column, it will display the results of the task. I selected a couple and in both cases the error is the same:


<core_client_version>7.0.65</core_client_version>
<![CDATA[
<message>
process exited with code 127 (0x7f, -129)
</message>
<stderr_txt>
../../projects/milkyway.cs.rpi.edu_milkyway/milkyway: error while loading shared libraries: libboinc_api.so.6: cannot open shared object file: No such file or directory

</stderr_txt>
]]>

I do not use Linux, but it could be a missing file or perhaps a permissions issue. Maybe someone who runs Linux will post with further ideas. Don't give up this is a great project.

---

I'm not sure why you'd be getting that error. It must pertain to how you installed BOINC. Using Ubuntu here, I just added a PPA that keeps up to date with the latest BOINC clients, so it will automatically upgrade to the latest BOINC over time. It worked perfectly fine after installation without needing to do anything special.

sudo add-apt-repository ppa:costamagnagianfranco/locutusofborg-ppa; sudo apt-get install boinc -y

Me too!
It seems since I did the upgrade from BOINC v.28 to 7.0.64(x64) I now receive a "Computation error" with every (opencl_amd_ati) GPU work unit I do.

Me too!
It seems since I did the upgrade from BOINC v.28 to 7.0.64(x64) I now receive a "Computation error" with every (opencl_amd_ati) GPU work unit I do.

I read another post that left me wondering if may have been the update to AMD Catalyst Version 13.4

I've been running Catalyst 13.4 via xorg edgers PPA with my Radeon HD 7950 without a single problem.

Me too!
It seems since I did the upgrade from BOINC v.28 to 7.0.64(x64) I now receive a "Computation error" with every (opencl_amd_ati) GPU work unit I do.

I'm having the same issue since updating to 7.0.64 (x86).

Had trouble myself when I updated to catalyst 13.4.Had to switch back to 12.8 to work with boinc 7.0.28 x64. Some say it's because openCl. Strangely I tried to switch openCl back to earlier version ( with 13.4) that did not work ( same problem). Catalyst 12.8 had and a openCl.msi installation package versus 13.4 that did not, If I remember correctly, they included (openCl) them in their catalyst installation package.

You could do a test with another project that uses the ati GPU.

Ver 13.4 was removed with the ati catalyst uninstaller.

I Have the same issue. However the errors only occur on milkyway@home. Both Einstenm@home and SETI@home run fine with the 13.4 catalyst driver and boinc 7.0.28 (x64) combination. may be its a bad batch of work units, or the gpu apps for milkyway are not compatiple with this combination.

I Have the same issue. However the errors only occur on milkyway@home. Both Einstenm@home and SETI@home run fine with the 13.4 catalyst driver and boinc 7.0.28 (x64) combination. may be its a bad batch of work units, or the gpu apps for milkyway are not compatiple with this combination.

It depends what the actual reported error is. SETI was plagued with "internal error: Compilation failed" from a number of drivers in the 13.2 - 13.4 range until the application was re-compiled without the "-fno-bin-llvmir" build option.

I allowed a batch of Seti AstroPulse v6.04 and Einstein BRP v1.34 to run and all of them were "Completed and validated" using BOINC 7.0.64 and AMD 13.4. So the problem is specific with MilkyWay. Once I read something has been addressed in this regards I'll go back in and reopen my preference to "Use AMD (ATI) GPU".

You're correct about the error messages being the same. It seems the three "computational errors" are simply the results of three sequential attempts. It means nothing to me, but attempts 1 and 2 died immediately; attempt 3 ran 0.01 seconds. The other two projects are happily buzzing along. Maybe the gods of milkyway@home are busily solving the problem, which clearly is not happening just on my computer.

@George Del Monte

Your mw error logs are showing the following reason for your 'Computation error':

../../projects/milkyway.cs.rpi.edu_milkyway/milkyway: error while loading shared libraries: libboinc_api.so.6: cannot open shared object file: No such file or directory

As I updated from AMD Catalyst 13.1 to 13.4 today, the MilkyWay work units are all failing.

Something that I did not expect, so searching the forum brought up this thread.
Running BOINC 7.0.64 on Win7 64bit AMD 69xx Cayman GPU


The error log indicates an exception, and dumps a BOINC debug trace to the log.
The error seems to occur at the end of processing.

--------------------------------------------
Example for Task: 481431579 WorkUnit: 368827958 computer: 366518


Using AMD IL kernel
Binary status (0): CL_SUCCESS
Estimated AMD GPU GFLOP/s: 2765 SP GFLOP/s, 691 DP FLOP/s
Using a target frequency of 30.0
Using a block size of 6144 with 121 blocks/chunk
Using clWaitForEvents() for polling (mode -1)
Range: { nu_steps = 320, mu_steps = 1600, r_steps = 1400 }
Iteration area: 2240000
Chunk estimate: 3
Num chunks: 4
Chunk size: 743424
Added area: 733696
Effective area: 2973696
Initial wait: 27 ms
Integration time: 37.905295 s. Average time per iteration = 118.454047 ms


Unhandled Exception Detected...

- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x000007FEDE811DCD read attempt to address 0x00000010

Engaging BOINC Windows Runtime Debugger...

I have Catalyst 13.3 for a while on my rig and all MilkyWay's will error out.
Going lower got problems with installing, de-istalling and a lot of pain. Eventually the one proper installed had an app missing according to BOINC and wouldn't crunch Einstein and Albert at home.
They run smooth now, but MW don't. So I have to wait for a new good driver or an update of the MW-app.

---

Greetings from,
TJ

As I updated from AMD Catalyst 13.1 to 13.4 today, the MilkyWay work units are all failing.

Something that I did not expect, so searching the forum brought up this thread.
Running BOINC 7.0.64 on Win7 64bit AMD 69xx Cayman GPU

AMD is again changing their software to favor gamers and not crunchers, they are working on it but don't hold your breath! If you ever find a version that is stable and just works AND you are not a gamer, then don't upgrade unless you hear the new one is MUCH faster and has been tested by others with your configuration. I am still running version 11.9 on one of my pc's and it works here just fine.

AMD is again changing their software to favor gamers and not crunchers, they are working on it but don't hold your breath! If you ever find a version that is stable and just works AND you are not a gamer, then don't upgrade unless you hear the new one is MUCH faster and has been tested by others with your configuration. I am still running version 11.9 on one of my pc's and it works here just fine.

I agree completely!! Updating GPU software/drivers is almost always in-favour of the gamer. 13.4 is currently on my "thou shall not pass" software list.

AMD is again changing their software to favor gamers and not crunchers, they are working on it but don't hold your breath! If you ever find a version that is stable and just works AND you are not a gamer, then don't upgrade unless you hear the new one is MUCH faster and has been tested by others with your configuration. I am still running version 11.9 on one of my pc's and it works here just fine.

I agree completely!! Updating GPU software/drivers is almost always in-favour of the gamer. 13.4 is currently on my "thou shall not pass" software list.

I agree too, but there was an issue with my 12.x version and Einstein@home.
You have 13.4 drivers and MilkyWay is working with no errors, do I understand that from your post correctly?
Then I must update at once.
Thanks.

---

Greetings from,
TJ

I think he means that he refuses to use 13.4. He appears to be using 12.8

<--- 13.1