AMD 5700XT Win10: 98% GPU-tasks invalid or inconclusive (0 points)
10 Aug 2019 8:50:15 UTC
Topic 219358
(moderation:
Hi folks.
The problem exists for new 5700 XT AMD GPU on Win10 OS: almost every GPU task (for the last approx 1 month since I bought this GPU) is failed having "incorrect" or "inconclusive" status, at the same time for the same PC most CPU-only task is ok.
Failed task example: https://einsteinathome.org/task/872036173 -- unfortunately I can not understand where is a problem from this log-file.
Only a few GPU tasks are valid: https://einsteinathome.org/host/12764660/tasks/4/40
Using this ( i.e. https://einsteinathome.org/workunit/414170017 ) one can see that 2 AMD 5700(XT) can overcome 1 Nvidia GPU. It seems that new Navi GPU results are not the same as other GPU results, nor Nvidia not AMD.
Vit-MIPT wrote:Hi folks. The
)
You need to go to AMD.com and download, and then install, the drivers for it, the Windows drivers are not ones that can crunch.
AMD OpenCL driver for Navi 10
)
AMD OpenCL driver for Navi 10 is not working, It can't be used for crunching in any BOINC project while AMD does not solve it.
Look here
https://einsteinathome.org/es/content/all-things-navi-10
Mikey, thank you, but AMD
)
Mikey, thank you, but AMD driver had already been installed from the very first day of this Navi GPU in my PC from AMD site. It was not installed by Win10 automatically. I can see on amd.com the latest version is 19.7.5 now and mine is 19.7.2. This is the only difference. Also we can see I can crunch but validation passed only when 2 of 3 GPU are 5700 (4 tasks per month in my case, see link above), then 5700 gives the same result and "wins" by majority rule, because Navi GPU results differ from any(?) other GPU results.
Trotador, thank you. I did
)
Trotador, thank you. I did search in "Problems and Bug Reports" only. So sad to see it is a global problem with Navi and OpenCL.
It is not a purely global
)
It is not a purely global problem. The 5700xt works on other BOINC projects (MilkyWay and Collatz).
Just running a quick diff on the stderr of the 5700xt vs a GTX 1080 doesn't show any obvious errors. The 5700xt omits a few zeroes compared to the 1080, but that is no different than the output of my other AMD GPUs (Fury-X, Vega64, Radeon VII)
https://einsteinathome.org/workunit/420044319
5700XT output (left) vs GTX 1080 output (right)
% nf1dots: 41 df1dot: 2.512676418e-15 f1dot_start: -1e-13 | % nf1dots: 41 df1dot: 2.512676418e-015 f1dot_start: -1e-013Other than a quick diff, I haven't had a chance to do any further debugging. Once AMD releases a new driver I will fire up Einstein on the 5700xt again.
One interesting task that validated: https://einsteinathome.org/workunit/419969386
On first glance it looks like two 5700's validated against each-other, but a third 5700 result was marked invalid. Looking at the runtime of the invalid result, I'm guessing that it actually wasn't ran on a 5700, but no way to verify without knowing if the 5700 is the only gpu in the system.
*Edit* The only results on my machine that were ran on a 5700XT are the tasks that were returned on 9/24. All of the other tasks were run on either a Vega64 or a Radeon VII.
You may be interested in this
)
You may be interested in this paragraph of Anandtech review: https://www.anandtech.com/show/14618/the-amd-radeon-rx-5700-xt-rx-5700-review/13
https://einsteinathome.org/ta
)
https://einsteinathome.org/task/883822367
https://einsteinathome.org/task/883841559
https://einsteinathome.org/task/884875802
So far I see three valid and hundreds of invalid with my RX 5700 XT. This is with the latest 19.9.2 driver.
I have a 5700 XT and am
)
I have a 5700 XT and am witnessing the same exact behavior. I really hope this gets fixed. It's a shame so much results went down the drain :(
Lubomir, according to this
)
Lubomir, according to this message https://einsteinathome.org/content/all-things-navi-10?page=3#comment-174312 you can "switch your prefernces to allow Gravitational Wave search O2 Multi-Directional GPU instead" with no errors and no energy waste.
I tried that yesterday, and
)
I tried that yesterday, and when I updated the project in the BOINC manager the old GPU tasks were still in the queue and I didnt see any new GPU tasks for Gravitational Wave search O2 Multi-Directional search. Do I have to wait for the old ones to expire to start receiving new ones that are only for Gravitational Wave search O2 Multi-Directional? I also tried manually aborttng the old GPU tasks and still no new ones.