Lights On, No Boot? Quick PSU/Mobo/RAM Checks
Lights on but no boot? Let’s make sense of it.
Your PC’s RGB is glowing, fans twitch, maybe the keyboard lights blink—but the monitor says No Signal. Stressful, right? Don’t panic. Below is a simple, safe way to narrow it down to PSU (power supply), motherboard, or RAM—no tools or disassembly required. And if it still won’t behave, AEPC – Auckland East PC is right around the corner in Burswood to get you running again.
TL;DR
✅ Lights on + no display isn’t rare—often PSU stability, RAM training, or motherboard POST.
🔌 Rule out the easy stuff (power, cables, monitor input, peripherals).
🧠 Quick symptom map below helps you guess PSU vs Mobo vs RAM safely.
🛠️ If it loops, beeps, or smells hot—stop and call a pro.
What “lights on, no display” usually means
When you press power, the system performs a POST (Power-On Self Test). If something fails early—power rails, memory training, CPU init, GPU hand-off—you’ll get no video even though lighting or some fans come on (those often run from +5V standby or basic rails).
Common culprits (order of likelihood in everyday cases):
-
RAM/Memory initialisation (training) hiccups
-
PSU instability under load (12V droop, protection tripping)
-
Motherboard POST/BIOS path issues (faulty board or firmware config)
-
Display chain (cable/monitor/input selection)
Quick, safe self-checks (no tools, no teardown)
Follow the instructions for your exact device and stop if a check is unclear or the device shows damage. No troubleshooting step or repair can be described as risk-free; protect important data before making changes.
-
Power sanity checks
-
Try a different wall socket or power strip.
-
Confirm PSU switch “I” is on.
-
Reseat the kettle/IEC cable at both ends; try a known-good cable.
-
-
Monitor & cable
-
Make sure the monitor is powered on and set to the correct input (HDMI/DP).
-
Test with another cable or a different monitor/TV.
-
If your CPU has integrated graphics, try the motherboard video port (HDMI/DP).
-
On the monitor, open the OSD/menu—if OSD shows but the PC reads “No Signal,” the display is fine.
-
-
Peripherals & simple indicators
-
Unplug extra USB gear (hubs, capture cards, VR link boxes).
-
Watch keyboard Num/Caps Lock—if the lights toggle after a few seconds, the system likely passed some POST steps.
-
Listen for beeps (some boards beep on RAM/CPU errors if a speaker/buzzer is present).
-
Note any debug LEDs on the motherboard visible through your case window (often labelled CPU/DRAM/VGA/BOOT).
-
-
Thermal/smell check (no touching inside)
-
If you smell electrical/burning, power off immediately and contact a pro.
-
Fans that start/stop repeatedly (rapid cycling) point to protection triggers—often PSU or short.
-
Quick isolation map: PSU vs Motherboard vs RAM
Use the pattern that matches your symptoms.
-
A. Lights on, fans don’t spin, nothing progresses
-
Strong hint: PSU 12V rail not delivering under load or protection tripping.
-
Also possible: Motherboard short/protection.
-
Next step: Professional PSU test with a load tester and board short check.
-
-
B. Fans spin once, then system repeatedly restarts (boot loop), no display
-
Common: RAM training failure or unstable PSU.
-
If you changed memory settings/XMP recently, that’s suspicious.
-
Next step: Pro reset of memory training, test with known-good RAM and PSU.
-
-
C. Fans run steadily, keyboard lights never respond, no beeps
-
Often motherboard POST path (board/CPU/firmware).
-
Could still be RAM, but boards usually signal RAM faults.
-
Next step: POST card diagnostics, CMOS checks, firmware sanity.
-
-
D. Fans run, keyboard lights respond, but monitor says No Signal
-
Check cable/monitor/input again; try integrated graphics port.
-
If discrete GPU was moved/changed recently, that’s relevant.
-
If still no video with iGPU: suspect motherboard/BIOS path.
-
Safety note: Avoid paperclip-bridging PSUs or component reseating if you’re not confident—those can damage parts or void warranties.
When to call a pro
-
You hear beep codes or see debug LEDs stuck on CPU/DRAM/VGA.
-
There’s smell, sparks, or the system power-cycles endlessly.
-
You recently changed BIOS settings, added RAM/GPU, or had a power outage.
-
The PC stores important work/school data—don’t risk it.
Questions to discuss before approving work
- What diagnostic lights or codes were observed before testing stopped?
- How can power, memory, graphics and firmware possibilities be distinguished?
- What evidence is needed before a replacement part or firmware change is proposed?
Need help today?
AEPC – Auckland East PC
📍 9/28 Torrens Road, Burswood, Auckland 2013
📞 0279-088880
📧 akleastpc@gmail.com
10AM–5PM · 24h appt. Please call before visiting.
Prevention & best practices
-
Use a quality PSU sized with headroom; avoid no-name units.
-
Surge protection or a small UPS helps with Auckland’s occasional power blips.
-
Keep BIOS/UEFI defaults unless you know what you’re changing.
-
Avoid mixing RAM kits; buy a matched set.
-
Keep dust down; ensure front intake is clear and cables aren’t blocking fans.
-
Shut down properly—don’t hard-kill the power unless necessary.
FAQ
1) Can a faulty PSU still light up the PC?
Yes. Fans/RGB may run from minimal rails, but the PSU can still fail under load, causing no display or restart loops.
2) Is “no display” the same as “not booting”?
Not always. A PC can boot headless (no video) if the display chain fails. But most “no display” cases are early POST failures.
3) Will resetting BIOS or RAM lose my data?
Do not assume that a firmware change is risk-free. Discuss the exact device, backup status and possible effects on access to encrypted data before changing settings.
4) Could the motherboard be fine and it’s just memory?
Absolutely. Memory training is sensitive to voltage, timings, and mixed kits.
5) Do I need a new motherboard if it beeps for DRAM?
Not necessarily. DRAM beeps often point to the memory path—sometimes fixed by configuration or matched modules.
6) How long does diagnosis take?
Timing depends on the fault, model, assessment and any parts required. Ask for a current estimate before approving work; no completion time is promised here.
7) Is it safe to keep trying to power it on?
If it’s looping, beeping, or there’s a smell—stop. Repeated attempts can stress components.
8) Will my files be safe?
The outcome depends on the fault, storage condition, encryption and available backups. Discuss a data-protection plan before testing or migration. Do not assume that files can be preserved or recovered in every case.