Readme
Readme
32
Copyright (c) 2009 - 2011 Nir Sofer
Web site: http://www.nirsoft.net
Description
===========
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).
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.
Versions History
================
* Version 1.32:
o Added 'Mark Odd/Even Rows' option, under the View menu. When it's
turned on, the odd and even rows are displayed in different color, to
make it easier to read a single line.
* Version 1.31:
o Added 'Google Search - Bug Check+Driver' for searching in Google
the driver name and bug check code of the selected blue screen.
* Version 1.30:
o Added 'Dump File Size' column.
* Version 1.29:
o You can now send the list of blue screen crashes to stdout by
specifying an empty filename ("") in the command-line of all save
parameters.
For example: bluescreenview.exe /stab "" > c:\temp\blue_screens.txt
* Version 1.28:
o Added 'Add Header Line To CSV/Tab-Delimited File' option. When
this option is turned on, the column names are added as the first
line when you export to csv or tab-delimited file.
* Version 1.27:
o Fixed issue: removed the wrong encoding from the xml string,
which caused problems to some xml viewers.
* Version 1.26:
o Fixed 'DumpChk' mode to work properly when DumpChk processing
takes more than a few seconds.
* Version 1.25:
o Added 'DumpChk' mode, which displays the output of Microsoft
DumpChk utility (DumpChk.exe). You can set the right path and
parameters of DumpChk in 'Advanced Options' window. By default,
BlueScreenView tries to run DumpChk from '%programfiles%\Debugging
Tools for Windows'
o The default MiniDump folder is now taken from
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl
* Version 1.20:
o Added 3 new columns in the upper pane: Processors Count, Major
Version, Minor Version.
o Added 'Explorer Copy' option, which allows you to copy dump files
to the clipboard and then paste them into Explorer window.
* Version 1.15:
o Added option to view the blue screen list of multiple computers
on your network. The computer names are specified in a simple text
file. (See below).
o Added Combo-Box to easily choose the MiniDump folders available
in the hard-disks currently attached to your computer.
o Added 'Computer Name' and 'Full Path' columns.
* Version 1.11:
o Added /sort command-line option.
* Version 1.10:
o Added accelerator keys for allowing you to toggle between modes
more easily.
o Added command-line options for saving the crash dumps list to
text/csv/html/xml file.
o Added command-line option for opening BlueScreenView with the
desired MiniDump folder.
o Fixed focus problems when opening the 'Advanced Options' window.
o Added 'default' button to the 'Advanced Options' window.
o Added 'processor' column - 32-bit or x64.
* Version 1.05 - Added support for x64 MiniDump files.
* Version 1.00 - First release.
BlueScreenView Features
=======================
System Requirements
===================
Using BlueScreenView
====================
BlueScreenView doesn't require any installation process or additional dll
files. In order to start using it, simply run the executable file -
BlueScreenView.exe
After running BlueScreenView, it automatically scans your MiniDump folder
and display all crash details in the upper pane.
* Dump File: The MiniDump filename that stores the crash data.
* Crash Time: The created time of the MiniDump filename, which also
matches to the date/time that the crash occurred.
* Bug Check String: The crash error string. This error string is
determined according to the Bug Check Code, and it's also displayed in
the blue screen window of Windows.
* Bug Check Code: The bug check code, as displayed in the blue screen
window.
* Parameter 1/2/3/4: The 4 crash parameters that are also displayed in
the blue screen of death.
* Caused By Driver: The driver that probably caused this crash.
BlueScreenView tries to locate the right driver or module that caused
the blue screen by looking inside the crash stack. However, be aware
that the driver detection mechanism is not 100% accurate, and you
should also look in the lower pane, that display all drivers/modules
found in the stack. These drivers/modules are marked in pink color.
* Caused By Address: Similar to 'Caused By Driver' column, but also
display the relative address of the crash.
* File Description: The file description of the driver that probably
caused this crash. This information is loaded from the version resource
of the driver.
* Product Name: The product name of the driver that probably caused
this crash. This information is loaded from the version resource of the
driver.
* Company: The company name of the driver that probably caused this
crash. This information is loaded from the version resource of the
driver.
* File Version: The file version of the driver that probably caused
this crash. This information is loaded from the version resource of the
driver.
Command-Line Options
====================
/LoadFrom <Source>
Specifies the source to load from.
1 -> Load from a single MiniDump folder (/MiniDumpFolder parameter)
2 -> Load from all computers specified in the computer list file.
(/ComputersFile parameter)
/MiniDumpFolder <Folder>
Start BlueScreenView with the specified MiniDump folder.
/ComputersFile <Filename>
Specifies the computers list filename. (When LoadFrom = 2)
/LowerPaneMode <1 - 3>
Start BlueScreenView with the specified mode. 1 = All Drivers, 2 = Only
Drivers Found In Stack, 3 = Blue Screen in XP Style.
/stext <Filename>
Save the list of blue screen crashes into a regular text file.
/stab <Filename>
Save the list of blue screen crashes into a tab-delimited text file.
/scomma <Filename>
Save the list of blue screen crashes into a comma-delimited text file
(csv).
/stabular <Filename>
Save the list of blue screen crashes into a tabular text file.
/shtml <Filename>
Save the list of blue screen crashes into HTML file (Horizontal).
/sverhtml <Filename>
Save the list of blue screen crashes into HTML file (Vertical).
/sxml <Filename>
Save the list of blue screen crashes into XML file.
/sort <column>
This command-line option can be used with other save options for sorting
by the desired column. If you don't specify this option, the list is
sorted according to the last sort that you made from the user interface.
The <column> parameter can specify the column index (0 for the first
column, 1 for the second column, and so on) or the name of the column,
like "Bug Check Code" and "Crash Time". You can specify the '~' prefix
character (e.g: "~Crash Time") if you want to sort in descending order.
You can put multiple /sort in the command-line if you want to sort by
multiple columns.
Examples:
BlueScreenView.exe /shtml "f:\temp\crashes.html" /sort 2 /sort ~1
BlueScreenView.exe /shtml "f:\temp\crashes.html" /sort "Bug Check String"
/sort "~Crash Time"
/nosort
When you specify this command-line option, the list will be saved without
any sorting.
License
=======
This utility is released as freeware. You are allowed to freely
distribute this utility via floppy disk, CD-ROM, Internet, or in any
other way, as long as you don't charge anything for this. If you
distribute this utility, you must include all files in the distribution
package, without any modification !
Disclaimer
==========
The software is provided "AS IS" without any warranty, either expressed
or implied, including, but not limited to, the implied warranties of
merchantability and fitness for a particular purpose. The author will not
be liable for any special, incidental, consequential or indirect damages
due to loss of data or any other reason.
Feedback
========
If you have any problem, suggestion, comment, or you found a bug in my
utility, you can send a message to [email protected]