F5F Stay Refreshed Software Operating Systems Error message appears when trying to boot, indicating a problem with the boot device following a BIOS update.

Error message appears when trying to boot, indicating a problem with the boot device following a BIOS update.

Error message appears when trying to boot, indicating a problem with the boot device following a BIOS update.

O
oOEmmaOo
Posting Freak
818
08-13-2020, 06:20 PM
#1
I've constructed this system back in 2019 and chose to give it a complete makeover.
Began by installing all Windows 10 updates and restarting – fine.
Then, I installed Bios F23 (the current one was F3, honestly) and flashed it via the app, which rebooted my computer.
Now, it refuses to boot into Windows, displaying an error about the title of this post.
I suspect the BIOS update reset my settings, but I have no idea what they were before.
I chose to keep the old BIOS, though the app is so slow that I’m unsure if it worked at all.
I attempt to stay updated with technology, but with all these UEFI, AHCI, VDM, CSM, RST... stuff—really no clue what I’m doing, to be honest!
Reinstalling everything is the last resort I want to take, since I forgot to save my files (lesson: can’t trust those programmers who handle BIOS/Boot stuff).
Hardware:
Gigabyte Z490 Aurus Pro AX
Intel i5-10600k
ADATA XPG SX8200 Pro 1 TB M.2-2280 PCIe 3.0 X4 NVME SSD (only one drive)
I attempted to load "optimized defaults" and adjusted settings extensively. I think I might have explored all possible combinations, but without success—though I haven’t found the "VDM" that many discussions mention.
Rant: Would it have been so difficult to set up a fallback method or run a real diagnostics check like "SSD is set to UEFI, BIOS is set to Legacy"?
I’m seeking any advice on what to do next.
So far, I’m considering retrieving the "saved old bios," but it would be a mess since I don’t really have another place to plug in that SSD for file access. Also, I don’t have a USB stick for Q-flash...
O
oOEmmaOo
08-13-2020, 06:20 PM #1

I've constructed this system back in 2019 and chose to give it a complete makeover.
Began by installing all Windows 10 updates and restarting – fine.
Then, I installed Bios F23 (the current one was F3, honestly) and flashed it via the app, which rebooted my computer.
Now, it refuses to boot into Windows, displaying an error about the title of this post.
I suspect the BIOS update reset my settings, but I have no idea what they were before.
I chose to keep the old BIOS, though the app is so slow that I’m unsure if it worked at all.
I attempt to stay updated with technology, but with all these UEFI, AHCI, VDM, CSM, RST... stuff—really no clue what I’m doing, to be honest!
Reinstalling everything is the last resort I want to take, since I forgot to save my files (lesson: can’t trust those programmers who handle BIOS/Boot stuff).
Hardware:
Gigabyte Z490 Aurus Pro AX
Intel i5-10600k
ADATA XPG SX8200 Pro 1 TB M.2-2280 PCIe 3.0 X4 NVME SSD (only one drive)
I attempted to load "optimized defaults" and adjusted settings extensively. I think I might have explored all possible combinations, but without success—though I haven’t found the "VDM" that many discussions mention.
Rant: Would it have been so difficult to set up a fallback method or run a real diagnostics check like "SSD is set to UEFI, BIOS is set to Legacy"?
I’m seeking any advice on what to do next.
So far, I’m considering retrieving the "saved old bios," but it would be a mess since I don’t really have another place to plug in that SSD for file access. Also, I don’t have a USB stick for Q-flash...

E
Ethmasher
Member
96
09-04-2020, 03:51 AM
#2
I'm still not out of the situation but I have additional details for those who update their BIOS and encounter this issue:
It seems I installed Windows-10 while my BIOS had "Intel RST" turned on. This appears to be a RAID controller that doesn't make sense if you're using just one storage device (like me), though I probably enabled it because it seemed faster. (In reality, AHCI performs better with only one non-optane drive.)
Windows needs to boot using the correct RST/AHCI settings it was originally installed with.
Regarding VMD (my BIOS doesn't mention it)—it's actually the Intel RST, which is a VMD created by Intel.
I was able to boot in safe mode again, as I mentioned earlier it should be straightforward for the system to diagnose or fall back. I'm not sure if this is the optimal approach, but I found a command prompt solution: 'bcdedit /enum' then check if Windows Boot Loader's identifier matches {current} or {default}, and adjust accordingly:
'bcdedit /set {current} safeboot minimal'
Now in safe mode, I can see in Device Manager that Storage controllers include the Intel RST—confirming Windows was installed with RST.
For now, I don't plan to fix it, just want to get normal booting. From here on, my focus will be adjusting other BIOS settings while keeping RST enabled.
E
Ethmasher
09-04-2020, 03:51 AM #2

I'm still not out of the situation but I have additional details for those who update their BIOS and encounter this issue:
It seems I installed Windows-10 while my BIOS had "Intel RST" turned on. This appears to be a RAID controller that doesn't make sense if you're using just one storage device (like me), though I probably enabled it because it seemed faster. (In reality, AHCI performs better with only one non-optane drive.)
Windows needs to boot using the correct RST/AHCI settings it was originally installed with.
Regarding VMD (my BIOS doesn't mention it)—it's actually the Intel RST, which is a VMD created by Intel.
I was able to boot in safe mode again, as I mentioned earlier it should be straightforward for the system to diagnose or fall back. I'm not sure if this is the optimal approach, but I found a command prompt solution: 'bcdedit /enum' then check if Windows Boot Loader's identifier matches {current} or {default}, and adjust accordingly:
'bcdedit /set {current} safeboot minimal'
Now in safe mode, I can see in Device Manager that Storage controllers include the Intel RST—confirming Windows was installed with RST.
For now, I don't plan to fix it, just want to get normal booting. From here on, my focus will be adjusting other BIOS settings while keeping RST enabled.

W
WPaige
Senior Member
377
09-04-2020, 05:13 AM
#3
I ran 'sfc /scannow' which detected some issues and resolved them. The system still starts in safe mode only, but the commands I found don't function properly. However, after checking msconfig and looking at the Boot section, I can uncheck Safe Mode and it works fine. I believe I've fixed the problem.

I was thinking about upgrading my SSD (I had it for a few months ago) anyway, so I'm not too concerned about fixing everything. My main goal is to finish my work, save all data, and take some time for a clean Windows-11 installation.
W
WPaige
09-04-2020, 05:13 AM #3

I ran 'sfc /scannow' which detected some issues and resolved them. The system still starts in safe mode only, but the commands I found don't function properly. However, after checking msconfig and looking at the Boot section, I can uncheck Safe Mode and it works fine. I believe I've fixed the problem.

I was thinking about upgrading my SSD (I had it for a few months ago) anyway, so I'm not too concerned about fixing everything. My main goal is to finish my work, save all data, and take some time for a clean Windows-11 installation.