Repository navigation
Releases
CrashSleuth 0.9.14
Test version. Install over the top of any earlier version: your history, settings and updates are kept.
New since 0.9.5
Dump detective work & stack analysis
- Automatically runs deeper WinDbg checks when Windows blames itself (
ntoskrnl.exe), inspecting memory pools (!pool), CPU core states during freezes (!running -it), hung power requests (!irp), and raw stack scans (dps @rsp) to trace third-party drivers. - Displays up to 12 call stack entries for recent crashes with non-Microsoft drivers explicitly flagged (
<- not Microsoft's) to highlight real culprits.
Safety, updates, and broader diagnostics
- Preserves up to two full recent memory dumps safely while monitoring minidump configuration.
- Features a self-updater that checks daily, downloads incremental patches, restarts the tray icon, and rolls back if issues occur.
- Expands coverage to include program crash dumps, Windows file repairs, driver latency, Windows Update issues, startup timing, Wi-Fi dropouts, browser extensions, drive health, and Defender checks.
Sending a report & verification
- Click Show the copy to share (or find the -shareable file in Documents > CrashSleuth Reports) and send it to reports@directcompare.dev (usernames, machine names, and network details are scrubbed).
- Because the installer is unsigned, verify its integrity by matching its SHA-256 hash in PowerShell:
Get-FileHash .\CrashSleuth-Setup-0.9.14.exe
- SHA-256 checksums (also in
CrashSleuth-Setup-0.9.14.sha256.txt):CrashSleuth-Setup-0.9.14.exe:894ed4da3d9e316d1c1bb2973c6f3616d3f2368b323f45b1f60dd196bf9e00e3CrashSleuth.exe:830c7c4854b36345c434c281dd4410ffd4e2d115cfb3b98aa29f0f5fddb6a9e3CrashSleuthMcp.exe:b1ad31d056973180dbb3d24ccc0ac7a290a640b4b12b65e8b1f5a509a15b01f3
CrashSleuth 0.9.5
Test version. Install over the top of any earlier version: your history and settings are kept.
New since 0.9.4
Network watch: who's calling home
- The background monitor now notes which programs connect to the internet: where to, when and how much. It never sees what they send or receive.
- Programs that are signed and installed where only installers can write (Windows, Program Files, Microsoft Store apps) are trusted and left out completely, so your browser and Windows' own traffic aren't recorded.
- Everything else is judged on what it actually does, which is how adware and malware give themselves away:
- contacting the same server on a timer, especially when it never gets through
- trying lots of addresses that don't answer, or connecting on unusual ports
- looking up made-up web names, or the same dead one over and over
- sending a lot of data out and getting little back
- being online when a Windows event log was wiped
- It also takes into account who the program is (unsigned, running from AppData or a temporary folder, or a Windows tool like PowerShell that runs whatever it's told), and whether Defender has caught something in its folder in the last 30 days.
- Suspicious programs raise an alert and get their own section in the scan report, with the reasons and where they went. Programs worth keeping an eye on are listed separately.
- Nothing is blocked in this version. It only watches and reports. Blocking comes later, once we've seen what normal looks like on real PCs, so please send a report after a day or two so we can check for false alarms.
- What it records is kept for 24 hours in a folder only administrators can read, and survives restarts and updates.
Privacy
- The copy of the report to share now also hides the web addresses programs used, and IPv6 addresses as well as the usual IPv4 ones.
- The privacy statement explains what the network watch records and where.
Smaller fixes
- A disk that's unplugged while the monitor is watching it is quietly dropped instead of being logged as an error.
- CrashSleuth's own health line no longer counts harmless "needs admin rights" hiccups from non-admin runs as failures.
Sending a report
After a scan, email the copy ending in -shareable from Documents > CrashSleuth Reports to reports@directcompare.dev. It has your names, the PC's name, email, network and web addresses and screenshots taken out.
Checking the download
The installer isn't code-signed yet, so Windows may warn about it. To check you have the real file, compare its SHA-256 checksum with the one in CrashSleuth-Setup-0.9.5.sha256.txt below. In PowerShell:
Get-FileHash .\CrashSleuth-Setup-0.9.5.exe
The installer's SHA-256 is cc07e84886ff0f971acd994677048bc6170e802765e5b4794b4470967b86cd93.
CrashSleuth 0.9.4
Test version. Install over the top of any earlier version: your history and settings are kept.
New since 0.9.1
Temperatures and power (no extra driver)
- The background monitor now records, every 5 minutes, what Windows can read on its own: the hottest temperature sensor, how fast the processor is running against its normal top speed, each drive's own temperature, and whether the PC is on the charger or battery (and how charged).
- A sensor that never changes is recognised as a board or placeholder value, not the processor, and is never treated as a temperature to worry about.
- Alerts when a real sensor reaches 90°C or a drive reaches 60°C.
- The scan picks up Windows' own "shut down because it was too hot" records and the processor being held back by the BIOS.
- New explanation tested on every scan: the PC is overheating. For sudden power-offs, CrashSleuth now looks at the last reading before each one: hot just before it points at heat; cool and on a low battery points at the battery or charger.
- Vital signs dashboard: new Temperatures and Processor speed charts. Clicking an event shows the temperature, speed and power source at that moment.
Safer automatic fixing
- CrashSleuth only removes something by itself when Microsoft Defender has flagged it too. Its own adware list alone is never enough.
- Rules updates are refused if they would target well-known programs, match almost anything, or add a suspicious number of entries at once, even when properly signed.
- A program you use won't be removed by itself just because a flagged file turned up inside its folder later (someone could plant one to frame it). It's still offered on the Fixes tab, with the reason it wasn't automatic.
- The automatic run never changes Defender's own settings. Turning on Defender's blocking of unwanted programs is now its own fix, for you to apply.
- Undo won't put files back through a folder that has since been swapped for a link to somewhere else.
Easier to share, easier to trust
- Every scan now saves a copy of the report ready to share, ending in "-shareable", with your user names, PC name, email and network addresses and screenshots taken out. "Show the copy to share" opens the folder with it selected. Please send that one to reports@directcompare.dev.
- The memory test fix now explains exactly what you'll see at the next restart (a blue test screen, not a crash), how long it takes, and how to cancel it.
- The Claude connection treats everything it reads from the PC as data, never instructions, and only applies fixes the last scan actually offered.
- If a future Windows stops reporting kernel memory by tag, the dashboard explains the empty chart instead of leaving it blank.
Checking the download
The installer isn't code-signed yet, so Windows may warn about it. To check you have the real file, compare its SHA-256 checksum with the one in CrashSleuth-Setup-0.9.4.sha256.txt below. In PowerShell:
Get-FileHash .\CrashSleuth-Setup-0.9.4.exe
The installer's SHA-256 is 123e74b74545fb547aedaea92d23c8d918748c0499852e3f60cfeaccb3f933a0.
CrashSleuth 0.9.1
Test version. Superseded by a newer release: get the latest from the Releases page.
New since 0.8.0
Security
- The background service now keeps its files in a folder only it and administrators can change, so nothing running as a normal user can tamper with what it records or use it to gain admin rights.
- Fixes and undos always need you to click Yes in Windows' admin prompt.
- Automatic fixing is off unless you turn it on: by default CrashSleuth tells you what it would remove and removes nothing.
- Programs CrashSleuth removes are scrambled in its undo store, so they can't run there or set off your antivirus. Undo restores them exactly.
Better answers
- New explanation tested on every scan: the power is cutting out (a worn battery, charger or power supply).
- Monitor history is read over 3 days, so a laptop that's mostly off doesn't look like it has no history. Areas with too little data say "Unknown" instead of "Healthy".
- Leak warnings that went quiet now say why, rather than disappearing.
- Every fix CrashSleuth won't do by itself says why not.
- Drive trouble is dated from the Windows drive's own errors, not a USB stick's.
- A program crashing several processes at once counts as one crash. Defender and Windows components get repair advice instead of "reinstall".
- Antivirus that doesn't register with Windows Security (such as TotalAV) is now recognised.
Sharing
- "Save a copy to share" makes a version of the report with your user names, PC name, email and network addresses and screenshots taken out.
CrashSleuth 0.8.0
CrashSleuth 0.8.0: it works problems out, and fixes the cause
Since 0.5.0, CrashSleuth has picked up a live dashboard, and it now fixes things on its own. When it finds a problem it follows it back to where it came from and fixes that, so the problem doesn't keep coming back.
Fixes the cause, not the symptom
- Traces problems to their source. When CrashSleuth finds adware, a junk startup entry or a task that keeps reappearing, it follows the trail back through what Windows recorded about it: which program created it, which download it came from, and what was installed at the same time. It stops when the trail ends, and fixes it there.
- If something comes back, it finds out why. Removing the same thing again achieves nothing. On a comeback it searches wider, locks the folders it came back into so it can't reinstall there, and switches on Windows' own audit logging so the next attempt names the culprit.
- Programs you chose are left alone. If the trail leads to a program you installed and use, CrashSleuth doesn't remove it. It blocks the junk that program brings in instead.
- Safe experiments. For problems with no single obvious cause (devices dropping out, for example), CrashSleuth can try one change at a time, such as turning off PCI Express power saving. It compares the following days with the 30 days before, then keeps the change or undoes it.
- Works unattended. Safe, undoable fixes run on their own: 15 minutes after start-up, then daily, and shortly after Windows Security catches something. Every fix is checked afterwards and can be undone from the Undo tab. You can switch this off in the Fixes tab.
- Built-in safety rails. It never blames Windows or Microsoft programs just because of when something happened, and it stops at the installer rather than chasing further. Removing a whole folder needs hard proof and your OK.
Better crash answers
- Leak or cache? Windows uses spare memory to remember files you've opened, and that used to look like a memory leak. The tray app now notices when you're away from the PC: memory that keeps growing while nobody's using it is a real leak, while growth that only happens when you're busy is harmless caching. If it is a leak, CrashSleuth names the program busiest at the time.
- CRITICAL_PROCESS_DIED explained. These blue screens name a Windows process but not why it died. CrashSleuth now looks for the background service that crashed just before each one, names it, and says whether it belongs to Windows or another program, with the right advice for each. The monitor also warns you whenever a background service crashes.
- Honest wording. A crash cause measured after the crashes happened is worded as a possibility, not a fact. The onset date is the first crash on record. If event logs were cleared, the report says so even after you've marked it as reviewed.
- New report section, "Traced to the source": what each problem was traced back to, what was done about the cause, and any experiments still running.
Vital signs dashboard (new since 0.5.0)
- A live dashboard of everything the background monitor records: how long the PC ran before each blue screen compared with now, memory, kernel memory, handles, window objects, disk response times and recent events, with 6-hour to 7-day views.
- Open it from the tray icon (double-click), the Vital signs button, or the "CrashSleuth Vital Signs" shortcut. It refreshes itself every 5 minutes, and it tells you if the figures on screen are out of date.
- Fixed: counts of window objects (the ones that make dialogs go blank when a program runs out) were always recorded as 0 since 0.3.1. The tray now measures them properly.
Smaller fixes
- Early warnings the monitor has since withdrawn no longer keep the tray red.
- Windows' own scheduled tasks (tips, notifications) are no longer reported as new tasks.
- Microsoft's self-updating apps (Edge, Copilot) aren't listed as suspects just because they updated near a problem.
- Change history no longer records false changes when CrashSleuth is started from inside a Store app.
Download
CrashSleuth-Setup-0.8.0.exe. SHA-256: A184344B8FBB2C4AACD0EA772BA1EC2A9B41B0F9A7CCB28ABBFF1CCA057981AD
The installer isn't code-signed yet, so Windows may show "Windows protected your PC": click More info, then Run anyway. Upgrading keeps your settings, history and the background monitor.
CrashSleuth 0.5.0
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.
CrashSleuth 0.4.0 (test version)
CrashSleuth v0.4.0 (test release)
CrashSleuth finds out why a Windows PC crashes, freezes or throws error pop-ups, explains it in plain English, and fixes what it safely can, with an undo button. Windows 10/11, 64-bit.
⚠️ Not code-signed yet. If Windows shows "Windows protected your PC", click More info, then Run anyway.
What it checks
- Crash history: blue screens, unexpected restarts (power button, sleep or no warning), hardware (WHEA) errors, graphics driver resets, and programs that keep crashing or hanging.
- Crash dumps: names the driver behind each blue screen using Microsoft's debugger (downloaded on first use). Without it or without internet, it reads the dumps itself for the stop code, uptime and the drivers on the crash stack.
- Windows Error Reporting archive: recovers crashes even if the event logs were cleared, plus non-fatal "live" kernel errors (USB, graphics, Wi-Fi resets), naming the device involved.
- Malware-style persistence: scheduled tasks, Run keys, services and Startup folders: encoded or downloading scripts, unsigned programs hiding in user folders, tasks that wipe event logs.
- Microsoft Defender: risky exclusions, real-time or tamper protection switched off, old definitions, threats that keep coming back.
- Drivers and hardware: known crash-prone and known vulnerable drivers, devices in error, network filter drivers, Intel 13th/14th gen microcode, BIOS age, RAM setup, drive health and space.
- Software: registry cleaners, driver updaters, "optimisers", game boosters, adware and cracked-software markers.
- Leaks: programs steadily eating memory, handles or GDI/USER objects.
Fixing
Fixes are offered, never automatic. Tick what you want; CrashSleuth makes a System Restore point first, and every fix can be undone from the Undo history tab. It never deletes your files, never clears Windows' logs or crash dumps, doesn't "clean the registry" and doesn't install drivers.
Background monitor (optional)
A Windows service samples the system every 5 minutes, watches the event logs and flags trouble with a coloured dot by the clock, so crashes that happen while you're away still get caught. Scans and fixes started from the tray run without an admin prompt: the service starts them as the logged-on user with that user's own admin rights, through a local named pipe only that user can use.
Privacy
Nothing is sent anywhere automatically. CrashSleuth downloads Microsoft's debugger and symbol files when needed, and small signed updates to its known-issues list from crashsleuth-rules.
Testers: please send your report
Email the newest report from Documents > CrashSleuth Reports to reports@directcompare.dev. If you found out what was really wrong with the PC, say so: "CrashSleuth said X, it was really Y" is the most useful feedback there is. Please don't post reports as GitHub issues; they're public and list the PC's name and installed programs.
Verify your download
Get-FileHash .\CrashSleuth-Setup-0.4.0.exe -Algorithm SHA256It should print D1744082CD2BAB33AFF6D638398D554A2CB961E39972FF4EE42A2BB15EB8D21C.