Comments on: How To Analyze A Windows Blue Screen Of Death With WhoCrashed

By: JJ

JJ — Thu, 10 Dec 2009 21:22:16 +0000

I would agree with bruno, Nirsoft's BlueScreenView is very similar but this has some great value to it if you know what you are doing. Thanks for the post. Blue Screen Error

By: bruno

bruno — Sat, 22 Aug 2009 02:32:00 +0000

Nirsoft has a BlueScreenView, a similar utility without the home use restriction.

By: shocked

shocked — Tue, 28 Jul 2009 13:44:47 +0000

An interesting program though. Thank you.

By: shocked

shocked — Tue, 28 Jul 2009 13:42:58 +0000

RAM memory?
That’s as silly as ATM machine? PIN number? lolz, tut tut.

By: Thor

Thor — Wed, 22 Jul 2009 17:10:28 +0000

I’ve run my own tech support business for years. The most common BSODs I’ve found are driver related. Usually, in the BSOD, there will be a line that refers to a file. I look that up on Google to find out what it is. Then I either install an update, do a roll-back, if there is no update, or remove the driver/device and install a clean copy of the driver.
If the driver was not the initial problem (it got corrupted by something else) the next step is to do further testing and diagnostics to determine what caused the problem in the first place (another driver for something else, a virus, a device, memory, motherboard, etc)

It will be interesting to see if this program helps in any way.

By: Jalley

Jalley — Fri, 17 Jul 2009 09:24:30 +0000

Thank you for bringing this useful app to our collective attention. Using Debugging Tools for Windows alone is often an arduous, time-consuming process. Perhaps this utility will help simplify the detective work.