I'm trying to change a BIOS setting for Valorant, but I can't get into BIOS during startup. I've tried F2, F8, F10, Delete, holding the keys, and using another keyboard, but the computer either boots directly to the Windows login screen or appears to stay off while I'm pressing the keys. Unlike my other PC, using Shift+Restart doesn't bring up the recovery menu either.
The computer also fails to restart normally from Windows. The screen goes black, the fans keep spinning, and their usual lighting turns off. It never starts back up, so I have to hold the physical power button to shut it down. I also never see the Windows logo during a normal startup; it goes straight to the login screen. The motherboard is a Gigabyte Eagle AX. Has anyone dealt with this problem or know how I can access BIOS safely?
3 Answers
The black-screen restart and missing startup logo suggest the system may be skipping or failing during the firmware handoff, rather than this being only a keyboard problem. A CMOS reset is a reasonable first step. Afterward, check the motherboard manual for the exact BIOS key and consider testing with only one monitor connected, since a display may not show an image until Windows loads.
Try entering BIOS immediately after pressing the power button rather than waiting for anything to appear. Tap the motherboard’s setup key repeatedly from the moment you turn the PC on. On many Gigabyte boards that key is Delete, though some systems may use F2. You can also try Windows’ advanced startup options and choose the UEFI firmware settings option if it appears.
A complete power drain and CMOS reset may restore normal firmware startup. Shut the PC down, unplug it, hold the case power button for about 10–15 seconds, then clear the CMOS using the motherboard’s jumper or by removing the CMOS battery for a few minutes. Reconnect everything and give the first boot extra time. Be aware that resetting BIOS will restore default settings, so you may need to re-enable settings such as XMP afterward.
I also discovered that Valorant actually requires UEFI Secure Boot to be enabled, so I may have remembered the requirement backward. I’ll avoid changing that setting unless I confirm it’s necessary.