• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
  • The forums have been upgraded with support for dark mode. By default it will follow the setting on your system/browser. You may override it by scrolling to the end of the page and clicking the gears icon.

AMD Software Adrenalin 23.2.1 Released: Finally Updates for RX 6000 Series and Older

As far as I've been able to read, people are complaining about bootloops after windows starts loading. DDU on Safe Mode is enough to fix it, and it could be just caused by a screwed up installer.

According to speculation/what people said, it only happened when updating from Adrenalin, standalone upgrade works (and I did it). The upgrade doesn't show in Adrenalin now. Do it manually and you're fine, otherwise just enter safe mode and DDU away.

No, nothing breaks on your PC. It's a half-way screwed up driver caused by a broken installer delivered by Adrenaline that BSODs in a loop.
 
Drivers can't make changes to the bios.
F.U.D
 
From the article itself

"In response to a Twitter announcement from AMD about the newly released driver update, a few users jumped into the replies to complain that the updates kept them from booting into Windows.


While it's not unusual for a driver update to cause system issues, it is rare for a driver to actually corrupt an operating system. We haven't confirmed the driver issue ourselves yet, but the official Twitter account for frame capture tool CapFrameX tweeted out a possible cause for the issue, indicating that the driver might be making changes to the system BIOS.



CapFrameX also points to a forum post on German tech site ComputerBase about the issue, which other users on the site appear to confirm as well. TechRadar has reached out to AMD about the reports and will update this post if and when we hear back from the company."

If it's an issue only on windows 11, to me that signals it's more likely the operating system is at fault.

Windows is already notorious for auto-installing AMD GPU drivers when the end user already had drivers installed, causing various issues on the user's end.

I recently upgraded to windows 11 and I will say the OS still needs a lot more time in the oven. There are still some bugs and the new new settings app is missing a lot of options, some of them very basic like being able to set how apps are grouped on the taskbar.

Also, I'm not sure I'd qualify this as news. It's an article based on a few twitter replies. There is no journalism here, only the intent to get clicks same as the last "AMD driver IS BRICKING CARDS OMG Click NOW" debacle.

I'm going to laugh when these rumor websites are replaced by AI because gathering tweets on a particular subject and writing a summary is something that is now well within that purview.
 
The whole rumor is indeed completely baseless. Honestly you could chuck it either to Windows Update partially replacing driver files, or the update delivered by Adrenalin being partially corrupt. Either of those doesn't screw up your system, and anyone half competent can fix it by literally just using Safe Mode.

No, windows didn't get corrupted. No, your PC didn't break. Geez.

And specially no, a driver update doesn't change your BIOS settings. That's just insanity (or maybe not)

Sure, *something* went wrong that shouldn't have gone wrong, but the theories and fearmongering about it breaking everything and corrupting windows, bricking your entire computer and even changing bios settings.

We should just wait for official word on this. It might be specific configurations or Windows settings. Might even be an issue on Windows itself for all we know.
 
Last edited:
Why then do many have no issues at all?!.

I installed last night in as simple a way as possible, download then run.

It chose a clean install, not me, I did think that odd or different at least.

Two boots later, one to remove one to reinstall and all done.

So it's not corrupted.
It's not bricking all PCs

It's possibly affecting some configs because of something, but it's not a corrupt driver or everyone would see only turd with it wouldn't they.

I'm starting to wonder WTAF IS going on though.
 
Forgive him SquadAMD, for he knows not what he's done. Please do not nuke the Swamp and Donkey.

DemonicRyzen666 said:
Drivers can't make changes to the bios.
F.U.D
Click to expand...

AMD GPU drivers (well, Adrenalin) are capable of modifying the BIOS settings for AMD CPU overclocking. There was a previous issue with the drivers that could wipe out any PBO/CO settings you had made in the BIOS when Adrenalin shit the bed.
 
TheoneandonlyMrK said:
It's possibly affecting some configs because of something, but it's not a corrupt driver or everyone would see only turd with it wouldn't they.

I'm starting to wonder WTAF IS going on though.
Click to expand...
Some people said it happened after installing it from Adrenalin the hour it released and that it worked when they used the standalone installer. But yeah, I wouldn't really say it was corrupt or anything as a fact, just less insane speculation.

Installing it worked fine for me, too.

Super Firm Tofu said:
Forgive him SquadAMD, for he knows not what he's done. Please do not nuke the Swamp and Donkey.



AMD GPU drivers (well, Adrenalin) are capable of modifying the BIOS settings for AMD CPU overclocking. There was a previous issue with the drivers that could wipe out any PBO/CO settings you had made in the BIOS when Adrenalin shit the bed.
Click to expand...
That's because of Ryzen Master integration with the RM (AMDRyzenMasterDriver.sys, which controls PBO on the CPU if you set it on RM or Adrenalin) driver, though. Not directly changing BIOS settings.

It would be hilarious if THAT was the issue, but I doubt it.
 
Last edited:
Kodehawa said:
Some people said it happened after installing it from Adrenalin the hour it released and that it worked when they used the standalone installer. But yeah, I wouldn't really say it was corrupt or anything as a fact, just less insane speculation.

Installing it worked fine for me, too.



That's because of Ryzen Master integration with the RM driver, though. Not directly changing BIOS settings.

It would be hilarious if THAT was the issue, but I doubt it.
Click to expand...
Well, however you slice it, the default AMD drivers package has the ability to change the PBO settings in the BIOS.

I don't think there's any widespread issue either, but people need to be aware that 'software can't change bios setting from within Windows' isn't true.
 
Vya Domus said:
Here we go with the bs claims again, just like those drivers causing GPU to explode.
Click to expand...

That specific thing is BS, but in the past AMD drivers have effectively bricked Windows 10 systems. A friend had a AMD APU laptop which wouldn't even boot into safe mode if the GPU drivers pushed by Windows 10 were installed, which they were, unless you blocked that driver, or did what I did and just disabled the GPU and let it use a generic driver. He basically only used it for mail and he would set a weird resolution anyway so he didn't notice. And it was a driver problem because some time later it would work as normal with correct drivers.
 
Last edited:
Kodehawa said:
Some people said it happened after installing it from Adrenalin the hour it released and that it worked when they used the standalone installer. But yeah, I wouldn't really say it was corrupt or anything as a fact, just less insane speculation.

Installing it worked fine for me, too.


That's because of Ryzen Master integration with the RM (AMDRyzenMasterDriver.sys, which controls PBO on the CPU if you set it on RM or Adrenalin) driver, though. Not directly changing BIOS settings.

It would be hilarious if THAT was the issue, but I doubt it.
Click to expand...
That's what I did let the driver DL and update the driver exactly how AMD prepped it sorry I thought I said as much.
 
TheoneandonlyMrK said:
That's what I did let the driver DL and update the driver exactly how AMD prepped it sorry I thought I said as much.
Click to expand...
To be honest I think it could be whatever at this point. All we can really do is speculate, but its probably only on some specific scenarios.
 
I updated from within Adrenalin and it went just fine, used the "factory reset" option and cleared user settings. Screen flickered a few times, restarted, booted back up and finished no problemo.

Edit: Am on Win11 22H2
 
  • Up to 19% increase in performance for F1 2022 @ 4k, using AMD Software: Adrenalin Edition 23.2.1 on the Radeon ️ RX 6950XT GPU, versus the previous software driver version 22.11.2 RS-525
Click to expand...
Has anybody tested this claim yet? Even if it's specific to a certain scene, it should have some impact on the rest of the game and the rest of AMD's lineup.
That would put the 6900 XT ahead of the 3090 Ti and make the 6950 XT a match for the 4080 :eek:
Granted, AMD is underperforming a bit in this title, but 19 % is a wild claim
1676583729428.png
 
Something could have changed in the drivers from AMD website since their name now ends with "2023" after the pre-existing one. So, I wonder if that change fixes the installer problems some users reported. @W1zzard : Anyone from the staff that could upload the latest version to the TPU downloading server?

UPDATE: That filename doesn't exist now, they should have updated the initial one with the latest. Still, the download server might need to have the latest existing one.
 
Last edited:
StefanM said:
ComputerBase explains:
www.computerbase.de

AMD Adrenalin Radeon-Treiber Download

AMD Adrenalin (ehemals Crimson bzw. Catalyst) ist der Treiber für alle Radeon-Grafikkarten. Deutsch, Freeware, kostenloser Download!
www.computerbase.de www.computerbase.de
Click to expand...
Which in English says the only difference is that "reset to default" was, then wasn't checked, nothing else
 
Go and rerun your speedway/port royal benches! MOAR POINTZ!
 
Yep, upgraded from Nimez 23.1.2 to this driver, and it corrupted my Windows install.

4rnZrSP.jpg


Fun stuff, using Macrium Recovery as I type this to try and fix it.

Worst case scenario, I can recover from my weekly backups (latest one is 6 days old).

EDIT: And, Macrium didn't work. Thanks AMD! This is why backups are important.

EDIT 2: Retrying with Fast Boot disabled. This still seems like an unacceptable issue to me.

EDIT 3: Still doesn't work.

Alright, so I've learned a lesson to enable restore points I guess.

Restoring from my February 12th backup and will be staying on the latest NimeZ driver. I was wondering why they hadn't done 23.2.1 yet; guess this is why.

EDIT 4: Restored from the backup and everything is working now. Probably lost my BG3 save, but whatever.

I will not be using the official drivers in the future. NimeZ for the win.

I also cannot stress the importance of regular backups enough.

EDIT 5: Added picture of the recovery screen error code.
 
Last edited:
TheinsanegamerN said:
Fast Boot is notoriously buggy, causes all sorts of issues at work because windows 10 does NOT like going 7+ days without a reboot
Click to expand...
Restarting bypasses/resets fast boot and is normally all that's needed to fix any issues there


Otherwise i've found going into safe mode and leaving it, a method to get out of any fast boot related hiccups - even letting you do things like change between IDE/RAID/AHCI mode on older platforms if needed
 
sam_86314 said:
Yep, upgraded from Nimez 23.1.2 to this driver, and it corrupted my Windows install.

4rnZrSP.jpg


Fun stuff, using Macrium Recovery as I type this to try and fix it.

Worst case scenario, I can recover from my weekly backups (latest one is 6 days old).

EDIT: And, Macrium didn't work. Thanks AMD! This is why backups are important.

EDIT 2: Retrying with Fast Boot disabled. This still seems like an unacceptable issue to me.

EDIT 3: Still doesn't work.

Alright, so I've learned a lesson to enable restore points I guess.

Restoring from my February 12th backup and will be staying on the latest NimeZ driver. I was wondering why they hadn't done 23.2.1 yet; guess this is why.

EDIT 4: Restored from the backup and everything is working now. Probably lost my BG3 save, but whatever.

I will not be using the official drivers in the future. NimeZ for the win.

I also cannot stress the importance of regular backups enough.

EDIT 5: Added picture of the recovery screen error code.
Click to expand...
Do yourself a favor and don't use NimeZ drivers unless you have an older card, e.g. 5700, the only good thing it has is that the tessellation is disabled in the registry (off) and you can even run 3dmark without it considering the test invalid, that's where the performance increase comes from.
 
I can't possibly fathom how some people believe piously in those modded drivers... and blames AMD(!) for the issues it causes.
 
You must log in or register to reply here.
Back
Top