I am going to spend some time specifically looking into the GPU issues for the next couple days. Can everyone please post the exact issues you are having here? This includes quotes of the error messages you are seeing and any other information you think is useful. I've been going through old forums posts trying to decide where I think the problem is and I am still unsure where the problem is.

don't know if this helps, but milkyway@home did not seem to find my GPU in the last few days (GPU missing under BOINC status).
The GPU did work fine with other projects like SETI or Asteroids at that time.

Could be related to the Win10 Anniversary Upgrade, or the latest NVIDIA drivers update (GTX 750 Ti here). At least Windows did not mess with the driver, as the nvidia one was still installed.
But after reinstalling the same drivers (no clean install) milkyway is now again using the GPU so far.

There are too many computation problems with work units dated 1st August. The longer the work unit the more likely it is to be aborted . Has anyone else reported the same problem ? Is it the age of my computer at fault (6 yrs) or is there a problem with the data in the work units ?

Looks like your problems are with N-body, please post them over in number crunching. It is not appropriate to post them here were we are discussing GPU issues.

boboviz,

When you are running without the anonymous platforms, what do you see from the server? Do you get error messages? Does it just send CPU work units and pretend you don't have a GPU? What are you seeing on your end?

Pe,

I think your error was a one off due to Windows. Seems like a super minor problem with a simple fix. Going to focus on the other issues for now.

When you are running without the anonymous platforms, what do you see from the server? Do you get error messages? Does it just send CPU work units and pretend you don't have a GPU? What are you seeing on your end?

It depends.
Sometimes "got 0 new task" (specially if queue is empty), otherwise like other volunteers "Ati does not support Opencl"
https://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=3824
I have 260x and crunch with Seti, Einstein, Poem, etc without problems

Quick progress report: I am working on updating the BOINC API code we build into our clients to be up to date. Maybe this will fix some of the compatibility issues with more modern GPUs, maybe it won't. Its the only thing I can think of updating at this point that may provide a quick fix. If it doesn't work we will try some more drastic options. Expect these new binaries to be released within a week or so after they have received proper testing and compile on all platforms.

Since "modfit" is discontinued, I remove / add Milkyway to starts on fresh files.
The 1st time I connect the manager, I get the "classicc" message as my R600 AMD gpu isn't recognize!!
Now it only say me : "got 0 new task"

Quick progress report: I am working on updating the BOINC API code we build into our clients to be up to date. Maybe this will fix some of the compatibility issues with more modern GPUs, maybe it won't.

I think this is the solution. It's not a problem of gpu driver, but of boinc server...