![]() |
Radeon RX 7000 BIOS update procedure |
Post Reply
|
| Author | |
Xaltar
Moderator Group
Joined: 16 May 2015 Location: Europe Status: Online Points: 44088 |
Post Options
Thanks(0)
Quote Reply
Topic: Radeon RX 7000 BIOS update procedurePosted: 05 Nov 2026 at 6:41pm |
|
Hello all.
It has been brought to my attention that some people have experienced bad flashes while updating to the latest security fix vBIOS for RX 7000 series cards. The issue has been pinned down to a driver problem that causes flashes to fail in some cases. During the vBIOS update process, the procedure provided by ASRock requires all graphics drivers to be completely removed beforehand. If the drivers are not fully uninstalled, the vBIOS update may fail and potentially result in vBIOS corruption. If you have experienced a bad flash and your card is preventing your system from POSTing then ASRock advise that you contact them using their support form. https://tw.asrock.com/events/tsd.asp I hope this helps. |
|
|
|
![]() |
|
MOhankan
Newbie
Joined: 05 Nov 2026 Status: Offline Points: 75 |
Post Options
Thanks(0)
Quote Reply
Posted: 05 Nov 2026 at 9:07pm |
|
Thanks for using time on this matter Xaltar.
I am one of the ones affected. I got the issue even though I ran the uninstaller from the guide, so maybe the uninstaller has a flaw also? Maybe they should also have the flashing utility run a check on whether such a driver is still running to some extent if it can cause such a consequence. I filed a request sunday through the form but haven't heard a thing since. Not having a solution ready yet is of course OK, but silence is worrying, so just a short "we're looking into a solution" would be reaffirming. Best regards |
|
![]() |
|
Xaltar
Moderator Group
Joined: 16 May 2015 Location: Europe Status: Online Points: 44088 |
Post Options
Thanks(0)
Quote Reply
Posted: 05 Nov 2026 at 9:16pm |
|
Sorry to hear about your bad luck. There is almost nothing that would make me flash
my vBIOS, mostly because I know it is far less refined of a process vs a regular motherboard BIOS flash. I always flash vBIOS updates using Windows Safe Mode. That completely cuts out the chance that any drivers or other software will interfere. Unfortunately, quite often the OS will try to install drivers even when you uninstalled them. You can get around this using Display Driver Uninstaller (Search for DDU) and set it to not automatically install drivers but given you have to enter safe mode to properly use it anyway, may as well flash the vBIOS in safe mode. |
|
|
|
![]() |
|
MOhankan
Newbie
Joined: 05 Nov 2026 Status: Offline Points: 75 |
Post Options
Thanks(0)
Quote Reply
Posted: 05 Nov 2026 at 9:24pm |
|
Ok I can appreciate that, but with AMD pushing for users to install this security update and the manufacturers pushing it out for "older" cards like this, and everything that goes on with critical vulnerabilities found daily in hardware and software, it also felt risky not to do so.
|
|
![]() |
|
MOhankan
Newbie
Joined: 05 Nov 2026 Status: Offline Points: 75 |
Post Options
Thanks(1)
Quote Reply
Posted: 05 Nov 2026 at 9:40pm |
|
I just snooped around a bit and found the SOP for the 2023 Vbios update instructions - It specifically mention the bios flashing software not allowing the flash to run if it finds drivers on the system - really makes you wonder how this check was removed if the procedure is that fragile https://download.asrock.com/Manual/QIG/Update%20vBIOS%20SOP.pdf
|
|
![]() |
|
Xaltar
Moderator Group
Joined: 16 May 2015 Location: Europe Status: Online Points: 44088 |
Post Options
Thanks(0)
Quote Reply
Posted: 05 Nov 2026 at 11:21pm |
I hear you, security concerns are among the reasons I would consider an update myself. Sorry if that wasn't clear in my post. All I was trying to say is, despite my vast experience, vBIOS updates still scare me. Any time you are updating firmware on a live component (in use by the OS) you run the risk of the OS and just about any other app interfering and bricking it. Thanks for the link to the SOP. Good luck with the RMA, I don't see any reason it would be refused or cause you issues if that helps. |
|
|
|
![]() |
|
MOhankan
Newbie
Joined: 05 Nov 2026 Status: Offline Points: 75 |
Post Options
Thanks(0)
Quote Reply
Posted: 06 Nov 2026 at 12:00am |
|
It does help actually seeing your seniority on this forum - thank you. I would also expect it to be a formality, but the silence still is uncomfortable.
I haven't had issues with Asrock hardware before, and I don't know their customer support to be flagged as poor in general, but some pc component manufacturers for sure has a tendency to silence problems away if at all possible. Seeing people already beginning to resolve this themselves by buying flashing equipment, sharing roms, getting help from professionals etc., thereby voiding the warranty, speaks a little into this lack of confidence in general for me sadly. A lot of this could be halted by a quick "we're on it" message from Asrock even if they don't have the actual procedure set up yet (which is understandable) |
|
![]() |
|
Xaltar
Moderator Group
Joined: 16 May 2015 Location: Europe Status: Online Points: 44088 |
Post Options
Thanks(0)
Quote Reply
Posted: 06 Nov 2026 at 12:51am |
|
Yeah, I get where you are coming from. I have typically found ASRock's support to
be top notch but that is on the scale of manufacturer level support. It can be a bit slow to get a response at times. Generally if you don't get a response in 14 working days then you need to submit a new support form. Usually the responses come within about a week. I find submitting support forms during the week give them a higher chance to be responded to quickly. Weekend reports end up on the backlog pile and tend to get overlooked/missed more easily. So long as you received your confirmation email you should be good to go. ASRock's support team is on the small side compared to other brands but I have always found them to be very helpful. If your situation is urgent you can try calling the support department closest to your region (EU, USA, Asia/Australia). https://www.asrock.com/general/about.asp(question mark)cat=Contact For some reason the forums don't show the question mark character since the last update so I have put it in brackets, just replace (question mark) with a question mark. Good luck. |
|
|
|
![]() |
|
Dicer
Newbie
Joined: 1 hour 27 minutes ago Status: Offline Points: 15 |
Post Options
Thanks(0)
Quote Reply
Posted: 1 hour 21 minutes ago at 11:22pm |
|
With the new 1.0.6 VBIOS I was unable to flash it onto my graphics card. I thoroughly followed the steps of the provided manual however this is the problem:
Option 1: If you remove everything including the Basic Microsoft Display Driver, then it says no AMD card detected and you can't continue. Option 2: If you leave the Microsofot Basic Display Driver there and just run the AMD Cleanup Utility (which does NOT remove the Microsoft Basic DD) then the flashing tool gives you a warning but you can continue anyway on your own risk. If my card gets bricked with option 2 it's my own fault and I have to buy a 9070XT for about 1000 € (due to lack of stock and high prices in my area) so I don't want to risk that. I would prefer that the tool would work as intended and would let me flash my 9700XT Phantom Gaming as described with option 1. But it then is not detected by the flashing tool. I hope to have described the problem in a way that is understandable and leaves nothing in the dark. Please help |
|
![]() |
|
Xaltar
Moderator Group
Joined: 16 May 2015 Location: Europe Status: Online Points: 44088 |
Post Options
Thanks(0)
Quote Reply
Posted: 9 minutes ago at 12:34am |
|
The Microsoft "inbox driver" refers to Microsoft's own certified driver for your card
(where applicable) that it downloads via windows update . You do not need to nor should you remove the basic display adapter driver. The warning you receive is simply that, a warning about the risk of flashing your vBIOS. There is always a risk when doing so, regardless of the steps followed. Flashing a vBIOS is risky because it is done through the operating system (Windows) this is why ASRock and most other manufacturers stopped providing BIOS update tools for windows and insist on instant flash from within the BIOS itself. Windows itself trying to update/change drivers (hence the need to remove AMD's drivers and rely on the basic display adapter driver), antivirus/antimalware apps, a youtube video trying to load at a bad time, all of these and more can cause a flash to fail. If you are not concerned about the security risk that requires the update, I honestly wouldn't bother with it. The risk is "undisclosed" and there have been no reports of exploits in the wild. AMD is obviously advocating for vBIOS updates to cover themselves legally. This way, if anyone has their system compromised they can say they provided a fix and encouraged users to use it. Otherwise they could be sued. Personally, I wouldn't risk bricking my expensive bit of kit for a legal cover. If the security risk was considered severe and there were reported instances of it being exploited in a way that would impact me, I would risk it then. Bare in mind, this is my personal opinion, I do not speak for ASRock in this. That said, the "undisclosed" part bothers me. That means they are concerned about the nature of the vulnerability being discovered because it may lead to exploitation. If it is kept under wraps properly it should be fine but.... If you still want to go ahead and update, that warning is not an indication you did something wrong, it appears regardless given the nature of vBIOS flashing and the risk involved. I assume you are referring to the: "Burning firmware carries a risk of failure" If so, it is in the instructions and you are prompted to click "yes". Flashing vBIOS firmware is scary, even for someone like me with decades of experience. It should not be undertaken lightly. ASRock or a competent tech with an external flasher should be able to recover the card from a bad flash if you are unlucky. It may be worth opening a support ticket with ASRock about it and asking them if you are covered for a bad flash and can RMA if it happens. https://tw.asrock.com/events/tsd.asp?kind=VGA Good luck and let me know how it goes if you decide to go ahead with the update. Edited by Xaltar - 7 minutes ago at 12:36am |
|
|
|
![]() |
|
Post Reply
|
|
| Tweet |
| Forum Jump | Forum Permissions ![]() You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |