Windows fails to start unless accessed via BIO settings
Windows fails to start unless accessed via BIO settings
Hello everyone, I’m dealing with a strange issue and haven’t found a fix yet. In December my nine-year-old power supply failed, which corrupted my Windows installation. After replacing it, the computer required a fresh Windows 10 setup. That wasn’t the issue. The problem arose after installing it on a brand-new SSD. As mentioned in the description, I need to adjust the BIOS boot settings and choose “boot this now.” This option is already set as the default. However, if I don’t select it that way, the system displays a BIOS post-screen, and when Windows login appears, the screen goes black, loses signal, and the num key stops working. During normal boot through BIOS, the post-screen appears first, then the Windows logo, and the display turns off after a few seconds before coming back. In some cases, the bootloader functions correctly but only when accessed via BIOS, allowing the login screen to appear. Could something be causing this behavior? When started through BIOS, everything seems to work even under stress, suggesting no hardware failure. My system uses an Intel i7-3770k, ASUS Maximus V Gene 32 GB DDR3 970 1 TB Evo as boot drive, paired with an Asus RTX 2070 dual-core graphics card.
It might be feasible to have an old Windows boot sector present. Disconnecting both SATA cables and attempting a boot only with the 970 EVO can help determine if that’s the case.
I attempted to disconnect all drives except the 970 1Tb, and the outcome remained consistent. The next phase will involve testing it on another spare drive and performing a fresh installation.
I've performed a new installation on an unused SSD, but the problem persists. It looks like the motherboard isn't sending the correct data when choosing the Windows boot manager.
The most likely scenario is an installation of Ubuntu on the new SSD, which might create complications. I’m running out of creative ideas. Could the Windows key left on the motherboard interfere, or is there a misconfigured boot setup?
Reviewed both installations (old and new). They’re active. Tested under these conditions: 870 evo 1tb with all disks connected, plus all disks removed; and 850 evo 120gb with all other disks taken off. Even after a fresh setup on the 850 120gb, it performed consistently. Still puzzling. Checked mainboard boot settings. Fast boot is enabled, USB support partial initialized, network stack driver disabled on startup after PSU failure. Boot logo appears normally, delay time 2 seconds, status at boot: on. If error occurs, F1 prompt appears. ROM messages show BIOS interrupt 19 capture disabled, setup mode active, normal boot logo, UEFI in boot sequence. Boot priorities: Windows Boot Manager, disabled boot option, disabled.
I observed a change. To start the system, I don’t have to navigate into the BIOS and pick Windows Boot Manager as the direct boot option. All I need to do is simply enter and exit the BIOS to reach the login screen. When I skip the BIOS step, the problem persists as before.