RX 470 100% Utilisation after closing DX12 and VK games and apps

[hrp32]

So RX 470/570 users including me, have been experiencing this issue for at least a year now. It's in the known issues section of the AMD Software website download page but I wonder what's keeping AMD from fixing it.
I've used ATi cards most of my life but their drivers have not always been the best, had many minor issues throughout the years.
I hate Nvidia with all my guts and I will never switch to them again. I wish best of luck for Intel and their graphics team though.

 

[pavle]

There have been some issues, but never as big as 100% utilisation in idle, but hey, AMD must have overlooked something in the driver the card not being the newest and all...

 

[Romulus2K4]

This is a known issue that increases/decreases in frequency from driver release to driver release, it's the dreaded idle clock bug.

 

[P4-630]

This is a known issue that increases/decreases in frequency from driver release to driver release, it's the dreaded idle clock bug.

OP is talking about 100% load on idle as far I understand...

Edit: Miner software running perhaps? Or (mining)malware.

 

[Romulus2K4]

OP is talking about 100% load on idle as far I understand...

Edit: Miner software running perhaps? Or (mining)malware.

When this idle clock bug occurs, it does show 100% GPU usage. The memory clock downclocks, but not the core. A simple restart of the GPU driver fixes the issue, I recommend using the Restart64.exe that comes with ToastyX's CRU (Custom Resolution Utility) just for restarting the driver when needed. The power draw is quite low, and this behavior was under AMD's known list of bugs for Polaris for quite some time.

 

[hrp32]

OP is talking about 100% load on idle as far I understand...

Edit: Miner software running perhaps? Or (mining)malware.

It's a known issue for AMD which is discussed about on other forums, including AMD'S own website many times.
It just seems they don't care at the moment.

 

[Romulus2K4]

It's a known issue for AMD which is discussed about on other forums, including AMD'S own website many times.
It just seems they don't care at the moment.

It was fixed in a build, then the issue just came back. I can't remember in which build though.

 

[The King]

Windows button + ctrl + shift + B can be used to restart the gpu driver as well.

 

[hrp32]

It was fixed in a build, then the issue just came back. I can't remember in which build though.

TBH, It's not a big deal for me. If you open and close another dx11/OpenGL app or game, the utilisation gets back to below 5%.

I'm just wondering if it took an entire year and the issue is still there, their code could be a mess or they just simply don't care. Either way, this makes me think twice about choosing AMD/ATi cards for my next build but then again I despise Nvidia so wishing good luck for Intel and hope AMD/ATi care a bit more.

 

[Romulus2K4]

TBH, It's not a big deal for me. If you open and close another dx11/OpenGL app or game, the utilisation gets back to below 5%.

I'm just wondering if it took an entire year and the issue is still there, their code could be a mess or they just simply don't care. Either way, this makes me think twice about choosing AMD/ATi cards for my next build but then again I despise Nvidia so wishing good luck for Intel and hope AMD/ATi care a bit more.

Wait just a bit more, the issue will likely get addressed, real soon.

 

[eidairaman1]

Use the Radeon Pro For Enterprise drivers

 

[Romulus2K4]

Or just wait for the next release, which is just around the corner. It'll definitely have this issue fixed.

 

[Romulus2K4]

@hrp32 22.11.2 is out right now, and it fixes the issue.

https://www.amd.com/en/support/kb/release-notes/rn-rad-win-22-11-2

 

[eidairaman1]

@hrp32 22.11.2 is out right now, and it fixes the issue.

https://www.amd.com/en/support/kb/release-notes/rn-rad-win-22-11-2

Good to know but heads up for Stable drivers when the Standard Adrenaline set are wonky use the Enterprise Drivers

 

[Hofnaerrchen]

So RX 470/570 users including me, have been experiencing this issue for at least a year now. It's in the known issues section of the AMD Software website download page but I wonder what's keeping AMD from fixing it.

Other problems/bugs that plague newer products. At a certain point it's simply no longer profitable to use resources on fixing problems of older cards. In almost all industries you'll find a mindset like "they probably get a newer product nonetheless soon".

 

[eidairaman1]

Other problems/bugs that plague newer products. At a certain point it's simply no longer profitable to use resources on fixing problems of older cards. In almost all industries you'll find a mindset like "they probably get a newer product nonetheless soon".

AMD has been releasing Drivers for RX400 and older under a different time cycle compared to RX 500 and newer.

 

[mechtech]

I've seen that happen sometimes with browsers and gpu acceleration. Also with steam and certain settings.

I heard malware could also do that.

Try restarting in safe mode and looking??

 

[Romulus2K4]

Good to know but heads up for Stable drivers when the Standard Adrenaline set are wonky use the Enterprise Drivers

Sorry, but I have to disagree with this.

I've seen that happen sometimes with browsers and gpu acceleration. Also with steam and certain settings.

I heard malware could also do that.

Try restarting in safe mode and looking??

Please try reading some of the older posts from the thread.

 

[eidairaman1]

Sorry, but I have to disagree with this.



Please try reading some of the older posts from the thread.

Your choice, seen many here switch and issues be resolved

 

[Romulus2K4]

At the end of the day, if you're happy with the enterprise drivers and they work for you, by all means continue using them. The same applies to the standard drivers.

 

[Hofnaerrchen]

AMD has been releasing Drivers for RX400 and older under a different time cycle compared to RX 500 and newer.

Wake up!

Releasing drivers and fixing bugs is quite a different story in terms of used resources. You can see this behavior everywhere. Take older versions of Operation Systems for example. They might get security updates but no new features they might have received while being the current version. It's part of marketing. While you don't want to completely displease your old customers you also want to give them a reason to buy a new product and in a quite short-lived branch, like GPUs, a six to five year old product is just not worth the extra amount of care it might need. Should the bug be fixed it's probably a coincidence but - as I already said - most likely not because they did put much effort in it. Fixing problems of the newer generations have priority and with RDNA3 being on the doorstep they will focus on the new generation and bugs that might prevent sales.

Edit: Looks like you will be a very happy person today - it got fixed with 22-11-2.

 

[Zyll Goliat]

Well seems like that latest 22.11.2 FIXED this issue so pls. download this driver and check if the problem still exist.......

 

[hrp32]

Thanks everyone. I will update when I get a chance and report back here.

 

[Romulus2K4]

If you do come across issues with Polaris GPUs in the future, and if it's something that I am able to reproduce on my end, I'll make sure to report it to someplace where it'll at least be looked at with importance. Whether the issue will get fixed with certainty is another story.. but still, feel free to ping/tag me with a detailed description of the issue and how to reproduce it. Think of me as just a messenger.

 

[eidairaman1]

Wake up!

Releasing drivers and fixing bugs is quite a different story in terms of used resources. You can see this behavior everywhere. Take older versions of Operation Systems for example. They might get security updates but no new features they might have received while being the current version. It's part of marketing. While you don't want to completely displease your old customers you also want to give them a reason to buy a new product and in a quite short-lived branch, like GPUs, a six to five year old product is just not worth the extra amount of care it might need. Should the bug be fixed it's probably a coincidence but - as I already said - most likely not because they did put much effort in it. Fixing problems of the newer generations have priority and with RDNA3 being on the doorstep they will focus on the new generation and bugs that might prevent sales.

Edit: Looks like you will be a very happy person today - it got fixed with 22-11-2.

How about you open your eyes.