Quite a few users have encountered the phenomenon of blue screen of death. Not everyone knows what to do (Windows 7 is most often susceptible to such trouble) in this situation. And therefore the sight of a blue screen is terrifying. However, sometimes error codes help correct the situation. They indicate a problem. And based on it, you need to make certain decisions regarding the treatment of the computer. Today we will learn how to deal with some of the causes of a blue screen, and also find out what should be done to eliminate this problem once and for all. Some advice from professional system administrators often helps even the average user overcome problems. Let us begin to study our current problem as soon as possible.

What's happened

But let's start by figuring out what we're going to be dealing with. Only after this will it be possible to think about how to remove the blue screen of death. To be honest, this issue requires special attention.

So, what kind of phenomenon will we become aware of today? death is a kind of system error. And it appears when the operating system boots or directly during operation. In this case, you get a blue screen for a while. Hence the strange name. Blue screen of death codes are written on it. More precisely, codification of the errors that have arisen. Based on them, you can figure out what is causing the problem. And sometimes even eliminate it.

But, as practice shows, a blue screen of death or some other) is the first sign that your computer is going into oblivion. This means that he will have to be treated quickly. We can say that our phenomenon is a demonstration that the operating system and hardware of the device refuse to work. Therefore, it is worth knowing how to behave in a given situation. Let's try to find out what can be done.

Screen problem

Let's get you started by learning about some common blue screen of death error codes. After all, they will help you not to be scared when it appears, but to quickly move on to decisive action. For example, quite often a blue screen of death occurs, error code 0x00000116. There is no need to be afraid of this phenomenon.

The thing is that this codification indicates that when loading the operating system, an attempt was made to reset and restart the display driver. And since we got an error, the action didn’t work. This problem can be solved in many ways. But there are some tips that will help you save your data as well.

First, you should try to reinstall the drivers on your computers. And that's all. And start with those related to the monitor and video card. Also, update your codecs. This helps a lot.

It would also be a good idea to disable antivirus programs when errors appear. Sometimes they cause a blue screen of death. What to do? Windows 7, as you know, is most susceptible to this phenomenon. This means that you will have to be very careful with antiviruses in it.

System boot

There is no point in listing all the blue screen of death codes. Windows 7 will give you errors when errors occur. And then, based on the data obtained, it will be possible to use a special directory of computer errors. This lists all the codes that relate to a blue screen. But still, we will look at one more option.

Quite often this blue screen of death appears: 0x0000007b. This error always occurs immediately when the computer boots. If the previous option can appear while working with programs, applications, games, then this one always “does not allow” Windows.

Code 0x0000007b indicates that access to the system partition of the hard drive was lost while the computer was booting. The reasons can be different - from a banal virus to major damage to the iron. But this problem always needs to be fixed.

Reinstalling Windows with full formatting and redoing the hard drive partitions helps here. But sometimes the problem does not go away even after such a radical step.

In this case, download the latest system configuration. To do this, when you boot your computer, press F8, then select “Last Known Known Configuration.” The computer will boot. You can be happy with the result.

Check the compatibility of the hard drive and other hardware. If there is any discrepancy, replace the components. After this the problem will disappear. Often, code 0x0000007b appears after connecting a new or additional hard drive.

Rollback

Now it’s worth learning the general provisions on how to remove the blue screen of death. Sometimes all the advice turns out to be quite effective, regardless of the error that occurs. And the first option that can be recommended is to perform a system rollback. The technique is relevant when the system boots initially.

In order to rollback, you need to go to “Start”, “All Programs”. Next, find the “Standard” section there, and from there go to “Service”. Select "System Restore". A window will appear in front of you with a welcome message and a warning that the process is irreversible. Agree and select a rollback point in the next menu that opens - to the moment when the computer was not bothered by the blue screen of death. Click "Next" and wait for a while.

During the entire process, the computer will reboot itself about 2-3 times. This is fine. After the rollback, some settings should be reset. But all programs and personal data will remain in perfect order. Quite often, this technique helps to permanently eliminate the problem.

Checking the contents

If you suddenly have a blue screen of death, you don’t know what to do (Windows 7 or any other operating system), then it’s time to check the configuration of your computer. Sometimes even an old cable can cause a lot of inconvenience. Particular attention should be paid to components in cases where you have recently changed something in your computer.

As already mentioned, often problems with the blue screen of death arise due to a hardware conflict. This may even apply to a flash drive. So be careful. If you suspect a hardware conflict in your computer and do not have the necessary knowledge about compatibility, it would be better to take your device to a specialized computer help service. They will help you quickly fix the problem.

In general, carefully study the compatibility of all components on your computer. This will help you avoid many problems. It will also prevent you from seeing the blue screen of death. Why else does it occur? And how to deal with it?

Overheat

For example, sometimes this phenomenon occurs when the computer or processor overheats. In the case of stationary options, everything is fixed quickly and easily - either an additional cooler is installed, or the hardware is cleaned (or it is better to start from this point), or it is completely removed from the case for greater air penetration.

But the blue screen of death on a laptop due to overheating is already a serious problem. Firstly, the device will have to be taken to a computer service for cleaning. Secondly, you may additionally need to install a cooler (and this service is not that cheap). Third, put less load on your computer while working. This will help avoid overheating and its consequences.

Applications

For some unknown reason, did you experience a blue screen of death? What to do? Windows 7 is an unsurpassed leader in this regard. And it was also in this operating system that application conflicts and their incompatibility with each other began to arise. This may be a consequence of the appearance of the death screen.

What to do in this case? First, remember after installing which program the problems started. After that, set the compatibility parameters. Sometimes this technique helps. But you shouldn’t rely too much on it.

If compatibility mode does not help, then uninstall the installed application. Don't want to spend a long time dealing with the problem? In this case, if you have nothing to lose, then simply reinstall the entire operating system. In this situation, this is often the best solution.

Update

Some users complain about the appearance of a blue screen of death after updating the operating system using the built-in center. If you notice that all the troubles started after this, you will have to do a system rollback and also disable process automation.

Go to Windows Update. There, go to settings. Select the option that is marked as "not recommended." That is, do not automatically check, download and install updates. Never. This will help avoid many problems in the future. And they will not necessarily be associated with the blue screen of death.

Drivers

Another problem that can arise and cause our current phenomenon is nothing more than hardware drivers. Sometimes they are the ones that cause the blue screen of death. What to do? Windows 7 offers a fairly fast, simple and secure solution. This is nothing more than reinstalling all existing drivers and updating them in a timely manner.

To prevent the process from causing inconvenience, it is best to use the official websites of manufacturers to download applications. They will not introduce infection to your computer. And there is always only high-quality content. After updating and installing all drivers, it is better to restart your computer. That's all. Now you will notice that the Blue Screen of Death problem will disappear. But this doesn't always happen. After all, there are other reasons for this phenomenon.

Antivirus

Occasionally there are situations in which a blue screen of death appears for no apparent reason. What to do? Windows 7 or any other operating system - it doesn't matter. The main thing is that there is one small but - this is an antivirus. If you have it, then it's worth turning it off for a while. Or delete it altogether. And watch the computer. After all, sometimes it is this application that causes the blue screen of death.

Most often, owners of Avast and Kaspersky suffer from this phenomenon. As a last resort, replace the antivirus. Did it help? You can rejoice. No? Then completely remove the antivirus, and then take the computer for repair. Tell us about the problem - professionals will definitely help you there.

Viruses

And of course, the blue screen of death can appear due to viruses on the computer. Some infections are aimed at just this. Indeed, with this phenomenon, the entire operating system is destroyed. Do you suspect an infection? Then take your computer and treat it.

Scan it with antiviruses, antispyware and other healing content. Cure all dangerous objects, and then remove those that did not respond to the process. Usually this is enough. Also clean your computer's registry - this is important. Now look at the result. If all is useless, then reinstalling the operating system will help. But it's worth trying a rollback first.

With Windows blue screens of death ( B lue S creen o f D ead) has not come across, perhaps, only a rare lucky person. Most of us had the “fortune” to witness this phenomenon on our own PC. And it drives many people into panic: what if the computer is dead?

In order not to get lost when a blue “lantern” suddenly lights up on the screen, you need to be able to look the enemy “in the face.” That is, learn to find out what led to the appearance of BSoD, assess how critical the situation is and know what to do so that it does not happen again.

Blue Lantern turns on unexpectedly

During the operation of Windows, many errors arise, most of which the system eliminates without the user noticing. But some of them are so serious that continuation of the work session becomes impossible. Or the problem that has arisen threatens Windows or hardware with irreversible damage. In such cases, BSoD appears. The system seems to be telling the user: “Sorry, friend, but I had no other choice. If it weren't for the crash, something bad would have happened."

Blue screens of death occur at any stage of computer startup 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, damage or changes in parameters.
  • Incorrect operation of software, most often those that create their own services - antiviruses, firewalls, hardware emulators, etc.
  • Malware infection.
  • 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.
  • Violation of data exchange between devices - poor contact in connectors, faulty cables and cables.
  • 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 that the user can fix independently and relatively quickly, without resorting to reinstalling Windows. Software problems are characterized by random BSoDs with the same or similar error codes.

Hardware “bruises” more often occur under the same conditions (for example, when the load on the video card increases, or when trying 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 signs only allow us to make an assumption about the cause of the problem. To clarify it, more detailed information is needed.

The Windows 10 Blue Screen of Death looks like this:


The error information is contained in the line “ Stopcode" In my example this is CRITICAL PROCESS DIED.

By scanning the QR code located here with your phone, you can go to the website windowscom/ stopcode, which contains general tips for troubleshooting. Tips from Microsoft are sometimes useful, but there is nothing there about the cause of your specific case, which means you will have to look for this data in another source, for example:

  • On computer forums.
  • In 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 the 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. In order for such files to be created, you need to make several small settings.

How to enable the feature to create and save small memory dumps

To save memory dumps on your hard drive, the system definitely needs one, which must be located in the same partition as the Windows folder. Its size can be from 2 Mb or more.

  • Go through the context menu to the folder properties " Computer».


  • Click the button in the window that opens Advanced System Settings».


» press 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 contents of minidumps

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

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


The utility interface, despite the lack of Russian language, is very friendly. The main window is divided into 2 halves. At the top is a table of minidumps - 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 data about a specific failure in a separate window, which opens by double-clicking on the line of interest (shown below). The main window gives more information about the problem as a whole if BSoDs have occurred repeatedly. It makes it easy to track the dates of incidents and error codes, the frequency of which can be used to 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 highlighted in the list. The lines highlighted in pink show the contents of the event stream stack, and the drivers mentioned in them are most directly related to the cause of the failure.

Let's look at one of the small memory dumps with error code 0x00000154 as an example. Let me say in advance that it was caused by a broken hard drive cable. Starting the analysis, let's look at the list of drivers in the event stack. There is nothing here except ntoskrnl.exe - the Windows OS kernel, which, of course, is not to blame for the problem - it’s just that at the time of the failure there was not a single driver in the stack, and it is always present there.



Go ahead. According to Microsoft's website, error 0x00000154 occurs when "a storage component encounters an unexpected exception" and is typically associated with storage issues.

To test this version, let's evaluate the S.M.A.R.T indicators of the computer's hard drive, which are monitored by the Hard Disk Sentinel program. On the day of the accident, changes in the following attributes appeared here:

  • 188 Command Timeout.
  • 199 UltraDMA CRC Error Count.


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

Let's look at another case of a blue screen of death caused by Kaspersky Anti-Virus. BSoD occurred intermittently during Windows 10 startup and when the computer resumed from sleep mode.

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


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


After removing 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 on your PC, which is loaded into the program by default. Copy them to any convenient location, for example, on your desktop, and tell the program the new location of the directory that should be downloaded.

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


Having checked the box here, click the button “ Browse" and find the desired directory in Explorer. When you want to return the settings to default, 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 their entirety, you can identify the source of the problem and successfully fix it. By the way, you can find hints about which driver belongs to what. Recommendations for solving related problems are also provided there.

In this article we will talk about such a phenomenon in the Windows operating system as - Blue Screen of Death or in our opinion blue screen of death", also called STOP error. Let's look at the main causes and decipher these error codes.

First, let's define what " Blue Screen of Death"is a way to generate a fatal error message in the operating systems Windows NT 4.0, Windows 2000, Windows 2003, Windows XP, Windows Vista and Windows 7 caused by malfunctions of some programs or drivers, but still more often due to hardware failures of the computer.

A blue screen causes all processes in the operating system to stop and the computer to freeze after the blue screen is displayed. In general, the blue screen helps us, you may ask, in what way, but in that it prevents the destruction of the operating system and the failure 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 corruption 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 may already be a problem related to the computer’s hardware, for example, damage to the drivers, file system, hard drive, or RAM memory blocks. But to find out the reasons for the error that occurred, it is necessary to rewrite the first two output 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 on every time).

To enable this option, go to the properties of “My Computer”, select the “Advanced” tab. In the "Boot and Recovery" field, click the "Options" button. In the window that appears, uncheck the box next to “Perform automatic reboot.”

When a STOP error appears, the text of the message briefly describes the method for solving it, albeit in English. But I can say for sure that currently the common cause of STOP errors is hardware problems with the computer hardware or its software parts, and sometimes due to inconsistencies between one and the other.

Now let's move on directly to the errors themselves and look at the reasons for their occurrence and short solutions.

0x00000001: APC_INDEX_MISMATCH

Internal kernel error. The problem is most often associated with a driver problem, lack of RAM or hard drive space.

0x0000000A: IRQL_NOT_LESS_OR_EQUAL

There was virtual memory interference on a high-level internal IRQ process. The most common cause is that the device driver is 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:

  1. Address where the erroneous request was made
  2. IRQL that was used to access memory
  3. Memory access type: 0 = read operation, 1 = write operation
  4. Address of the instruction that requested memory access at address

0x0000001E: KMODE_EXCEPTION_NOT_HANDLED

This is a very common mistake. Typically the excluded address points to the driver or function that caused the freeze screen. Always pay attention not only to the specified driver, but also to the address or image itself that contains this error. This is usually the exception code 0x80000003. This error means that a breakpoint or handler was initialized during a memory access, 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 your processor manufacturer.
Typically, you need to look at the second parameter of this message, which indicates the address of the driver/function that was causing the problem.
Options:

  1. Exception code
  2. Address that failed to process
  3. Parameter 0 - exception
  4. Parameter 1 - exception

0x00000020: KERNEL_APC_PENDING_DURING_EXIT

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

  1. APC address at the time of failure.
  2. Failed APC thread
  3. 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 with the format NTFS. The failure may be due to damage to the file system, or to the appearance of bad sectors on the disk. The failure may also be due to software that changes the disk structure ( encryption programs, etc.).

0x0000002A: INCONSISTENT_IRP

I/O Request Packet (IRP) is not functioning; Occurs when a field or multiple fields are incorrect compared to the preserved 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. A possible cause of the error could also be damage to the kernel itself.

0x0000002E: DATA_BUS_ERROR

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

  1. Virtual memory address that caused the error
  2. Physical address of the error cause
  3. Processor Status Record (PSR)
  4. Error Instruction Logging (FIR)

0x00000031: PHASE0_INITIALIZATION_FAILED

System initialization could not be completed at an early stage (phase 0). It is necessary to study the error in more detail, since this error code says practically nothing.
0x00000032: PHASE1_INITIALIZATION_FAILED
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 says practically nothing.
Options:

  1. System level code that describes why the system believes that initialization has not completed
  2. Indicates the location within INIT.C where phase 1 initialization failed

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 a fatal situation because the high-level driver thinks it has filled in the parameters for the low-level driver (something it had to do to call the low-level driver). However, since there is no free space in the stack area, the end of the packet was overwritten. This often occurs 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 hit counter of this component was not equal to zero - this means that there are some outstanding tasks behind this component (the counter indicates an error code, which is why this component cannot be unloaded). This is a driver call error.
Options:
1 — object address

0x0000003E: MULTIPROCESSOR_CONFIGURATION_NOT_SUPPORTED

A multiprocessor system is not symmetrical with respect to each other. For proper 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 generate an error. In addition, on x86 systems, floating point capabilities must be available on all processors or on none.

0x0000003F: NO_MORE_SYSTEM_PTES

There are not enough PTE (page file entries - access points to the paging file). Usually the cause is a driver that does not clean out the swap file well and it becomes full. The cause may also be excessive fragmentation of the paging file.

0x00000040: TARGET_MDL_TOO_SMALL

The driver called IoBuildPartialMdl() and passed the MDL to it to reveal the source portion of the MDL, but the destination MDL area is not large enough to show the limits of the required addresses. This is a driver error.

0x00000041: MUST_SUCCEED_POOL_EMPTY

The system driver has requested space 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:

  1. Amount of request required
  2. Page number used
  3. Number of pages requested
  4. Number of available pages

0x00000044: MULTIPLE_IRP_COMPLETE_REQUESTS

The driver requested completion of the IRP, but the packet was already completed. This error is difficult to detect. A possible cause is that the driver is trying to complete the same operation multiple times. A rare cause is 2 different drivers trying to acquire the package and terminate it. The first one usually works, but the second one doesn’t. It is difficult to track which driver did this, since 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) that must be terminated has a cancellation order defined within it, i.e. this means that a package in this mode can be canceled. However, the package no longer belongs to the driver, since it has already entered the final stage.
Options:
1 - IRP address

0x00000049: PAGE_FAULT_WITH_INTERRUPTS_OFF

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

0x0000004C: FATAL_UNHANDLED_HARD_ERROR

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

0x0000004D: NO_PAGES_AVAILABLE

There is no more free page memory to complete the operation. Check the available disk space. Replace the driver. Options:

  1. Number of pages used
  2. Number of physical pages on the machine
  3. Extended page size
  4. Overall page size

0x0000004E: PFN_LIST_CORRUPT

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

  1. Value 1
  2. ListHead value that is corrupted
  3. Number of available pages
  1. Value 2
  2. Data that is deleted
  3. Maximum number of physical pages
  4. Summary of deleted data

0x00000050: PAGE_FAULT_IN_NONPAGED_AREA

Occurs when the requested information was not found in memory. The system checks the page file, but the missing information was indicated as not being able to be written to the page file.
Options:
1. indicates the address in memory that made an error

0x00000051: REGISTRY_ERROR

An I/O error occurred with the registry when the system tried to read one of its files, which suggests that the error could be caused by a hardware problem or damage to the system itself. This could also mean that the error is caused by an update operation that is only used by the security system and this error occurs when resources are running low. If such an error occurs, check whether the machine is PDC or BDC and how many accounts are in the SAM (Security Account Manager) database, and whether 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 HvCheckHive's return code, if any
library is damaged

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 ok, but in fact it is not. The real library images are in the shadow copy. You need to boot from them.

0x00000067: CONFIG_INITIALIZATION_FAILED

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

0x00000069: IO1_INITIALIZATION_FAILED

The I/O device failed to initialize for an unknown reason. This happens if the system installer incorrectly identified the equipment during the system installation process, or the user incorrectly reconfigured the system.

0x0000006B: PROCESS1_INITIALIZATION_FAILED

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

0x00000073: CONFIG_LIST_FAILED

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

0x00000074: BAD_SYSTEM_CONFIG_INFO

This error may occur because the SYSTEM registry file loaded through the NTLDR component is corrupted.
This error may also mean that some required parameters and their parameters are missing. Loading into LastKnownGood may solve this problem. But it is possible that you will have to reinstall the system, or use a 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) during the first phase of registry initialization (when file systems are accessed). 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 may occur due to 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 is a bad block of the virtual memory file or a disk controller error (very rarely, the cause may be a lack of system resources, or more precisely, the non-virtual memory reserve may run out with status c0000009a).
If the first and second parameters of the error code are 0, then this means that the error location 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 that the information cannot be read due to a bad block in memory. After reboot, 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 the error
4. kernel error address or

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

0x00000079: MISMATCHED_HAL

The HAL check level and 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. Either the machine has 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. stuck lock type
2. error status (usually I/O code)
3. current process (virtual address for blocking type 3 or PTE)
4. virtual memory address that cannot be moved to the page file

0x0000007B: INACCESSIBLE_BOOT_DEVICE

During the installation of an I/O system, the boot device driver may have failed to initialize the device from which the system was attempting to boot, or the file system that was supposed to read the device either failed to initialize or simply did not recognize information on the device, such as file system structure. In the above case, the first argument is the address of a unicode information structure, which is the ARC name of the device from which the attempt was made to boot. 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, the system may have been installed on a disk or SCSI controller that is not supported by it. Please note that some controllers are only supported by Windows Driver Driver 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 system partitions. In this case, on x86 systems, you need to edit BOOT.INI.
Options:
1. pointer to a device object or Unicode string, or ARC name.

0x0000007D: INSTALL_MORE_MEMORY

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

0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

There is a hardware problem, driver problem, or low disk space detected. The error may also appear when trying to update Windows XP to Service Pack 2 or Service Pack 3, or Windows Vista when trying to update to Service Pack 1. The cause of the error may be related to hardware drivers. It is necessary to roll back the changes to the state at the time of installing the Service Pack, or remove 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, occurred in which the kernel does not fire. Also, the cause of the error can be an interruption, which entails immediate death in the form of 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, the error appears when the processor makes an error that the kernel cannot handle. Most often, the error occurs due to bad RAM blocks, and sometimes due to overclocking the processor.
Try disabling the synchronous data transfer function in the BIOS.

0x00000080: NMI_HARDWARE_FAILURE

Error initializing the kernel on this hardware. HAL should provide any specific information it has and encourage the user to contact the hardware vendor for technical support.

0x00000085: SETUP_FAILURE

An error occurs when loading the system installer in earlier versions of Windows NT. The setup text form no longer uses a bugcheck procedure to avoid causing serious interference during installation. Therefore, you will never encounter this error. All error checking has been replaced with friendlier and (where possible) more informative error messages.

0x0000008B: MBR_CHECKSUM_MISMATCH

The error occurs during the boot process when the MBR checksum calculated by the system does not match the boot loader 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 written to osloader
3 - MBR checksum recorded in the system

0x0000008E: PAGE_FAULT_IN_NON_PAGED_AREA

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

0x0000008F: PP0_INITIALIZATION_FAILED

The error occurs during phase 0 initialization of the Plug and Play manager in kernel mode. Check your hardware and system disk.

0x00000090: PP1_INITIALIZATION_FAILED

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

0x00000092: UP_DRIVER_ON_MP_SYSTEM

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

0x00000093: INVALID_KERNEL_HANDLE

The error occurs when kernel code or other critical OS components attempt to close a handle that is not valid.
Options:
1 - NtClose handle called
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 has expired. Options:
1 — Installation date (lower 32-bits)
2 - Installation date (upper 32-bits)
3 — Trial period in minutes.

0x00000099: INVALID_REGION_OR_SEGMENT

ExInitializeRegion or ExInterlockedExtendRegion was called with the wrong set of parameters.

0x0000009A: SYSTEM_LICENSE_VIOLATION

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

0x0000009B: UDFS_FILE_SYSTEM

There was a failure to read or write to UDFS-formatted media. The failure may be due to damage to the file system, or to the appearance of bad sectors on the disk. The failure may also be associated with software that changes the disk structure (encryption programs, etc.).

0x0000009C: MACHINE_CHECK_EXCEPTION

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

0x0000009F: DRIVER_POWER_STATE_FAILURE

The driver is in an inconsistent or unacceptable power consumption state. This usually happens due to power failures, rebooting, resuming from sleep mode, etc. It is necessary to replace the faulty driver, or remove software that controls the file system (antiviruses, encryption programs

0x000000A5: ACPI_BIOS_ERROR

The reason for this message is constant 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 card driver. The problem is mainly related to the video drivers, or there is a hardware conflict with the video card. Reboot into safe mode and change the video driver to the standard one.

0x000000BE: ATTEMPTED_WRITE_TO_READONLY_MEMORY

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

0x000000C2: BAD_POOL_CALLER

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

0x000000C4: DRIVER_VERIFIER_DETECTED_VIOLATION

The driver checker detected a fatal error in the STOP error generation module. Accompanying parameters are parameters that are passed to KeBugCheckEx and displayed on the blue screen. Change the 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 the driver.

0x000000C6: DRIVER_CAUGHT_MODIFYING_FREED_POOL

The driver attempted to access a freed memory pool. Change the driver.

0x000000C7: TIMER_OR_DPC_INVALID

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

0x000000C9: DRIVER_VERIFIER_IOMANAGER_VIOLATION

This is a message from one of the driver verification managers. Change the 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 is unable to open locked pages after an I/O operation. Pay attention to the name of the application driver in the STOP error window. Change the driver.

0x000000CE: DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS

The driver cannot cancel the frozen state of system components. The error usually occurs after installing bad drivers or service components. Change the driver.

0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL

The system attempted to access paged memory using a kernel process via a high-level IRQL. The most common reason is a bad device driver. This could also be caused by damaged RAM, or a damaged page file.

0x000000D8: DRIVER_USED_EXCESSIVE_PTES

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

0x000000E3: RESOURCE_NOT_OWNED

Various file system related failures result in this STOP error. The problem may be related to the NTFS.SYS driver.

0x000000EA: THREAD_STUCK_IN_DEVICE_DRIVER

A problematic device driver has caused the system to freeze. Typically, this is caused by the display driver when the computer tries to enter standby mode. This problem is related to the video adapter, or a bad video driver.
An error occurred while connecting the boot drive. The error can occur on computers with high-performance disk controllers that were not configured and installed correctly, or were connected with a poor-quality cable. After a normal reboot, the system can resume normal operation as if nothing had happened. This error also appears after Windows shuts down incorrectly and the failure may be due to file system corruption.

0x000000F2: HARDWARE_INTERRUPT_STORM

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

0x000000F3: DISORDERLY_SHUTDOWN

Windows shutdown crashed due to insufficient memory. Determine which program is running out of memory, try to discover why virtual memory is not providing the system resources it needs, and investigate whether the program (or sometimes a driver) refuses to exit without freeing open pages in memory.

0x000000FA: HTTP_DRIVER_CORRUPTED

The Http.sys system driver is corrupted. This component must be restored 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 the attempt was made to execute the function
2 - Contents of page table entry (PTE)
0x000000FD: DIRTY_NOWRITE_PAGES_CONGESTION
There is no free page memory to continue basic system operations.
Options:
1 - Total amount of paged memory requested
2 - The amount of paged memory requested that cannot be written to.
3 —
4 — Status code at the time of the last write to page memory

0x000000FE: BUGCODE_USB_DRIVER

A critical 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 clock interrupt on a secondary processor in a multiprocessor system was not received within a specified interval. This processor does not handle interrupts. Typically, this happens when the processor is not responding or has entered an infinite loop.
Options:
1 — Interval for blocking the clock interrupt time, in
nominal system clock cycles
2 - zero
3 - Address of the processor control block (PRCB) for non-responsive
processor
4 - zero

0x00000104: AGP_INVALID_ACCESS

The GPU attempted to write to memory that was not reserved for it. The error is related to the video driver or an old BIOS version.
Options:
1 — Offset (in ULONG) within AGP pages to the first data
ULONG whose data is destroyed
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 the DMA (Direct Memory Access) driver not working properly.
Options:
1 - Base address (virtual) in GART
2 - Offset in GART where distortion is detected
3 - Base address (virtual) from GART cache (GART copy)
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 critical error occurred in a third-party file system filter. The error may be caused by antivirus software, defragmentation programs, data backup programs, and other third-party utilities. Try also increasing the size of the page file and RAM.

0x00000109: CRITICAL_STRUCTURE_CORRUPTION

The system kernel has detected incorrect code or data integrity violation. 64-code based systems are protected from this bug. The problem could be caused by a RAM failure 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 msrpc.sys system component returned an error code during execution. The error code is specified in the first parameter.

0x00000113: VIDEO_DXGKRNL_FATAL_ERROR

The DirectX Graphics kernel has encountered a critical error.

0x00000114: VIDEO_SHADOW_DRIVER_FATAL_ERROR

The shadow video driver has encountered a critical error.

0x00000115: AGP_INTERNAL

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

0x00000116: VIDEO_TDR_ERROR

The video driver timeout reset was not successful.

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 - Contents of PTE
3 - reserved
4 - reserved The name of the driver attempting the write operation is printed as
Unicode string on error screen.

0x00000121: DRIVER_VIOLATION

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

0x00000122: WHEA_INTERNAL_ERROR

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

0x00000124: WHEA_UNCORRECTABLE_ERROR

An error has occurred in the computer hardware. This error is 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 triggering 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 the memory page. This error is related to hardware RAM. Options:
1 - Virtual address in memory, which indicates an incorrect
page.
2 - Physical page number
3 - zero
4 - zero

0x0000012C: EXFAT_FILE_SYSTEM

There was a failure to read or write to a media partition in exFat format. The failure may be due to damage to the file system, or to the appearance of bad sectors on the disk. The failure may also be associated with software that changes the disk structure (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. Increase the size of your hard drive and the amount of RAM.

0xC0000135: UNABLE TO LOCATE DLL

Windows tried to load a DLL and received an 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 corruption of the system DLL library.

0xC0000218: UNKNOWN_HARD_ERROR

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

0xC000021A: STATUS_SYSTEM_PROCESS_TERMINATED

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

0xC0000221: STATUS_IMAGE_CHECKSUM_MISMATCH

the driver is damaged or the system library was 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. Constant 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

A STOP error occurs when the audit policy enables the CrashOnAuditFail setting

0xC000026C

Typically indicates device driver problems. 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 triggered a 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 didn’t exist, the computer would simply break down , and you would have to have your equipment repaired, or buy a new one, or maybe even the entire computer. Therefore, 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».

Tweet

What is BSoD

BSoD - Blue Sceen of Death, blue screen of death. Appears in the most critical situations, when closing a faulty program is impossible.

The Windows operating system has several layers of running programs. We see only the top one - open program windows and running services. These are what the Task Manager shows. When one of the programs makes an error that it is not able to process and work around, it, as many users say, “crashes.” You can start it again and continue working.

Software modules running at a lower level (drivers) will not be able to restart in the event of an error. The Windows operating system tries to protect the user from many errors, but this does not always work and it capitulates, showing a sad face or a set of characters on the computer screen.

You need to understand that drivers are an intermediary between the software and hardware of a computer. Both drivers can fail (programmers are people too, they may not take something into account or make a mistake), as well as the hardware part of the computer.

Symptoms of BSoD

1. The appearance of a blue screen with strange symbols or a sad emoticon.

In 99% of cases, the computer reboots on its own due to a critical error (BSoD), but there can be a worse situation: problems with the power supply or motherboard. If you have a desktop PC, check to see if there are any bulges anywhere.

Reasons for a blue screen

1. Overheating. Overheating of the video card or processor leads to the blue screen of death.

By the way, in Windows XP, when the video card overheated, a BSoD always occurred; in Vista and newer, the video driver simply rebooted. If you see the message “The video driver has stopped responding and has been restored,” then this is an overheating of the video card:

The newer Windows, the better the protection against failures. Let's hope that in some Windows XV, instead of a blue screen, we will see an error notification that does not interfere with work.

2. RAM failure. It’s possible, but in order not to hit the mark, read on first - perhaps the cause of your blue screen of death is something else.

If you installed new RAM in your computer and get frequent BSoDs, replace it at the store with a working one. There are no other ways to overcome blue screens of death when replacing RAM.

3. Failure of other hardware. Maybe the voltage in the power supply “sags”. Maybe there is a loss of contact somewhere. Maybe your computer doesn't like the full moon. There are many reasons, one can guess endlessly.

If, after you have analyzed the minidump (more on this below) and eliminated errors, the blue screen does not go away, you should replace all components one by one. You can’t just go ahead and determine the cause of BSoD if the error codes are different every time.

4. Overclocking. If you are an advanced overclocker, then you know what overclocking a computer has to do with BSoD. If not, don't overclock your computer.

5. Driver(s) failure. The cause of BSoD is not necessarily a hardware problem. Unstable drivers are a frequent guest on user computers. How to identify a faulty driver will be discussed next.

6. Viruses. Be sure to check your computer with some or .

I never tire of being amazed at the self-confidence of users who say “ I have no viruses and no antivirus either! I have a straight hand/I only use trusted sites/sometimes I check with a one-time antivirus and that’s why everything is fine!". Leaving aside the debate about how you can live without an antivirus, think about it: if a person sees BSoD, he has This is no longer a normal situation. How can you say that there are no viruses and this is not the cause of the blue screen?

Also, do not think that if you have an antivirus installed with the latest databases, there cannot be viruses. Check with others to completely rule out the possibility.

7. Antiviruses. It's funny (and sad) that antiviruses can cause crashes. Remove your antivirus temporarily. Have blue screens of death stopped appearing? Install a new one so that blue screens do not appear due to reason No. 6.

8. Windows updates. Developers at Microsoft sometimes test updates poorly. Because of this, some people completely disable Windows Update and sit without updates, although this is not an option. Control Panel - Programs and Features - View installed updates- right click - Delete according to the updates installed recently, then check the operation of Windows. Has everything returned to normal? Just don't install updates for a couple of weeks - usually during this time some kind of corrective update for the update comes out and everything becomes fine.

9. Programs crash. This happens, but rarely. If you see BSoD during a game or when running a specific program, I advise you to check your computer for overheating, because most programs are not capable of causing a blue screen, with the exception of those installing drivers into the system (antiviruses, virtual disk emulators, game protection systems like PunkBuster, accounting programs that work with digital keys).

10. Hard disk file system errors. It won't be amiss

Let's find out the cause of BSoD

As you can see, there are quite a lot of reasons and there is no point in guessing. Fortunately, the Blue Screen of Death contains clues as to why Windows suddenly started to crash. Among the incomprehensible text there will be error codes containing a direct indication of what caused the failure.

Most often you are BSoD you won't see, since Windows settings by default enable restarting the computer in case of critical errors.

You can disable automatic restart of Windows like this: Control Panel - System - Advanced System Settings - Options- check/uncheck the boxes as in the screenshot below:

Pay attention to the “Small memory dump” item - check it too.

Google the error code from the Windows Log

The “Write event to system log” checkbox is checked by default, which means error codes will be in the Windows Log.

Go to Control Panel - Administration - Event Viewer - System- and look for a line in the list that coincides in time with the appearance of a blue screen or restarting the computer:

Look for the error code (in the screenshot above it is 0x0000009f) in Google and read the first few sites in the results, follow the recommendations that have helped others. If a driver is specified (a word ending .sys, then it’s generally great - the likely culprit was found immediately, you need to install a driver for this device of an older/newer version. If there is no clear and clear indication on the Internet of the cause of BSoD for the specified error code, read my instructions further.

If there is nothing in the Windows Log, wait for the blue screen to appear and look for the error there:

Just search Google for information on the error code and follow the recommendations.

Analyze the minidump

Unfortunately, if the problem is a faulty driver, this is not always shown on the blue screen. The error code is also not always informative. You need to analyze the minidump file that is created when a BSoD occurs and contains information about the failure, in particular which drivers reported the error. There are two programs for minidump analysis: Windows Debugging Tools and BlueScreenView. Unfortunately, the first one is too complicated for novice users, although it gives a more informative result. In 99% of cases, the second, simple and free BlueScreenView is enough.

The BlueScreenView installer is available at this link.

After starting the program, you will see a window in which at the top there will be minidumps created by the system and information about them, at the bottom - a list of drivers. Failed drivers will be indicated in yellow.

Example No. 1 - the video card is to blame

A blue screen appears with the text ATTEMPTED_WRITE_TO_READONLY_MEMORY. Let's look at the minidump:

The ATTEMPTED_WRITE_TO_READONLY_MEMORY error, judging by googling, is caused by some driver. The likely culprit in this case is nv4_disp.sys. There are others, but they are part of the system and are statistically unlikely to be the cause. A Google search showed that nv4_disp.sys is a video card driver from nVidia. Three steps:

1. Check the video card for overheating.

2. Installing an older video card driver (new if the old one is installed). This is done with any drivers, not just video cards.

3. Installing the video card in another computer.

4. If a blue screen appears on another computer, take the video card to a service center. If the warranty is still valid, you can replace it with a working one free of charge.

5. Doesn't the blue screen appear on another computer? Try installing a different power supply on yours - this may be the reason.

6. Doesn't help? Reinstall Windows completely.

7. If this does not help, take it to the service center for diagnostics.

Example No. 2 - the culprit is not at all what was expected

A blue screen with the message PAGE_FAULT_IN_NONPAGED_AREA is associated with many problems:

If the likely faulty driver was ntfs.sys, then I would recommend checking the hard drive for errors, as well as replacing the cable that goes from the hard drive to the motherboard. In this case, BlueScreenView points to the USB port driver and this could be true, but where I took the dump from as an example, the person’s motherboard is at fault - the capacitors on it are swollen. The solution is to pick up the system unit and head to the service center.

Example No. 3 - the antivirus is to blame

I found this minidump on the Internet:

The culprit was SRTSP.SYS, an antivirus component from Norton. Solved by removing it.

Example No. 4 - “broken” RAM

A blue screen with MEMORY_MANAGEMENT is a sign that the RAM is unusable:

Reinstall Windows

I thought for a long time whether to recommend this. However, a quick glance through popular forums showed that many users are still using pirated builds of Windows. So, if you have:

  • Windows assembly,
  • there are or have been installed many optimizers,
  • the computer takes more than ten minutes to boot,
  • programs often close with errors,

reinstall Windows completely! And install normal, original Windows. If you have a laptop, there will be a recovery partition on your hard drive with Windows prepared by the manufacturer - read the instructions and install (restore) it!

Installing Windows is not a matter of five minutes, but even a novice user can do it if desired.

Where can I get help?

Nothing helps? There is an excellent forum thread: Troubleshooting critical Windows errors (read the rules first).

Just first make sure that you have done everything possible: analyzed the minidump, updated the faulty driver. If the problem is in the hardware, the only way out is to contact a service center.

A critical error in Windows that causes a Blue Screen of Death is accompanied by a system freeze and an abrupt termination of the session followed by a reboot. As a rule, unsaved session data is lost because of it. Also, often the appearance of a critical error with a “blue screen” indicates serious malfunctions in the operating system and can lead to even more unpleasant consequences.

Causes

Before trying to deal with an error, you need to identify its causes and try to find an appropriate solution. In total, the reasons can be divided into two large general groups - hardware and software. The first ones arise in case of problems with the internal components of the computer. The second with the software part of the computer. The most common problems with hardware:

  • You have installed additional equipment that is incompatible with what is already installed. For example, they added RAM sticks that are incompatible with the motherboard or another stick;
  • Failure of certain computer components, for example, a hard drive or RAM stick. In such cases, the operating system may not boot at all;
  • You have incorrectly overclocked your video card, processor, or any other component.

Causes with a software component can be divided into the following categories:

  • Driver conflict and/or incompatibility with current hardware and software;
  • Penetration of virus software and its active activity;
  • Incorrectly installed updates to the operating system or programs important for its operation;
  • Problems with important system applications and services.

Option 1: Software conflict

If you have recently installed any program, then there is a possibility that this program conflicts with the operating system. It is also possible that some program on your computer has been updated, but the update packages conflict with the operating system or other programs. This usually concerns important system programs.

Provided that suspicion falls on a recently installed program, it needs to be removed. You can do this in the following way:


If you are unable to determine which program is causing the error or you think that it is not the program itself that is to blame, but its updates, then you will have to use the system restore option. From the interface of the operating system itself, this can be done like this (relevant only if you have "Restore Points"):

  1. Run "Control Panel".
  2. Expand the element there "Recovery". If you can’t find it, then put it opposite "View" parameter "Large Icons".


  3. Here you will need to click on the button "Run System Restore".


  4. If you don't have it on your computer "Restore Points", then you will receive an error message. You will have to use the installation image of the operating system from a flash drive. If everything is fine, a window will appear containing a brief description of the system recovery function. Click "Further".
  5. Select the one you need from the list provided "Restore point". You need to choose the one that was created at a time when the computer was working normally.


  6. Click "Further".


  7. The procedure will begin to run. Wait for it to complete and don't touch anything. The process usually takes about an hour. Your personal data will not be affected.

If you do not have a “Restore Point” or the system does not boot, then you will have to restore it using a flash drive with a recorded system image. It is important that it be the same version and bitness as your operating system:


Option 2: Virus infection

There is some possibility that the Blue Screen of Death appears due to the fact that the computer has been infected with viruses. In this case, you will have to perform virus removal. Unfortunately, in Windows 7, the standard Defender antivirus is not as high quality as it is in Windows 8 and 10, so it will not be used in this article.

You will have to download and install some kind of antivirus if you don't have one. In this article, we will look at how to scan your computer for viruses and remove them using Kaspersky Free. This antivirus is a stripped-down version of paid solutions from Kaspersky, but is distributed completely free of charge. Its capabilities are sufficient to detect even the newest viruses:


Option 3: Not enough free space on Drive C

If there is too little space on the main volume of the hard drive, the computer may begin to slow down frequently and display various errors, including the “blue screen of death.” As a rule, in such cases, it is enough to simply clean up Disk C. Microsoft recommends that there be at least 100 megabytes of free memory on the disk. This is enough for the computer to function more or less normally and without failures. However, practice shows that for better computer performance you need about 10-15% of free space from the total volume size.

Let's look at how you can quickly clean your hard drive of various junk using the CCleaner program. User data will not be affected.


If cleaning does not free up enough disk space, you can also try to fix possible errors in the registry using the CCleaner program. This may also free up some space:


You can additionally clear space on Drive C by deleting and transferring programs to another volume. Using CCleaner you can remove this or that program:


Option 4: Install system updates

It is possible that all the problems are due to incorrectly installed or not installed updates at all. Some builds of Windows 7 are not always stable, so it is recommended to update them to get rid of most problems, since updates contain fixes. However, if you have a pirated copy of Windows installed, then it is better to refrain from updating, as you risk aggravating the situation.

The Windows 7 update process is as follows:


Option 5: Update drivers

Very often, the appearance of a blue screen of death is associated with incorrectly installed and/or not installed drivers at all. In this case, you need to reinstall the “problematic” drivers. However, it is very difficult to find out which component caused the error, especially if there are several of them, so it is recommended to use programs that automate the process.

The best solution in this case is DriverPack Solution. This program does not require installation on your computer. It is completely free, and the search and installation of drivers occurs automatically:

  1. Go to the official website of the Driver Pack developer. Click on the button “Install all necessary drivers”. After this, an archive with an EXE file will be downloaded to your computer, which you will need to run.


  2. When the program is launched for the first time, it begins scanning the computer for missing drivers. It usually takes no more than a minute.


  3. Driver Pack will offer you to use parameters automatically selected for your computer. To do this, use the button . However, in this case, DriverPack can install programs on the computer that it considers justified to install. Usually this software is not really needed by the user.


  4. If you do not want any additional software to be installed on your computer, but only the drivers you need at the moment, then use "Expert Mode", which is located at the bottom of the window.


  5. Here, pay attention to the left side of the window. There you need to go over the tile with the 4 squares icon.
  6. Uncheck all applications that you do not currently need on your computer or that have already been installed.


  7. When you're done, go back using the wrench icon. There click on the button "Set up your computer automatically". In this case, only the drivers that remain selected will be installed.


  8. After clicking the button, the program will create "Restore point", with which you can roll back driver updates if they are suddenly performed incorrectly.


  9. Wait until your computer is set up and the necessary drivers are installed. When it's over you will need to click on "Further".


  10. Restart your computer and check if the blue screen error disappears.

Option 6: System errors

Blue screens in Windows 7 can be caused by various types of system errors. It is recommended that you write them down when the corresponding message appears and look at the documentation for them on the Microsoft website. If you do not have the opportunity to view the window with the error, then you can view it in a special window that opens as follows:

You can look for a solution to this problem on the official Microsoft website, but remember that most system errors can be resolved by running the operating system recovery process. The procedure was described in detail in the first scenario.

Option 7: Reset BIOS Settings

Incorrect settings in the BIOS can cause a blue screen to appear when working in the operating system, but most often when it starts. In this case, it is recommended to reset the BIOS settings or try to change the setting that causes the blue screen.

Since you are unlikely to know which parameter in the BIOS is configured incorrectly and that it causes the blue screen, the only option left is to reset the settings completely. It can be done from the operating system interface, but most likely it won’t start for you due to a blue screen, so let’s consider a universal option:


Option 8: Hardware problems

It is possible that the cause of the critical error and blue screen was the incorrect connection of any important computer components to the motherboard. Most often this happens if some contact suddenly falls out of its socket. To do this, you will have to disassemble the computer/laptop case and check if everything is in order. Additionally, inspect the cables and cables for physical defects.

If during the inspection it turns out that any of the elements are not connected tightly enough, then simply reconnect it. Provided that faults are found on one or another element, this part will have to be taken for repair or replaced with a new one. This statement is relevant both for damaged cables/cables and computer components (hard drive, motherboard, etc.).

As you can see, there are a lot of reasons that can cause a blue screen of death in Windows 7, and each of them needs to be “fighted” differently. Within the framework of this article, all variants of the occurrence of a critical error were considered and recommendations were given for eliminating them.