Interactive Troubleshooter

Published: Aug 31, 2026

Updated: Sep 1, 2026

Interactive: PC Won’t Boot - Power, RAM, or OS?

Time: 15 mins Level: Beginner

By StepDiag Engineering Team

Reviewed by Ibraheem Taofeeq Opeyemi

Interactive root-cause decision tree to systematically isolate PC boot failures across Power Supply Units, memory POST training, corrupt BIOS firmware, and damaged OS bootloaders. Follow precise hardware and software diagnostics to identify component faults or restore system bootability.

Full Diagnostic Tree & Step-by-Step Overview

When you press the PC power button, what primary physical response occurs?

Complete dead response: No fans spin, no motherboard LEDs turn on, and no sound is emitted
Power lights turn on and fans spin, but there is no display output or POST screen (Debug LED / Beep code present)
Displays motherboard logo, but hangs indefinitely, blue-screens (BSOD), or enters an automatic repair boot loop

How does the power supply unit (PSU) or system react during startup testing?

PSU fan does not spin at all, even when tested directly or when shorting power switch pins
Fans spin or lights click on for a split second, then the system shuts off immediately

Diagnose Power Delivery Failure, Bad PSU, or Faulty Front Panel Switch

Solution:

Root Cause: Dead PSU, Tripped Internal Thermal Fuse, or Broken Front Panel Switch Header

A completely non-responsive PC points to an interrupted primary AC input, a failed power supply unit (PSU) internal rail, or a physically damaged front panel switch (PWR_SW) that fails to bridge motherboard sensing pins.

# Step-by-Step Fix:

Verify AC Main Power & Wall Outlet:

Ensure the rear PSU rocker switch is set to the 'I' (ON) position.

Test the wall outlet with a known working appliance and ensure the C13 power cable is firmly seated into the PSU socket.

Bypass the Chassis Power Switch (PWR_SW):

Unplug the front panel switch connector from the motherboard JFP1 / PANEL header.

Momentarily bridge the two PWR_SW pins using a flathead screwdriver. If the PC turns on, the chassis power button or cable is defective.

Perform PSU Paperclip Jump Test:

Turn off the PSU switch and disconnect all cables from motherboard and GPU components.

Insert a paperclip to bridge Pin 16 (PS_ON - Green wire) and any adjacent Ground pin (Black wire) on the 24-pin ATX connector.

Flip the PSU switch back ON. If the PSU fan does not spin, the power supply unit has suffered internal rail component failure and must be replaced.

Clear Motherboard Short Circuits and Reset Power Supply Protection

Solution:

Root Cause: Short-Circuit Protection (SCP) or Over-Current Protection (OCP) Trigger

When a power supply detects a direct short between a +12V/+5V/+3.3V power rail and the ground plane (or a pinched wire / misplaced chassis standoff), the internal protection circuit cuts power within milliseconds to prevent fire or hardware destruction.

# Step-by-Step Fix:

Disconnect External and Internal Peripherals:

Unplug all USB devices, RGB headers, front-panel audio cables, SATA drives, and PCIe expansion cards.

Attempt to power on with only the 24-pin ATX motherboard power cable and 8-pin EPS CPU power cable connected.

Isolate EPS 12V CPU & PCIe Power Short Circuits:

Unplug the 8-pin CPU EPS cable near the CPU socket. If the system stays powered on without displaying a screen, the short circuit is located within the motherboard VRM or CPU socket.

Ensure PCIe power cables are native 8-pin connectors and not EPS cables mistakenly forced into the GPU.

Inspect Motherboard Chassis Standoffs:

Remove the motherboard from the computer case and lay it on an anti-static surface or cardboard box (out-of-case benchmark test).

Check for extra metal chassis standoffs touching bare motherboard traces beneath the board.

What hardware diagnostic indicator is displayed on your motherboard (Q-LED, Debug Code, or Beep Codes)?

DRAM LED remains lit solid, or system emits memory error beeps (e.g., 3 long beeps)
CPU or VGA LED remains lit solid, or system loops continuously through power restarts

Reseat Memory Modules, Clear CMOS, and Correct Channel Topology

Solution:

Root Cause: Memory Training Failure, Unstable XMP/EXPO Timings, or Contact Oxidation

During the Power-On Self-Test (POST), the BIOS checks and trains the RAM modules. Contact oxidation, physical displacement, improperly populated dual-channel slots, or unstable overclocking profiles (XMP/EXPO) will prevent the memory controller from completing initialization.

# Step-by-Step Fix:

Perform CMOS Hardware Reset:

Disconnect the AC power cord from the wall.

Remove the circular CR2032 coin-cell battery from the motherboard for 5 minutes, or short the CLR_CMOS / JBAT1 jumper pins for 10 seconds using a metal screwdriver to clear invalid BIOS timings.

Single-Stick Isolation & Slot Verification:

Remove all RAM sticks.

Insert a single RAM stick firmly into primary slot A2 (usually the second slot away from the CPU socket) until both retention latches click shut.

Power on and allow up to 3 minutes for initial DDR5 memory training.

Clean RAM Gold Contacts:

Wipe the golden edge pins of each RAM stick with a pencil eraser or isopropyl alcohol (>90%) to clear microscopic surface oxidation.

Execute BIOS Flashback and Inspect CPU Socket Pins / GPU Cables

Solution:

Root Cause: Corrupted BIOS EEPROM, Bent Socket Pins, or Unsupported CPU Microcode

When the CPU or VGA LED stays lit, the system cannot load CPU microcode or initialize graphics. This occurs if a new CPU is installed on an older BIOS version, BIOS EEPROM binary data is corrupted, or pins in the CPU socket are damaged.

# Step-by-Step Fix:

Execute USB BIOS Flashback (No CPU/RAM required):

On a working computer, download the latest stable BIOS firmware from the official motherboard manufacturer page.

Rename the downloaded BIOS binary file according to manufacturer requirements (e.g., creative.rom or MSI.ROM).

Format a USB flash drive as FAT32, paste the BIOS file onto the root directory, insert it into the dedicated BIOS Flashback USB port, and press the rear Flashback button for 3 seconds.

Inspect CPU Socket & PCIe Power Delivery:

Unmount the CPU cooler and lift the CPU out of the socket.

Use a flashlight and magnifying lens to check the LGA socket pins (or PGA CPU pins) for bends or thermal paste contamination.

Ensure the GPU is fully seated in the top PCIe x16 slot and connected via dedicated 12VHPWR / 8-pin power cables.

At what exact point during operating system startup does the failure happen?

Fails with 'No Bootable Device Found' or BSOD error INACCESSIBLE_BOOT_DEVICE
Stuck on loading animation circle or continuously loops 'Preparing Automatic Repair'

Repair Windows EFI/BCD Bootloader or Correct AHCI/NVMe/RAID Storage Mode

Solution:

Root Cause: Corrupted Boot Configuration Data (BCD) or SATA/NVMe Controller Mode Mismatch

An INACCESSIBLE_BOOT_DEVICE error or missing boot option occurs when the BIOS storage mode is changed (e.g., AHCI switched to RAID/VMD), or when the Boot Configuration Data store inside the hidden EFI System Partition (ESP) is damaged.

# Step-by-Step Fix:

Verify BIOS Storage Controller Settings:

Enter BIOS setup (Del or F2 during boot).

Navigate to Storage Configuration / SATA Mode and verify settings. If Windows was installed under AHCI, ensure Intel VMD / RAID mode is disabled.

Ensure Boot Mode is set to UEFI (disable CSM/Legacy mode for modern Windows 10/11 installs).

Rebuild EFI Partition and BCD Data via WinRE Command Prompt:

Boot from a Windows Installation USB media and click Repair your computer > Troubleshoot > Command Prompt.

Execute the following commands in order to repair the boot partition:

cmd
   diskpart
   list disk
   select disk 0
   list partition
   select partition 2
   assign letter=V:
   exit

Re-create the BCD boot files:

cmd
   cd /d V:\EFI\Microsoft\Boot\
   bootrec /fixboot
   ren BCD BCD.bak
   bcdboot C:\Windows /l en-us /s V: /f ALL

Run System File Checker (SFC/DISM) and Repair Operating System Kernel

Solution:

Root Cause: Corrupted Operating System System Files or Storage Drive Failure

When Windows hangs during initialization or loops in automatic repair, core system drivers, Windows registry hives (SYSTEM / SOFTWARE), or kernel executables (ntoskrnl.exe) have become corrupted due to unexpected shutdowns or NAND flash wear.

# Step-by-Step Fix:

Run Offline System File Checker (SFC) in Command Prompt:

Boot into Windows Recovery Environment (WinRE) using a bootable Windows Installation USB.

Open Command Prompt under Advanced Options and execute:

cmd
   sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows

Execute Deployment Image Servicing and Management (DISM) Repair:

Repair offline system components using the Windows installation media as source:

cmd
   dism /Image:C:\Windows /Cleanup-Image /RestoreHealth

Test SSD/HDD Hardware Health:

Execute disk check to isolate bad sectors or flash storage read errors:

cmd
   chkdsk C: /f /r

If errors persist after repairs, perform a clean OS reinstallation or replace the failing boot drive.

Related Diagnostic Guides

Fix Copy text (Ctrl-C or context menu) not working on browsers

Windows Credential Guard Blocking App Exclusions: How to Fix It

WordPress Redirecting to Spam Websites: How to Fix It

Malicious Browser Extensions: How to Detect and Remove Them

Unreal Engine Shader Compilation Stuttering: How to Fix It

Subscribe to StepDiag

Embed Guide on Your Website