BlueScreenView Determines Which Driver Caused Blue Screen on Windows

Posted By Raymond In Category: Computer

Aug
9
2009
Donate

Earlier this year I found a tool called WhoCrashed which is sometimes useful in finding out what is the cause of a blue screen crash. A lot of times a blue screen happens very quickly which you can’t even see what are the error messages and your computer got restarted. The annoying part of using WhoCrashed is you need to have Microsoft Debugging Tools installed or else it cannot analyze the mdmp files.

windows blue screen crash

Nir Sofer, a very experienced developer that released many useful utilities for Windows has came up with a new tool called BlueScreenView. Basically it is a new utility that allows you to watch the details of all ‘Blue Screen of Death’ crashes that occurred in your system.


BlueScreenView scans all your minidump files created during ‘blue screen of death’ crashes, and displays the information about all crashes in one table. For each crash, BlueScreenView displays the minidump filename, the date/time of the crash, the basic crash information displayed in the blue screen (Bug Check Code and 4 parameters), and the details of the driver or module that possibly caused the crash (filename, product name, file description, and file version).

blue screen viewer

For each crash displayed in the upper pane, you can view the details of the device drivers loaded during the crash in the lower pane. BlueScreenView also mark the drivers that their addresses found in the crash stack, so you can easily locate the suspected drivers that possibly caused the crash. For the fun of it, you can even view a demo of the crash by going to Options > Lower Pane Mode > and select Blue Screen in XP Style.

What I like about BlueScreenView is it doesn’t require any installation and the executable can run straight from a USB flash drive. Oh and you don’t even need Microsoft Debugging Tools installed to use this tool. From my experience, most of blue screen crashes are either caused by bad/conflicting drivers or a faulty hardware. An example is some software such as keylogger requires installing badly coded drivers and it can cause blue screen. If you have a bad RAM, you can also get blue screen and random lock ups.

BlueScreenView works with Windows XP, Windows Server 2003, Windows Server 2008, Windows Vista, and Windows 7, as long as Windows is configured to save minidump files during BSOD crashes. Currently, BlueScreenView can only read minidump files of 32-bit systems, but it cannot read the dump files created by x64 systems. It’s possible that x64 support will be added in future versions.

[ Download BlueScreenView ]


Related posts:
  • Blue Screen of Death (BSOD)
  • Move Windows XP Hard Drive or Change Motherboard Without Getting Blue Screen of Death
  • Analyzing Windows Crash Dump or Minidump with WhoCrashed
  • Fix Windows is Starting Slow Logon Caused by wlnotify.dll
  • Fix Firefox 3 Crashing Problem Caused By Kaspersky 2009 Products
    • Antonio

      Thanks ray! This is a very useful tool for me because my girlfriend’s comp keeps getting the blue screen… Will use and attempt to fix the problem THANKS again!

    • manoj

      Thanks Ray!

      that would be very useful as i m geting blue screens often..

      Nice post.

    • light

      thx for sharing this ….it save me alot of work…

    • Gatau

      Owh this tool seems usefull than whocrased.
      Whocrased only show error caused by driver.
      Thank Raymond for your info.

    • Ali

      Thanks Ray….

    • webcadre

      another usefull tips and tool from the great master himself, thanks ray! :)

    • Ajay

      Thanx Raymond.

    • Ed

      Almost all my tools comes from:

      Sysinternals
      Nirsofer
      and I read Raymond’s blog for using other individual tools.

      Anyone knows of more places like these?

    • x

      thanks a lot Ray. ur website has been really helpful

    • ByteCode

      very nice tool

      thanks alot

    • Mahmoud Musatafa

      thanks Raymond .. I was fuffering of blue screen .. and now it’s time to know the reason …

    • flashkidz

      Thanks for sharing this tool sir ray, this very use specially on winxp users like me that sometimes getting errors, BSOD & Hang-up, but when i look the reason what went wrong microsoft popup explorer error notice said “unknown”… >_<

    • Ziad

      Thanks Raymond. I was checking for such a program lately!! Best wishs :)

    • Oneide

      Thanks, man! Almost sure will need this.

    • Merlin_Magii

      Another very useful tool in the armoury – thank you Raymond.

      Have you got a similar tool for analysing who the culprit is when the PC freezes for several minutes at a time?

    • MR7

      Great tool. I wonder if there is one that can do the same without booting Windows. It would be awesome for a PC that crashs before to load Windows…

    • yangming

      wow i have 31 crashes. time for a new pc! thanks for sharing this ray! :D

    • ete

      Does this program work if Windows is not bootable? If not, then someone should make it part of a liveCD in order for this utility to be truly useful.

    • Ashish Sharma

      This Is the best Post and utility i ever found…
      thanx for information and tool

    • Michael Capella

      I have no idea what to do after BSV identifies the causes of the crash.

      My problems are:
      ntoskrnl.exe
      SYMEVENT64x86.SYS
      ataport.SYS
      PSHED.dll
      netbt.sys

      What do I do now that I know what the problems are?

    • Joshua Richards

      Hey, as of v 1.05 they support x64, they are in v 1.11 now (9/28/2009)

    • PaulieWalnuts

      Linked in vistax64 forum! It’s insane, the number of BSOD we get! Thanks for the information about this program.

    • Fuck

      Cant understant anything about this page because, i cant read this kind of finnis language?????? Why cant i see this from english, this is idiotism!

    • shane

      very usefull tool.

    • http://6bestregistryceaner.com/ james

      Great post Ray! I also have the same problem but I already fixed it using registry cleaner.

    Copyright © 2005-2012 - Raymond.CC Blog