Menu
Hardware
Homelab & NAS
Tools & Builders
Prices & Data
Troubleshoot

Start with what happened

Open the guide that matches the symptom

Each route opens the guide for that symptom. It organizes your next observation; it doesn't identify a failed part. To keep notes while you test, start an incident record below.

Save on this device

Save a browser copy; review each export

Saving writes to this browser profile only. Clearing site data, resetting the profile, or using another device can remove or hide the record. Download the full JSON before browser cleanup or repair work.

Before sharing: full JSON and the plain-text summary include diagnostic notes. A limited snapshot omits named note fields and the compatibility checklist but retains the title, products and tool inputs. Check what each format retains.

Persistent incident record

Track the evidence without losing the machine context

Open Hardware Projects

Inputs

Saved on this device

Choose a recognizable title. It is retained in limited share links, so avoid private names here.

Write what you could see, hear, or read. Avoid a diagnosis here.

Exact models, firmware, OS, driver, application, and relevant versions.

Source → port → cable or adapter → display, network hop, storage bus, or container boundary.

Local date and time, workload, idle/load transition, frequency, and whether it repeats.

Update, setting, cable, component, workload, move, or maintenance before the first event.

Exact messages, LEDs, temperatures with units, event IDs, counters, logs, and what stayed running.

One changed variable per line: action, controlled condition, duration or repetitions, and observed result.

Resolved, reproduced, not reproduced, still unknown, or the exact evidence needed next.

Exports use the current form, including unsaved edits. A limited link can still reveal the title or a saved device name. Deleting the local project cannot recall files, pasted summaries or shared links. Review the field examples.

Live result

Created
Last saved

This incident has no linked machine products yet.

Loading projects stored in this browser…

Capture before changing the machine

The most useful incident record starts with what the machine did, not what you think failed. Write the exact message, indicator, sound, or loss of function. Add the local date and time, workload, and what stayed operational. A monitor that displays No Signal, a screen that goes black and returns, and a PC that loses power are three different observations even when they happen during the same game.

Save volatile evidence before a restart when it is safe to do so. That can include an on-screen error, an event timestamp, a container state, a temperature with its unit, or the name and version of a driver. The workbench does not run commands, change settings, restart services, erase logs, or decide that a part is bad.

Map the full path

Record the path between the thing producing data and the place the symptom appears. For a display that might be GPU → GPU port → cable or adapter → monitor input → monitor. For a drive it can be SSD → M.2 slot or cable → controller → firmware → operating-system driver. For a container it includes the container limit, parent cgroup, host memory, and time window.

Exact hardware and software identity keeps later tests comparable. Include model numbers, firmware, operating system, driver, application, and workload when they matter. A linked product from Hardware Projects stays attached when you edit the diagnostic record here.

Change one variable per controlled test

For each test, write four things:

  1. The one variable changed.
  2. The conditions held constant.
  3. The duration or number of repetitions.
  4. The observed result, including a unit where one applies.

If you changed a cable, driver, power limit, and graphics setting together, record that as an uncontrolled test. It may restore service, but it cannot show which change mattered. Keep destructive actions, firmware changes, and storage writes outside an improvised experiment; use the exact device documentation and a current backup before a step can put data or recoverability at risk.

Blank worksheet for JavaScript-off use

Copy this block into a local text file when browser scripting is unavailable:

Hardware incident title:
Record created (local date and time):
Last updated (local date and time):

Exact symptom:

Hardware and software:

Display, signal, storage, network, or container path:

Trigger, timing, frequency, and workload:

Recent change before the first event:

Observations and evidence:

Tests already run:
- Variable changed:
- Conditions held constant:
- Duration or repetitions:
- Observed result:

Outcome or next evidence checkpoint:

Save and share the record

  • Save on this device keeps the record in this browser profile. Its URL holds a local ID, so opening it on another device does not bring the notes with it.
  • Download full JSON is the backup: every supported project field, including the diagnostic notes, evidence and compatibility records. Treat it as private if it holds serial numbers, hostnames, addresses, account names, file paths or log excerpts. Importing it in Hardware Projects opens an unsaved preview; choose Save as a new project to keep it.
  • Copy private summary puts the title, dates and completed diagnostic fields on your clipboard as plain text. It does not automatically include product references, tool state, separate evidence or compatibility records.
  • Copy limited snapshot link leaves out the diagnostic text, evidence, constraints, use case and compatibility records, but keeps the title, type, products, tool inputs and dates, which can still identify your equipment.

Every export uses the current form, unsaved edits included. Removing the browser project does not revoke files, pasted summaries, copied links or anyone else’s saved copy; the privacy guide compares the full and limited payloads. Download the JSON before you clear site data, move browser profiles, reinstall the browser or start repair work that may touch the operating-system drive.

Frequently asked questions

How do I find out what is causing my PC problem?
Start from the exact symptom rather than a guess about the part: write down what you saw, heard or read and when. Open the guide for that symptom from the routes at the top, then change one thing at a time and record each test, so a fix tells you which change mattered.
Where does the Hardware Diagnostic Workbench save my notes?
Save writes the project to this browser profile on this device, without creating an account or uploading the record as part of that save. Browser site-data cleanup, a profile reset, private browsing, or moving to another device can make it unavailable. Download a private full JSON backup when the notes matter.
Does the share URL include my diagnostic notes?
The limited snapshot omits diagnostic text, evidence, constraints, use case and compatibility records. It retains the title, products, supported tool inputs and dates, which can still identify your equipment. Full JSON and the plain-text summary include diagnostic notes. All three can include current unsaved form edits, so review them before sending.
Can this workbench diagnose a failed component automatically?
No. It records observations and routes you to a guide based on the symptom you select. A symptom can have several causes, so the record does not turn a black screen, restart, WHEA record, storage warning, or container exit into an automatic verdict.
What should one test entry contain?
Name the single variable you changed, the conditions held constant, the duration or number of repetitions, and the observed result. If several settings changed together, list that as an uncontrolled test instead of attributing the result to one setting.

Updates and corrections

Last updated
Methodology
See our methodology for research and review standards.
Update log
  • 2026-11-18 — The symptom routes now lead the page, a route for coil whine was added, and the export section was cut to the essentials.
Corrections
Spotted an error? Email a correction with the affected line and what you found. The draft includes this page’s address. Verified changes are recorded here. Contact details.