4 Core 1: Troubleshooting and Practice

A repeatable troubleshooting process

In CompTIA A+ 220-1201, Hardware and Network Troubleshooting accounts for 28% of the exam. CompTIA presents its troubleshooting methodology as a practical best practice, not as a formal exam objective; troubleshooting scenarios nevertheless remain part of the exam.

A repeatable process helps connect a reported symptom to likely causes, a suitable diagnostic tool, and a safe next step:

1. Identify the problem. Ask what changed, when the issue began, who or what is affected, and whether the problem can be reproduced. Check error messages and relevant system or device indicators.

2. Establish a probable cause. Begin with simple, likely explanations such as loose cables, incorrect settings, depleted batteries, blocked airflow, or a service interruption. Research unfamiliar symptoms when appropriate.

3. Test the theory. Change one variable at a time, such as testing with a known-good cable or device. If a test disproves the theory, reconsider the evidence.

4. Plan and implement a solution. Consider risk, data protection, user impact, and whether the change can be reversed. Obtain authorization when required.

5. Verify operation. Confirm that the original symptom is gone and related functions still work. Check with the user when possible.

6. Document the outcome. Record symptoms, tests, findings, actions, and any preventive steps.

Diagnostic tools and their limits

Choose tools that match the fault being investigated. A measurement or connectivity test can narrow the possibilities, but it does not necessarily prove that every component or service is healthy.

• Multimeter: Measures voltage, continuity, and resistance. Use appropriate settings and safety precautions.

• Power supply tester: Checks whether a computer power supply provides expected outputs, but does not prove every component is healthy under load.

• POST indicators or diagnostic LEDs: Help narrow startup failures to hardware categories. Use the manufacturer's documentation to interpret codes.

• Cable tester: Checks cable wiring and continuity, helping find opens, shorts, or miswires.

• Toner and probe: Traces a cable through a bundle or wall to identify its path or endpoint.

• Wi-Fi analyzer: Reveals nearby networks, channels, and signal conditions that can help identify congestion or interference.

• Loopback plug: Tests whether a network or serial interface can transmit and receive through its own port.

• Operating-system utilities: ping tests reachability and response time; ipconfig or ifconfig displays network configuration; tracert or traceroute shows the route toward a destination.

A successful ping means a host responded, but does not prove that every application or service is working; a particular service may be unavailable or blocked. Other network tools include crimpers, cable strippers, punchdown tools, network taps, cable testers, loopback plugs, and Wi-Fi analyzers.

Hardware symptom patterns

Power, memory, and processor

• No power: First check the outlet, power cable, power strip, PSU switch, and external connections. If there is still no response, consider the PSU, motherboard, or power button. A burning smell or visible damage is a reason to stop, disconnect power if safe, and escalate rather than continue testing.

• Fans run but the screen is blank, or POST beeps occur: Check the display input and cable, then consider RAM seating, graphics hardware, and motherboard connections. Beep meanings vary by manufacturer, so consult the system documentation rather than assuming a universal code.

• Overheating, sluggishness, or random shutdowns: Check airflow, dust, fan operation, heat-sink seating, and workload. A sudden shutdown under load can point to thermal or power problems.

• Application crashes or crash screens: Note whether the failure is repeatable and whether it began after a hardware, driver, or configuration change. Test memory and review system diagnostics before replacing parts.

• Inaccurate date and time: A clock that is repeatedly incorrect after shutdown may indicate a depleted CMOS/RTC battery or a time-configuration problem.

Drives and displays

• Clicking or grinding from a hard drive, SMART warnings, slow reads, or missing files: Treat the drive as potentially failing. Protect important data and avoid unnecessary writes before further testing or replacement.

• “Bootable device not found”: Check firmware boot order, drive detection, and storage connections. If the drive is detected but cannot boot, investigate the boot configuration or drive health.

• No display, flicker, wrong color, or distorted image: Check power, input source, cable seating, adapters, resolution, and refresh rate. Test with a known-good cable or display to isolate the failing side.

• Dim projector image or intermittent shutdown: Check the selected input, ventilation, and lamp or light-source status where applicable.

These symptom patterns cover troubleshooting concerns involving motherboards, RAM, CPUs, power, drives, and displays.

Isolate connectivity problems

Isolate a connection problem by working outward from the endpoint: device → cable or wireless link → switch/access point/router → internet service → destination service. Compare with a second device when available to help determine whether the fault is local or shared.

• One device cannot connect: Check Wi-Fi or airplane-mode settings, credentials, signal strength, cable seating, and IP configuration.

• An IPv4 address beginning with 169.254: This is an APIPA address. The device may not have received a DHCP lease, so check the link and whether DHCP is reachable.

• Local network works but internet access fails: Check the default gateway, router/modem or ONT status, and whether other devices are affected. If multiple devices lose internet access, investigate shared equipment or the provider connection.

• Intermittent wireless connection: Check distance, obstructions, interference, channel congestion, and access-point placement. Compare performance near the access point and on another band or network when available.

• Slow transfers or high latency: Compare wired and wireless connections and local and internet destinations. Look for congestion, weak signal, or a failing link. Latency is delay; jitter is variation in delay and can disrupt voice or video calls.

• Authentication failure: Confirm the network name, password, security compatibility, and account or device restrictions before changing broader network settings.

• Port flapping: A switch port repeatedly changes link state. Check the cable and connectors, endpoint NIC, and switch port. A cable tester or known-good cable can help isolate the fault.

For example, if a laptop can reach the router but cannot load websites, test whether other devices have internet access and whether a destination can be reached by IP address. If IP reachability works but names do not resolve, investigate DNS. If other devices also fail, focus on shared network equipment or the internet connection.

Practice choosing the next step

Use the symptom to choose an initial comparison or test, then verify the result before making broader changes.

1. A desktop powers on, but the monitor says “No signal.” First confirm the monitor's selected input and check the display cable and connections. Then test with a known-good cable or display.

2. Wi-Fi drops in one conference room while nearby rooms work normally. Compare signal and connectivity in the affected room with a working room. Investigate access-point coverage, obstructions, and interference before changing unrelated settings.

3. A computer shows a 169.254.x.x IPv4 address. Investigate DHCP availability and the device's network link; the address suggests that it did not obtain a DHCP lease.

4. A workstation's hard drive clicks and read times have become very slow. Protect important data and minimize unnecessary writes because the symptoms suggest possible drive failure.

5. A network switch port repeatedly disconnects and reconnects. Test the cable and connectors, then the endpoint NIC or switch port. A cable tester or known-good cable can help isolate the cause.

Across these cases, define the symptom, test likely causes one at a time, apply a considered fix, verify the result, and document it. Use tools suited to the fault, compare with known-good components or network paths where useful, and treat signs of electrical danger or possible drive failure cautiously.