AMD GPU shows VRAM clock stuck at 1250 -- much lower than expected

[birbowirbo]

Describe the bug

Currently running a 7900xtx AMD GPU -- when under heavy load the VRAM clock is stuck at 1.25ghz -- when under similar load in Windows, the VRAM clock routinely boosts to 2.5ghz (as reported by AMD's Adrenalin)

Opening lact I find that the program has the Maximum VRAM auto detected to 1250 -- and can only be set to a value of 1500.

What did you expect to happen?

I expected lact to allow for similar VRAM clocks as windows.

Output of rpm-ostree status

Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:stable
                   Digest: sha256:beb803ae02ef84a1536f4a78caa98d091454ce03bb2ad626d0e854fba8096de1
                  Version: 41.20250206 (2025-02-06T17:57:19Z)
          LayeredPackages: coolercontrol lact liquidctl

  ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:stable
                   Digest: sha256:beb803ae02ef84a1536f4a78caa98d091454ce03bb2ad626d0e854fba8096de1
                  Version: 41.20250206 (2025-02-06T17:57:19Z)

Hardware

B850M PRO RS WIFI

Extra information or context

[KyleGospo]

1250 x2 is 2500

The first D in DDR stands for Double

[birbowirbo]

Kyle you have educated me.
Thank you.