A workstation powers on, its fans spin, and its keyboard lights briefly, but the monitor remains blank. A technician is tempted to replace the graphics card because the complaint mentions the display. A careful technician first checks power delivery, monitor input, diagnostic indicators, memory seating, and whether the system completes its power-on self-test. The symptom is real, but its cause is not yet established. PC hardware troubleshooting becomes more efficient when technicians understand component roles and collect evidence before ordering parts.
The CompTIA A+ Core 1 220-1201 exam covers hardware, mobile devices, networking, virtualization and cloud basics, and hardware or network troubleshooting. It is designed around entry-level support tasks rather than advanced electronics engineering. Candidates should recognize components, compatibility constraints, safe replacement procedures, and practical diagnostic sequences that preserve data and minimize unnecessary work.
Identify the job of each core component
The motherboard connects the processor, memory, expansion interfaces, storage controllers, and many peripheral functions. The CPU executes instructions and depends on an appropriate socket, firmware support, cooling, and electrical configuration. RAM holds active working data, while persistent storage retains information when power is removed. Understanding these distinct roles helps avoid blaming storage for every slow application or memory for every boot failure.
Compatibility is critical when replacing components. Memory type, form factor, supported speed, processor generation, firmware revision, and power requirements must be checked against the system’s specifications. A physically similar module may not be electrically or firmware compatible. For an organizational fleet, approved spare-part lists can save technicians from experimenting with replacements that introduce unpredictable failures.
Graphics processing may be integrated or discrete depending on the system. A display problem may involve the monitor, cable, chosen input, firmware settings, display adapter, or operating system driver. A useful hardware diagnosis separates failures before boot from those that occur only after the operating system loads. These categories lead to different next tests.
Check power and thermal behavior before replacing boards
A desktop with no response to the power button may have a disconnected cable, failed power supply, front-panel switch problem, or an internal short. Verify the safe basics before opening the chassis: known-good outlet, cable, power switch, and external accessories. Follow approved safety procedures and never open a power-supply enclosure to investigate hazardous internal components as a routine support task.
Intermittent shutdowns or thermal throttling may reflect blocked vents, failed fans, improper heatsink contact, or abnormal workload. Check temperature evidence where available and inspect airflow before concluding that the processor is defective. Dust accumulation can be important, but cleaning must be done with the equipment appropriately powered down and handled safely. Replacing an expensive CPU when the fan does not run is a poor diagnosis.
Power budgeting matters for upgrades. Adding a high-demand graphics card or multiple drives can exceed the capacity or connector availability of an existing power supply. The technician should confirm system requirements rather than relying on a nominal wattage alone. Reliable repairs account for load, connectors, cooling, and chassis constraints together.
Compare storage and memory failure patterns
A slow computer may be short of memory, waiting on a failing disk, overloaded by software, or affected by malware. Storage and RAM serve different functions, so their failure patterns should be interpreted carefully. A system that repeatedly fails memory diagnostics suggests a different path from one that reports storage errors during file reads. Use appropriate diagnostic tools rather than changing several components at once.
HDDs contain moving parts and can exhibit mechanical or performance symptoms. SSDs use different technology and failure behavior, with form factors and interfaces such as SATA or supported NVMe arrangements. An SSD’s form factor does not by itself tell you whether the motherboard supports the necessary electrical interface or boot configuration. Confirm specifications before recommending an upgrade.
Data protection comes before invasive troubleshooting. A failing drive may deteriorate with repeated attempts to scan or reinstall. Follow organizational backup and recovery procedures, minimize unnecessary writes, and escalate sensitive recovery cases appropriately. A successful replacement is incomplete if the organization’s only copy of important work was lost during the process.
Understand expansion and peripheral interfaces
USB versions and connector shapes are related but not identical ideas. A USB-C connector does not automatically guarantee a particular data rate, charging capability, or display feature. Likewise, different video interfaces have different supported resolution, refresh-rate, and audio behavior depending on devices and cables. Technicians should verify the negotiated function instead of making assumptions from how a port looks.
Peripheral problems can originate with power, cabling, firmware, driver support, or the device itself. A keyboard that fails in the operating system but works in firmware setup suggests a different issue from one that never receives power. A network adapter with no link light may indicate a cable or physical connection problem even before TCP/IP settings matter. Classifying where the failure appears reduces wasted time.
Expansion cards and internal connectors require safe handling. Use appropriate electrostatic-discharge precautions and manufacturer guidance, including correct alignment, seating, and secure cabling. A technician should avoid forcing a component into a slot or improvising adapter combinations that exceed specifications. Good hardware practice protects both equipment and the person working on it.
Follow a structured troubleshooting method
Begin by identifying the exact complaint and gathering evidence. When did the issue start? Does it occur at boot or under load? Has hardware or software changed? Can the problem be reproduced? Establish a theory based on observed symptoms, test it with the least disruptive appropriate action, then confirm the result. The goal is a reliable explanation, not a lucky substitution.
Change one meaningful variable at a time when practical. If a workstation fails to start after a RAM upgrade, restoring the known-good memory configuration provides a useful comparison. Swapping the display and graphics card simultaneously may make the symptom disappear without revealing which component was responsible. Documentation of each test avoids repeating work and supports escalation.
Verify full operation after repair. A replacement power supply might allow the computer to boot while instability remains under load. A newly installed SSD may work locally but fail the organization’s encryption or deployment checks. Acceptance criteria should reflect the user’s actual job and security requirements, not only whether a technician can reach the desktop.
Use firmware and diagnostics intelligently
UEFI or BIOS settings influence boot order, hardware initialization, security capabilities, and sometimes performance behavior. Incorrect settings can make a healthy drive appear unbootable or prevent an expected peripheral from operating. Firmware updates may correct supported issues but carry risk; use approved files, verify model compatibility, and follow manufacturer procedures. Do not flash firmware merely because a machine feels slow.
Diagnostic indicators, built-in tests, event logs, and vendor utilities can narrow a problem. Their outputs need context. A successful memory test does not prove every intermittent issue is absent, and a SMART warning does not automatically explain an unrelated network failure. Combine test evidence with symptoms and recent changes rather than treating one diagnostic code as a complete verdict.
Repairs should fit service policy. Devices under warranty or containing sensitive information may require authorized servicing rather than user-directed disassembly. Record identifiers, replaced components, diagnostic results, and the final verification performed. The next support agent should be able to understand what happened without starting from zero.
Component replacement should begin with an understanding of the platform’s supported combinations. A memory module may physically fit yet fail because the system does not support its capacity or specification. A storage device can appear similar while using a different interface or lane configuration. Before authorizing a repair, check the system model, service documentation, warranty constraints, and the failure evidence. Correct compatibility decisions save more time than repeatedly installing parts that happen to be available in a drawer.
Hardware symptoms can also be misleading when several subsystems interact. A workstation that freezes during a graphics-intensive task could suffer from thermal throttling, an unstable power supply, a driver issue, memory faults, or a defective graphics component. A technician should record whether the failure is reproducible, whether temperatures and logs show a pattern, and whether a known-good test changes the result. The next test should distinguish plausible causes rather than simply produce another symptom. Swapping an expensive board before checking power and cooling can make diagnosis slower and more costly.
Handling and disposal are part of repair quality. Power isolation, electrostatic-discharge precautions, and approved battery procedures protect users and devices. Replacing a drive also creates a data-handling responsibility: the old component may hold customer or employee information, even if it no longer boots. Follow established asset custody and media sanitization procedures rather than placing failed storage in ordinary electronic waste. A reliable support process restores the device while preserving evidence, warranty coverage, safety, and the organization’s data obligations.
Connect hardware choices to the user’s workload
A designer editing large images may benefit more from appropriate memory and graphics capabilities than from an indiscriminate CPU upgrade. A field sales device may prioritize battery life, durability, and connectivity. Component selection should follow actual use, compatibility, budget, and support lifecycle. Purchasing the highest specification for every employee often creates expense without matching business benefit.
The related CompTIA A+ Core 2 220-1202 covers operating systems and supporting operational concerns that complement Core 1. Hardware troubleshooting remains grounded in the same principle: define the symptom, understand the component path, test a plausible cause safely, verify the user’s outcome, and document what changed. Competence is demonstrated through disciplined diagnosis, not the size of the technician’s replacement-parts collection.