I built my first AMD-based PC and am having trouble performing a clean Windows 11 installation. The installer usually reaches about 75% and then the computer restarts. Afterward, it either tells me to remove the installation media and continue—which sends me back to the BIOS with no internal drive available as a boot option—or it starts the installation over again. I wiped and reformatted the target drive before installing. The BIOS display itself is clear and readable, and changing the boot order or unplugging other USB devices has not solved the problem.
The system sometimes crashes with different stop errors that disappear too quickly to record. Windows eventually installed, but the crashes continued. The SSD manufacturer's diagnostic reports that the drive is healthy, while Windows Memory Diagnostic reports that hardware problems were detected. The system uses an ASRock 850M-WiFi motherboard, Ryzen 5 9600K processor, 32GB of Corsair Vengeance DDR5 in two 16GB modules, and a Crucial P3 Plus 1TB M.2 SSD. What should I test next, and is defective or unstable RAM the likely cause?
3 Answers
The memory test reporting hardware problems is a strong lead. Shut the PC down, remove one RAM module, and test with the other module by itself. Repeat the test with each stick and try the recommended single-stick slot from the motherboard manual. If one module fails consistently, it is probably defective; if both pass alone but fail together, check the slots, BIOS settings, and memory compatibility. Leave any overclocking or EXPO memory profile disabled while troubleshooting.
Reset the BIOS to its defaults and update it if the board is running an older version, especially with a newer processor and DDR5 memory. Avoid enabling EXPO until Windows is stable. Also reseat both memory sticks and the M.2 drive, and confirm the drive is detected in the firmware. A healthy SSD cannot compensate for unstable memory, since corrupted data can cause installation failures and seemingly random stop codes.
If Windows reaches the desktop, check C:WindowsMinidump for crash files. WinDbg or another dump analyzer can identify the stop code and the driver involved. Make sure the chipset, graphics, storage, and network drivers are current, but hardware errors from Windows Memory Diagnostic should be investigated before assuming drivers are the main problem.
That makes sense. I was initially focusing on the SSD because the installation kept failing, but the memory diagnostic result points more directly at the RAM or its settings.