Identifying and resolving common hardware and software issues is the practical skill that turns theory into real-world value. When a computer wont turn on or a program keeps crashing, you need a reliable method to diagnose and fix the problem — not just trial and error. This chapter gives you the foundational troubleshooting methodology that every IT professional uses, starting with the very first step any beginner can apply.
Jump to a section
A simple way to picture Common Hardware and Software Issues
3 times this month, your kitchen sink has drained slower and slower until it stopped completely. At first, you noticed the water taking an extra 10 seconds to disappear. A few days later, it took a full minute. Now, standing water sits in the basin for hours. You know the issue is somewhere in the pipe, but you have to figure out whether it is a simple clog of food scraps near the drain opening, a buildup of grease deeper in the pipe, or a problem with the main house drain outside. Each possibility requires a different fix. If you just keep pouring drain cleaner into the same spot, you might temporarily clear the top blockage but miss the real problem further down. Worse, if you ignore the slow drain and keep using the sink, water may overflow onto the floor and damage the cabinet below.
This is exactly how hardware and software issues work in IT. A slow computer could be a temporary software conflict (the food scraps near the drain), a failing hard drive (the grease deep in the pipe), or a network problem (the main house drain). You need a systematic approach: observe the symptoms, isolate the cause, and apply the correct fix. Just like you would check the drain trap before calling a plumber, an IT professional checks the simplest, most likely cause first — and escalates only when necessary. The cost of guessing wrong is downtime, data loss, and frustrated users.
The CompTIA Tech+ exam expects you to understand a structured approach to troubleshooting, not just a grab bag of fixes. This is called the troubleshooting methodology — a step-by-step process that ensures you solve the root cause, not just the symptom. The six steps are: identify the problem, establish a theory of probable cause, test the theory, establish a plan of action, implement the solution, verify full system functionality, and document findings.
First, identify the problem. This means gathering information from the user: What were you doing when it happened? When did it start? Has this happened before? You also check the obvious — is the device plugged in? Is the power switch on? Is there an error message on screen? For example, a user says 'My computer wont start'. You check the power cable, the monitor cable, and the power button. If the power light is off, the problem is likely power-related. If the light is on but the screen is black, the issue may be the monitor, the video cable, or the graphics card.
Second, establish a theory of probable cause. This is your educated guess based on the symptoms. You start with the simplest, most likely cause first. For a computer that wont start, the simplest cause is that it is unplugged. The next simplest is a dead power supply. You do not start by assuming the motherboard is fried. You work from simple to complex. This is often called Occam's Razor in IT — the simplest explanation is usually the right one.
Third, test your theory. If you think the power cable is loose, you push it in firmly. If you think the power supply is dead, you try a known-working power supply or use a power supply tester. If the computer now starts, you have confirmed the theory. If not, you move to the next theory. You test each theory one at a time, and you do not skip steps.
Fourth, establish a plan of action. Once you have identified the actual cause — say, a faulty power supply — you plan how to fix it. The plan includes: what tools you need (a screwdriver to open the case), what replacement parts you need (a compatible power supply), and what safety precautions to take (power off, unplugged, anti-static wrist strap). You also consider the impact: if you replace the power supply, will the user lose data? No. But if you need to replace the hard drive, you need a backup plan.
Fifth, implement the solution. You execute the plan step by step. For a power supply replacement, you unplug all cables, remove the old unit, install the new one, and reconnect everything. You double-check connections before powering on.
Sixth, verify full system functionality. After the fix, you boot the computer and confirm it works normally. You also check that nothing else was broken during the repair — for example, that all fans spin, all USB ports work, and the operating system loads without errors. You ask the user to test it themselves. Finally, document findings. You write down what the problem was, what you did to fix it, and any follow-up actions needed. This helps if the same problem occurs again.
Now let us apply this to software issues. Software issues are problems with programs, operating systems, drivers, or settings — not physical hardware. Common software issues include: application crashes, blue screen errors (BSOD or stop errors), slow performance, driver failures, and malware infections. The troubleshooting steps are the same.
For example, a user says 'Excel keeps crashing when I open my budget file'. You identify the problem: the crash occurs only with this specific file, not other files. Theory: the file is corrupted. Test: open the file on another computer — it crashes there too. Plan: use Excels built-in repair feature. Implement: run the Open and Repair command. Verify: the file opens and all data is intact. Document: note the file name and the repair outcome.
Common hardware issues include: device not powering on, overheating (loud fans, thermal shutdown), storage drive failure (clicking noises, data loss, slow access), memory failure (random crashes, blue screens), and peripheral failure (keyboard keys not working, mouse cursor jumping). Each of these is diagnosed by isolating the component. For overheating, you check if fans are spinning and vents are clear. For storage failure, you run a diagnostic tool like CHKDSK (Check Disk) or SMART (Self-Monitoring, Analysis, and Reporting Technology) status check.
A critical concept is the difference between a symptom and a cause. A symptom is what the user sees — 'My screen is blue with white text'. The cause could be a bad driver, failing RAM, overheating, or a corrupted operating system file. Do not fix the symptom; fix the cause. The troubleshooting methodology is the tool that gets you from symptom to cause.
Another key idea is the boot process. Understanding what happens when you press the power button helps you diagnose startup issues. The basic boot sequence is: power on, POST (Power-On Self-Test) checks hardware, BIOS/UEFI (Basic Input/Output System / Unified Extensible Firmware Interface) loads boot device, boot loader loads the operating system, and the OS loads essential drivers and services. If any step fails, you get a specific error. A single beep from the motherboard usually means POST passed. Continuous beeps mean a hardware problem — often RAM or graphics card. No beeps and no display means a power or motherboard issue.
For the exam, you must know specific error messages and what they mean. For example, 'No boot device found' means the computer cannot find a hard drive or SSD with an operating system. 'CMOS battery failure' means the small battery that keeps BIOS settings is dead. 'Disk boot failure' is similar to no boot device. 'Missing operating system' means the boot loader cannot find the OS files on the drive.
You also need to know about using Safe Mode. Safe Mode loads Windows with only essential drivers and services. It is used to diagnose problems that occur during normal boot. If the problem disappears in Safe Mode, the cause is likely a third-party driver, a startup program, or a service. You can then disable the problematic item. Accessing Safe Mode is done by pressing F8 during boot (older Windows) or using the recovery environment (Windows 10 and 11).
Finally, you must understand the difference between a hardware fault and a software fault. A hardware fault is physical — a broken fan, a dead hard drive, a loose cable. A software fault is logical — a corrupted file, a misconfigured setting, a buggy update. The same symptom can have either cause. For instance, random crashes can be caused by faulty RAM (hardware) or a faulty driver (software). The troubleshooting process helps you determine which it is. You always test the simplest, cheapest possibility first. That means checking software settings and drivers before opening the case and replacing components.
Identify the Problem
Gather information from the user and check obvious issues. Ask open-ended questions: 'What were you doing when it happened?' 'Has this happened before?' Look for error messages, check cables, and verify power. This step narrows down the scope of the issue.
Establish a Theory of Probable Cause
Based on the symptoms, make an educated guess about what is wrong. Start with the simplest, most likely cause. For a computer that will not start, unplugged cables are the simplest cause. Do not assume a dead motherboard yet. List multiple possible causes in order of likelihood.
Test the Theory
Perform actions to confirm or disprove your theory. If the theory is that a cable is loose, reseat it. If the computer starts, the theory is confirmed. If not, move to the next most likely cause. Test one theory at a time to avoid confusion.
Establish a Plan of Action and Implement the Solution
Once you have identified the actual cause, decide what to do. If the fix requires a replacement part, order it. If it requires a configuration change, prepare the steps. Then execute the plan carefully, following safety procedures like powering off and unplugging the device.
Verify Full System Functionality
After implementing the fix, check that the original problem is resolved and that no new issues have appeared. Boot the system, run the affected program, and ask the user to test it themselves. If applicable, run a full system check to ensure everything works.
Document Findings, Actions, and Outcomes
Write down what the problem was, what the root cause was, what steps you took, and what the final outcome was. Note any serial numbers, error codes, or software versions. This record helps with future troubleshooting and can be shared with other IT staff.
You are a junior IT support technician at a small accounting firm with 30 employees. It is a Tuesday morning, and you receive a ticket from a user named Priya: 'My computer is running very slowly this morning. It took five minutes to open Outlook, and now Excel freezes whenever I switch between windows.' This is a typical real-world scenario.
You start by identifying the problem more precisely. You call Priya and ask: When did the slowness start? Right after I logged in this morning. Were there any updates or changes yesterday? I installed a new accounting software plugin yesterday. Did you restart the computer after the install? No, I just kept working. Have you checked Task Manager? I dont know how.
From this conversation, you have a strong theory: the new plugin may be causing a resource conflict or memory leak. Your theory is that the plugin is using too much CPU or RAM, or it is conflicting with another program. Next step: test the theory. You ask Priya to press Ctrl+Alt+Delete and open Task Manager. You ask her to sort processes by CPU usage. She tells you the accounting software plugin is using 98% of the CPU. That confirms the theory.
Your plan of action: disable the plugin, restart the accounting software, and see if performance returns to normal. You walk her through the steps: open the accounting software, go to Add-Ins or Plugin Manager, disable the new plugin, exit the program completely, then reopen it. You also ask her to restart the computer to clear any residual memory issues.
After the restart, she opens Outlook and Excel. Both open in under 10 seconds. She can switch between windows without freezing. You have verified full system functionality. Now you document: ticket number, user name, problem description, theory, steps taken, outcome. You also add a note: The plugin vendor may need to be contacted about the performance issue. Recommend updating the plugin to a compatible version.
Here is what you do not do: you do not immediately assume the hardware is failing. You do not order a new computer. You do not reinstall the operating system. You follow the structured process, and it saves the company money and downtime.
Another common scenario is hardware failure. A user reports that their computer makes a clicking noise and files take a long time to open. You identify the symptom: clicking noise from the hard drive area. Theory: the hard drive is failing. Test: run a SMART diagnostic using a tool like CrystalDiskInfo or the built-in CHKDSK. The result shows 'Reallocated Sectors Count' is critically high — the drive is predicting its own failure.
Plan: back up all user data immediately, then replace the hard drive. You instruct the user to copy important files to a network share or external drive. You then order a replacement SSD (solid-state drive — faster and more reliable than a traditional hard drive). Implement: power down the computer, replace the drive, install the operating system and software, restore user data from backup. Verify: the system boots normally, all files are accessible, no more clicking noise. Document: drive serial number, failure code, backup location, replacement details.
In a real business, documentation is crucial. If the same drive model fails in another computer, you can proactively replace them before they fail. You also create a knowledge base article: 'How to identify a failing hard drive using SMART data'.
Finally, consider a network issue. A user cannot access the internet, but other users can. Your steps: identify the problem (only this user, not others), theory (network cable unplugged or Wi-Fi turned off), test (check network icon in system tray — it shows a red X), plan (check physical cable connection), implement (reseat the Ethernet cable at both ends), verify (internet works now). If the cable is damaged, you replace it. This seems simple, but beginners often skip the obvious checks and waste time on complex solutions.
The FC0-U71 exam devotes significant attention to the troubleshooting methodology. You will be expected to recall the six steps in order, and apply them to specific scenarios. The exam does not just ask you to list them — it presents a symptom and asks 'What should you do next?' or 'What is the most likely cause?'
The exact steps you must memorise are: 1) Identify the problem. 2) Establish a theory of probable cause. 3) Test the theory to determine cause. 4) Establish a plan of action and implement the solution. 5) Verify full system functionality and, if applicable, implement preventive measures. 6) Document findings, actions, and outcomes.
Traps the exam sets: - 'Which step comes first after identifying the problem?' The answer is always 'Establish a theory of probable cause', not 'Implement a solution' or 'Replace the component'. Beginners often jump straight to fixing. - The exam may ask: 'A user reports that their computer is slow. Which of the following is the best first step?' The correct answer is 'Ask the user what changed recently.' Not 'Run a virus scan' or 'Upgrade the RAM'. - They love to test 'Most likely cause' questions. For a no-display issue, the most likely cause is a loose cable, not a dead motherboard. For a printer that is not printing, the most likely cause is the printer being offline or out of paper — not a corrupted driver. - They test the difference between a symptom and a cause. For example: 'Which of the following is a symptom of a failing hard drive?' Answer: 'Clicking noise' (not 'Hard drive failure' as that is the cause). - They test specific error messages: 'What does the error message 'No boot device found' indicate?' Answer: 'The computer cannot find a hard drive or SSD with an operating system.' - They test the boot process: 'During the boot process, what does a single beep from the motherboard normally indicate?' Answer: 'That POST completed successfully.' - They test about Safe Mode: 'You suspect a newly installed driver is causing blue screen errors. What mode should you boot into?' Answer: 'Safe Mode.' - They test about hardware vs software: 'Which of the following is a hardware issue?' A: 'A broken fan' (hardware). B: 'A corrupted system file' (software). - They test about overheating: 'A computer shuts down unexpectedly after running for 30 minutes. What is the most likely cause?' Answer: 'Overheating due to fan failure or blocked vents.' - They test about memory issues: 'A computer blue screens with different error codes. What is a likely hardware cause?' Answer: 'Faulty RAM.' - They test about storage: 'What tool can you use to check the health of a hard drive?' Answer: 'SMART status or CHKDSK.'
Key definitions to memorise:
POST: Power-On Self-Test — the initial hardware check when a computer starts.
BIOS/UEFI: firmware that initialises hardware and loads the operating system.
Safe Mode: a diagnostic mode of Windows that loads only essential drivers and services.
BSOD: Blue Screen of Death — a stop error screen that appears when Windows encounters a critical error it cannot recover from.
Driver: software that allows the operating system to communicate with a hardware component.
CHKDSK: Check Disk — a utility that scans the file system for errors.
SMART: Self-Monitoring, Analysis, and Reporting Technology — a monitoring system built into hard drives and SSDs that reports on their health.
CMOS battery: the small battery on the motherboard that powers the BIOS settings when the computer is off.
The exam may also present a scenario with multiple symptoms and ask you to identify the single most likely cause. For example: 'A user reports that their computer is slow, the fan is loud, and the bottom of the laptop is hot. What is the most likely cause?' Answer: 'Dust blocking the vents and causing overheating.'
Finally, the exam will test your understanding of what to do after you fix a problem: you must verify full system functionality and document findings. Many students forget these final steps. Do not.
The six-step troubleshooting methodology is always followed in order: identify the problem, establish a theory, test the theory, implement a plan, verify functionality, and document findings.
Always start with the simplest and most likely cause before assuming a complex hardware failure.
A symptom is what the user sees or experiences; the cause is the underlying fault that must be identified and fixed.
The boot sequence begins with POST, which checks basic hardware, and a single beep typically means the hardware passed the test.
Safe Mode loads only essential drivers and is used to diagnose problems caused by third-party software or drivers.
Documenting every step of the troubleshooting process is essential for future reference and for creating a knowledge base that helps the entire team.
These come up on the exam all the time. Here's how to tell them apart.
Hardware Issue
Caused by physical damage or failure of a component (e.g., broken fan, dead hard drive).
Symptoms include physical signs like noise, heat, or smell.
Requires replacement or repair of the physical component.
Software Issue
Caused by logical errors like corrupted files, misconfigured settings, or buggy updates.
Symptoms include error messages, crashes, or slow performance without physical signs.
Requires reinstallation, update, or configuration change.
Symptom
What the user observes or experiences (e.g., slow performance, blue screen, clicking noise).
Not fixed directly; you must address the underlying cause.
Multiple symptoms can point to the same cause.
Cause
The root reason for the symptom (e.g., failing hard drive, corrupted driver, overheating).
The target of the troubleshooting process.
One cause can produce multiple symptoms.
POST (Power-On Self-Test)
Runs automatically when the computer is powered on.
Checks basic hardware components like CPU, RAM, and storage.
Typically reports results with beep codes or diagnostic LEDs.
Boot Loader
Runs after POST, if hardware passes the test.
Locates the operating system on the storage device and loads it into memory.
If it fails, you see messages like 'No boot device found'.
Mistake
If a computer does not turn on, the power supply is definitely dead.
Correct
The power supply could be dead, but the most common cause is that the power cable is loose, the outlet is faulty, or the power switch on the back of the power supply is off. Always check the obvious first.
Beginners tend to assume the worst-case scenario because they have heard horror stories about failing power supplies. They skip the simplest checks that often solve the problem.
Mistake
A blue screen error always means the RAM is broken.
Correct
Blue screen errors can be caused by faulty RAM, but also by corrupted drivers, overheating, failing storage, or malware. The error code on the blue screen points to the specific cause.
RAM is a common culprit, so many beginners latch onto it. They do not realise that driver issues are actually more frequent causes of blue screens.
Mistake
If a program keeps crashing, reinstalling the operating system is the fastest fix.
Correct
Reinstalling the operating system is a last resort. The first step should be to check for program updates, restart the program, or reinstall just that specific program. Reinstalling the OS is time-consuming and may delete user data if not backed up.
Reinstalling the OS feels like a clean slate, so beginners think it is a magic bullet. They underestimate how much time and data loss it costs, and they overestimate how often it is necessary.
Mistake
All hardware problems cause error messages on screen.
Correct
Many hardware problems cause no error message at all. For example, a dead hard drive may cause a 'No boot device' message, but a failing fan just makes noise — or no noise at all — with no on-screen warning until the system overheats and shuts down.
People expect computers to announce their problems like a car dashboard warning light. In reality, many hardware failures are silent until they become catastrophic.
Mistake
If a computer is slow, it must need more RAM.
Correct
Slow performance is often caused by too many programs running at startup, malware, a fragmented hard drive, or overheating causing the CPU to throttle down. Adding more RAM is one possible solution, but it is not the most likely one.
Marketing and common wisdom both say 'more RAM = faster computer'. Beginners do not understand that RAM is a resource, and if the system is not using all of it, adding more will not help.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
Check that the power cable is firmly plugged into both the computer and the wall outlet. Ensure the power switch on the back of the power supply unit is in the 'on' (I) position. If you are using a power strip or surge protector, check that it is turned on and working.
A blue screen of death (BSOD) indicates that Windows encountered a critical error it could not recover from. It is usually caused by a faulty driver, failing hardware (like RAM or a hard drive), or a corrupt system file. Read the error code on the screen to narrow down the cause.
On Windows 10 and 11, hold the Shift key while clicking Restart to access the recovery environment, then choose Troubleshoot > Advanced Options > Startup Settings > Restart, and press 4 or F4 for Safe Mode. On older Windows, press F8 repeatedly during boot before the Windows logo appears.
A clicking noise from a hard drive often indicates a mechanical failure. Back up your important files immediately if you can. Then run a diagnostic tool like CHKDSK or check the SMART status. If the drive is failing, replace it as soon as possible to avoid data loss.
This can be caused by overheating (check that fans are working and vents are clear), a failing power supply, or a software issue like a driver problem. Check the Windows Event Viewer for error logs, and run a system file checker (sfc /scannow) to repair corrupt system files.
If the problem occurs consistently with a specific program or after a software update, it is likely software-related. If the problem occurs at random times, involves physical symptoms (noise, smell, heat), or happens across multiple programs, it may be hardware-related. Testing in Safe Mode can help isolate software causes.
You've finished Common Hardware and Software Issues. Continue through the FC0-U71 study guide to build a complete picture of the exam.
Done with this chapter?