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
In progress Windows operation 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. For software problems Typical are 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.
Blue screen death Windows 10 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 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 reference books various codes errors, in particular, in .
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 the hard drive, the system definitely needs one, which must be located in the same partition where Windows folder. Its size can be from 2 Mb or more.
- Login via context menu in folder properties " Computer».
- Click the button in the window that opens Advanced System Settings».
- 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
Exists different ways crash dump analysis Windows memory, but we will get acquainted with the most, in my opinion, convenient and simple - using free utility.BlueScreenView is especially convenient because it does not require the installation of cumbersome Debugging Tools packages on your computer for Windows 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 that opens double click 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. I'll say in advance that it was caused by a crease in the cable hard drive. 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.
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 periodically during Windows startup 10 and when the computer wakes 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 out 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. Early in the launch phase operating system This PC did not start with too many programs 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 don't need to copy them to Windows folder\ Minidump your PC, which is loaded into the default program. Copy them to any comfortable spot, for example, to your desktop, and tell the program the new location of the directory to download.
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».
Blue Screen of Death (BSOD) is one of the most vexing problems that Windows user may collide. Knowing how to determine the cause of the crash is one of the most important forms of diagnosing BSOD. An error with a blue screen code can occur for various reasons, and without analyzing what is causing the error, it is difficult to eliminate it. These are the main reasons for Blue Screen of Death BSOD:
- Driver conflicts- Driver conflicts occur when two or more drivers cannot work with each other properly. This can also happen if multiple drivers are installed for the same device without uninstalling the previous version.
- Hardware conflicts- Incorrect overclocking of a PC can immediately create a BSOD. Blue Screen of Death can also occur if your RAM sticks are not installed correctly or if a piece of hardware is starting to wear out.
- Operating system (OS) errors- User error or malware can delete vital files of your OS. Significant missing files can result in a crippling error causing your PC to enter a BSOD cycle in which you get a blue screen every time your PC turns on.
Preparing to analyze a BSOD file dump
Whenever a BSOD error occurs, Windows dumps some information about it into a file on your PC, but trying to understand this dump file very complex. One of the easier ways to understand is to use the utility BlueScreenView by NirSoft, a free tool that finds these dump files and displays them in a more user-friendly form. First of all, you should check the settings for the memory dump report in the Windows system itself:
- Click Win+R and enter sysdm.cpl
- Go to the tab Additionally and select from below
- Make sure you have the error logging settings enabled.
Now download the program BlueScreenView scroll to the center of the site to download the file. You will see three links as in the picture below, select the installer that is most convenient for you. If you want to Russify the program, then find Russian in the table below and download the file. The downloaded file will contain a "BlueScreenView_lng" file, just place it in installation program to the root.
Find out Blue Screen of Death error codes
When you run the program, it will show you errors in files and memory dumps. As you can see in the figure below, I get a blue screen with an ndis.sys error and there seems to be a problem in the ntoskrni.exe file. In the top column I can see the full file dump report, and by clicking on it right click mouse find in google information for correction. The error is most likely related to the installed virtual machine, or rather be with a virtual one network adapter and an antivirus that creates a blue screen error after sleep mode and the initial boot of the system.
How to Fix Blue Screen of Death Error Codes
I will give a couple of ways of what to do and how to eliminate errors using popular methods:
- When, for example, a blue screen of death occurs in Windows 10, there will be QR code which will redirect you to the site.
- On the site Microsoft there is already a database with BSOD errors and prompting tools.
- Use the Microsoft Virtual Agent, enter BSOD in the first line and follow the instructions.
- Microsoft also suggests running
Blue screen of death (BSoD – blue screen of death) is the result of a serious error that occurred while the operating system was running. Actually, that's why it got its name - if you saw it, the error is so serious that the computer has nothing left to do except turn off Windows and reboot. This does not always mean that something is broken, perhaps just some isolated failure occurred. This article describes the most common reasons why a Blue Screen of Death occurs when loading Windows, and what to do if it happens on your computer. 
General information
The operating system is a very complex complex various programs and services. They all constantly interact with each other, create new files according to given algorithms, which are then used by other programs, and so on. Of course, Windows developers have provided a huge number of protections against failures and errors, but they can still occur.
The Blue Screen of Death occurs when Windows' built-in security measures fail to correct the problem. The system will try various methods, but if nothing works, it will have to urgently shut down and restart the PC. Such errors are called unsolvable.
For comfort Windows users shows the reason why the operation was stopped. If you carefully examine the blue screen, it becomes clear that it contains the reason for the “death” of the OS, recommendations on what to do to eliminate errors, as well as special code. You can enter this code in your search engine to find out more about this problem full information, and also receive instructions on how to solve the problem. 
Possible causes
In order to understand what to do to fix the problem, you need to know why it happened. IN this list The most common causes of the screen of death are presented:
- There is not enough free space on the system hard drive. If your drive C (or another one containing system Windows files) is packed to capacity, a similar error may occur.
- Drivers are not working correctly - you may have installed wrong version drivers for one of the devices, or a system failure occurred during the installation process, system operation may be interrupted, including when attempting to boot.
- Registry errors - occur when incorrect installation programs. You may have downloaded a broken application installer, or your PC is infected with viruses, which is causing the problem.
- Damaged system files – this often happens on older operating systems. Over time, many small errors accumulate on the disk, which may one day cause the death of Windows.
- Unstable operation of internal components personal computer. A normal breakdown, power outages, overheating - all this can also cause a blue screen.
Problem solving
Some of these loading errors can be easily resolved by users on their own. For others, you may have to turn to specialists.
The first thing you should do if you see a blue screen of death is try to remember the code indicated at the very bottom. After this, try turning on your computer as usual. Often problems occur once and will not happen again.
If the problem returns after a reboot, you need to start Windows using the Last Known Good Configuration. To do this you need to do the following:
If the cause of death and the appearance of a blue screen were problems with the registry, system files, or recently installed drivers, a similar approach can solve this problem.
If BSoD appears every time booting Windows, it is recommended to try performing a system restore using a disk or bootable USB flash drive.
Diagnosing blue screens
To find out what exactly caused the “death” of Windows, you need to write down the error code. But with standard configurations, the blue screen of death appears only for a couple of seconds. It is unlikely that you will have time to write down or photograph anything. To increase display time, you need to change your OS settings. To do this you need to do the following:
Most often, the main sign of any serious problems in Windows 7 is a blue screen. Moreover, its presence can indicate both problems with the hardware of the personal computer and the software.
Fixing problems of this type is in most cases quite simple; you can almost always do it yourself. Only rarely may specialist consultation be required.
Setting up the system to diagnose the problem
When appears often Blue Screen of Death, first of all, it is necessary to perform two operations in strict sequence:
- disable reboot;
- run a special system utility.
Disabling reboot will allow you to get rid of automatic restart when BlueScreenofDeath appears. This is necessary in order to find out the error code that caused an emergency on a personal computer.
This operation is performed as follows:
After completing all the above operations, the system will no longer reboot on its own. And the user will be able to get acquainted with all the information about the problem that led to the appearance of the corresponding message on the display.
Most often, the problem lies in the PC's RAM. You should definitely analyze it using special utility. The OS already has the necessary software built into it to achieve this goal.
It is launched as follows:
You must choose the first option, as it is optimal. It is important to remember that the type check in question takes a long time to complete.
Under no circumstances should you interrupt the process.
After it is completed, the machine will reboot into automatic mode. The PC display will display all the information with the test results. This will allow you to determine how to fix the problem.
Reasons for appearance
This type of problem can occur due to a variety of problems.
But all of them can be divided into main categories:
- equipment malfunction;
- inappropriate or malfunctioning drivers;
- software.
The surest way to determine a malfunction is to analyze the information present on the monitor at the moment Blue Screenof Death appears. In most cases, the computer uses special character sets to point the user to the problem node. It is best to find a decoding of error codes on the Internet in advance.
Faulty installed equipment
Very often, the type of problem in question appears due to problems in the PC hardware. They can arise due to improper assembly or microcircuit failure. Quite often both the first and the second are present.
The most common malfunction is swelling of the capacitors on motherboard. Detecting this is very simple: you need to open the PC case and carefully examine the small bars with round legs on the Motherboard. If the end part of any capacitor is swollen, it must be replaced. This process It’s quite simple; you just need to select a component with a similar capacity.
Often a similar problem occurs with power supplies. The presence of swollen capacitors in them can also lead to a blue screen. It is advisable to carefully inspect all components of the PC - the presence of damage (carbon deposits or other defects) indicates a hardware malfunction. Often the problems lie in the connection buses.
Drivers
Very often Blue Screen of Death occurs due to incorrectly selected drivers. Most often this is due to catalysts for the video card. This is especially true for applications downloaded from unofficial resources.
Solving this problem is easy, you just need to replace installed programs to standard. But sometimes it happens that dealing with a problem of the type in question is not so easy.
If the user does not have sufficient knowledge and experience to detect the problematic driver that is causing the BSOD, then a special built-in utility for this should be used. It's called Verifier.exe, and it's very easy to find and run.
Software
Often, BSOD occurs due to the presence of some malicious application. An antivirus will help resolve this situation.
On this moment It is best to use the following to check your PC:
- Kaspersky Anti-Virus;
- Nod 32;
- D.R. WEB;
- Avast.
Sometimes BSOD appears due to a variety of applications that for some reason conflict with drivers or other programs or utilities. Therefore, sometimes you can get rid of the blue screen of death by simply uninstalling recently installed programs.
Memory dump analysis using BlueScreenView utility
If a Windows 7 blue screen occurs, what should you do? The situation can be resolved using universal application BlueScreenView. This utility does not require installation and immediately after launch it automatically detects all dump files.
With BlueScreenView you can easily analyze your computer's messages.
The process of viewing a dump is quite simple:
- dump files are displayed in the upper part of the window - you need to click on the required one, and the drivers that caused the BSOD will be displayed in the lower area;
- you need to double-click on the desired item - this will allow you to see the parameters in a tabular format;
- click on “settings” - “selected window mode” - “drivers found in the crash track”;
- right-click and select HTMLReport.
The information received can be sent to the support service, or analyzed independently - if the user has the appropriate knowledge and skills for this. If necessary, you can view the original BSOD screen using the utility in question. It has very wide functionality and many settings, which is why it is quite popular.
Video: problem solving
Common errors
Figuring out how to find out the cause of a BSOD is quite simple. It is much more difficult to eliminate it. Usually the error is displayed on the monitor screen in the form of a hexadecimal code, which can be easily translated into plain English.
The most common errors that occur are:
It is necessary to find a translation of error codes into English or directly into Russian in advance. This will make it possible to simplify the task of troubleshooting the type of malfunction as much as possible. If for some reason it was not possible to resolve the problem, then you should contact competent specialists.
Avoid occurrenceBSODor you can eliminate it after it appears using some actions:
Also, often the cause of the appearance of the blue screen of death is an installed unlicensed operating system. Perhaps installing the original distribution will get rid of the troubles.
The best way to solve the problem of BSOD on a PC is to simply prevent it from occurring. It is necessary to update the software in a timely manner, and also not to use pirated programs, OS. It is imperative to monitor the hardware (temperature conditions, dust levels). All this will avoid the need to waste time fixing problems.
>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 operating systems. Windows systems 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 computer hardware failures.
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 via 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 hardware, for example, damaged drivers, file system, hard disk, blocks RAM memory. 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 turn on this windows possibility, or you simply won’t 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. English language. 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 consider the reasons for their occurrence and shortcuts 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
Virtual memory tampering occurred on an internal IRQ process high level. 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:
- Address where the erroneous request was made
- IRQL that was used to access memory
- Memory access type: 0 = read operation, 1 = write operation
- 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:
- Exception code
- Address that failed to process
- Parameter 0 - exception
- 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 serious problem in third party drivers.
Options:
- APC address at the time of 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 with the format NTFS. The failure may be due to damage to the file system, or to the appearance bad sectors on disk. The failure may also be due to software, changing 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:
- Virtual memory address that caused the error
- Physical address of the error cause
- Processor Status Record (PSR)
- 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:
- System level code that describes why the system believes that initialization has not completed
- Indicates the location within INIT.C where phase 1 initialization failed
0x00000035: NO_MORE_IRP_STACK_LOCATIONS
A high level driver tried to call the driver low level via 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 done because the system does not allocate space in the Must Suceed Pool. Replace or update the faulty system driver.
Options:
- Amount of request required
- Page number used
- Number of pages requested
- 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. Possible reason— the driver tries to complete the same operation several 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:
- Number of pages used
- Number of physical pages on the machine
- Extended page size
- Overall 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 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 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
Not enough RAM to run Windows kernels(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 Windows updates 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 hardware drivers. It is necessary to roll back the changes to the state at the time of installing the Service Pack, or delete 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 early Windows versions N.T. 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 antivirus program, having previously booted from the CD.
KerBugCheckEx parameters:
1 — Disk signature in MBR
2 — Check sum MBR 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 incorrect driver equipment.
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 software violation has occurred license agreement. 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 due to incorrect hardware configuration, processor overclocking, unstable work RAM blocks, overheating of system components, 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 standard.
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 may also be caused by damaged RAM, or damaged file swaps.
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 Associated with the video adapter, or a bad video driver.
There was a problem connecting boot disk. 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 "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 terminate without being freed open pages in mind.
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 moment last entry to page memory
0x000000FE: BUGCODE_USB_DRIVER
Happened critical error in the operation of the USB controller and related devices. The problem is usually caused incorrect work 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
Recording attempt GPU into memory that was not reserved for this. The error is related to the video driver, or old version BIOS.
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
Discovered Internal error video drivers. 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 hardware error detection architecture Windows tools(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 number pages
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 boot DLL library and received an error code. Possible cause: the file is missing or damaged. Possibly also damaged system registry.
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 (rescue disk or reinstalling Windows). 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 happen when the computer is restarted after the system administrator has changed permissions so that SYSTEM Account no longer had 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 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 names files, 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».
Loading...
