Troubleshooting Common Hardware Issues

Effective troubleshooting is a methodical process — not random trying of different things until something works. This systematic approach resolves most hardware problems faster and more reliably:

• Step 1: Identify the symptom precisely — 'it does not work' is not a useful problem description. 'The monitor displays no image when the computer is on, the power light is amber, and it worked correctly this morning' gives you specific, actionable information. Document the exact symptom before attempting any fix.
• Step 2: Check the simple things first — is it plugged in? Is the power on? Is it connected? Are the cables secure? Most hardware issues in office environments are connection or power problems. Before assuming a device is broken, physically inspect every cable and connection. Reseat (unplug and replug) any cable that is involved in the problem.
• Step 3: Restart and test — restart the computer and test the device again. Many driver-level hardware issues resolve with a restart. If the device has its own power, turn it off, wait 30 seconds, and turn it back on. This is the troubleshooting step most often skipped and most often effective.
• Step 4: Test with known-good components — if you have a spare cable, try replacing the suspect cable. If you have another monitor, connect it to the same computer to determine whether the problem is the monitor or the computer. Isolation testing tells you exactly which component is faulty.
• Step 5: Document and escalate — if the simple steps do not resolve the issue, document exactly what you tried and what happened, then escalate to IT with that documentation. 'I have tried X, Y, and Z and the behavior is still [specific symptom]' tells IT exactly where to start, saving time for everyone.

These are the most frequently occurring hardware issues in office environments — and most can be resolved without IT:

• Monitor no image: Check that the monitor power light is on (if not, check the power cable and outlet). Check that the video cable (HDMI or DisplayPort) is securely connected at both the monitor and computer ends. Try pressing a key or moving the mouse (the monitor may be in sleep mode). If the computer has multiple video outputs, try a different port. If the computer shows on a different monitor, the original monitor may need replacement.
• Keyboard or mouse not responding (wired): Disconnect and reconnect the USB cable. Try a different USB port on the computer. Restart the computer with the device connected. If still not working, try the device on another computer — this tells you if the device or the computer's USB port is the problem.
• Keyboard or mouse not responding (wireless): Check the battery level (replace batteries even if recently installed — a battery may fail unexpectedly). Check that the USB receiver dongle is firmly plugged in and try a different USB port. Power off the keyboard/mouse, wait 10 seconds, power on. Check the pairing button if the device uses Bluetooth.
• USB device not recognized: Try the device in a different USB port. Restart the computer. Check Device Manager (right-click Start > Device Manager) for any yellow warning triangles indicating a driver problem. If a USB hub is in use, plug the device directly into the computer to rule out the hub as the problem.

Knowing when to escalate is as important as knowing how to troubleshoot — attempting to fix things beyond your authorization can cause more damage:

• Escalate hardware issues you cannot resolve after the five-step process — if the device still does not work after systematic troubleshooting, it likely needs repair or replacement by IT. Do not continue attempting fixes beyond the connection, restart, and cable-swap level.
• Escalate issues that require opening hardware — do not open a computer case, replace internal components, or attempt to repair printer internals. These tasks require technical training and may void warranties.
• Escalate network connectivity problems beyond the basic check — if the internet is down for the whole office after checking the router (as covered in Module 3), that is an IT or ISP issue requiring their intervention. Do not attempt to reconfigure the router.
• Write a clear incident report for IT — include: the device name/model, what exactly is happening, what you already tried, and when the problem started. A clear incident report means IT does not have to spend the first 10 minutes of their engagement re-gathering information you already have.