Can’t boot from nvme drive after bios update

dannyboy75 · 2 Dec 2023 at 16:01

This morning I updated my MSI Z790 BIOS to the latest E7E07IMS.A80 version. Before doing so I updated all drivers including Intel management engine.
After the bios updated, I can no longer select my Samsung 990 nvme as boot device. I tried enabling CSM, but my 3080 doesn’t seem to like that. With csm enabled I get four short beeps at post, and a black screen w/ flashing cursor, and system won’t boot from anything then. I can see the Samsung drive in Legacy boot options, but if I set that it still refuses to boot from it.
Re enabling UEFI mode stop the four short beeps, but I still don’t see the Samsung drive as an option to boot from in UEFI boot devices. I’ve tried removing my other nvme drive and moving the Samsung to a different slot too. I have seen other threads saying that management engine drivers need updating, but I did update those before the bios update, and can’t get into windows now anyway. I also rolled back the bios to previous version, and then did a CMOS reset for good measure.

The Samsung drive is visible as a connected device in the bios, and I can even run the MSI self test feature on it (which comes back fine). So I don’t think there’s anything wrong with the drive.

Bit stumped at this point though. Really appreciate any help. Thanks all.

Danny

sg0 · 2 Dec 2023 at 19:00

Do you have an igpu in your cpu? For testing maybe disconnect your 3080 and try to boot from your nvme. Then try to repair your boot files from within windows? Or just reinstall?

Jupiter · 2 Dec 2023 at 19:26

Usual process - start disconnecting things from your PC until it boots. Then diagnose why problem thing prevented booting

Mr Oxide · 2 Dec 2023 at 19:33

Does the MSI Motherboard have the equivalent of Asus Flashback for bios via USB?

Go back to your previous Bios if all fails.

I had an issue with CSM but I am at a loss to remember what is was at this moment as drunk.

dannyboy75 · 3 Dec 2023 at 12:30

Thanks for the replies gents. Back up and running now, finally. Something with that bios update hosed my boot loader. Still not really sure how, or why. Rolling back to previous bios version didn’t help either, oddly.

I was struggling yesterday to even create a Windows 11 USB or DVD, as I had loaned my only flash drive to a friend, and the only spare computer I had was my work laptop (which I have to be very careful what I use for these days, to avoid the wrath of my boss!)

Finally managed to get my flash drive back this morning, to set up Win 11 bootable using Rufus. Then tried automatic start-up repair - failed.
Next, tried running the steps from this page:

How to Repair Windows 11 UEFI Bootloader [Full Guide]

What to do when you upgraded to Windows 11 but are not able to enable UEFI and convert from MBR to GPT? Here is an ultimate guide that allows you to convert without data loss, and enable UEFI using Advanced Recovery.

www.easeus.com

Some commands errored but others didn’t. I just tried all of them anyway. Then tried running start-up repair again, and, thankfully, this time my system is bootable once again.
Thanks again for the help.

dannyboy75 · 3 Dec 2023 at 13:10

sg0 said:
Do you have an igpu in your cpu? For testing maybe disconnect your 3080 and try to boot from your nvme. Then try to repair your boot files from within windows? Or just reinstall?

To answer your question - no. I was a cheapskate and went for the 13700KF with no iGPU. Would've helped a lot with troubleshooting yesterday, so I won't make that mistake again just to save a few quid!

SpellowHouse · 3 Dec 2023 at 13:14

I have no idea what I am talking about, but I wonder if it is one of the Windows secure boot options that's causing the trouble. Has one of these been reset with the BIOS?

dannyboy75 · 3 Dec 2023 at 13:17

SpellowHouse said:
I have no idea what I am talking about, but I wonder if it is one of the Windows secure boot options that's causing the trouble. Has one of these been reset with the BIOS?

I did check all the BIOS settings numerous times but couldn't see anything that looked wrong. When I was running the diskpart / bcdedi commands, the EFI partition had totally vanished. Only partition on that disk was the main Windows one. Very odd. But all working now anyway.