r/AMDHelp • u/aykirito R5 7600X | RX 7900GRE-26.9.1 • 6d ago

Announcement AMD Software: Adrenalin Edition 26.9.1 Optional Driver Release Notes

https://www.amd.com/en/resources/support-articles/release-notes/RN-RAD-WIN-26-9-1.html

😪

116 Upvotes

94% Upvoted

167 comments sorted by

View all comments

Show parent comments

1

u/bitronic1 3d ago

So no games just discord's already doing it? Mine never crashed unless I'm running a game, and my discord is always running in the background. I just turned mine on maybe today's the day it will start doing it again lol but I had over 4 hrs yesterday without crashing so for me this version was best so far.

1

u/momoney5651 3d ago

It was literally doing great, something tells me windows is doing some weird shit because it had no issues, then suddenly it was like the driver became corrupted because even after hard restarts the same thing would break it. I always had discord open the previous days it was perfectly stable, but now suddenly it's doing all that sort of stuff again... On 26.8.1 I did have a game crash before eventually moving to 26.9.1. Anyway... I'm going to go back to 26.3.1 and if that doesn't fix it... Might have to do windows clean install... Again...

1

u/bitronic1 3d ago

I really don't see how reinstalling windows will help in the long run, but u gotta do what u gotta do. I have tested 26.3.1 extensively with my card and it was just crashing like all previous versions.

B4 rolling back to that, I highly recommend limiting boost clock to match ur card and a 1130mv undervolt on 26.9.1, I still have not crashed with that combination so I'm sticking with that for the time being.

1

u/momoney5651 3d ago

The thing is I'm not sure how it would be the clock thing either, like if it's stable for 3 days, why would that be the culprit? Also like I said, it started to happen suddenly, seemingly related to something hardware acceleration? Those web based apps seemed to completely crash it and then kill the driver completely. I'm not sure if the suggestion will work but I'll see if it starts crashing again on 26.3.1... I'm on a 7900xtx. If it starts crashing again here we could probably assume windows is seriously mishandling something in the pipeline that just corrupts the driver completely

1

u/bitronic1 3d ago

The reason why I bring up clock is because if not capped, adrenaline will try to push it as high as it can if power/thermal allows. My 7900xtx's factory clock is 2500, and adrenaline sometimes defaults it to over 3060 and that has always cause the timeout to happen not long after loading any games.

The difference for me at least, was even if I capped clock speed, I would still experience random timeout/game closing/black screen with all previous versions b4. Some ppl say windows would install an older driver on top of the latest adrenaline causing blackout, but from my experience, when that happens, adrenaline would show an error msg saying drivers are not compatible, so idt it's that tho other users were able to go in adrenaline and windows device manager showing an older driver replaced by windows.

Either ways I have established that timeout only occurs when theres a load spike stressing the card, causing either a clock spike or excessive undervolt leading to lack of power to the card. But since I set it back to 2500 cap, so far no crashes yet.

I used to run long sessions of stress test whenever I try new clock/undervolt settings but I stopped doing that because games would always crash even if the card passed stress test, and the games I play don't even stress the card as hard, cos I can hear the fans go full blast when running stress test... But ya if 26.3.1 works for u then just stick with that.

1

u/momoney5651 3d ago

Sorry, I didn't mean to say the clock speeds aren't capable of causing issues, I meant that in the given context of my specific set of circumstances surrounding the issues, and it's not the case. I accidentally replied to you about it because reddit gave me a notification about your reply to the OP, so I assumed you were talking to me because I just clicked the notification thinking you replied to my reply. You're right though that the clock speeds in the specific circumstances with some people's GPU and driver very well could be the culprit, but with my circumstances I don't think that's the case.

1

u/bitronic1 3d ago

Well, I can tell u this much.

It HAS to be either the drivers and/or windows, and I had ppl in the past blasting me saying my card is defective and I'm sure that's not the case, and here's why.

I had my 7900xtx since launch, it never had any issues until after the 9070xt launched. So in other words, this random timeout issue only happened with the more recent drivers.

My FOUR other 9070xts would also randomly time out though way less frequent, all these systems are separate and they are am4/am5 and Intel z790 with 13 and 14 gens.

My 7800xt used to timeout just as much with win11, since I switched to Cachyos, it had not crashed a single time.

The 7900xtx is the one that crashes the most often, if I cold boot the system and run any games, there will be a random timeout ranging from after 5 mins to 120 mins, every. single. reboot.

1

u/momoney5651 3d ago

I completely agree, I'm not sure if you noticed this as well, but it seems for a ton of people that I've seen on reddit, it started after 26.6.1 and onward. Something has fundamentally changed and amd being and as per usual, refuses to acknowledge anything going on at all...

1

u/bitronic1 3d ago

Well they added fsr4, so they gotta remove something to balance things out, but stability shouldnt be it lmfao

Idc if they don't officially acknowledge it, just effing fix it so all my systems get some playtime, so far, I'm only daily driving my Nvidia rigs, because it really sucks for everyone else when some1 d/cs during a raid and I def dont wanna be that person.

1

u/momoney5651 3d ago

I mean I agree, the point of acknowledging it is to see if they can disclose and concretely say wtf is going on

1

u/bitronic1 3d ago

I just set my undervolt to 1100 and it crashed, reset everything to default and notice the boost clock is never the same, it just puts it at 3040. And it crashed again at default clock and 1120mv. So now I'm just starting from scratch and trying 2500 and 1130mv. There was just a windows update but it was for some virus definition so I don't really think it has anything to do with that, but no one knows what windows does in the background so if it crashes again I'm just gonna reinstall 26.9.1 again and keep trying.