First PC setup issue – can't reach BIOS settings
First PC setup issue – can't reach BIOS settings
I've been watching this video and still can't access the BIOS during the bench troubleshooting stage (1:02:14). A screen appears with an "ami" logo asking me to delete it before entering setup. It displays messages like "New CPU installed, fTPM/PSP NV corrupted... or changed" followed by options to reset or keep the current fTPM. Would this be considered the post? The motherboard is an Aorus X670 Elite AX. The CPU is Ryzen 7 7700X. The power supply is a Phanteks AMP 650. No GPU is present. RAM is installed in slots A2 and B2 (2&4). I'm seeing a VGA GPU warning light. I've used two keyboards—one wireless, one wired—and neither works when I press delete or F2. I've tried power cycling. I read online to update to the latest BIOS. I downloaded the newest BIOS onto a USB and used the Q-Flash Plus button while the system was powered down. It took a moment for the PSU and cooler fans to activate, then the flash drive light appeared, after which everything shut off. I believe my current BIOS version is F5 based on what I see. Pressing the CMOS_SW button didn't seem effective. Any suggestions for further troubleshooting? Your help would be greatly appreciated. Thank you!
You're experiencing the same issue again. The Y key didn't trigger the expected message, and after replacing the battery and trying other commands, you're still stuck on the POST screen. Deleting and using F2 doesn't help, but pressing ALT + CTRL + Delete to restart seems to work. It might be worth checking if a recent BIOS update is necessary.
You're experiencing the same issue again. You've tried several fixes—pressing Y, removing the battery, deleting the motherboard, and using F2 or ALT+CTRL+Delete—but nothing seems to resolve the POST problem. The fact that you switched to a wired keyboard with a cheap wired keyboard worked suggests the original issue might be related to the wireless setup or BIOS configuration. Consider checking your BIOS version and updating it if necessary, as outdated firmware can cause similar problems.