The sudden appearance of the so-called "blue screen of death", abbreviated as BSoD, if not all, then most users cause almost a shock state. But sometimes it can occur for no apparent reason, which the user can not always identify. For this, the BlueScreenView program was developed. How to use this application will now be shown. At the same time, we will touch upon some theoretical issues related to such failures.
The Blue Screen of Death: Causes
To better understand the essence of this phenomenon, you need to look at comparing the computer with the human psyche. For example, a person suddenly saw something terrible, instantly frightened and fainted.
The same thing is observed in the case of a computer, only some critical error, mechanical or software failure, appears as the reason. The computer is “scared”, and the blue screen is a sign of a fainting state, although in some cases such a response can also be interpreted as a protective reaction when the system shuts down all processes that could threaten the security or performance of the system.
As a rule, after restarting the system everything works fine again. But if the screen appears for the second, third time, then you already urgently need to find out the cause of the failures and apply drastic measures to eliminate their causes.
Although there is an indication of a failure on the screen (this is indicated by the description of the error with a special stop code), sometimes the average user cannot understand what the reason was. Among the main distinguish the following:
- mechanical damage to the “iron” components (most often problems with RAM, sound and video equipment);
- Conflicts at the level of incorrectly installed drivers;
- conflicts after the installation of an inappropriate configuration of a computer software or games (software requirements are obviously higher than this particular system has);
- exposure to viruses, malware, etc.
But with the BlueScreenView program, identifying such errors with obtaining the most complete information on emerging conflicts becomes an elementary matter, even for a user who does not understand the essence of this issue.
What is BlueScreenView 1.42, and why is it needed?
The BlueScreenView application is one of the easiest tools to identify not common, but specific causes of BSoD. With its help, you can view crash dumps, as well as find out which software or hardware component caused it. Based on the report, you can already make an appropriate decision to resolve the situation.
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, followed by an automatic restart of the system. The user sometimes does not even have time to read the critical error message.
To prevent this from happening and you can scrupulously study the error descriptions, you just need to disable the reboot. This is done simply. First, we call up the properties menu by right-clicking on the computer icon (on the "Desktop", in "Explorer" or in any other file manager), then go to the "Advanced" section, and press the options button on the boot and recovery line. In the new window, remove the “bird” opposite the parameter indicating the use of automatic reboot when the system crashes.
BlueScreenView: how to use?
Now you can start the program itself. First and most important: its current modification is available as a portable version (Portable), that is, it does not require installation. The downloaded archive you just need to unzip to a convenient place for yourself and already from the main folder of the program to launch it (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. Error dumps are displayed at the top, and problematic drivers and components are displayed at the bottom.
To get complete information on the failure of interest to us, you need to select it in the upper window, and in the lower window, double-click on the problem component that caused the critical error (all of them are marked in red). The report window will be displayed on the screen, where the name of the file, its description, version, location, software developer, etc. are indicated.
Thus, it immediately becomes clear what exactly affected the appearance of the problems. Next, a decision is made to fix the problems (for example, reinstalling or updating the problematic device driver).
Additional tools
Among the additional features of the program, a convenient system for sorting and organizing the displayed information can be noted (you can leave only what is needed 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 present in the BlueScreenView program. How to use the utility is already clear, but any user may have a situation when he does not want to analyze the crash report or simply does not understand its essence, nor the search for an appropriate method to fix the problem.
To do this, the application provides the function of instantly sending a report in the form of an HTML document, for example, to someone from friends or specialists. To do this, the desired dump file is selected in the upper field, and the context menu is used with a right click, where the corresponding line for creating the HTML report 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 everything is not always so cloudless. Sometimes an error may occur when starting the application itself. The reasons for this can be counted quite a lot. To get started, pay attention to the moment that you need to run the program if you are running on Windows 7 and above only as an administrator. Also, an error at startup may appear if the initially downloaded archive did not contain absolutely all the components necessary for the correct functioning of the application, it was damaged or simply “not downloaded”.
It may be that the bit depth of the application and the operating system do not match (the user is trying to run a 64-bit program on a 32-bit system). It would be worth paying attention to such seemingly trifles. Yes, and it’s better to download the application to your computer from verified sites from the very beginning, because today there are cases when the desired archive contained trojan viruses. In an extreme case, before unpacking it is better to check it at least with a regular anti-virus scanner.
Conclusion
That's it for BlueScreenView. How to use this utility, it seems, is already clear to everyone. There is nothing supernatural in this. It remains to add that on the Internet you can easily find BlueScreenView in Russian, which will make it much easier for many users to work not only with the main elements of the interface, but also with the descriptive part of the report files.