Skip to content

CrashSleuth 0.5.0

Choose a tag to compare

@Moorey79 Moorey79 released this 04 Nov 09:35
· 7 commits to main since this release

CrashSleuth 0.5.0: early warnings and a proper investigation

CrashSleuth now remembers what changed on the PC, warns before things fall over, and shows its reasoning.

Early warnings (background monitor)

  • Three levels. Watch (shown in the report only), Warning (tray turns amber) and Critical (tray turns red and a notification pops up).
  • No false alarms from a single spike. A level only counts once it has lasted: Watch needs 3 of the last 6 samples, Warning 6 of the last 12, Critical 3 in a row. Real emergencies (commit charge at 95% or more) count straight away.
  • Every warning explains itself. It says what was measured, what it projects (for example "runs out of memory in about 6 hours"), and how confident that projection is.
  • What's watched:
    • memory commit charge
    • kernel pool growth (short and long trends must agree)
    • per-program handles and GDI/USER objects
    • disk response times (25 ms warning, 50 ms critical, sustained)
  • New events caught as they happen: drive resets (event 129), disks disappearing (event 157), and hardware errors (WHEA) named by component and PCIe slot.

Investigation (in every report)

  • Health by area, with no overall score. Eight areas: memory and resources, kernel and drivers, storage, graphics, hardware, Windows integrity, security and persistence, and devices and connectivity.
  • Eight explanations, tested every scan. Each is scored against the evidence:
    • a program leaking resources
    • a driver leaking kernel memory
    • running out of commit
    • a device reset storm
    • unstable hardware or PCIe
    • a failing drive
    • graphics instability
    • tampering or evidence suppression
  • Clear scoring. Every point of the score is a line of evidence. "Looked, not found" and "couldn't check" are listed separately, so a low score from missing data isn't mistaken for a clean bill of health.
  • Labelled statements. Everything in the report is marked as a fact (measured), an inference (worked out) or a hypothesis (being tested).

History and timeline

  • Change history. CrashSleuth keeps a history database of drivers, programs, services, tasks, startup entries, Defender exclusions, BIOS and Windows updates, and records what changed and when.
  • Honest timestamps. Each change's time keeps its source and how far to trust it, e.g. "install record", "day only", "first noticed between ...", or "can be faked" for scheduled tasks.
  • One timeline. The timeline now merges crashes, warnings, threats and changes. Changes in the week before a problem started are listed as leads.

Fixes

  • Checked afterwards. Every fix is re-checked once it's applied (is the task really gone, the service really disabled?) and the result is saved with its undo record.
  • Permanent changes say so. Fixes that can't be undone say so in their description.
  • Read-only mode for AI assistants (new default). Claude and other AI assistants can scan and read reports but can't apply or undo fixes unless you tick "Let AI assistants apply and undo fixes" in the Fixes tab or in the installer.

Installer

  • Optional Claude connection. A new tick box connects CrashSleuth to the Claude desktop app (off by default).
  • Optional AI fixes. Another tick box lets AI assistants apply fixes (off by default).

Download

CrashSleuth-Setup-0.5.0.exe. SHA-256: EC0735B868C5323A41314CDFBDA4D2B88D84182C6DE31D4C4C9C0776B92EB211

The installer isn't code-signed yet, so Windows may show 'Windows protected your PC': click More info, then Run anyway. Upgrading from 0.4 keeps your settings and the background monitor.