PC connects to BIOS after CMOS reset, yet it still loops without reaching normal BIOS mode.
PC connects to BIOS after CMOS reset, yet it still loops without reaching normal BIOS mode.
I faced some problems with my PC before (refer to earlier post), so I upgraded to a new ASUS B560M-A motherboard. It seemed to resolve the issues. I successfully installed a fresh Windows version and completed the setup without trouble. After turning it off, the next day I booted into BitLocker recovery. I closed out of it and it started looping. The fans spun and lights illuminated for four seconds before shutting down endlessly. When I unplugged the PC and reset the CMOS, it booted into BIOS but returned to looping when I exited BIOS. Everything else was functioning perfectly yesterday. My system had an Intel i5-10400K, ASUS Prime B560M-A, Radeon Sapphire Pulse RTX 6600 XT, and a 2x8GB DDR4-3600 Samsung 990 Pro M.2 SSD.
You mentioned difficulties with accessing the BIOS during a loop, suggesting a potential loading problem. It seems like the operating system might be having trouble starting properly. You could attempt using a bootable installation media or live disk to test whether the issue lies in the BIOS or the OS itself.
I've tried booting from 2 drives that have working installations of windows and booting windows installation media. There is no visual output when its looping, i cant get into bios while its looping.
To reach your boot menu, simply power on your computer and maintain the necessary key presses. Sometimes I hold them even when the machine is off.
The issue isn't related to bios. I can reach it by resetting the CMOS. I can't start in Windows or install media.
I successfully booted into Windows via BIOS after updating the CMOS with a fresh battery, but restarting caused it to restart endlessly. It appears to work well once the PC is powered on and off, yet loops when the system is powered on but the power supply remains active.
It won’t let you power on and it keeps looping whenever you attempt to start it. I don’t know what caused this issue.