CompTIA A+ 220-1201 Objective 5.1 focuses on hardware and system symptoms that often point to the same underlying failure. In practice, these signs rarely appear alone, so you need to recognize the pattern early, protect data, and correct the root cause before more damage occurs.
This section covers the symptoms you're expected to identify on the exam and in real support work: overheating, a burning smell, random shutdowns, application crashes, unusual noise, capacitor swelling, and inaccurate system date/time. Some are urgent safety warnings, while others hint at slow hardware decline, unstable power, or failing cooling.
A good technician responds with safe steps, fast checks, and clear next actions. That means powering down when there's heat or odor, confirming fans and airflow, checking power and board health, and validating BIOS or CMOS settings when the clock won't hold. By the end, you'll know what each symptom suggests, what to verify first, and when to stop troubleshooting and replace the part.
Start safe and triage the problem fast
When a PC shows hardware symptoms, your first job is to control risk. Heat, odor, and sudden shutdowns can signal a fault that damages components or creates a safety hazard. At the same time, you need quick, disciplined triage so you don't chase the wrong cause or lose useful evidence.
The goal is simple: make the system safe, capture key observations, then protect data before deeper troubleshooting.
Safety first when you notice heat, smoke, or a burning smell
Treat overheating and burning odors as urgent until proven otherwise. If the system feels unusually hot, vents blast very warm air, or you notice a sharp electrical smell, stop normal use right away. Continued operation can turn a minor cooling issue into a failed GPU, PSU, or motherboard.
Start with immediate actions that reduce power and heat:
- Shut down if it's safe (use the OS shutdown if the system responds). If it's frozen, press and hold the power button to power off.
- Unplug AC power from the wall and from the device.
- For laptops, remove the battery if it's removable. If it's internal, don't open the chassis while active smoke or sparking is present.
- Stop using the device until you identify the source. Let it cool before touching internal parts.
Avoid opening the case when you see visible smoke, hear popping, or notice sparking. In those cases, power isolation matters more than inspection. If you can do so safely, unplug from the wall, then move the device away from papers or fabric. If the outlet or power strip feels hot, stop and address the building power source first.
A "burning smell" often points to a small set of causes:
- Failing power supply (PSU): hot electronics smell, unstable power, random shutdowns under load.
- Shorted component or cable: sharp electrical odor, possible scorch marks, sudden power loss.
- Overheated dust or blocked airflow: "hot dust" smell, high fan speed, rising temps over time.
ESD protection still matters once the situation is stable. Static discharge can damage boards that are already stressed. Before touching internals, power off, unplug, press the power button for a few seconds, then ground yourself (for example, with an anti-static wrist strap to the chassis, or by touching bare metal on the case often). Work on a hard surface, not carpet.
If the smell persists after shutdown, or you see melted plastic, scorch marks, or a warm outlet, escalate. Replace suspect power parts and inspect the power source before any further testing.
Quick triage questions that narrow the cause
After the system is safe, you want fast answers that point to the most likely category of failure. Good triage is less about tools and more about asking the right questions, then matching symptoms to patterns. Keep your questions short and specific, because vague reports ("it just crashes") slow diagnosis.
Start with timing and workload:
- Does it happen at boot, after login, during gaming or video, or while idle?
- Is the issue repeatable (same trigger) or random?
- Does it affect one app or the whole system?
Then check for recent changes, because many failures follow a change:
- New hardware (RAM, GPU, storage, PSU, fans)?
- A BIOS update, driver update, or major OS update?
- New peripherals or docking equipment?
- Recent drop, spill, or transport?
Finally, ask about the environment:
- Are vents blocked by a desk, bed, or carpet?
- Is the room unusually hot, or is the PC in a tight cabinet?
- Does the system sit near a heater, sunny window, or dusty area?
These answers map to likely causes:
- Thermal cause: happens under load, fans loud, chassis hot, performance slows before shutdown.
- Power delivery cause: instant power loss, burning smell near PSU or adapter, resets under load, inconsistent boot behavior.
- Storage or file system cause: crashes during updates, slow boots, errors when opening files, repeated repair screens.
- Driver or OS cause: one app crashes, blue screens after updates, issues tied to a device (Wi-Fi, GPU, audio).
While you triage, record details that you can't reconstruct later. Write them down or capture screenshots/photos if safe.
- Temperatures and fan behavior (if you can view them without stressing the system).
- Exact error text (blue screen message, event dialog, beep codes).
- The time it happened and what was running at that moment.
A short incident log helps you spot patterns. If a crash always follows a GPU-intensive task, focus on cooling and power. If the clock is wrong and crashes appear after power loss, consider CMOS battery or unstable power. In other words, your notes become your map.
Protect user data before you chase the root cause
Random shutdowns and crashes don't just interrupt work, they can corrupt files and damage the operating system over time. Before you run heavy tests or repeated reboots, make a quick plan to protect the user's data. This step also reduces pressure during troubleshooting, because you won't feel forced to "keep trying" on an unstable machine.
If the system is stable enough to stay on briefly, take lightweight backup actions first. Copy the most important items (documents, desktop, photos, project folders) to external storage or a network share. Prioritize what can't be replaced, and keep the session short to limit heat buildup.
Avoid repeated hard power-offs. Cutting power can corrupt open files and, in some cases, the file system. If the device becomes unresponsive, let it sit for a moment, then shut down once, not over and over.
When normal boot is unreliable, use the least stressful path to reach files:
- Safe Mode: loads fewer drivers and startup items, which can reduce crashes tied to a bad driver or overheating under load.
- Recovery environment: if the OS won't boot normally, a recovery option may still let you access basic repair and file access paths.
- Remove the drive only when needed: if the system won't stay on at all, you may need to pull the storage device and copy data from another machine (only after power is disconnected and ESD steps are followed).
Keep the approach exam-friendly: protect data first, then troubleshoot. Once the user's files are safe, you can run longer checks for overheating, power faults, unstable RAM, or failing storage without risking the only copy of critical work.
A practical rule: if crashes are frequent and unpredictable, assume data is at risk. Stabilize, back up, then investigate the root cause.
Overheating symptoms, causes, and the fixes that usually work
Overheating is one of the most common hardware symptoms you will diagnose for CompTIA A+ Core 1 (220-1201). It can look like a performance problem at first, then turn into shutdowns, crashes, and data loss. Heat also hides other faults because it changes behavior as the system warms up.
The practical goal is to spot the pattern early, confirm it with simple checks, then apply fixes in a safe order. Most overheating cases come down to airflow, fan failure, or poor heat transfer between the chip and the cooler.
How overheating shows up: hot case, slowdowns, and sudden power-offs
Overheating rarely starts with a clear error message. Instead, you notice the system working harder to stay cool. Fans ramp up and stay loud, the case feels hot near the CPU or GPU area, and performance drops during tasks that used to run fine.
A key sign is thermal throttling. Modern CPUs and GPUs protect themselves by lowering clock speed when temperatures rise. As a result, you see stuttering in games, slow video exports, lag in virtual meetings, or long app load times. On laptops, you may also feel heat on the keyboard deck or near the hinge, because many models exhaust there.
When heat keeps climbing, stability goes next. You can see:
- Random restarts during gaming, benchmarks, or large file copies.
- Sudden power-offs with no warning, often when the system is under load.
- Application crashes that seem unrelated (browser closes, games crash to desktop).
- Blue screens (stop errors) when drivers or hardware fail under thermal stress.
It also helps to separate what the user experienced. A normal shutdown follows the operating system's rules. A thermal cut behaves like someone pulled the plug.
Here is a quick way to tell them apart:
| What you observe | Planned shutdown (OS-driven) | Thermal or power cut (hardware-driven) |
|---|---|---|
| Screen behavior | Shows "Shutting down" or a closing sequence | Goes black instantly, sometimes mid-task |
| User warning | Often some notice (close apps, updates) | No warning, may restart immediately |
| After restart | System may say it shut down properly | Often shows "Windows didn't shut down correctly" |
| Trigger pattern | Can occur at idle too (updates, settings) | Common under load, after heat builds |
If the user reports "it just turned off," treat overheating and power as top suspects. In contrast, if the system shows a clear shutdown message, focus first on OS settings, updates, or a user action.
If the system powers off instantly under load, assume a thermal or power protection event until testing proves otherwise.
Common reasons PCs overheat
Most PCs overheat for simple, physical reasons. Heat must move from the chip to the heatsink, then out of the case. If any step fails, temperatures climb fast.
Dust and clogged airflow paths are the most common causes. Dust mats form on intake filters, heatsinks, and radiator fins. Air still moves, but not enough. This is why a system can sound loud yet still run hot, the fans are trying, but airflow is blocked.
Failed or blocked fans come next. A fan can stall, wobble, or spin too slowly. Cables can also drift into fan blades after a repair or upgrade. In small form factor cases, one stopped fan can raise all internal temperatures because there is little spare airflow.
Another frequent cause is dried or poorly applied thermal paste. Paste fills microscopic gaps between the CPU and the cooler. Over time, it can dry out, crack, or pump out from repeated heat cycles. As a result, heat transfer gets worse, even if the fan works fine.
Airflow design matters as well. Poor case airflow happens when:
- Cables block the front intake or hang in front of the CPU cooler.
- The case sits in a tight cabinet or against a wall.
- Too few case fans exist, or they face the wrong direction.
Environment adds pressure. High ambient temperature reduces cooling capacity because the system cannot dump heat into already warm air. This shows up during summer months, in server closets, or in rooms with weak ventilation.
Overclocking also increases risk. Higher frequency and voltage raise power draw, and power draw becomes heat. Even a mild overclock can push a "barely adequate" cooler over the edge.
Laptops have their own patterns. Intake vents can block easily on soft surfaces like beds, couches, or thick blankets. In addition, laptop fans and fins clog faster because the passages are narrow. Some models also suffer from failing heat pipes (or poor contact along the heat pipe path). When that happens, one area becomes very hot while the fan seems to run normally.
Finally, consider the power supply. If the PSU exhaust air feels unusually hot, or the PSU fan is loud and struggling, the PSU may be overheating. A PSU running hot can trigger shutdowns, cause instability, or produce a hot electronics odor. Because the PSU is a safety-sensitive part, treat abnormal heat there with extra caution and plan for replacement if symptoms persist.
Step-by-step checks to confirm a heat problem
Confirming overheating does not require advanced tools. You want safe, low-effort checks that either support the heat theory or push you toward another cause.
Start with what you can see and hear. Check the vents and intake areas for dust buildup. Then listen at boot and under light use. Fans should spin up briefly at startup on many systems. Grinding, rattling, or silence when you expect airflow points to a fan problem.
Next, use built-in monitoring. BIOS/UEFI often includes a hardware monitor page with CPU temperature, system temperature, and fan RPM. This view is valuable because it removes OS drivers from the equation. If the CPU temperature is already high in BIOS after a short time, cooling is the likely cause.
In the operating system, use any available temperature and fan readings provided by the device vendor tools or system utilities. If you cannot see exact numbers, you can still watch indirect signs like rapid fan ramping, stutters under load, and repeated crashes during graphics tasks.
On desktops, a controlled test can help: run the system briefly with the case side panel removed and observe whether behavior improves. Better airflow should reduce fan noise and reduce shutdowns if heat is the true trigger. Do this only for short testing, and keep hands away from moving fans.
Safety matters during these checks. Avoid touching heatsinks, heat pipes, or the PSU casing because they can burn skin. Also, do not move a running desktop around with the case open.
A useful diagnostic clue is how fast temperatures rise. If temperatures spike quickly from idle to critical under light load, suspect poor cooler contact, dried paste, or a dead fan. In contrast, a slow climb over 10 to 20 minutes often points to dust buildup or weak case airflow.
If the system shuts off instantly during a stress event, do not repeat the test many times. Each thermal cut adds wear and can corrupt data. Instead, move to inspection and cleaning, then retest once conditions improve.
Fixes: cleaning, airflow, fan replacement, and thermal paste
Most overheating fixes work best in a simple order. You start with the easiest, lowest-risk steps, then move toward parts replacement and rework. This approach also matches exam logic and real support workflows.
First, clean dust safely. Power down, unplug, and let the system cool. Use compressed air to clear vents, heatsinks, and filters. Hold fan blades in place while you blow air, because overspinning can damage bearings. Focus on CPU cooler fins, GPU heatsinks, front intakes, and radiator fins if the system uses liquid cooling.
Next, fix airflow basics. Route cables away from fans and intakes. Confirm that case fans face the correct direction, with front or bottom as intake and rear or top as exhaust in many builds. Also, give the case breathing room, especially behind the exhaust.
If cleaning and airflow do not help, inspect the cooling hardware. A loose heatsink or an uneven mount can break thermal contact. Re-seat the cooler if you suspect poor contact. When you remove the cooler, clean off old paste (use appropriate cleaning materials) and apply fresh paste in a controlled amount. Too little paste leaves gaps, while too much can spill and reduce effective contact.
Fan replacement is often the turning point. Replace any fan that:
- Does not spin reliably.
- Makes grinding or clicking noise.
- Reports erratic RPM, if monitoring is available.
For laptops, the steps stay similar but require more care. Clean vents and exhaust paths first. If the fan is noisy, slow, or intermittent, replace the fan assembly as designed for that model. Also, correct the everyday cause: keep the laptop on a hard surface, and avoid thick fabric that blocks intake.
Do not forget the PSU angle.