I've seen crashes with every 30.x series drivers in Battlefield 1 with my Vega 56 after some time of game play. But as I am largely playing this game on Linux these days, it matters less and less for me.
Software Version - 2021.1201.0115.2259
Driver Version - 21.40.11.03-211201a-374383E-RadeonSoftware
Provider - Advanced Micro Devices, Inc.
2D Driver Version - 8.1.1.1634
Direct3D® Version - 9.14.10.01515
OpenGL® Version - 29.20.11000.14802
AMD Audio Driver Version - 10.0.1.23
Vulkan™ Driver Version - 2.0.204
Vulkan™ API Version - 1.2.196
VRAM clock stuck at idle?
Is it related to this?
Radeon performance metrics and logging features may intermittently report extremely high and incorrect memory clock values.
Nowdays driver it's easy to notice. All radeon driver has WHQL certification, the only difference are signature which can found on GPU-z Section.
WHQL present (dxdiag) with Beta Signature (GPUz) are classified as Optional Driver
WHQL present (dxdiag) with WHQL Signature (GPUz) are classified as Stable driver
Note: If the driver doesn't have WHQL signature, game with drm protection like EAC (EasyAntiCheat) or Vanguard will refuses to run resulting on "Untrusted System File Detected"
VRAM clock stuck at idle?
Is it related to this?
Radeon performance metrics and logging features may intermittently report extremely high and incorrect memory clock values.
No. If you have multiple monitors with different refresh rates or monitors with very high refresh rates then you memory clocks will be higher.
For instance I have a 1080p 60Hz and a 1440p 144Hz dual monitor setup.
If I run them both at those frequencies then memory clocks stick to max all the time, if I drop the one monitor from 144Hz to 120Hz and run the two monitors in 60Hz and 120Hz then memory clocks drop to around 192MHz.
This is the way is always been AFAIK with multiple monitors with mixed resolutions, refresh rates, etc.
No. If you have multiple monitors with different refresh rates or monitors with very high refresh rates then you memory clocks will be higher.
For instance I have a 1080p 60Hz and a 1440p 144Hz dual monitor setup.
If I run them both at those frequencies then memory clocks stick to max all the time, if I drop the one monitor from 144Hz to 120Hz and run the two monitors in 60Hz and 120Hz then memory clocks drop to around 192MHz.
This is the way is always been AFAIK with multiple monitors with mixed resolutions, refresh rates, etc.
Exactly. My memory clocks dont drop unless i use only one monitor. I've been using three monitors and it has always been maxed out.
Exactly. My memory clocks dont drop unless i use only one monitor. I've been using three monitors and it has always been maxed out.
That's not really an issue AMD can even fix. It's caused by non standard settings for monitors. You can actually fix the issue by changing the display settings with CRU
It says "non whql" because it's not a recommended driver. But the driver is signed.