Astyanax:

Did you upgrade the driver with AB running?

Humm i dont know.. maybe yes :/ edit: i did a clean installation again with DDU and its the same thing, cant set fans at msi afterburner. And at AMD software i only can set it at fan graphic by temperature, at fixed value % i cant, always stay at 0RPM. But now, i have another question, i set some values at AMD Software but my profiles keeps resetting everytime i reboot pc. Is there any other way to load the profile from the saved xml file besides loading via the menu button?

Ivan Obscura Valentine:

Am I the only one who actually have overheating problem since updating to 2020 edition of AMD drivers? I tried it more than 3 times now, each time I go back to older drivers it gets fixed, when I install any 2020 driver version overheating starts again, no clock changes and nothing strange, just overheating, fans are also working

What exact model of card you have? What temps you have when you run just simple graphic test like one that GPU-Z have by clicking [?] and then click on Sensors tab, and take a picture of temps.

Not bad I noticed that the gpu frequency don't fluctuate as wildly now.

joaoameixa88:

Humm i dont know.. maybe yes :/ edit: i did a clean installation again with DDU and its the same thing, cant set fans at msi afterburner. And at AMD software i only can set it at fan graphic by temperature, at fixed value % i cant, always stay at 0RPM. But now, i have another question, i set some values at AMD Software but my profiles keeps resetting everytime i reboot pc. Is there any other way to load the profile from the saved xml file besides loading via the menu button?

One of the reported side issues with how AMD altered the fan behavior with this driver, there's a reporting issue too for how some of the stats such as clock speeds are detected and listed though that's visual only but for the fan it does seem to run at a higher min speed at least for the reference models (20% instead of 10%) and it does wrest control over the fan behavior from third party utilities now so these are a bit limited currently. (For zero fan mode it seems overriding the fan control in Wattman either disables it or makes it work less reliably so it's often running at a lower speed instead of just being off entirely.) As to reboot and profile resetting that might be the old problem (Years.) that exists with fast boot being enabled in the power saving options using hibernation to store the systems state to RAM instead of fully unloading when you shut off. (It does unload on reboot though far as I know so if it's this then the issue lies elsewhere.) Wattman can be wonky to sleep mode and hibernation too though and might register it as a driver crash and reload the settings but the "!" notifications in the Radeon Settings software should state as much I believe whenever this occurs. EDIT: From that 20.2.2 topic on Reddit from before. https://www.reddit.com/r/Amd/comments/favtfv/radeon_software_adrenalin_2020_edition_2022/

Nice work, quite a huge fix list right here, well done guys Ironically, this added an issue for me... I was sitting on 20.1.4, everything was quite stable (except Battlefield V blackscreen issue, which I were solving by unplugging-plugging again DP cable). So this update breaks Zero RPM feature, like completely. This feature always worked for me on previous versions, but on this one my fans are always 30% in idle and it cannot be changed. Just to mention, 30% is the lowest I can change fan speed in Wattman. Before that I was setting like 10% fan speed paired with 50C temperature in Fan Tuning, and under 50C my card went to Zero RPM. PowerColor 5700 XT Red Devil.

And others. Should be posts there and in other topics also pointing to Afterburner not changing the fan behavior and the higher min speed although I see that's a thing here too with the Red Devil. AMD changed some parameters in 19.7.2 and I guess now there's a few more that are basically "This" and they're kinda locked and will be "This" because AMD says so well it's a change but eh it's a bit strict if it can't be changed at all and now the behavior forces more changes. If there's a larger compatibility conflict with Afterburner and other software or possibly even bios or soft modded values that is a issue too for the additional fan settings and how it changes but the only thing to do is to report it and see what AMD changes and eh yeah it's also how long that might take which could be a while. EDIT: As to my own testing the GPU clocks are indeed fluctuating less but unfortunately the stability testing didn't quite work, bit better though it was perhaps just random but DXVK is still very much a improvement to stability still for at least Ghost Recon Breakpoint. Next up trying it again with some tweakage in Wattman for lower clocks and then voltage tuning but I expect the results to be similar, it's a good improvement though overall for this driver but not quite perfect and some issues do still linger although feedback so far is quite positive but there are also remaining issues like this stability one, some FreeSync issues and the multi-display issue and then from what I can find also VR and specific problems for some of the earlier GPU models that are still there. After that well time to see how Atelier handles things, hoping it's stable but if it crashes it crashes and there's still something with D3D11 possibly - greatly - affected by game specific issues and usages that aren't quite standard for this and possibly other API's much as that's nothing new sadly ha ha. But that's not the state of the drivers it's the state of how some development practices are done and how much wrong can be in one title or a series of titles over several years in this case unfortunately and other games too yeah driver side fixes and workarounds aren't going anywhere. (And that's about as expected I suppose though some of the issues one wonders how that could happen at all.) Reading up on it the hardware acceleration crash issue seems improved on Chrome but that could be due to users not having updated from some of the more unstable 80.x builds of Chromium and then for Firefox I'm reading some crashes still though again you have the stable, beta and dev builds that could be seeing different results. For the beta 74 version it's been " " and silence from B1 to B9 now for what's actually changed and the beta page itself is pretty sparse on details too oddly enough though the faster turnout time has shrunk things a bit for what each new version brings. (Doesn't mean much of anything though as such.) And for now time to do some more reading and impressions on this driver, overall it seems to be a good improvement and Navi is getting there in terms of fixes and stability although it was always very much random what happened and in which games and even the downclock issues other than some extreme titles was also kinda all over for how far it flujctuated and dropped so it's good to see it tracked down and it is understandable though unfortunate it's taken this long. Bigger team and more budget is perhaps starting to show a bit now after getting the 2020 driver out but what do I know, I like the results even if there's a bit more and there's some side effect for some of the improvement for now at least. (Hopefully the next few drivers will solidify these positive results and the rest of the issues will be done with well in time that is but hopefully not too long but who knows eh.)

skoprowski:

Unfortunately, I take back what I said now. Got a Developer 6068 error and game locked. Ugh. I played a very long time before it happened though which it much better. It has to be a crappy coded game. I blame the game more than the GPU.

Did the system freeze, or just the game? Games can be the source of problems, sure... Had one changing my desktop wallpaper/theme -_-

Ivan Obscura Valentine:

Am I the only one who actually have overheating problem since updating to 2020 edition of AMD drivers ? i tried it more than 3 times now, each time i go back to older drivers it gets fixed, when i install any 2020 driver version overheating starts again, no clock changes and nothing strange, just overheating, fans are also working

I have overheatingproblems with the cpu after the adrenaline 2020 versions, never had that before, and are running with a sapphire R9 390.

patteSatan:

I have overheatingproblems with the cpu after the adrenaline 2020 versions, never had that before, and are running with a sapphire R9 390.

Affected the CPU? Those rascals at AMD!!! 🙂

DDU might have taken the chipset drivers if it's a AMD motherboard but that doesn't affect the CPU fan unless manually configured via perhaps Ryzen Master if that's capable of doing that, I just use the bios but then I also threw a Noctua on the CPU and set a higher curve to basically set it and forget it so that's solved, mostly. (Temps can still climb a bit up to the 70's and affect scaling somewhat in very intensive CPU scenarios but it's pretty uncommon.) Overheating would require somewhere around 80 - 90 if not more if we're talking about where the CPU starts really throttling depending on if it's AMD or Intel and the model and process it's on but full on overheating should be rare unless it somehow stops or doesn't spin up at all however the GPU drivers could affect that. Unless the case is a smaller form factor and the GPU is blasting hot air directly on the CPU but then mounting on the reference and most models puts the fan downwards towards the PSU if anything and out of the case short of some very restrictive airflow or very high ambient air temperature does it not? EDIT: Or it's just a slight typo and something got affected when AMD tweaked the fan behavior and testing was insufficient on early GPU models which could be a thing too. (I would expect the card to respect the bios defaults especially the thermal limits for when it ramps up to avoid hitting any other issues though.) EDIT: Well would and would hell anything could happen but I doubt very much that AMD kinda pushed aside the bios defaults and forcibly overrode behavior to that degree beyond some tuning to minimum values via software but you never really know what sort of issues can occur and pop up I suppose. EDIT: Though they did kinda upgrade (Not entirely problem free initially.) other GPU models up to OverDrive X or 6.0 or what it was so eh could be something affecting previous cards but then Polaris and Vega should be on 7.0 and Navi (And Radeon VII) on 8.0 sorta I'm not entirely certain as to the specific OverDrive numbering here. 🙂 (PowerPlay and that and all the revisions and versions plus changes to especially Navi moving from the previous set states and more freely scaling and working it as a sort of curve instead.) EDIT: And cursor issues and separate from using a high polling rate too. https://www.reddit.com/r/Amd/comments/ev9wml/5700xt_mouse_cursor_hardware_acceleration_is_one/ And also happens on Linux.

Interesting. I’m seeing this on the Linux drivers as well. I’m thinking that the pointer plane update is locking the pipeline and randomly causing the page flip request to be delayed past the vblank interval. Pointer updates should be completely asynchronous or lower priority. edit this is on a 5700 xt. The rx580 with same system doesn’t have this problem.

https://www.reddit.com/r/Amd/comments/favtfv/radeon_software_adrenalin_2020_edition_2022/fj1kx46/

patteSatan:

I have overheatingproblems with the cpu after the adrenaline 2020 versions, never had that before, and are running with a sapphire R9 390.

Your cpu overheating is a different issue entirely.

Reddit is happy...now im waiting for the people that they were saying ''im gonna sell my radeon gpu to buy nvidia'' to sell the nvidia and buy the radeon again 😀:p:D;):) - Well played by Radeon team.

LocoDiceGR:

Reddit is happy...now im waiting for the people that they were saying ''im gonna sell my radeon gpu to buy nvidia'' to sell the nvidia and buy the radeon again 😀:p:D;):) - Well played by Radeon team.

Many people bought 5700 and exchanged to 2070 after this fiasco. You saw HU poll and half amd users had some sort of issues. Thats a bad marketing but despite that amd outsold nvidia cards only becouse nvidia is too damn expensive.

Battlefield 5 doesn't crash anymore with DX12 but it still runs choppy on my Vega 56 (Future Frame Rendering disabled) [edit:] But that is only true in Fullscreen Exclusive Mode. If I set the game to Borderless the game appears to run smoother but still freezes after a couple of minutes of gameplay [I am on the current Windows 10 Insider Preview]. Freesync is on, Monitor is set to 144 Hz and the "Keep syncing with the Monitor" option in the game. Also, I've got Anti-Lag enabled but no other driver option.

another plus,, minimum game clock is now 800mhz ish example .. batman arkham city, 60fps vsync on old drivers would run about 4-500mhz at ~70% usage now its 800 ish and 30% usage I really have to say well done team red!

Upgraded over 20.2.1. So far so good.

Performance Metrics Overlay and Radeon WattMan incorrectly report higher than expected idle clock speeds on Radeon RX 5700 series graphics products. Performance and power consumption are not impacted by this incorrect reporting

So the now reported 800MHz GPU clock speed at idle is fake? In Wattman cannot go lower than 800MHz and 750mv.

Might be though apparently the GPU draws more power so might be pushing a bit higher though the Linux drivers also idles at 800 Mhz however they draw less power than the Windows drivers did so it might be possible to balance it further. Minimum clock state in Wattman for Navi GPU's should also have some effect now instead of just the minimum voltage curve, perhaps that is what is interfering and it drops to what the cap is but no lower than that? I don't think it's too problematic but there is a effect on power usage and a slight increase in temps which should confirm that the card is operating a bit higher than the usual 6 - 30 Mhz it was at before even if the sensors might be a bit inaccurate with the current drivers. 🙂 EDIT: Although sensibly same as the fan speed having user control over idle behavior and not just during load would be best so some options or toggles wouldn't hurt like disabling/enabling Zero Fan mode or setting the minimum clock and fan states to apply under idle load conditions too. Best of both and full control from the users side as I see it. Say P1 to P3 for low, medium and high GPU load and a P0 for idle sort-of though the fan curve already has some pins but that too could be improved unless the API and actual hardware really is that restrictive. Part of it is software though I'm sure as some of this worked for adjusting idle operating parameters in pre-Adrenaline 2020 drivers even with some of the bugs and quirks Navi GPU's had or Vega before that and the whole fan curve but actually a stepping which should also be overlooked at .... some point. EDIT: Full on power user mode would be nice too but adding custom states for specific GPU load percentages and all that might be beyond OverDrive version whatever and current PowerPlay functionality nice as having complete control over all the parameters and settings and how these operate would be. Even the ability to lock states as before though then Navi might be a bit tough with it's hardware being all scalable and dynamic instead of fixed so yeah it's easy to say it's probably a lot tougher for the actual code and implementation. Funny, overbuilt and cumbersome as Wattman actually is there's actually a number of options and modes that would be really useful but they're missing entirely and some options do some stuff on certain GPU models and other things entirely on others. (Well, it needs work or a complete overhaul perhaps or several over time improving and adding features and functionality within whatever the actual hardware supports.) EDIT: Eh it's easy to dream. Fixes first then extend functionality and features. 🙂

MaCk0y:

Upgraded over 20.2.1. So far so good. So the now reported 800MHz GPU clock speed at idle is fake? In Wattman cannot go lower than 800MHz and 750mv.

GPU-Z also reports the raised idle clock. So, maybe this was the only way to have things run properly? Power consumption seems ok, so...)

Passus:

another plus,, minimum game clock is now 800mhz ish example .. batman arkham city, 60fps vsync on old drivers would run about 4-500mhz at ~70% usage now its 800 ish and 30% usage I really have to say well done team red!

End results are very different?

connos:

Seems you can lock the frequency now with Radeon Settings. Well done AMD!!!!! It doesn't cause the card to get hot an it doesn't increase the wattage usage.

Like here: [spoiler=screen] https://i.imgur.com/WcGkqRB.jpg[/spoiler]

ms178:

Battlefield 5 doesn't crash anymore with DX12 but it still runs choppy on my Vega 56 (Future Frame Rendering disabled) [edit:] But that is only true in Fullscreen Exclusive Mode. If I set the game to Borderless the game appears to run smoother but still freezes after a couple of minutes of gameplay [I am on the current Windows 10 Insider Preview]. Freesync is on, Monitor is set to 144 Hz and the "Keep syncing with the Monitor" option in the game. Also, I've got Anti-Lag enabled but no other driver option.

BFV/BF1 really don't like any FPS limiter. No Chill, FRT or RTSS Make file user.cfg (in main directory). [spoiler=paste] Perfoverlay.drawfps 0 RenderDevice.Dx11Dot1Enable 1 EntityFrustumCull.Enable 1 RenderDevice.ForceRenderAheadLimit 3 GameTime.MaxVariableFps 142 WorldRender.MotionBlurEnable 0 [/spoiler] and report back in Vega thread. Note: Playing BFV every day (DX11 + Reshade) 😛 -> smooth as butter.

Hi everyone i own vega 56. when i activate Hbcc and any game exceeds 8 gb, the game i tested crashes. My tests are on Resident Evil 7, RE 2 Remake, and the demo of Middle earth shadow of war. Windows 10 operating system with all updates. Anyone with vega who can confirm me this huge bug?