The Blue Screen of Death or BSOD (Blue Screen of Death) has been seen by almost every Windows user. Its appearance indicates a critical failure in hardware or software and is accompanied by a reboot of the operating system with the loss of all unsaved data. It's hard to imagine how many nerve cells this error killed, especially in the days of Windows 2000 and XP. Now the screen of death does not appear so often, but you need to deal with the problem immediately. The main thing is to find out the cause of the disease and prescribe the right course of treatment.

What is BSoD?

In simplified terms, Windows architecture consists of two layers - user and kernel mode. The first runs applications and services, and the second runs OS and driver code. BSOD occurs when a critical error is detected in kernel mode. Both drivers and PC hardware can fail. As a result, the system urgently stops its work and displays information about the error - the notorious screen of death. All unsaved data is lost.

Some time after the BSOD appears, the computer automatically restarts. This often happens too quickly, and the user does not have time to remember the error code. In this case, it is enough to disable automatic loading of the OS. After rebooting, the system will continue to work, however, if the cause of the failure is not eliminated, then BSOD will appear again and again. The error information is written to a memory dump file with a ".dmp" extension and, by default, is added to the folder at "C: \ Windows \ Minidump".

In addition to the classic blue screen, sometimes there is green screen of death ... In fact, this error is identical to the standard BSOD, but only appears on test versions of Windows 10 starting in 2016. This separation allows you to quickly understand which version (test or release) crashed.

One of the test versions of Windows Vista, known as Longhorn, sometimes showed users red screen of death ... The problem was the download manager crashing. In addition, the red background was used to notify the ACPI error in Windows 98.

It should be borne in mind that the color of the screen of death can change to any other due to an accidental re-filling of the display after a video card driver failure.

The main reasons for the emergence of BSoD

The death screen occurs due to errors in the execution of code in kernel mode. This can be caused by problems in the hardware (hardware) or software failures:

  • failure of the hardware;
  • conflict of connected devices / drivers;
  • overheating of the video card or processor;
  • overclocking of components;
  • incompatibility of the device / driver with the OS;
  • infecting your computer with a virus;
  • inappropriate or incorrectly installed driver;
  • insufficient amount of free disk space;
  • problems in the RAM module;
  • incorrect BIOS settings;
  • Windows update;
  • file system errors.

Most often BSOD appears due to incorrect operation of the driver of one of the connected devices. To improve system reliability, use only the latest official versions of drivers and software.

How to find out the BSoD error code?

In order to find out the reason for the failure, you need an error code. The data is shown directly on the screen of death at the time of its appearance, recorded in the Windows log and saved in a special file.

In the first case, it is necessary to carefully consider information on the display. The appearance of the screens of death depends on the version of the OS. In the case of Windows XP and 7, a large amount of data is displayed with the name and error parameters, as well as recommendations for its elimination.

Starting with Windows 8, the user sees only a sad smile, a brief description of the error and the QR code with reference to the solution of the problem from Microsoft.

If you have not remembered the error code immediately after the appearance of BSOD, you can find it using a Windows log. To do this, go to the "Control Panel" chain - "Administration" - "View Events" - "System". Focusing on the date and time of failure, click on the appropriate entry in the journal. The description will indicate the code and the name of the error, for example, hexadecimal code 0x00000001 corresponds to an APC_INDEX_MISMATCH error.

By default, error information is saved in the memory dump. To view it, a special utility will be required, for example, a free BlueScreenView program. At the top of the main window displays a list of memory dumps, from the installation of the OS. The table indicates the report formation time, error code, parameters and driver, which most likely led to the appearance of BSOD. The bottom of the screen provides a list of drivers, while the reds are noted by those that were active at the time of the failure.

BSOD error when loading / installed OS

Blue screen can appear directly when installing the operating system. The reason most often serves:

  • defective image file;
  • Problems with hardware;
  • Incorrect BIOS setup.

If you are sure that the iron is in order, the image of the operating system is most likely damaged. Try not to use pirate builds with non-standard settings and pre-installed programs.

In some cases, OS constantly goes into a reboot without the appearance of a graphical interface. Most likely the reason for damage or incorrect formatting of the hard disk, as well as the incorrect BIOS parameters. Reset BIOS to default settings can be one of two ways:

  • BIOS SETUP. To start the utility, press the Delete key during the initial computer testing and go to the settings. Activate the option "Load Optimal Defaults" - the name may differ in various versions of the BIOS.
  • Closing contacts on the board. Disable the power of the computer and open the housing cover. On the motherboard, find a jumper with a margin of CMOS or BIOS Reset (the signature depends on the board model). If you are two contacts, then closed them once. In the case of 3 contact jumpers, it will be necessary to rearrange the external cap from 1-2 contacts at position 2-3. Leave the fee in this state for 15-20 seconds and return the cap to its original position.

You can use the secure mode to load the OS. In this case, the system uses only the most necessary drivers. If the problem is not in them, it will be possible to correct the error.

Elimination bsod.

If you know the error code, you can find the instructions for eliminating on the Internet, for example, on this site. Starting with Windows 8, a QR code is displayed on the death screen with reference to the troubleshooting method from Microsoft.

To restore a stable PC mode, you can use universal methods. If you apply the whole range of measures, this is likely to correct the error, will speed up the system speed and will prolong the service life of the components:

  • Remove dust from your computer. It is advisable to lubricate all mechanisms of the serviced fans with a special oil.
  • Find out the temperature of the processor / video card in normal and loaded modes. If components overheat, add additional fans to the chassis or reorganize the cooling system.
  • Check if there is free space on the disk. If it is not enough, delete unnecessary files and uninstall unused software.
  • Scan your OS with a reliable anti-virus program. If dangerous objects are found, delete them. In some cases, the antivirus itself may be the cause of the failure.
  • If the error appeared not so long ago, then use the System Restore Wizard and download the latest stable version.
  • Install the latest official system service pack (Service Pack). It is recommended to enable automatic Windows updates.
  • If the error appeared after installing a certain program, then reinstall it by downloading it from the official website.
  • If a failure occurs after connecting a specific device, then check it for compatibility with your OS version. Download the new driver from the manufacturer's website. If the driver is fresh, then roll it back to the previous version.
  • Reset BIOS to default settings using one of the methods described above.
  • Check the RAM for errors in a specialized application like memtest86 +. If a damaged memory strip is found, the strip will have to be replaced.
  • Check your hard drive with built-in diagnostics or third-party software. Repair broken sectors.

If none of the above helped, then reinstall the operating system using the licensed image.

Today we will tell you what the Windows 7 blue screen of death is, what to do when it appears. We often see this phenomenon when a computer suddenly decides to arbitrarily reboot. Windows 7 Blue Screen of Death gives error codes along with many obscure labels. Knowing the meaning of the basic codes will help to eliminate the problem with the greatest efficiency. If we see a blue screen, this means that the operating system cannot correct the situation on its own. The appearance of the screen ends with a reboot, and all unsaved data is often lost. The main reasons for this phenomenon: software error, problems with the hardware elements of the PC.

Reasons for the appearance of BSOD - screen of death

Windows 7 Blue Screen of Death occurs due to malfunctions in individual devices of the computer system or errors in the drivers responsible for supporting these devices. BSOD in some cases occurs due to a failure in the kernel of the operating system, it is usually called low-level software.

Windows 7 screen of death errors cannot be caused by problems in individual applications that are not part of the operating system. In such cases, the OS operates normally. System kernel mode and user mode are separate. If Windows finds a STOP error, a Blue Screen occurs. This situation stops the operation of the operating system.

At the same time, it is the "Screen of Death" that is a protective mechanism for Windows. In order to understand how this works, you can take the human body as an example. If the pain is too strong, the person loses consciousness in order not to die of shock. Blue Screen works in a similar way.

If an incorrect code is detected, Windows will shut down, providing us with information about the problem in the form of a code on the screen. Then the user can only restart the computer, or turn it off for a while.

Applications in such circumstances do not have the means and time to save information, so some of the data may be irretrievably lost. Only those applications that automatically and regularly save changes are insured against losses.

When a crash of interest appears on the screen, Windows automatically creates a special file into which data from the physical memory of the system is entered. This is where the error data is stored. Looking into this file, you can even after a while find out what caused the failure and protect yourself from its repetition.

How to understand that BSOD is in front of you

Unfortunately, few users can boast that they have never seen the "Blue Screen". In the Windows 7 operating system, BSOD is in the form of a blue screen, with a lot of strange codes and white text. In Windows 8 and 10, it has been greatly simplified, in these versions of the system you can see a sad smile, an error code and the actual message that there was a problem.

Probably, Microsoft decided not to scare users with cryptic ciphers. Blue screen is a phenomenon known to users of very early versions of Windows. Curiously, in 2016, users were shown the green screen of death for the first time.

In this case, we are talking about the same phenomenon, but at that time Microsoft was testing the new Windows 10 system, the color change allowed developers to more quickly track errors, respond to them and quickly fix them.

Restart Windows with BSOD

When a critical error or Blue Screen appears, Windows often restarts on its own. In such circumstances, you may not have time to get acquainted with the error code and remain in the dark about the reasons for the failure. At this point, users often panic the most.

But as we said above, Windows stores all error data in a separate file, which is often forgotten even by experienced users. In this case, diagnostics can be facilitated even more if you prohibit the system in advance without permission to reboot. This possibility is provided in the "Control Panel".

Algorithm of actions:

  • We open "Explorer".
  • Click on "This computer" with a "right click" and select the "Properties" item in the menu that appears.
  • Open "Additional system properties".
  • In the small window that appears, use the "Advanced" tab.
  • We apply the option "Download and Restore".
  • Go to "Options".
  • Click on "System Failure".
  • Uncheck the box "Perform automatic restart".

Performing these actions in advance will allow you to get time to familiarize yourself with the information presented on the blue screen and write down the error code separately. After that, you can restart your computer yourself.

Diagnostics - how to find out why the screen of death appeared

Windows 7 blue screen of death - how to view events

Download BlueScreenView

It is not easy to determine the causes of the failure using the operating system tools, but the BlueScreenView program will help us. This application scans the error data files by itself and shows more detailed information about the crashes.

The classic Event Viewer tool theoretically allows you to get similar information, but in this case it will be displayed along with information from the system log and messages about application crashes. BlueScreenView receives information about all death screens that have occurred in the system.

Here you can see many useful information about failure, among other things:

  • Driver that caused a mistake.
  • An error description.
  • Error code.
  • Time and date of error.

Let's call the main causes of "blue screen":

  • Most often, the problem lies in the driver malfunction of one of the computer system devices.
  • The breakage of the PC component, such, for example, can be a video card or RAM.
  • Incorrect acceleration of RAM or processor.
  • BIOS is configured with errors.
  • Incompatible equipment, conflict of individual PC components.
  • The computer overheats.
  • There are viruses in the system.

Experienced users and developers can apply a more complex tool from Microsoft called WinDBG.

Error codes


This code may appear if there are difficulties with the compositebus.sys driver. When the portable or multimedia device is first connected to a PC, it sets the driver, and the USB is reset. Error causes simultaneous appeal to Compositebus.sys . If you try to install a third-party driver, a similar failure may occur.


The device queue was not busy. The problem lies in drivers or hardware. To correct the position, you need to update the drivers. Also, the computer needs checking for viruses. The registry will have to be cleaned. Hard disk Check for errors will also be useful. If this does not help, update the operating system to the current version.


Error is also caused by problems in drivers or hardware environments. The algorithm of correction is already familiar to us: check the hard disk for the presence of failures, clean the registry, looking for viruses, eliminate them, update the drivers. If all this turned out to be useless, load and installed on your computer the current version of the Windows operating system.


This code indicates an exceptional invalid situation with access to data. The cause of the failure can be the hardware part of the PC or device drivers. The recipe is already familiar to us: we clean the registry from all extra, eliminate viruses, update the versions of the drivers. If this did not help, you will have to go to a more modern operating system.


This failure is associated with encoding error in the element. Http.sys . The operating system will have to update so that the position is not repeated. This error occurs when the driver appeals to the function KeattachProcess. However, if the flow is busy with another process, a problem arises. Using a function KestackatTachProcess. It may become more efficient in this position.


This error is also associated with KeattachProcess. . Here will also help the transition to the function KestackatTachProcess. . Among other possible reasons for this failure: breakage in the power supply, failure of memory, overheating. It is necessary to check the power of the power supply, test the hard drive and make sure that there are no viruses in the system. If this does not help, update the operating system.

All About the Blue Screen of Death in Windows 7

The seventh version of the Windows family version is the most stable and reliable of all OS developed by Microsoft, but despite this, and there are sometimes errors in it. When critical failures occur, a blue screen appears in which the problem code is specified.

Sometimes such a problem occurs only once and after restarting the system disappears, but if it has taken a permanent nature, then it should be understood. In this extensive article, we will describe because of which such an error appears, which means its codes, and to which methods can be resorted to solve the problem.

What is this error

BSoD - aka blue screen - is an abbreviation of the English name - Blue Screen of Death, which literally translates as "Blue Screen of Death". This notification informs about a fatal failure, after which further operation of the OS is impossible and a reboot occurs.

Error codes and their decoding

After a fatal failure has occurred in the system, a message will appear indicating the error number and the name of the file that caused it. In some cases, there may be several such files.

For example, the fault number 0x00000010 SPIN_LOCK_NOT_OWNED indicates a problem with the hard drive, and 0x0000001A MEMORY_MANAGEMENT reports a critical failure in the computer's memory.

There are a large number of such codes in total, and by themselves they give only minimal information about the problem. To fix the problem, you need to pay attention to the name of the file that caused it. Having learned that it belongs to the operating system or to the software of the devices, we will be able to resort to the appropriate way to eliminate the error in the future.

Blue screen reasons

All BSoD errors can be divided into two categories:

  1. Software crashes - problems with Windows components, installed drivers and applications, or lack of free space on the system partition of the disk.
  2. Hardware problems - for example, a video card, hard drives, RAM, power supply, as well as in case of overheating of the processor or other components.

Determining the cause of the failure and how to fix the error

Troubleshooting options for critical Windows errors depend on what caused them. In some cases, the PC immediately restarts and does not allow reading the code, as well as seeing the name of the file that caused the error. To disable the reboot and see the information we need, we will perform the following operations:

  1. Go to "Properties" computer from the desktop or from the start menu.
Go to computer properties
Go to computer properties

2. Next, click on the link "Additional system parameters" .

Additional parameters item in computer properties
Additional parameters item in computer properties

3. Open the tab "Additionally" .

4. Click on the button "Options" .

Boot and recovery options on the Advanced tab.
Boot and recovery options on the Advanced tab.

5. In a group "System failure" remove the bird next to the item "Perform automatic reboot" .

6. In paragraph "Writing debug information" select the option from the drop-down list "Small memory dump" ... This will allow you to view information about the failure in the future using a special application.

7. Save the adjusted settings by clicking on the button "OK" .

We set the necessary parameters so that the computer does not restart after an error
We set the necessary parameters so that the computer does not restart after an error

After the performed operations, the system will stop automatically turning off when an error occurs and it will be possible to get the information we need.

Now, if, in addition to the code on the screen, there is the name of the file that caused the error, it will be possible to understand the cause of the problem. In our example, in the screenshot, a failure occurred in the file EPUSBSDK.sys .

An example of a blue screen showing the file that caused the crash
An example of a blue screen showing the file that caused the crash

By typing the name of the file into the search engine, we find out that it belongs to the product EPSON PCMCIA Reader, and this indicates a problem with the connection of the EPSON printer via the USB interface. Accordingly, in order to eliminate the error, you will need to reinstall the drivers for this device. Other similar problems are eliminated in the same way.

But what if the name of the file that caused the crash is not specified? In order to find out the cause of the error in such cases, we can use the Windows system log. To do this, we will perform the following operations:

  1. We open "Control Panel" from the system start menu.
"Control Panel" item in the start menu
"Control Panel" item in the start menu

2. Next, go to the section "Administration" .

Section "Administration" in the control panel
Section "Administration" in the control panel

3. In the window that appears, click on the item Event Viewer .

Open "Event Viewer" from the "Administration" section
Open "Event Viewer" from the "Administration" section

4. In the application that opens, go to the folder Windows Logs and select the section "System" .

5. Now, on the right side, you can find an error, highlighting which, its description will be displayed below

An example of a description of a critical system error in the Windows log
An example of a description of a critical system error in the Windows log

In addition to the log built into the system, you can also use the third-party Blue Screen View application to decrypt memory dumps.

Download Blue Screen View from Official Website

After downloading and installing the program, run it. A window will appear on the screen, divided into two parts. Dump files with errors and the time of their occurrence will be shown at the top. At the bottom you can see which file caused the problem and its description.

Checked files caused a critical system crash
Checked files caused a critical system crash

Having found out the culprit of the error, we can take the appropriate action, as described earlier.

In the BlueScreenView program, if necessary, you can save the report and send it to the specialist. To do this, right-click on the dump file and select the option “ HTML-report - Selected Items " .

The item in the context menu of the dump for saving the report
The item in the context menu of the dump for saving the report

In addition, in the same menu, you can search for information about an error in a Google search engine directly from the application.

An item in the context menu of a dump to search for information about an error in Google
An item in the context menu of a dump to search for information about an error in Google

In most cases, failures occur when the drivers of certain components are running, and the problem is solved by reinstalling them. If the problem is caused by a file of a third-party program, then you can simply delete it. For a complete uninstallation of applications, it is better to use special programs that completely clean the system of files, and also erase unnecessary information from the registry.

Checking system files

If by reinstalling the driver it was not possible to resolve the error or it was caused by a failure in the system itself, then you can try to check the Windows files for their integrity. This operation is recommended to be performed by booting the computer in safe mode. To start scanning, do the following:

  1. Reboot the system and periodically press the key before turning it on "F8" .
  2. Boot into safe mode, open a window "Run" and enter the command there cmd .
Open the command line from the Run menu
Open the command line from the Run menu

3. Click on the button "OK" .

4. After that, in the window that appears, enter the command sfc / scannow and press "Enter" on keyboard.

Run the system file checker using the sfc / scannow command
Run the system file checker using the sfc / scannow command

The procedure for checking system files will begin, and if errors are detected, they will be automatically corrected. Sometimes during the operation, the system may ask for the Windows installation disc - you just need to insert it into the drive and the application will automatically continue its work.

System Disk Cleanup

Often, a blue screen can appear due to the fact that there is simply not enough free space on the system drive. To see how much of it is left in the Windows partition and clean up unnecessary files, do the following:

  1. We open "A computer" using the icon on the desktop or from the system start menu.

2. Choosing a hard drive С, on which the system is installed by default and from its context menu we go to "Properties" .

Go to the properties of the C drive
Go to the properties of the C drive

For the normal functioning of Windows 7, you need to have at least 2-3 gigabytes of free space.

3. In the window that appears, you can see how much free space is available and clean up the disk by clicking on the corresponding button.

Open disk C cleanup from its properties
Open disk C cleanup from its properties

4. Having started the procedure, mark all the items in the settings window and click on the button "OK" .

We set the parameters for cleaning the disk
We set the parameters for cleaning the disk

The process of deleting unnecessary files will begin, after which it will be possible to see how much free space was obtained as a result of cleaning.

Removing incorrectly functioning updates

If you recently installed an update and after that a blue screen began to appear, then it will not be difficult to remove it. This is done in almost the same way as in the case of uninstalling regular programs. You will need to do the following steps:

  1. We open "Control Panel" from the Windows start menu.
Go to the "Control Panel" from the start menu of the system
Go to the "Control Panel" from the start menu of the system

2. Go to the section "Programs and Features" .

Open the "Programs and Features" section in the control panel
Open the "Programs and Features" section in the control panel

3. Click on the link "View installed updates" .

Go to the section for viewing installed updates
Go to the section for viewing installed updates

4. In the list that opens, delete the recently installed update using the corresponding button.

Removing the crashing update
Removing the crashing update

Having memorized the update number, you can skip it during the next system update.

Checking disks for errors

In some cases, hard disk errors can be the cause of a critical failure. To check the media and fix the problem, we will do the following:

  1. Let's open "A computer" using the icon on the desktop or using the start menu of the system.
  2. Next, go to "Properties" system disk by selecting the appropriate item in the context menu.
Go to the properties of the C drive
Go to the properties of the C drive

3. Open the tab "Service" and click on the button "Checkout" .

Run disk check on the "Service" tab
Run disk check on the "Service" tab

4. In the window that appears, put a check in both checkboxes of the scan settings.

5. Click on the button "Launch" .

We set the parameters for checking the disk and start the operation
We set the parameters for checking the disk and start the operation

Scanning of the media will begin and errors will be corrected automatically if errors are found.

Problems with device drivers

A fatal crash can also occur if the driver files are corrupted or in conflict. You can check that the hardware is functioning properly using the Windows Device Manager. To do this, we will perform the following operations:

  1. Opening the menu "Run" by pressing the keyboard shortcut "Win + R" .
  2. Next, enter the command in the line devmgmt.msc (you can also open the dispatcher from the corresponding point in "Control panels" ).
Launch Device Manager from the Run menu
Launch Device Manager from the Run menu

Problematic devices in the parts list will be indicated by a yellow triangle with an exclamation mark.

An example of the designation of an incorrectly functioning device
An example of the designation of an incorrectly functioning device

To fix the problem, we need to uninstall the driver and reinstall it. To do this, let's do the following:

  1. Right-click on the line with the device name and select the option from the context menu "Delete" .
Removing the problem device from the system
Removing the problem device from the system

2. Confirm our action by clicking on the button "OK" .

3. After the device disappears from the list, open the menu "Act" and click on the item "Update hardware configuration" .

We update the system configuration in the manager
We update the system configuration in the manager

The computer will detect the new device and automatically install the driver for it. If this does not happen, then you will need to download the driver installation package from the equipment manufacturer's website and install it.

RAM problems

A blue screen can also appear due to problems with the computer's RAM. To diagnose it, you can use the special application Memtest86 +.

Download Memtest86 + from the official website

This program does not work in the Windows environment - you need to boot your computer using a flash drive. To create it, we will do the following operations:

  1. After downloading the application, launch it and specify the drive letter with the flash drive.
  2. Click on the button "Create" .
Create a bootable disk using Memtest86 +
Create a bootable disk using Memtest86 +

Now we need to boot the computer using the created flash drive, setting the appropriate settings in the BIOS of the system. Having done this, an application window will appear on the screen, where, in the case of using the trial version of the program, you will need to click on the number "1" to start automatic memory testing with default settings. At the end of the check, the program will display the result, and if there are errors, they will be highlighted in red.

An example of RAM errors in the Memtest86 + program
An example of RAM errors in the Memtest86 + program

In most cases, you can fix the problem with RAM only by purchasing a new stick of RAM.

Scan the system for viruses

Certain viruses can also cause critical crashes. In this case, it will be easiest to use special portable scanners to check your computer. We can recommend the anti-virus application Dr. Web CureIt!

Launching a system scan for viruses using Dr. Web CureIt!
Launching a system scan for viruses using Dr. Web CureIt!

Download Cureit from the official site

or a similar program from Kaspersky.

Button for starting a system scan for viruses using Kaspersky Virus Removal Tool
Button for starting a system scan for viruses using Kaspersky Virus Removal Tool

Download Kaspersky Virus Removal Tool Both scanners are distributed free of charge, and a computer scan is launched with one click on the corresponding button. This procedure is best done by booting Windows in Safe Mode by pressing the key "F8" before starting the system.


Critical crashes usually occur due to problems with the component drivers and disappear after reinstalling them. It is recommended to download the driver installation package from the manufacturer's official website.

In addition to the methods of solving the problem described in the article, it is also necessary to clean the system unit from dust and reconnect all the cords by checking the connector pins. At first glance, this may seem strange, but due to contamination of the system unit, critical errors can also occur.

Author of the material: Viktor Zverev
Subscribe to our channel and like it! You can also visit our official site .

Recently, the Microsoft team continues to demonstrate not the best achievements in the field of security, since almost every update for the Windows platform is fraught with serious bugs with the prospect of rolling back to the previous version, which, in principle, is unacceptable for such popular products. At the same time, older versions of the operating system are not immune to all kinds of problems. Even when it comes to the beloved by many "seven".

Danger and meaning of the blue screen of death in Windows 7

One of these glitches has received the frightening name "Blue Screen of Death" or BSOD, since the bug is literally translated into English as Blue Screen of Death. Most of the error occurs on such ancient versions of the platform as XP, 7 and more recent, but by no means the most up-to-date G8. The very problem of the occurrence of such a phenomenon as a blue screen can be triggered by various factors, from software or system conflicts to banal overheating of the PC hardware system.

Simply put, this time the developers' fault is not so much, perhaps the smallest, because it was possible to make the operating system not so pampered. It's another matter that her potential opportunities are not the same as compared to the same top ten. The seriousness of the situation is added by the fact that the bug is not so much a system bug as a hardware bug, being caused by a kernel error or a so-called stop error, which makes the further functioning of the OS impossible by definition.

Death screen

That is, there is a real paralysis of all operations, displayed in the form of a frightening bright blue screen. And, of course, it will be impossible to correct the situation using the usual tools. And to be inactive, waiting for the weather from the sea, most often does not make sense. Although it is not uncommon for a BSOD to appear only for a while, after which an automatic reboot of the system occurs, followed by recovery.

Causes of BSOD problem

Even if the automatic recovery did not happen, there are not many reasons for panic, since the Blue Screen paralyzing PC is a reversible process. But before proceeding to rectify the situation that has arisen, it makes sense to analyze the root cause that provoked its development. After all, if the conditioned stimulus is not eliminated, then the problem can come back again and again, giving the user a lot of trouble.

So, among the main factors that lead to the occurrence of BSOD, it is worth highlighting:

  1. Driver problem. You should refer to the system installer when a failure occurs immediately after using a new driver on a PC or updating its current version. In such cases, it makes sense to play everything back by restoring the previously used installer.
  2. Failed to update the operating system. Yes, yes, an unsuccessful Windows update can also make the screen "blue" by decorating it with a sad emoticon. And here it is already worth "to say hello" to the developers of the next "raw" assembly, the patches of which often turn out to be frankly low-quality, and sometimes potentially dangerous. As for further actions, by analogy with problem drivers, the user will have no choice but to roll back the installed OS version to the previous one. Blue window
  3. Errors in the operation of the device. Quite often, the fault is the incorrect functioning of the equipment itself, which can be checked through a special stress test. To do this, you can use the appropriate software such as "AIDA64" and its most famous analogues. It will not hurt to test the PC's RAM, as well as the operation of its disk media.
  4. Reset the current BIOS settings. If the user suddenly decides to change the operating mode of the drive, then in this case the prospect of a stop error becomes more than real. Parameters fail due to a dead BIOS battery, which must also be taken into account in advance.
  5. Virus software. All kinds of malicious software can also provoke such problems, so it is possible and necessary to arrange regular PC checks using special antivirus software.
  6. Software conflicts. Another reason for BSOD is the incompatibility of the software used on the PC. It makes sense to suspect this reason when the display turns blue immediately after installing a new application or updating some program previously used on the device.

    It is noteworthy that such problems are solved quite simply - by rolling back to the previous installation versions of the problematic software.

  7. Violation of the license. If the screen “turns blue” every couple of hours, then there is a non-activated version of Windows OS exploitation.
  8. There is no point in talking about the dangers of using pirated versions of Windows. Every user who deliberately installs unlicensed copies of software on his computer must be prepared for problems and more serious than the "screen of death".
  9. Overheating or any other problem with the graphics card. Most often, such a development of events can be observed by active gamers or those users who view and edit a lot of videos. And again, diagnostics involves the use of a stress test, as well as taking into account the temperature parameters of the graphic editor.

As you can see, there are quite a few potential errors, and almost any of them can happen to any device. That is why you should not lose your vigilance, armed with all the necessary knowledge to fix the BSOD problem should it arise.

How to find out the error code in Windows 7

The only correct algorithm on the way to solving a sudden problem is to accurately identify the error, without which its further elimination becomes impossible. To do this, you must disable the option to automatically reboot the system by going to the path: "PC Properties - Additional parameters - Boot and recovery", deactivating the current state of the PC OS.

Error code

Next, you need to identify the code itself by reading it immediately after the STOP command on a blue background (relevant for the "seven", XP and older versions) or read the highlighted failure QR code, which is most often issued on the "eight". The next stage involves decoding the error using specialized resources such as and or by entering the code itself into any browser search engine.

Most common codes

Of course, there are many reasons for the failure, as well as the errors themselves. But, as practice shows, most often you can observe three main bugs. Fortunately, today they have all been deciphered in detail. Therefore, eliminating them should not have any problems even for the most advanced user.


This error is called MEMORY_MANAGEMENT. And from the name alone it becomes clear that it is directly related to a serious failure in memory management. In this case, the solution to the problem will directly depend on which version of the operating system was installed on the PC.



INACCESSIBLE_BOOT_DEVICE most often occurs during the installation of an I / O system due to the inability to initialize the device by drivers or as a result of various failures in the file system. It also happens that an error pops up due to the fact that the system is installed on a hard disk or a SCSI controller that is unable to support it. The installation of the latest adapters is also capable of provoking such bugs, to fix which it makes sense to edit BOOT.INI (relevant for x86 architectures) or run Setup if you happen to work with ARC systems.


PAGE_FAULT_IN_NONPAGED_AREA - an error indicating the absence of a page in the used address space, which clearly indicates an erroneous address in memory. Such a failure also occurs when the USB drivers function incorrectly, as well as when the computer system is infected with the HaxDoor virus software.


How to fix the problem

Elimination of such errors does not imply any super-difficult manipulations to perform. And if desired, it is quite possible to cope with the task at hand even without the help of a specialist.

Despite the fact that the listed bugs are of different nature and reasons, the algorithm for solving them lies in the same plane, implying the following steps:

  • updating driver installations;
  • unscheduled update of the current OS version;
  • anti-virus scanning;
  • checking SSD for errors;
  • memory check.

Usually, these manipulations are more than enough to get rid of BSOD. However, a successful solution to one problem is not a cause for optimism. There are a lot of system errors, and each of them can happen at any time, being provoked by the slightest malfunction of the device, for which you must be prepared.


Blue screen of death. Windows error codes

Any ordinary PC user, at least once in his life, has heard about "blue screen of death" , it is also called BSoD ... And he even managed to catch some by surprise. This phenomenon, which has become synonymous with computer failure, with which inexperienced users are often frightened, in fact, this phenomenon is not as terrible as it might seem to you at first glance. What is it? Why does the blue screen of death occur? Today we will talk about this and you will find out what can lead to it and how to cope with this scourge.

What is this error?

We can say that in this way the operating system reports the occurrence of a fatal error. But it does not just inform, but indicates what specific error occurred and possible ways to solve it. As you can see, this is a very useful thing. And it is useful not only for the information that it carries, but also for the timely stopping of all processes on the computer, which simply stops its activity. This function allows you to save the OS system files from damage and distortion, and also saves all your equipment from failure.

Quite often, this error can be cured by simply restarting the computer. After all, it could be caused by incorrectly processed files, or incorrectly transmitted packets, inside the local network. But if it happens that a fatal error appears regularly and no reboot has been able to get rid of it, then the problems can be more serious. Most likely, this will come from the hardware: possible damage to drivers, RAM modules, violation of the file system, and even failure of the hard disk.

But nevertheless, this or that problem will not remain a mystery to us, because the system will certainly tell us where to heal it. We can learn about this or that type of fatal error through special Windows error codes which the blue screen displays to us, namely the first two lines. For example, a message like this may appear:

STOP 0x0000006B (0xC0000022, 0x00000000, 0x00000000, 0x00000000) PROCESS1_INITIALIZATION_FAILED

Where: 0x00000000 - codes that determine the nature of this error in BSoD.

It is important to keep in mind that the BSoD display function may be disabled in your OS. In this case, when critical problems or errors appear, the computer will reboot, and you will never be able to find out what caused this. This will be especially problematic if the computer starts to restart every time soon after turning on. Therefore, it is recommended to disable automatic reboot. To do this, in the "My Computer" properties, go to the additional settings tab. Then we find the parameters button in the download and restore field, click it and in the window that opened, remove the "check box" from the "Perform automatic restart" item.

Causes of BSoD

They can be divided into two groups. The first group is the emergence of BSoD due to the installation of any software. The second group - Malfunctions of a personal computer of a software or physical nature.

Group A:

  • Adding new equipment to the already installed one. This can be a hard drive, video card, RAM, etc.
  • Installing Windows updates;
  • Updating existing drivers.

Group B:

  • Breakdown of one of the elements of the computer (RAM, power supply, video card, hard drive, etc.);
  • Some devices are in contact. An example would be a hard drive cable getting caught in a cooler blade;
  • Excessive overheating of the processor;
  • Mismatch of the driver for a specific device;
  • Driver conflict;
  • Small amount of free space on the hard drive;
  • The result of overclocking the performance of RAM or processor;
  • Incorrect BIOS firmware.

There are times when after several reboots the BSoD problem disappears by itself. In this case, you can ignore it and not take any action. But this applies only to those computers on which a pirated version of Windows is installed. Pirate builds imply a large number of all kinds of bugs. It is they who can cause the appearance of BSoD for no good reason.

Sometimes the blue screen of death appears a few seconds after the computer freezes. In this case, it is necessary to determine the origins of the problem. First of all, you need to disable automatic restart of the operating system when critical errors occur in the operating system. What can this give? The first step is to start Windows in Safe Mode. Next, you need to do the following:

For computers with Window XP installed:

Hover the cursor over "My Computer" and click on the right mouse button. In the menu that appears, select the "Properties" item. The panel opens. On its left side is "System Protection". Click. Then go to the "Advanced" tab and open the "Parameters" subgroup. Here you need to uncheck the box next to the "Perform automatic reboot" item. You also need to enable writing small memory dumps. This is done in the "Recording debug information" group. From the list we need to select "Small memory dump".

Zagruzka-i-vosstanovlenie-XPFor computers with Windows 7 or Vista:

We open "My Computer". At the top, select "Properties", go to the "Advanced" tab. We are interested in the Boot and Recovery subgroup. This subgroup contains the "Parameters" item. In the window that appears, uncheck the "Perform automatic reboot" checkbox and turn off the recording of small dumps (done in the same way as in the Windows XP operating system). Zagruzka-i-vosstanovlenie-Vista-7After that, you need to restart your computer.

After restarting your computer, you will be able to see the error code. Better to write it down on a piece of paper. To check the code, we use the resource .

To determine the driver that causes the blue screen of death to appear, we need the Blue Screen View program. Following the link , you can download this utility and read the instructions for its use.

blue screen of deathAfter that, using search engines, we find the problem driver on the Internet. If the driver is responsible for the correct operation of the video card, then it needs to be updated or rolled back to the previous version. If the BSoD is caused by a sound driver, network card or motherboard driver, then it must be updated or installed to a later version.

If this approach did not give results, then you need to remember the name of the driver. The table below shows the names of the drivers and their corresponding error codes. It can be used to identify the program or device to which the driver belongs. This will identify the specific program or device whose driver is causing Windows to crash. If the driver belongs to the software, it must be reinstalled. This might help fix the problem. If reinstallation did not help, then the program must be removed. It is better to install a similar but more stable utility instead. If the driver is part of the PC system, then it needs to be updated. Often the problem can be resolved by rolling back to a later version of the driver. That's probably all.

Windows error codesAll of the above allows you to solve the problem of BSoD occurrence. Now we can summarize.

What should be done to avoid future BSoDs?

The following guidelines must be followed:

  1. You should always make sure that the system partition of the HDD has free space. If there is no free space, you need to delete some data immediately. The personal computer must always be clean. Check it regularly with an antivirus to avoid the accumulation of any rubbish. sinij-jekran-smerti-kody-oshibok
  2. Update your operating system regularly. This must be done exclusively from the official Microsoft server. All new updates are aimed at eliminating "holes" in the system.
  3. If a BSoD appears due to the installation of a new version of the driver, it must be rolled back to a later version, which is more stable. To eliminate BSoD after installing the program, only its complete removal from the system will help. sinij-jekran-smerti-kak-ispravit
  4. In some cases, BSoD appears after connecting a new device to the computer. This indicates that it is incompatible with this version of the operating system. Installing the hardware driver downloaded from the official website of the manufacturer will help to solve this problem.
  5. BIOS settings should be standard. Incorrect settings affect the correct operation of the system. Moreover, BSoD is not the worst threat. It is better to entrust BIOS setup to professionals. It is not recommended for a beginner to climb there.
  6. Also BSoD can appear when the RAM fails. You can download several programs on the Internet to test it. If a malfunction is found, the strip must be replaced.
  7. Problems can also arise due to the presence of errors or bad sectors in the hard disk. You can try to eliminate errors and restore sectors using the standard tools built into the OS. sinij-jekran-smerti-kody-oshibok
  8. Care should be taken to ensure that the components of the computer do not overheat. To do this, the system unit must be regularly cleaned from dust and lubricated by the cooler. The overheating problem can be solved by installing an additional cooler.
  9. Cables and accessories must be connected correctly.
  10. The most extreme case is reinstalling Windows. You need to use only licensed software.

In addition to the causes of problems, the blue screen also informs about possible solutions. I would like to note that the most common cause of the "screen of death" is a variety of hardware problems. There is usually something wrong with your hardware, or programs that directly interact with it.

Consider all Blue Screen of Death errors

You can press the keyboard shortcut right now Ctrl + F , and in the search bar that appears, start entering the error code that you have. This is a page search, if a description of your error is on this page, then you will see it.

An error that occurred in the very kernel of the installed operating system. You need to make sure that you have the drivers installed and they work correctly. The reason is also likely due to a lack of RAM: RAM or hard drive.

Incorrect processing of data in virtual memory associated with the IRQ process. Most likely, one of the drivers is not working properly. You should reinstall the drivers. Sometimes an error can occur due to hardware malfunction, but this is very rare. Possible error parameters: 1 - incorrect address access; 2 - the IRQL process through which the memory was accessed; 3 - how exactly the process accessed memory: 0 - read was performed; 1-memory write was performed; 4 is the instruction that performed the memory request.

Quite a common case. Typically, the error code can point to the specific driver or function that caused the fatal error. Therefore, you should always pay attention, in addition to the driver name, to the address that contains the error. This will most often look like an exception code 0x80000003. What will mean the initialization of the handler at the time of accessing memory and loading the system with the / NODEBUG key. This error cannot appear all the time. If this happens, you need to make sure that the debugger is connected and the system boots from the / DEBUG key. If you have a non-Intel system, then the address will look like this: 0XBFC0304. Such an exception address would indicate that the error was caused by processor caching. If this error persists, you should contact your processor manufacturer for help. Possible parameters: 1 - positive situation; 2 - address where the failure occurred; 3 - Parameter 0 - exception; 4 - Parameter 1 is an exception.

From this line you can see that the error is related to the APC counter. With this error, it is worth checking every file system on your computer (everything that is), for example, using the EMRD kit. It is necessary that the current IRQL is equal to zero. If this is not the case, then a certain sequence of unloading drivers may be violated, leading to an error and a "blue screen". Remember what driver was last installed on the PC. This error may be related to a serious driver problem. Three error parameters: 1 - address at the time of failure; 2 - failed APC thread; 3 - current IRQ level.

Failed to process data on the hard disk in the FAT format partition. There may be damage to the file system, incorrect reading or writing, the presence of "bad" sectors on the disk. Some programs that work with partitions and file systems can lead to this error.

Failure to process data on a hard disk in an NTFS formatted partition. There may be damage to the file system, incorrect reading or writing, the presence of "bad" sectors on the disk. Some programs that work with partitions and file systems can lead to this error.

I / O Request Packet (IRP) failure. This happens when the fields are filled incorrectly compared to the saved state of the IRP. For example, disabling the IRP while the driver is waiting for a command from it.

Parameters: 1 - non-working IRP address;

Kernel stack overflow. The kernel driver has started to occupy critical stack sizes. It is quite possible even damage to the core.

This message tells us that the driver has accessed a nonexistent RAM address. Unsuccessful initialization of the system (zero phase). It is necessary to determine more details, with such an error, carefully study everything. This is because the error does not indicate a specific problem.

Unsuccessful initialization of the system at a late stage (phase one). The error is of a general nature, the cause must be determined yourself.


1 - code indicating the reason for incomplete initialization;

2 is the INIT.C point at which the error occurred.

Occurs when a high-level driver calls a low-level driver when there is no free space in the stack area. Because of this, the low-level driver does not reach the required parameters, due to their absence and the loss of some of the packets. This can happen when the stack memory blocks are damaged. Check all drivers and memory for errors.


1 - the address at which the error occurred.

An error related to calling the driver. There was an attempt by the driver to remove a component of its device, at a time when there were uncompleted tasks for this component and its hit counter was not equal to zero.


1 - component address.

In case of asymmetry of the multiprocessor system. Occurs when the system has different levels and types of processors, as well as different parameters of floating point calculations on different processors.

Insufficient access points to the paging file. Occurs when a paging file driver does not clear it, thereby causing an overflow. Sometimes, fragmentation of the swap partition can be the cause.

Driver error related to the insufficient size of the MDL recipient area to display the address limits, at the time of calling the IoBuildPartialMdl () function and defining the MDL source.

Failure to execute a function for the driver related to the allocation of space in the Must Suceed Pool. The system driver needs to be reinstalled.

Error parameters:

1 - required space;

2 - number of the page that is used;

3 - the number of pages in the request;

4 - the number of pages that are available.

An attempt by a driver to complete an IRP while it has already completed. The driver may have completed the same operation several times. Sometimes, this can happen when two drivers tried to complete the same operation at once. One of them failed. Quite a tricky mistake to diagnose.

Her parameter:

1 - the address for which a failure occurred.

The package is drawn at the cancel stage, but it does not apply to the driver and now is not completed.


1 - address of the package.

Memory access error, IRQ interrupts are disabled. The same as the error 0x0000000a.

Fatal not recognized error. Most likely, possible causes are such as in 0xc0000218, 0x0000022a or 0xc0000221.

Not enough page, the operation cannot be completed. Make sure that you have free space on your disk. Try reinstalling the driver.

Main settings:

1 - the number of pages involved;

2 - the physical number of pcs on the PC;

3 - extended pages;

4 - Total pages.

Damage to the input / output structure of the driver.

Main settings:

1 - value 1;

2 - damaged page title value;

3 - the number of available pages;

4 - zero.

1 - second meaning;

2 - data for removal;

3 - the maximum possible number of physical pages;

4 - Results of data deletion.

Failed to find the information requested in memory. The information that is missing by the mark that prohibits the record to the paging file.


1 - error address.

The problem is in the equipment, or in the system itself. In this connection, it was not possible to read the registry files. It can also be associated with the overflow of the account security manager libraries, and you need to make sure that the PDC machine, or BDC, is.


1 - error address 1;

2 - error address 2;

3 - library address;

4 - indicates damaged libraries (returns the HVCheckhive code).

Loading the system from the restored section of the array, while the library reports the health of the mirror, which is not valid. It is necessary to boot from these libraries that are in the shadow copy.

Lack of place, for correct operation of the registry files. This error can not occur, since for the operation of the registry, even when the system is loaded, there is enough space (location).

Parameters: 1 - five;

2 - indicates NTOS \ config \ cmsysini, which failed.

Error initializing an input or output device for an unknown reason. It may occur if the PC equipment was incorrectly defined when installing the system, or configuration changes to the user themselves.

Error initializing system process:

1 - process code;

2 - indicates the place in NTOS \ ps \ psinit.c, where an error occurred.

Indicates a point in NTOS \ init \ init.c, where an error was detected.


1 - session code that has defined not successful system initialization.

Damage to one of the registry files. May be damaged: Software, Security, SAM. Ensure that enough free disk space and enough RAM.

Damage to the System registry file, which is loaded via NTLDR. Other reasons may be associated with the lack of some keys and registry parameters. Try downloading the last successful option. In the extreme case, you will have to use a rescue disk, or even reinstalling the system.

At the initialization of the registry, it was not possible to record additional parameters to the System and System.alt files. This error may occur due to the lack of free applications on the disk.

It occurs when not a complete unloading of the driver occurs, after an input / output operation.

Main settings:

1 - the address of the process in which the error is detected;

2 - the number of pages that have been closed;

3 - reserve pages;

4 - zero.

Failed to read the kernel page. There may be a bad virtual memory block, or a disk controller error. Zero values ​​for the first two parameters indicate that the error location was not found. This may indicate the presence of bad equipment.

Status c0000009a - lack of system resources.

Status c000009c, or C000016AL - may indicate a damaged memory block. Try restarting your computer.

Status c0000185 - check the connection and operability of the SCSI device.

Parameters: 1 - 0;


3 - PTE value, at the time of the error;

4 - error address.

1 - status code;

2 - status code;

3 - virtual memory page;

4 - offset in the paging file.

The type and configuration of the HAL cannot be matched to the OS kernel or hardware. Perhaps due to incorrect changes in the NTOSKRNL.EXE or HAL.DLL files.

Error reading the page by the kernel. The error may be related to memory problems.


1 - lock type;

2 - error status (input / output code);

3 - address of the current process;

4 is the address of a memory block that has not been moved to the paging file.

Error initializing the boot device from which the system was booted. File system read error on this device, or inability to initialize. Error reading information from the device, the structure of the file system. If an error occurred during the installation of the OS, then the system may not support this disk or SCSI controller. Sometimes an error occurs when installing a new adapter or controller. If you have an x86 system, then just edit the BOOT.INI file.


1 - indicates a device object, or ARC.

There is not enough random access memory (RAM) to start the kernel. 5 MB required.

Parameters: 1 - numbers of physical pages;

2 - bottom page;

3 - top page;

4 - 0.

Hardware malfunction, or driver error. Possible lack of free disk space. Occasionally occurs when updating the OS. It is necessary to update the drivers for the equipment by downloading new ones from the manufacturers' websites.

The exception of an unexpected kernel mode action or interrupt that prevents the kernel from starting. An error occurred that the kernel was unable to cope with. It may be related to low-quality RAM blocks, or processor overclocking. You can try to cancel the function of synchronous data transfer in BIOS.

Invalid kernel initialization on this hardware. HAL will display all available information on the given problem. It is recommended that you contact your hardware manufacturer for technical support.

May occur in early versions of Windows NT when loading the installer. Most likely, you will never encounter this error.

The MBR checksum did not match the bootloader checksum. Most likely you have a virus. Just in case, scan the boot sector of the disk with an antivirus, booting from the Live-CD.


1 - Disk signature in MBR;

2 - MBR checksum recorded in osloader;

3 - MBR checksum recorded in the system.

Incompatible RAM units installed, or faulty. Diagnose blocks, replace damaged ones.

Initialization error, during phase zero, of the kernel-mode Plug and Play manager. The equipment needs to be checked.

Error loading one processor driver on multiple processor systems.


1 - driver address.

An attempt was made by a critical system component to close an invalid handle. Main settings:

1 - descriptor;

2 - 0 - protected handle is closed;

1 - invalid handle closed.

The existing thread has a blocked stack. The problem is related to the hardware driver.

Hardware driver problem.

Windows trial period has ended.

Main settings:

1 - installation date (lower 32-bits);

2 - installation date (upper 32-bits);

3 - trial period.

The call to ExInitializeRegion, or ExInterlockedExtendRegion failed. Associated with incorrect parameters.

Violation of the license agreement. It can happen when you try to change the product type, extend the trial period of the system.

An error occurred while reading or writing data to UDFS media. The file system may be damaged, bad sectors on the disk. Or, an error may occur due to the incorrect operation of the software that works and changes the structure of the file system.

The error is associated with a malfunction in the hardware of the PC. Possible misconfiguration, overclocking, overheating of components, power problems.

The driver has unstable power consumption parameters. Update or replace the faulty driver.

BIOS failure. Through the OS, it is impossible to understand such a problem.

Unsuccessful loading of the video card driver. Boot into Safe Mode and install the new driver.

An attempt was made to write data to ROM. This is due to a "defective" driver that needs to be reinstalled.

An attempt was made to write data to an invalid memory location. Replace the driver.

An error occurred while accessing memory. Associated with a driver or other software that needs to be replaced.

When checking the driver, an error was found in the STOP-error generation module. All parameters are recorded in KeBugCheckEx and displayed on the screen. The driver needs to be replaced.

An attempt was made to access a high-level process from an invalid memory area. This error almost always occurs due to drivers that need to be replaced.

The driver accessed the freed memory pool. The driver needs to be replaced.

A kernel timer was found in an invalid memory area. This error occurs when the driver has not expired the kernel timer before unloading it from memory. The driver needs to be replaced.

The driver was unable to cancel the operation of frozen OS components. This can happen if bad drivers or components are installed. The driver needs to be replaced.

The OS accessed the page memory through a high-level process. As with many similar cases, the problem is a bad driver for the device. It needs to be replaced. Sometimes, an error can occur when the RAM, or the paging file is damaged.

The driver made a request from too much kernel memory.

The error can occur if the NTFS.SYS file is faulty. But it can also occur with various other file system failures.

A faulty driver caused the system to freeze. Oftentimes, the culprit is the display driver when the OS goes into standby. The reason may lie in the video card, or the driver for it.

The problem may arise after an incorrect shutdown of Windows and damage to the file system.

There may have been a failure while connecting to the boot disk. This happens when the configuration is incorrect, or when disk controllers are connected. The problem can be fixed by a simple reboot of the system.

The kernel detected an interruption storm. This state is characterized by the inability to issue an interrupt request caused by the interrupt-level device. This is usually due to a faulty driver.

Failed to shutdown the OS due to insufficient memory. It is necessary to calculate the program that did not "fit" into the memory boundaries, to determine the reason why the virtual memory could not provide the necessary resources. Try to determine whether this program will refuse, terminate its work, without freeing open pages in memory.

Damage to the system driver Http.sys. Replace this file with a similar, serviceable one.

An attempt was made to execute a process in a non-executable region of memory.


1 - address from which this attempt was made;

2 - Contents of the page table entry (PTE).

There is not enough free page memory, it is impossible to continue performing basic system operations.

Main settings:

1 - the amount of memory that was requested;

2 - the requested amount of memory, with the impossibility of recording;

3 - last state code.

A fatal error has occurred in the USB controller. It can also be connected with other related devices. Such a problem may be associated with a malfunction in the controller itself, or in the devices connected to it, or in the connection itself. Try replacing the device driver. The problem can be solved by completely disconnecting the USB controller.

One of the processors, on a multiprocessor system, stopped responding, or entered an infinite loop. The error is related to the fact that the expected interrupt was not received from the processor, within the required time.

Main settings:

1 - sync pulse interruption interval;


3 - address of the processor unit that is not responding;

4 - 0.

The GPU tried to write data to an area of ​​memory that was not designated or reserved. There may be an error in the video driver itself, or a mismatch in the BIOS version.

Main settings:

1 - Offset (in ULONG) within AGP pages to the first ULONG data whose data is corrupted;



4 - 0.

Graphics Aperture Remapping Table (GART) corruption associated with an incorrect DMA driver.


1 - virtual address in GART;

2 - offset in which incorrect parameters were found;

3 - address from the GART cache;

4 - 0.

Signature error, or damaged video driver. It needs to be replaced.


1 - original team;

2 - current command;


4 - 0.

Fatal error caused by a third-party file system filter. Often the error is caused by various third-party software: defragmentation utilities, data backup, antivirus software. You can get rid of these programs, or increase the paging file and RAM.

The kernel has detected corruption of the system code, violation of data integrity. Such a problem may arise due to the failure of third-party drivers, a malfunction of the RAM.

Internal video driver error. You need to reinstall the driver.

An exception occurred in the kernel-mode resource manager.

A fatal error has occurred during the execution of the msrpc.sys component. The error code is specified in the first parameter.

Fatal error in the DirectX kernel.

The shadow video driver encountered a fatal error.

The video port driver, in the AGP interface, has encountered a fatal error.

Unsuccessful reset of the video driver, op timeout.

An attempt was detected to write to the write protected area of ​​the configuration manager.


1 - address of the recording command;

2 - PTE content;

3 - reserved;

4 - reserved.

The driver that made an entry is specified in the form of the Unicode string.

Access disorders in the memory area caused by the driver.


1 - type of violation;

2 - reserved;

3 - reserved.

Through the kernel debugger, you must open the call stack in which you can define a driver that caused this error.

Error associated with computer hardware.

The memory page has not been completely filled with zeros. This is usually associated with hardware failures. Sometimes, components with privileges in the OS can prematurely make changes in the memory pages.


1 - page address;

2 - page number;


4 - 0.

Error reading the media partition with EXFAT format, this happens if there are damaged sectors on the disk, or even damage to the file system. Perhaps the error led various programs that interact directly with the disk and the file system. There occurs with media, with formatting under Windows Vista Service Pack 1.

The Windows kernel took all PC resources, including the paging file and then cannot continue its work. Scan hard drive on errors. An increase in the volume of disk and RAM can help.

Error booting a DLL library. The reason may be associated with the lack of this file, or damage it. Sometimes, it may be the cause of the registry damage.

Damage to the library .dll .

Failed to load the required registry file. Perhaps this file is damaged, or is generally absent. This may happen if the hard disk is damaged. Sometimes, loading into memory, the driver can damage the data of the system registry. It is necessary to check the prompt memory.

Failure associated with WinLogon or CSRSS, at the time of Windows transition to a privileged mode. It may appear when damaged the user32.dll library file and the .SYS system drivers. An error occurs if the system account settings are changed on behalf of the system administrator, and it has more adequate permissions, to access files and system folders.

Damage to the driver, or system library. If the operating system has revealed a damaged file, then it is necessary to replace it with a similar, working. A good option will reinstall the system. If such an error arises constantly, then this means that there is a problem with information carriers, their controllers, possibly their damage.

The audit policy activated the Crashonauditfail parameter.

The error indicates the problem of device driver.

Emergency failure caused by the user intentionally.

Here is such a list of major errors of the "blue screen of death". And this is not so terrible. As you can see, any error can always be corrected, it is enough just to figure it out in its reasons.

How to remove the blue screen of death windows 7The blue screen of the death of Windows 7 is a critical error that leads to the appearance of a static image with a report on the breakage. As a result, the user loses access to the system, often after rebooting the situation does not change. The solution to the problem comes from the cause of the appearance - hardware or software.

Possible reasons

The appearance of the blue screen (BSOD) is often associated with software problems that occur as a result:

  • the lack of compatibility of the operating system (software) of the Software (software);
  • conflict installed hardware drivers;
  • exposure to malware.
  • crash in the work of programs.

Note! If system problems become the cause, the problem can be removed without the use of auxiliary equipment by starting in safe mode.

BSoD can occur due to damage or incompatibility of the computer hardware, for example:

  • breakdown of random access memory (RAM) or hard disk;
  • lack of compatibility of installed components;
  • hardware failure due to improper overclocking of the graphics chip or processor.

Important! In the event of a hardware failure, replacement or repair of the system unit elements will be required.

Diagnosing the problem

To diagnose the problem that has arisen, you need to look at the text of the report. By default, the screen automatically disappears after a certain time, to find out the information, you will need to make changes to the system configuration:

  1. Expand the menu « Start ", Right-click (RMB) on the item" A computer ", select " Properties ".

Go to computer properties

  1. On the sidebar, follow the link “ Additional system parameters ".

Go to "Advanced system parameters"

  1. On the tab “ Additionally »Click Options in the block " Boot and recovery ".

Boot and recovery options

  1. Uncheck the item " Perform automatic reboot ", From the drop-down menu below select" Small memory dump (256 KB) ".
  2. Click OK .

Changing Startup and Recovery options

After the specified parameters, when a blue screen appears, there will be time to study the information in detail and, if necessary, rewrite it for further decryption.

Decoding the error

The error report text is unique for each case. The system automatically analyzes possible causes and provides detailed information with accompanying instructions for correction. Below you will find information on the example of a driver failure.

  1. The first paragraph informs about the appearance of an error in the system.

Information about the appearance of an error in the system

  1. This is followed by the name of the error, from the content you can understand that the cause is an incorrectly installed driver.

Error name

  1. Then, in three paragraphs, solutions to the problem are proposed, which will be described in detail below in the text of the article.

Solutions to the problem

  1. After the word STOP there are malfunction identifiers for a clearer understanding of the current situation. The information is intended for specialists and does not carry any payload to the average user.

Error indicator

  1. Depending on the type of malfunction, at the end, the address of the RAM in the sector of which the error appeared will be reported. The presented code is intended for specialists.

For the user, only the second paragraph is important, which will suggest further solutions for resuming the OS.

Ways to Eliminate Blue Screen of Death in Windows 7

There are several ways to fix the blue screen of death in Windows 7, but the effectiveness directly depends on the cause of the problem. If this information is not available, it is recommended that you follow the instructions below one at a time.

System Restore

Among the standard programs there is a system recovery tool using pre-created checkpoints. To use this feature, you need to start the OS in safe mode:

  1. To restart a computer.
  2. Press the key during startup. F8 .
  3. In the menu of additional boot options, select the item " Safe mode ".

After the desktop appears, you need to run the appropriate utility and perform the recovery:

  1. Expand the menu « Start ".
  2. In the search box, enter “ System Restore », Click on the item of the same name.

Launching the System Restore utility

  1. In the initial window, click Further .

Go to the "System Restore" menu

  1. Select a previously created nugget from the list, click Further .
  2. Confirm the action with the button Done .

If the BSoD screen appears when you try to start in safe mode, you must use the recovery environment. For this:

  1. When starting the computer, press F8 .
  2. Select from the list the item " Troubleshoot computer problems ".
  3. In the new window, click on " System Restore ".

The corresponding utility will start, which will need to select the system control snapshot and roll back.

Important! The method can be used if there are restore points.

Installing the latest updates

Early versions of Windows 7 are not stable, so it is recommended that you install the latest updates that will solve many problems.

Note! It is recommended to start the system in safe mode.

Step by step guide:

  1. Through the menu " Start »Run« Control Panel ".

Perekhov in the "Control Panel"

  1. Go to the section " system and safety ".

Go to the "System and Security" menu

  1. Enter " Windows Update ".

Go to Windows Update

  1. Click on the link “ Search for updates »On the sidebar.

Search for updates

  1. After completing the search, click Install now .

Note! We recommend that you periodically check for updates and install them.

Virus removal

Virus software can disrupt the correct operation of the OS. If an error occurs, you should check the system using specialized software. Guide for using the standard Windows 7 tool:

  1. On the menu " Start »Search by request Windows Defender », Run the program of the same name.
  2. Click on the drop-down list " Check »On the top panel.
  3. Select the option " Full check ".

After the scan is complete, a report will be provided. When prompted for action with viruses, you should remove them.

Alternatively, you can use third-party antiviruses, for example: AVG Antivirus, AVZ, 360 Total Security, Kaspersky Anti-Virus or Avast.

Repair damaged system files

Often BSoD crawls out due to damage to system files. You can restore them using the built-in console utility SFC :

  1. In the search bar of the menu " Start »Enter« Command line ".
  2. In the results, right-click on the component of the same name.
  3. Select the option " Run as administrator ".

Running "Command Line" as administrator "

  1. In the console window, enter and execute the command sfc / scannow .

Entering sfc scannow at Command Prompt

After a lengthy scan, the utility will detect and replace corrupted system files.

Reset BIOS

Incorrect configuration of the input and output utility (BIOS) can cause an error to crash on the screen. To fix, you should reset the settings to the initial ones:

  1. Press the BIOS startup key while the computer is starting up. It could be Delete , F2 or Esc F10 .
  2. Go to section Exit using the arrows on the keyboard.
  3. Select line Load Setup Defaults , press Enter .
  4. Confirm the action.

Attention! The location of this option may differ depending on the BIOS version.

Fix when booting or installing Windows

The appearance of a blue screen during download or installation is possible only in three cases:

  • damage to computer components (error code: 0x00000116 , IGDPMD64.SYS , fltmgr , ntoskrnl ).
  • the operating system image was damaged during boot or recording.
  • BIOS configuration is incorrect.

If the image or boot drive is damaged, you should replace the flash drive and download Windows 7 from another source.

If there is a problem with the hard disk or RAM, you will need to make diagnostics with the possible subsequent replacement of equipment. Without a lack of experience, it is recommended to consult a specialist.

Prevention of the appearance

To prevent the blue screen from reappearing, it is recommended to adhere to the following rules:

  • systematically scan the system for viruses;
  • to clean the components of the system unit or laptop case;
  • check for updates with subsequent installation;
  • prevent clogging of the system partition, the CCleaner program is suitable for cleaning;
  • periodically defragment the hard drive.

Fixing a critical BSoD error involves interacting with system components and utilities to repair damaged files. If the cause of the malfunction is a software component, it will not be difficult to restore the computer to work. In the event of a component breakdown, you will need to resort to replacing the equipment.