Windows 11 intermittently boots, but Windows Recovery and independent installation media freeze during startup, possible firmware or hardware initialization issue

John Doe 0 Reputation points
2026-10-27T09:29:11.7833333+00:00

Hello,

I'm experiencing a persistent startup issue with my Windows 11 desktop. I'm looking for help determining whether the problem is related to Windows initialization, UEFI firmware, or underlying hardware.

System specs

  • Motherboard: Gigabyte B550 AORUS ELITE V2, Revision 1.0

CPU: AMD Ryzen 5 5600G

RAM: 32GB Corsair Vengeance LPX DDR4 (2×16GB)

GPU: NVIDIA RTX 3070 Ti

Windows system drive: WD Blue SN580 2TB NVMe

Secondary drive: Crucial P5 Plus 500GB NVMe

BIOS: Recently updated successfully from F12 (January 2021) to F17

OS: Windows 11

issue

My desktop frequently freezes or restarts while starting Windows, usually around the motherboard logoo, Windows loading animation, or "Preparing Automatic repair" screen

The loading animation sometimes freezes indefinitely while the fans continue running. Other times, the system restarts and repeats the boot process.

However, Windows sometimes boots successfully. When it does, I can use the computer for several hours, occasionally overnight, including running demanding applications. Rare hard freezes have also occurred during normal Windows sessions, but this time the problem has gootten worse and I cannot start it up at all without it repeating the boot process over and over.

things already done

  1. I Repaired an earlier EFI/BCD boot configuration problem caused by SSD cloning. Rebuilt the boot configuration on the proper FAT32 EFI partition and corrected the Windows Recovery Environment configuration. The current symptoms persisted.

Reset BIOS settings and tested various CPU and power-management options, with XMP disabled.

Tested individual RAM modules. A previous Memtest86+ pass reported no errors, although that pass only covered 16GB due to a temporarily unseated module.

Physically removed the RTX 3070 Ti and tested using the Ryzen 5 5600G's integrated graphics. The startup issue persisted.

Physically removed the main 2TB Windows SSD and attempted to boot from Microsoft's Windows installation USB. The installer still failed to start properly. The secondary Crucial NVMe remained connected.

Tested the exact same Windows installation USB on a separate laptop. It successfully reached the Windows recovery interface.

Also attempted booting Linux Mint installation media on the desktop. This failed during startup.

Updated the Gigabyte motherboard BIOS from F12 to F17 using Q-Flash Plus. The updated version is confirmed in BIOS, but the startup failures remain.

Tested the USB boot entries through the Gigabyte F12 boot menu. The UEFI entry sometimes fails to launch, while the other USB entry reaches the Windows logo before freezing or resetting.

Observations

The motherboard BIOS interface itself is consistently accessible.

The machine can sometimes sustain long Windows sessions despite severe startup unreliability.

The problem occurs even when the installed Windows system drive and dedicated GPU are removed.

The Windows installation USB is functional on another computer.

Windows Automatic Repair and external recovery environments cannot reliably initialize.

Question

What could cause Windows 11 installation/recovery media to hang before reaching Setup on this particular computer, even without the installed Windows drive connected?

Could this indicate an ACPI, UEFI, CPU initialization, memory-controller, or storage-controller problem?

Are there diagnostic approaches that don't require successfully starting Windows or Windows Recovery?

Can Microsoft recommend any way to distinguish Windows boot-environment incompatibility from failing motherboard, CPU, RAM, or PSU hardware before replacing components?

I want to preserve the data on my NVMe drives and avoid unnecessary Windows reinstallation, especially since independent installation media also fails.

Thank you for any technical guidance.

Windows for home | Windows 11 | Performance and system failures
0 comments

1 answer

Sort by: Newest
Most helpful Newest Oldest

  1. AI answer

    2026-10-27T09:29:54.7633333+00:00

    The behavior points away from a Windows-only boot configuration problem and toward firmware or hardware-level startup failure.

    The strongest indicators are:

    1. The problem occurs even when the Windows NVMe drive is removed.
    2. Windows installation and recovery media also freeze before Setup loads.
    3. Linux installation media also fails during startup.
    4. BIOS setup remains accessible.
    5. Windows can sometimes run for hours once it does start.

    From the documented Windows startup model, a failure this early means the system is likely not consistently getting through the preboot or boot loader stages. Microsoft guidance separates startup into PreBoot, Windows Boot Manager, OS Loader, and Kernel phases. If external boot media also hangs, the issue is no longer limited to the installed Windows boot files or BCD.

    A practical way to interpret the symptoms is:

    • If the system freezes at the motherboard logo or before Windows Setup appears, suspect the PreBoot phase.
    • If the screen is black, stuck, or repeatedly restarts while trying to load boot media, suspect the transition into the Boot Loader phase.
    • Because Linux media also fails, the issue is more consistent with firmware initialization or hardware instability than with Windows Recovery itself.

    Useful diagnostic approach without relying on Windows:

    1. Start with the minimum hardware configuration
      • Keep only motherboard, CPU, one RAM module, integrated graphics, keyboard, and the USB installation media.
      • Disconnect both NVMe drives during testing to protect data and remove storage as a variable.
      • Since the issue persists without the RTX 3070 Ti, continue testing on the Ryzen 5 5600G integrated graphics.
    2. Keep BIOS at default settings
      • Since BIOS settings were already reset and XMP disabled, continue with default settings only.
      • Avoid changing multiple power or CPU options at once.
    3. Use installation media only to test boot phase behavior
      • Boot from Windows installation media.
      • If the system reaches Install Windows, select Next > Repair your computer > Troubleshoot > Advanced options > Startup Repair.
      • In this case, the more important result is whether the machine can consistently reach that screen. If it cannot, that supports a pre-Windows cause.
    4. Classify the failure by phase
      • Freeze at vendor logo or before boot media loads: likely PreBoot.
      • Freeze at Windows logo / loading animation / “Preparing Automatic Repair”: likely Boot Loader.
      • A black screen with blinking cursor or errors such as BCD missing, boot sector missing, or Bootmgr missing would fit Boot Loader corruption, but that does not match the broader cross-media failure already described.
    5. If Windows ever starts, use a clean boot to test later-phase software conflicts
      • This is only relevant if the machine becomes stable enough to boot Windows again.
      • Use msconfig, select Selective startup, and test services one at a time.
      • This helps only for kernel/service-phase issues and does not explain Linux and Windows installer media both failing.
    6. Treat intermittent successful boots as possible instability, not proof of software health
      • Microsoft guidance for unexpected restarts and stop-code style failures notes that hardware devices, drivers, or software can cause restart behavior.
      • In this case, because recovery and installer media also fail, hardware or firmware remains the stronger direction.

    What this most likely helps distinguish:

    • Less likely: damaged Windows installation, damaged BCD, or WinRE-only corruption.
    • More likely: motherboard firmware behavior, memory path instability, CPU/platform initialization instability, or another hardware-level startup problem.

    About preserving data:

    • Keeping both NVMe drives disconnected during boot-media testing is the safest diagnostic step.
    • Do not reinstall Windows while installation and recovery media are still freezing, because that does not address the apparent root cause.

    What Microsoft guidance supports here:

    • Determine the startup phase first.
    • Use installation media and WinRE only if the machine can reliably reach them.
    • If the issue survives removal of the Windows drive and affects external boot media, the problem is beyond normal Windows boot-file repair.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.