Radeon Driver Bug Corrupts Windows, AMD Shares Fix

Radeon GPUs
Radeon GPUs (Image credit: AMD)

It takes time to reproduce bugs and find solutions, especially rare ones. However, after a couple of weeks of investigation, AMD finally found a solution for Radeon graphics card owners who faced an Adrenalin WHQL driver bug that corrupted their systems.

AMD's Adrenalin 23.2.1 driver delivered decent performance improvements and new features to users. But, lamentably, the driver also brought some users headaches since it bricked their Windows installation. 

The issue isn't limited to the Adrenalin 23.2.1 driver, either. Brad Chacos, the executive editor at PCWorld, encountered the same bug even with the latest Adrenalin 23.2.2 driver that recently left AMD's oven. Chacos worked hand-in-hand with AMD engineers to discover the root cause of the problem and a temporary workaround.

"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," one AMD spokesperson told PCWorld.

Judging from AMD's statement, the software has a flaw that appears to conflict with Windows Update. However, you can argue that it's a Windows bug, not an AMD bug. Windows shouldn't be updating a driver of any kind if there's a current installation in progress. It has been an issue with all sorts of other drivers for quite some time. It's the reason why some users prefer to disable automatic driver updates.

In the meantime, AMD has advised users not to use the "Factory Reset" option while installing the Adrenalin drivers. The aforementioned option removes all traces of the previously installed driver, similar to what popular third-party Display Driver Uninstaller (DDU) does, and requires a restart. Our theory is that Windows Update simultaneously installs the Adrenalin driver during the standard driver installation because the system momentarily lacks a display driver when restarted.

Adrenalin Software (Image credit: AMD)

It's good practice to always do a clean install of your display drivers with every update. However, the feature is currently borked on AMD's Adrenalin drivers, so heed the company's advice and make sure you untick the "Factory Reset" option before installation. Also, for good measure, disable or pause your Windows updates before installing the Adrenalin drivers. AMD believes it's an uncommon bug, but we don't recommend taking any chances until the chipmaker provides a final solution.

DDU, for example, has a specific option that prevents Windows Update from downloading drivers when the program is running. AMD could adopt a similar strategy to ensure that Windows Update and the Adrenalin software don't perform a parallel installation.

Windows recovery mode is the answer for those unlucky users that have already gone down this road. However, it may not be easy to get there.

According to Chacos, AMD recommended hitting the power button to force Windows into automatic recovery. It's easier said than done, though. The trick is to hit the power button right after the BIOS options disappear but before the Windows circle. Unfortunately, Chacos noted that pushing the power button during the BIOS options would turn off the system and at the Windows spinning circle only lead to a black screen. It took Chacos 15 attempts to succeed, so perseverance is key to recovering your system.

If you're not the type to keep regular data backups, you should probably do so before installing AMD's latest Adrenalin drivers. It's a rare bug, and unticking "Factory Reset" seemingly prevents it from happening, but do you want to take that chance?

Zhiye Liu
RAM Reviewer and News Editor

Zhiye Liu is a Freelance News Writer at Tom’s Hardware US. Although he loves everything that’s hardware, he has a soft spot for CPUs, GPUs, and RAM.

  • PlaneInTheSky


    The fact this is AMD's WHQL-certified driver is even more insane.

    A WHQL driver bricking Windows and causing people to lose their data. If any other company did this, you wouldn't hear the end of it. But this is AMD, supported by a throng of fans who think this is acceptable.

    Terrible drivers is why I stopped buying AMD GPU.
    Reply
  • _deXter_
    PlaneInTheSky said:
    A WQHL driver bricking Windows and causing people to lose their data. If any other company did this, you wouldn't hear the end of it. But this is AMD, supported by a throng of fans who think this is acceptable.

    Terrible drivers is why I stopped buying AMD GPU.

    Some of us don't use or care about Windows. AMD's open-source drivers on Linux are top notch and I haven't had any issues with them, unlike nVidia, which still doesn't play well with Wayland and has a chance to break with every kernel update.

    Their excellent Linux support is why I continue buying AMD GPU.
    Reply
  • TechieTwo
    PlaneInTheSky said:


    The fact this is AMD's WQHL-certified driver is even more insane.

    A WQHL driver bricking Windows and causing people to lose their data. If any other company did this, you wouldn't hear the end of it. But this is AMD, supported by a throng of fans who think this is acceptable.

    Terrible drivers is why I stopped buying AMD GPU.

    As the story notes this could actually be considered a Windows bug more so than the AMD driver - which functions properly but is being corrupted by Windows trying to load two video drivers at the same time.
    Reply
  • USAFRet
    PlaneInTheSky said:
    A WQHL driver bricking Windows and causing people to lose their data.
    While the driver issue is absolutely bad and should not happen, 'lose their data' or "now I have to set up Windows again from scratch' should not be a thing. At all. Ever.

    This is what actual backups are for.
    Reply
  • Amdlova
    When I have a AMD graphics in the system first I try to find in Google what it's the best version... because the new shine drivers come with lot of bugs. The amd driver is pain in the ... and yes I have systems locked up because the amd graphics.
    Reply
  • greenreaper
    I would argue that if it is WHQL-certified, this is something that Microsoft should probably have caught. That's part of what you pay for when they qualify it. Maybe they need to add Windows Update to their testing matrix.
    Reply
  • GeorgeLY
    _deXter_ said:
    Some of us don't use or care about Windows. AMD's open-source drivers on Linux are top notch and I haven't had any issues with them, unlike nVidia, which still doesn't play well with Wayland and has a chance to break with every kernel update.

    Their excellent Linux support is why I continue buying AMD GPU.
    Well, you're almost right. The open-source driver for Linux is excellent, but it does not prevent other parts breaking. There was introduced instability on integrated AMD graphics in Linux kernel 5.19 that caused crashes once an hour or so, that fortunately got fixed in kernel 6.1. Unfortunately though Ubuntu LTS recently updated to kernel 5.19 which means a lot of people that wouldn't be able to troubleshoot the cause will blame it on the driver.
    Reply
  • TechieTwo said:
    As the story notes this could actually be considered a Windows bug more so than the AMD driver - which functions properly but is being corrupted by Windows trying to load two video drivers at the same time.
    I agree. I'm surprised concurrent installations is a thing in Windows. It should not be possible. In Linux when a program has access to install database, there's a file lock in place and nothing else can do modifications. It might be annoying if you leave something running in background, but it's a well thought safety feature which should be standard in Windows.
    Reply
  • cfbcfb
    It's a windows problem and it's been a long standing issue with drivers, requiring turning off auto updates?

    Not in my experience. I've had a bunch of machines on windows autoupdate with all sorts of drivers and I can't recall the last time I had an issue with that. Years.

    What I have had is at least 3 times that AMD drivers gave me problems, and they're all in the past 12-15 months. The 'finewine' has turned to vinegar.
    Reply
  • drivinfast247
    So the title should read: "Windows bug allows AMD Adrenaline to corrupt install".
    Reply