Radeon Driver Bug Corrupts Windows

[erek]

AMD has a fix

“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?”

Source: https://www.tomshardware.com/news/amd-driver-bug-corrupts-windows

 

[uOpt]

Again?

 

[OutOfPhase]

It will turn into fine wine.

 

[Meeho]

"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."

 

[ZeroBarrier]

"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."

So it only happens to their drivers? And they want to pass the buck onto Windows? I hope users don't accept that answer and hold them to the same standard they hold other companies when such errors occur. But who am I kidding, people will just give AMD another pass.

 

[Lakados]

I

So it only happens to their drivers? And they want to pass the buck onto Windows? I hope users don't accept that answer and hold them to the same standard they hold other companies when such errors occur. But who am I kidding, people will just give AMD another pass.

AMDs actual installers have been garbage for a long time, with older drivers you can trigger the “Black Screen” bugs if you install the drivers while windows is doing updates on a fresh install. Which is why it is recommended to install the AMD graphics drivers after all the system drivers are installed and the OS is fully updated.

 

[Ebernanut]

Again?

No it's a rehash of what was already discussed a couple of weeks ago.

 

[rinaldo00]

So it only happens to their drivers? And they want to pass the buck onto Windows? I hope users don't accept that answer and hold them to the same standard they hold other companies when such errors occur. But who am I kidding, people will just give AMD another pass.

I am not here to defend AMD but in the quote that you quoted in your reply says that it happens to others. Here is the quote again

"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."

 

[ZeroBarrier]

I am not here to defend AMD but in the quote that you quoted in your reply says that it happens to others. Here is the quote again

"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."

And yet you never hear of this happening with other drivers. Sounds to me AMDs statement is full of shit.

 

[vonviener]

Windows is always trying to update drivers in the background for unknown devices, and occasionally already known/installed devices. It can cause issues for sure. I always disconnect from wifi/ethernet before doing any parts swapping. Sometimes windows will install basic drivers that are already packaged in the os even if disconnected from the internet. Just let it do its thing then install over the ms basic drivers. I have had issues with MS updating chipset, ethernet, wifi, nvidia, amd, specialty laptop drivers, and storage drivers in the past. Usually they don't brick the whole OS though, on rare occasion I do have to do a clean install to fix it.

 

[NightReaver]

And yet you never hear of this happening with other drivers. Sounds to me AMDs statement is full of shit.

Idk, sounds like some "user error". Looking at vonviener 's post, people should learn better driver install practices.

 

[rinaldo00]

And yet you never hear of this happening with other drivers. Sounds to me AMDs statement is full of shit.

That statement comes from the article not AMD.

 

[Marees]

No it's a rehash of what was already discussed a couple of weeks ago.

It appears the same issue. The difference this time is it happened to a PC World editor & AMD worked with him to isolate the issue.

 

[Twisted Kidney]

Between AMD and Microsoft it's like nobody wants Windows to work.

 

[Verado]

This actually happened to my new lenovo yoga slim 7 pro x first few hours of use.
Had spend the afternoon downloading recovery media through lenovos cumbersome system, that costs you a few hours regardless of your connection speed.
I was not amused.

 

[lopoetve]

And yet you never hear of this happening with other drivers. Sounds to me AMDs statement is full of shit.

Had it happen with Nvidia drivers and an Intel NIC driver.

Turn off windows driver updates - problem solved (also fixes a lot of OTHER issues I've had).

 

[PC-Only]

Turn off windows driver updates - problem solved (also fixes a lot of OTHER issues I've had).

Are you talking about the Optional updates that you have to manually choose (and are not included in auto updates) or do you mean turn off all auto windows updates? And if you turn off auto windows updates, how do you avoid getting the Preview updates? I stopped manually forcing windows updates when I found out that a manual update check also forces unstable/buggy Preview updates to download/install. Auto updates do not include the Preview updates.

 

[pendragon1]

ive had windows do whats described but it didnt break anything, just forced its drivers in while amd installer was running. its one of the reasons i still ddu first, to ensure the "disable windows driver updates" is set.

 

[pendragon1]

Are you talking about the Optional updates that you have to manually choose (and are not included in auto updates) or do you mean turn off all auto windows updates? And if you turn off auto windows updates, how do you avoid getting the Preview updates? I stopped manually forcing windows updates when I found out that a manual update check also forces unstable/buggy Preview updates to download/install. Auto updates do not include the Preview updates.

no, its an advanced system setting that likes to re-enable itself.

 

[jlbenedict]

 

[lopoetve]

Are you talking about the Optional updates that you have to manually choose (and are not included in auto updates) or do you mean turn off all auto windows updates? And if you turn off auto windows updates, how do you avoid getting the Preview updates? I stopped manually forcing windows updates when I found out that a manual update check also forces unstable/buggy Preview updates to download/install. Auto updates do not include the Preview updates.

I disable driver updates, which is separate from normal windows updates. I do have a few systems with auto-reboot disabled (because they tend to be running background tasks) - I just hit them every friday afternoon.

 

[Furious_Styles]

View attachment 554026

This is the way. Helps keep problems to a minimum.

 

[Armenius]

View attachment 554026

This only works on the Pro version of Windows, by the way. There is a way to install and enable the Group Policy Editor on Home versions, but I can't vouch for it since I've always used Pro since Vista. I'd imagine you would be missing a lot of options either way.

 

[lopoetve]

This only works on the Pro version of Windows, by the way. There is a way to install and enable the Group Policy Editor on Home versions, but I can't vouch for it since I've always used Pro since Vista. I'd imagine you would be missing a lot of options either way.

Can still disable driver updates via the control panel. I have to look it up every time though.

 

[Lakados]

This only works on the Pro version of Windows, by the way. There is a way to install and enable the Group Policy Editor on Home versions, but I can't vouch for it since I've always used Pro since Vista. I'd imagine you would be missing a lot of options either way.

Easy work around is to flag the connection as “Metered”, windows will not automatically update on a metered connection unless you also enable “update over metered connections”.
Microsoft wouldn’t dare change that arrangement intentionally the lawsuits would be astounding.

 

[jlbenedict]

Easy work around is to flag the connection as “Metered”, windows will not automatically update on a metered connection unless you also enable “update over metered connections”.
Microsoft wouldn’t dare change that arrangement intentionally the lawsuits would be astounding.

Cool trick. (have to keep that in my back pocket)

 

[crazycrave]

Is this limited to RX 7000 cards? I have ran both drivers on my RX 6700 without any issue and used factory reset both times on Window 11.

I don't use DDU on my AMD stuff, just use AMD's built in driver remove tool = C:\Program Files\AMD\CIM\Bin64\AMDCleanupUtility.exe

 

[Mega6]

Is this limited to RX 7000 cards? I have ran both drivers on my RX 6700 without any issue and used factory reset both times on Window 11.

I don't use DDU on my AMD stuff, just use AMD's built in driver remove tool = C:\Program Files\AMD\CIM\Bin64\AMDCleanupUtility.exe

That's what I use too instead of DDU. Works well.

Got mine here - https://www.amd.com/en/support/kb/faq/gpu-601

 

[socK]

It will turn into fine wine.

turned into vinegar this time

 

[Marees]

Is this limited to RX 7000 cards? I have ran both drivers on my RX 6700 without any issue and used factory reset both times on Window 11.

I don't use DDU on my AMD stuff, just use AMD's built in driver remove tool = C:\Program Files\AMD\CIM\Bin64\AMDCleanupUtility.exe

I believe the issue was first reported for the Rx 6xxx series cards. So it impacts all cards. Don't update amd drivers until & unless windows has completed its update

 

[Marees]

Is this limited to RX 7000 cards? I have ran both drivers on my RX 6700 without any issue and used factory reset both times on Window 11.

I don't use DDU on my AMD stuff, just use AMD's built in driver remove tool = C:\Program Files\AMD\CIM\Bin64\AMDCleanupUtility.exe

This issue was reported last month in 6xxx thread

So fun side effect for AMD CPU users who are also using a 6000 series GPU with these drivers, it may modify your boot order, so lots of users reporting an inability to boot their systems after the drivers install as well as lots of reports of Windows installs being corrupted after changing the boot order back requiring a full OS reinstall.
So be safe out there.

 

[Mega6]

Unplug the network. Uninstall and clean the driver in SAFE MODE. Reboot, install driver. Reboot. Plug in network. I literally just did this three days ago. Because - yeah I could see the windows driver updating by flashing the screen earlier. Good advice on disabling driver updates, I usually have that off, prob got re-enabled on an OS update. Group policy fixed that. Just kind of ironic that a dipshit compute "tech" writer borks his box, gets help and then writes this whole article to declare how much of a non-computer person he is.

 

[Ebernanut]

Easy work around is to flag the connection as “Metered”, windows will not automatically update on a metered connection unless you also enable “update over metered connections”.
Microsoft wouldn’t dare change that arrangement intentionally the lawsuits would be astounding.

I've had good luck in win 10 with the registry tweak that sets windows update to check for updates but not to download or install until you tell it to, I'm not sure if that's limited to pro. I've never had it force an update like that and you don't have to go back in and manually turn updates back on when you do want to update like with the other methods.

 

[rgMekanic]

Unplug the network. Uninstall and clean the driver in SAFE MODE. Reboot, install driver. Reboot. Plug in network. I literally just did this three days ago. Because - yeah I could see the windows driver updating by flashing the screen earlier. Good advice on disabling driver updates, I usually have that off, prob got re-enabled on an OS update. Group policy fixed that. Just kind of ironic that a dipshit compute "tech" writer borks his box, gets help and then writes this whole article to declare how much of a non-computer person he is.

While it seems very simple to you and I. Some people just want an Xbox with keyboard support.

 

[Mega6]

While it seems very simple to you and I. Some people just want an Xbox with keyboard support.

Sorry, I expect more from someone associated with a major tech website,

 

[PC-Only]

Unplug the network. Uninstall and clean the driver in SAFE MODE. Reboot, install driver. Reboot. Plug in network. I literally just did this three days ago. Because - yeah I could see the windows driver updating by flashing the screen earlier. Good advice on disabling driver updates, I usually have that off, prob got re-enabled on an OS update. Group policy fixed that. Just kind of ironic that a dipshit compute "tech" writer borks his box, gets help and then writes this whole article to declare how much of a non-computer person he is.

While it seems very simple to you and I. Some people just want an Xbox with keyboard support.

Sorry, I expect more from someone associated with a major tech website,

Maybe the person(s) involved with this article is an idiot if they did not do the proper investigation to determine who is definitely at fault and why. Sounds like it happens with everyone, which would indicate the blame is likely with Microsoft. But it does not matter which vendor(s) the fault lies with. It is utterly absurd in 2023 to expect people to have to go through this process to keep their devices up-to-date. Equivalent to Apple's "you're holding it wrong" line. Everything should be fine to be left on 100% automatic with all "proper" update procedures handled in the background with user prompts if and when necessary. Manual updates should still perform an automatic procedure with best practices and where absolutely necessary, warn/instruct the user on what correct manual steps are needed next. Anything less is shoddy design.

 

[Dayaks]

Maybe the person(s) involved with this article is an idiot if they did not do the proper investigation to determine who is definitely at fault and why. Sounds like it happens with everyone, which would indicate the blame is likely with Microsoft. But it does not matter which vendor(s) the fault lies with. It is utterly absurd in 2023 to expect people to have to go through this process to keep their devices up-to-date. Equivalent to Apple's "you're holding it wrong" line. Everything should be fine to be left on 100% automatic with all "proper" update procedures handled in the background with user prompts if and when necessary. Manual updates should still perform an automatic procedure with best practices and where absolutely necessary, warn/instruct the user on what correct manual steps are needed next. Anything less is shoddy design.

Exactly. I don’t need to spend half a night fixing 4 PCs.

This is a good example why I avoid AMD. The 7950x3d is the same deal, you have to waste time figuring out how to make it clock up right in some games.

I tried AMD once.. 2700x and Fury X.. spent way too much time trying to mitigate issues that disappeared when I made that a htpc and got intel/nvidia for the main/vr pc.

 

[blackmomba]

For GPUs I too got burned by random black screens when I had my last AMD card which was Vega 64. I was gonna pull the trigger on a 7000 series card but Steve from HWUB mentioned having the same issue with his review 7900xtx, having to pull out the display cable to get the display back. Wtf? That was enough to keep me away a little longer honestly.

 

[Geforcepat]

For GPUs I too got burned by random black screens when I had my last AMD card which was Vega 64. I was gonna pull the trigger on a 7000 series card but Steve from HWUB mentioned having the same issue with his review 7900xtx, having to pull out the display cable to get the display back. Wtf? That was enough to keep me away a little longer honestly.

My 1080 would do this every now and then. Had to pull out then re insert the DP cable to the card.

 

[NightReaver]

My 1080 would do this every now and then. Had to pull out then re insert the DP cable to the card.

Pretty much. Man, if I swore off every pc brand I had some sort of issue with for the next 10 years I'd never be able to have a pc, lol.