Troubleshooting Hardware, Drives, Displays & Mobile Devices
A+ Core 1 220-1201 · Hardware and Network Troubleshooting
Troubleshooting is the largest domain on Core 1 at 28%, and it is the domain that separates candidates who memorized facts from candidates who can think like a technician. The questions are scenarios: a symptom is described, and you must identify the most likely cause or the best next step. This guide covers the hardware half — motherboards, RAM, CPUs, power, drives, displays, and mobile devices. The companion guide covers networks and printers.
Troubleshooting methodology
CompTIA's objectives describe a troubleshooting methodology that, while not directly tested as an objective in the 1200 series, is the framework behind every scenario question: identify the problem, establish a theory of probable cause (question the obvious), test the theory to determine the cause, establish a plan of action and implement the solution, verify full system functionality and implement preventive measures, and document findings, actions, and outcomes. The practical habits that matter on the exam are to start with the simplest explanation, to change one thing at a time, and to verify the fix works before closing the ticket. When a question asks for the "best first step" or "most likely cause," it is testing this structured thinking.
Motherboards, RAM, CPUs, and power
The symptoms CompTIA lists for this objective are a diagnostic vocabulary. POST beeps are the coded sounds a computer makes during the power-on self-test: a single short beep usually means all is well, while a pattern of beeps indicates a specific failure (often RAM or video) — the exact codes vary by BIOS manufacturer, so the exam tests the concept, not specific codes. A proprietary crash screen is the vendor-specific error display (such as Windows' blue screen) that appears when the system fails. A blank screen on boot with fans spinning can mean a failed video card, unseated RAM, or a motherboard fault. No power at all — no lights, no fans — points to the power supply, the power cable, or the outlet.
Sluggish performance has many causes, but overheating is a common one: a CPU that is too hot throttles itself to a lower speed. Overheating itself is caused by blocked vents, failed fans, dried-out thermal paste, or dust buildup. A burning smell is a serious warning — power off immediately and inspect for a failed component, usually the PSU or a capacitor. Random shutdowns often mean overheating or a failing PSU. Application crashes that affect many different programs can indicate failing RAM (test with a memory diagnostic tool). Unusual noises — grinding, clicking, or loud fan noise — point to fans or drives. Capacitor swelling (bulging or leaking capacitors on the motherboard) causes instability and is a sign the board is failing. An inaccurate system date/time that resets on every boot usually means the CMOS battery on the motherboard is dead.
Drive and RAID issues
Drive symptoms are distinctive. LED status indicators on a drive bay or RAID controller show drive health at a glance — amber or red usually means a failed or failing drive. Grinding noises and clicking sounds (the "click of death") from a hard drive mean mechanical failure is imminent: back up immediately. "Bootable device not found" means the system cannot see a bootable drive — check cables, BIOS boot order, and whether the drive is detected at all. Data loss or corruption can come from a failing drive, a bad cable, or file system damage. A RAID failure shows as a degraded array: the array keeps working but has lost its redundancy, and the failed drive must be replaced and the array rebuilt. S.M.A.R.T. failure is a warning from the drive's self-monitoring system that it is predicting its own failure — replace the drive. Extended read/write times and low IOPS (input/output operations per second) mean the drive or array is struggling, often because of a failing drive or a degraded RAID rebuild in progress. Missing drives in the OS can mean a loose cable, a failed drive, or a driver problem. An array missing entirely and audible alarms from the RAID controller both indicate serious array problems that need immediate attention.
Video, projector, and display issues
Display troubleshooting starts with the obvious: incorrect input source (the monitor is set to HDMI 2 when the PC is on HDMI 1) and physical cabling issues (a loose or damaged cable). A burnt-out bulb in a projector produces no image at all — check the lamp hours. A fuzzy image can mean a wrong resolution, a damaged analogue (VGA) cable, or a projector out of focus. Display burn-in is a permanent ghost image left by a static display, most common on OLED screens. Dead pixels are individual pixels stuck black (or stuck on one colour) — a manufacturing defect that usually cannot be fixed. A flashing screen can be caused by a loose cable, a failing backlight, or a refresh rate the monitor does not support. Incorrect colour display often means a damaged cable (a bent pin on a VGA connector) or wrong colour settings. A dim image on an older LCD can mean a failing backlight or inverter; on any display, check brightness settings first. Intermittent projector shutdown is usually overheating — check the air filter and ventilation. Sizing issues (image too large or small for the screen) are usually a resolution or aspect-ratio mismatch. A distorted image can mean a failing graphics card or a wrong resolution. Audio issues on a display with built-in speakers often mean the wrong audio output device is selected in the OS.
Mobile device issues
Mobile symptoms overlap with the mobile devices guide. Poor battery health shows as short battery life; check the battery's health in the OS and replace it if capacity is far below design. A swollen battery is a safety issue — stop using the device and replace the battery safely. A broken screen may still show an image (cracked glass only) or nothing at all (damaged display panel). Improper charging can be a bad cable, a damaged charging port, or a failing charger — test with a known-good charger and cable. Poor or no connectivity can be a software setting (airplane mode, disabled Wi-Fi), a SIM problem, or a hardware fault. Liquid damage needs immediate power-off: do not try to charge or power on a wet device. Overheating in a phone is often caused by a runaway app or a failing battery. Digitizer issues show as touch not responding or responding in the wrong place. Physically damaged ports (bent pins, debris) cause intermittent charging or connection failures. Malware on a phone shows as pop-ups, battery drain, and unexpected data usage. A stylus that does not work may need a new battery (active stylus) or re-pairing. Degraded performance can be caused by a full storage, too many background apps, or an aging battery throttling the CPU. Cursor drift or touch calibration problems can be fixed by recalibrating or replacing the digitizer. Unable to install new applications is usually a storage, account, or OS-version problem.
Exam traps to watch for
- Assuming a blank screen means a dead monitor: with fans spinning, the cause is more often unseated RAM, a failed video card, or a motherboard fault — check the POST beeps first.
- Ignoring S.M.A.R.T. warnings: a S.M.A.R.T. failure means the drive is predicting its own failure. Back up and replace it; do not wait.
- Treating a clicking hard drive as a software problem: clicking and grinding are mechanical failure sounds. Back up immediately.
- Forgetting the CMOS battery: a system date and time that reset on every boot is the classic symptom of a dead CMOS battery, not an OS problem.
Practice questions
Test yourself on this guide. Answers are checked instantly, with a full explanation for each question.
Q1.A desktop powers on — fans spin and lights come on — but the screen stays blank and the computer emits a series of beeps. What should the technician check first?
Explanation: POST beeps during startup are the BIOS reporting a hardware fault before the OS loads, and beep codes most commonly indicate RAM or video problems — reseating the RAM is the standard first step. Option C is wrong because the OS has not started loading yet; a blank screen with beeps is a pre-boot hardware issue. Option A is wrong because network connectivity has nothing to do with POST. Option B is wrong because printer drivers load with the OS, long after POST.
Exam objective: 220-1201 Objective 5.1: Given a scenario, troubleshoot motherboards, RAM, CPUs, and power
Q2.A user reports that their computer's clock resets to the wrong date and time every time the computer is unplugged. All other functions work normally. What is the most likely cause?
Explanation: The CMOS battery powers the real-time clock when the computer is unplugged; when it dies, the date and time reset on every power loss while everything else works normally. Option B is wrong because a wrong time zone would show a consistent offset, not a reset on every boot. Option C is wrong because overheating causes throttling or shutdowns, not clock resets. Option D is wrong because a failing drive causes data errors and boot problems, not clock resets.
Exam objective: 220-1201 Objective 5.1: Given a scenario, troubleshoot motherboards, RAM, CPUs, and power
Q3.A computer randomly shuts down after about 30 minutes of use, and the case feels very hot. It works fine for the first few minutes after cooling down. What is the most likely cause?
Explanation: Shutdowns that follow a pattern of working when cool and failing when hot are the classic signature of overheating — the system protects itself by shutting down. The usual causes are a failed CPU fan, dust-blocked vents, or dried-out thermal paste. Option D is wrong because a failing drive causes data errors and boot failures, not heat-related shutdowns. Option C is wrong because OS corruption would cause errors at any temperature, not only when hot. Option A is wrong because insufficient RAM causes slowness and low-memory warnings, not thermal shutdowns.
Exam objective: 220-1201 Objective 5.1: Given a scenario, troubleshoot motherboards, RAM, CPUs, and power
Q4.A user's hard drive has started making a repeated clicking sound, and files are taking much longer to open. What should the technician do first?
Explanation: Repeated clicking from a hard drive (the "click of death") means the read/write heads cannot find data — a sign of imminent mechanical failure. The priority is to back up the data before the drive dies completely. Option A is wrong because defragmenting a failing drive adds stress and wastes the remaining time. Option C is wrong because reinstalling the OS does not fix a mechanical fault and risks the data. Option B is wrong because a bad cable would cause the drive to disappear or show errors, not a rhythmic clicking sound.
Exam objective: 220-1201 Objective 5.2: Given a scenario, troubleshoot drive and RAID issues
Q5.During boot, a computer displays a S.M.A.R.T. failure warning for the hard drive but still starts Windows. What should the technician recommend?
Explanation: S.M.A.R.T. is the drive's self-monitoring system, and a S.M.A.R.T. failure means the drive has detected that it is likely to fail soon. The correct response is to back up the data and replace the drive before it fails completely. Option C is wrong because ignoring the warning risks total data loss. Option D is wrong because malware does not cause S.M.A.R.T. warnings. Option B is wrong because a BIOS update does not repair a failing drive.
Exam objective: 220-1201 Objective 5.2: Given a scenario, troubleshoot drive and RAID issues
Q6.A RAID 5 array shows a degraded status, and one drive bay has an amber LED. The array is still accessible. What should the technician do?
Explanation: A degraded RAID 5 array has lost its redundancy: it survives one failure, and one has already happened, so a second failure would destroy the data. The failed drive (identified by the amber LED) must be replaced and the array rebuilt. Option B is wrong because running degraded leaves the data unprotected. Option C is wrong because reformatting would destroy the data. Option A is wrong because the problem is a failed drive, not the controller.
Exam objective: 220-1201 Objective 5.2: Given a scenario, troubleshoot drive and RAID issues
Q7.A user connects a laptop to an external monitor, but the monitor displays "No Signal" even though the laptop is on. The cable is known to be good. What should the technician check first?
Explanation: A monitor showing "No Signal" with a known-good cable most commonly means the monitor is set to the wrong input (for example, DisplayPort when the laptop is connected via HDMI). Checking the input source is the quickest first step. Option D is wrong because a failing drive would not prevent the laptop from outputting video. Option C is wrong because monitor firmware is rarely the cause of a no-signal condition. Option B is wrong because the battery is unrelated to video output.
Exam objective: 220-1201 Objective 5.3: Given a scenario, troubleshoot video, projector, and display issues
Q8.A user drops their phone in water. They pull it out immediately and it still appears to work. What is the best advice?
Explanation: Liquid damage can cause short circuits, especially while the device is powered on or charging. The correct response is to power off immediately, avoid charging, and let the device dry and be inspected. Option B is wrong because charging a wet device can cause short circuits and corrosion. Option A is wrong and dangerous — a microwave would destroy the phone and could cause a fire. Option D is wrong because water inside the device causes corrosion over time even if it appears to work at first.
Exam objective: 220-1201 Objective 5.4: Given a scenario, troubleshoot common mobile device issues