I checked with the product team and their feedback is that depending on specific display configurations (resolution and refresh rate combinations) and background tasks, RX 5000 Series GPUs may maintain memory frequency to ensure an optimal user experience. This behavior is expected and does not impact the RX 5000 GPU in any way.
Seams to be a lot of issues with the 5700 series GPUs. Such a shame they really have promising performance vs Nvidia, but if you have to deal with a multitude of issues it makes the lower price not worth it. So far legitimate issues reported with these cards are.
1. Eventually runs so hot under load the GPU shuts off the computer.
2. Card shipped with bios corruption/bugs that prevent stats from reporting to the driver correctly or at all.
3. Memory runs far too hot damaging performance.
4. The cards are seriously memory speed limited so overclocking yields little to no improvement.
These issue are serious enough that they will not likely be fixed anytime soon. This underminds the reputation of Navi in the pc gaming community and bolsters RTX just like last generation with vega. Such a same.
Im still waiting on my replacement 5700XT 5AE that suffered from all the issues listed above.
So in your point 2, you mention bios corruption/bugs preventing the sensor data coming through.
How do you know this is bios corruption or a bug and not driver related?
Mainly because in my experience with GPUs I've seen this behavior before and it normally is due to bios corruption or a bad factory bios flash. Also, I uninstalled and reinstalled the latest driver several times using the DDU tool and it literally had no effect on that issue.
Have the same problem with my Sapphire Rx 5700.
Tried a few combinations:
144 hz @ 1080p or 1440p = MemClk 875
60, 120 hz @ 1440p = MemClk 100
50, 60, 120 hz @ 1080p =MemClk 100
Your instructions works perfectly. Hope AMD can/will fix this soon with driver update.
Facing the same issue here when using 3440x1440 resolution. Tried 60Hz, 100Hz, 118Hz, all results in the memory being stuck at 875. Lowering resolution does work, but that's not ideal. Hope AMD sorts this out asap.
Edit: this is on a 5700XT and Windows 10
Edit2: changed from DP to HDMI and now 3440x1440 is working at 100Hz refresh (max of monitor). Still would like to see this fixed for DP
Edit3: turning on HDR in Windows will also cause memory clock to be stuck at 875
Edit4: drivers version 19.7.5 has resolved the HDR issue. DP issue still persist
I have the same issue at 144hz memory does not down clock. Using freesync premium setting on my benq ex3203r freesync 2 monitor which reduces the monitor to 120hz and was working with an rx 580 is now locked at 60hz (ram down clocks) with the rx 5700, so there is also an issue with their freesync 2 support in the driver.
I just wanted to add to this: Memory clocks stays high at 875mhz on my 5700 xt on the 19.7.3 driver when running dual monitors (2560x1440@144 & 1920x1080@144) causing idle power to be higher than it needs to be, this is fixed when I run a single monitor and it drops down to 100mhz causing idle power to plummet aswell.
Interesting, does it downclock to 100 mhz with any single monitor configuration (1440p 144hz and 1080p 144hz) for you?
What type of connection do you use in a single monitor config for each? (Displayport 1.2/1.4 or hdmi 1.4 or 2.0+)?
In my case the problem is still here on 19.7.3 driver with LG 32gk650f (1440p 144hz) connected via displayport 1.2.
I don't have hdmi 2.1 cable to test (and 1.4 version can't provide enough bandwidth for 1440p 144hz) and i wouldn't use it even it worked properly since freesync range with any sort of hdmi connection becomes limited to 60-100hz accordinng to LG's manual while it is 48-144 with displayport.
And It doesn't look like the cable/monitor monitor issue since it works flawlessly on my second pc with vega 56
Ok so this spawned an interesting scenario: Only the 1440p Asus MG279Q(freesync on, DP1.2, mini and standard DP has the same results) monitor solo will drop power consumption, the 1080p Philips 242G5D(no freesync, DP1.2) monitor solo will have memory clocks stay high.
I used to have a vega 56 aswell and things worked fine there.