Jump to content
AIDA64 Discussion Forum
JuniorSantana93

fixed: Locked GPU utilization on Radeon RX 500 Series

Recommended Posts

I have an AIDA64 Extreme error after AMD Crimson ReLive 17.5.2, and there is still no AMD Crimson ReLive 17.9.3, GPU usage is locked at 16%, see a photo.

Note: I use a Gigabyte RX 570 G1 Gaming 4GB, and it looks like the error is on the entire RX 500 line from AMD.

Screenshot_7.jpg

Share this post


Link to post
Share on other sites

We've checked, and we haven't been able to reproduce this issue with either Crimson 17.5.2 or 17.9.3 WHQL.  Maybe because we use a RX 560 test card, and the issue affects only RX 570 and RX 580?

Please right-click on the bottom status bar of AIDA64 main window --> Video Debug --> ATI GPU Registers. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first.

BTW, have you tried to install the recently released Crimson 17.9.3. WHQL driver?  I wonder if that makes this issue go away or not.


Thanks,
Fiery

Share this post


Link to post
Share on other sites
On 10/10/2017 at 11:27 AM, Fiery said:

We've checked, and we haven't been able to reproduce this issue with either Crimson 17.5.2 or 17.9.3 WHQL.  Maybe because we use a RX 560 test card, and the issue affects only RX 570 and RX 580?

Please right-click on the bottom status bar of AIDA64 main window --> Video Debug --> ATI GPU Registers. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first.

BTW, have you tried to install the recently released Crimson 17.9.3. WHQL driver?  I wonder if that makes this issue go away or not.


Thanks,
Fiery

This problem occurred after drive 17.5.2, in that drive a GPU load detection, is in normal state.
Obs: I'm using Crimson 17.9.3 WHQL.

atigpureg.txt

Share this post


Link to post
Share on other sites
34 minutes ago, JuniorSantana93 said:

This problem occurred after drive 17.5.2, in that drive a GPU load detection, is in normal state.
Obs: I'm using Crimson 17.9.3 WHQL.

atigpureg.txt

Thank you.  Please upgrade to the latest beta version of AIDA64 Extreme available at:

https://www.aida64.com/downloads/latesta64xebeta

After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

Let me know how it works.

Share this post


Link to post
Share on other sites
1 hour ago, Fiery said:

Thank you.  Please upgrade to the latest beta version of AIDA64 Extreme available at:

https://www.aida64.com/downloads/latesta64xebeta

After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

Let me know how it works.

Now, yes, I had tested the beta version of the site and continued with the bug, but with this beta version that you passed, it is working perfectly. Thank you.

Note: It's time to update the stable version now on the site.

Screenshot_8.jpg

Share this post


Link to post
Share on other sites

Thank you for your feedback. It will take a few more weeks for us to get to rolling out a new stable update ;)

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

  • Similar Content

    • By neg12roni
      Running a Gigabyte Vision D Z490 board with the Core i5-10400 CPU. Have configured the fans in  BIOS but Aida64 doesn't see any of them in the LCD option, none are listed.
      Also, CPU temp never changes from 28celcius so I'm guessing that isn't really working either.
    • By DmitryKo
      Display - GPU tab shows incorrect shader model version 6.3 with AMD WDDM 2.7 drivers, whereas dxcapsviewer reports shader model 6.5.
      Please note you need  to pre-initialize the feature query with the highest SM version to report - so if you ask for SM 6.3, you will never get higher than that. The correct detection algorythm has to cycle through all known shader models, starting from the highest known version and going down until success (or start with 5.1 and loop up to the highest until failure). The latest Windows SDK Preview defines SM 6.6.
       
    • By Laxeringsmedel69
      First problem: I have problem with my OSDpanel, while playing for example Pubg I have "Cpu" and "Gpu" temps and they wont stay as top most window.
      Second problem: My sensorpanel every time i click (left and right) on my desktop the sensorpanel closes and opens it takes between 0,5 and 1 seconds. If I right click on my desktop the sensorpanel disappears and the normal windows drop-down menu comes up for a good 0,5 to 1 seconds and then closes and the sensorpanel pops back where it should be. It is just a little annoying because i can not while the sensorpanel is showing change any thing in the drop-down menu. My friend does not have the problem and I can not find the issue... (My spelling isnt perfect but hey its not that important)
    • By AliOXen
      I'm having issues finding the CPU Temperature sensor. Using a Strix B450-I mobo.
      The 2070 Super Temperature sensor shows up fine.
      Am I doing something wrong?

    • By monchote
      Hi there, AIDA64 is not showing the motherboard temperature and showing the SB temp twice instead (see attached image for comparison). The M/B sensor is reporting 45C instead of 67C.
      Motherboard: ASRock X570 Phantom Gaming-ITX/TB3
      Thanks a lot in advance!

×
×
  • Create New...