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.
Solved! Go to Solution.
I fixed it.
Get vivetool. This is a command line interface that will allow you to disable co-pilot (which is causing this issue) with the command:
./vivetool /disable /id:44774629,44776738,44850061,42105254,41655236
Note the period and the slash at the beginning. This is required if you're using PowerShell (administrator). You could also issue the command without the period and slash in CMD (admin)
Short story short? Go here:
https://github.com/thebookisclosed/ViVe/releases
unpack it to a folder (ie c:\vivetool)
Open that folder in an admin PowerShell session and issue that command. Reboot and all is well.
With vivetool windows will NEVER again tell me what I can or can't have on my computer.
Just picked up a RX 6800 and the CP looks nice but I've been running into issue after issue. First I had to disable ULPS as my whole PC would crash after waking, now none of the settings in the panel will save after either wake OR reboot. And why in the world is AMD Software in the context menu globally? It should ONLY be when right clicking the desktop.
At least it didn't try to fry itself like my 7950 nearly did after Crimson drivers forced a 0% fan all the time.
I guess AMD still hasn't figured out this driver thing after 25+ years.
The vivetool seemed to help for reboots but it's still happening on wake. I noticed all windows go black on wake too, it's like the driver is crashing on wake.
I had used Vivetool in the past to fix this, but it started happening again after a recent W10 update. Just wanted to report back that this solution still works, and that I only had to disable ID: 42105254 for it to be successful. I'm also still on driver version 24.5.1. Maybe the newer drivers are not affected by Co-Pilot, but I can't check because the newer drivers have so far been completely broken on my system.
No, the reason was Gigabyte Control Center addon Gigabyte VGA Tools
gr33tz