Resplendence.WhoCrashedComprehensible crash dump analysis, find out why your system crashed.
$ winget install --id Resplendence.WhoCrashed --exact --version 7.10Run in Command Prompt, PowerShell, or Windows Terminal. Prompts for any agreements.
For Intune admins
Automated application patching for Microsoft Intune. Pckgr keeps a curated library of 1,000+ apps continuously up-to-date in your tenant via Microsoft Graph — no manual repackaging, no chasing vendor sites.
See Pckgr's app library### WhoCrashed reveals the drivers responsible for crashing your computer
Whenever a computer running Windows suddenly reboots without displaying any
notice or blue or black screen of death, the first thing that is often thought
about is a hardware failure. In reality, crashes are often caused by
malfunctioning device drivers and kernel modules. In case of a kernel error,
computers running Windows do not show a blue or black screen unless they are
configured to do so. Instead these systems suddenly reboot without any notice.
WhoCrashed shows the drivers that have been crashing your computer with a single
click. In most cases it can pinpoint the offending drivers that have been
causing misery on your computer system in the past. It does post-mortem
crashdump analysis and presents all gathered information in a comprehensible
way. In case your system has been crashing because of a hardware failure,
WhoCrashed will provide you with guidance to trace the root cause of the
problem.
Normally, debugging skills and a set of debugging tools are required to do
post-mortem crash dump analysis. Using WhoCrashed you do not need any debugging
skills to be able to find out what drivers are causing trouble to your computer.
| Architecture | Type | Scope | Install | Download |
|---|---|---|---|---|
| neutral | inno | machine | Direct |
Copy a command tailored to that specific architecture, type, and scope - useful when winget would otherwise pick a different default.