Question Windows doesn't boot anymore after BIOS update (error code: 0xc0000098)

[Jalu66]

Hello, I'm having very big issues with my Windows 10 PC. I updated my BIOS, because I was planning on upgrading my CPU to Ryzen 7 5700x, which required a BIOS update.

My current CPU: Ryzen 5 2400G
My motherboard: MSI B350M PRO-VDH
I updated to BIOS version E7A38AMS.AL6
After the update Windows no longer boots and gives the following error message: Error code: 0xc0000098 File: \BCD

I tried multiple YouTube tutorials and ChatGPT. This is what I tried so far:
(i used ChatGPT to summarize all the things I tried, that's why it might look like AI)

🛠️ Windows Installation USB Stick
Created via Media Creation Tool
Booted from USB → Used Repair Tools → Command Prompt

⚙️ Bootloader Repair
fixmbr
bootrec /fixboot → initially "Access Denied", then fixed using bootsect /nt60 sys
bootrec /rebuildbcd → finds 0 installations
bcdboot used correctly multiple times → no change
scanos also returns 0 installations

📁 EFI Partition
Detected via diskpart (Volume 3, 100MB, FAT32, hidden)
Assigned as Z: → bcdboot used properly
Later formatted using format z: /fs:fat32
bcdboot D:\Windows /s Z: /f UEFI → issue persists

🔁 Boot Order / Devices
UEFI Boot Manager correctly configured
Tested various device orders and boot modes (UEFI vs. Legacy)

🧪 chkdsk
Run on Windows partition (D: → no errors found

📦 BCD Files
BCD renamed to BCD.bak, new one created → no improvement

🧲 USB Stick Recreated
Initially made with MBR/NTFS in Rufus → later redone with GPT
Reformatted several times
Two partitions appeared in boot menu

🔍 sfc /scannow
"Windows Resource Protection did not find any integrity violations"

🔐 Secure Boot / UEFI
Tried Secure Boot enabled and disabled
CSM and UEFI-only tested → no difference
Confirmed GPT format via diskpart (there was a *)

🔄 BIOS Downgrade
Downgraded to an older version (E7A38AMS.AL3 Beta) via M-FLASH
Same error remains (including after UEFI change)

🩺 System Restore
System Restore Point made before BIOS update found and used
No improvement; error reappears after restart

Occasionally: “Inaccessible Boot Device” + black screen after restart + Mouse/keyboard stop working when Windows tries to load (this only appears when the "Inaccessible Boot Device" comes up, not with the 0xc0000098 error)

🔐 Reset Defaults
BIOS defaults restored

🧯 Final Options Considered
Full reinstallation avoided so far

Considering flashing back to original pre-AL6 and pre-AL3 BIOS

Planning to install Ryzen 7 5700X later → BIOS must support Ryzen 5000 series, older than AL3 wouldn't support Ryzen 5000 series

 

[Lutfij]

Welcome to the forums, newcomer!

First, I hope you have a discrete GPU since the Ryzen 7 5700x doesn't have an iGPU.

Second, even if your motherboard has a heatsink over it's VRM, expect the VRM area to run hot as the Ryzen 3000 and 5000 series were known to tax the VRM as they drew more power than the Ryzen 1000 and 2000 series.

Third,
My motherboard: MSI B350M PRO-VDH
I updated to BIOS version E7A38AMS.AL6
what BIOS version you on prior to the update? I hope your chipset drivers were also on the latest version prior to flashing the BIOS.

Fourth,
Please list the specs to your build like so:
CPU:
CPU cooler:
Motherboard:
Ram:
SSD/HDD:
GPU:
PSU:
Chassis:
OS:
Monitor:
include the age of the PSU apart from it's make and model. BIOS version for your motherboard at this moment of time.

Two partitions appeared in boot menu
You don't see Windows Boot Manager in Boot Device Priority list?

Moved thread from Motherboards section to Windows 10 section.

 

[Jalu66]

Welcome to the forums, newcomer!

First, I hope you have a discrete GPU since the Ryzen 7 5700x doesn't have an iGPU.

Second, even if your motherboard has a heatsink over it's VRM, expect the VRM area to run hot as the Ryzen 3000 and 5000 series were known to tax the VRM as they drew more power than the Ryzen 1000 and 2000 series.

Third,
My motherboard: MSI B350M PRO-VDH
I updated to BIOS version E7A38AMS.AL6
what BIOS version you on prior to the update? I hope your chipset drivers were also on the latest version prior to flashing the BIOS.

Fourth,
Please list the specs to your build like so:
CPU:
CPU cooler:
Motherboard:
Ram:
SSD/HDD:
GPU:
PSU:
Chassis:
OS:
Monitor:
include the age of the PSU apart from it's make and model. BIOS version for your motherboard at this moment of time.

Two partitions appeared in boot menu
You don't see Windows Boot Manager in Boot Device Priority list?

Moved thread from Motherboards section to Windows 10 section.

Hi, thanks for your reply.

Yes, I do have a GPU.

Here are my answers to your questions:

My previous BIOS Version was this:
BIOS-Version/-Date:
American Megatrends Inc. A.H0, 02.02.2019

I did not manually update chipset drivers before the flash.

Current CPU: Ryzen 5 2400G
CPU cooler: AMD Wraith Spire (boxed with Ryzen 5 2400G)
Motherboard: MSI B350M PRO-VDH
RAM: 2x 8gb DDR4
SSD/HDD: Crucial MX500 250 GB (SSD) & Seagate SkyHawk 1 TB, SATA 6 Gb/s (HDD)
Current GPU: AMD RX580 (will be upgraded to RTX 5070 soon, after my PC is working again)
PSU: be quiet! 750W (5-6 years in use) [I don't know the exact model, can check if necessary)
Chassis: Sharkoon T3-V
OS: Windows 10 Pro
Monitor: Lenovo (don't know which model)

Current BIOS installed: E7A38AMS.AL3

You don't see Windows Boot Manager in Boot Device Priority list?

I do see it: "Windows Boot Manager (SATA1: CT250MX500SSD1)"

 

[johnbl]

2: kd> !error 0xc0000098
Error code: (NTSTATUS) 0xc0000098 (3221225624) - The volume for a file has been externally altered such that the opened file is no longer valid.

first thing I would do is go into bios and see what mode you are using for your drive.

Sata ? Raid? if the mode is incorrect (from the original bios setting) then the system will not see the partition and the repair utilities will not work.
normally, you can change the mode and try to boot and see if the disk partition is readable.

your motherboard supports:
4 sata port slots (raid 0, 1 and 10)
and 1 m.2 slot

i would check to see what mode it currently is in, then change it to another mode ahci or raid 0 are most likely

 

[Jalu66]

The SATA mode is currently set to AHCI Mode. I have also never changed this to anything else.

 

[johnbl]

The SATA mode is currently set to AHCI Mode. I have also never changed this to anything else.

ahci mode would not require a non microsoft driver. it would be the most stable mode since the driver is updated by microsoft.

I would keep this mode if you are sure you did not have it set to raid 0 by the oem when you got it.

I have seen cases where you had to run a chkdsk on the drive before you could run diskpart.exe and
run
bootrec.exe /rebuildbcd
note: you would have to assign a drive letter to the drive that can not be read, then run chkdsk command on that drive to get it to read again if it is marked as raw drive type.

(only have seen this on intel system when there was a bug in the intel rapid storage driver)