BlueScreenView: how to use the program. The reasons for the "blue screen of death"

The sudden appearance of the so-called "blue screen of death", abbreviated as BSoD, if not at all, for most users, it almost causes a shock state. And in fact sometimes it can arise for no apparent reason, which the user can not always identify. For this, the BlueScreenView program was developed. How to use this application, now and will be shown. At the same time we will touch upon some theoretical questions connected with such failures.

"Blue screen of death": the reasons for the appearance

To better understand the essence of this phenomenon, you need to turn to comparing the computer with the human psyche. For example, a person suddenly saw something terrible, immediately became frightened and fell into a swoon.

The same is observed in the case of a computer, only as a reason there is some critical error, mechanical or software failure. The computer is "frightened," and the blue screen is a sign of an unconscious state, although in some cases this can also be treated as a protective reaction when the system disables all processes that could threaten the security or operability of the system.

As a rule, after restarting the system, everything again works fine. But if the screen appears in the second, the third time, there is already an urgent need to find out the cause of the failures and apply cardinal measures to eliminate their causes.

Although the indication of a failure on the screen is present (this is indicated by a description of the error with a special stop code), sometimes an ordinary user can not understand what the reason was. Among the main distinguish the following:

• Mechanical damage to "iron" components (most often problems with RAM, sound and video equipment);
• Conflicts at the level of incorrectly installed drivers;
• Conflicts after installing an inappropriate configuration of the computer software or games (software requirements are certainly higher than what this particular system has);
• The impact of viruses, malicious code, and so on.

But with the BlueScreenView program, the detection of such errors with obtaining the most complete information on emerging conflicts becomes an elementary matter even for a user who does not really understand the issue.

What is BlueScreenView 1.42, and why is it needed?

The BlueScreenView application is one of the easiest tools to identify non-common, and specific reasons for the emergence of BSoD. With its help, you can view crash dumps, and find out which program or "iron" component it called. Based on the report, you can already make the appropriate decision to eliminate the emerged situations.

Presets

Before you figure out how to use the program, you need to make some necessary settings. Many, probably, noticed that the information about the failure can be kept on the screen for only a few seconds, after which the automatic restart of the system follows. The user sometimes does not even have time to read the critical error message.

To prevent this from happening and you could scrupulously study the descriptions of errors, you just need to disable the reboot. This is done simply. First, we call the properties menu with a right-click on the computer icon (on the desktop, in the explorer or any other file manager), then go to the "Advanced" section, and click the options button on the download and restore line. In a new window, you should remove the "bird" in front of a parameter indicating the use of an automatic reboot while crashing the system.

BlueScreenView: how to use?

Now you can proceed to the program itself. The first and most important: the current version of it is released in the form of a portable version (Portable), that is, does not require installation. The downloaded archive should be simply unpacked in a convenient place for itself and starting from the program's main folder to launch it (a standard EXE file). Versions are available for both 32-bit and 64-bit systems, not to mention the fact that the utility supports a huge number of language packs and "weighs" only 54 Kb.

Now about how to use the program in the most primitive case, using standard tools. The main application window is divided into two large fields. Top of the list are error dumps, from the bottom - problem drivers and components.

To get the full information on the fault that interests us, select it in the upper window, and in the bottom - double click on the problem component that caused the critical error (they are all marked in red). A report window will appear on the screen, indicating the name of the file, its description, version, location, software developer, etc.

Thus, it immediately becomes clear what exactly influenced the appearance of the malfunctions. Next, a solution is made to fix the problems (for example, reinstalling or updating the problem device driver).

Additional Tools

Among the additional features of the program, you can note a convenient system for sorting and ordering the displayed information (you can leave only what you need at the moment, removing everything else). Also, if desired, from below, you can display the original "blue screen", which was shown on the monitor at the time of the crash.

Creating and sending reports

Now a few words about one more nuance that is present in the program BlueScreenView. How to use the utility is already understandable, but any user can have a situation when he does not want to analyze the report on malfunctions or simply does not understand either its essence or the search for an appropriate method of eliminating the problem.

To do this, the application provides a function to immediately send a report as an HTML document, for example, to someone from friends or specialists. To do this, select the desired dump file in the top field, and right-click the context menu where the corresponding HTML report creation line is used. In addition, there are several more options (search for errors in the Google system and a number of additional settings).

Possible startup errors

But not always so cloudless. Sometimes an error may occur when the application starts. There are a lot of reasons for this. First, pay attention to the moment that you run the program, if you work on Windows 7 and above, you need only on behalf of the administrator. Also, an error at startup may appear if the initially loaded archive did not contain absolutely all the components necessary for the correct functioning of the application, was corrupted or simply "nedokachan."

It may also be that the bit depth of the application and the operating system does not match (the 64-bit program the user tries to run in a 32-bit system). On such seemingly small things, too, should pay attention. Yes, and download the application to your computer is better initially from proven sites, since today there are cases when the desired archive contained Trojan viruses. In extreme cases, before unpacking it is better to check at once with a regular antivirus scanner.

Conclusion

That's all for the BlueScreenView program. How to use this utility, I think everyone is already clear. There is nothing supernatural in this. It remains to add that on the Internet you can easily find BlueScreenView in Russian, which many users will greatly facilitate the work not only with the basic elements of the interface, but also with the descriptive part of the report files.