Windows installation is leading to boot failures.
Windows installation is leading to boot failures.
Hi, since switching from a 2060 to a 3070 about a year ago, I've faced recurring crashes. The problem intensified over time, and after each failure I'd have to replace the RAM, GPU, and reset the CMOS battery just to get the system running again. This happened multiple times, most recently on Sunday when I returned from a two-month absence and found it wouldn't boot. Recently, while playing Oblivion Remastered—possibly linked to its new release status—I experienced another crash. I suspect the issue lies in software rather than hardware. I've checked the GPU power cable, tested RAM slots, and confirmed no hardware faults. My motherboard displays LEDs for CPU, RAM, GPU, and BOOT, all indicating successful starts. However, after the Aorus logo appears, the PC crashes again. After entering BIOS, I noticed everything appears correctly, including boot drives and hardware status. When I tried to open the BOOT menu during a restart, it crashed immediately. I then switched to using the Windows Boot Manager on my Samsung 970 Evo drive, but it also failed. Eventually, I created a Windows installation USB from an old stick and connected it via monitor, keyboard, and USB. Instead of the BIOS prompt, a loading circle appeared with "Starting Automatic Repair" text, followed by a crash. Now, whenever I power on the PC, that same loading circle remains below the Aorus logo, but without any instructions, before the system crashes. Any guidance or advice would be invaluable. I'm at a loss for what to do next.
High-detail configuration: Ryzen 7 3700X paired with stock cooler from Gigabyte Aorus B550 Pro AC Wi-Fi MSI RTX 3070 graphics. Includes 8GB and 32GB DDR4 memory, Corsair Vengeance RAM at 3200MHz. Powered by a 1TB Samsung 970 EVO SSD and a Crucial P3 M.2 4TB drive. Comes with a boot drive from Seagate HDD.
The loading ring indicates you've surpassed BIOS and the system is attempting to boot your operating system, which appears corrupt. Verify your boot sequence (ensuring the flash device is first), then regenerate Windows installation media on a functional PC if possible. If you still cannot launch Windows setup, consider using an alternative flash memory.
Your wireless keyboard isn't being recognized, even with the dongle and USB cable. You can still access BIOS by restarting your PC in safe mode or using a recovery USB, then adjust the boot order without needing a physical keyboard. If that doesn’t work, testing another drive might be necessary.
It might be quicker to switch to another flash drive. You can disconnect the boot drive (like the 970 Evo) while the computer is off—it won’t proceed past POST because nothing is left to load. Once it’s off, you might enter BIOS, but I’m not sure if your support guide will work then. If it does, you’ll need to adjust the boot order since the 970 Evo is missing. You could also reset the CMOS, though this would erase all BIOS settings and might not make the drive the first choice again. Personally, I’d retrieve an older wired one, borrow or buy another. EDIT: Make sure your wireless model isn’t detected; if the timeout to enter BIOS is short, press keys quickly as soon as the PC powers on.
Thanks, yes. My keyboard didn’t connect properly; it shows an LED that flashes when disconnected and stays solid when plugged in. I removed the CMOS battery and used a wired keyboard instead. When I powered on my PC, the LED stayed stuck on 'BOOT'. The monitor remained off, but after a short while it started working again. Eventually I accessed BIOS, set the UEFI USB drive as the boot device, saved and exited. Then the Aorus logo appeared without a loading screen or text, giving me a brief sense of hope before it crashed once more. I don’t have a larger USB drive for a Windows installer, and I’m worried about doing this today since it’s a public holiday in Australia. Any suggestions? Thanks again.
Progress has been made finally. You might attempt recreating the windows installation media on your existing flash drive. Consider using Rufus rather than the Windows Media Creation utility to generate the bootable USB. Downloading the Windows ISO from the official Microsoft site is also recommended.
Are you wondering if the new GPU is putting pressure on the MOBO? It seems problems started gradually after the upgrade, which makes Occams Razor relevant. I think it’s likely a tower setup and the newer GPU is slightly heavier than before. If there are tiny cracks in the traces or MOBO, they might not cause issues right away, but when temperatures rise and heat expands naturally, it could lead to shorts or connection loss. I’ve experienced this before—once from an impact on the MOBO and again when the CPU heatsink added extra weight.