BlueScreen problem event name - how to fix? BlueScreen what is this problem? How to use bluescreenview

“Blue Screen of Death”, or as experts call BSOD, is a protective reaction of the computer that suspends system work before potential failures or damage. In certain situations, BlueScreen (error) appears due to driver problems. In such cases, simply restarting the computer helps a lot. But situations often occur when, without additional actions and special programs is no longer possible. One of these popular applications is BlueScreen Viewer, which will be discussed in detail later.

It should be understood that " blue screen“- it’s not as scary as they say, but it’s very unpleasant when it appears. To remove it, you need to have certain knowledge in computer technology and, of course, know the reasons for its appearance.

The event (problem) name is BlueScreen. Causes

The reasons for the appearance of a similar problem on a computer are varied: from a virus and a power outage to the deletion of operating system files and incorrect installation software. In most cases, you can cope with this problem without leaving your home. But to do this, you should at least approximately determine the reasons that led to the “blue screen”. These reasons can be briefly summarized as follows:

• severe overheating motherboard or video cards;
• driver damage;
• attempt to overclock the video card;
• violation in random access memory;
• lack of power in the power supply;
• failure of the device itself.

Most of the causes of blue screens lie in the computer's video card. For example, such a common problem as BlueScreen (code 1049) means that the video card is not working properly.

Diagnose the problem that has arisen

The most common cause of the blue screen problem is recent actions to replace or install new components on the computer. This means that either there are no drivers for the new components, or they are installed “crookedly”.

Sometimes a BlueScreen event occurs because the computer's internal parts are not properly connected in place. motherboard or with other nodes. In order to check all the parts, you should open and inspect the cables, RAM and video card for correct connections. This check is harder to do on a laptop. The only thing you can do is open back cover laptop and check the connections hard drive and RAM.

Due to severe overheating of the video card and central processor Often system failures can also occur. To find out whether the processor and video card are overheating, you can look at the BIOS menu, where the internal one is indicated, or use a special program that measures the temperature internal components and nodes.

The next reason why the event name is displayed is BlueScreen problems, is a breakdown of the RAM stick. The operation of the RAM can be tested with the Memtest program, which within a few minutes will scan the memory and show whether the RAM is really causing the system to fail.

Also, the BlueScreen problem may appear due to violations in work hard disk. To check this option, you can use special programs to eliminate errors and failures in your hard drive or system function chkdsk, which can be found in Windows, in the “Service” tab. When it starts, it will start checking for errors.

And the last common option is to scan your computer for viruses. Commonly used ones are suitable for this. antivirus programs, such as Avast, Doctor Web, Norton, Kaspersky and others.

If BlueScreen (1049) error still appears, how can I fix it?

It happens that system failures that lead to a “blue screen” effect are caused by more serious problems than the reasons described above. Therefore, more radical means of correcting this error should be used.

If all of the above methods did not help, and the “screen of death” constantly appears on the monitor when loading or while the computer is running, then the most effective way To restore everything to working condition is to return the PC to basic configurations and parameters, i.e., reinstall the system. Programmers often joke that this is the only effective way to solve all computer system problems, including BlueScreen (1049). Indeed, this method can solve almost all computer problems related to system failures, violations or viral infections. However, this option has a serious drawback - it is the loss of all saved information on the hard drive during the reinstallation of Windows. Therefore, this is the most extreme way to restore your computer.

There is another way to eradicate BSOD, which may allow the user not to resort to radical methods such as reinstalling the operating system - special recovery programs.

Using utility programs

First of all, I would like to name such a program as BlueScreen Viewer, which deserves to take first place among computer users when you need to clean your PC or fix system errors. This program can be downloaded in Russian completely free of charge and installed on your device. It has a number of advantages and disadvantages compared to other similar programs:

• scans minidump files created during a system failure that led to a blue screen;
• provides detailed information in the consolidated table;
• shows the date/time the problem occurred;
• shows error code;
• displays the names of minidump files on the monitor;
• provides information about modules and drivers that could cause the system to crash.

Advantages of the Viewer BlueScreen application

In addition, the program has the following advantages:

• it's free;
• does not require it to be installed on a PC;
• V file folder there is a localization tool;
• lightweight and easy to use.

How the program works

When a system failure occurs, the program searches for files and drivers that could cause such a disruption in the computer. When it detects them, it creates a report in the form of a table describing the driver and its location.

The program can also find the real reason for the system crash and display Full description this problem with the date it occurred.

In addition to the above program, BlueScreen (error) can also be diagnosed by such applications as WhoCrashed and WhatIsHang. These are free programs that detect faulty drivers that cause the operating system to crash.

Computer blue screen - request for help

Many people refer to this problem as the “death” of the PC, when in fact, the “death screen” is a cry for help from the user. When a person has something in pain, he can complain to his loved ones or a doctor about this pain, talk about the symptoms, and so on. What should a smart, but still silent device do when a serious problem occurs in its “organism”, which we call BlueScreen (error)? All it can do is show us a “blue screen” on the monitor, on which the computer’s “complaints” will be written in white letters and symbols to the user with brief description problem containing just a few numbers.

These "complaints" are known as BlueScreen codes. Descriptions of these codes can be easily found. Each code is specifically responsible for a particular error and the reason for the occurrence of a malfunction in the system. If you do not understand the code description language, then it is better to go to some well-known programming forum, where experts can explain the system error and advise how to remove it.

If you have already tried everything, and the “blue screen” still appears, then you should contact service center for repairs personal computers and laptops.

Features and nuances of self-recovery of the system

• If there was a recent video driver update, you should try to roll it back or restore the system to a higher level. early date. To do this, in the system options of your computer, you need to set the function to automatically fix a restore point when installing new software.
• BlueScreen (error) may appear due to an attempt to overclock the processor, video card or operating memory - these processes must be stopped.
• If this problem occurs during games, you need to lower the screen resolution and set the graphics to the minimum settings.
• You need to update the Direct file.

There are different methods for solving the “screen of death” problem. Professionals recommend using them one at a time and not rushing to take radical measures, such as reinstalling the system, returning Windows to basic parameters or sending the computer for repair at service centers.

Here is another option for restoring the OS.

If the blue screen does not allow the system to boot, then you should switch to safe PC mode. To do this, press F8 while the computer is booting. After this, the boot menu will appear, in which you can select the mode we need. The difference between safe mode and other boots is that it boots without using network drivers.

In this mode it is possible because they also often display the event name - BlueScreen. To do this, you should use anti-virus programs with an updated version of the database.

also in safe mode You can try to restore the system without reinstalling it. In this case, insert the disk with Windows, select the “System Restore” function and click “OK”. Thanks to this choice, old system files are erased and new ones are installed without losing personal information.

In the same mode, you can roll back drivers. Incorrect installed drivers may cause system failure.

Secrets of programmers

There is another secret that reveals the reason for the appearance of BSOD - lack of free space on your hard drive. Many people don’t know this, but if there is less than 15% free space left on the hard drive, this also often causes this problem. It is necessary to clean the hard drive from old and unnecessary files using special programs or functions of the system itself.

On some motherboards there is a special button located near the processor, which, when pressed, resets all recent installations and system updates. Therefore, as one option, you should open the computer unit and see if this button is there. If there is, then you should use it, holding it for 15 seconds, which will allow you to return the system to its initial state.

Results

There is no need to immediately grab your head because the BlueScreen (1049) error message appears. How to fix the blue screen problem at home, while having basic knowledge of computer use, can be seen from the information described above. And it’s still too early to run to the nearest PC repair center; you need to try to restore the “fallen” system yourself, which will save quite a lot of money and give you confidence in your strengths and capabilities. And only if all methods do not bring results, you can take the computer for repair.

Attention! The article describes methods that require some preparedness and experience of the user.

In this article there will be no “smart” words; we will try to explain unclear words right away. The article will provide general recommendations for eliminating the “blue screen of death” specifically for beginners. For all programs used, there will (if possible) be links to download files or pages from which you can download them.

Blue screen of death, also known as BSOD, also known as bluescreen. What to do?

A lot has already been written about the so-called blue screens of death. Experienced users of personal computers with the Windows operating system have long learned to study them and quite successfully determine the reason for their appearance.

The problem for novice users is that they are terrified of blue screens. Of course, such a screen can cause a lot of trouble. But seven troubles - one answer: a “programmer” comes in who got a bad mark in English at school, and the Unified State Exam is just around the corner and reinstalls the system. And 20 minutes after he leaves, you are very disappointed - the unfortunate error pops up again.

But what to do then, because on most forums and websites, everything is written in technical language. Once you ask a clarifying question, you are sent to the “sandbox” - a section of a website or forum for beginners. Good advice. Such sections usually contain information that will allow you to study basic concepts and terms. But all this takes time, and you obviously won’t do this if you, for example, have a small child. What can you advise in this case?

• Take your computer (laptop) to a service center. This is the most preferred option.
• Try to fix the BSOD without outside help. Also a good option, but it requires you basic concepts and skills, at least such as entering the website address directly into address bar without the help of Google or Yandex.

If you understand what is meant in the second paragraph, we can get started.

Standard testing methods.

Let's assume that your operating system still boots normally and the BSOD error appears some time after startup. Let's try to take advantage standard methods checking the computer until it appeared.

1. Checking the temperature of computer components

It happens that novice users do not even know about the need to clean their computer. If they do, it comes down to regular vacuuming.

Cleaning your computer involves a whole range of activities. This includes cleaning the computer from dust inside the case, cleaning radiators (dust is compressed in its fins), also cleaning and lubricating fans, replacing thermal paste between radiators and microcircuits. So vacuuming is quite ineffective.

Let's check the temperature of your computer components. To do this, it is advisable to use some specialized program. We will use one of the most popular programs - AIDA64. It's paid. But effective. Just a warning: ways to get it for free, etc. you won't find it.

So let's launch the program. On the left side of the window select "Computer" then "Sensors" and look.

We warn you right away. Meaning "PCH Diode" very often shows high temperature. Somewhere on the forum, developers AIDA64 confirmed that this is exactly the case on many boards. This screenshot was no exception. The actual temperature of all components of our PC does not exceed 34 degrees.

In general, opinions about what temperature is considered normal vary. But nevertheless, we will proceed from the fact that the normal operating temperature CPU- 30-50 degrees. Anything higher will be considered overheating. For video card ( GPU), normal temperature Let's consider 60-65 degrees. I would like to clarify that these figures are taken from personal experience and the norm varies from processor to processor, from video card to video card. For a motherboard, the “tolerable” norm is 40-45, but for some motherboards the norm may be 50.

If the numbers are an order of magnitude higher than those given, the “patient’s” temperature needs to be “brought down.” It is possible that overheating is the cause of the blue screen. If this is left to chance, the computer may begin to turn off spontaneously - the protection will be triggered. If for some reason it does not work, or your motherboard is of poor quality, then the consequences can be dire.

Also pay attention to the fan speed CPU. If its speed is above 3500 rpm. This also indirectly indicates overheating.

Many bloggers on YouTube tell you how to clean your computer at home.

//www.youtube.com/watch?v=KW5onHAIhjc

2. Checking RAM

Sometimes the culprits of stop errors are “broken” RAM modules. To check them, use the utility MemTest86+. This program is available for Windows, as well as a version with its own bootloader (allows you to load MemTest instead of Windows). The latter is preferable, since when scanning from Windows, the computer may freeze, and you never know what else. So we will use the second option.

We will need:

1. Flash drive.
2. Internet connection.

2.1 Downloading and recording MemTest to a flash card.

Download the automatic program installer MemTest and unpack it to any convenient place, for example on Desktop.

Insert a clean USB flash drive into your computer and run the extracted file.

The red rectangle marks the required parameters that will be used when recording MemTest to a USB flash drive. Select the letter of the flash drive and check the box that will allow the program to format it.

Click the button , and on the next screen .

All. Program MemTest recorded, and the flash drive is now bootable.

2.2 Load MemTest from a flash drive.

We turn on the computer and see this picture:

The boot menu in our case opens by pressing . In your case, it may be another key - you will have to figure it out yourself.

Select our flash drive, click and after a couple of seconds the RAM check begins.

Our memory test completed successfully.

The bad thing is when red lines appear during the check.

If a similar picture appears on your screen, most likely the bluescreen appeared precisely because of a malfunction of one or more RAM modules. What to do in this case:

1. try to identify the faulty module by inserting them one by one into the motherboard and checking each one MemTest-ohm.

2. do not use a faulty module, or replace it with a working one.

Remember: any modern computer or a laptop is a high-tech device that requires thoughtful handling of all its components.

If you are not confident in your abilities, ask more experienced users for help. You perform all actions at your own peril and risk. Only you and no one else is responsible for your actions.

3. Checking the video card.

The video card is a fairly common cause of a stop error. If your computer has a discrete video card and there is a connector on the motherboard SVGA, try removing the video adapter board and working with the built-in one.

How to remove the video card is shown in the video above.

4. Checking the power supply.

Unfortunately, it is almost impossible to check the power supply at home. Someone may disagree, but nevertheless it is so. It is not enough to measure the voltage at the connectors with a multimeter. Checking the power supply is a painstaking process.

The only thing you can try to do is try to put similar in parameters power supply from a working machine. Again, some skills are required.

5. Checking the hard drive.

Last time, common cause screens of "death" steel hard disks. 10-15 years ago, and there was no thought of sinning on the hard drive. They were the most reliable element of the computer.

Now that they have begun to save heavily on their production, i.e. They moved production to countries with cheaper labor, began to use copper or brass alloys instead of gilding, the quality and price of the discs leave much to be desired.

Of course, there are quality ones, but affording them home computer Not everyone can. So it's still worth checking the disk.

5.1 Checking the S.M.A.R.T of the hard drive.

Modern hard drives have this amazing technology - S.M.A.R.T. This is such a microprogram in hard controller disk, which collects information about its errors - read-write errors, head movement errors, etc.

So, it will not be possible to describe every parameter collected by this technology, since this is a broad topic, clearly not for ordinary users. We will just check the overall health of our disk.

For this we need a program HHDScan from Data Recovery Lab R.LAB.

The archive needs to be unpacked to any place convenient for you.

Let's move directly to the program itself. On the main screen of the program you need to select the hard drive to be tested and click on the button .

A window will open with many parameters, and they will be marked in green or red. If everyone is green, everything is fine. If there are red ones, look for their meanings in Yandex or Google.

5.2 Checking the file system for errors.

All that remains is to check file system for mistakes. This can be done from the command line using the utility CHKDSK.

Run the cmd program as Administrator (habit).

In the window that opens, enter:

chkdsk c: /r /f

where “c” is the letter of your system drive.

Be patient. The process is not fast. The program will check and correct any errors found automatically.

Something else. If errors are detected, try changing the interface cable SATA or IDE or simply “trail”.

6. Checking the operating system, updating it and updating drivers.

Before this, we were checking equipment. Now let's check the integrity of system files, update the operating system and drivers, and check for viruses. Let's start with viruses, since their presence can prevent us from performing other actions.

6.1 Checking for viruses and malware

The Internet was once relatively clean. There was a minimum of advertising, and there were only rumors about viruses. Now everything has changed - advertising is at every step, and there is no need to talk about the number of viruses and any other “evil spirits”. Especially recently, the so-called Malware- malware from which it is very difficult to escape. It easily bypasses antiviruses and firewalls.

So, update your antivirus, and turn off its screens for a while (so as not to interfere). Download utilities Cure IT And AntiMalwareBytes. Scan your computer with them. Why these programs? They are very simple for any user, even a beginner. Each of these utilities finds viruses and malware even on seemingly clean computers.

After the reboot, you can proceed to further actions.

6.2 Checking the integrity of system files.

Run again command line on behalf of the Administrator. In the program window, enter:

sfc /scannow

and press .

The scanning process will begin, during which you will definitely have time to drink tea. As a result, Windows will restore all files that it considers damaged.

Restart your computer.

6.3 Windows update.

Update Windows. Whatever one may say, it needs to be updated. The update helps eliminate system flaws and vulnerabilities. It also improves its overall stability and security.

It is quite possible that the update has already resolved some problems due to which bluescreen may appear on your equipment. You can update the system by opening Control Panel, and then Windows Update.

6.4 Update drivers

Update your hardware drivers. The considerations are the same as with Windows updates - the more recent the better. This can be done in several ways. It all depends on your desire and experience. You can download each driver individually by visiting the websites of your hardware manufacturers.

You can use the utilities that are located on the driver disk from your motherboard, for example MSI Live Update And ASUS.

You can download offline and online driver packs containing all kinds of hardware drivers, For example DriverPack Solution or DevID Agent. All listed programs are in Russian and are as automated as possible.

Conclusion

These are not all the ways to resolve the BSOD error. There is a lot that was not included in this article.

For example:

• How to disable automatic system reboot upon failure.
• how to identify an error by its code.
• how to read a memory dump.
• and much more...

But that was not the purpose of the post.

The purpose of the post is to show an inexperienced user how to deal with an error in ways available to him. Explain that it is not necessary to waste time and energy on reinstalling the system, being unsure of the result.

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:

1. Problems with computer hardware - wrong installed devices;
2. Overheating of the video card, processor or other components of the laptop or PC;
3. Voltage drop in the network;
4. Wrong installed updates Windows;
5. Important items removed system files or folders;
6. Incorrectly installed drivers are the most common mistake.

As a rule, in case of a Blue Screen, a simple reboot helps many users. After it everything returns to normal. But if the problem is with the drivers, then in 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 an error appears BSOD screen appears literally for a second and then reboots. 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 Perform an 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 in 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:

1. Disable the built-in video card (if any) in the settings;
2. Completely update video drivers;
3. Check the physical parameters - for overheating and whether it fits tightly in the slot;
4. Use the BlueScreenView utility to determine.

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

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
• 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

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

1. 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.
2. 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.
3. Blue Screen in XP Style: Displays a blue screen that looks very similar to the one that Windows displayed during the crash.
4. 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

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

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

Translating BlueScreenView to other languages

1. Run BlueScreenView with /savelangfile parameter:
   BlueScreenView.exe /savelangfile
   A file named BlueScreenView_lng.ini will be created in the folder of BlueScreenView utility.
2. Open the created language file in Notepad or in any other text editor.
3. 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.
4. 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

PC users have a strong fear that unites everyone - BSOD (Blue Screen of Death), a critical error that leads to a system crash without saving data. It is difficult for the average user to decipher information about a failure if, after displaying technical information, the computer immediately reboots. Therefore, let's look at how to use BlueScreenView, an application that saves and decrypts information about OS failures.

Creating a Dump File

IN operating systems Windows 7, 8, 10 RAM dump is saved automatically. But we will edit the file creation settings and optimize them for BlueScreenView.

Let's go through the following points:

1. Open “This PC” – “System Properties”.
   
   
2. Click Advanced System Settings.
   
   
3. In the “Advanced” tab, click on the “Options” button in the “Boot and Recovery” block.
   
4. In the window that appears, uncheck the “Replace existing dump file” checkbox and select “Small memory dump (256 KB)” in the “Write debugging information” field.
   

Reference! A small memory dump contains the necessary information to analyze the error and does not take up much disk space. It is not recommended to replace an existing dump file, because... There are several errors, but only one is recorded.

Memory dump analysis

First of all, launch BlueScreenView. The application automatically scans the storage folder for all memory dumps.

To extract the necessary information you need:

1. Select the required .dmp file from the list, look at the list of drivers and components that were loaded during the last OS startup.
   
   
2. Double-click on the field highlighted in red.
3. Acquainted with technical information about the error.
   
   
4. By right-clicking on the memory dump field, you can import the data into a file for subsequent sending to a specialist or support service. It is also possible to search for a solution to a problem directly from the application.
   
   

As a result, we can say that using BlueScreenView is a complete pleasure. This is a small and functional utility that will free you from the need to watch for BSOD errors with a sheet of paper in your hands.

For those interested, a video is provided on how to use BlueScreenView.