From a symptom to useful evidence
Device Troubleshooting Planner
Choose the problem you are trying to understand. Compare what happens here, in another application and on another input or output path.
No account, automatic device scan or AI diagnosis. The complete instructions are readable without JavaScript.
What are you noticing?
Choose one symptom for a focused comparison. You do not need to run every device test.
Plan a Missing Keyboard Input Check
Separate page focus, layout and connection problems with a three-comparison keyboard worksheet and a clear record for support.
Open this plan →3 controlled comparisons · printable recordPlan an Unexpected Mouse Click Check
Distinguish short click intervals, application double-click behavior and connection changes without labeling every fast pair a faulty switch.
Open this plan →3 controlled comparisons · printable recordPlan a Camera or Microphone Access Check
Work through browser permission, selected input and another application before treating a camera or microphone startup error as hardware failure.
Open this plan →3 controlled comparisons · printable recordPlan a Silent or One-Sided Audio Check
Compare the selected audio route, channel position and another output with low-volume playback and a printable evidence record.
Open this plan →3 controlled comparisons · printable recordPlan a Suspicious Screen Pixel Check
Compare a suspicious display spot across solid colors and applications, then prepare a cautious manufacturer-support record without pixel-repair claims.
Open this plan →3 controlled comparisons · printable recordPlan a Controller Drift and Mapping Check
Compare browser controller discovery, centered axes and game behavior before changing dead zones or assuming a damaged stick.
Open this plan →Use the comparison, not a pass/fail label
A browser result answers a narrow question: what input, media or display behavior reached this page under these conditions? It does not inspect a cable, switch, amplifier or panel. A second application or connection helps you locate where the behavior changes without inventing a physical cause.
- Keep a baseline. Note the browser, operating-system family, connection and exact harmless action. Repeat it before changing a setting.
- Change one factor. Comparing two browsers while also changing the cable and device creates several possible explanations. Separate those comparisons.
- Keep uncertainty visible. A skipped step is not tested. A working sample is not a reliability guarantee. A recurring problem needs model-specific support when a repair or warranty decision matters.
What your record contains
Each plan provides choices with visible interpretation tables, optional context and before/after notes, and a plain-text summary. Notes and choices remain in the open page. Copy or print deliberately if you want to retain them; the site does not save or submit the record.
When to stop
Do not use browser comparisons to investigate sparking, overheating, liquid damage or electrical safety. Stop using unsafe equipment and contact qualified support. Do not apply pressure, heat or unapproved cleaning methods to make a test result change.
Read the testing methodology · Read the full guide library · Suggest a correction