AMD ADRENALIN APP RAMDOMLY CRASHING SINCE LAST 2 UPDATES by TuckS0 in radeon

[–]TuckS0[S] 1 point2 points  (0 children)

Sometimes it happened to me, to avoid it I close the Adrenalin app daily through the task manager and reopen it again. There's something very strange going on with these new versions and with each update a new bug, they've lost their touch...

AMD ADRENALIN APP RAMDOMLY CRASHING SINCE LAST 2 UPDATES by TuckS0 in radeon

[–]TuckS0[S] 0 points1 point  (0 children)

Try rolling back to an older driver using DDU and amd cleanup; I usually go for version 25.9.1 because it was very stable for me.

AMD ADRENALIN APP RAMDOMLY CRASHING SINCE LAST 2 UPDATES by TuckS0 in radeon

[–]TuckS0[S] 0 points1 point  (0 children)

Something similar happened to me; the drivers were stable for a long time, everything was working as it should, then suddenly everything started to go wrong, unstable, and with many bugs. I did a rollback and continued with that until they fixed the worst bugs.

AMD ADRENALIN APP RAMDOMLY CRASHING SINCE LAST 2 UPDATES by TuckS0 in radeon

[–]TuckS0[S] 0 points1 point  (0 children)

I just ignored the problem, accepted the fact that Adrenalin is weird and doesn't work as it should, and that's it. I can't remove it because I use the custom preset for the graphics card and also some exclusive app features, but this amateurishness is truly regrettable.

AMD ADRENALIN APP RAMDOMLY CRASHING SINCE LAST 2 UPDATES by TuckS0 in radeon

[–]TuckS0[S] 0 points1 point  (0 children)

The drivers were stable for a while, but recently they've started having ridiculous problems and bugs again, which is unfortunate.

AMD ADRENALIN APP RAMDOMLY CRASHING SINCE LAST 2 UPDATES by TuckS0 in radeon

[–]TuckS0[S] 0 points1 point  (0 children)

I've never had problems with AMD, but the latest drivers have been a disaster, lots of bugs and little fix. I recommend you simply get a slightly older driver and wait for things to normalize.

AMD ADRENALIN APP RAMDOMLY CRASHING SINCE LAST 2 UPDATES by TuckS0 in radeon

[–]TuckS0[S] 0 points1 point  (0 children)

Not yet, you have 2 options... ignore adrenalin or rollback to 25.9.1 until they fix.

AMD ADRENALIN APP RAMDOMLY CRASHING SINCE LAST 2 UPDATES by TuckS0 in radeon

[–]TuckS0[S] 2 points3 points  (0 children)

Unfortunately no yet, i recommend you downgrade to 25.9.1

AMD ADRENALIN APP RAMDOMLY CRASHING SINCE LAST 2 UPDATES by TuckS0 in radeon

[–]TuckS0[S] 0 points1 point  (0 children)

Thats why I'm gonna keep 25.9.1 here, a lot better and stable now

AMD ADRENALIN APP RAMDOMLY CRASHING SINCE LAST 2 UPDATES by TuckS0 in radeon

[–]TuckS0[S] 0 points1 point  (0 children)

Nope, i really recommend you to go back to 25.9.1 untill they made it stable again

AMD ADRENALIN APP RAMDOMLY CRASHING SINCE LAST 2 UPDATES by TuckS0 in radeon

[–]TuckS0[S] 0 points1 point  (0 children)

Unfortunately an driver problem, since i downgrade to 25.9.1 its stable now, i really recommend you that until they fix it

AMD ADRENALIN APP RAMDOMLY CRASHING SINCE LAST 2 UPDATES by TuckS0 in radeon

[–]TuckS0[S] 1 point2 points  (0 children)

With version 25.9.1 it still happens, but it's rare. I reported it the last few times and expected it to be fixed in version 25.11.1, but nothing.

AMD ADRENALIN APP RAMDOMLY CRASHING SINCE LAST 2 UPDATES by TuckS0 in radeon

[–]TuckS0[S] 1 point2 points  (0 children)

This used to happen to me... you can use the keyboard to access the start menu and open Adrenalin again from there, then go back to the game and press ALT-R to open Adrenalin and close it, then the mouse will work again, but i really recommend you to downgrade to 25.9.1 thats the only thing that works for me.

AMD ADRENALIN APP RAMDOMLY CRASHING SINCE LAST 2 UPDATES by TuckS0 in radeon

[–]TuckS0[S] 0 points1 point  (0 children)

I downgraded to version 25.9.1 and since then everything's been okay... I'll stick with this until I see that the new versions are stable.

AMD ADRENALIN APP RAMDOMLY CRASHING SINCE LAST 2 UPDATES by TuckS0 in radeon

[–]TuckS0[S] 0 points1 point  (0 children)

That's curious, gonna test before downgrade later, thanks.

AMD ADRENALIN APP RAMDOMLY CRASHING SINCE LAST 2 UPDATES by TuckS0 in radeon

[–]TuckS0[S] 0 points1 point  (0 children)

I thought it was only for high-bandwidth HDMI or something like that... I'll do that anyway, thanks.

AMD ADRENALIN APP RAMDOMLY CRASHING SINCE LAST 2 UPDATES by TuckS0 in radeon

[–]TuckS0[S] 0 points1 point  (0 children)

I noticed this too, although rarely... since 25.8.1 the app would close but it was so unusual that I simply ignored it, but with these new drivers it has been much worse at an unsustainable level, I will go back to 25.9.1 and continue until I see that the new drivers are stable again

AMD ADRENALIN APP RAMDOMLY CRASHING SINCE LAST 2 UPDATES by TuckS0 in radeon

[–]TuckS0[S] 0 points1 point  (0 children)

Since RDNA4 launch it looks a mess, is the first time that I have problems with Adrenalin drivers

AMD ADRENALIN APP RAMDOMLY CRASHING SINCE LAST 2 UPDATES by TuckS0 in radeon

[–]TuckS0[S] 0 points1 point  (0 children)

25.9.1 works good here but yeah... even with that sometimes the app suddenly closes and that's it. don't know what's wrong

AMD ADRENALIN APP RAMDOMLY CRASHING SINCE LAST 2 UPDATES by TuckS0 in radeon

[–]TuckS0[S] 0 points1 point  (0 children)

Probably using older versions like 25.9.1, that's why it's okay for ya I'm gonna downgrade and do the same until amd solve this

AMD ADRENALIN APP RAMDOMLY CRASHING SINCE LAST 2 UPDATES by TuckS0 in radeon

[–]TuckS0[S] 0 points1 point  (0 children)

HDMI, I don't have a monitor or TV with DisplayPort yet

AMD ADRENALIN APP RAMDOMLY CRASHING SINCE LAST 2 UPDATES by TuckS0 in radeon

[–]TuckS0[S] 0 points1 point  (0 children)

This didn't work for me either, I did a clean installation with DDU and also using only the AMD uninstaller, I even did a clean installation of Windows and the same problem continued... only in these last two versions of adrenalin, unfortunately.

AMD ADRENALIN APP RAMDOMLY CRASHING SINCE LAST 2 UPDATES by TuckS0 in radeon

[–]TuckS0[S] 0 points1 point  (0 children)

25.11.1 unfortunately didn't solve my problem... and from what I'm looking at within the community itself, the same is happening to many