F5F Stay Refreshed Hardware Desktop Screen error, code 0xc00000e9, Windows issues no action.

Screen error, code 0xc00000e9, Windows issues no action.

Screen error, code 0xc00000e9, Windows issues no action.

X
xXSuperNovaXx
Posting Freak
811
05-30-2021, 12:04 PM
#1
Hello everyone, welcome back before the holidays! I’m still getting familiar with this forum, so I’m sure I did everything correctly. About two days ago my computer (the specs below) was fine, but when I tried to start yesterday it crashed immediately into a blue screen, showing error code 0xc00000e9. It won’t boot into Windows 11 at all. I restarted, unplugged all connections, removed all drives except the Windows drive, but nothing helped. Then I attempted a Windows reinstall using Rufus on my laptop. It was tricky because I’m using Windows 11 with an MBR partition. When I tried the startup repair tool from the Windows installation, it said there were no issues to fix (see photo). After that, I tried reinstalling Windows from the USB drive, but it also showed: “Can’t install Windows on inserted media.” It mentioned the upgrade option wasn’t available. As a last option, I used an old Linux Mint bootable disc and checked if it pointed to the right files. The Winload.efi was in the correct location (see final photo). Since the restore tool indicated nothing needed fixing, the installer said it couldn’t install and I’m not sure what to do next.

PC specs: CPU – Ryzen 5 2600X, Motherboard – X470 Aorus Ultra Gaming on BIOS F62d, GPU – Gigabyte RTX 2070, RAM – 2x 8GB and 2x 16GB (2147MHz), Corsair, SSD – Samsung 970 Evo plus 1TB (~2 years old), PSU – Corsair CX750, I/O – Razer Ornata keyboard & Logitech G604 mouse.

I really hope someone can suggest a solution. Otherwise it’s going to be a frustrating holiday.
X
xXSuperNovaXx
05-30-2021, 12:04 PM #1

Hello everyone, welcome back before the holidays! I’m still getting familiar with this forum, so I’m sure I did everything correctly. About two days ago my computer (the specs below) was fine, but when I tried to start yesterday it crashed immediately into a blue screen, showing error code 0xc00000e9. It won’t boot into Windows 11 at all. I restarted, unplugged all connections, removed all drives except the Windows drive, but nothing helped. Then I attempted a Windows reinstall using Rufus on my laptop. It was tricky because I’m using Windows 11 with an MBR partition. When I tried the startup repair tool from the Windows installation, it said there were no issues to fix (see photo). After that, I tried reinstalling Windows from the USB drive, but it also showed: “Can’t install Windows on inserted media.” It mentioned the upgrade option wasn’t available. As a last option, I used an old Linux Mint bootable disc and checked if it pointed to the right files. The Winload.efi was in the correct location (see final photo). Since the restore tool indicated nothing needed fixing, the installer said it couldn’t install and I’m not sure what to do next.

PC specs: CPU – Ryzen 5 2600X, Motherboard – X470 Aorus Ultra Gaming on BIOS F62d, GPU – Gigabyte RTX 2070, RAM – 2x 8GB and 2x 16GB (2147MHz), Corsair, SSD – Samsung 970 Evo plus 1TB (~2 years old), PSU – Corsair CX750, I/O – Razer Ornata keyboard & Logitech G604 mouse.

I really hope someone can suggest a solution. Otherwise it’s going to be a frustrating holiday.

S
Sebbe551
Junior Member
33
05-30-2021, 03:54 PM
#2
I don’t have the solution, but I faced a similar problem before—specifically on an Intel system using Windows 10. After some research, I discovered the issue stemmed from a Windows bug. There was a way to boot into safe mode or use recovery media to fix a corrupted file in System 32. It was surprising it resolved. I’m hoping there’s a quick fix, but if not, you’ll need to go through several steps: back up data, wipe the drive, reset CMOS, and reinstall Windows. It’s not the ideal path, but it might work.
S
Sebbe551
05-30-2021, 03:54 PM #2

I don’t have the solution, but I faced a similar problem before—specifically on an Intel system using Windows 10. After some research, I discovered the issue stemmed from a Windows bug. There was a way to boot into safe mode or use recovery media to fix a corrupted file in System 32. It was surprising it resolved. I’m hoping there’s a quick fix, but if not, you’ll need to go through several steps: back up data, wipe the drive, reset CMOS, and reinstall Windows. It’s not the ideal path, but it might work.