WTFIsStalling 0.5.1

What's new

Stalls are tied to hardware errors. When a stall, or a moment you flagged with "I felt it", happens within 2 seconds of a hardware error Windows logged (WHEA: memory, processor, PCI Express), the report says so in that hardware finding. Stalls where "the CPU went dark" get the explanation that goes with it: the firmware was busy handling that error.

Crashes and sudden power loss. Unexpected shutdowns from the last 7 days are reported: blue screens with their stop code and name (for example 0x9F DRIVER_POWER_STATE_FAILURE), and separately restarts or power loss with no blue screen, which point at the power supply, heat or an unstable overclock. Someone simply holding the power button is not counted as a crash.

Firmware speed caps. Windows' "firmware limited the processor's speed" event now backs up a CPU throttling finding. It only counts by itself when it fired during the run, because some PCs log it at every boot.

The details section lists the count for every kind of event-log entry checked, so a clean log is visible too.

Also: SHA256SUMS.txt now works with sha256sum -c on Linux, macOS and Git Bash.

Please report odd output

These event-log paths could only be tested against constructed events, because the development PC has none of them. If a report misses something you can see in Event Viewer, please open an issue with the report file.

Verifying this download

gh attestation verify WTFIsStalling.exe --repo Tyberious/WTFIsStalling proves the file was built by this repository's release workflow from the tagged commit. The executables are not code-signed yet, so SmartScreen may warn: More info -> Run anyway. If an antivirus blocks the download, please open an issue with the detection name.

Download

WTFIsStalling.exe is the app. wtfis-cli.exe is the same engine for the console.