Motherboard, CPU, RAM, and Power Issues for A+

This A+ topic covers technician-level recognition and basic domain routing for the official A+ Core 1 symptom set related to motherboard, CPU, RAM and power: POST beeps, blank screen during startup, no power, proprietary crash screens, application crashes, sluggish performance, overheating, burning smell, random shutdown, unusual noise, capacitor swelling, and inaccurate system date/time. The objective is symptom recognition, grouping into troubleshooting buckets (startup, stability, thermal, board-warning), and making safe, practical technician decisions (e.g., escalate, stop use, basic checks) rather than deep repair.

Start first lesson

4 lessons in this topic

POST, Blank Screen & No Power

Recognize startup-domain hardware symptoms such as POST beeps, blank screen during startup, and no-power conditions.

Crash Screens & Stability Issues

Recognize crash screens, repeated application crashes, and sluggish performance as possible motherboard/CPU/RAM/power-domain symptoms.

Heat, Shutdown & Burn Smell

Identify overheating, burning smell, and random shutdown as serious motherboard/CPU/RAM/power troubleshooting symptoms.

Board Warning Signs

Recognize visible or persistent board-warning symptoms such as capacitor swelling, inaccurate system date/time, and abnormal platform noise.

Common mistakes to avoid

- Misidentifying blank-screen as purely monitor failure; always confirm platform POST activity first. - Attempting to memorize vendor beep patterns; A+ requires recognizing beeps as hardware signals, not memorizing codes.

- Treating every crash as a software bug; conversely, assuming every crash is hardware. The correct A+ stance is pattern recognition: repeated, system-wide, or timing-correlated crashes bias toward hardware investigation.

- Minimizing a burning smell as "just dust"; any such smell is a serious sign requiring conservative action. - Attributing random shutdowns immediately to software updates; correlate with thermal and power indicators before concluding software cause.

- Ignoring slight fan noise changes; persistent new sounds should be evaluated. - Replacing software settings for clock issues without checking CMOS battery or hardware cause.