How to document hardware problems for warranty support

Warranty support can help faster when you show what the device does, when it happens, and what you have already checked. Intermittent faults are especially hard to assess from a description like “it keeps disconnecting.”

Use a short symptom log and the Test Everything report to give support useful evidence. A browser test can help describe a problem, but it cannot prove the cause or replace the manufacturer's own checks.

Document the problem

1. Write down the device details. Note the model, operating system, and the date you first noticed the issue. For an external device, include its model and how it connects. Give the serial number to the manufacturer through its official support process, but cover it in images you post publicly.
2. Describe one repeatable symptom. Say exactly what you see or hear, what you were doing, and how often it happens. For example: “The external keyboard misses several letters after about ten minutes of typing, then works again after I reconnect it.” Avoid guessing at the cause.
3. Try to reproduce it safely. Use the same app, cable, port, and conditions that usually trigger the issue. Record the time and whether the problem happened. Stop if the device becomes unusually hot, smells burnt, makes an alarming noise, or shows other signs of an electrical fault.
4. Run a browser check. Open Test Everything and follow its on-screen sequence. It runs tests step by step and provides a report. Note the relevant test results and whether the original symptom appeared during the check. Do not treat an unrelated result as evidence about the faulty part.
5. Collect clear evidence. Take a photo or video of a visible fault, or capture the exact error message on screen. Include enough of the device or app to show what is happening, but hide passwords, private messages, account details, and serial numbers when sharing publicly.
6. Make a concise support request. List the symptom, when it occurs, the checks you performed, and the relevant results. Attach only the evidence the manufacturer requests, and ask what diagnostic step they want next.

Keep a copy of your notes and the relevant report details. If you take a screenshot, check that it does not reveal private information before attaching it to a ticket.

What the test results mean

The related test shows a problem

Record the test name, the result shown, and the date. If the symptom also happens during normal use, describe both observations separately. A result can support your report, but it does not identify every possible cause or confirm that a part is defective.

The tests pass, but the problem still happens

A passing browser test means the tested function responded during that check. It does not rule out an intermittent fault, a problem that appears only in one app, or an issue that depends on heat, movement, a particular cable, or a specific workload. Tell support when the fault appears and when it does not.

A test cannot access the device or feature

Write down the message and what you were testing. A browser permission, unsupported browser feature, or disconnected device can prevent a check without showing that the hardware is broken. Say whether you saw the physical symptom outside the test.

The issue is visible but not covered by a browser test

Use a clear photo or video and a short description. For example, a damaged hinge, loose connector, unusual screen mark, or casing crack may need inspection by the manufacturer's service team. A browser report cannot assess physical damage inside the device.

For more context on what a browser report can and cannot establish, see What a good hardware report cannot prove.

Rule out simple causes without risking the warranty

1. Check the connection. For an external device, make sure the plug is seated and inspect the cable for visible damage. If it is safe and easy, try another compatible port and note whether the symptom changes.
2. Restart and repeat once. Restart the computer, reconnect the device, and try the same action again. Record whether the fault returns. Repeated stress tests are not necessary for a support report.
3. Compare with a second app or device. If the problem is with a keyboard, mouse, camera, or headset, try it in another app or on another compatible computer if available. If the symptom follows the device, include that observation. If it appears in only one app, tell support which app and version.
4. Keep changes reversible. Do not open the device, remove sealed parts, or install unofficial firmware just to collect evidence. Check the warranty terms or ask support before attempting a repair or reset that could erase data.

When the problem may be hardware

A fault is more likely to need hardware service if it repeats with a known-good cable or compatible device, follows the same component between apps or computers, or is visible as physical damage. These clues still do not prove which part failed. A computer can also have a driver, power, or software problem that looks like hardware trouble.

Keep the original notes, dates, and unedited evidence. Contact the manufacturer or authorized service provider while the device is covered, describe what you observed without naming a cause as fact, and ask before opening or repairing it.