• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

The AMD Driver Thread

For anyone who is having issues with Wattman forgetting overclock/undervolt setting on reboot. Try disabling Windows fast boot. Ever since I disabled this setting my Wattman settings are applied on reboot/startup.
  1. Go to Control Panel.
  2. Click Power Options.
  3. Click Choose what the power buttons do.
  4. Click Change settings that are currently unavailable.
  5. Scroll down to Shutdown settings and uncheck Turn on fast startup.
  6. Click Save changes.
 
For anyone who is having issues with Wattman forgetting overclock/undervolt setting on reboot. Try disabling Windows fast boot. Ever since I disabled this setting my Wattman settings are applied on reboot/startup.
  1. Go to Control Panel.
  2. Click Power Options.
  3. Click Choose what the power buttons do.
  4. Click Change settings that are currently unavailable.
  5. Scroll down to Shutdown settings and uncheck Turn on fast startup.
  6. Click Save changes.

I guess you also have fastboot switched off in the BIOS?
 
Not sure, I can check but doing this within Windows seems to have worked for me. Though to be honest I have only been testing a few days, but before this every single reboot resulted in OC/UV being back to balanced mode.
 
I guess you also have fastboot switched off in the BIOS?

There's usually an option in BIOS called "Fast boot" to shorten the POST sequence and start running the bootloader without first waiting for all storage devices and peripherals to be enumerated and identified. This takes place before Windows gets going and is independent of Windows "fast startup" which uses the hibernation file as a cache to shortcut device driver initialisation. BIOS fast boot shouldn't affect Wattman, but Windows fast startup does.
 
There's usually an option in BIOS called "Fast boot" to shorten the POST sequence and start running the bootloader without first waiting for all storage devices and peripherals to be enumerated and identified. This takes place before Windows gets going and is independent of Windows "fast startup" which uses the hibernation file as a cache to shortcut device driver initialisation. BIOS fast boot shouldn't affect Wattman, but Windows fast startup does.

Yep, BIOS fast boot and Windows fast boot are independent of each other.
 
There's usually an option in BIOS called "Fast boot" to shorten the POST sequence and start running the bootloader without first waiting for all storage devices and peripherals to be enumerated and identified. This takes place before Windows gets going and is independent of Windows "fast startup" which uses the hibernation file as a cache to shortcut device driver initialisation. BIOS fast boot shouldn't affect Wattman, but Windows fast startup does.

OK this makes sense and it's something I also reported onto here couple months back.
That resetting Windows hibernation files seems to have fixed my wattman issue I was having.
 
Interesting. What problem?

When booting PC from a cold boot wattman would reset itself to default settings. If I shutdown PC and start up again it would remember my settings.

It was an issue with Windows fast boot/hibernation

I just switched hibernation off and back on again and not once had the issue again.

It only happened that once.

The great thing about Asus LED on board if my motherboard reads AO that means it's running from a cold boot no fastboot, if it says 40 the it's running from a hibernation file =fastboot.
 
When booting PC from a cold boot wattman would reset itself to default settings. If I shutdown PC and start up again it would remember my settings.

It was an issue with Windows fast boot/hibernation

I just switched hibernation off and back on again and not once had the issue again.

It only happened that once.

The great thing about Asus LED on board if my motherboard reads AO that means it's running from a cold boot no fastboot, if it says 40 the it's running from a hibernation file =fastboot.
Thanks, will put that little trick in my tech support back pocket.
 
What!!!, how did you get credit for my fix :p

:)


Post 14267 :p
Possible fix for you guys that have Wattman reset on system start up. Seems like its a glitch that happens when you have Windows 10 Fast boot enabled... If fast boot fails to load it will load the last known clean settings that also restores Wattman settings. I just found this out by my Fast boot glitched and failed to load some programs at start up and I also got Wattman failure.

Too see if this is the case for you, does wattman only fail from a full system power on meaning you first have shutdown then system? Or does it also fail even with a simple system restart?
If it doesn't happen with a normal restart then you will need to delete or temp disable and re-enable Hibernation

https://www.tenforums.com/tutorials/2859-enable-disable-hibernate-windows-10-a.html

Put this here also from VEGA 56 thread so more people can see it.

Windows 8 and 10 added a feature called Fastboot it uses hibernation to create a image off all the Windows loaded settings so when you power on the PC you will start much faster.. When you pull the PSU switch you will reset all the Windows setting and even remove the fastboot image so Windows will fall back to the default settings.
I just tried it myself and it failed my Wattman settings.

If a user shutdowns Windows with Fastboot enabled, and then switches the PSU off next start up will fall back to default windows image and result in Wattman settings from failing.

This could explain why users on here are saying the wattman doesn't always remember settings after see do these guys power off the PSU!!!
 
Last edited:
Anyone else find MSI Afterburner completely locks up your pc when starting the program up?

Found this regardless of which driver I'm using. I assume this is a driver issue? :/
 
Pl
Anyone else find MSI Afterburner completely locks up your pc when starting the program up?

Found this regardless of which driver I'm using. I assume this is a driver issue? :/

I have a V64 and Afterburner is unusable if you plan to undervolt it. The voltage control in Afterburner affects ALL P-States on your AMD GPU and this causes serious instability, because on boot your lowest idle P-State gets loaded with not enough power to remains stable.
 
Does use of WattMan profile lock all manual controls/settings?
Or can those be tweaked manually, while profile acts more like presets?

With finally stabilized availability/pricing here in Finland considering getting Vega soon.
And Power Save profile could be good starting point for optimizing power efficiency.



I have a V64 and Afterburner is unusable if you plan to undervolt it. The voltage control in Afterburner affects ALL P-States on your AMD GPU and this causes serious instability, because on boot your lowest idle P-State gets loaded with not enough power to remains stable.
So Afterburner sticking its nose into where it shouldn't be...
Guess MSI forgot some testing.
 
Back
Top Bottom