Common Hardware Faults and How to Diagnose Them
Most peripheral problems aren't mysterious once you know the short list of ways each device tends to fail. The trick to diagnosis is isolation: change one thing at a time, confirm what's working before chasing what isn't, and let a simple test tell you whether the fault is the hardware, the connection, or the software. This is a field guide to the faults that turn up most often, and the quickest way to pin each one down.
The universal first move: rule out software
Before blaming any device, separate hardware from software by testing it somewhere neutral. A browser-based test is ideal for this because it sidesteps whatever app you were fighting with. If your mic works in the microphone test but not in a specific meeting app, the hardware is fine and the problem is that app's settings or permissions. If it fails everywhere, the fault is lower down — the device, its driver, or its connection. That single split saves more time than any other diagnostic step, so make it your reflex.
Webcam faults
Cameras fail in a small number of recognizable ways. A black preview almost always means the device is busy — held by another app or a background call — rather than broken; close everything using it and retry. A camera that's missing entirely from the device list points to a connection or privacy-shutter issue, or a disabled device in your operating system. A picture that's present but grainy or soft is usually a lighting problem, not a fault, because cameras drop resolution and crank gain in dim rooms. Confirm all of this in the webcam test: a live image rules out the device, and the resolution readout tells you whether you're getting the mode you paid for.
Microphone faults
The classic mic fault isn't a dead microphone at all — it's the wrong input selected, with the system listening to a built-in mic while you talk into a headset. A flat meter on one device and a lively one on another confirms it instantly. Genuine faults include a mic that's far too quiet (low gain, or a mic positioned too far away), one that clips and distorts (gain too high), and one that produces a constant hiss or hum (interference, a bad cable, or a ground loop on desktop audio). The microphone test shows all three as distinct meter and waveform behaviours, so you can tell "quiet" from "clipping" from "noisy" at a glance.
Speaker and headphone faults
The most common speaker complaint — "sound only comes from one side" — is usually a loose connector or a dead channel, and the left/right tones in the speaker test isolate it in seconds. A buzz or rattle at certain volumes or pitches suggests a physically damaged driver or something vibrating loose, which the frequency sweep will expose as you pass through the offending range. And "no sound at all" is, more often than people admit, the wrong output device — audio routed to a monitor's unused speakers or to Bluetooth headphones in another room. Verifying the output in a simple tone test rules the hardware in or out before you go hunting through settings.
Keyboard faults
Keyboards give you three recurring problems. A dead key that never registers means a failed switch or a break in the matrix. A stuck or chattering key repeats or fires on its own, usually from debris or a worn switch. And missed simultaneous keys — combinations that silently don't register — are the blocking behaviour covered in our ghosting and rollover article. The keyboard tester catches all three: pressed keys stay lit so dead ones are obvious by their absence, a key lighting up untouched reveals chatter, and the simultaneous-key counter shows where blocking kicks in. Before replacing anything, try compressed air and a reseat of the keycap, since a surprising share of "dead" keys are just dirty.
Mouse faults
Mice wear out at the switches and the sensor. A double-click fault — where one deliberate click registers as two — is the most common aging failure, caused by a worn button switch, and you can catch it by clicking once slowly in the mouse test and watching whether the counter jumps by two. A cursor that stutters or jumps points to a dirty or failing sensor, or a poor surface; the live position readout makes erratic tracking visible. A scroll wheel that skips or scrolls the wrong way and a button that doesn't register round out the list, and both show up directly on the tool's indicators.
Monitor faults
Beyond dead and stuck pixels — which have their own dedicated test and a full article — monitors show backlight bleed (uneven glow at the edges, visible on a full black screen), banding (visible steps in what should be a smooth gradient), and uniformity problems (patches that are brighter or a different tint than the rest). A solid-colour test surfaces every one of these: black reveals bleed, grey reveals uniformity issues, and the pure colours reveal stuck sub-pixels.
Game controller faults
Controllers have their own signature failure: analog stick drift, where a stick reports movement even when you're not touching it, causing your character or camera to creep on its own. It's caused by wear in the stick's potentiometers or contamination inside the mechanism, and it's one of the most common reasons controllers get retired. Browsers can't always read a controller through these general-purpose tools, so if you suspect drift, use a dedicated checker like stickdriftcheck.com, which visualizes each stick's resting position and shows drift immediately.
A diagnostic mindset
Whatever the device, the method is the same: confirm the good before chasing the bad, change one variable at a time, and use a neutral test to separate hardware from software. Nine times out of ten the fault turns out to be a loose cable, a wrong device selection, or a setting — not a broken part — and the few minutes it takes to run a quick check will tell you which. When it genuinely is the hardware, you'll at least know exactly what to describe on a warranty claim.