AMD formally addresses rare driver bug suspected of bricking Windows installations

Jimmy2x

Posts: 238   +29
Staff
Recap: AMD graphics card users have been reporting instances of driver installations completely bricking their Windows installs since mid-February. Despite the reports popping up on several social media outlets and forums, no official statement regarding the issue was ever made. AMD has now stepped forward and admitted that they've been able to reproduce the issue, identifying the Adrenalin driver package's "Factory Reset" option as the main issue.

The issue, which was originally reported earlier this year, was suspected to be a bug in the recent Adrenalin 23.2.1 driver package. AMD users who were unfortunate enough to encounter the issue would attempt to install the drivers, only to be met with an inaccessible boot drive error upon restart. Once encountered, affected users had two choices: attempt to restore to an earlier restore point, or completely reinstall Windows.

PCWorld editor Brad Chacos has been investigating the issue and working closely with AMD to identify and resolve it since the first reports trickled in. In a recent article, Chacos reported that AMD formally acknowledged the issue, discovering a flaw that could result in the inaccessible boot scenario when using the software's "Factory Reset" option during driver installation.

"We have reproduced an issue that can occur in an extremely small number of instances if a PC update occurs during the installation of AMD Software: Adrenalin Edition, and we are actively investigating. We recommend users ensure all system updates are applied or paused before installing the driver, and that the "Factory Reset" option is unchecked during the AMD driver installation process. We are committed to resolve issues as quickly as possible and strongly encourage users to submit issues with AMD Software: Adrenalin Edition via the Bug Report Tool."

According to the article, AMD is actively investigating the issue, which has been found to be extremely rare and hard to reproduce. Regardless of how rare it may be, the potential for a botched operating system installation and loss of data is never a promising possibility. Fortunately, there's a very easy workaround: simply don't check the "Factory Reset" box during the Adrenalin installation process.

While many users may never check the feature's box, there are a number who use it to clear old data and ensure a clean driver installation. All users should exercise caution when using the "Factory Reset" feature until a fix is implemented. Those who use it to perform a clean installation and clear any legacy driver files can fall back to another well-known graphics driver removal tool, Display Driver Uninstalller (DDU). The program is available for Windows 7 through to Windows 11 and can be used to remove all traces of AMD, Nvidia, or Intel graphics drivers.

The bug is extremely rare, and many users (myself included) have installed the latest driver packages using the reset feature without issue. That doesn't mean it doesn't exist, and ensuring the "Factory Reset" box is unchecked is an extremely easy step to ensure you don't become one of the affected users before AMD can remediate the issue.

Permalink to story.

 
This reminds me of my ATI X1900, instead of installing the new video driver I would better install a fresh Windows and then the GPU driver. If I just upgrade or uninstall old and install new then Windows enter a boot loop with a BSOD.

Well done Microsoft and AMD for another WHQL driver.
 
This reminds me of my ATI X1900, instead of installing the new video driver I would better install a fresh Windows and then the GPU driver. If I just upgrade or uninstall old and install new then Windows enter a boot loop with a BSOD.

Well done Microsoft and AMD for another WHQL driver.

I remember this same issue in the mid-2000's...probably a Radeon 9700 back then. Every driver upgrade was a crapshoot.
 
Way to go AMD another notch in your belt.
Nobody believes in QC anymore, just throw the garbage out there and let the end user have to deal with it?
Not very smart
You ask top dollar for your product
To much for us to ask for our moneys worth?
 
I've got nothing. Quality control is an afterthought for everyone these days. AMD drivers blow up the operating system; Nvidia has a new cable that can set their RTX on fire; Intel has an Ethernet adapter that times out. And then you have a bunch of games that get released and fixed on the fly. It's all about making that stock look appetizing for the shareholders, no matter what the cost.
 
So the answer is: don't update your drivers with the Factory Reset option if Windows is also updating in the background? Um, why doesn't Windows lock out all installs/updates while the OS is updating? Macs do this, which is an annoyance when you just want to get something simple installed, but I guess there's a reason.
 
This reminds me of my ATI X1900, instead of installing the new video driver I would better install a fresh Windows and then the GPU driver. If I just upgrade or uninstall old and install new then Windows enter a boot loop with a BSOD.

Well done Microsoft and AMD for another WHQL driver.
I was planning to do the same after installing my 6700xt coming today.
 
Happened to me, wanted a fresh install of the AMD driver on a new harddrive since it needs to store cache files on the main windows installation, it ended up with windows not recognizing the driver , tried to reinstall it multiple ways and it was not working, did new Windows 11 install
 
My BIOS is flickering when I just installed the new 6700xt. Happened on DP, tried hdmi nothing worked. GPU removed, installing new windows with onboard video. Will reseat gpu and install AMD drivers. Let's see what happens.
 
New windows installed, GPU reseated still the same issue. Rolled back BIOS still same. Looks like I have to return it. What a waste of time lol.
 
Omega drivers were really good ! I heard somebody continued to this day with custom drivers but I forgot the name :/
NimeZ drivers, they add the polish that AMD tends to miss and also the option to stick on older kernel drivers while using newer driver features which saves a lot of headaches when newer drivers releases breaks a bunch of stuff while you just want the add features.
 
Happened to me, wanted a fresh install of the AMD driver on a new harddrive since it needs to store cache files on the main windows installation, it ended up with windows not recognizing the driver , tried to reinstall it multiple ways and it was not working, did new Windows 11 install

Did you try using DDU in safe mode (with no networking) to uninstall old drivers, rebooting with Internet disconnected and then install latest Adrenaline drivers leaving reset unchecked? Disconnecting means Windows won't try and install it's own driver when you reboot.

I've had zero issues using this approach.
 
I've got nothing. Quality control is an afterthought for everyone these days. AMD drivers blow up the operating system; Nvidia has a new cable that can set their RTX on fire; Intel has an Ethernet adapter that times out. And then you have a bunch of games that get released and fixed on the fly. It's all about making that stock look appetizing for the shareholders, no matter what the cost.
Check out the Sinclair QL, the Twiggy floppy, the IBM DeathStar, the Zip drive, the NeXT magneto-optical drive, Windows ME, Windows 1.x – 2.x, the Mac Performa 5200, the Apple III (drop the computer to re-seat the chips after it overheats... sorry about the clock not working, though!), Windows 98 (want to get all those Windows updates to install? Ha!), cassette storage for home computers, the Coleco ADAM, Windows 95 (it's so fun getting back to the desktop, again and again and again), Netscape 2, the Apple puck mouse, Microsoft Office 6 on the Mac, the CoCo non-centering joysticks, the Intel 80186, and the Atari 5200 non-centering joysticks. The Mac Plus couldn't have its RAM fully expanded because it would overheat and its power supply was too weak. The Apple Lisa shipped with an underpowered power supply. The G4 Cube cracked and cooked hard drives. At least one of the iMacs cooked hard drives. Windows 3.x had a bad UI. The first Mac was so pathetic that it couldn't support a hard drive, had only 128K of non-expandable RAM, and was substituted with an unobtainable 512K model when Jobs 'demoed the first Mac' to the tech press. The 1.13 Ghz Pentium III...

There has been a lot of bad and poor tech over the years. Of that list, I have a soft spot for Netscape 2 because at least it was the best browser at the time, despite constant crashes. One of the most successful CPUs in history, the Motorola 68000, had a severe bug that prevented it from being able to work with virtual memory and it didn't have a decent MMU (which were external in those days). Another example is the CD and its successors (except for DVD-RAM) which didn't have protective shells. That was particularly inexcusable with consoles aimed at kids. Of all of those formats, the one that was done right, DVD-RAM, flopped. Humanity likes to reward mediocrity.
 
QC is often just a patch on a bad development process. QC doesn’t, shouldn’t, fix anything. It should provide a rough metric of quality. I suspect AMD ‘found’ the issue because some engineer just wouldn’t let it go, kept chasing down every occurrence of the issue (I would do this, ultimately find a solution, people would ask why I spent so much time on such a ‘small’ and ‘old’ problem).

Doing much more Linux than Windows these days, stories of the unnatural acts one must do to successfully install a Windows driver are humorous, except I used to do such things and I too thought I was clever with such solutions.
 
One of the most successful CPUs in history, the Motorola 68000, had a severe bug that prevented it from being able to work with virtual memory and it didn't have a decent MMU (which were external in those days).
The Amiga chip? I'm confused, didn't the Amiga specifically have external RAM upgrades available, or am I misunderstanding "virtual memory" here?
 
Back