Build a symptom evidence report Guided Practice

Lab brief

Know the problem and the evidence you need

The situation

A PC is described as “slow and unstable,” but no one has recorded when the behavior occurs or what changed.

Your finished record

A reproducible symptom evidence report

Produce a one-page evidence report that separates observations, timing, recent changes, and the next low-risk test.

Why this matters

A precise symptom record prevents random fixes, gives every later test a baseline, and makes it possible to prove whether a change actually helped.

Safety and setup

Prepare before changing anything

Have this ready

Do not install cleaners, optimizers, drivers, or repair tools during this lab.
Have a text editor or paper available for the evidence report.
Stop and back up important data if the PC clicks, disappears from firmware, or repeatedly reports storage errors.

Field checks

Run the lab

Complete one check at a time. Record the evidence before moving on.

0 of 5 checks complete

Check 1 of 5 Record the symptom without naming a cause Do thisWrite one sentence describing what happens, when it happens, and what remains usable. Record thisA factual statement such as “Windows becomes unresponsive for 20 seconds after sign-in while the pointer still moves.”
Check 2 of 5 Record timing and frequency Do thisNote the first occurrence, recurrence, duration, and conditions that reproduce the symptom. Record thisA timestamped pattern that can be compared after each test.
Check 3 of 5 List recent changes Do thisInclude updates, applications, drivers, peripherals, drops, heat, and power events near the first occurrence. Record thisA short chronological list limited to relevant recent changes.
Check 4 of 5 Capture one baseline Do thisRecord Windows version, free storage, uptime, and idle CPU, memory, and disk readings. Record thisA baseline snapshot taken before changing the system.
Check 5 of 5 Choose one low-risk test Do thisSelect one reversible change and write the expected result before running it. Record thisOne test with a predicted outcome and a clear rollback path.

Interpret results

Match the evidence to the next action

If you seeNext action

The symptom is reproducible

Use the same trigger after each single-variable test so results are comparable.

The symptom is random

Record timestamps and use Event Viewer or reliability history to correlate later.

Storage or hardware warnings appear

Stop software experimentation, protect data, and continue with the drive-health lab.

Decision point

Choose the next action

Continue to the lesson or lab that matches the strongest evidence category: performance, crash, startup, storage, temperature, battery, or repair.

Completion

Confirm the evidence you produced

Finished record: A reproducible symptom evidence report

My problem statement contains an observable symptom.
I recorded timing, frequency, and recent changes.
I selected one reversible next test.

I recorded the evidence and selected a next action.