Chương 5 / 530% của kỳ thi

Hardware and Network Troubleshooting

Troubleshooting is the core skill of IT support. This chapter presents the standard methodology and applies it to common hardware, power, display, storage, and network problems, along with the tools used to diagnose them.

The Troubleshooting Methodology

CompTIA defines a repeatable, best-practice process. Following the steps in order leads to faster, more reliable resolutions and good documentation.

Identify the problem first
Gather information, question the user, and note recent changes before acting.
Establish and test a theory
Form a probable cause, then test it; if disproven, form a new theory or escalate.
Implement, then verify
Apply the fix, verify full functionality, and add preventive measures.
Document the outcome
Record findings, actions, and results to preserve knowledge for the future.

Power and POST Problems

When a system will not start, work from the simplest external cause inward, and use POST indicators to localize faults.

Check power first for a dead PC
Verify the outlet, cable, and PSU switch before swapping internal parts.
Interpret beep codes
Repeating POST beeps map to hardware faults documented by the board vendor.
Reseat RAM and GPU on no video
No POST with fans spinning often points to seating or a wrong monitor input.
Use a minimal configuration
Boot with CPU, one RAM stick, and basic video to isolate a failing component.

Storage, Display, and Thermal Issues

Drives, screens, and cooling each produce recognizable symptoms that guide the technician to the failing part.

Clicking drives are failing
Stop using a clicking HDD and recover data before it dies completely.
Heed S.M.A.R.T. warnings
A S.M.A.R.T. error predicts drive failure; back up and plan replacement.
Dim panel points to backlight
If an external monitor works but the built-in screen is dim, suspect the backlight circuit.
Clean vents for thermal shutdowns
Dust, failing fans, or old thermal paste cause overheating and reboots.

Network Troubleshooting

Isolate whether a problem is local to one device or affects the whole network, then work from the physical layer up.

Scope the outage
If only one device fails, check its IP config and connection, not the ISP.
Verify link at the physical layer
Swap a known-good cable and try another switch port for link errors.
Use ping and traceroute
These tools distinguish local, gateway, DNS, and remote reachability problems.
Check APIPA and IP config
A 169.254 address indicates a DHCP failure to investigate on that host.

Diagnostic Tools

The right tool confirms a theory quickly and safely. A technician should know what each instrument measures.

Multimeter and PSU tester
These verify voltage output from the power supply's rails and connectors.
Cable tester
It checks pin-by-pin continuity and correct termination of network cables.
Memory diagnostics
Run a RAM test and reseat or swap modules when memory errors or BSODs appear.
Driver rollback for post-update faults
When one device fails after an update, roll back or update its driver first.
Kiểm tra kiến thức của bạn
Câu hỏi luyện tập về Hardware and Network Troubleshooting
Luyện tập ngay →

Last updated: July 2026

Báo lỗi