WhoCrashed Pro
Reviewed June 2009
| What’s It Do?
WhoCrashed, described as a "comprehensible crash dump analysis
tool" identifies which drivers are responsible for crashing a
computer. It does a "post-mortem crashdump analysis" and
presents all gathered information in a comprehensible way
without requiring the user to have any debugging skills. Does it do what it promises? Reviewer 1: Yes, it seems to work fine. It reported a crash on my computer and pointed to my video card drivers as the culprit. It provided a link to the driver and the site if I wanted to update or repair a corrupted driver. The report appeared as follows:
Reviewer 2: No. While it does as it promises regarding analyzing system crashes, it also promises to “download and extract. . . automatically for you” the Windows Debugging Program needed to use Who Crashed, if not already installed. I could find nowhere that this could be accomplished, automatically or otherwise. Reviewer 3: I was unable to verify the claims for WhoCrashed during my months of testing. It runs in the background and is supposed to give a report of the drivers that may have been responsible when an entire system shuts down or reboots spontaneously. Despite numerous program crashes and some system crashes, WhoCrashed never generated a report on either the laptop on which it was installed, or on other computers on my network. Reviewer 4: Yes, it does. It produces a lot of very technical information, most of which would make very little sense to a new computer user. But for someone interested in learning about some of the deep and gritty functions of the Operating System, WhoCrashed will lead to places one might otherwise never explore. Was it easy to install? Reviewer 1: Yes, this was a typical install routine. The free version can be installed on any home machine. The Pro version has the ability to work over a network so one installation should handle any machine on the network and additional installations are not needed. A Desktop icon and Start Menu folder are optional and by default, they are unchecked. WhoCrashed requires installation of Microsoft Windows Debugging Tools© and offers to download and install it on the first run if it is not already installed. Reviewer 2: Yes. Considering that it is a tiny 702kb download that takes less than two seconds on a reasonably fast DSL connection and has no actual GUI (Graphic User Interface), help files, or options. It installs using a standard wizard and takes only a meager 1.9MB of space on one’s hard drive. The EULA (End User License Agreement) may be one of the most liberal that I have ever seen. It allows unrestricted use on as many computers as desired and allows copying and distributing the program; otherwise, there is the standard disclaimer as to liability and warranty. There is no warranty offered of any kind for his product. Reviewer 3: Installation was fast and easy. The license agreement is very simple and allows an unlimited number of installations provided they are all on computers in one’s home. Reviewer 4: Yes, It is a standard Windows installation process that allowed me to place the program and its icons in the locations I chose. As the Pro version is provided from a specific location on the Resplendence web site, it is already registered, so no further registration procedure was needed. Good Points? Reviewer 1: Once installed and run, WhoCrashed is very quick. If there is anything to report in the C:\Windows\Minidump file from the Microsoft tools, it will be reported by WhoCrashed. WhoCrashed displays the dump file information in an easy-to-read format that includes links to the offending files and to the appropriate Web sites for downloading a new driver if that was the problem. Updates for the program are offered on the opening screen. Reviewer 2: I am at a loss to list or identify good points as essentially this program does nothing. As it claims, it will analyze the crash dump on a computer after a crash of BSOD (“Blue Screen of Death”) and attempt to point out the cause such as a faulty driver; however it further states it “cannot always be accurate.” That is all that does. Reviewer 3: WhoCrashed can check the computer it is installed on as well as other computers on one’s network. It ran quietly on my system without noticeable interference with my computer’s performance. Reviewer 4: Once I had everything properly configured, the program worked as described. WhoCrashed uses a set of programs from Microsoft called WinDbg. The first time I did a WhoCrashed analysis, I was given the choice of either searching for WinDbg myself (useful for a true tech who would have it already) or to download and install a version appropriate to my computer's architecture. I chose the download and install option. In a minute or so (on a high-speed connection) the whole procedure was complete, with no need for user intervention. I like the fact that I was given that choice, and I was equally impressed by the seamless way in which the installation was carried out. When WhoCrashed runs an analysis, it displays something such as the following:
Some of this information actually does appear when the infamous "Blue Screen of Death" (the BSOD) strikes. Since the computer has totally stopped, and all functions have been shut down, one cannot even do a "PrintScreen". The only option is to shut it down manually (or pull the plug). Or course, t what little clues one might have had from all the writing that appears on the BSOD is then lost. Prior to having WhoCrashed, on the occasions that I have had this happen, I would painstakingly write down all the Xxes and Ooes in the "Bugcheck code" hoping that it would provide useful information. By being able to recall this information after restarting the computer with WhoCrashed, one can, at the very least, click on some of the hyperlinks in its report. This will lead to places on the Internet where some analysis of the problem is available. Other than the Microsoft site, where some of these codes are described and explained (often very technically), I discovered several very interesting forums where people who really know about these problems offer advice and assistance to those of us who are willing to ask questions. So, even though I am not a technician, I have been able to get some idea where I should look to try to identify the problems that led to the crash. The WinDbg analysis is a text file that has been stored on my computer. It provides a detailed account of everything that was going on at the moment of the crash. I have to confess that it is far too technical for me at present. But I do have a record of what did happen, and if I have a series of similar crashes, I expect that it will help me to resolve the problem. The license offered by Resplendence reads: You may install, copy and run the home edition of the software on as many computer systems as you desire provided these computer systems are located at home. I wish that this would become the minimum standard for all software programs that I purchase. Kudos go to the developers for this licensing model. I also find this policy to be refreshingly honest: We don't promise that the Program will be free of bugs or program errors. If you report a program error or bug to us, we will do our best to correct it. If we issue a maintenance release for the Program which includes a correction for an error you reported, we will assist you in downloading it, or send you a copy of that maintenance release at no charge if you request it. Weak Points? Reviewer 1: The update feature mentioned above downloaded and overwrote my Pro version installation with the Home version and I had to reinstall the Pro version again. Tech support advised that it was a mistake and that one of the links was pointing to the wrong version. They included a link to re-download the program again. The update process launches Internet Explorer rather than my default browser that is Firefox 3.09. This may be due to the fact that it relies on Microsoft’s Minidump tools and may require ActiveX functionality. Per tech support, this is indeed the case. I could not get the “Analyze Remote” function to work on my home network. This was not surprising since my network is a rather clumsy arrangement of Windows XP, Vista & Windows 7 RC. Windows 7 RC does not like to play nice with other versions as far as networking goes. Reviewer 2: Again it is difficult to list specific weak points, as the program itself is weak in its concept and execution. The GUI consists of a crude and unattractive window with a tab to click to start an analysis after which the window will fill with crudely rendered and hard-to-read typography, most of which the user can read from his computer’s logs. I attempted to test its ability to identify the cause of two self-imposed crashes and it failed in both instances. In the first instance I purposely disabled an essential IDE controller and in the second I loosened my video card. In both instances the program stated that it was caused by “a driver which could not be identified.” There are no help files, no documentation on the Web site, the FAQ is unavailable due to its “being updated” which seems to be its permanent condition, and the support is an email/ticket type which offers no turn around time. Finally, as stated above, the promised automatic download and installation if needed of the necessary Windows program seems to be non-existent. And for all of this you can pay $34.95. Reviewer 3: During many months of having WhoCrashed running in the background, and despite having individual programs crash and some severe system slowdowns and crashes, I never received a report from WhoCrashed containing information about what the problem might have been. In part, this may be a tribute to how Windows XP handles crashes compared to earlier operating systems. XP is designed to isolate an issue so that a program can be shut down by the problem while the overall system continues to run. The typical report I received during a WhoCrashed analysis is as follows:
Crash dumps are enabled and no crash dumps have been found in the directory specified. In case your computer does experience sudden reboots it is likely these are caused by malfunctioning hardware or power failure. Then it's suggested you contact the support department of the manufacturer of your system or test your system with a memory test utility for further investigation. Reviewer 4: Through experience, I discovered that there are a few things that need to be configured in order for the program to be able to produce an analysis. Without these preliminary steps, WhoCrashed cannot give any useful information at all. This is the message that I received, after waiting some months for my first "Blue Screen” Crash dumps are not enabled on this computer. This is why there are no crash dumps available. It is suggested you enable crash dumps on your computer. As it also happens, on one of my computers, there was no boot.ini file, which is necessary for enabling the aforementioned "crash dumps". Since these steps must be taken before the program can be useful at all, this information should be provided, either when WhoCrashed is started for the first time, or built into the installation procedure. It is true that the program does explain how to enable crash dumps, but this is information that I completely missed until I had "wasted" a couple of real Blue Screens. I also discovered that in order for an analysis to be available on a remote computer, certain steps need to be taken. First, crash dumps have to be enabled. Second: the folder where the crash dumps will be dumped needs to be shared; otherwise WhoCrashed will not have access to it. Although all this makes sense after running the program for the first time, I only discovered it by trial and (mostly) error. Again, I "wasted" some Blue Screens, before carrying out the now-obvious preliminary steps. Other Comments? Reviewer 1: Responses to my support requests took three days and I consider that somewhat slow. Reviewer 2: There is a story about P.T. Barnum's unloading a batch of unmarketable white salmon by advertising it as "guaranteed not to turn pink in the can." I am quite sure I can promise you that WhoCrashed will not turn pink in the can or for that matter do little else to justify its cost. Reviewer 3: WhoCrashed is designed to help troubleshoot a specific kind of crash, one where a computer suddenly shuts down without a warning. It is not helpful in the more common problems where an individual program crashes, or when there are memory leaks and/or too many programs running and the system bogs down and becomes functionally unresponsive. There is a free download of the home edition available. If one is having the specific type of crash where the computer shuts down without warning and without a message, trying WhoCrashed may be useful in determining the problem if the crash is due to a corrupted driver. Reviewer 4: To make sure that the program is working, one need not wait for a real system crash. To deliberately cause the infamous screen to occur, completely harmlessly, follow instructions at http://pcsupport.about.com/od/tipstricks/ht/makebsodxp.htm . As it involves editing a Registry key, make a backup of the Registry before beginning. Also, the instructions at http://pcsupport.about.com/od/tipstricks/ht/disautorestart.htm are easy to locate, in the same section of the System Properties where one enables crash dumps. Although I do not wish that anyone should have to deal with the Blue Screen, WhoCrashed is a useful item to have in the toolkit. As mentioned above, taking time to follow some of the links provided by a WhoCrashed analysis will lead to a better understanding of how the computer functions. The user having crash problems, and lacking the technical ability to deal with it can use the information provided by WhoCrashed to provide technicians with the information that will help them fix the problem properly. Developer’s Web site: Reviewer 1: The Web site was clean and easy to navigate. Resplendence offers a number of other programs as well as WhoCrashed. Reviewer 2: The site is unattractive, amateurish, and it would seem its purpose is the sale of the developer’s products. Reviewer 3: The information on the developer’s website is sparse. The WhoCrashed FAQ information has been “being updated” over the time I have been testing this program. The most significant support information I found was the disclaimer that: 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. Reviewer 4: I have bookmarked the Resplendence Site as a good place for some interesting technical information, resources and tools. There are several freeware program offered, some of their source code is offered for educational (not commercial) use, and support and links to other places where people will find support is offered both to users of their free products and to paying clients. It is a clean and professional site, with no distracting advertising banners and pop-ups. In fact, you have to look for the commercial section, as most of the site provides information and resource tools. Will you continue to use it? Reviewer 1: Yes, since it requires no resources at all unless executed, it is handy to have to diagnose those rare times I manage to crash my system. Reviewer 2: No. Reviewer 3: No. Reviewer 4: Yes, I certainly will. |
OPERATING SYSTEMS USED IN THIS REVIEW
Windows XP Pro, XP Home, XP Home and Media Center Edition
Back