PC won't boot at all? 10–30 min safety-first checklist

Start by deciding whether the PC is getting power. Most 'no boot' problems are power or early hardware-initialization issues you can narrow with a short, safety-first triage. Follow a 10-minute exterior checklist, then do a few reversible internal tests. If the system powers on but won’t load the OS, use rescue USB media to preserve data.

Quick overview and how long this will take

This is a safety-first troubleshooting path for a desktop or laptop that refuses to start. It begins with exterior checks you can do without opening the case, moves to a few reversible internal tests, then to rescue USB steps to save data if needed.

Expected outcomes: the system boots again; you reach a reproducible failure to hand to a technician; or you copy critical files to external media before escalation. Plan 10–30 minutes for the exterior and minimal internal checks, and add 20–60 minutes if you must make and use a rescue USB.

Tools to have ready:

• a working phone or second computer
• a flashlight
• a Phillips screwdriver set
• an external USB drive for backups

Safety first — stop if you see these danger signs

Unplug the machine from AC before opening a case. For laptops with removable batteries, remove the battery first.

Ground yourself by touching a metal part of the case before touching components. An anti-static wrist strap is safer when available.

Stop and call a technician if you find scorched connectors, ruptured or bulging capacitors, melted plastic, or a strong acrid odor.

If you encounter an active electrical hazard or fire, evacuate and call emergency services.

Symptom checklist: name what you actually see

Start by describing exactly what happens when you press the power button and when it happens. Those details decide the next steps.

• No lights, no fans, no beeps: the motherboard is not receiving power. Suspects: outlet, PSU (desktop), AC adapter or DC jack (laptop), internal battery, or power button.

• Fans spin and lights on but no display: power reaches the board but POST, graphics, or firmware may fail. Suspects: GPU, RAM, motherboard, or firmware.

• Beeps, flashing LEDs, or POST codes: the motherboard is reporting an error. Note the exact beep pattern, LED color, and any POST code shown.

• Lights but no OS activity (no drive LED activity, no BIOS): the system may be stuck before boot or the storage device or boot configuration may have failed.

Write down exact observations (LED colors, fan behavior, beep sequence, and timing). Those details help remote support or a repair technician.

Before you start: applicability and stop conditions

This guide applies to home and small-office desktops and laptops you can safely access with basic tools. Stop if you are uncomfortable opening the case, encounter glued or unusual fasteners, or see any danger signs from the Safety section.

• Preconditions: a safe, dry workspace, a screwdriver, and the ability to disconnect power.

• When to stop and call a professional: smoke, heat, burning smell, swollen battery, visible electrical damage, or clicking/grinding drive noises when the drive contains irreplaceable data.

• Data priority: if the drive likely holds irreplaceable files, consider copying the drive with an adapter or calling a data-recovery specialist before making aggressive repairs.

10-minute exterior triage — safest next checks anyone can do

Do the steps in order. Stop and re-evaluate after any step if the symptom changes.

1. Verify the outlet and power source.

• Plug a lamp or phone charger into the same outlet to confirm it supplies power.

2. Confirm the power cable and external switches.

• If you use a power strip or UPS, bypass it and plug the PC directly into the wall. Swap the power cable with a known-good one.

3. Desktop: check the PSU rear switch is ON.

4. Laptop: remove any removable battery and try AC power only. If the battery is internal, leave the laptop unplugged for 60 seconds, then connect AC power and try to start.

5. Power-button reset.

• Hold the power button for 15–30 seconds with power removed, then reconnect power and try to start.

6. Disconnect peripherals.

• Unplug printers, USB drives, docking stations, external GPUs, and other peripherals; a shorted peripheral can prevent startup.

7. CMOS/RTC reset (exterior-friendly).

• If the manufacturer documents an external CMOS reset button or pinhole, use that. If there is no documented exterior method, skip internal RTC battery removal unless you’re comfortable opening the device.

Expected results: restoring outlet power, replacing a bad power cable, or toggling the PSU switch will often bring lights or fans back. If nothing changes, proceed to minimal internal checks.

Minimal internal checks a confident non-expert can do

1. Open the case or access panel and ground yourself.

2. Do a visual inspection: look for loose cables, scorch marks, bulging capacitors, or disconnected power connectors.

3. Reseat RAM.

• Remove all RAM modules.

• Insert one module into the primary slot and try to power on.

• If no change, try each module alone in each slot, one at a time.

Expected result: getting a POST beep, BIOS screen, or different behavior with a particular module or slot indicates a faulty module or slot.

4. Test graphics (desktop).

• Remove the discrete GPU and connect the display to the motherboard video output.

Expected result: if video appears now, the GPU or its power/slot is likely the problem.

5. Disconnect storage drives.

• Unplug SATA power/data and remove NVMe drives if accessible, then try to power on.

Expected result: a drive short rarely prevents POST, but removing drives rules out a drive-related short or electrical fault during diagnosis.

6. PSU basic check (desktop only).

• With the PSU disconnected from the motherboard, short the green wire PS_ON to any black ground wire on the 20/24-pin connector to see if the PSU spins up.

Expected result: a PSU that powers up under this test can still fail under load; if the PSU runs but the system won’t POST, continue testing other parts.

If you see scorch, smoke, or rapid heating during any internal check, stop and call a technician.

Boot from rescue USB and how to protect your data

If the machine powers but the OS won't start, use rescue media to inspect and copy files before repairs.

1. On a working computer, download a current recovery image from your OS vendor or a reputable rescue distro and create a bootable USB following the vendor's instructions.

2. Insert the rescue USB and an external USB drive for backups into the problem PC, then use the BIOS/UEFI boot menu to start from USB.

3. In the rescue environment, use the file manager to copy Documents, Desktop, Pictures, and any other critical folders to the external drive.

Expected result: if you can read and copy files, the storage media is at least partially readable and your data is likely recoverable.

4. Run file-system checks or startup-repair tools from the rescue media only after backing up critical files.

If the rescue environment cannot see the drive or shows mechanical errors (clicking/grinding), avoid further power cycles and consult a data-recovery specialist for drives with irreplaceable data.

How to tell the fix worked and what to do next

Use these concrete checks to confirm a repair.

1. Successful POST or firmware screen.

• You hear the expected single POST beep or see the manufacturer logo and can enter BIOS/UEFI.

2. BIOS/UEFI is reachable and responsive.

• The keyboard works inside the firmware screen and settings are visible.

3. OS loads.

• You reach the login screen and can open files.

If these succeed, decide whether to run OS repairs (startup-repair, SFC, reinstall) or replace the failed hardware part. After replacing hardware, perform several cold boots and a short stress test or normal use. Back up important files immediately and log the steps you took and the observed results so a technician can continue if problems recur.

When to stop and call a technician or data-recovery service

Call professional help immediately if you see smoke, smell burning, find bulging capacitors, or if a drive with critical data shows mechanical failure (clicking or grinding).

Before you call, document:

• the exact symptom and when it happens
• any beep or LED codes and the steps you tried (power-cable swap, RAM reseat, rescue USB)
• model and serial numbers of the PC and drives

Choose a repair shop or recovery service that provides a written estimate and a clear chain of custody for drives. For critical data, prefer services that document their media-handling procedures and provide a no-data, no-charge policy where possible; check current reviews and certifications before sending drives.

Tools and 48-hour parts checklist for a quick attempt

You can try these tools and parts within 48 hours for a quick attempt at repair.

• Multimeter — for voltage checks if you know how to use it and have the PSU pinout.

• Anti-static wrist strap.

• Phillips screwdriver set and small plastic pry tools for laptops.

• Known-good PSU (or borrow one) for desktop swap testing; verify connector compatibility first.

• Spare compatible RAM DIMM(s) — matching speed is not required for initial boot testing; consult your motherboard documentation.

• SATA-to-USB or NVMe-to-USB adapter to read drives externally.

• Small external SSD or USB drive for rescue backups.

Appendix: POST/beep basics and printable one-page quick reference

POST-beep and LED codes vary by motherboard maker and model. Record the exact pattern and consult the motherboard or system manual for that model's meaning.

Quick-reference troubleshooting flow:

1. No power -> Verify outlet, swap cable, try AC-only on laptop -> If still no power, check PSU or AC adapter.

2. Lights/fans but no video -> Remove GPU, reseat RAM -> Boot to BIOS/UEFI or rescue USB.

3. Beeps -> Note pattern -> Check manual -> Reseat RAM/CPU only if comfortable.

4. Powers but no OS -> Boot rescue USB -> Backup files -> Run repair tools.

Troubleshooting log template to give a technician:

• Device model/serial:

• Exact symptom:

• Beep/LED pattern:

• Steps tried (with timestamps):

• Files backed up (yes/no) and destination:

Conclusion

If the system reaches POST or boots the OS, back up files and decide whether to run OS repairs or replace hardware. If you see smoke, visible damage, or a failing drive with irreplaceable data, stop and contact a qualified technician or a professional data-recovery service.