Discussion in 'Videocards - AMD Radeon Drivers Section' started by Hilbert Hagedoorn, Nov 4, 2019.
what major issue do you have?
I quote myself to confirm these drivers are working flawlesslly for me on Destiny 2
Ahh i see, thanks!
So all the bugs from before are still ruining gaming on the 5700 series?
I don't understand, AMD lists the API as 1.1.125, so why is the loader left at 1.1.114?
Some of them have been fixed, but I not all of them have been addressed as of yet, unfortunately.
can rvii owners use wattman again to OC or is that still broken?
Meanwhile there is a new one:
Still missing here. Had it with recent drivers, with rx480, on Windows 7...oh well)
Had same issue with my rx480 and 1607.
It works on RX580 with 19.11.1, I don't have RX 5700 to test it on, but I see people say that they removed it from RX 5700.
Yeah 19.7.5 is still the most stable here for whatever reason though reading through forums and the AMD Reddit there's plenty of other 5700/5700XT users who have no problems at all and others using 19.9.2 as the most stable driver so it's kinda hard to nail it down to anything specific other than just something in the driver software possibly also affected by specific hardware and the GPU itself doesn't seem to exhibit anything that would indicate that it's faulty so it's a complicated little mess of a situation with whatever is going on.
Not too much of a issue with using older drivers though until this can be confirmed as fixed assuming it is entirely in software or the display drivers though a few games might have some fixes in later drivers that go beyond just ~3 - 5% performance gains and support for newer Vulkan extensions if required though not many games are using these so far.
Well, for what it's worth, 19.11.1 are working really well for me so far: Red Dead Redemption 2 (Vulkan), Destiny 2, Shadow of the Tomb Raider, Battlefield V, Batman: Arkham Knight, The Division 2, The Outer Worlds, World of Tanks and Apex Legends.
So finally Stable driver for Navi
Now i can wait for Big Navi HBM.....
Game wise it's definitively among the most stable drivers since Navi launched and there's no visual glitches or errors other than the boost sensitivity under lower GPU workloads.
Still hits periodic black screens and restarts during idle though, would be really interesting to know just what the card is doing particularly in what differentiates a black screen display loss and recovery and a full restart. Takes around one day too before it happens but that could just be coincidental.
EDIT: Well there's the draw distance visual glitch in Outer Worlds but that's minimal in what it affects.
So 19.8.1 and later here causes display cursor corruption after a few hours of uptime and after that black screen display loss but it always recovers.
19.9.3 and later is where it starts doing the restarts instead.
19.7.5 so far I have tested it for about two weeks before testing a newer driver and comparing results with and no problems other than the known issues for how Navi operates and the display cursor loading or "spinner" discoloration which still happens in 19.11.1
(Seen a few other posts about it but testing doesn't indicate anything's off with the hardware such as memory problems so not sure if it's anything but it seems harmless.)
Well, there are still some quirks here and there, but the driver's team have clearly made some significant strides in the right direction
Jonas, I've noticed two different 'black screen' issues with Navi. One of them is a genuine bug from the drivers, and you're forced to hard reset the system. The other one can be caused by a way too aggressive undervolting, but this one can be recovered through a driver restart (Winkey+Shift+Ctrl+B).
Sorry for the double post - I'm on my phone.
Im pretty sure that bug is because of hardware acceleration from some apps.
Chrome/steam/discord/battlenet/spotify - I have hardware acceleration off
Yeah I know the Chromium hardware acceleration issue cropped up around then affecting Steam and Discord for example and yep undervolting can be tricky with how Navi scales and boosts and varying demands on the GPU, raised the initial amount after testing to find lower settings crashed in The Outer Worlds which for some reason or another is very demanding on the card and excellent for stability testing.
Set the fan profile to a minimum of 60% in something like Division 2 and the drivers will hold that with plenty to spare before hitting the temperature threshold, set it to 60% in TOW however and after a while it boosts to probably near 100% meaning it hit the 95 degree limit and the fan is ramping up further in response which can also be confirmed with Wattman itself listing 95 degrees as the peak junction temperature.
Testing so far has amount to just idling and doing little with no other background tasks running and stock settings, undervolt and almost overvolted at ~1500 Mhz boost target and 1150mv plus clean settings with Wattman disabled as to see if there's other glitches just by manually enabling settings here which some users discussed but it seems to be more on how conservative Wattman is with auto undervolting compared to what users set.
From 1260mv default at 2100Mhz <- WTH really. And then auto undervolt shifts it to 1118mv here which I keep around 1100mv at 1900Mhz currently and it's holding.
Can be lowered further but I keep a bit extra as needed and temps are already down a bit with almost no real impact to performance though 1900 to 1950 Mhz is what the GPU usually boosts to anyway before calming down.
(Can be tuned a bit via the power limit slider and core voltage and clock speeds but generally it'll be around 50Mhz lower than the target boost and at least on my end it doesn't easily breech 2 Ghz anyways so it can be reduced from that stock setting trying to target 2.1 with no real performance impact as a result of never reaching it to begin with.)
EDIT: I've also seen reports on how the Chromium Engine Framework issue might have resurfaced after 19.10.1 again but nothing seems to confirm this though there are still the occasional post about Discord causing a driver crash so there could be some situation where it could still happen.
Hah so much to read up on and check plus my own system is a bit aged by this point putting it mildly although I am curious as to how the earlier drivers can be stable and the newer ones apparently are less so though could be just about anything, it's a complex piece of software these drivers after all.
Not too worried although mostly curious and trying to figure out or learn more on this but it's not going very well because there's so many possibilities and there's a good number of Navi specific issues remaining as well which could lead to other regressions when fixed or who knows.
Hoping a few more months can start really settling these last remaining stability problems at least and then the performance issues and various game specific issues can be dealt with over time but until then 19.7.5 for me and tests as newer drivers get released and seeing how these operate.
Then go full stupid with new system build and start really clearing out any possible issue hopefully by mid 2020 ha ha. I'm learning, well I'm learning I have more to learn if nothing else.
EDIT: As to using earlier drivers there's no real problem, can even install the latest and use the device manager to retain Catalyst Settings and the rest and maybe place the VLK or DXGI/D3D11/D3D12 .dll files in specific game folders there's usually no real hinder unless a newer game completely breaks on a earlier driver which I think for Navi there's not much here yet.
For Vega the earlier 2017 drivers completely fail at Assassin's Creed Odyssey but then performance is improved and overall compared to the 2019 drivers the difference is at most 10% or so from testing done by users so it's generally fine as far as framerate is concerened at least.
(Newer Vulkan games might want the later AMD VLK driver .dll file and a manual install of the Vulkan runtime files but Surge 2, Rage 2 and Wolfenstein Youngblood all handle just fine as is although Red Dead Redemption 2 could be a exception.)
EDIT: Still a really fast card too so in that regard when it works it's definitively recommended for anyone considering a AMD GPU but the software side well that's more variable.
My own experiences are a bit more mixed but that's a good opportunity to learn a bit and tinker some more plus as long as 19.7 is stable there's no real problems so far and this system is about to be replaced as soon as the resources and hardware allow for it.
Boost performance problems for D3D9 and a few select games does need to be resolved though as that's a blocker far as having the GPU perform at ideal levels of #BetterRed but it'll happen in some later driver.
(Well it would be kinda silly if it wasn't resolved at least.)
After finding my previous issue were related to a hidden miner on my system, I'm having 0 issues with this driver on my Vega 64.
Glad to be able to use sharpening on some of these newer DX12 titles like SoTTR, since they often appear a bit blurry.