Dear,

Since I got my new laptop at work, I seem to be receiving all computation errors on my WU's for ps_seperation tasks. The multithreaded tasks complete fine.

This is all CPU only.

Does any1 else have these problems?

I don't see any errors for your tasks since they've cleared out by now

Will one of you Milkyway@home Gurus please help us out on this "computation error on the ps_separation_82..." I could be using my ATI HD 4770 on Vista 32-bit OS to do a lot of Milkyway number crunching if somebody would give us an answer.

I keep seeing info about app_info.xml and have copied two of the many on this forum and added app_info.xml to path C:\ProgramData\Boinc\projects\milkyway.cs.rpi.edu_milkyway but still get the computation errors. I'm not sure I'm doing this right so, please tell me very specifically how to setup (do I just set it up as a text file and name it app_info.xml?) app_info.xml and where specifically to place it; in other words I want the path in it's entirety. Thanks in advance.

I've detached Milkyway, stopped then started Boinc, and attached Milkyway all
to no avail.

SO, PLEASE HELP!!! Frustrated Cruncher!

---

I think you need to update your Catalyst driver. Older Catalyst versions have not worked since the MilkyWay ATI applications were updated about 6 months ago. I use Catalyst 11.3, some have had problems on MilkyWay with Catalyst versions newer than 11.3.

Ok, I'll try that. Thnak you kindly, kashi.

Hello,

I paused my current milkyway work. I will upload a result now that has the error message.

Can hibernating cause this issue? I do pause my work before I hibernate and I have the option to keep work in memory.

EDIT: This is the task:

115687258 80444060 328105 26 Sep 2011 | 10:13:58 UTC 3 Oct 2011 | 6:14:20 UTC Computation error 14,385.74 13,573.75 --- MilkyWay@Home v0.88

Thanks!

Matthias

Does hibernating preserve the graphics card memory? I suspect that it doesn't, only the memory used directly by the CPU.

Hey Robert, I don't use a gfx card for boinc. My lappy only has an intel onboard chip :).