• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
  • The forums have been upgraded with support for dark mode. By default it will follow the setting on your system/browser. You may override it by scrolling to the end of the page and clicking the gears icon.

22.5.2 amd and gpu-z 2.46.0

I tested 22.6.1 and it works for CPU Z and GPU Z issues
 

Attachments

  • 20218a9d40448cec.png
    20218a9d40448cec.png
    34.9 KB · Views: 91
  • -4bd8192b536078c1.png
    -4bd8192b536078c1.png
    57.5 KB · Views: 100
  • -45b2f1f885d67a9.png
    -45b2f1f885d67a9.png
    35.9 KB · Views: 78
  • -48bea6203190b409.png
    -48bea6203190b409.png
    50.6 KB · Views: 84
@StefanM - I think yours is a separate, unrelated laptop GPU issue, IIRC. And thus needing a separate, other fix.
Whatever was broken, it has been fixed in 22.7.1

x3m.png
8d4.png
 
If using GPU Z 2.46 in a 22.7.1 driven computer will it work like GPUZ 2.47 in your picture?
Yes, because AMD fixed the issue in their drivers
 
Yes, because AMD fixed the issue in their drivers
There are Vega cores included (?
Not for me... (before s.o. asks: i rebooted after installation)

gjs.png
v8y.png

In his previous dialogue Vega is useless under 22.6.1 driver

So I wonder if AMD has further fixed this issue in the 22.7.1 driver

and wondered if this 22.7.1 driver would also work on older GPU Z (like version 2.46)
 
There are Vega cores included (?


In his previous dialogue Vega is useless under 22.6.1 driver

So I wonder if AMD has further fixed this issue in the 22.7.1 driver

and wondered if this 22.7.1 driver would also work on older GPU Z (like version 2.46)

I can roll back to GPU-Z 2.4.1 (ignoring the Crimson vs. Adrenaline naming)
Yet older versions do not detect memory size.
 
After installing the 22.10.2 driver on my friend's 6650XT, some of his information cannot be read (even if the problem still exists after reinstallation)

(Edit: It seems that even the AMD driver has this problem in VRAM reading)

Wondering if anyone else has encountered
 

Attachments

  • Screenshot_20221022-143752_Facebook.jpg
    Screenshot_20221022-143752_Facebook.jpg
    163.7 KB · Views: 68
  • received_824902101867211.jpeg
    received_824902101867211.jpeg
    82.5 KB · Views: 61
For comparison, could you take these same screenshots, but with older 22.10.1 driver?

And latest one for Sept 2022 too?
 
For comparison, could you take these same screenshots, but with older 22.10.1 driver?

And latest one for Sept 2022 too?
I was asking to see if my friend could help I noticed it when I was looking at a picture my friend sent me

Me I can't test it, just wanted to ask if anyone else using the 22.10.2 driver has encountered it
 
For comparison, could you take these same screenshots, but with older 22.10.1 driver?

And latest one for Sept 2022 too?
Can you ask if you have encountered the same problem after using the 22.10.2 driver
 
Great! :) Thanks for letting us know.
I guess it was a known bug in 22.10.2 driver.
 
Back
Top