A week ago, brikulex posted a solution on amd forums and I’m genuinely dumbfounded that this works:
I don’t think that AMD is actually working on fixing this.
However I believe I have found something (at least something that works for me).
As always, I am not responsible for what you do, and if following my guide makes your computer explode, it’s not my fault.
I am asking some of you who are affected by this bug and ever had Epic Games Launcher installed to try this:
Exit Epic Games Launcher if you have it open (right click it in the notification tray and click Exit)
Open the folder %localappdata%\EpicGamesLauncher\Saved
Rename the Logs folder to something like LogsBackup
Try to open Radeon Software and hope it works
Please respond if it fixed your issue or not, or if you don’t even have the EpicGamesLauncher folder.
If I find out it doesn’t actually work and it was just a coincidence, I will edit this post to correct it.
Good Luck!
didn’t work for me, what did work was deleting %localappdata%/AMD/CN/gmdb.blb.
TYSM bro, holy shit it worked!
How bizarre.
I’ll keep this in mind if I come across this bug.
If a bug exists and amd can reproduce it then it gets fixed
There is no ignoring suchwe dont need conspiracy theories
Agreed, but this could also be an Epic games problem. The fix is to change a file name with Epic games, not AMD.
I disagree. AMD is reading the game files and expects something to be there. If the file(s) aren’t there or are corrupt AMD needs to be able to handle that in their software with good error handling. Clearly its not currently as it is throwing an error and nothing is catching it so the whole AMD suite breaks at launch. - speaking as a dev.
This solution would only make sense if the problem (Adrenalin crashing/failing to launch) was caused by the game detection part of Adrenalin throwing an unhandled exception when trying to access the Epic Games Launcher folder. Perhaps the permissions/ownership of the folder were changed to restrict who can access the Logs folder, and the game detection routine does not fail gracefully if it can’t access the folder properly. That would be bad programming practice, since you never can rely on files on the filesystem being there at all times and under all configurations.
And if that is the case, then some other software that also requires privileged access for their folders would also cause that.
A bad thing to try in this case: Try starting Adrenalin with Administrator privileges. This should not be done for normal usage, and since Adrenalin has a lot of attack surface, it should not be a real solution.
I don’t have this problem, although I have several different launchers installed.
worked for me
I’m just buying an nvidia card next time. Cba doing more fixes.
Why I uninstalled Epic games launcher years ago and don’t play anything from them - always caused weird issues.
Something I’ve noticed only in the latest drivers (might have had it before) on my 5700XT, when fps is near the fos cap I set (with Vsync, freesync or any other fps limiter) I hear something like coolwine, but not the high pitched I did a few times, something like with more base/deep
Wtf it worked for me, I uninstalled EGS like one year ago but it still did the trick !
https://i.imgur.com/vFlqlJs.png
Thank you
And if the Epic Launcher solution does not work there’s
- delete corrupted game profile “c:\Users\ \Local\AMD\CN\gmdb.blb” file and restart
thanks so much
Do you have the backup copy for the EGS logs when the issue is reproduced? I would love to grab them to see if we can reproduce this issue in-house.
Thanks!
Awesome, thank you very much! Downloaded and will be forwarding it to our team to help reproduce the issue
wow I can’t believe the whole time it’s some appdata caused it, I don’t even have EpicGamesLauncher installed at the time, it’s some left over data.
Thanks for forwarding the solution here. Finally I can go with the stable driver, not preview driver just to use the adrenalin software.
I couldn’t open it randomly 2 days later was able too . Didn’t change anything … just remember trying to open it to check settings while playing MW3 … closed game out when done tried opening … nada … shut down bc didn’t feel like going down rabbit hole . Next day same but only on for 10 mins following day opened … go figure
Wait so this is why Fortnite always crashes my driver all of a sudden?? I was wondering why it started weeks after my last adrenalin update.
I wound up just installing the display driver standalone without Adrenalin and it’s been working fine since.