It beeps in a pattern. Or one small light on the motherboard stays lit while the others go out. That is not the PC complaining — it is the PC reporting, in the only language it has before a screen exists. This page teaches you how to take that report seriously without pretending it says more than it does: the honest version, where the motherboard manual outranks every chart on the internet.
Before a picture can appear, the board runs a power-on self-test — processor, memory, graphics, boot device, in that order. When a stage fails, the test stops and the board announces where: older and simpler boards with beep codes, newer ones with debug LEDs labelled CPU, DRAM, VGA and BOOT. Reading these signals well means knowing two things: what the signal points at, and how far to trust it. Both halves are on this page.
Think of the start as a roll call. The board calls the processor first; only if it answers does memory get called; graphics next; then it looks for something to boot from. A failure at any name ends the roll call there — which is why a memory problem can look exactly like a graphics problem from outside: the picture never arrives in both cases. Beeps and LEDs are the board telling you which name went unanswered. That single fact focuses every check that follows.
Here is the honesty most charts skip: there is no universal beep code table. AMI, Award, Phoenix and the board makers' own UEFI firmware all use different patterns, and the same pattern can mean different things on different boards. What you will find on the internet is other boards' dictionaries. Use them only as a compass: on many BIOS types, repeated or continuous beeps lean towards memory, and a pattern like one long and two or three short often leans towards graphics — but the only authority for your board is its manual or the maker's support page for your exact model. Count the pattern carefully — long versus short, and the pause before it repeats — and write it down before you search.
Most current boards carry four small LEDs labelled CPU, DRAM, VGA, BOOT. During a healthy start they light in sequence and go out. The one that stays lit names the stuck stage, with no counting and no dictionary: DRAM lit means the board is unhappy with memory — reseat it, try one stick, try the other slot. VGA lit points at the graphics card or its power cables. BOOT lit is almost good news — the hardware passed, and the problem is the missing or unhappy boot drive. Of all the no-start signals, this row of lights is the one to trust first.
Ready-built desktops and laptops from the big brands often speak a third dialect: the power light or a small LED blinks in a pattern — so many white, so many amber — or the keyboard lights flash a code. These patterns are documented per model on the maker's support site, and they are genuinely useful, but only the page for your exact model counts. A pattern borrowed from a different model year will send you confidently to the wrong part.
Silence is not a verdict. Many modern cases ship without the little speaker that makes beeps, so a faulty machine and a healthy one can be equally quiet. Some boards have no debug LEDs either. In that case the report does not exist and you fall back on behaviour: the keyboard witnesses, the timing of any shutdown, and the strip-down minimal boot from the core guide — remove parts until the machine either starts or has nothing left to blame but the board and supply. Do not let anyone sell you a diagnosis based on a beep code your PC never made.
The video reads a non-starting PC's signals in order and lets them point. It is slower than guessing and much, much cheaper.
▶️ Watch Full VideoIt leans that way on many BIOS types — repeated beeps are a common memory complaint — but beep meanings belong to your board's BIOS maker, not to a universal chart. Check the manual for your exact model. Meanwhile, the practical first move is the same either way: reseat the RAM, then test one stick at a time. If the beeps change or stop, memory was indeed the story.
It proves the board is stuck at the memory stage, which is not quite the same thing. A stick can be unseated, in the wrong slot, dirty at the contacts, or mismatched — all recoverable without buying anything. Reseat first, test one stick at a time in the slot the manual names, and only a stick that fails alone in known-good slots has honestly earned the word dead.
You work behaviourally. Keyboard lights tell you whether the machine is alive; the timing of any shutdown separates power and heat stories; and the minimal boot — one RAM stick, no USB extras, nothing non-essential — strips the suspect list down to board, processor, memory and supply. It is slower than reading an LED, but it is the same logic and it works.