Resplendence  
· Home
· About
· Contact

 News & Updates
·News Feed (RSS)    

 Online Store
· Buy Now

 Customer
· Customer Login
· Customer Support
· Registry Support

 Download
· Free downloads
· Registered customers

 Windows Registry
· Registrar Registry
   Manager

· Registrar Command
   Line Edition

· Registry Support Site

 System Monitoring
· MultiMon
· ObjMon
· Textractor

 Crash Analysis
· WhoCrashed

 Security Tools
· SanityCheck
· AntiFreeze

 Source Code
· Driver source code

 Consultancy
· Driver Development

 Newsletter
If you would like to receive a message now and then about product releases, upgrades and discounts,  then please enter your email address to subscribe to our newsletter. 

  

 · Introduction
 · Supported OS
 · Pro Edition
 · What's new
 · FAQ
 · Download
 · Buy Pro Edition

WhoCrashed Introduction

WhoCrashed reveals the drivers responsible for crashing your computer
New: version 2.10 released

Whenever a computer running Windows suddenly reboots without displaying any notice or blue screen of death, the first thing that is often though about is a hardware failure. In reality, most crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, most computers running Windows do not show a blue screen unless they are configured to do so. Instead these systems suddenly reboot without any notice.

WhoCrashed shows the drivers which have been crashing your computer with a single click. In most cases it can pinpoint the offending drivers which 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.

Normally, debugging skills and a set of debugging tools are required to do post-mortem crash dump analysis. By using this utility you do not need any debugging skills to be able to find out what drivers are causing trouble to your computer.

Note

Note that WhoCrashed cannot be always 100% sure about the drivers which are responsible for crashing your computer. Because all kernel modules run in the same address space, a kernel module is able to corrupt another. Also, a driver may be able to cause problems to another driver which runs in the same device stack. So keep in mind this software is not guaranteed to identify the culprit in every case but most often it does.

WhoCrashed relies on the Windows Debugging Package (WinDbg) from Microsoft. If this is not installed, WhoCrashed will download and extract this package automatically for you.


Screen shot







Copyright © 1997-2010 Resplendence Software Projects Sp. All rights reserved. Privacy Policy.
Page generated on 3/16/2010 7:14:45 PM. Last updated on 12/15/2008 5:58:04 PM.