Motherboard Lights On, Computer Won't Start: Finding the Fault

A lit motherboard means power is reaching it. It does not mean anything else is working, and the distance between "has power" and "boots" contains most of the problems people meet.

Read the diagnostic indicators first

Before touching anything.

Diagnostic LEDs. Most current motherboards have four small labelled lights — CPU, DRAM, VGA, BOOT. During startup each lights in turn as that component is checked. The one that stays lit is where the process stopped, and that single observation eliminates most of the guessing.

Beep codes, on boards with a speaker. A pattern of beeps that means something specific, and the meaning differs by manufacturer. Look up the code for your exact board rather than a general list.

A two-digit code display, on some enthusiast boards. The most precise of the three — look the code up in the manual.

If the board has none of these, you are diagnosing by symptom, which is slower but works.

What each stuck indicator means

CPU light stays lit. The processor is not being detected or not responding. Check that the separate CPU power connector is plugged in — this is by far the most common cause and it is easy to miss because it is a different connector from the main one. Then check seating and look for bent socket pins.

DRAM light stays lit. Memory not detected. Reseat the modules firmly until both clips engage. Try one module alone, in the slot the manual specifies. Check the memory is compatible with the board.

VGA light stays lit. No display output detected. Reseat the graphics card, check its power connectors, and check the monitor is plugged into the card rather than the motherboard.

BOOT light stays lit. Everything else passed and no bootable drive was found. Good news — the hardware is largely fine. Check drive connections, whether the drive appears in firmware, and the boot order.

Stuck on the motherboard splash screen

Different from not starting at all. The firmware is running, so processor, memory and graphics are working.

It is usually waiting for something.

A drive that is slow to respond or failing. Disconnect drives one at a time and see whether it proceeds.

A USB device. Unplug everything except keyboard and mouse. External drives, hubs and card readers are frequent causes, and one that the firmware is trying to enumerate can hang the process indefinitely.

Boot order pointing at a device that no longer exists.

A firmware setting, particularly after a change or a battery replacement. Clearing the firmware settings to default resolves many of these.

Fast boot enabled, which skips checks and occasionally hangs when something has changed. Disable it while diagnosing.

A failed or pending firmware update.

Try in this order: unplug all USB devices, then disconnect all drives except the boot drive, then clear firmware settings to default.

New memory and the machine will not post

Extremely common after an upgrade, and rarely a faulty module.

Not fully seated. Memory needs more force than people expect. Both retaining clips must click into place. This is the cause in most cases.

Wrong slots. Two modules in a four-slot board go in specific slots — usually the second and fourth, though the manual is authoritative. The wrong pair frequently will not post at all.

Mixed modules. Different speeds, capacities or manufacturers may work, and may not. Test each module alone before assuming the board is at fault.

Speed profile not supported. Memory rated above what the board or processor supports will not run at that speed. It usually falls back automatically, and sometimes it does not — enabling the speed profile manually can prevent posting, and the fix is to reset to default and enable it afterwards.

Firmware too old to support newer memory. This is a genuine problem on boards from an earlier generation, and it needs a firmware update performed with older memory installed.

Capacity beyond what the board supports.

The method: one module, in the first slot the manual specifies, at default settings. If that posts, add the second. If it does not, try the other module in the same slot. Two tests separate a bad module from a bad slot.

Will any motherboard fit any case?

No, and the compatibility rules are simple once known.

Form factor is the main thing. ATX, Micro-ATX and Mini-ITX are the common desktop sizes, in descending order. A case states which it accepts.

Larger cases accept smaller boards. An ATX case takes Micro-ATX and Mini-ITX; the reverse is not true.

Standoffs must match the board's mounting holes. This matters more than it sounds — a standoff where the board has no hole shorts the board against the case, and the symptom is a machine that starts for a second and stops. It is one of the most common first-build faults and it is invisible once assembled.

The rear input/output shield must match the board. Boards supply one, or have it built in.

Then check clearances: graphics card length, cooler height, power supply size, and radiator support if using liquid cooling. Cases publish these figures.

And the front panel connectors. Case buttons and ports connect to the board by small individual pins, and the layout differs by board. The manual has the diagram, and getting the power switch pair wrong is a common reason a new build appears completely dead.

The diagnostic routine

When indicators do not tell you enough.

1. Reduce to the minimum. Motherboard, processor, one memory module, power supply, graphics if required, and the power switch. Nothing else.

2. Test outside the case if you suspect a short. Board on its own box, minimum components. If it posts outside and not inside, you have a standoff or a case ground problem.

3. Check both power connectors. The large main one and the separate CPU connector.

4. Reseat everything. Partly seated is the cause far more often than faulty.

5. Clear the firmware settings. Either the jumper or removing the small battery for a few minutes.

6. Add components back one at a time, testing between each.

Change one thing per test. Changing three and finding it works tells you nothing.

When it is genuinely the board

Visible damage — bulging capacitors, burn marks, a smell.

Bent socket pins, which sometimes can be straightened carefully and frequently cannot.

No response at all with confirmed-good processor, memory and power supply, tested individually.

Before concluding this, test the power supply if you can. A failing supply mimics a dead board precisely, and it is the cheaper and more commonly faulty component.

The short version

Read the diagnostic LED or beep code first — the one that stays lit tells you exactly where the process stopped.

The separate CPU power connector is the most commonly missed thing in a machine that will not post.

Memory needs more force than people expect, and the slot pairing matters — check the manual.

Stuck on the splash screen means the hardware is working and something is being waited on. Unplug USB devices, then drives.

A standoff where the board has no hole shorts it against the case — and the symptom looks exactly like a dead board.

For current Windows procedures and troubleshooting steps, see Microsoft Support.