Multiple clean installs, New SSD, still going to auto repair loop

noofy · 08 Feb 2021

x2 SSDs
16gb RAM
Windows 10 Pro (digital license) 20H2 from MS's Media Creation Tool
Motherboard: ECS H61H2-MV

After multiple (like 10+) clean installs on two different SSDs (one brand new), Windows 10 keeps going into an auto repair loop and is unable to be fixed by any bcdboot or bcdedit commands. Trying to restore the bcdstore is not going to work. I've tried so many things that it's dizzying. Going through the auto repair process will occasionally work, but when it does, it goes into chkdsk, repairs, then allows me back into Windows; except, when I get there, everything is mangled -- all the programs are messed up, even Edge is broken. So throughout all my attempts at fixing this, I've simply stopped going that route. But when it does inevitably begin to get stuck in the auto-repair loop, I've taken TONS of measures in the cmd prompt environment and nothing's worked. I've even tried installing in IDE mode and AHCI mode to see if it'd behave differently, and it did not; the same thing happens.

I'm suspecting some hardware might somehow be broken. I've run extensive tests on the memory; all come back clean. When this first started, I thought it was the SSD and got a new one, and it still does messes up. I'm suspecting it could also be EUFI-related? So my next try is going to consist of switching to full legacy bios and reinstalling Windows for the umpteenth time.

Can a power supply cause such a thing? It causes it in the same manner each time though, which is why I've been thinking it may not be power supply, but maybe it is??? Also, I thought that installing Adobe programs was causing it, but I haven't installed it this time. This time, it started the repair loop upon restarting even without installing anything by Adobe, so it's clearly not that either. I also suspected Windows updates, but this time, I hadn't installed updates -- still doing it.

Any ideas? Do you think not using EUFI and going legacy could be the way to go? And yes, I've tried Windows installations during which I left the system/recovery partitions in place and installations during which I didn't. Nothing at all seems to work so far.

spunk · 08 Feb 2021

I would suggest your Windows installer USB is probably missing some files. Create a new one using a brand new never used USB Flash Drive. Only have one SSD drive plugged in at a time until after Window is installed and do a Clean Install

NavyLCDR · 09 Feb 2021

^^^^I agree with what @spunk posted. Also, do not connect to the internet at all during the install. Disconnect any Ethernet cables and do not connect to WiFi. See if you can reboot 3-4 times with no issues. Then connect to the internet for updates.

Also, if you are installing from a USB flash drive, plug it into a black USB 2.0 port directly off the motherboard (back of computer). It will be more reliable than a Blue USB 3.0 port on the front of the computer.

Also, if you are overclocked, having the base clock frequency set higher than 100 mhz can affect some SSDs. I have an M.2 SATA SSD that doesn't like the base clock set any higher than 101.