A computer may not boot because power, hardware, drive faults, firmware settings, or damaged startup files break the startup chain.
“Boot” is a chain, not one switch. Power reaches the board, firmware runs checks, video turns on, then the system loads an operating system from storage.
When that chain breaks, the symptom you see is often one step away from the real cause. Use these checkpoints to narrow it down fast and avoid random part swaps. If you’re stuck, the same question keeps coming up: what causes a computer not to boot up?
Fast Checks Before You Open Anything
Start with steps that take minutes and don’t touch files. Each step tries to change the symptom. A changed symptom is a solid clue.
- Test wall power: try a different outlet, skip the power strip, and press the strip’s reset if it has one.
- Unplug extras: remove USB drives, hubs, printers, memory cards, and external disks.
- Try a clean display path: swap the HDMI/DP cable, try a second monitor, and switch ports.
- Full power drain: shut down, unplug, hold the power button for 15 seconds, then reconnect.
- Watch the signs: fan spin, caps lock light, beeps, LED blink codes, and any logo screen.
| Startup Symptom | Most Common Cause Area | Fast Check That Narrows It |
|---|---|---|
| No lights, no fan, no sound | Outlet, cable, PSU/charger, power switch | New outlet and cable; laptop: AC only test |
| Fans spin, screen stays black | Monitor/cable, GPU, RAM seating | Other monitor/cable; try iGPU port if available |
| Beeps or blinking LED code | Pre-boot hardware check failure | Count beeps/blinks; remove added parts |
| Logo shows, then freezes | Device check hang, storage detection | Boot with all USB unplugged |
| “No boot device” message | Boot order, loose cable, missing boot entry | Enter BIOS/UEFI; confirm the drive is listed |
| Boot loop (restarts on repeat) | RAM instability, PSU sag, file damage | One RAM stick test; then OS recovery tools |
| Spinning dots forever | Update/driver crash, disk errors | Try recovery menu; undo the last change |
| Blue screen early in load | Driver, RAM, storage errors | Disconnect new hardware; memory test |
| Clicking HDD sound | Failing hard drive | Stop repeated boots; plan data copy |
Causes Of A Computer Not Booting Up By Symptom
Pick the branch that matches what you see. If your symptom shifts after a step, follow the new branch. You just moved to a different link in the chain.
No Lights Or Fans
This points to the power path before the motherboard can run firmware checks.
- Outlet and strip: test the outlet with a lamp. Bypass the strip.
- Cable and plug fit: reseat both ends of the power cord until it’s snug.
- Desktop PSU: a failing PSU can show zero signs, or it can start for a split second and stop.
- Laptop charger: try another compatible charger if you can borrow one.
Fans Spin But The Screen Is Black
This can be “no video” or “no boot.” Separate the two first.
- Try another screen path: one monitor, one cable, one port.
- Switch outputs: desktop with built-in graphics: test the motherboard video port.
- Reseat the GPU: desktop only; check GPU power plugs click into place.
- Reseat RAM: desktop only; try one stick at a time in the board’s primary slot.
Beeps, Blink Codes, Or A Frozen Logo
Beeps and blink codes mean the firmware hit a failed check. A frozen logo often means it’s stuck while checking a device.
- Memory faults: a loose stick, mixed kit timing, or a bad module can block startup.
- USB faults: a bad hub can lock pre-boot checks. Boot with all USB unplugged.
- Storage hang: a drive can stall detection and freeze the logo screen.
What Causes A Computer Not To Boot Up?
Most cases land in five buckets. Each bucket breaks a different step, so the best next action depends on where you’re stuck.
- No power delivery: outlet, cable, PSU/charger, battery, power switch.
- Pre-boot check failure: RAM, GPU, CPU, board, shorted device.
- Firmware can’t find a boot target: boot order, missing boot entry, drive not detected.
- Drive can’t load the system: boot records, file damage, failing SSD/HDD.
- System starts then crashes: drivers, updates, disk errors, heat shutdowns.
Firmware And Boot Settings That Block Startup
BIOS/UEFI settings can stop a healthy machine from reaching the operating system, often after a firmware update, a reset, or a drive clone.
Boot Order And Boot Entries
If the system tries the wrong device first, you may see “no boot device,” or it may try a network boot. Set the internal drive (or the “Windows Boot Manager” entry, if shown) as the first option.
UEFI systems keep boot choices in firmware variables. The UEFI specification’s Boot Manager section explains how firmware uses a boot order list to decide what to load; see UEFI Boot Manager behavior.
Secure Boot Mismatch
Secure Boot checks that the bootloader is signed. If you swapped drives, restored an image, or installed another operating system, Secure Boot settings can block boot. A quick test is to switch Secure Boot off, try one boot, then switch it back on if you rely on it.
Clock Reset And CMOS Battery
On desktops, a weak CMOS battery can reset settings after the PC is unplugged. If the clock resets and boot order keeps changing, replacing the coin cell can stop repeat failures.
When Windows Starts To Load Then Fails
If you reach a logo screen and then hit a loop, a repair screen, or an error code, early hardware checks are mostly passing. That shifts attention to the drive and startup files.
Check That The Drive Is Detected
Enter BIOS/UEFI and confirm your SSD/HDD shows up. If it vanishes between boots, treat it as a failing part and move to data-first steps.
Windows Recovery Tools
Windows Recovery (WinRE) includes tools for startup failures. Microsoft’s troubleshooting article explains common boot issue patterns and the role of Startup Repair; see Windows boot issues troubleshooting.
Run Startup Repair once. If it fails, think back to the last change: an update, a driver, a new SSD, or a sudden power loss during updates. Undoing that one change often beats a reinstall.
Loose Cables And NVMe Seating
On desktops, SATA cables can loosen. Reseat both ends. NVMe SSDs can lift if the screw isn’t snug, so reseat the drive if it’s not detected.
Failing Drives And Data-First Choices
Hard drives may click or take a long time to show up. SSDs can fail without noise. If you can’t lose the files, avoid endless boot attempts. Pull the drive, attach it to another computer with a USB adapter, and copy what you can before running repair commands that write to disk.
Laptop-Specific Boot Stops
Laptops can look dead even when the main board is fine, because power can be blocked upstream. A battery that’s failed short can stop charging. A charging port can loosen. Some models also hang after sleep or hibernate and won’t wake cleanly.
Try an AC-only start: shut down, unplug, hold the power button for 15 seconds, then plug in AC and start. If the laptop starts on AC but won’t run on battery, the battery or charging path is the likely culprit.
If the fans spin but there’s still no image, check for a faint screen glow. A lit-but-blank panel often points to the display path, not storage. An external monitor test separates “no video” from “no boot” in one step.
Last, listen for repeated short power cycles. A laptop that turns on for a second and shuts off may be tripping on a short, a failed fan, or a heat sensor reading. In that case, repeated starts can raise the repair bill.
| Order | Safe Step To Try | What It Tells You |
|---|---|---|
| 1 | Unplug all USB devices and external drives | If it boots, a device or boot order caused the block |
| 2 | Swap outlet and power cable; bypass strip | If it powers on, wall/strip/cable was the break |
| 3 | Try another monitor and video cable | If video returns, the PC may have been booting |
| 4 | Enter BIOS/UEFI and check drive detection | If no drive, reseat cables/NVMe; drive may be failing |
| 5 | Boot with one RAM stick, then swap sticks | If one works, you found a bad module or slot |
| 6 | Set internal drive or boot entry first | If it boots, firmware was pointing to the wrong target |
| 7 | Run WinRE Startup Repair once | If fixed, startup files were damaged |
| 8 | Copy data from the drive using another PC | If unreadable, plan replacement and recovery |
When To Stop And Hand It Off
Some signs point to board-level faults that aren’t a good home project. If you smell burnt plastic, see scorch marks, or the system shuts off the instant it’s powered, stop and unplug it.
If liquid was spilled, don’t keep trying to start it. Repeated power-on attempts can spread damage.
If the computer is under warranty, opening the case can void coverage. Write down the symptom, list the steps you tried, and hand it to a repair desk with clear notes.
Habits That Cut Down Repeat Boot Failures
- Use a surge protector you trust, and replace old strips that trip often.
- Shut down cleanly before moving a desktop so cables and cards stay seated.
- Keep vents clear and clean dust so temps stay steady.
- After major updates, let the first reboot finish even if it feels slow.
- Back up files so a drive failure becomes a hassle, not a disaster.
If you’re still stuck, rerun the chain from the top and match your symptom to the table. Your answer to “what causes a computer not to boot up?” should now be narrow enough to act on.