Overclocking and reinstalling Windows appears to be a poor combination.
Overclocking and reinstalling Windows appears to be a poor combination.
Before I speak, I'm a first-time overclocking enthusiast, so please be kind. I recently upgraded my CPU and somehow every time I booted up it would jump straight to BIOS, only allowing me to access Windows afterward. The motherboard I have is an Asus Z170-e, and I followed a guide from Overclockers UK that came with their overclocking kits, which I purchased. Because of the requirement to enter BIOS on every boot, I began reinstalling Windows 10. Once the installation started, the first time it went through caused my system to malfunction. After resetting the BIOS back to its default settings, my PC still doesn’t seem able to boot past the Windows loading screen—it just freezes when I try to boot from the Windows HDD or the bootable USB with the Windows installer. I’ve tried various USB ports, but I have no idea what’s going on. Any advice would be greatly appreciated.
Yes. All settings have been restored to their default values in the BIOS.
I possess the same motherboard, and if my overclock fails to function correctly, it forces me to access the BIOS each time I power on. How did you perform the BIOS reset? Did you disconnect the PC and remove the battery for ten minutes? The instability seems similar to a faulty overclock.
I have set it back to the default in the BIOS menu and attempted to boot via USB because Windows wouldn't load after the installation pause, but the problem persisted. After removing the battery, the situation remained unchanged. I haven't tried resetting the CMOS, though I suspect that was done by removing the battery as well.
Disconnect the PC and take out the CMOS battery, then press the power button several times. This should fully reset your BIOS to its original settings.
I'll handle it first thing in the morning and share the results here!
Nothing has altered. The same issue persists with the group. Could it be attempting to load, which is causing it to remain unresponsive? It might be due to the corrupted installation.
Consider verifying the CSM configurations in your UEFI. It might help to enable or set AUTO. Additionally, check the boot sequence once Windows begins installation—ensure "Windows Boot Manager" appears first. Look for an option to select all devices as a boot choice.