Changing my BIOS to allow AMD SAM succeeds initially, but it doesn’t start properly afterward.
Changing my BIOS to allow AMD SAM succeeds initially, but it doesn’t start properly afterward.
I've been using my gaming PC smoothly lately. The hardware includes an AMD Ryzen 7 3700X with MSI M PG X570 Gaming Edge Wifi (ATX), 32GB RAM (4x8GB) Corsair Vengeance LPX DDR-4 at 3200MHz, and a MSI AMD Radeon 5500 XT Mech 8GB OC with Samsung 970 EVO 500GB NVMe. The boot drive holds the system, plus another 1TB NVMe and three HDDs for a total of 2.25TB. I'm running Fractal Design Ion+ at 760W on Windows 11 64-bit.
I haven't found a RTX 3080 12GB model that's worth the high price, so I stuck with the 5500 XT. It doesn't handle demanding games well on my Samsung CRG49 (previously had Odyssey G9 with 5140x1440p). After AMD announced support for 3000-series CPUs and 5000-series GPUs, I decided to upgrade my BIOS from E7C37AMS.110 to the latest stable version (E7C37AMS.1I0), which unlocks all new features.
After the update, booting into Windows works smoothly once I enable XMP and SAM settings. But when I restart, the PC powers on fine, yet it won't boot into Windows. The MSI startup logo disappears, and my keyboard doesn't receive power, making it hard to enter BIOS. I've reset my motherboard to the oldest BIOS version listed, but other updates haven't helped. My EZ-Debug LEDs have been unhelpful so far—sometimes a GPU light appears, but also Boot and CPU indicators.
I've re-installed the CPU and drivers after an update, but nothing changed. I'm running out of troubleshooting options and might keep using the old BIOS for stability. Do you have any suggestions or experiences to share?
Best,
Joker
Confirming your BIOS is updated and verifying boot configurations, such as secure boot and FTPM.
Hi 191x7 and GuiltySpark_, I completely overlooked the secure boot details... UEFI was turned on. It seems Secure Boot could have been the issue, since I thought it stayed active after the BIOS update! I managed to turn off and restart the machine, which suggests everything is working fine now. I plan to test the PC over the coming days to check for any problems, but hoping it all goes smoothly. So far, it appears you've resolved my concern. These were important points—I should have noticed them. Thanks both of you, Joker!
Following the update, after some time passed, when I power on the computer, the screen turns on but remains blank. The keyboard also fails to display anything, though the internal components continue to spin. Hibernation is disabled. Restarting back into the initial BIOS, I ran an sfc /scannow. It completed its verification and repair transaction, confirming that "All files and registry keys listed in this transaction have been successfully repaired."
Hey there, I spent the last two hours troubleshooting this problem on my end. But I can share that it's quite similar after updating the BIOS on my MSI board. I'm not sure if it'll work for you, but you might try using the older BIOS version—your PC should boot fine then. The latest drivers seem to affect Secure Boot settings, which could be the cause.
Hey Munchboy Yeah getting into the old BIOS is not an issue for me, as there I have everything working fine and without problems. When Flashing the new BIOS via MFlash with an USB stick I can usually even get back into the BIOS to change the secure boot settings. Its only after a complete switch off and a few minutes wait that when I turn on the PC where it shows the symptons mentioned here: