windows3-8  Exercise 1: Inventory Your Hardware
=================================================================

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

Prediction (work this out before running the script):

  Before running: is your memory likely to be running at its rated speed? Do you expect any WHEA events?

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

  .\hardware_check.ps1

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

  --- Memory modules (rated speed vs the speed in use)
  DIMM 0 | 16 GB | rated 5600 | in use 5600 | Micron Technology CT16G56C46S5.C8D | 1100 mV
  DIMM 0 | 16 GB | rated 5600 | in use 5600 | Micron Technology CT16G56C46S5.C8D | 1100 mV
  --- Firmware
  American Megatrends International, LLC. | version 1.08 | dated 2024-11-05
  System: Micro Computer (HK) Tech Limited EliteMini Series
  --- Disk health as Windows reports it
  0 | KINGSTON OM8PGP41024N-A0 | SSD | health Healthy | OK
  2 | Seagate One Touch Hub | HDD | health Healthy | OK
  1 | WD Elements 2620 | HDD | health Healthy | OK
  --- Hardware-error events
  WHEA-Logger events: 0
  Windows Memory Diagnostic results logged: 0
  disk events: 3549, on 53 different days

WHY THIS WORKS AS AN ANSWER
---------------------------
  Memory: both modules show rated 5600 and in use 5600 at 1100 mV, so on this evidence nothing is overclocked
  (I read Speed as rated and ConfiguredClockSpeed as in use; if the two differ on your PC, a memory profile or
  overclock is active, which is a first thing to switch off when testing stability).
  WHEA-Logger events 0: the hardware has not reported an error of its own. That is some evidence against a
  CPU/memory fault but not proof: it only covers the period the log holds, and faults can occur unreported.
  Windows Memory Diagnostic results 0: it has never been run, so there is NO memory-test evidence either way.
  Common mistakes: reading "no WHEA events" as "RAM is fine"; reading zero memory-diagnostic results as a pass
  (zero results means never run); and treating the module slot names as reliable (both said DIMM 0).