What to Do When Your Computer Won't Turn On

Tap each step to follow along in order.

  1. Check the power cable and outlet

    First make sure the power cable is fully plugged in at both ends, and that the outlet or power strip itself isn't the problem.

  2. Check the monitor connection

    If the computer case powers on but nothing appears on screen, check the monitor cable connection, the monitor's own power, and its input source setting.

  3. Listen for sounds or watch the indicator lights at startup

    Fan noise, beep codes, and the color or blink pattern of indicator lights when you power on can hint at which component is causing the problem.

  4. Disconnect all peripherals and try again

    Unplug unnecessary peripherals like USB drives and external hard drives, then try powering the computer on again.

  5. Try Safe Mode, or get it looked at professionally

    If none of this works, try booting into Safe Mode. If that still does not resolve it, there may be a hardware fault worth having checked by a repair service.

Stay calm and work through it step by step

A computer that suddenly won't turn on is alarming, but a large share of cases come down to something simple like a loose cable or a disconnected outlet. Going through the checks in order helps you narrow down the actual cause instead of guessing.

If it keeps restarting during boot

A boot loop, where the computer restarts over and over before finishing startup, is often caused by overheating, a failing memory module, or a recently installed program or update. Booting into Safe Mode, which loads only essential drivers, is a good way to check whether a software change is the culprit.

Frequently Asked Questions

The power turns on but the screen stays black.

This usually points to a graphics card or monitor connection issue. Try reseating the cable at both ends, or testing with a different monitor if you have one available.

It keeps restarting during the boot process.

Overheating, a failing memory module, or a recently installed program or update can all cause this. Booting into Safe Mode is a good way to narrow down whether a recent software change is responsible.