📝 Computer Health Symptoms: What to Check Before Asking

Most support conversations open with “my computer isn’t working” and then spend half an hour narrowing that down. Five minutes of preparation changes the whole exchange. A good symptom description says what you were doing, when it started, and what changed — and that is usually half the diagnosis.

Describe the conditions, not just the symptom

The word “slow” on its own carries no information. Note instead: slow while doing what, slow from startup or only after a while, slow always or only in certain programs. The same symptom points at completely different causes depending on the conditions around it.

When it started matters just as much. After installing something? After an update? Or with no change at all, one morning? That single sentence often narrows the field more than any test.

Measure what can be measured

Bringing a measured result instead of a description changes the conversation entirely. The computer health check measures processor speed, core count, graphics class and available storage from your browser and shows each one with the score it contributed.

A screenshot of that result settles the “is my computer just old?” argument. It also makes it harder for anyone to sell you an upgrade you do not need.

What each symptom tends to point at

• Long startup, normal afterwards: usually the number of programs launching at boot, or the state of the drive.
• Fine at first, slow after a while, fixed by restarting: a program leaking memory, or heat.
• Freezes in one application only: the problem is that application, not the system.
• Loud and hot: look at cooling and dust before anything else.
• Lines, flicker or colour shifts on screen: display, cable or graphics side.

Narrow it down before you pay anyone

Try to reproduce the fault with a different cable, on a different device, or in a second user account. A problem that appears in only one user account has nothing to do with hardware. A display fault that disappears on an external monitor points at the laptop’s own panel.

What to bring to the conversation

Arrive with: when it started, what you were doing when it appears, a photo of the exact error message if there is one, the steps you already tried and what each one did, and your measurement result. Photograph error messages rather than paraphrasing them — the code is often the single most useful piece of information in the whole exchange.

What to avoid

Do not install “optimiser” or “cleaner” software from search results. Do not give remote access to anyone who phoned you claiming to be technical support; real manufacturers do not call you first.

Frequently asked questions

Is a browser test a real diagnosis?
No. A browser cannot see inside your hardware. It does measure what it can measure honestly, which gives you something concrete to point at instead of an adjective.

I have tried everything and still cannot describe it.
Record a ten second video instead of explaining it. It will save both sides ten minutes.