no bootable device asus bios b650e i

[kimastor]

I just built a system for my dad. It sometimes did not find a bootable device, so it got stuck in BIOS, and sometimes just bootes very slow. This was often resolved after restarting the system, but still annoying and not a feature you want on a new mobo. It came with BIOS 1818 so I decided to update to the latest 3024, but now the system did not boot to windows (11) at all. I tried with different MCR settings, but it did not work. Also no bitlocker. Eventually, I had to flash it back to 1818. 

If there is a solution I would very much appreciate all the help and information I can get!

System: ROG b650e i, Ryzen 5 7600, Kingston 32gb (2x16) 5200 cl36 Fury Beast, Samsung 990 evo m2 2bt in main slot (only drive), RTX4060

[Silent_Scone]

Hi @kimastor 
1. When the system is booting slowly, what QLED is lit? Please be advised that initial DRAM training may take some time.

2. Are you enabling AMD EXPO?

3. Can you advise what you're referring to as the "main slot" for your NVME?

[kimastor]

Thanks for the answer! 

1. Unfortunately, I don't have the computer at hand atm, but the slow boot may have been improved, I will look it up. 

2. I have not enabled EXPO or anything else, just running it at default settings (I assume it is off by default)

3. The main slot would be the one with a heatsink over the pci-e slot, not the one on the back. 

[Silent_Scone]

The initial POST time can depend on memory configuration as memory training takes place.

As the 990 EVO is a GEN4 drive, have you tried using the secondary M.2 slot to see if the boot behaviour persists?

[kimastor]

I thought Gen 5 slots would be backward-compatible (only affecting speed)?

It is a very tight ITX build, so changing things around is a bit of a hassle... perhaps it would be enough to configure a Gen 5 slot to operate as a Gen 4 slot in the BIOS settings? I will give it a try!

[Silent_Scone]

Indeed it should work in the initial GEN5 slot, however, this is for troubleshooting purposes. Yes, you can manually adjust the protocol to GEN4, I can't say whether this will resolve the issue.