Search results

Thank you :) I'll submit a bug report to AMD, I'm currently on the latest drivers (23.2.2), maybe they have broken something in the recent releases.

Also this is roughly what it looks like before the sensor disappears:

I believe I have captured this situation, After the sensor disappeared, shutdown HWiNFO, changed HWiNFO64.INI to add DebugMode=1, and re-ran with sensor missing then closed the application again. Sensor was not available again until system was rebooted.

Has anyone else seen odd behavior for monitoring Memory Clock frequency on Radeon 6000 series cards? It is possible that this is some type of driver issue/ADL/ALDX problem perhaps, but under HWiNFO 7.36 and 7.40 I've noticed that "GPU Memory Clock" values appear to stop working. The issue...

"GPU Memory Usage" is definitely broken on AMD cards/later drivers, my 6900 XT will report this value to exceed 70gb at times. Is this value derived from the AMD ADL API? Also does anyone know the "official" method to report issues to AMD's driver team?

I looks like this *might* be fixed by 477.11, it has been running for quite some time without the previous behavior.

Noticed 7.02 was consuming 1GB+ of memory, found this topic, issue still exists in 466.11 drivers as well

Okay, thanks for the information. I will just use run-as functionality going forward.

Has there been some fundamental change in how the installed driver is detected in 5.8x? In 5.7x (and previous), launching the program as an administrator, installing the driver, and then marking the driver as persistent then allowed non-administrative users to still launch the program and see...