Turning on instant replay or starting a recording though relive makes the Core Clock set itself to Min/Max in State 7
Video of the issue in action:
System
- AMD Graphics Card Make & Model
- RX Vega 64
- Desktop or Laptop System
- Desktop
- Operating System
- Windows 10 Pro 64bit Version 21H2 OS Build 19044.1586
- Driver version installed
- Radeon Software Adrenaline 22.3.2 (I have rollback all they way to 21.12.1 and while it didn't happen before in earlier ones it does now)
- Display Make and model and connection/adapter in use, resolution, and refresh rate.
- Philips 43PUS8536 3840x2160 @60Hz connected through HDMI
- CPU/APU Make and model number
- Ryzen 5 2600X
- Motherboard Make & Model + Bios Revision
- Asus ROG Crosshair VII X470 BIOS 4402
- Power Supply Unit Make & Model + Wattage
- Corsair RMi1000 1000w Plus Gold
- System Memory Make & Model + Frequency
- Corsair Vengeance RGB Pro 3200Mhz CL16 2x8GB
Thanks for the help
V64 owner here too. Had many times in the past with core/mem clocks getting stuck on highest power state during wattman overclocking and applying wattman profiles. Seems to be entirely random when it happens.I usually just spam restarts or DDU + reinstall drivers when it gets stubborn. I've never personally seen this specific behaviour with Instant Replay though.
Also, that thing where the other power states get greyed out in wattman is a relatively new thing, I've had it before too but only in the past few driver versions. That also seems to happen randomly too - no real rhyme or reason to it that I can discern.
This is from February, when I first ran into it.
not sure why you'd ever actually do that in a real situation though?
here's mine as of right now
also, just tried it. doesnt turn grey for me.
edit: should probably point out that the settings in this screenshot are identical to the one i posted above. yet that one has greyed out sliders. it is UTTERLY random and happens on multiple driver versions from this year. i can go an entire overclocking session without seeing it a single time, then it'll randomly start doing it over something as simple as changing a fan curve, or applying a profile. theres no rhyme or reason that i've been able to see at all.
so, i have HWinfo open on my second monitor 100% of the time when im on my PC. just to keep an eye on things.
and now im recalling all the times in the past where i've looked at core clocks while on a menu (or an otherwise low-usage scenario) in a game and thought "huh, why is it pegged at max?". of course, clocks always drop during any significant load, meaning the problem becomes undetectable. and due to the heavy undervolt i run on my card, its hard to notice any increase in temps from this either. good job finding this dude.
glad i dont actually use desktop recording LOL. and i guess i dont mind stuck core clocks when im actually on a game.
