Look I'm not an expert, but I don't see how this is supposed to be normal. My "fix" involved setting the refresh rate on the Radeon Software custom resolution to 142 Hz. No more permanent 1750 MHz clock speeds, now idles around 200 MHz. What is the issue here exactly? Is this a monitor issue? Is this an issue with your drivers? I want to know if I'm not using my monitor to it's fullest abilities.
Also extremely disheartening to read further that this has been an issue since 2019.
Well sorry to pick this topic up again, Amdmatt. This is regarding the 20.11.2 drivers released today.
I run a RX5700 MSI Gaming X since December 2019 always using the lastest driver versions (also optional) and never had an issue with the VRAM on a 75 hz monitor. Until 20.11.1 the VRAM has clocked down to 200 mhz. After upgrading to 20.11.2 the VRAM does not clock down anymore on the very same 75 hz monitor from Iiyama (Black Hawk 2018) I use via Display Port 1.4 since I have bought the card - and the Idle power consupmtion suddenly goes up zu 35 watts and the card gets 9 degrees warmer. You simply cannot tell me that this is a "feature" and a wanted behavior. This is a bug - that I hat the luck not to encounter until today. So you guys need to look into whis again. You cannot tell me it is normal that after a year without issues and with correctly downclocking ram - this is not workind anymore comes a new driver release.
I stick with 20.11.1 for now. But you guys at AMD should look onto 20.11.2. It is buggy and tbh - there is no need that a 75hz display needs load memory clocks - expecially not if it was running perfectly with proper idle clocks for almost a year.
Maybe you are right talking about 144hz or 240 hz screens. But I run a 75 hz 1080p screen - and the card was clocking down the VRAM to 200 mhz for a year now....so there MUST be an issue with the 20.11.2 driver.
Well said miccellomann! This is a major issue if you ask me and is blowing up on many forums including reddit. 20.11.2 should NEVER have been put as a recommended driver over 20.11.1. All Drivers after 20.11.1 have this issue.
1. this is NOT A BUG - its actually a needed FEATURE!
2. very high refreshrates or dual (or tri) monitors will most-likely trigger the higher VRAM clocks...
3. read 1.
It is definetely a bug. I run a 75 hz Iiyama screen. From 19.12.1 driver till 20.11.1 the VRAM was clocking down to idle state in Desktop Mode. Starting with 20.11.2 the VRAM is in load state all the time without changing screens or setting. Since than a manual display stting via CRU is needed in order to let the card clock as intended (idle ram speed in Desktop Mode).
There is an issue the drivers have with the display timings - there seems to be a problem which prevents the driver fom correctly detecting the blanking lines of some screens with refresh rates above 60 hz. This IS a bug - NOT a feature. AMD is not honest with us here.
If you are capable of reading and understanding German, have a look at this. Here is a way to fix this issue with a workaround using the tool CRU:
[HowTo] VRAM taktet nicht runter - Lösung mittels CRU | ComputerBase Forum
AMD needs to aknowledge this issue and finally solve it.
Single monitor use with 1920x1200 60hz panel. It is not needed and is not triggered by high refresh rate monitors. If it was a needed feature which it may be for some it is implemented very badly as it should not be triggered by 1080p 60hz monitor. Dramatically increasing power tables by over 20% and thermals by a additional 20% is a very bad idea. This is basically a overclock and I doubt it is intentional. If it is I will not be updating my drivers ever again. I also find I’d suspect that this is a feature as amd themselves have not committed about it in anyway publicly. I’ve only heard it is from others and seen it on mine and others cards. I would think if it was a feature that dramatically changed power profiles of a series of cards that they would have included it in their release notes, but it has not been at all. If you are aware of any such announcement I for one would appreciate seeing it. I also know this was a bug on last years driver updates that was fixed in the past so it may be something that has returned like freesync breaking. Overall I would like a general response from AMD on weather it is a bug or a feature. As of right now I consider it a bug because 1. It is not announced. 2. It did not improve anything that I am aware of in anyway 3. Dramatically increased thermals and power levels.
with drivers 20.11.2 - 20.12.1 high values vram temp power. Shappire 5700 connected using DP monitor Dell S2721DGF . Test all settings, FreeSync on - off , hdmi connected , another monitor. https://youtu.be/CxQwSFV_R40
Drivers 20.11.1 no problem vram 60Hz ,120 Hz, 144Hz. " 165 Hz = high values vram. "
Drivers 20.11.2 - 20.12.1 no problem vram 120 Hz ,144 Hz. " 60 Hz , 165 Hz = high values vram. "
i have told why its a feature because of Industry Standard - but you troll around and therefore getting your posts deleted...