Blue Screen of Death (BSoD)

Almost any user had to, if not encounter, then certainly hear about such a thing as the "Windows blue screen of death." This topic is vast, so read it carefully! In this article we will discuss what the blue screen of death is, what to do in this situation, and of course, I will try to show everything clearly. The name of this phenomenon was invented exactly what it needs - frightening and memorable. In today's article, I will take a closer look at the causes of the blue screen of death, as well as possible solutions to this problem.

The Blue Screen of Death is a serious problem that drives PC users into a stupor. Before you start reading the article, I recommend that you postpone all your affairs and so that no one distracts you. If you understand the essence of the occurrence and solution of this problem, then in practice it will be much easier. I have already been contacted with this problem more than once, and there have even been situations when, in their practice, administrators did not know what to do when a blue screen occurred. Instead, they told the users that they needed to replace the system unit completely. WHAT? If you were told so, then remove the noodles from your ears and read the article to the end.

What is this mistake

As a result of the appearance of a problem, the operating system (OS), being unable to correct the error on its own, urgently shuts down. Naturally, no user data is saved (open documents, etc.). The only thing that Windows manages to do is write information to the log and create a dump file, if the settings specify the creation of this file when such errors occur.

To avoid unfair accusations against Windows, I will immediately make a reservation: the blue screen of death does not appear without serious reasons, and shutting down in such a situation is the only way out.

The blue screen of death looks like this:

From the screenshot, I think it is clear where the word "blue" came from in the title. As for "death", here we mean the death of the operating system, that is, its inevitable reboot, and in some cases, reinstallation. In practice, most of the causes of blue screens of death are successfully eliminated without reinstalling the OS, provided, of course, a timely and correct response. Most importantly, you need to understand where the legs grow from. I mean, if you don't know why the blue screen of death appears, then the problem is difficult to solve.

What is Windows telling us on the horrible blue screen of death?

To make it easier to understand, I will conditionally divide it into several blocks and describe each one separately (for those who know English, self-understanding for the most part will not be difficult).

1. Here Windows reports that the problem was found, and to prevent damage to the computer, the system had to be shut down urgently.

2. The type of error is indicated here. There are a limited number of them, and for each such error, information can be easily found on the Internet.

3. In this part, the OS informs about the possible causes of the problem, and also gives some recommendations for eliminating the problem.

4. In the section with the name "Technical information" the error code is indicated, and it is also possible to indicate the name of the problematic driver (more details below).

After reviewing the blue screen, you should understand what this error is or find out about the file that may be listed on the screen.

Causes of the Blue Screen of Death

The Blue Screen of Death can appear for a variety of reasons.

The most common reason is drivers. This includes drivers that are incompatible with each other or with the operating system, and other failures associated with them.

In this case, I have a little story, this information is not only for you to read and forget !!! With the help of this story, you will learn how the problem with the blue screen of death is solved.

I used to work as an Administrator Assistant and maintain a fleet of 80 computers. On almost 20 computers, the blue screen of death appeared from time to time. When I asked the administrator about the reasons for such a misfortune, he just shrugged his shoulders and said that he did not understand at all what was going on (I think he just didn’t want to figure it out). After his answer, it became interesting for me to find the essence of the problem myself.

First of all, I looked at what error appeared on the screen, then wrote down the error code and the name of the file on a piece of paper, which was pointed to by the blue screen of death. After wandering around the Internet a little, I found out that this file is used for Wi-Fi adapters. After that, I made a small detour of the problem computers, and made sure that they all really work in the network via Wi-Fi adapters.

Then I decided to find out what drivers the administrator installs when connecting these devices. His answer drove me to a dead end. It turned out that he was installing the drivers that came with the equipment. After that, I spent 2 hours, but still found the topic of interest to me on the Internet. It turned out that these very devices are buggy with standard drivers.

It's strange, because the D-link company is considered one of the best, but in fact it turns out that it supplies drivers for adapters that do not work with them. By that time, a topic with a similar problem had already been created on the manufacturer's forum d-link. And for about 2 years this problem has existed among many users of these adapters.

To get out of our situation, it was decided to use other drivers (from other developers). We installed them on the problem computer and asked the user to notify us in case of a blue screen of death. Of course, I didn't know which drivers to install instead of the official ones. After reading all the topics on the forum in full, I found a dozen reviews that tried another driver (now I don't remember which one) and they solved this problem.

A few days later, he did not call, did not come to us, which means that there were no more problems! After making sure that everything was fine with his computer, we installed this driver on all computers and users breathed a sigh of relief.

Problems with the hardware of the computer.

Often problems with "hardware" are more likely a consequence, but the cause may be overheating of components. It also includes hardware, memory, or hard drive problems that have arisen on your own.

Problems with programs.

The screen of death can be triggered by antivirus applications and various emulators. Also, sometimes viruses become the cause of the appearance of the blue screen of death, this does not happen often, but it also occurs.

What do we have to do

First, you need to prepare in advance for potential problems. Windows is configured by default so that the death screen appears for just a couple of seconds, after which the computer automatically restarts.

However, this does not give us the opportunity to have time to write down the error data, which does not suit us at all.

Note: if it does not reboot automatically, then use the "Power" button.

It will be enough for us to configure Windows so that it does not automatically restart. Thus, we can understand why the blue screen of death appears. Since in this error, you can read the error code or file that is to blame for the blue screen of death. After that, the Internet will help us. For this setting, you need to do the following:

On Windows XP: "Start" - "Settings" - "Control Panel" - "System" - "Advanced" - "Startup and Recovery" - "Options" - "System Failure". In the window that appears, you need to uncheck the "Perform automatic reboot" checkbox, and in the "Record debug information" block, select "Small memory dump", and click the "OK" button.

On Windows Vista / 7: "Start" - "Control Panel" - "System and Security" - "System" - "Advanced System Settings". In the window that appears, select the "Advanced" tab, the "Startup and Recovery" subsection, and click the "Options" button, all that remains is to uncheck the "Perform automatic reboot" checkbox, enable a small memory dump and click "OK".

You can also get to this window by right-clicking on "Computer" - select "Properties" - on the left click "Advanced system settings" - go to the "Advanced" tab - for me this method seems easier.

Secondly, at the first appearance of the blue "enemy", you need to write down the data from the blue screen on paper. This data can help in finding the cause of the problem.

And thirdly, let's show you how to remove the blue screen of death.

You need to understand that the screen of death appears much more often after any user action than by itself. Therefore, the first thing to do is to try to return the computer to the state in which it worked stably.

If no special manipulations with the computer were carried out, that is, you just worked, and suddenly “He” appeared, you will have to look for answers on the Internet. Since the most common cause of BSODs is drivers, the first priority is to find the name of the faulty driver.

If the information was indicated on the screen of death itself, then in this case we only need to find a description of the error or problem that the driver caused. To do this, simply enter the name of the faulty file known to us in any search engine. Thus, we find out what kind of file it is. For example, if this file is needed for the video card to work, then you need to remove the video card driver and download a new one from the office. manufacturer's website.

Otherwise, you need to start the search with the data that you manually rewrote. Using this information, you can roughly navigate the possible reasons. If we didn’t manage to find out anything useful, we proceed to the analysis of the memory dump.

Do not install various assemblies that were made by unknown authors. If your neighbor Uncle Vasya even advised you to install his assembly, then my advice to you is - DO NOT DO THAT! It is better to install a full-fledged original Windows distribution and you will be happy.

If no problems with the drivers were identified, you need to check the hardware components of the computer, which can be the cause of the blue screen of death. First of all, this is RAM, hard drive or overheating of any system components (video card or processor). You can use the AIDA program to check the temperature.

If you think that the problem is with the hardware, then borrow from your friend this part from his computer and install it on yours. After making sure that this particular part is unstable on your computer, you can then buy it in the store.

To check the RAM, I recommend the MemTest86 program, and to check the hard drive, the Victoria program (I will describe in detail the work of these programs in separate articles). In addition, it does not hurt to conduct a full virus scan by first updating the virus signature database.

Let me remind you that a dump is a file that is created at the time of the problem and contains a detailed description of the state of the system at the time of the error, and, therefore, can tell about the cause of the failure.

Let's imagine a situation where your friend has a blue screen of death. He does not understand what it is and why the blue screen of death appeared. Naturally, he turns off the computer and tries to find out from his friends what it was. Of course, he did not write anything on a piece of paper, that is, he does not know what was written, but as you already know, in order to solve this problem, you need to know why the error appeared.

Just for this, there are special programs with which you can find out what the reason was. Now even if you are in another city, you know how you can help your comrade. You can use Debugging Tools for Windows or BlueScreenView to view the contents of the dump.

Let's take the BlueScreenView program as an example and figure out how to view the dumps. Download a russified program for a 32 bit system.

Now we run the file "BlueScreenView.exe".

If there are no lines at the top, then your computer has not crashed.

I didn't have a blue screen of death and so I had to borrow it;). So now we have a dump that will help us understand how this program works.

To point to the dump I have, I need to make changes to the program. To do this, I press "Settings" - "Additional parameters" or "CRTL" + "O".

Click "Browse" and indicate where our dump is located.

Note: If the program is located on the problem computer, then nothing needs to be changed.

Now we see which files caused the error. Click on the line with the right mouse button and select "Properties".

Copy the "File name" and go to any search engine to find out what kind of file it is.

After a couple of minutes, we understand that this file is a video card driver. This is how in a few minutes you can understand what is the cause of the blue screen of death. But sometimes it takes an hour or more to find out the reasons.

I hope now you will have no difficulties in solving the blue screen of death problem.

See you soon!

A must-see video, because there is something that cannot be told in words:

All users of Windows 7, at least once in their life, have encountered the Blue Screen of Death.

For ordinary users, this problem causes serious fear because of this name. Seeing a blue background and white letters on the monitor, they rush to take their computer to a service center, where they are even more frightened.

As a result, the user pays a lot of money to fix this problem.

We will explain what the blue screen of death is and what to do when it appears in windows 7.

Blue screen of death - a system notification of a threatening error in the OS.

Errors are different, so there are also several BSODs. Malfunctions due to which the Blue screen of death appears on the monitor, are divided into two types:

overheating of the computer hardware ("hardware");
system problems in the software (software).

If the reason is overheating of the hardware, then, first of all, you need to make sure that all the fans are working, clean the system unit from dust, you may even have to replace the capacitors on the power supply.

Overheating can be caused by malfunctions in the motherboard, as well as in other components of the computer.

If you are not a computer engineer and do not understand hardware, then it is better to seek help from specialists.

For more accurate diagnostics, take your PC to a service center for the repair of office equipment.

If there is no overheating, then the problem is in the software. Often the screen of death appears due to driver incompatibility, but there may be other reasons.

Let's consider them in more detail in the section "Causes of BSOD and Ways to Solve the Problem". Now let's talk about pre-configuring windows 7 OS.

Setting up the operating system

To determine the cause of the appearance of the blue screen of death, first of all, it is necessary to disable the automatic restart of the PC, since the BSOD quickly disappears.

To do this, you need to follow the steps indicated in the video instructions below:

What is a kernel memory dump

Computer information is written to the hard disk.

But first, the files go into random access memory (RAM), which is automatically cleared every time the computer is restarted.

If critical errors occur, using the "kernel memory dump" option, the system will create a so-called DMP file before rebooting.

It will store BSOD information.

To open an encrypted DMP file, you need to download a special utility "BlueScreenView" from the official website of the developer of this program.

Now that the computer is ready, you can start fixing the error.

Causes of BSOD and ways to solve the problem

Let's consider a few examples of how to solve the problem.

Example # 1

Let's analyze one of the BSODs.

The first sentence says that a fatal error has occurred. Second, it displays the reason for the error (DRIVER_IRQL_NOT_LESS_OR_EQUAL).

In this example, this is a driver incompatibility. Next comes the standard system message with tips for solving the problem. We go down to the STOP section.

Here is the error code (STOP: 0x000000D1), you need to remember this code.

It is necessary in order to find on the Internet a solution to any problem that has arisen on your PC.

Below the STOP section is the registry file in which the error occurred (gv3.sys).

Let's restart the computer, launch the BlueScreenView program and in the window that appears on the screen, we will find the message highlighted in red.

There will be indicated the device, the faulty driver of which caused the screen of death.

Please update the driver for this device to the latest version.

There are times when BSOD began to occur after updating the driver. Then it is necessary, on the contrary, to restore the old version of this driver.

Example No. 2

Consider the next Blue screen of death.

This error can be caused by a number of problems, usually hardware. These problems cannot always be solved at home. NO_PAGES_AVAILABLE means that the system does not find any important files.

Therefore, it is worth checking the status of the hard drive and RAM.

Try to get one of the RAM sticks and start the computer without it. If it starts up normally, then remove the dust from the RAM slots in the system unit.

This may not help, then you need to replace the RAM.

If the problem is not in the RAM, defragment the hard disk using a special utility, for example, "CCleaner".

This will organize the files and reduce the load on the hard drive.

Example No. 3

This blue screen indicates that the error was caused manually by pressing a keyboard shortcut. But this error can also be caused by a virus.

To get rid of it, you need to clean the computer registry. You can, of course, use special utilities, the same "CCleaner", but then the dump files will be deleted, which is undesirable.

Therefore, we will clean the registry manually.

Below the STOP line, we see that the error was caused by playing the kbdhid.sys file. Let's find it in the registry.

For this you need:

Open the "Start" menu and enter the "regedit" command in the "search", press the "Enter" key.
In the opened registry editor, select the item "Edit", then "Find" or press the key combination "Ctrl" + "F".
Enter the name of the folder with the extension (kbdhid.sys).

After that, in the found folder kbdhid.sys, open the files by double-clicking the left mouse button. In the file of the REG_SZ type, set the "Default" value.

In a file of type REG_DWORD, set the value as parentheses.

It should be remembered that if there are numbers from two-digit numbers and more in brackets, then in the "value" field enter signs (numbers or Latin letters) after x without leading zeros.

After these steps, restart your computer. The blue screen will no longer appear.

Example No. 4

This BSOD arose due to an outdated driver.

To fix this error, let's go below the STOP section. Under the second sign "***" we will find the name of the outdated driver. We need to update it.

Example No. 5

The first time you connect any USB device, for example, a Flash drive, the system automatically installs its driver.

Therefore, the OS recognizes this device. But there are situations when the system cannot find the driver, then the OS is incompatible with the USB device, and the windows 7 blue screen of death appears. What to do in this case?

To fix this error, you need to remove the "flash drive" from the USB connector, restart the computer, find the driver yourself and install it manually on the system drive C: \ Program Files.

After that, you can safely use this "flash drive".

Conclusion

Now you know that if the blue screen of death appears, you don't need to panic. We have covered the common types of BSODs.

We hope that this information will help you cope with this little nuisance on your own.

In this article, we will talk about such a phenomenon in the Windows operating system as - Blue screen of death or in our “ blue screen of death", Also called STOP error. Let's consider the main causes of occurrence and decipher the codes of these errors.

And first, let's give a definition of what is “ Blue screen of death"Is a method of generating a fatal error message in Windows NT 4.0, Windows 2000, Windows 2003, Windows XP, Windows Vista and Windows 7, caused by malfunctioning of some programs or drivers, but still more often due to hardware failures of the computer.

A blue screen stops all processes in the operating system and freezes the computer after displaying a blue screen. In general, the blue screen helps us, you ask, but because it prevents the destruction of the operating system and the decommissioning of equipment. When “ blue screen of death»The error code and how to solve it are displayed. But it may be that the STOP error was caused, for example, by distortion of data packets transmitted over the local network, in this case a simple reboot helps. If the error appears every time you start the operating system, then this is already a possible problem related to the hardware of the computer, for example, damage to drivers, file system, hard disk, RAM blocks. But to find out the reasons for the error that occurred, it is necessary to rewrite the first two lines of the STOP error. For example, as shown just below:

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

where 0xC0000022, 0x00000000, 0x00000000, 0x00000000- parameters that reveal the meaning of this BSoD.

By the way, there is a small feature, it lies in the fact that in the operating system, in order to see the blue screen, you must first enable this windows feature, or you simply will not see this screen, if an error occurs, the computer will simply reboot quickly (and so every time).

To enable this option, go to the properties "My Computer", select the "Advanced" tab. In the Startup and Recovery box, click the Options button. In the window that appears, uncheck the box next to "Perform automatic restart".

With the appearance of a STOP error in the text of the message, a method for solving it is briefly presented, though in English. But I can say for sure that at the present time a common cause of STOP errors is hardware problems with the hardware of a computer or its software parts, and sometimes due to a mismatch between one and the other.

Now let's go directly to the errors themselves and look at their causes and short solutions.

0x00000001: APC_INDEX_MISMATCH

Internal kernel error. The problem is most often associated with a driver problem, insufficient RAM or hard disk space.

0x0000000A: IRQL_NOT_LESS_OR_EQUAL

There was a tampering with virtual memory on an internal high IRQ process. The most common cause is a device driver using the wrong address. The error occurs due to bad drivers. Rarely occurs due to a malfunction of one of the devices in the system.
Options:

The address to which the erroneous call was made
IRQL used to access memory
Memory access type: 0 = read operation, 1 = write operation
The address of the instruction that requested access to memory at address

0x0000001E: KMODE_EXCEPTION_NOT_HANDLED

This is a very common mistake. Usually, the excluded address points to the driver or function that caused the stop screen. Always pay attention not only to the specified driver, but also to the address itself or the image containing this error. This is usually the exception code 0x80000003. This error means that a breakpoint or handler was initialized when accessing memory, but the system booted with the / NODEBUG switch. This error may not appear too often. If the error appears constantly, make sure that the debugger is connected and the system boots with the / DEBUG key.
On non-Intel systems, if the exception address is 0XBFC0304, the error occurs due to processor caching. If the error persists, contact the processor manufacturer.
Typically, analysis of the second parameter of this message is required, which indicates the address of the driver / function that caused the problem.
Options:

Exception code
Failed address
Parameter 0 - exception
Parameter 1 - Exception

0x00000020: KERNEL_APC_PENDING_DURING_EXIT

The error name indicates a damaged / disabled APC counter. If you have such a situation, check all the file systems installed on the machine, for example using the EMRD rescue kit.
The current IRQL must be zero. If the IRQ is not equal to zero, then a certain order of unloading drivers, when returning to a higher IRQ level, may cause an error. Try to remember what you were doing or which applications were closing, which drivers were installed when the blue screen occurred. This symptom indicates a serious problem with third-party drivers.
Options:

APC address at the time of the failure.
Failed APC Thread
Current IRQ level

0x00000023: FAT_FILE_SYSTEM

FAT).

0x00000024: NTFS_FILE_SYSTEM

There was a failure to read or write to a hard disk partition formatted as NTFS... The failure can be associated with damage to the file system, or with the appearance of bad sectors on the disk. Also, the failure can be associated with software that changes the disk structure ( encryption programs and stuff).

0x0000002A: INCONSISTENT_IRP

I / O Request Packet (IRP) is not functional; occurs when a field or more than one field is invalid compared to the persistent state of the IRP. For example, the IRP was already disabled when a device driver was waiting for a command.
Options:
1 - the address at which the IRP was found in idle mode

0x0000002B: PANIC_STACK_SWITCH

This error occurs when the kernel stack area is full. The error occurs when the kernel driver uses too much stack space. Damage to the kernel itself can also be a possible cause of the error.

0x0000002E: DATA_BUS_ERROR

This STOP error most often occurs due to a failure in the RAM area. This can happen when a driver tries to access a memory address that does not exist.
Options:

The virtual memory address that caused the error
The physical address of the cause of the error
Processor Status Registration (PSR)
Error Instruction Registration (FIR)

0x00000031: PHASE0_INITIALIZATION_FAILED

System initialization could not be completed early (phase 0). It is necessary to study the error in more detail, since this error code does not say practically anything.
0x00000032: PHASE1_INITIALIZATION_FAILED
The system initialization could not be completed at a late stage (phase 1). It is necessary to study the error in more detail, since this error code does not say practically anything.
Options:

System-level code that describes why the system thinks initialization has not completed
Indicates the location within INIT.C where the phase 1 initialization error occurred

0x00000035: NO_MORE_IRP_STACK_LOCATIONS

The high-level driver tried to call the low-level driver through the IoCallDriver () interface, but the system did not have free space in the stack area, for this reason, the low-level driver will not reach the required parameters, since there are no parameters for it at all. This is fatal because the high-level driver thinks it has filled in the parameters for the low-level driver (it must have done something to invoke the low-level driver). However, since there is no free space in the stack area, the end of the packet was overwritten. This is often due to corruption of stack memory blocks. It is necessary to check the memory and drivers for errors.
Options:
1 - IRP address

0x00000036: DEVICE_REFERENCE_COUNT_NOT_ZERO

The device driver tried to remove one of the components of its device from the system, but the counter of this component was not equal to zero, which means that there are some outstanding tasks behind this component (the counter indicates an error code, due to which this component cannot be unloaded). This is a driver call error.
Options:
1 - object address

0x0000003E: MULTIPROCESSOR_CONFIGURATION_NOT_SUPPORTED

The multiprocessor system is not symmetrical with respect to each other. For correct symmetry, processors must be of the same type and level. For example, trying to use a Pentium-level processor and an 80486 at the same time will throw an error. Also, on x86 systems, floating point capability must be present on either all processors or none.

0x0000003F: NO_MORE_SYSTEM_PTES

Not enough PTE (page file entries - paging file access points). Usually the cause is a driver that does not clean up the swap file well and it overflows. Excessive fragmentation of the paging file may also be the cause.

0x00000040: TARGET_MDL_TOO_SMALL

The driver called the IoBuildPartialMdl () function and passed the MDL to it to detect a portion of the MDL source, but the destination MDL scope is not large enough to display the required address limits. This is a driver error.

0x00000041: MUST_SUCCEED_POOL_EMPTY

The system driver has requested a seat in the Must Suceed Pool. This function cannot be performed because the system does not allocate space in the Must Suceed Pool. Replace or update the faulty system driver.
Options:

Required request size
Used page number
Number of pages requested
Number of available pages

0x00000044: MULTIPLE_IRP_COMPLETE_REQUESTS

The driver requested an IRP to be completed, but the package was already completed. This error is difficult to detect. Possible cause - the driver tries to complete the same operation several times. A rare reason - 2 different drivers are trying to take over the package and terminate it. The first usually works, but the second does not. It is difficult to trace which driver did this, as traces of the first driver were overwritten by the second.
Options:
1 - IRP address

0x00000048: CANCEL_STATE_IN_COMPLETED_IRP

This error indicates that the I / O Request Packet (IRP) to be completed has a cancellation order defined in it, i.e. this means that a packet in this mode can be canceled. However, the package is no longer related to the driver, since it has already entered the completion stage.
Options:
1 - IRP address

0x00000049: PAGE_FAULT_WITH_INTERRUPTS_OFF

Page error while accessing memory with disabled IRQ interrupts. The error description is the same as for 0x0000000A.

0x0000004C: FATAL_UNHANDLED_HARD_ERROR

Fatal unrecognized error. The most likely causes are described in 0xC0000218, 0xC000022A or
0xC0000221.

0x0000004D: NO_PAGES_AVAILABLE

No more free page memory to complete the operation. Check for free disk space. Replace the driver. Options:

Number of pages used
Number of physical pages per machine
Extended page size
Total page size

0x0000004E: PFN_LIST_CORRUPT

The reason is a damaged / faulty driver I / O structure. Options:

Value 1
ListHead value that is corrupted
Number of available pages

Value 2
Data that is deleted
Maximum number of physical pages
Summary of deleted data

0x00000050: PAGE_FAULT_IN_NONPAGED_AREA

Occurs when the requested information was not found in memory. The system is checking the page file, but the missing information has been indicated as not being written to the page file.
Options:
1.points to the memory address that made the error

0x00000051: REGISTRY_ERROR

An I / O error occurred with the registry when the system tried to read one of its files, it follows that the error could be caused by a hardware problem or damage to the system itself. It can also mean that the error is caused by an update operation that is used only by the security system and this error occurs when resources are running low. If this error occurs, check if the machine is a PDC or BDC and how many accounts are in the SAM (Account Security Manager) database, if the corresponding libraries are almost full.
Options:
1.value 1 (indicates where the error occurred)
2.value 2 (indicates where the error occurred)
3.may point to a library
4.may be the return code of HvCheckHive, if any
library corrupted

0x00000058: FTDISK_INTERNAL_ERROR

The system booted from the restored primary partition of the array, as a result of which the libraries report that the mirror is in order, but in fact it is not. Real library images are in shadow copy. You need to boot from them.

0x00000067: CONFIG_INITIALIZATION_FAILED

An error means that the registry cannot allocate space for the registry files to function. This error can never appear because the process of reserving such space occurs early in the system boot phase and sufficient space is allocated for the registry.
Options:
1.five
2. Indicates NTOS \ CONFIG \ CMSYSINI that failed.

0x00000069: IO1_INITIALIZATION_FAILED

Failed to initialize the I / O device for an unknown reason. This happens if the system installer has incorrectly detected the hardware during the installation of the system, or the user has incorrectly reconfigured the system.

0x0000006B: PROCESS1_INITIALIZATION_FAILED

Options:
1. reports to the code of the process that decided that the system initialization was not successful.
2. Reports to the location in NTOS \ PS \ PSINIT.C where the error was found.
0x0000006D: SESSION1_INITIALIZATION_FAILED 0x0000006E: SESSION2_INITIALIZATION_FAILED 0x0000006F: SESSION3_INITIALIZATION_FAILED 0x00000070: SESSION4_INITIALIZATION_FAILED 0x00000071: SESSATION_FAILEDIAL
These codes (SESSION1 - SESSION5) indicate the location in NTOS \ INIT \ INIT.C where the error was made.
Options:
1. reports the code of the session, which decided that the system initialization was not successful.

0x00000073: CONFIG_LIST_FAILED

Indicates that one of the registry files is damaged or unreadable. One of the following registry files is damaged: SOFTWARE, SECURITY, SAM (Account Security Manager). Possible reason is lack of disk space or insufficient RAM.

0x00000074: BAD_SYSTEM_CONFIG_INFO

This error can occur because the SYSTEM registry file loaded through the NTLDR component is damaged.
This error can also mean that some required and their parameters are missing. Loading into LastKnownGood will probably fix this problem. But it is possible that you will have to reinstall the system, or use the rescue disk.

0x00000075: CANNOT_WRITE_CONFIGURATION

This error can occur when additional data cannot be written to the system registry files (SYSTEM and SYSTEM.ALT) at the time of registry initializations at the time of the first phase (when access to file systems appears). This error means that there is no free space on the disk and an attempt was made to save the registry to a read-only device.

0x00000076: PROCESS_HAS_LOCKED_PAGES

This error can be caused by a driver that is not completely unloaded after an I / O operation. Options:
1.process address
2.number of closed pages
3.number of reserved pages
4.zero

0x00000077: KERNEL_STACK_INPAGE_ERROR

Error reading one of the system kernel pages. The problem lies in a bad block of a virtual memory file or a disk controller error (very rarely, the cause may be a lack of system resources, or rather, the non-virtual memory reserve with status c0000009a may run out).
If the first and second parameters of the error code are 0, it means that the location of the error in the kernel was not found. This means that the error is caused by bad hardware.
I / O status c000009c (STATUS_DEVICE_DATA_ERROR) or C000016AL (STATUS_DISK_OPERATION_FAILED) usually means the information cannot be read due to a bad block in memory. After a reboot, an automatic disk check will try to determine the address of the bad block in memory. If the status is C0000185 (STATUS_IO_DEVICE_ERROR) and the virtual memory is on a SCSI disk, then check the connection and operation of the SCSI device.
Options:
1.zero
2.zero
3. PTE value at the time of error
4.address of kernel error, or

1.status code
2.I / O status code
3.virtual memory page number
4. Offset in the swap file

0x00000079: MISMATCHED_HAL

The HAL validation level and the HAL configuration type are not appropriate for the system kernel or machine type. This error is most likely caused by the user manually updating either NTOSKRNL.EXE or HAL.DLL. Or on the machine a multiprocessor HAL (MP) and a uniprocessor kernel (UP), or vice versa.

0x0000007A: KERNEL_DATA_INPAGE_ERROR

The page requested by the kernel is not read. The error is caused by a bad block in memory or a disk controller error. See also 0x00000077. Options:
1.type of frozen lock
2. error status (usually I / O code)
3.current process (virtual address for blocking type 3 or PTE)
4.address of virtual memory that cannot be moved to the paging file

0x0000007B: INACCESSIBLE_BOOT_DEVICE

During the installation of the I / O system, the boot device driver may not have been able to initialize the device from which the system was trying to boot, or the file system that should have read this device either failed to initialize or simply did not recognize the information on the device, as file system structure. In the above case, the first argument is the address of the unicode information structure, which is the ARC name of the device from which the boot was attempted. In the second case, the first argument is the address of the device object that cannot be mounted.
If this error occurred during the initial installation of the system, it is possible that the system was installed on a disk or SCSI controller that it does not support. Note that some controllers are only supported by Windows Drivers Libraries (WDL), which must be installed in Custom Install mode.
This error can also occur after installing a new SCSI adapter or controller, or after changing the system partitions. In this case, on x86 systems, you need to edit BOOT.INI.
Options:
1. a pointer to a device object or Unicode string, or ARC name.

0x0000007D: INSTALL_MORE_MEMORY

Not enough RAM to run Windows kernel (5 MB required)
Options:
1.number of physical pages found
2.bottom physical page
3.the top physical page
4.zero

0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

There is a hardware, driver, or low disk space problem. The error can also appear when trying to upgrade Windows XP to Service Pack 2 or Service Pack 3, or Windows Vista when trying to upgrade to Service Pack 1. The cause of the error may be related to the hardware drivers. You need to roll back the changes to the state at the time of the Service Pack installation, or uninstall the installed update. To solve this problem, you need to update the hardware drivers from the manufacturer's website.

0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP

An unexpected kernel-mode exception, or interrupt, has occurred that prevents the kernel from firing. Also, the cause of the error can be an interrupt, which entailed immediate death in the form of a double fault - a double fault. The first number in the error code is the interrupt number (8 = double fault). To find out more about what this interrupt is, refer to the Intel x86 family manual.
In other words, an error occurs when the processor makes an error that the kernel cannot handle. Most often, the error occurs due to bad blocks of RAM, and sometimes due to overclocking the processor.
Try to disable the synchronous data transfer function in the BIOS.

0x00000080: NMI_HARDWARE_FAILURE

Kernel initialization error on this hardware. The HAL should provide any specific information it has and invite the user to contact the hardware vendor for technical support.

0x00000085: SETUP_FAILURE

The error occurs when loading the system installer in earlier versions of Windows NT. The setup'a text form no longer uses a bugcheck procedure so as not to seriously interfere with the installation. Therefore, you will never encounter this error. All error checks have been replaced with friendlier and (where possible) more informative error messages.

0x0000008B: MBR_CHECKSUM_MISMATCH

An error occurs during the boot process when the MBR checksum calculated by the system does not match the bootloader checksum. This usually means a virus. Scan the boot sector with an antivirus program after booting from the CD.
KerBugCheckEx parameters:
1 - Disk signature in MBR
2 - MBR checksum recorded in osloader
3 - Checksum MBR recorded in the system

0x0000008E: PAGE_FAULT_IN_NON_PAGED_AREA

Incompatible or defective RAM memory blocks. Diagnose memory and replace faulty RAM modules.

0x0000008F: PP0_INITIALIZATION_FAILED

An error occurs during the initialization of phase zero of the Plug and Play manager in kernel mode. Check your hardware and system drive.

0x00000090: PP1_INITIALIZATION_FAILED

An error occurs during the initialization of the primary phase of the Plug and Play manager in kernel mode. At this point, the system files, drivers and registry have been initialized. Check your hardware and system drive.

0x00000092: UP_DRIVER_ON_MP_SYSTEM

The error occurs when a uniprocessor driver is loaded on a system where more than one active processor is present. KeBugCheckEx parameters: 1 - Base address of the uniprocessor driver

0x00000093: INVALID_KERNEL_HANDLE

The error appears when kernel code or other critical OS components try to close a handle that is not valid.
Options:
1 - Called handle NtClose
2 - 0 means the protected handle was closed
1 means the wrong handle was closed
0x00000094: KERNEL_STACK_LOCKED_AT_EXIT
This message appears when a thread exists while its stack is marked as blocked. The problem is caused by a hardware driver.

0x00000096: INVALID_WORK_QUEUE_ITEM

0x00000097: BOUND_IMAGE_UNSUPPORTED

The problem is caused by an incorrect hardware driver.

0x00000098: END_OF_NT_EVALUATION_PERIOD

The Windows demo version has ended. Options:
1 - Installation date (lower 32-bit)
2 - Installation date (upper 32-bit)
3 - Trial period in minutes.

0x00000099: INVALID_REGION_OR_SEGMENT

ExInitializeRegion or ExInterlockedExtendRegion were called with the wrong parameter set.

0x0000009A: SYSTEM_LICENSE_VIOLATION

A software license agreement violation has occurred. This could be either an attempt to change the product type of the system, or an attempt to change the OS trial period.

0x0000009B: UDFS_FILE_SYSTEM

Failed to read or write to UDFS media. The failure can be associated with damage to the file system, or with the appearance of bad sectors on the disk. Also, the failure may be associated with software that changes the structure of the disk (encryption programs, etc.).

0x0000009C: MACHINE_CHECK_EXCEPTION

Fatal Error Machine Check Exception. The error is associated with improper hardware configuration, processor overclocking, unstable operation of RAM units, overheating of system components, unstable operation of the power supply.

0x0000009F: DRIVER_POWER_STATE_FAILURE

The driver is in an inconsistent or invalid power consumption state. This usually happens due to power failures, reboots, waking from hibernation, etc. It is necessary to replace the faulty driver, or remove the software that controls the file system (antiviruses, encryption programs

0x000000A5: ACPI_BIOS_ERROR

This message is caused by persistent failures in the ACPI BIOS. This problem cannot be solved at the operating system level. A detailed analysis is required.

0x000000B4: VIDEO_DRIVER_INIT_FAILURE

Windows was unable to load the video driver. The problem is mostly related to the video drivers, or there was a hardware conflict with the video card. Reboot into safe mode and change the video driver to standard.

0x000000BE: ATTEMPTED_WRITE_TO_READONLY_MEMORY

The driver tried to write data to read-only memory (ROM), which cannot be written to. The problem is mainly related to the installation of a bad device driver, service, or firmware. Change your driver.
_MEMORY_CORRUPTION
The driver wrote data to an invalid section of memory. Change your driver.

0x000000C2: BAD_POOL_CALLER

The system kernel or driver issued an invalid memory access command. Typically, a bad driver or software has caused this error. Change your driver.

0x000000C4: DRIVER_VERIFIER_DETECTED_VIOLATION

The driver checker encountered a fatal error in the STOP error generating module. Accompanying parameters are parameters that are passed to KeBugCheckEx and displayed on a blue screen. Change your driver.

0x000000C5: DRIVER_CORRUPTED_EXPOOL

An attempt was made to access a high-level IRQL process from an invalid memory location. This error almost always occurs due to drivers that have corrupted the system pool. Change your driver.

0x000000C6: DRIVER_CAUGHT_MODIFYING_FREED_POOL

The driver tried to access a freed memory pool. Change your driver.

0x000000C7: TIMER_OR_DPC_INVALID

A kernel timer or Delayed Procedure Call (DPC) is present in a prohibited area of memory. This error occurs when the driver was unable to complete the kernel timer or Delayed Procedure Call (DPC) before unloading it from memory. Change your driver.

0x000000C9: DRIVER_VERIFIER_IOMANAGER_VIOLATION

This is a message from one of the driver verification managers. Change your driver.

0x000000CB: DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS

An error similar to STOP error 0x00000076. It differs from the latter only in that in this case the error was detected during kernel tracing. The error indicates that the driver or I / O manager cannot open locked pages after an I / O operation. Pay attention to the name of the application driver in the STOP error window. Change your driver.

0x000000CE: DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS

The driver cannot undo the stuck state of the system components. The error usually occurs after installing bad drivers or service components. Change your driver.

0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL

The system attempted to access paged memory using a kernel process through a high level IRQL. The most common cause is a bad device driver. It can also be caused by damaged RAM, or a corrupted paging file.

0x000000D8: DRIVER_USED_EXCESSIVE_PTES

The error occurs when the driver requests a large amount of kernel memory.

0x000000E3: RESOURCE_NOT_OWNED

Various crashes related to the file system lead to this STOP error. The problem may be related to the NTFS.SYS driver.

0x000000EA: THREAD_STUCK_IN_DEVICE_DRIVER

The problematic device driver has put the system into a hang state. This is usually caused by the display driver trying to enter standby mode. This problem is related to the video adapter, or a bad video driver.
A failure occurred while connecting the boot disk. The error can occur on computers with high-performance disk controllers that have not been correctly configured and installed, or are connected with a poor quality cable. After a normal reboot, the system can resume normal operation as if nothing had happened. Also, this error appears after an incorrect shutdown of Windows and the failure may be associated with damage to the file system.

0x000000F2: HARDWARE_INTERRUPT_STORM

This message appears if the kernel detects an interrupt storm, that is, when an interrupt-level device is unable to issue an interrupt request. This is usually caused by a bad device driver.

0x000000F3: DISORDERLY_SHUTDOWN

Windows shutdown crashed due to insufficient memory. Determine which program is "out of memory", try to find out why virtual memory does not provide the necessary system resources, and investigate if the program (or, sometimes, the driver) refuses to exit without freeing open pages in memory.

0x000000FA: HTTP_DRIVER_CORRUPTED

The system driver Http.sys is corrupted. It is necessary to restore this component from the original disk.

0x000000FC: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY

An attempt was made to execute a function in non-executable memory. Options:
1 - Address from which an attempt was made to execute the function
2 - Contents of the page table entry (PTE)
0x000000FD: DIRTY_NOWRITE_PAGES_CONGESTION
There is no free page memory to continue basic system operations.
Options:
1 - The total amount of requested page memory
2 - The amount of paged memory requested with the impossibility of writing.
3 —
4 - Status code at the time of the last write to page memory

0x000000FE: BUGCODE_USB_DRIVER

A fatal error has occurred in the operation of the USB controller and related devices. The problem is usually caused by incorrect operation of the USB controller, or a malfunction of the connected USB devices. Disconnect all USB devices from the computer, also try disabling the USB controller in the BIOS. Update USB drivers.

0x00000101: CLOCK_WATCHDOG_TIMEOUT

Indicates that an expected sync interrupt on a secondary processor on a multiprocessor system was not received within a specified interval. This processor does not handle interrupts. This usually happens when the processor is not responding or has entered an infinite loop.
Options:
1 - Interval of blocking interrupt time by sync pulses, in
nominal system clock ticks
2 - zero
3 - Address of the processor control block (PRCB) for non-responsive
processor
4 - zero

0x00000104: AGP_INVALID_ACCESS

An attempt was made by the GPU to write to memory that was not reserved for this. The error is related to the video driver or the old BIOS version.
Options:
1 - Offset (in ULONG) within AGP pages to first data
ULONG whose data is corrupted
2 - zero
3 - zero
4 - zero

0x00000105: AGP_GART_CORRUPTION

The error appears when the Graphics Aperture Remapping Table (GART) is damaged. The error is caused by improper operation of the DMA (Direct Memory Access) driver
Options:
1 - Base address (virtual) in GART
2 - Bias in GART where distortion is detected
3 - Base address (virtual) from GART cache (copy of GART)
4 - zero

0x00000106: AGP_ILLEGALLY_REPROGRAMMED

The error is caused by an unsigned or damaged video driver. Replace the video driver. Options:
1 - Original team
2 - Current team
3 - zero
4 - zero

0x00000108: THIRD_PARTY_FILE_SYSTEM_FAILURE

A fatal error has occurred in a third-party file system filter. The error can be caused by antivirus software, defragmentation software, data backup, and other third-party utilities. Try increasing the paging file and RAM as well.

0x00000109: CRITICAL_STRUCTURE_CORRUPTION

The system kernel has detected incorrect code or data integrity violation. 64-code based systems are immune to this bug. The problem could be caused by a malfunctioning RAM or third party drivers.

0x0000010E: VIDEO_MEMORY_MANAGEMENT_INTERNAL

An internal video driver error has been detected. Video driver problem.

0x0000010F: RESOURCE_MANAGER_EXCEPTION_NOT_HANDLED

An exception occurred in the kernel-mode resource manager.

0x00000112: MSRPC_STATE_VIOLATION

The system component msrpc.sys returned an error code during runtime. The error code is specified in the first parameter.

0x00000113: VIDEO_DXGKRNL_FATAL_ERROR

The DirectX Graphics kernel has encountered a fatal error.

0x00000114: VIDEO_SHADOW_DRIVER_FATAL_ERROR

The shadow video driver has encountered a fatal error.

0x00000115: AGP_INTERNAL

A fatal error was detected by the video port driver in the AGP video interface.

0x00000116: VIDEO_TDR_ERROR

The video driver timeout was not successfully reset.

0x0000011C: ATTEMPTED_WRITE_TO_CM_PROTECTED_STORAGE

An attempt was made to write to the write-protected area of the configuration manager: Parameters:
1 - Virtual address of the attempted write command
2 - PTE content
3 - reserved
4 - Reserved The name of the driver attempting the write operation is printed as
the unicode string on the error screen.

0x00000121: DRIVER_VIOLATION

The driver has committed an access violation to one of the memory areas. Options:
1 - describes the type of violation
2 - reserved
3 - Reserved Use a kernel debugger and view the call stack to determine
the name of the driver that caused the access violation.

0x00000122: WHEA_INTERNAL_ERROR

An internal error has occurred in the Windows Hardware Error Architecture (WHEA)

0x00000124: WHEA_UNCORRECTABLE_ERROR

An error has occurred in the hardware of the computer. This error was detected by the Windows Hardware Error Architecture (WHEA)

0x00000127: PAGE_NOT_ZERO

The memory page was not completely filled with zeros. This error occurs due to a hardware failure, or due to the activation of a privileged component of the operating system that made a premature page change in memory.
Options:

page.

3 - zero
4 - zero

0x0000012B: FAULTY_HARDWARE_CORRUPTED_PAGE

A single bit error was detected on a page of memory. This error is related to hardware RAM. Options:
1 - The virtual address in memory, which indicates an invalid
page.
2 - Physical page number
3 - zero
4 - zero

0x0000012C: EXFAT_FILE_SYSTEM

Failed to read or write to the exFat section of the media. The failure can be associated with damage to the file system, or with the appearance of bad sectors on the disk. Also, the failure may be associated with software that changes the structure of the disk (encryption programs, etc.). This failure applies to media formatted for Windows Vista Service Pack 1.

0x1000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
0x1000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
0xC000009A: STATUS_INSUFFICIENT_RESOURCES

The system kernel of the operating system has exhausted all system resources for its work, including the paging file. Check the disk for errors. Expand your hard disk and RAM.

0xC0000135: UNABLE TO LOCATE DLL

Windows tried to load DLL and got error code. Possible cause - the file is missing or damaged. The system registry may also be damaged.

0xC0000142: DLL Initialization Failure

This error was caused by a damaged system DLL.

0xC0000218: UNKNOWN_HARD_ERROR

The required registry file cannot be loaded. The file may be damaged or missing (rescue disk or Windows reinstallation required). The registry files may have been corrupted due to damage to the hard drive. The driver may have corrupted the registry data when loaded into memory, or the memory where the registry was loaded has a parity error (turn off the external cache and check the RAM).

0xC000021A: STATUS_SYSTEM_PROCESS_TERMINATED

This occurs when Windows has switched to privileged mode and non-privileged mode subsystems such as Winlogon or Client Server Runtime Subsystem (CSRSS) have caused some kind of failure and protection cannot be guaranteed. Because Windows XP cannot function without Winlogon or CSRSS, this is one of the few situations where a non-privileged mode denial of service can cause the system to stop responding. This can also happen when the computer is restarted after the system administrator changed the permissions so that the SYSTEM account no longer has adequate permissions to access system files and folders. The error can also be caused by a damaged user32.dll file or incorrect system drivers (.sys)

0xC0000221: STATUS_IMAGE_CHECKSUM_MISMATCH

the driver is damaged or the system library has been recognized as damaged. The system does everything to check the integrity of important system files. The blue screen shows the name of the damaged file. If this happens, boot into any other system or, if there are none, reinstall the system. Make sure that the version of the file that was detected as damaged matches the version of the file in the system distribution, and if so, replace it from the disk. Persistent errors with different file names indicate that there are problems with the storage media or with the disk controller where these files are located.

0xC0000244

STOP error occurs when audit policy activates the CrashOnAuditFail parameter

0xC000026C

Usually indicates a problem with a device driver. More information about this error

0xDEADDEAD: MANUALLY_INITIATED_CRASH1

"It's dead, Jim!" (It's dead Jim!) This STOP error indicates that the user intentionally initiated the crash, either from the kernel debugger or the keyboard.

Here is a small list of errors that can appear in the operating systems Windows NT 4.0, Windows 2000, Windows 2003, Windows XP, Windows Vista and Windows 7. Everyone is afraid of the blue screen of death, but in fact, if it did not exist, the computer would simply break down. , and you would have to send your equipment for repair, or buy new, or maybe even the whole computer. So let's pay tribute to the developers of this operating system who take care of our wallets. This is where we end our conversation about the famous " Blue screen of death».

Windows blue screens of death ( B lue S creen o f D ead) did not come across, perhaps only a rare lucky one. Most of us had the "good fortune" to contemplate this phenomenon on our own PC. And it drives many people into panic: what if the computer is lid?

In order not to get lost when a blue "lantern" suddenly flashed on the screen, you need to be able to look the enemy "in the face". That is, learn how to find out what led to the emergence of BSoD, assess how critical the situation is and know what to do so that it does not repeat itself.

Blue light turns on unexpectedly

In the course of Windows operation, a lot of errors occur, the bulk of which are eliminated by the system unnoticed by the user. But some of them are so serious that the continuation of the session becomes impossible. Either the problem that has arisen threatens Windows or the hardware with permanent damage. In such cases, BSoD pops up. The system seems to say to the user: “Sorry, friend, but I had no other choice. If it hadn't been for the abnormal termination, something bad would have happened. "

Blue screens of death occur at any stage of the computer boot and operation. And the following leads to them:

Incorrect operation of device drivers due to poor compatibility with the operating system, conflict with other drivers, damaged or changed parameters.
Incorrect operation of software, more often the one that creates its own services - antiviruses, firewalls, equipment emulators, etc.
Infection with malware.
Hardware problems - malfunction of RAM, disk drives, network, sound adapters, video subsystem, motherboard, power supply and other equipment.
Abnormal operation of devices - overheating, unstable power supply, overclocking.
Disruption of data exchange between devices - poor contact in connectors, faulty cables and loops.
Device incompatibility.

By the way, a one-time BSoD after connecting a new device to the computer, if in the future everything works flawlessly, can be considered the norm.

What can you learn from the information on the blue screen

Fortunately, the vast majority of blue screens of death are caused by software glitches, which the user can fix on their own and relatively quickly, without having to reinstall Windows. Software problems are characterized by random BSoDs with the same or similar error codes.

Hardware "bruises" often occur under the same conditions (for example, when the load on the video card increases, when you try to open a large file) and have different codes. Or, these codes indicate problems with specific equipment, such as: errors in accessing the device, inability to read, recognize.

However, these indications only allow one to make an assumption about the cause of the problem. More detailed information is needed to clarify it.

Windows 10 Blue Screen of Death looks like this:

Information about the error in it is carried by the line “ Stopcode". In my example, this is CRITICAL PROCESS DIED.

Having scanned the QR code with your phone, which is located here, you can go to the site windowscom / stopcode, which contains general troubleshooting tips. Hints from Microsoft are sometimes useful, but there is nothing about the reason for your specific case, which means that you will have to look for this data in another source, for example:

On computer forums.
References for various error codes, in particular on the Docs.Micosoft website and elsewhere.

But this is not entirely complete information. Each error is unique, and the most accurate information about it is contained in a file that the system saves to disk at the time of the failure. Namely - in a small memory dump, which we will learn to analyze. And in order for such files to be created, you need to make a few small settings.

How to enable the function of creating and saving small memory dumps

To save memory dumps on the hard disk, the system must be located in the same partition as the Windows folder. Its size can be 2 Mb or more.

Go through the context menu to the properties of the folder " A computer».

Click in the window that opens the button " Additional system parameters».

"Click the button" Options».

In the new window section “ System failure" from the list " Writing debug information»Select« Small memory dump". Let it be indicated as the save location «% SystemRoot% \Minidump"(% Systemroot% is the Windows folder).

This completes the setup. Now information about BSoDs will be saved in the above directory.

How to analyze the content of minidumps

There are different ways to analyze Windows crash memory dumps, but we will get acquainted with the most, in my opinion, convenient and simple - with the help of a free utility BlueScreenView .

BlueScreenView is especially convenient in that it does not require the installation of bulky Debugging Tools for Windows packages on the computer and can be launched from any media, just click on the file of the same name.

The interface of the utility, despite the absence of the Russian language, is very friendly. The main window is divided into 2 halves. Above - a table of minidump files from the Windows \ Minidump folder with the date and time of creation (column Crash Time), error code in hexadecimal format (column Bug Check Code), its four parameters and other information. However, it is more convenient to view the data on a specific failure in a separate window, which is opened by double-clicking on the line of interest (shown below). The main window gives more information about the problem as a whole, if BSoD's happened more than once. It is easy to track the dates of incidents and error codes, by the recurrence of which you can judge the nature of the problem.

The lower half of the main window displays the drivers loaded into memory at the time of the emergency for a specific dump selected in the list. The lines highlighted in pink show the contents of the event flow stack, and the drivers mentioned in them are most directly related to the cause of the failure.

Let's analyze, for example, one of the small memory dumps with error code 0x00000154. I will say in advance that it was caused by a kinked hard disk cable. To begin our analysis, let's take a look at the list of drivers in the event stack. There is nothing here except ntoskrnl.exe - the Windows kernel, which, of course, is not to blame for the problem - it is just that during the failure there was not a single driver in the stack, but it is always present there.

Move on. According to the Microsoft website, error 0x00000154 occurs when "a storage component encounters an unexpected exception" and is usually associated with a drive problem.

To check this version, let's evaluate the S.M.A.R.T indicators of the hard disk of the computer, which are monitored by the Hard Disk Sentinel program. On the day of the accident, there were changes to the following attributes:

188 Command Timeout.
199 UltraDMA CRC Error Count.

Both indicate errors in the transmission of data on the interface cable. The hard surface test and checking the file structure did not reveal any deviations, so the problem was solved by replacing the cable.

Consider another case of a blue screen of death caused by Kaspersky antivirus. BSoD intermittently occurred during Windows 10 startup and when the computer woke up from hibernation.

The error was recorded several times under the same code - 0x000000d1, which means the following: "a kernel-mode driver tried to access a memory page in an IRQL process that had too high priority." This time BlueScreenView pointed out a problem in the NDIS.sys driver for network connections. This means that there is a high probability that the failure is of software origin and is related to something that is using the network.

To identify the culprit, it was necessary to analyze the startup of applications. At the early stage of the launch of the operating system of this PC, not too many programs were launched that were allowed access to the Internet, more precisely, one Kaspersky. To confirm his involvement, I again turned to the list of drivers loaded into the memory in BlueScreenView and among what is usually present here, I found kl1.sys, which belongs to the antivirus.

After uninstalling Kaspersky, blue screens no longer popped up.

The BlueScreenView utility allows you to analyze crash memory dumps obtained not only where it is running, but also on another computer. To do this, you do not need to copy them to the Windows \ Minidump folder of your PC, which is loaded into the program by default. Copy them to any convenient place, for example, on the desktop, and tell the program the new location of the directory to be loaded.

The function of selecting a folder with dump files is located in the menu “ Options» – « Advanced options"(Opened by the keyboard shortcut Ctrl + O) and is called" Load from the following minidump folder».

After checking the box, click the button " Browse»And find the required directory in the explorer. When you want to return to the default settings, click " Default».

This is how, in a matter of minutes, you can find out the cause of almost any Windows blue screen of death, and by examining the minidumps in aggregate, you can identify the source of the problem and successfully fix it. By the way, you can find hints about which driver belongs to which. There are also recommendations for solving related problems.

The Blue Screen of Death is familiar to every user of Windows operating systems. For some users, it appears so often that they begin to think that this is normal. But this is not the case. Let's see what the blue screen of death is. This is an error that appears during startup or after an abrupt shutdown of the computer. It indicates that there are problems with the operating system or internal hardware. Only by understanding the causes of occurrence, you can eliminate it as efficiently as possible.

If a blue screen of death appears on a computer with Windows 7, then we bring to your attention this article, it will definitely help you find and fix this problem.

Blue screen of death, its causes

The reasons for the appearance of a blue screen can be divided into two main groups:

Systemic... Problems with the operating system: there are no necessary files required for the correct operation of Windows, an incorrectly installed OS, infection with malicious software or a file, and so on.
Hardware... Problems with computer hardware: malfunction of the hard drive or video card, overheating of the processor, and so on.

In order to accurately determine the cause of the error, you must carefully study the content of the blue screen. After all, it is on it that all the information the user needs is indicated, namely: the reason for the error and even recommendations for its elimination.

If the information that is indicated on the screen is not enough, then the computer can be configured specifically to diagnose the blue screen of death.

File corruption win32k sys provokes a blue screen. Therefore, be sure to check and scan other directories.

Diagnostics

Windows blue screen or memory dump is a reflection of the working (or not quite) state of the operating system at a certain period of time. Since immediately after the appearance of a critical error, after which an abrupt shutdown of the device may follow, Windows displays all the necessary information on the famous blue screen, then for further diagnostics you just need to remember it: rewrite or photograph.

The main trouble is that the blue screen is shown for a strictly limited time. Then the reboot mechanism starts. Therefore, an unprepared user who does not know where to look may find it difficult to have time to rewrite the necessary information.

To disable auto-restart of the device, that is, when the computer or laptop immediately starts to reboot, immediately after the blue screen of death appears, it is necessary to activate the recording of small memory dumps, that is, part of its important content. This requires the following steps:

Now the blue screen of death when Windows 7 boots up will not immediately disappear, so you will have time to rewrite the necessary information.

Decoding the error

Since any problem can cause the blue screen of death, it is necessary to identify it in order to fix the error.

As soon as you managed to take a picture of the blue screen when Windows boots or write down the information that appears on it, you can proceed to decrypting the error that caused it:

The first line of the system in English politely notifies that a critical shutdown of Windows has occurred.
It goes on to explain what exactly caused the problem. This can be the name of a file or driver for a video card, audio card, TCPIP.SYS, SPCMDCON.SYS, DXGKRNLl.SYS, NTKRNLPA.EXE, NETIO.SYS, and so on. If this line is missing, then the cause of the error should be looked for in the computer hardware.
A user-readable error name such as DRIVER_IRQL_NOT_LESS_OR_EQUAL indicates that an error occurred while installing the driver.
This is followed by a large body of text in which Windows suggests a possible solution to the problem. For example, check if the drivers were installed correctly, start the check disk service, perform a system restore, and so on.
After the word STOP, the technical error code is indicated for more accurate identification and elimination. It can look like 0x1000007e, 0x00000116 and the like.
Below the system may re-indicate the names of files or drivers, such as TCPIP.SYS, SPCMDCON.SYS, NTKRNLPA.EXE, NTOSKRNL.SYS, NETIO.SYS and the like, which could have provoked a blue screen.
Additionally, depending on the type of problem, Windows may display the memory address at which the critical error occurred. By analogy with the STOP code, it will probably have a format like Address 0x00000116.

Knowing this information, it becomes clear how to remove the blue screen of death.

Problems with a blue screen in 90% of cases are the most commonplace and appear among users who are poorly versed in computers, therefore they often neglect the installation of system updates, drivers, the correct procedure for uninstalling programs, and so on.

Damage to the acpi sys file can cause a blue screen, so to fix the error, you must replace it with a workable one.

Even if the screen says that the error was caused by files like tcpip, ntoskrnl, fltmgr, netio, ntkrnlpa, the first thing to do is:

It will not be superfluous to defragment, check and clean the registry. This is best done using special software. One of these programs is.

With its help, it is also possible to check the presence of all files and libraries necessary for the stable operation of the operating system. If some of them are missing or damaged, the program will offer to download and replace them. If you wish, you can make a copy of the original files and save them in any convenient place on your hard drive.

Death screen when booting or installing Windows

If you do not know how to remove the blue screen of death when installing Windows 7, then carefully read the following information. This error can occur only in three cases, if:

faulty x64 operating system image;
working image, but faulty hardware (error 0x00000116, IGDPMD64.SYS, fltmgr, ntoskrnl);
BIOS setup was incorrect.

If, during the installation of Windows XP, the blue screen repeats over and over again, but you are sure that the computer hardware is in order, then the problem most likely lies in the faulty operating system image that you are using.

A blue screen during Windows installation or recovery can occur due to a faulty internal storage device (HDD) or incorrect formatting. Do not neglect the standard procedure for checking the operability of the used OS image, disk or flash drive. All this information can be found on the screen. You fix other problems in the same way.

Missing or damaged system files

If you are not sure how to remove the blue screen of death due to missing or corrupt system files or libraries such as TCPIP.SYS, SPCMDCON.SYS, IGDPMD64.SYS, fltmgr, DXGKRNLl.SYS, NTKRNLPA.EXE, NETIO.SYS or error 0x00000116 then this method is for you. It is also suitable for errors caused by other files with extension .SYS, .DLL, .EXE. To do this, you can use a special third-party shareware utility. One of the most popular is.

After installing the program, you need to launch it and start scanning using the Start button. Next, the utility will offer to scan files like ntoskrnl, dxgkrnl, igdpmd64, fltmgr, tcpip, netio, ntkrnlpa. Additionally, the program will check other directories as well. If you are sure that it was the nvlddmkm sys file that caused the blue screen of Windows 7 or any other, the name of which you should know for sure, then you can check it.

As soon as the scan is finished, it will offer:

replace the file if it really was damaged;
proceed to check the rest of the system files if the specified file is not damaged;
only delete the faulty file if you want to replace it yourself;
do nothing, but open the folder with the damaged file to solve the problem yourself.

Optionally, you can install other applications to automatically search for damaged system files and replace them. Some of them similarly identify and fix driver problems.

Reset BIOS

If you have recently made BIOS changes or tried to overclock the processor, then this may be the cause of the problem. Therefore, you should definitely try to return its default settings. This can be done in several ways:

Conclusion

And this article was considered: what is the blue screen of death, its causes. An explanation of the errors was given, as well as various options for eliminating the resulting breakdowns were proposed. Now, if you see the Windows 7 death screen again, then you already know what to do.

What is this mistake

What is Windows telling us on the horrible blue screen of death?

Causes of the Blue Screen of Death