windows3-10  Exercise 1: Your Own Case File
=================================================================

Verification: Level 1 (run on the author's machine, read-only, no administrator rights).

Prediction (work this out before running the script):

  Before running: what is the first thing you expect to find odd in your own case file?

Command (case_file.ps1 saved in the current folder):

  .\case_file.ps1

Output (real, from the author's machine on 2026-10-24; your numbers will differ):

  1. Machine : Micro Computer (HK) Tech Limited EliteMini Series, 29.8 GB usable RAM, Windows build 10.0.26300
  2. Memory  : commit 26.7 of 77.8 GB; page file peak 153 MB of 49152 MB
  3. Restarts: 4 unexpected since the log began
       2026-07-24 21:33  stop code 0x0
       2026-10-19 15:38  stop code 0x13A
       2026-10-23 19:10  stop code 0x0
       2026-10-24 17:02  stop code 0x13A
  4. Dumps   : 2 in C:\Windows\Minidump (listing works; reading needs administrator)
  5. Hardware: WHEA errors 0; memory test results 0
  6. Storage : 3549 disk events (1402 bad block, 128 controller error, 326 paging error, 1693 retried I/O)
  7. Drivers : 194 running kernel drivers
  8. Changes : last feature update "Windows 11, version 26H2" on 2026-10-08

WHY THIS WORKS AS AN ANSWER
---------------------------
  A usable case file has the eight lines above, then a timeline (chapter 9's change_timeline.ps1) and one sentence on
  what has not been checked. For this PC: "Not checked: the contents of either dump, any memory test, temperatures,
  the external drives' own SMART data; no experiment has been done."
  Common mistakes: filling the case file with interpretations rather than measurements; leaving out the "not
  checked" sentence; and forgetting the date the file was made (the numbers change).