Computer Hardware and Troubleshooting Basics: Fix Common PC Problems

Most computer problems in an office, school lab or cyber cafe are not serious. A loose cable, a full disk, a jammed print queue or a dusty fan causes far more breakdowns than a dead motherboard. If you know what each part does and check things in a sensible order, you can fix many problems in minutes — and when you cannot, you can tell the technician exactly what is wrong. This guide covers the hardware basics, safe working rules and a symptom-by-symptom checklist.

The topics match what a beginner's "Computer Hardware, Networking & Troubleshooting Basics" subject covers in a DCA-level course: parts and their functions, ports, basic networking checks and first-level troubleshooting. Everything here is first-level work that needs no special tools.

Parts of a computer and what they do

Common ports and connectors

Safety rules before you touch anything

• Save and shut down properly from the Start menu before checking cables or opening a cabinet. Then switch off at the wall socket and unplug.
• Wait a minute after unplugging and press the power button once to drain leftover charge before opening a desktop side panel.
• Static electricity can damage RAM and boards. Touch an unpainted metal part of the cabinet before handling parts, hold RAM by its edges, and avoid working on carpet.
• Do not force connectors. Every plug fits only one way. If it does not go in, turn it around or check you have the right port.
• Keep liquids away. If water or tea spills on a laptop or keyboard, switch off immediately, unplug, remove the battery if it is removable, and do not switch on until it is checked and fully dry.
• Back up before repairs. If the computer still works, copy important files to a pen drive or cloud storage before anyone formats or replaces anything.
• Office computers belong to the employer. Do not open cabinets, install software or change settings without permission from your supervisor or IT person.

The troubleshooting method: simple first

Technicians follow an order. Use the same order and you will rarely waste time:

1. Ask and observe. What exactly happens? When did it start? Was anything changed — new software, a power cut, the PC moved? Note any error message word for word or take a photo.
2. Check power and cables. Is the socket switched on? Is each cable firmly pushed in at both ends? Swap a doubtful cable with a known good one.
3. Restart. A full restart (not just closing the lid) clears many temporary faults.
4. Change one thing at a time and test after each change, so you know what fixed it.
5. Swap to isolate. Try the mouse on another PC, or another monitor on this PC. Whichever moves with the problem is faulty.
6. Write down what you did — useful if the problem returns or you need a technician.

Symptom checklist: likely cause and what to try

Work through the "What to try" column in order. Stop at the first step that fixes the problem.

Basic networking checks every student should know

Networking problems are the most common lab and office complaint. A few Command Prompt tools help you find where the problem is. Open Command Prompt by pressing Win+R, typing cmd and pressing Enter.

Press Ctrl+C to stop a ping that keeps running. In an office, check with the IT person before changing any network setting.

Preventive care: a monthly routine

• Shut down from the Start menu, not by pressing the power button or switching off at the wall.
• Use a UPS or at least a good surge protector; frequent voltage fluctuation damages SMPS and adapters.
• Wipe dust from vents, keyboard and screen with a dry soft cloth (screen: microfibre cloth, no harsh sprays).
• Keep Windows and antivirus (Windows Security is built in) updated; restart when updates ask.
• Keep free space on the C: drive; empty Downloads of old installers.
• Back up important files weekly to a second location — pen drive, external disk or cloud.
• Do not install pirated software or "cracks"; they are a major source of malware and are illegal.
• Eject pen drives with "Safely Remove" before pulling them out.

When to stop and call a technician

First-level troubleshooting has limits. Stop and call a qualified technician, the company's IT support or the manufacturer's authorised service centre when you see any of these:

• A burning smell, smoke, sparks, or a crackling sound from the SMPS, UPS or charger — switch off at the wall immediately.
• A swollen laptop battery (the case bulges or the touchpad lifts). Stop using and charging it.
• Liquid spilled inside a laptop.
• Clicking or grinding from a hard disk — back up immediately if the PC still works, then stop using it.
• Repeated blue screens after updates and driver checks.
• The device is under warranty — opening it yourself may cancel the warranty.
• The fix needs opening the cabinet and you are not trained or not permitted.

What to tell the technician

Give a short written note: model, what happens, when it started, any error code (with photo), and what you have already tried. This saves time and money, and shows you understand the machine — a quality employers value in any office or lab assistant.

Practice exercises

1. Label every port on the back of a lab desktop and write what plugs into each.
2. Open Task Manager and note the CPU, memory and disk usage when idle and when Chrome has ten tabs open.
3. Run ipconfig and write down your IP address and default gateway.
4. Unplug the network cable and run ping 8.8.8.8; plug it back and run it again. Compare the results.
5. Set a different default printer, print a test page, and set it back.
6. With your trainer's permission, watch a desktop being opened and identify the CPU fan, RAM sticks, storage drive, SMPS and CMOS battery.

These skills are useful well beyond IT jobs: data entry operators, office assistants and computer lab staff are expected to handle small problems without waiting. For the wider set of skills employers check, see the basic computer skills checklist.

Frequently asked questions