windows3-10  Exercise 3: Measured, Inferred, Not Checked
=================================================================

Verification: Level 1 (writing exercise based on measured evidence; nothing run).

Prediction (work this out before running the script):

  Before reading the solution: pick one claim you would make about your PC and decide which of the three lists it belongs to.

This is a writing exercise. Worked example for this PC:

Worked example:

  MEASURED (a command ran and returned this)
    - Four unexpected restarts: 2026-07-24 (code 0), 2026-10-19 (0x13A), 2026-10-23 (0), 2026-10-24 (0x13A).
    - Commit 26.7 of 77.8 GB; page file peak 153 MB of 49,152 MB.
    - 0 WHEA events; 0 memory-diagnostic results.
    - 1,402 bad-block, 128 controller-error, 326 paging-error and 1,693 retried-I/O events in the System log.
    - 194 running kernel drivers; feature update to version 26H2 installed 2026-10-08.
  INFERRED (reasoned from the above, not tested)
    - Running out of memory is unlikely to be the cause.
    - No overclock is active (memory at rated speed).
    - The crashes began after the feature update (a correlation).
    - The disk errors come from the external drives (disk numbers are not stable).
  NOT CHECKED
    - The contents of either dump; any memory test; temperatures; the drives' own SMART data and the vendors' diagnostics;
      whether a newer BIOS exists; whether the 26H2 'go back' window is still open; what the two no-code restarts were.

WHY THIS WORKS AS AN ANSWER
---------------------------
  The three lists keep what you know apart from what you suspect. A claim belongs under MEASURED only if you can say
  which command produced it. 'Probably' or 'because' makes it INFERRED. Anything you have not looked at goes under NOT
  CHECKED, and writing that list is the part people skip.
  Common mistakes: putting an inference in the measured list because it feels certain; leaving the not-checked list
  short; and writing the lists once and not updating them as you test.