Fast boot already disabled. Wattman settings (maybe ZeroRPM and fan only) missing on wakeup (fan has 0 RPM while my manual profile set it at 37%)
I stopped having this problem once I uninstalled Afterburner. I have fast start disabled too. But it took not using afterburner to stop the resetting. The only thing I afterburner for is the onscreen display. Now I use the amd overlay if I am curious about performance and temps.
I have this Problem too. I set Wattman Global Settings to a User-Fan-Curve without zero RPM (so the fan is always on) which works fine for the first System-Start. But after wakeup from energy saving states it shows my settings BUT does have 0 RPM on the fan.
Reload my profile does not solve it: At first I have to reset the settings and than load my profile to get it work. Alternative is while in Alt-R Overlay under Wattmann/Fan turn 0RPM on and off again makes it work at once.
My Radeon Software is 19.4.2
Also while the setup fpr Wattman names Global Settings under games (which autmatically seem to use game-profiles) it will ignore my setting. Is it for real that I have to set up my fan-curve for every single gameprofile?
exactly same problem... actually after wake up i load up wattman turn zeroRPM and save then load my profile
again...btw it's very annoying. Glad not to be the only one with this issue.
Same here, sometimes my custom settings get applied at startup, sometimes they don't.
I know for a fact that if I let windows' shut off the display after x minus of being idle after boot with no log in, that the settings will need to be reapplied.
I can also, usually, count on the same behavior if I turn off my primary monitor while logged in to windows.
Lately I have just resorted using radeon chill with a narrow framerate rather than trying to undervolt my vega 64. It just runs too hot and I don't want to rebuild it to replace the pads on the vrms. ( Asus strix oc variant ).
I can, in fact get it stable for testing purposes at the advertised clock for that card. But meh, might be better off without the whirring of 3700 rpms directly behind my monitor.
Have you disabled fast start?
Note..you must restart your computer for the settings to apply.
Deciding whether to bother with Fast Startup actually takes longer than turning it on or off. First, open up your power options by hitting Windows+X or right-clicking your Start menu and selecting Power Options. In the Power Options window, click “Choose what the power buttons do.”
If this is the first time you’ve messed with these settings, you’ll need click “Change settings that are currently unavailable” to make the Fast Startup option available for configuration.
Scroll to the bottom of the window and you should see “Turn on fast startup (recommended),” along with other shutdown settings. Just use the check box to enable or disable Fast Startup. Save your changes and shut down your system to test it out.
If you don’t see the option at all, it means hibernation is not enabled on your machine. In this case, the only shutdown options you’ll see are Sleep and Lock. The quickest way to enable hibernation is to close the power settings window and then hit Windows+X and open Command Prompt (Admin). At the Command Prompt, type the command:
powercfg /hibernate on
Yes. I wouldn't be posting if I had not tried that. And those other things I did when I set windows up to begin with. I know the evils of hibernation.
Like I said, it seems completely random unless I cause a link state failure, or windows turns the monitor off on me because I've been staring at these forums in frustration for too long.
Ok, for this part of my statement I pull it back:
"Also while the setup fpr Wattman names Global Settings under games (which autmatically seem to use game-profiles) it will ignore my setting. Is it for real that I have to set up my fan-curve for every single gameprofile?"
This seems to work meanwhile (watched that one or two Radeon Versions before the last time). The Global Wattman Settings are now in every game profile AND working as intended: So my fan is always on and did not went off while gaming or leaving a game.