Home Hardware Diagnostic Checklist: Test Before You Repair or Return

When a monitor, keyboard, mouse, controller, microphone, speaker, or webcam behaves badly, the fastest response is often to change several things at once. That can make the symptom disappear, but it does not tell you what failed. A useful diagnosis follows a fixed order, changes one variable at a time, and records enough evidence to support the next decision.

This checklist is designed for a home, office, shop counter, or return-window inspection. It uses browser tests for screening and comparison, then adds operating-system and second-device checks. Read the browser hardware testing methodology for the measurement limits behind each step.

Before you start

Create a short test record with:

• exact brand and model;
• purchase date and return deadline;
• operating system and browser;
• cable, adapter, hub, receiver, and port in use;
• relevant firmware, profile, resolution, refresh rate, or audio setting;
• when the symptom started and whether it is constant or intermittent.

If the device is new, preserve packaging and do not open, press, heat, spray, or disassemble it before checking the seller's rules. A reversible comparison is safer than a physical “fix.” Stop any test that produces excessive heat, smell, smoke, sparking, painful sound, battery swelling, or an unstable power connection.

Step 1: Write a precise symptom

Replace a general complaint with an observable statement.

The statement determines which test to run and what would disprove the first theory.

Step 2: Check power, connection, and selection

Before measuring anything, inspect the basic signal path:

1. Confirm the device has power and sufficient battery.
2. Reseat the cable without forcing the connector.
3. Remove unnecessary hubs, docks, adapters, and extension cables.
4. Select the intended device in the operating system and browser permission prompt.
5. Check physical mute, input-source, profile, function-lock, and game-mode controls.
6. Keep a known-good cable or port available for the comparison pass.

Many “hardware” failures are selection problems. A webcam test may open the laptop camera instead of the USB camera. Channel audio may be routed to a monitor. A high-refresh display may still be configured at 60Hz. Write down the selected device rather than assuming the system chose correctly.

Step 3: Run the focused browser test twice

Choose the smallest relevant tool from the hardware test directory. Keep the tab visible and follow the on-page instructions. Run the same test twice before changing anything.

Two matching runs establish a basic baseline. Two very different runs are also useful: they show the symptom is intermittent or the test environment is unstable. Do not average away a dropout, disconnect, crash, or fixed visual defect.

Capture the useful evidence:

• a screenshot for settings, axes, permissions, and timing summaries;
• a photo for physical display defects, because a screenshot cannot contain a panel defect;
• a short note for sound, intermittent input, fan behavior, or disconnects;
• the time into the test when a crash or slowdown occurred.

Step 4: Change one variable

Use a comparison that targets the suspected layer:

Repeat the same two runs after the one change. If you change several variables, restart the comparison with a clean baseline before drawing a conclusion.

Display checklist

For a mark, flicker, wrong refresh rate, uneven field, or motion problem:

1. Clean the screen with the manufacturer-recommended method.
2. Use native resolution and confirm the intended refresh mode in the OS.
3. Open the Dead Pixel Test and inspect white, black, red, green, and blue.
4. Use a camera photo for a fixed physical mark; take it in normal room light and include enough screen area to show location.
5. Check another cable, input, and source device.
6. For uneven brightness or tint, repeat at the normal viewing position and brightness.
7. For missing high-refresh modes, verify the exact bandwidth supported by the GPU, port, cable, dock, and monitor input.

A mark that remains at the same physical location across colors and source devices is more likely to be in the panel. A mark visible inside a software screenshot on another display comes from rendered content or the graphics path, not the first panel.

Keyboard, mouse, and controller checklist

For missing keys, double input, inconsistent movement, low event rate, or stick drift:

1. Click inside the tester so the page has focus.
2. Compare the same input in a text editor, OS viewer, or game-controller settings panel.
3. Disable macros, remapping, game mode, and unusual device profiles temporarily.
4. Connect directly and test a second port.
5. Charge the device and compare wired, Bluetooth, and dedicated-receiver modes when available.
6. For combinations, test individual inputs first, then add keys or buttons one at a time.
7. For drift, release the stick gently and repeat after reconnecting; do not force calibration values to hide a mechanical problem.

System shortcuts and browser-reserved keys may never reach a page. A key that fails only in one browser is not yet evidence of a broken switch. A physical input that fails everywhere, including another computer, is much stronger hardware evidence.

Audio, microphone, and camera checklist

For silence, the wrong channel, no microphone level, a black camera view, or low delivered quality:

1. Confirm the browser has permission for the intended site and device.
2. Select the exact input or output instead of “default” when the interface allows it.
3. Check the operating-system volume mixer, input meter, privacy settings, and physical mute controls.
4. Close conferencing, streaming, recording, and virtual-camera software that may hold the device.
5. Test another browser, then another port or cable.
6. For cameras, improve room light before evaluating frame rate or noise.
7. For audio channels, keep volume at a comfortable level and never use a loud test to diagnose hearing.

The browser receives the stream negotiated by the system. A 1080p camera can deliver 720p because of light, bandwidth, active software, or constraints. Record both the advertised capability and the delivered stream without assuming one bad session proves a sensor failure.

Decide: configure, monitor, return, or repair

Use the evidence to choose the least risky next action.

Reconfigure when the symptom follows a browser, permission, profile, power mode, selected device, resolution, refresh setting, or software path.

Monitor when the result is within normal browser variation, cannot be repeated, and does not affect real use. Keep the baseline so you can compare if it becomes worse.

Return or contact the seller when a new device has a repeatable physical defect, advertised mode cannot be demonstrated with a compatible setup, or the product is unstable during its return window. Seller return terms are often simpler than a later warranty claim.

Request warranty or repair when the same defect persists across known-good cables, ports, browsers, settings, and a second compatible device. Provide the model, serial number when requested privately, purchase record, test conditions, photos or screenshots, and the exact comparison that isolated the device.

Final handoff record

Before contacting support, assemble one concise summary:

Model and connection: [device, cable, port]. Symptom: [observable failure]. Baseline: [two repeated results]. Comparison: [one changed variable and result]. Cross-check: [second browser, system tool, or computer]. Evidence: [photo or screenshot]. Safety and return status: [no physical modification; return deadline].

This format helps support reproduce the issue and reduces repeated basic questions. More importantly, it prevents an online test from being treated as proof of something it cannot inspect. The goal is not to collect the most scores; it is to make the next decision with the smallest amount of uncertainty.