Full Diagnostic Tree & Step-by-Step Overview
Your computer powers on but hangs indefinitely. What exactly do you see on your display?
- The Windows logo (or motherboard logo) is present, but the white loading dots are spinning infinitely
- The logo is visible, but the white loading dots are completely frozen or absent
- The system bypasses the logo but throws a Blue Screen of Death (BSOD) crash code (e.g., INACCESSIBLE_BOOT_DEVICE)
A completely frozen logo usually indicates a hardware interrupt lockup. Let's isolate the USB controller bus. Have you disconnected non-essential peripherals?
- I have unpinned all external devices except monitor, keyboard, and mouse, but the freeze persists
- Disconnecting external USB drives or webcams allowed the machine to pass the logo phase
BIOS/UEFI Hand-off Failure Due to Storage Device Controller Conflict
Solution:
Diagnostic Cause
Your system's motherboard firmware (BIOS/UEFI) is attempting to scan external USB mass storage controllers or unmapped device descriptors for a bootable partition during the early POST hand-off phase to the Windows kernel. This causes a complete system hardware interrupt deadlock.
Step-by-Step Fix
1. Isolate the Ports:
Turn off the machine, unplug all external multi-card readers, USB flash drives, high-draw external audio interfaces, or external HDDs/SSDs.2. Modify Firmware Boot Order:
Turn on the PC and tap the entry key (Del, F2, or F12 depending on your motherboard) to enter BIOS/UEFI Setup.Locate the Boot configuration tab.Disable Legacy USB Support or set your first boot priority specifically to Windows Boot Manager on your internal drive rather than the generic generic USB device stack.3. Save and Exit:
Press F10 to save configurations and reboot into the operating system.
To apply any software fixes, we must bypass the broken boot sector and reach the blue Windows Recovery Environment (WinRE) screens. Can you access the 'Choose an option' menu?
- I need instructions on how to force the recovery menu to load
- I am successfully sitting at the blue 'Choose an option' screen now
Triggering Advanced Startup Options Without a Bootable System Desktop
Solution:
Diagnostic Cause
Because the OS cannot initialize its graphical user shell, we must rely on the Windows Boot Manager's built-in emergency fallback protocol, which triggers automatically after detecting three consecutive failed boot sequences.
Step-by-Step Fix
1. Execute Power Interruptions:
Press and hold your computer's physical Power Button for 10 seconds to turn it completely off.Press the power button to boot the machine.As soon as the manufacturer logo or Windows logo appears on screen, press and hold the physical Power Button again for 10 seconds until the machine dies.2. Repeat Cycle:
Repeat this sequence a second time.Turn on the computer a third time. Allow it to run undisturbed. You will see a line of text appear under the logo stating 'Preparing Automatic Repair' or 'Diagnosing your PC'.3. Enter Advanced Options:
When the blue screen loads stating that repair could not restore your PC, click the Advanced Options button to unlock the service menu.
From the Advanced Options environment, let's step down into Safe Mode to determine if the graphics subsystem or custom application drivers are causing the boot freeze.
- Boot into standard 'Safe Mode with Networking' to isolate third-party driver deadlocks
- Safe Mode fails to boot or hangs on the loading files line, requiring command-line recovery
Safe Mode Initialization & Driver/Update Deconfliction
Solution:
Diagnostic Cause
An infinite spinning loading loop usually indicates that the core Windows kernel has loaded successfully, but the system is deadlocking when trying to spin up secondary display drivers (NVIDIA/AMD) or background third-party kernel-level security filters (Antivirus/Anti-cheat software).
Step-by-Step Fix
1. Navigate to Startup Settings:
From the Advanced Options screen, click Troubleshoot > Advanced options > Startup Settings > Click Restart.2. Select Boot Mode:
Upon reboot, a numbered list will appear. Press 5 or F5 to select Enable Safe Mode with Networking.3. Roll Back Broken Drivers (Inside Safe Mode):
Once booted onto the low-resolution Safe Mode desktop, right-click the Start Menu button and open Device Manager.Expand Display adapters, right-click your GPU (e.g., Nvidia GeForce / AMD Radeon) > Properties > Driver tab > click Roll Back Driver (if available) or choose Uninstall Device.4. Remove Recent Updates:
If the issue occurred directly after an update, open Control Panel > Uninstall a program > View installed updates.Locate the latest Microsoft Cumulative Update, click Uninstall, then reboot normally.
If Safe Mode cannot load or you face an INACCESSIBLE_BOOT_DEVICE crash, the file system metadata or boot configuration store is corrupted. Let's resolve this via the Command Prompt environment.
- Execute Automated Boot Record and BCD Store Rebuilds
- Clear Pending Update States That Are Causing Reboot Loops
Corrupted Master Boot Record or Broken BCD Mapping Database
Solution:
Diagnostic Cause
The references pointing to your primary Windows kernel installation directory inside the hidden boot sectors or the Boot Configuration Data (BCD) directory are corrupted, causing the motherboard initialization sequence to loop blindly.
Step-by-Step Fix
1. Open the Recovery Console:
Navigate to Troubleshoot > Advanced options > Command Prompt.2. Run Disk & Master Boot Record Repair Tools:
Run the following commands sequentially, hitting Enter after each line: bootrec /fixmbr
bootrec /fixboot *(Note: If you receive an 'Access is denied' error on modern UEFI systems, run bootsect /nt60 sys first, then retry the command)*
3. Scan and Re-index Windows Installations:
Re-inventory your storage drives by typing: bootrec /scanos
Completely rebuild the configuration metadata array: bootrec /rebuildbcd
If prompted to add the discovered Windows installation to the boot list, type Y and press Enter.4. Run System Verification:
Repair underlying partition block clusters: chkdsk c: /f /rClose Command Prompt, click Continue to boot normally.
Stalled Component Servicing Stack Deadlocking System Initialization
Solution:
Diagnostic Cause
An installation script or system file migration phase within a background Windows Update package has crashed or hit an unresolvable file lock, trapping the system in an execution script queue every time the boot loader starts up.
Step-by-Step Fix
1. Open Command Prompt from Advanced Options:
Click Troubleshoot > Advanced options > Command Prompt.2. Query Pending Packages via Custom DISM Matrix:
Check for pending updates staged to your operating system drive (assuming C: is your active Windows partition): DISM /Image:C:\ /Get-Packages
3. Revert Pending Actions:
Tell the servicing architecture to discard all interrupted update configurations: DISM /Image:C:\ /Cleanup-Image /RevertPendingActions
4. Run sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows to repair any underlying system files broken by the failed update, then close out the environment and restart the PC.