RX 5700 XT - 75 Hz/144 Hz/non-standard refresh rates causing VRAM clock to run at max

[Mussels]

I've had and continue to have, more driver crashes with the RX 5700 XT than any other card since I started using PCs. None of the latest drivers fix the mem idle issue and the driver crashes are persistent.
I've also reported the crashes to AMD using the built in tool, for what it's worth. Anyway, I just live with the crashes now, reboot the system and move on. And if I could afford to, I would certainly upgrade the card, either green or red.

It's semi unrelated, but having ran similar hardware to you on the nvidia side, make sure you're not using power extensions or PCI-E risers to the GPU and triple check your RAM stability (with four sticks try SoC voltage at 1.15v?). Instability from RAM can cause the PCI-E bus to reset, which for some causes USB dropouts and for others, the GPU driver crashes.


Back onto this older topic since it's still an issue, it's far more common now to see monitors going outside the standard bandwidths with "overclocked" modes built into their UI's
Throwing in some googled info on the pixel clock rates of various monitor connections:

1440p 165Hz runs at 640MHz, which causes the GPU's to clock up
144Hz is 559Hz
120Hz is a low 380Mhz

Using CRU to do the math for me, 154Hz is the max some GPU's can do before they'd clock up to compensate.

4K 68Hz fits in at 595Hz on the pixel clock, and as a shocking coincidence almost every 4K TV i've hooked up to a PC will overclock to 67Hz


TL;DR: If the pixel clock goes above what your monitor connection supports, some GPU's raise their clock speeds. I don't know why that is.

 

[Bomby569]

I've had and continue to have, more driver crashes with the RX 5700 XT than any other card since I started using PCs. None of the latest drivers fix the mem idle issue and the driver crashes are persistent.
I've also reported the crashes to AMD using the built in tool, for what it's worth. Anyway, I just live with the crashes now, reboot the system and move on. And if I could afford to, I would certainly upgrade the card, either green or red.

I also had a bad experience with that card (had almost since launch), like almost everyone that owned it. I fixed all my problems by selling it. That's a crazy good cryptominer card, just sell it and get a new one for the same money or even at a profit. I sold mine used and got a brand new 3060ti and even pocketed the difference (mind you i didn't even paid MRSP and still made a profit), and i got no more problems since.
It's a win (new card), win (extra money), win (no more shitty drivers card) situation. Crypto is were that card shines and belongs

 

[Valantar]

It's so weird how the 5700 XT continues to have so many problems that seem absent in not only the 6000-series, but other 5000-series cards.

About the VRAM clock speed thing though, sadly after a driver update a month or so ago this kicked in on my 6900 XT - it's now stuck at 2000MHz VRAM at all times, essentially doubling GPU power draw at idle. I've reported the bug to AMD (as this was not the case previously), just crossing my fingers that they can identify whatever they borked at that point.

 

[Bomby569]

It's so weird how the 5700 XT continues to have so many problems that seem absent in not only the 6000-series, but other 5000-series cards.

About the VRAM clock speed thing though, sadly after a driver update a month or so ago this kicked in on my 6900 XT - it's now stuck at 2000MHz VRAM at all times, essentially doubling GPU power draw at idle. I've reported the bug to AMD (as this was not the case previously), just crossing my fingers that they can identify whatever they borked at that point.

if it's the same problem as the 5700 and i think it is, just try and lower the refresh rate of the monitor in windows (example: if you have 144, do 120), that should "fix it"

I'm not suggestion this is a solve, just a confirmation of the drivers problem

 

[eidairaman1]

It's so weird how the 5700 XT continues to have so many problems that seem absent in not only the 6000-series, but other 5000-series cards.

About the VRAM clock speed thing though, sadly after a driver update a month or so ago this kicked in on my 6900 XT - it's now stuck at 2000MHz VRAM at all times, essentially doubling GPU power draw at idle. I've reported the bug to AMD (as this was not the case previously), just crossing my fingers that they can identify whatever they borked at that point.

Id be using enterprise drivers

 

[sam_86314]

My card has also always been stuck at max speed (1748-1750MHz) on the memory. Core clock stays at idle (10-100MHz)

Power usage is around 30-40w when idle.

Running at 3440x1440 100Hz.

 

[Lew Zealand]

if it's the same problem as the 5700 and i think it is, just try and lower the refresh rate of the monitor in windows (example: if you have 144, do 120), that should "fix it"

I'm not suggestion this is a solve, just a confirmation of the drivers problem

This is exactly what I do on my 5600XT. Switch from 144Hz down to 120Hz (1440p monitor) and VRAM clocks down with lowest power draw.

One thing I've noticed is after even a short 15+ minute gaming session, after exiting the game the VRAM will clock down properly no matter the monitor refresh rate. Like you'd expect. However sometime later, maybe after a monitor sleep or maybe even a PC sleep, the VRAM goes back to full speed unless I go to 120Hz.

I have a 6600XT now and yes, it is a very well behaved GPU with none of these peccadillos.

 

[Bomby569]

This is exactly what I do on my 5600XT. Switch from 144Hz down to 120Hz (1440p monitor) and VRAM clocks down with lowest power draw.

One thing I've noticed is after even a short 15+ minute gaming session, after exiting the game the VRAM will clock down properly no matter the monitor refresh rate. Like you'd expect. However sometime later, maybe after a monitor sleep or maybe even a PC sleep, the VRAM goes back to full speed unless I go to 120Hz.

I have a 6600XT now and yes, it is a very well behaved GPU with none of these peccadillos.

i solved it by selling my 5700xt, moved to team green no more problem. I know people dislike we trash talk AMD, but i suffered for 2 year with this, i repeat 2 YEARS, AMD drivers are shit. Cooking the VRAM and wasting energy because they can't bother to fix this. And AMD shills always answered, but this also happens in nvidia. Oh no it doesn't, i had a 1060 before and a 3060 now and never seen this.

 

[FordGT90Concept]

NVIDIA cards do it too but AMD has two profiles for VRAM where NVIDIA has three.

The reason for this behavior is because of vblank timing. Some information on vblank here:

Using The V Blank For Timing - How To Program - Maxim’s World of Stuff

If I run my primary monitor at 120 Hz instead of 144 Hz, it drops to the lower VRAM profile.

 

[sam_86314]

Going down to 2560x1080 60Hz made my VRAM downclock. 3440x1440 60Hz did not.

Also, my computer doesn't seem to like the 99Hz profile I made and won't enable it.

Considering trying enterprise drivers, but I like the application-specific GPU profiles.

Though to be perfectly honest, I don't think this problem is a big deal.

EDIT: I use GPU scaling and custom resolutions don't like that I guess.

After turning that off, 3440x1440 99Hz and CVT Reduced Blanking did the trick. Everything is running a bit cooler now.

EDIT 2: Just tried 100Hz with CVT Reduced Blanking, and that works too. I noticed that the bit depth is 6-bit now, though I'm not noticing any banding so it's probably fine.

 

[Valantar]

i solved it by selling my 5700xt, moved to team green no more problem. I know people dislike we trash talk AMD, but i suffered for 2 year with this, i repeat 2 YEARS, AMD drivers are shit. Cooking the VRAM and wasting energy because they can't bother to fix this. And AMD shills always answered, but this also happens in nvidia. Oh no it doesn't, i had a 1060 before and a 3060 now and never seen this.

It's 99% likely not just a driver issue, but some sort of hardware or driver-hardware interaction issue, most aptly illustrated by no other piece of AMD GPU hardware having similar issues, even on the same architecture - 5600XT, 5500XT, even the 5700 (which is hard to understand, really). If it was just a driver issue, it would have been fixed by now. So, while I completely understand your frustration, saying "AMD drivers are shit" is just bloviating and factually untrue. The 5700XT has issues, and AMD just as Nvidia has various driver issues, some persistent, others intermittent, others one-and-done. That's how GPU drivers are, and there is no major difference between the two vendors (though one might argue that given Nvidia's ~4x install base it's impressive that they don't have more issues than AMD given the more diverse hardware; a point that is obviously counteracted by their driver development funding advantage).

Id be using enterprise drivers

Nah, I don't have a use for the features those deliver, and want the game optimizations of the consumer ones. Ultimately this is a minor annoyance - it doesn't affect noise levels, my electricity is 100% renewable, and my water loop doesn't care about 20 extra watts at idle, so ... yeah. I'd like to see it fixed, but it's not a big deal to me.

if it's the same problem as the 5700 and i think it is, just try and lower the refresh rate of the monitor in windows (example: if you have 144, do 120), that should "fix it"

I'm not suggestion this is a solve, just a confirmation of the drivers problem

I have two monitors, one 1440p60 and one 1080p75 - setting the 1080p monitor to 60Hz changed nothing; disabling it brought a 5-10W drop in power consumption but VRAM stayed at 2GHz; disabling it and disabling my Aquasuite monitoring desktop overlay finally brought me down to idle clocks. Both monitors active with Aquasuite closed still sticks to 2GHz. Still, it seems like my Aquasuite setup puts a sufficient load on the GPU to maintain full VRAM speed no matter what (Task Manager reads it as a ~5% 3D load, though that's with the GPU reporting clocks between 0-250MHz). Kind of understandable given that it shows a ton of graphs, though I would have expected that to be all 2D tbh. So this is at least partly my fault - but it should really manage to drop to idle VRAM clocks when I close the overlay even with both monitors active.

 

[Bomby569]

It's 99% likely not just a driver issue, but some sort of hardware or driver-hardware interaction issue, most aptly illustrated by no other piece of AMD GPU hardware having similar issues, even on the same architecture - 5600XT, 5500XT, even the 5700 (which is hard to understand, really). If it was just a driver issue, it would have been fixed by now. So, while I completely understand your frustration, saying "AMD drivers are shit" is just bloviating and factually untrue. The 5700XT has issues, and AMD just as Nvidia has various driver issues, some persistent, others intermittent, others one-and-done. That's how GPU drivers are, and there is no major difference between the two vendors (though one might argue that given Nvidia's ~4x install base it's impressive that they don't have more issues than AMD given the more diverse hardware; a point that is obviously counteracted by their driver development funding advantage).


Nah, I don't have a use for the features those deliver, and want the game optimizations of the consumer ones. Ultimately this is a minor annoyance - it doesn't affect noise levels, my electricity is 100% renewable, and my water loop doesn't care about 20 extra watts at idle, so ... yeah. I'd like to see it fixed, but it's not a big deal to me.

I have two monitors, one 1440p60 and one 1080p75 - setting the 1080p monitor to 60Hz changed nothing; disabling it brought a 5-10W drop in power consumption but VRAM stayed at 2GHz; disabling it and disabling my Aquasuite monitoring desktop overlay finally brought me down to idle clocks. Both monitors active with Aquasuite closed still sticks to 2GHz. Still, it seems like my Aquasuite setup puts a sufficient load on the GPU to maintain full VRAM speed no matter what (Task Manager reads it as a ~5% 3D load, though that's with the GPU reporting clocks between 0-250MHz). Kind of understandable given that it shows a ton of graphs, though I would have expected that to be all 2D tbh. So this is at least partly my fault - but it should really manage to drop to idle VRAM clocks when I close the overlay even with both monitors active.

you changed the refresh rate in windows and it didn't drop? i find that hard to believe because that worked for everyone, trust me i know, struggled with it ages ago on AMD forums. Everyone reported same issue. This is 100% software, it has nothing to do with the hardware, the problem has been extensively detailed on this 4 pages.

And the claims that it also happens in Nvidia by my experience are simply not true.

 

[Naki]

I know my AMD cards are all fairly old, but I must say I have had no AMD Radeon drivers issues for many years now, and am very happy with their drivers.
Some annoying issues used to happen sometimes but was for a very short time, and a very long time ago.
In latest 3-4+ years, it mostly works just fine and as I want it to.

Cards used here on my 3 PCs are -- AMD Radeon R9 290 4 GB, R9 390 8 GB, RX 480 8 GB.
Before those, I had a Radeon R7 260X too, which had some bad, random black screen issues but I don't think that was only drivers-related.

EDIT: I have had my fair share of nVidias over the years, notably GeForce 2 MX, GeForce 4.
But after those I mostly use AMD cards -- I still remember my Radeon HD4870 1GB, was a beast of a card.

 

[Valantar]

you changed the refresh rate in windows and it didn't drop? i find that hard to believe because that worked for everyone, trust me i know, struggled with it ages ago on AMD forums. Everyone reported same issue. This is 100% software, it has nothing to do with the hardware, the problem has been extensively detailed on this 4 pages.

Please re-read my post. I never said this had anything to do with anything but hardware. You're confusing me arguing two entirely different and unrelated points here. The 5700XT being flawed and this high VRAM clock issue are unrelated, as this issue has existed long before it (at least since Polaris) and, as we can see, after.

As for my situation:

I also tried setting the U2711 to 8-bit rather than 10-bit color, but that didn't affect anything, so it seem's this is where I'm at.

And the claims that it also happens in Nvidia by my experience are simply not true.

Try googling "Nvidia black screen bug", for example. Incidentally, the number of hits for that and "AMD black screen bug" are nearly the same - a good thing for Nvidia with a ~4x larger install base, but still notable. And of course there are many other kinds of issues that have cropped up over the years. Since AMD started their push for improved drivers in ~2015 (IIRC), the amount of persistent and long-term bugs across both manufacturers has been about equal, except for the 5700 XT being a significant outlier (which, as said above, along with the specific nature of the issues indicates that it's not purely a software issue). AMD does have a reputation for poor drivers, but that's mostly a holdover from the bad old days when they neither had the budget nor the expertise to develop great drivers (though even then the reputation was largely overblown, as online reputations tend to be).

So, has AMD had more driver issues? In the distant past (10+ years) arguably yes, and currently yes if including the outlier 5700 XT, but in general in the recent past? Not really. They entirely deserve to be called out for however they screwed up the 5700 XT - that GPU has issues, and to a level that isn't acceptable for a consumer product - but that doesn't equate to "AMD drivers are shit", like you put it. That's a broad and general statement that needs a more solid factual basis than "I owned one GPU that's known to be bad and they didn't manage to fix it in two years".

 

[skizzo]

perfectly happy RX 5700 XT user here. YMMV as they say!

Got mine within 2 weeks of launch. Game crashes were common within first month or two. Then it has been smooth since. The only game I can say that gives me any regularity of crashes is Assassins Creed Valhalla.....which would suggest the problem is with that game. It's the game that crashes, I don't get driver timeout errors or AMD related pop-ups.

I use 4K 120Hz desktop and it is the 120Hz selection that makes it run mem clock at max...mine is usually going at 1742 - 1750Mhz. Drop refresh rate down to 60Hz and mem clock goes to idle speeds. That or I could go to a lower res than 4K. I don't quite get the gripes, if you don't want the mem clock to run that fast then choose lower settings, right? you cannot have your cake (low clock speeds) and eat it too (using high res and refresh rate). Also before someone says RX 5700 XT cannot do 4K 120Hz, it's a 4:2:0 signal to achieve that.

 

[Splinterdog]

perfectly happy RX 5700 XT user here. YMMV as they say!

Got mine within 2 weeks of launch. Game crashes were common within first month or two. Then it has been smooth since. The only game I can say that gives me any regularity of crashes is Assassins Creed Valhalla.....which would suggest the problem is with that game. It's the game that crashes, I don't get driver timeout errors or AMD related pop-ups.

I use 4K 120Hz desktop and it is the 120Hz selection that makes it run mem clock at max...mine is usually going at 1742 - 1750Mhz. Drop refresh rate down to 60Hz and mem clock goes to idle speeds. That or I could go to a lower res than 4K. I don't quite get the gripes, if you don't want the mem clock to run that fast then choose lower settings, right? you cannot have your cake (low clock speeds) and eat it too (using high res and refresh rate). Also before someone says RX 5700 XT cannot do 4K 120Hz, it's a 4:2:0 signal to achieve that.

I don't agree about the cake, sorry. I bought a 1440p 144Hz monitor to run off an RX 5700 XT and I want to eat my cake, thank you.
Bizarre statement.

 

[Bomby569]

Please re-read my post. I never said this had anything to do with anything but hardware. You're confusing me arguing two entirely different and unrelated points here. The 5700XT being flawed and this high VRAM clock issue are unrelated, as this issue has existed long before it (at least since Polaris) and, as we can see, after.

As for my situation:

I also tried setting the U2711 to 8-bit rather than 10-bit color, but that didn't affect anything, so it seem's this is where I'm at.

Try googling "Nvidia black screen bug", for example. Incidentally, the number of hits for that and "AMD black screen bug" are nearly the same - a good thing for Nvidia with a ~4x larger install base, but still notable. And of course there are many other kinds of issues that have cropped up over the years. Since AMD started their push for improved drivers in ~2015 (IIRC), the amount of persistent and long-term bugs across both manufacturers has been about equal, except for the 5700 XT being a significant outlier (which, as said above, along with the specific nature of the issues indicates that it's not purely a software issue). AMD does have a reputation for poor drivers, but that's mostly a holdover from the bad old days when they neither had the budget nor the expertise to develop great drivers (though even then the reputation was largely overblown, as online reputations tend to be).

So, has AMD had more driver issues? In the distant past (10+ years) arguably yes, and currently yes if including the outlier 5700 XT, but in general in the recent past? Not really. They entirely deserve to be called out for however they screwed up the 5700 XT - that GPU has issues, and to a level that isn't acceptable for a consumer product - but that doesn't equate to "AMD drivers are shit", like you put it. That's a broad and general statement that needs a more solid factual basis than "I owned one GPU that's known to be bad and they didn't manage to fix it in two years".

your monitors are 60 and 75 right, change that to the lowest, like 30 or whatever it supports.

perfectly happy RX 5700 XT user here. YMMV as they say!

Got mine within 2 weeks of launch. Game crashes were common within first month or two. Then it has been smooth since. The only game I can say that gives me any regularity of crashes is Assassins Creed Valhalla.....which would suggest the problem is with that game. It's the game that crashes, I don't get driver timeout errors or AMD related pop-ups.

I use 4K 120Hz desktop and it is the 120Hz selection that makes it run mem clock at max...mine is usually going at 1742 - 1750Mhz. Drop refresh rate down to 60Hz and mem clock goes to idle speeds. That or I could go to a lower res than 4K. I don't quite get the gripes, if you don't want the mem clock to run that fast then choose lower settings, right? you cannot have your cake (low clock speeds) and eat it too (using high res and refresh rate). Also before someone says RX 5700 XT cannot do 4K 120Hz, it's a 4:2:0 signal to achieve that.

i have a 3060ti, run at 144hz native resolution for the monitor and the mem clock works just fine, i don't have to drop it for the vram clock speed to behave normaly and drop, that's absolute BS

 

[skizzo]

It's semi unrelated, but having ran similar hardware to you on the nvidia side, make sure you're not using power extensions or PCI-E risers to the GPU and triple check your RAM stability (with four sticks try SoC voltage at 1.15v?). Instability from RAM can cause the PCI-E bus to reset, which for some causes USB dropouts and for others, the GPU driver crashes.


Back onto this older topic since it's still an issue, it's far more common now to see monitors going outside the standard bandwidths with "overclocked" modes built into their UI's
Throwing in some googled info on the pixel clock rates of various monitor connections:

View attachment 234383

1440p 165Hz runs at 640MHz, which causes the GPU's to clock up
144Hz is 559Hz
120Hz is a low 380Mhz

Using CRU to do the math for me, 154Hz is the max some GPU's can do before they'd clock up to compensate.

4K 68Hz fits in at 595Hz on the pixel clock, and as a shocking coincidence almost every 4K TV i've hooked up to a PC will overclock to 67Hz


TL;DR: If the pixel clock goes above what your monitor connection supports, some GPU's raise their clock speeds. I don't know why that is.

I would think this post supports what I just said. It's not like I'm making shit up to stir your GPU pots up..... What I shared is my genuine real world experience

4K 120Hz is above the 600Mhz value so clocks up mem speed
4K 60Hz is below the 600Mhz value, so does NOT clock up mem speed

The dots connect to me...what am I missing?

@Bomby569 you didn't share your "native res"?
According to the quoted post...."144Hz is 559Hz" (I'm assuming this value is considering a 1440p res based on how it is written). With that said, this would mean that a 1440p or lower res with a 144Hz or lower refresh rate wouldn't push the GPU to clock up mem speed which aligns exactly with what your stating....this isn't a surprise to me....the dots still connect (also assuming you're using a 1440p res setting until you share otherwise)

The post by @Mussels aligns with my personal experience. You cannot call that "bizarre" nor "BS"....perhaps coincidence but c'mon as far as I can tell what they wrote is accurate. I also take note Mussels wrote "some GPUs raise their clock speeds" which I take away as this may not be how every GPU operates. In my experience in recent years, last 4 or 5, which involved a RX 580 and RX 5700 XT this is exactly what happened with me. YMMV apparently. A 3060ti may be an apple to my orange of a RX 5700 XT making this comparison pointless

I don't agree about the cake, sorry. I bought a 1440p 144Hz monitor to run off an RX 5700 XT and I want to eat my cake, thank you.
Bizarre statement.

hmm but yours still clocks up mem at 1440p at 144Hz? that does NOT align with the post from Mussels....?! I don't have a 144Hz display to test anything there myself. Any chance you use more than one display? I mean, you both cannot be right, (or can you?) so now I don't know what to think.

 

[Bomby569]

@Bomby569 you didn't share your "native res"?
According to the quoted post...."144Hz is 559Hz" (I'm assuming this value is considering a 1440p res based on how it is written). With that said, this would mean that a 1440p or lower res with a 144Hz or lower refresh rate wouldn't push the GPU to clock up mem speed which aligns exactly with what your stating....this isn't a surprise to me....the dots still connect (also assuming you're using a 1440p res setting until you share otherwise)

The monitor is the same, with the RX5700 vram clock was always at 100% (unless i turned it down to 120hz for example), with the 3060ti they're not. Only thing that changed was the gpu. It really doesn't even matter what the resolution of my monitor is.

 

[Valantar]

your monitors are 60 and 75 right, change that to the lowest, like 30 or whatever it supports.

Yeah, no thanks. Regardless of whether or not that brings down memory clocks, that's no solution to anything - even desktop usage is unacceptable at 30Hz. Try scrolling through a web page or text document before telling me otherwise. (And yes, quite few games play decently at 30fps, but that's quite a different use case.) As I said, I'm more concerned with AMD fixing this bug than with the actual power consumption in my specific case.

 

[Naki]

AMD drivers have a Report issue tool, did you report this?

 

[Splinterdog]

AMD drivers have a Report issue tool, did you report this?

Dozens of times, not to mention driver crashes reported nearly every day. No dice from AMD, at least not directly back to me anyway.

I would think this post supports what I just said. It's not like I'm making shit up to stir your GPU pots up..... What I shared is my genuine real world experience

4K 120Hz is above the 600Mhz value so clocks up mem speed
4K 60Hz is below the 600Mhz value, so does NOT clock up mem speed

The dots connect to me...what am I missing?

@Bomby569 you didn't share your "native res"?
According to the quoted post...."144Hz is 559Hz" (I'm assuming this value is considering a 1440p res based on how it is written). With that said, this would mean that a 1440p or lower res with a 144Hz or lower refresh rate wouldn't push the GPU to clock up mem speed which aligns exactly with what your stating....this isn't a surprise to me....the dots still connect (also assuming you're using a 1440p res setting until you share otherwise)

The post by @Mussels aligns with my personal experience. You cannot call that "bizarre" nor "BS"....perhaps coincidence but c'mon as far as I can tell what they wrote is accurate. I also take note Mussels wrote "some GPUs raise their clock speeds" which I take away as this may not be how every GPU operates. In my experience in recent years, last 4 or 5, which involved a RX 580 and RX 5700 XT this is exactly what happened with me. YMMV apparently. A 3060ti may be an apple to my orange of a RX 5700 XT making this comparison pointless


hmm but yours still clocks up mem at 1440p at 144Hz? that does NOT align with the post from Mussels....?! I don't have a 144Hz display to test anything there myself. Any chance you use more than one display? I mean, you both cannot be right, (or can you?) so now I don't know what to think.

Only one display on my wonderful LG 32" 144Hz. I don't expect the issue to shorten my life, but it is irritating.

 

[sam_86314]

I also tried setting the U2711 to 8-bit rather than 10-bit color, but that didn't affect anything, so it seem's this is where I'm at.

In my case, it got lowered to 6-bit (262,144 colors). Since I don't do color-critical work, so far this has been a non-issue. Blu-ray quality video still looks fine, so I guess dithering is much more effective than I thought.

 

[Splinterdog]

Changing from Display Port cable to HDMI brought the VRAM speed down to 200Mhz with no other tweaking. Scratches head...
Although I'll have to check that the HDMI cables delivers 144Hz in gaming. (not an expert on cables)

 

[Bomby569]

Yeah, no thanks. Regardless of whether or not that brings down memory clocks, that's no solution to anything - even desktop usage is unacceptable at 30Hz. Try scrolling through a web page or text document before telling me otherwise. (And yes, quite few games play decently at 30fps, but that's quite a different use case.) As I said, I'm more concerned with AMD fixing this bug than with the actual power consumption in my specific case.

if you go to the top, i specifically said it ISN'T A FIX, it's a way to know that it's an AMD driver problem and the same problem that plagued the 5700 for years and never was solved.

You have to wait for AMD to fix it, good luck with that, apparently people with 5700 are still waiting.

But there is a fix, i had found it on reddit, i'm sorry but i can't find now, it was something about changing the monitor range in some tool, maybe someone can remember. It's not a fix, it's a workaround, but it solves the problem.
If i find that post i post it here.