Repository navigation
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.