Advertisement

CHANGELOG

What's New in version 3.01:

  • In rare cases, WhoCrashed failed to properly detect the current crash dump directory resulting in no crash dumps found. This has been fixed.
  • On systems with more than 4GB RAM installed, WhoCrashed failed to properly report the amount of installed RAM and available virtual memory. This has been fixed.

What's New in version 3.00:

No longer requires download and installation of WinDbg package unless running on Windows XP or older
WhoCrashed no longer needs to download and install the WinDbg debugger package from Microsoft. Only if you are still running Windows XP or Windows 2000 this is still required. For all later operating system versions (Windows Vista, Windows 7, etc) it will run without requiring you to download and install additional software packages. This saves installation time.

More detailed analysis reports
Analysis reports now displays additional information including amount of up time, operating system versions and system information such as number of active processors at the time of the crash. Conclusions will now also include the likely nature of a problem (faulty hardware, a thermal issue, typical software problem, typical case of memory corruption, etc.)

Documentation assisting you in troubleshooting
WhoCrashed now comes with better documentation. Depending on any particular situation, it will assist you in undertaking steps to troubleshoot existing problems right from the conclusion section in the analysis report

Support and information on obscure and rare bug checks
WhoCrashed now recognize less common, obscure, proprietary and rare bug checks.

Crash dump overview (all versions)
The new version of WhoCrahsed offers a handy overview which gives quick insight on all system crashes that took place on a particular machine.

What's New in version 2.10:

  • Bug fixed: crash dump dates could get misreported