Blue Screen error detection program. General recommendations for eliminating BSOD errors for beginners. Checking the operating system, updating it and updating drivers
Related Utilities
- WinCrashReport - Displays a report about crashed Windows application.
- WhatIsHang - Get information about Windows software that stopped responding (hang)
- AppCrashView - View application crash information on Windows 7/Vista.
See Also
- NK2Edit- Edit, merge and fix the AutoComplete files (.NK2) of Microsoft Outlook.
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.55:
- Added Drag & Drop support: You can now drag a single MiniDump file from Explorer into the main window of BlueScreenView.
- Fixed bug: BlueScreenView failed to remember the last size/position of the main window if it was not located in the primary monitor.
- Version 1.52:
- Added "Google Search - Bug Check" and "Google Search - Bug Check + Parameter 1" options.
- Version 1.51:
- Added automatic secondary sorting ("Crash Time" column).
- Added 64-bit build.
- Version 1.50:
- The "Crash Time" now displays more accurate date/time of the crash. In previous versions, the value of "Crash Time" column was taken from the date/time of dump file, which actually represents that time that Windows loaded again, after the crash. The actual crash time is stored inside the dump file , and now the "Crash Time" displays this value.
- Added "Dump File Time" column, which displays the modified time of the dump file.
- Version 1.47:
- Added "Auto Size Columns+Headers" option, which allows you to automatically resize the columns according to the row values and column headers.
- Version 1.46:
- Fixed issue: The properties and the "Advanced Options" windows opened in the wrong monitor, on multi-monitors system.
- Version 1.45:
- You can now choose to open only a specific dump file - from the user interface or from command-line.
- You can now also specify the MiniDump folder or MiniDump file as a single parameter, and BlueScreenView will be opened with the right dump file/folder, for example: BlueScreenView.exe C:\windows\minidump\Mini011209-01.dmp
- Version 1.40:
- Added "Raw Data" mode on the lower pane, which displays the processor registers and memory hex dump.
- Version 1.35:
- Added "Crash Address" column.
- Added 3 columns that display that last 3 calls found in the stack (Only for 32-bit crashes)
- Version 1.32:
- 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:
- 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:
- Added "Dump File Size" column.
- Version 1.29:
- 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
- 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.
- Version 1.28:
- 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:
- Fixed issue: removed the wrong encoding from the xml string, which caused problems to some xml viewers.
- Version 1.26:
- Fixed "DumpChk" mode to work properly when DumpChk processing takes more than a few seconds.
- Version 1.25:
- 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"
- The default MiniDump folder is now taken from HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl
- Version 1.20:
- Added 3 new columns in the upper pane: Processors Count, Major Version, Minor Version.
- Added "Explorer Copy" option, which allows you to copy dump files to the clipboard and then paste them into Explorer window.
- Version 1.15:
- 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).
- Added Combo-Box to easily choose the MiniDump folders available in the hard-disks currently attached to your computer.
- Added "Computer Name" and "Full Path" columns.
- Version 1.11:
- Added /sort command-line option.
- Version 1.10:
- Added accelerator keys for allowing you to toggle between modes more easily.
- Added command-line options for saving the crash dumps list to text/csv/html/xml file.
- Added command-line option for opening BlueScreenView with the desired MiniDump folder.
- Fixed focus problems when opening the "Advanced Options" window.
- Added "default" button to the "Advanced Options" window.
- Added "processor" column - 32-bit or x64.
- Version 1.05 - Added support for x64 MiniDump files.
- Version 1.00 - First release.
BlueScreenView Features
- Automatically scans your current minidump folder and displays the list of all crash dumps, including crash dump date/time and crash details.
- Allows you to view a blue screen which is very similar to the one that Windows displayed during the crash.
- BlueScreenView enumerates the memory addresses inside the stack of the crash, and find all drivers/modules that might be involved in the crash.
- BlueScreenView also allows you to work with another instance of Windows, simply by choosing the right minidump folder (In Advanced Options).
- BlueScreenView automatically locate the drivers appeared in the crash dump, and extract their version resource information, including product name, file version, company, and file description.
System Requirements
- BlueScreenView works with Windows XP, Windows Server 2003, Windows Server 2008, Windows Vista, Windows 7, Windows 8, Windows 10, as long as Windows is configured to save minidump files during BSOD crashes. If your system doesn't create MiniDump files on a blue screen crash, try to configure it according to the following article:
- BlueScreenView can read the MiniDump files of both 32-bit and x64 systems.
- Be aware that on Windows 10, some of the created MiniDump files might be empty and BlueScreenView will not display them.
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.exeAfter running BlueScreenView, it automatically scans your MiniDump folder and display all crash details in the upper pane.
Crashes Information Columns (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.
- Crash Address: The memory address that the crash occurred. (The address in the EIP/RIP processor register) In some crashes, this value might be identical to "Caused By Address" value, while in others, the crash address is different from the driver that caused the crash.
- Stack Address 1 - 3: The last 3 addresses found in the call stack. Be aware that in some crashes, these values will be empty. Also, the stack addresses list is currently not supported for 64-bit crashes.
Drivers Information Columns (Lower Pane)
- Filename: The driver/module filename
- Address In Stack: The memory address of this driver that was found in the stack.
- From Address: First memory address of this driver.
- To Address: Last memory address of this driver.
- Size: Driver size in memory.
- Time Stamp: Time stamp of this driver.
- Time String: Time stamp of this driver, displayed in date/time format.
- Product Name: Product name of this driver, loaded from the version resource of the driver.
- File Description: File description of this driver, loaded from the version resource of the driver.
- File Version: File version of this driver, loaded from the version resource of the driver.
- Company: Company name of this driver, loaded from the version resource of the driver.
- Full Path: Full path of the driver filename.
Lower Pane Modes
Currently, the lower pane has 4 different display modes. You can change the display mode of the lower pane from Options->Lower Pane Mode menu.- All Drivers: Displays all the drivers that were loaded during the crash that you selected in the upper pane. The drivers/module that their memory addresses found in the stack, are marked in pink color.
- Only Drivers Found In Stack: Displays only the modules/drivers that their memory addresses found in the stack of the crash. There is a very high chance that one of the drivers in this list is the one that caused the crash.
- Blue Screen in XP Style: Displays a blue screen that looks very similar to the one that Windows displayed during the crash.
- DumpChk Output: Displays the output of Microsoft DumpChk utility. This mode only works when Microsoft DumpChk is installed on your computer and BlueScreenView is configured to run it from the right folder (In the Advanced Options window).
You can get DumpChk from the installation CD/DVD of Windows or with the installationtion of Debugging Tools for Windows.
Crashes of Remote Network Computer
If you have multiple computers on your network and you have full administrator access to them (e.g: you have access to \\ComputerName\c$), you can also view the crashes of the other computers on your network remotely. In order to do that, simply go to "Advanced Options" (Ctrl+O) and type the MiniDump folder of the remote computer, for example: \\MyComp\c$\Windows\MiniDump.Notice: If you fail to get full administrator access to the remote computer, you should read the instructions in the following Blog post: .
Watching the crashes of multiple computers on your network
If you have a network with multiple computers, and you have full admin access to these computers, you can view the blue screens list of all these computers in one table, and easily detect computers with recurring BSOD problems.In order to use this feature, prepare a list of all computer names/IP addresses that you want to inspect, and save it to a simple text file. The computer names in the list can be delimited by comma, semicolon, tab character, or Enter (CRLF).
Example for computer names list:
Comp01 comp02 192.168.0.1 192.168.0.2 192.168.0.4 After you have a text file contains the computers list, you can go to Advanced Options window (Ctrl+O), choose the second option and type the computers list filename.
Command-Line Options
| /LoadFrom | 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) 3 -> Load from a single MiniDump file (/SingleDumpFile parameter) |
| /MiniDumpFolder | Start BlueScreenView with the specified MiniDump folder. |
| /SingleDumpFile | Start BlueScreenView with the specified MiniDump file. (For using with /LoadFrom 3) |
| /ComputersFile | 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 | Save the list of blue screen crashes into a regular text file. |
| /stab | Save the list of blue screen crashes into a tab-delimited text file. |
| /scomma | Save the list of blue screen crashes into a comma-delimited text file (csv). |
| /stabular | Save the list of blue screen crashes into a tabular text file. |
| /shtml | Save the list of blue screen crashes into HTML file (Horizontal). |
| /sverhtml | Save the list of blue screen crashes into HTML file (Vertical). |
| /sxml | Save the list of blue screen crashes into XML file. |
| /sort | 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 Examples: |
| /nosort | When you specify this command-line option, the list will be saved without any sorting. |
Translating BlueScreenView to other languages
In order to translate BlueScreenView to other language, follow the instructions below:- Run BlueScreenView with /savelangfile parameter:
BlueScreenView.exe /savelangfile
A file named BlueScreenView_lng.ini will be created in the folder of BlueScreenView utility. - Open the created language file in Notepad or in any other text editor.
- Translate all string entries to the desired language. Optionally, you can also add your name and/or a link to your Web site. (TranslatorName and TranslatorURL values) If you add this information, it"ll be used in the "About" window.
- After you finish the translation, Run BlueScreenView, and all translated strings will be loaded from the language file.
If you want to run BlueScreenView without the translation, simply rename the language file, or move it to another folder.
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!Hello! Today we will talk about the problem of the blue screen of death - BlueScreen. Many users encounter it while working or playing on a computer. We will tell you what “Problem Event Name: BlueScreen” is and what you need to do to fix it. We will also describe a solution to the problem with BlueScreen error 1049.
Almost all of us have encountered the Blue Screen of Death. Let's try to give a simple definition of this problem, so:
BlueScreen is a “message” addressed to the user indicating a critical system error and that the computer will restart with the loss of all unsaved data. The message also indicates the general causes of the problem and the error code. Experts call this problem BSOD (Blue Screen of Death).
For Windows 7, if a blue screen occurs, an error message appears after a reboot.
The causes of BSOD can be different, from physical to systemic:
- Problems with computer hardware - incorrectly installed devices;
- Overheating of the video card, processor or other components of the laptop or PC;
- Voltage drop in the network;
- Incorrectly installed Windows updates;
- Important items removed system files or folders;
- Wrong installed drivers- the most common mistake.
As a rule, in case of a Blue Screen, it helps many users simple reboot. After it everything returns to normal. But if the problem is with the drivers, then certain cases, the problem will recur. This is possible when the user launches a game or program. Let's figure out what needs to be done in this case and how to determine what exactly the system does not like.
Very often, when a BSOD error appears, the screen appears literally for a second and then a reboot follows. To get acquainted with the problem and identify the code, you first need to remove the reboot. Sign in Control Panel\All Control Panel Items\System. Press Additional system parameters. In the window that opens, uncheck the Execute automatic reboot.
After this, you can write down the error code. There can be a huge number of sources of problems and codes. Therefore, next, you should enter this code into a search query and find a solution on the Internet. There is no single solution to such situations; each problem must be solved separately.
Diagnosis of overheating and physical problems is carried out very well by the AIDA64 program. In case of system problems, BlueScreenView is suitable for searching and identifying. It will list all the dumps (.dmp - error report) and analyze all the data, even indicating the driver that led to the problem. You can learn more about the BlueScreenView utility in this video (closer to the end).
BlueScreen code 1049 what is this problem
One of the most common reasons may be problems with video card drivers. In this case, the message “Problem event name: BlueScreen” (code 1049) appears, which means a problem with the video card. In this case, it is necessary:
- Disable the built-in video card (if any) in the settings;
- Completely update video drivers;
- Check the physical parameters - for overheating and whether it fits tightly in the slot;
- Use the BlueScreenView utility to determine.
Quote: rier
I launched it and nothing happens. How to enable scanning?
Despite the fact that the question is 2 years old, it is still relevant for lucky SES owners, and the BlueScreenView utility can help them.
Briefly about the main:
We say BSOD (not the official name), we mean SES, STOP code, crash dump, memory dump.
Occurs when there is a threat of OS crash, i.e., the developer protects the OS from “playful hands”.
Usually, SES pops up if there are problems with hardware or hardware drivers. Programs are often not capable of SES, because fail without affecting the operation of the OS, and those that work at the kernel (driver) level may present a surprise.
If it's time critical day: OS receives STOP code, stops communication, displays for 1 second Bill Gates Blue Square, goes to reboot, and automatically creates a memory dump.
To enjoy this wonderful picture: => RMB Computer or W+Break => Advanced System Settings=> Tab => Options... field System failure- remove the label Perform automatic reboot, and also, remove the label Replace existing dump file(may be useful for recurring errors). Ibid. Writing Debug Information there is a choice: Kernel memory dump or Small memory dump indicating the appropriate ways to save dumps.
But if you haven’t become the happy owner of an SES, it doesn’t matter, we will create it, because you need to know the enemy by sight.
=> W+R => regedit => Enter =>
For PS/2 keyboard: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\i8042prt\Parameters
For USB keyboard: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\kbdhid\Parameters
Create a new 32bit DWORD value called CrashOnCtrlScroll, with a value of 1.
Restart your PC.
now this happiness in your hands: holding right CTRL key press twice Scroll Lock, you will receive , we are interested within 1 And 2 .
What does it mean in translation:
An issue has been detected and the OS has been disabled to prevent damage to the PC.
User manually created a crash dump.
If you see a stop screen for the first time, restart your PC.
When repeating:
Check to see if any new hardware or software is installed correctly.
If new installation, contact the device or software manufacturer for Windows updates.
If problems continue, disable/uninstall any newly installed devices or software.
Disable BIOS memory options - caching/shadowing.
If needed safe mode to remove/disable components, restart your PC => F8 => Advanced startup options => Safe Mode.
Technical information:
*** STOP: 0x000000E2 (0x00000000, 0x00000000, 0x00000000, 0x00000000)
Data collection for emergency reset...
Initializing disk for emergency reset...
Start of physical memory reset.
Flushing physical memory to disk: 100
Reset physical memory.
For additional assistance, contact the admin/tech support team.
Error 0x000000E2 indicates that the user deliberately initiated a crash dump using the kernel debugger or using the keyboard.
Launch BlueScreenView, look..., if it doesn’t see it, help through Settings = Additional options...
“Blue Screen of Death” is an error that every user has had to deal with operating system Windows. In English it is called Blue Screen of Death, or, in short, BSOD. The error itself always leads to one thing - restarting the computer. However, it can be caused by hundreds of different factors, making it difficult to determine what causes it. IN Windows system There are special diagnostic tools that allow you to save the error log, but not every user will be able to decrypt it.
It is for the purpose of deciphering the causes of the “blue screen of death” that the BlueScreenView application is used. With its help, you can easily determine why a fatal error occurs and what needs to be done to prevent it from happening again.
What is BlueScreenView
BlueScreenView is free program, developed by Nir Sofer. It can be downloaded on the Internet from the official website of the developers and other trusted resources. The application supports a huge library of languages, including Russian.
The BlueScreenView program scans dump files on your computer that store information about the error that led to the Blue Screen of Death. Using the program, the user has the opportunity to find out as much information as possible about the error: when it occurred, what specific BSOD code was assigned by the Windows operating system, information about drivers, and so on.
How to configure Windows to run BlueScreenView
In order for the BlueScreenView application to tell you about the causes of errors, it needs to access the dump files. By default, in the Windows operating system, in order to save space on the hard drive, only the last dump file is written. To properly configure Windows to work with the BlueScreenView application, follow these steps:
At the expense of the faithful Windows settings, the BlueScreenView application will have access to all cases of BSOD errors. This will allow you to see a more complete picture of the emerging problem.
How to analyze a dump with BlueScreenView
Analyzing the error that led to the Blue Screen of Death using the BlueScreenView application is quite simple. To do this you need to do the following:
To find out more about a specific dump, right-click on it and select Google Search. All necessary information about the error that caused the Blue Screen of Death will be sent to the browser. Most often, solutions to the error can be found on the Microsoft website, which will indicate what steps you need to take to fix the problem. If instructions for resolving the error are not found, you should search in manual mode technical information about the error.
Experts often ask users to send them error dump data, which can be collected through the BlueScreenView application. To do this, right-click on a specific dump and select “HTML Report – All Items”. The error will be imported in HTML format, after which it can be sent to a technical specialist who will analyze it and try to find a way to solve the problem.
Due to pirated copies of Windows, many users are facing Bluescreen crash on their PC. Most often, the bug causes a Blue Screen to appear, which appears after launching games or programs. After the reboot, the user receives a notification window with the problem signature: “Problem event name: BlueScreen. Language code: 1049". Additional information is also indicated: OS version (for example - 6.1 7601.2 1.0 256.1) and BCCode (can be different 116, 124, 50, 19, d1, f4, a and others).
Example of critical stop error BlueScreen 1049What is this BlueScreen crash 1049?
There are many reasons why Bluescreen stop errors appear. The code itself (1049) indicates that the driver was unable to respond to the system request in a timely manner. Among the main reasons for the failure, the following can be identified:
- The corresponding driver has problems;
- Problems with overheating of computer hardware ( motherboard or video card);
- Unsuccessful attempts to overclock the video card;
- Problems with computer RAM and other malfunctions.
What to do about problem 1049?
- In most cases, the main cause of failures is “broken” video card drivers. You can check all video controllers in the Task Manager and look for a broken driver (with a yellow icon). Right-click on it and delete. After uninstallation, run the Registry Cleanup Wizard (I use third-party utilities - CCleaner). After cleaning, click on the problematic controller and select “Update drivers”.
An example of removing problematic drivers from Windows - Windows Installer works very poorly, so it is better to download drivers from the official developer resource or use the disk with all the configurations that comes with it. I use a comprehensive check and update of all drivers using the utility DriverPack Solution. True, many additional and advertising installations have appeared in it recently. But DPS does its job well.
Update Windows drivers via DriverPack Solution - If you were unable to complete the installation, or the update did not help you, then you can roll back the system to a restore point where no failures were observed.
- You can also check the functionality by starting Windows in clean boot. After a clean launch, launch the required game or application and check. You should know that there will be no application or game icons. They must be called from the installation folder or the Start menu. Video instruction.
- If you overclocked any of the PC hardware, cancel everything.
- For cases with game failures, it is advisable to update the video card drivers to
