AMD has finally fixed the vRAM running at high speed/3d clocks with high refresh rate monitors

[DoLlyBirD]

Clickbait title or no? for me not at all, I am thrilled with what I have just found out tonight......

After years and probably thousands of user reports by AMD GPU owners, AMD have finally fixed the vRAM running at high speed/3d clocks with high refresh rate monitors.

I am for the 1st time since owning my 165hz monitor able to just go to display settings in Windows and run it at 165hz and the vRAM doesn't automatically jump up to full speed when browsing or doing anything light/not gaming on the computer.

Right now, 6w usage with Opera browser open and 165hz refresh rate, previously I had to run 100hz top stop the vram from running full 3d clocks which in turn, increased the power draw from around 7w to 25-30w, increased heat output affecting the zero-fan feature. No more CRU custom profiles, running my monitor at a lower refresh rate or switching refresh rates when gaming/not gaming.

Hallelujah praise the lord it has only taken them a few years to work out , I'm using the latest 22.5.2 drivers for anyone interested.

 

[caroline!]

Wish they'd fix the horrendous driver control panel performance, constantly crashing, taking ages to switch from one tab to another, corrupting saved profiles for no reason... the cards are good but the software, man. Thankfully someone was bright enough to add an option to install just the drivers and skip all the bloatware.

 

[DoLlyBirD]

Wish they'd fix the horrendous driver control panel performance, constantly crashing, taking ages to switch from one tab to another, corrupting saved profiles for no reason... the cards are good but the software, man. Thankfully someone was bright enough to add an option to install just the drivers and skip all the bloatware.

Not experienced that myself, I have been using AMD GPU's for years as I know their cards and software, always work for me albeit you do have the odd issue like I mentioned above with the 3D clocks kicking in at anything above 75/100hz

It's like anything, 1 bad review will likely = 100 other users who don't have that issue, but you're more likely to leave feedback if you have a negative experience?

 

[AusWolf]

Wish they'd fix the horrendous driver control panel performance, constantly crashing, taking ages to switch from one tab to another, corrupting saved profiles for no reason... the cards are good but the software, man. Thankfully someone was bright enough to add an option to install just the drivers and skip all the bloatware.

I personally have no issue with the control panel, but the driver itself... *sigh*

It would all be nice if everything worked all the time, but there's always something to tarnish the otherwise great experience of owning an AMD card. I had a 5700 XT that I sold about a year ago because it kept crashing with "the driver didn't respond and reset itself" messages that were quite common on the 5700 series, unfortunately. Now I have a 6500 XT which, despite all the hate it gets, is not a bad card. It plays the games that I want at decent framerates, and is super silent... it's just that the driver sometimes decides that it should be even more silent by not turning the fan on when I'm on an OC profile. It was freaky as hell when the card nearly overheated after 5 minutes of ME: Andromeda the other day with fans at 0 rpm... on an unmodified fan profile!

AMD software engineers should focus on making things just simply work instead of overcomplicating unnecessary things.

 

[DoLlyBirD]

AMD software engineers should focus on making things just simply work work instead of overcomplicating unnecessary things.

I mean that's kind of implying that Nvidia cards/software don't have just as many issues, it's not the case, and again it's not a common issue afaik, as with all things computers it could well be just "one of those things" with your particular setup/software environment/hardware etc for the most part there is little to differentiate between both AMD and Nvidia, maybe price/perf in favour of AMD and slightly more issues, though not enough to warrant picking one over the other as being better or worse IMO

 

[AusWolf]

I mean that's kind of implying that Nvidia cards/software don't have just as many issues, it's not the case, and again it's not a common issue afaik, as with all things computers it could well be just "one of those things" with your particular setup/software environment/hardware etc for the most part there is little to differentiate between both AMD and Nvidia, maybe price/perf in favour of AMD and slightly more issues, though not enough to warrant picking one over the other as being better or worse IMO

Well, I've never had any driver-related issue with GeForce cards, but with AMD, there's always something small. They're not dealbreaker issues that would make me regret buying an AMD card, but they're there.

To make things fair, on nvidia's side, my complaint would be the extremely outdated and restrictive user interface. I mean, why do we still need third-party software to over-/underclock Nvidia cards? And why does the UI look like it's made for Windows 95? I get the "if it's not broken, don't fix it" approach, but c'mon...

 

[sam_86314]

From what I can tell, I still need to set the timing to CVT RB for the memory on my new 6800 XT and my old 5700 XT to downclock correctly.

While I haven't sat down and tested my 5700 XT recently, I do recall my 6800 XT running at full speed in 22.5.2 before changing stuff in CRU. As of writing this, and with the CRU changes applied, the memory is running at 192MHz.

 

[caroline!]

I personally have no issue with the control panel, but the driver itself... *sigh*

It would all be nice if everything worked all the time, but there's always something to tarnish the otherwise great experience of owning an AMD card. I had a 5700 XT that I sold about a year ago because it kept crashing with "the driver didn't respond and reset itself" messages that were quite common on the 5700 series

5700XT user here and I had the same error, however I found a solution to it in an unlikely place... a very old version of Everest monitoring software which I recalled had a fix for that. Upon starting a GPU stress test for the first time it prompts you to "apply a fix to increase the drivers freeze hold time" -or something in the lines of that- and if you dismiss it without reading what it is it'll never come back again, even if you uninstall and then reinstall Everest it won't prompt you again to apply this fix, it's really weird and I don't remember seeing it again in newer versions or in AIDA. It was a life (or card) saver and thankfully remembered that before going online and asking for help. You truly never know when an old dusty CD is holding the secret to resurrect your PC again ^^

Not experienced that myself, I have been using AMD GPU's for years as I know their cards and software, always work for me albeit you do have the odd issue like I mentioned above with the 3D clocks kicking in at anything above 75/100hz

It's like anything, 1 bad review will likely = 100 other users who don't have that issue, but you're more likely to leave feedback if you have a negative experience?

85Hz here and everything works correctly, perhaps the issue is native to newer cards, idk really. It just works but I wish I could make use of the control panel without it being more unstable than XP64 trying to run a game.

To make things fair, on nvidia's side, my complaint would be the extremely outdated and restrictive user interface. I mean, why do we still need third-party software to over-/underclock Nvidia cards? And why does the UI look like it's made for Windows 95? I get the "if it's not broken, don't fix it" approach, but c'mon...

Unironically that's why it's so stable. The old Catalyst drivers for AMD were as stable as nvidia's, but everything started going downhill when they replaced the UI with Crimson and the spaghetti code started piling up just to justify "muh better visuals are better" without caring for stability. Technically it was perfectly possible to add all of the options Crimson and the new drivers have to the previous Catalyst interface, but NO they had to ruin it.

 

[eidairaman1]

Wish they'd fix the horrendous driver control panel performance, constantly crashing, taking ages to switch from one tab to another, corrupting saved profiles for no reason... the cards are good but the software, man. Thankfully someone was bright enough to add an option to install just the drivers and skip all the bloatware.

Report it every driver release till it's fixed. They can't fix it till they hear about it.

 

[AsRock]

Wish they'd fix the horrendous driver control panel performance, constantly crashing, taking ages to switch from one tab to another, corrupting saved profiles for no reason... the cards are good but the software, man. Thankfully someone was bright enough to add an option to install just the drivers and skip all the bloatware.

They should of fixed all that shit before terminating a lot of other cards. A lot of the shit you can disable well in the older drivers at least.

They ever fix the DP to HDMI issue ?.

 

[nguyen]

it's just that the driver sometimes decides that it should be even more silent by not turning the fan on when I'm on an OC profile. It was freaky as hell when the card nearly overheated after 5 minutes of ME: Andromeda the other day with fans at 0 rpm... on an unmodified fan profile!

That was how my old R9 290 died, AMD driver decided to lock the fan speed to 20% and after maybe a month the card was dead, the VRM or VRAM probably cooked itself to death.

 

[eidairaman1]

Whats funny is the driver only option has been there since the ATi days

 

[AusWolf]

That was how my old R9 290 died, AMD driver decided to lock the fan speed to 20% and after maybe a month the card was dead, the VRM or VRAM probably cooked itself to death.

I can overlook lots of things, but the card cooking itself because the driver F*s up is unacceptable. I'm not even sure if the warranty covers such cases (probably not).

I'm glad I have GPU-Z and the Task Manager constantly running on a 7" touchscreen right beside my main monitor. My 6500 XT would have probably met the same fate as your 290 otherwise.

 

[Toothless]

They should of fixed all that shit before terminating a lot of other cards. A lot of the shit you can disable well in the older drivers at least.

They ever fix the DP to HDMI issue ?.

I'm using two DisplayPort to HDMI/DVI adapters, no issues.

Like Eidairaman said, report til it's fixed.

 

[wolf]

Well, I've never had any driver-related issue with GeForce cards, but with AMD, there's always something small. They're not dealbreaker issues that would make me regret buying an AMD card, but they're there.

My last AMD/ATi card was a 5870 + 5080 in CF, had some gripes back then but from what I gather they've come a hec of a long way. I think future purchases wouldn't really factor in drivers/control panel experience for me, more just the cards specs/perf etc and feature stack.

To make things fair, on nvidia's side, my complaint would be the extremely outdated and restrictive user interface. I mean, why do we still need third-party software to over-/underclock Nvidia cards? And why does the UI look like it's made for Windows 95? I get the "if it's not broken, don't fix it" approach, but c'mon...

No issues for years here either, and while the interface is old, it doesn't bother me in the slightest, it works, I know where everything is, and I spend very little time actually using it, maybe a few minutes per month? Maybe the overclocking this is more of a "we take no responsibility, so use a 3rd party app"? who knows, but I like MSI AB, I'd use it anyway for the tie in with Rivatuner SS and on screen display which I seemingly can't live without - so even with a Radeon I'd use AB + RTSS

 

[eidairaman1]

I can overlook lots of things, but the card cooking itself because the driver F*s up is unacceptable. I'm not even sure if the warranty covers such cases (probably not).

I'm glad I have GPU-Z and the Task Manager constantly running on a 7" touchscreen right beside my main monitor. My 6500 XT would have probably met the same fate as your 290 otherwise.

I remember detonators killing nv cards.

My 290 is fine to this day

 

[AsRock]

I'm using two DisplayPort to HDMI/DVI adapters, no issues.

Like Eidairaman said, report til it's fixed.

Good, still a shame they never fixed it in the older drivers even more so with all the "shortages" going on.

I get stuck st 30Hz unless a drop back about 6 month from when the put the last bunch of cards in legacy, and pointless reporting it any more.

 

[R0H1T]

it's really weird and I don't remember seeing it again in newer versions or in AIDA

It's there in AIDA as well, the fix is Windows video driver Timeout Detection and Recovery delay (TdrDelay).

Bookmark this for any future reference ~

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\GraphicsDrivers

 

[eidairaman1]

Good, still a shame they never fixed it in the older drivers even more so with all the "shortages" going on.

I get stuck st 30Hz unless a drop back about 6 month from when the put the last bunch of cards in legacy, and pointless reporting it any more.

Erm i did a report for 5 months straight, they do get fixed.

 

[AsRock]

Erm i did a report for 5 months straight, they do get fixed.

Well i cannot get 60Hz going though DP to HDMI 4k unless i use drivers way before they ended support for the 390X, as much as i found is that any thing newer than around this time 19.8.1-Aug20 will only give a max of 30Hz.

 

[eidairaman1]

@Hellfire

 

[Toothless]

Good, still a shame they never fixed it in the older drivers even more so with all the "shortages" going on.

I get stuck st 30Hz unless a drop back about 6 month from when the put the last bunch of cards in legacy, and pointless reporting it any more.

What's funny is I can use the mini displayport to full displayport to HDMI on my other, older cards like the HD7950 and R9280, and be fine.

 

[ARF]

If true, this is really a great news. The issue has plagued the Radeon products for a decade or more...

 

[FordGT90Concept]

Report it every driver release till it's fixed. They can't fix it till they hear about it.

It's not something that can really be fixed because of vBlank timings. The only thing they can do is add another VRAM clock stage like NVIDIA does where, for example, it would try 500 MHz before jumping to 2000 MHz. This is a hardware thing, so obviously the earliest that could happen is RDNA3.

AMD did try to eliminate the high clock when there's only one monitor connected. It is more likely to happen when there are two or more monitors connected. In my case, 144 Hz on the 4K causes 2000 MHz clock; 120 Hz on 4K drops to 0 MHz. I run 120 Hz in the summer and 144 Hz in the winter.

Well i cannot get 60Hz going though DP to HDMI 4k unless i use drivers way before they ended support for the 390X, as much as i found is that any thing newer than around this time 19.8.1-Aug20 will only give a max of 30Hz.

That's a bug. Not sure if it has been fixed or not.

 

[Splinterdog]

Clickbait title or no? for me not at all, I am thrilled with what I have just found out tonight......

After years and probably thousands of user reports by AMD GPU owners, AMD have finally fixed the vRAM running at high speed/3d clocks with high refresh rate monitors.

I am for the 1st time since owning my 165hz monitor able to just go to display settings in Windows and run it at 165hz and the vRAM doesn't automatically jump up to full speed when browsing or doing anything light/not gaming on the computer.

Right now, 6w usage with Opera browser open and 165hz refresh rate, previously I had to run 100hz top stop the vram from running full 3d clocks which in turn, increased the power draw from around 7w to 25-30w, increased heat output affecting the zero-fan feature. No more CRU custom profiles, running my monitor at a lower refresh rate or switching refresh rates when gaming/not gaming.

Hallelujah praise the lord it has only taken them a few years to work out , I'm using the latest 22.5.2 drivers for anyone interested.

Which GPU are you using? I have this problem, which AMD swears is normal, on my RX5700XT, not to mention more driver crashes than I have ever experienced with a video card.
I'll check later...