PC Drivers & Software

[cyberwaste]

Adrenaline 23.9.3 resets to default tuning values every boot/reboot stating there was an unexpected system failure when nothing happened. It does this even if the settings were already on default.

Anyone know how to fix this?

Everything is completely stable otherwise.

Using an Asus TUF 7900XTX OC.

[rawintellect]

What did you do to deactivate it? Simply switching the toggle off won't work. You have to disable it entirely using vivetool.

[sirhacky]

Hello, exactly, I did it with the Vivetool - several times.

The problem already occurred for me with version 23.8.1

[rawintellect]

Try updating your drivers to 23.10.1. Immediately after using vivetool with 23.9.2 and 23.9.3 I had no issues whatsoever. This has solved it for many others. I'm not exactly sure why you are still having an issue.

[cyberwaste]

Just an update that this still occurs with the latest (23.10.1) drivers (when not using the fix outlined in the thread).

[rawintellect]

Yep. I already mentioned this. They pulled 23.10.1 right now because it seems anti-lag was getting people banned from games.

[Anonymous]

i hope the radeon driver team gets wind of this, since vivetool is a nice workaround for what amd and microsoft should start to fix as soon as possible. this issue has been way too long.

[x0c0lait]

Today release 23.10.2 and this issue not fix.........

[silentgame]

Yeah have the same issue.  If I restart or boot my PC with fast start up disabled, in Windows I get the message and the reset of my settings.  Though, if I cold boot my PC with fast startup on in Windows I don't have any issues, everything functions normally.

[x0c0lait]

Today, without doing anything at all, adrenalin stopped resetting with each reboot, Microsoft would have patched something remotely.

[SirLanceAlot]

Same thing on my end. I'm on technical preview 23.30.01.02, will update to 23.10.2 and report back if anything changes.

[unclwish]

Adrenalin 23.9.2 Windows 11 Pro 23H2 latest. No changes. Checked just now. Any perfomance tuning resets after Windows reboot.

[TVH]

I downgraded from 11 to 10, installed 23.9.2 and so far no problems. Of course this was a bit extreme solution.

[unclwish]

"A bit extreme.."? I think it's a very extreme solution...

[TVH]

Indeed. For me it was okay, as I wanted to get rid of that CoPilot nonsense too.

[yaso0ow]

It has indeed been patched by microsoft. My OC settings doesnt reset anymore

[LosPollosHermanos]

It's very odd. I just made a new windows installation after cleaning my drive (backing everything up) and I thought the issue would have been fixed by either Microsoft or AMD but I'm still experiencing this issue after boot. Maybe i just have to wait for another Microsoft update to reach my PC? Or maybe Microsoft just made a temporary fix until it is fully fixed? Is anyone else still having the issue? I made sure to submit a bug report through AMD's bug report tool.

[Livingroom191]

For me it was also solved since driver V23.10.2 for exact one week, now the issue has returned for me. So weird.

[silentgame]

I no longer get this bug not sure why it stopped happening.  I've been on the beta AMD Fluid Motion Frames driver for a while now and the settings don't reset anymore.

[rawintellect]

Confirmed. I am on Windows release 22631.2506 (AMD driver 23.10.2) and I re-enabled Co-Pilot with vivetool. This issue appears to be fully resolved. I cannot speak for other releases of Windows.

[Bartek1205]

After installing the latest update (22621.2506), the issue disappeared, but after a few days, it came back again.

[rawintellect]

That's odd. I've rebooted quite a few (over 20+) times before posting my update just to be sure this issue was resolved. All is well for me. In fact, I rebooted just after reading your post (and just before posing this)  in fear of speaking too soon.  I'll keep an eye on it. Thanks!

[Bartek1205]

I updated to 22631.2506 (23H2) via the enablement package (Link), but it's still the same.

[rawintellect]

3 days in and still no issues.

[Bartek1205]

I used DDU and installed the 23.11.1 AMD driver, and the issue appears to be resolved for now.

[backFireX64]

AMD Adrenalin Software 23.11.1 driver solves the resetting issue for me. I'm on windows 11 22H2 v22621.2506

[sirhacky]

Me too

[unclwish]

I confirm, 23.11.1 drivers solved a problem.

Disturbingly, there are few changes in the drivers for Polaris-Navi compared to the rdna drivers. Let's hope AMD continue update drivers for Polaris-Navi in future.

[doomcreeper]

On a new PC it sometimes continues to reset to default values with adrenaline 23.11.1.

Settings are not always reset.

[creopard]

Hello,

I just registered here to say thank you!

Using the ViVeTool.exe as described here https://community.amd.com/t5/drivers-software/adrenaline-resetting-to-defaults-every-reboot/m-p/6342...

finally does not reset the custiom fan settings on every reboot von Windows 11 23H2.
(Updating the AMD Adrenalin driver to version 23.11.1 alone did not work, you need to combine it with the solution mentioned above.)

[realmister]

6750XT here, Win11 Pro 22H2, Adrenalin 23.12.1. Nothing on this thread works, not the pinned solution (vivetool) not the update recommendations, no nothing.

Honestly, my last AMD card was an RX570 and I remember very clearly switching back to team green precisely due driver/software BS like this. I cant believe after all those years team red STILL havent been able to make things as simples as persisting settings between reboots work out of the box. Disappointing.

edit. Tried updating Win to 23H2 via the enablement package. Vivetool and the rest continue not work. Bollocks.

[rawintellect]

run DDU to completely uninstall old/leftover drivers and try the solutions again. 

[realmister]

Before I installed the card I ran DDU "clean and shutdown" function in safe mode to uninstall my old nvidia card drivers. Are you suggesting that I should run it again for good measure? How many times does it take?

[rawintellect]

I was simply trying to help. I have no idea what you have and have not done. You have not stated what you've done already. Good luck to you.

[realmister]

Apologies if I came out as rude, not my intention. Anyways, I found the solution: 

It was MSI Afterburner that was messing with the tuning settings during boot. Got rid of it (and rivatuner for good measure) and now Adrenalin loaded all my undervolt, vram and fan curve setting during boot.

PS. Unwinder (afterburner dev) doesnt give a ratsass about AMD cards and its users (he said so himself in his forums) so best to go without it and use Adrenalin for all vga over/under clock needs anyway.

[Kahlimdor]

Hi there!

Glad to read that you could solve the problem. What version of Adrenalin are you running? I have a problem with Adrenalin right now. As soon as I try to change any setting (AKA not use default but custom settings) I can't run Destiny 2. After maybe 1 or 2 mins it crashes, stating that the connection was lost, or some driver failed.

Before, with Adrenalin, I was able to play D2 while OC/UV the GPU (XFX 6700XT) for months, but after some update, as soon as I try to change the stock GPU settings, D2 crashes, even being in orbit (basically afk).

Anyways, I hope they find a solution, since it was clearly possible to do before an update, now it's not. I even tried switching back to old Adrenalin versions (Of course, after running DDU) But still crashing. I find it rather "interesting" since this never happened before, but now it does, even when I'm running the same settings that back then and with older "stable versions".

Just sharing my experience. Hope you have a nice day!

Kind regards - Kahlimdor -

[doomcreeper]

I noticed how this works for me (the settings are reset) - during a normal reboot, nothing is reset - the video card settings are saved. But if I turn off the power to the PC for a couple of hours and turn it on again, then there is a chance that the video card settings will be reset, but it may not be reset.

[Gismo]

Unfortunately, i still got that problem. Do anybody got a fix for me, please...

[ AMD Default Performance Tuning Settings Have Been Restored Due To an Unexpected System Failure ]

System:   Win 11 Pro
GPU:   RX 580 8GB (No OC)

Tool for GPU-uninstall:   AMDcleanup

Thats what i have tried already:

-  Win-/AMD-driver up to date
-  ViveTool / Power Shell Admin (Configuration successful)
-  Fast Boot deactivated (BIOS+Win)
-  Win-device-installer deactivated
-  AMD Crash Defender deactivated

What else could fix my problem? Thx guys.

[NaClCrystal33]

Do you have afterburner installed? Try uninstall it.

[Anonymous]

unfortunately, the vivetool thing doesnt work for everyone and is just a temporary workaround. and theres no word from amd about it. but the thread is big enough. its time AMD takes this serious, because its supereasy to replicate. it needs to be fixed. ASAP. its absolutely arsenine to ignore this. its why amd drivers have the reputation as they do. i bet some AMD engineer is sitting on it, crying his eyes out, as ressources are poured elsewhere. i just hope the next driver release adresses this, otherwise i might contact microsoft directly.

[NaClCrystal33]

For those of you who did not get things work even with the help of vivetool, I suggest you should try to uninstall msi afterburner as it MAY affect your oc and other setting.