A critical error in Windows that causes the "Blue Screen of Death" to appear is accompanied by a system freeze and an abrupt end of the session followed by a reboot. As a rule, because of it, unsaved data for a session is lost. Also, the appearance of a critical error with a "blue screen" often indicates serious malfunctions in the operating system and can lead to even more unpleasant consequences.
Before trying to cope 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 hardware problems:
Software reasons can be divided into the following categories:
If you 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 the computer has been updated, but the service packs conflict with the operating system or other programs. This usually applies to important system programs.
Provided that suspicions fall on the recently installed program, it must be removed. This can be done in the following way:
If you are unable to determine which program is causing the error, or you think that it’s 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 this way (only relevant if there is "Recovery points"):
If you do not have a "Restore Point" or the system does not boot, then you will have to restore it using a USB flash drive with a recorded image of the system. It is important that it is the same version and bit as your operating system:
There is some possibility that the "blue screen of death" appears due to the fact that the computer was infected with viruses. In this case, you will have to perform a virus removal. Unfortunately, in Windows 7, the standard Defender antivirus is not as good 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 consider 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 it is distributed completely free of charge. Its capabilities are sufficient to detect even the newest viruses:
If there is too little space on the main volume of the hard disk, then the computer can often slow down and display various errors, including the "blue screen of death". Typically, in such cases, it is sufficient to simply clean up Disk C. Microsoft recommends that you have at least 100 megabytes of free memory on the disk. This is enough for the computer to function more or less normally and without interruptions. However, practice shows that for better computer performance, you need about 10-15% of the free space of the total volume size.
Let's take a look at how you can quickly clean up the hard disk from various garbage using the CCleaner program. User data will not be affected.
If the cleanup did not free up enough disk space, you can also try to fix possible errors in the registry using the CCleaner program. This can also free up some space:
Additionally, you can clear space on Drive C by uninstalling and transferring programs to another volume. With CCleaner, you can uninstall a particular program:
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 of the problems, as updates contain fixes. However, if you have a pirated copy of Windows installed, then it is better to abstain from updates, as you risk aggravating the situation.
The Windows 7 upgrade process is as follows:
Very often, the appearance of the blue screen of death is associated with incorrectly installed and / or not installed at all. In this case, you need to reinstall the "problem" drivers. However, it is very difficult to find out exactly 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 is automatic:
A blue screen in Windows 7 can provoke all sorts of system errors. It is recommended to write them down when the corresponding message appears and look at the documentation for them on the Microsoft website. If you are unable to view the error window, 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 are resolved by running the operating system recovery process. The procedure was described in detail in the first scenario.
Incorrect settings in the BIOS can provoke a blue screen when working in the operating system, but most often when it starts up. In this case, it is recommended to reset the BIOS settings or try to change the setting that causes the blue screen.
Since you hardly know which parameter in the BIOS is configured incorrectly, that it causes a blue screen, the only option remains with full dump settings. It can be made from the interface of the operating system, but most likely it does not start for you because of the blue screen, so consider the universal option:
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 suddenly some contact fell 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 cables and loops for physical problems.
If during the inspection it is found that some of the elements are not connected tightly enough, then simply reconnect it. Provided that faults were 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 / loops and computer elements (hard drive, motherboard, etc.).
As you can see, there are a lot of reasons that can cause the Blue Screen of Death in Windows 7 and each of them needs to be “fought” in different ways. Within the framework of this article, all the options for the appearance of a critical error were considered and recommendations for their elimination were given.
The Blue Screen of Death is familiar to every user of Windows operating systems. For some users, it appears so often that they begin to think that this is normal. But this is not the case. Let's see what the blue screen of death is. This is an error that appears during startup or after an abrupt shutdown of the computer. It indicates that there are problems with the operating system or internal hardware. Only by understanding the causes of occurrence, you can eliminate it as efficiently as possible.
If a blue screen of death appears on a computer with Windows 7, then we bring to your attention this article, it will definitely help you find and fix this problem.
The reasons for the appearance of a blue screen can be divided into two main groups:
In order to accurately determine the cause of the error, it is necessary to carefully study the contents of the blue screen. After all, it is on it that all the information the user needs is indicated, namely: the reason for the error and even recommendations for its elimination.
If the information that is indicated on the screen is not enough, then the computer can be configured specifically to diagnose the blue screen of death.
File corruption win32k sys provokes a blue screen. Therefore, be sure to check and scan other directories.
Windows blue screen or memory dump is a reflection of the working (or not quite) state of the operating system in a certain period of time. Since immediately after the appearance of a critical error, after which an abrupt shutdown of the device may follow, Windows displays all the necessary information on the famous blue screen, then for further diagnostics, you just need to remember it: rewrite or photograph.
The main nuisance is that the blue screen is shown for a strictly limited time. After that, the reboot mechanism starts. Therefore, an unprepared user who does not know where to look may find it difficult to have time to rewrite the necessary information.
To disable auto-restart of the device, that is, when the computer or laptop immediately starts to reboot, immediately after the blue screen of death appears, it is necessary to activate the recording of small memory dumps, that is, part of its important content. This requires the following steps:
Now the blue screen of death when booting Windows 7 will not disappear immediately, so you will have time to rewrite the necessary information.
Since any problem can cause the blue screen of death, it is necessary to identify it in order to fix the error.
As soon as you managed to take a picture of the blue screen when Windows boots or write down the information that appears on it, you can proceed to decipher the error that caused it:
Knowing this information, it becomes clear how to remove the blue screen of death.
Problems with a blue screen in 90% of cases are the most commonplace and appear among users who are poorly versed in computers, so they often neglect the installation of system updates, drivers, the correct procedure for uninstalling programs, and so on.
Damage to the acpi sys file can cause a blue screen, so to fix the error, you must replace it with a workable one.
Even if the screen says that the error was caused by files like tcpip, ntoskrnl, fltmgr, netio, ntkrnlpa, the first thing to do is:
It will not be superfluous to defragment, check and clean the registry. This is best done using special software. One of these programs is.
With its help, it is also possible to check the presence of all files and libraries necessary for the stable operation of the operating system. If some of them are missing or damaged, the program will offer to download and replace them. If you wish, you can make a copy of the original files and save them in any convenient place on your hard drive.
If you do not know how to remove the blue screen of death when Windows installation 7, please read the following information carefully. This error can occur only in three cases, if:
If, during the installation of Windows XP, the blue screen repeats over and over again, but you are sure that the computer hardware is in order, then the problem most likely lies in the faulty operating system image that you are using.
Blue screen during installation or Windows recovery may occur due to faulty internal storage (HDD) or incorrect formatting. Do not neglect the standard procedure for checking the operability of the used OS image, disk or flash drive. All this information can be found on the screen. You fix other problems in the same way.
If you do not know how to remove the blue screen of death that occurs due to missing or damaged system files or libraries like TCPIP.SYS, SPCMDCON.SYS, IGDPMD64.SYS, fltmgr, DXGKRNLl.SYS, NTKRNLPA.EXE, NETIO.SYS or error 0x00000116, then this method is for you. It is also suitable for errors caused by other files with the extension .SYS, .DLL, .EXE. To do this, you can use a special third-party shareware utility. One of the most popular is.
After installing the program, you need to launch it and start scanning using the Start button. Next, the utility will offer to scan files like ntoskrnl, dxgkrnl, igdpmd64, fltmgr, tcpip, netio, ntkrnlpa. Additionally, the program will check other directories as well. If you are sure that it was the nvlddmkm sys file that caused the blue screen of Windows 7 or any other, the name of which you should know for sure, then you can check it.
As soon as the scan is finished, it will offer:
Optionally, you can install other applications to automatically search for damaged system files and replace them. Some of them similarly identify and fix driver problems.
If you have recently made BIOS changes or tried to overclock the processor, then this may be the cause of the problem. Therefore, you should definitely try to return its default settings. This can be done in several ways:
And this article examined: what is the blue screen of death, its causes. An explanation of the errors was given, and various options for eliminating the resulting breakdowns were proposed. Now, if you see the Windows 7 death screen again, then you already know what to do.
Quite a few users have come across such a phenomenon as the blue screen of death. What to do (Windows 7 is most often subject to such a nuisance) in this situation, not everyone knows. And therefore, the sight of a blue screen is terrifying. However, sometimes error codes help to correct the situation. They indicate a problem. And already proceeding from it, it is necessary to make certain decisions regarding the treatment of the computer. Today we will learn how to deal with some of the causes of the appearance of a blue screen, as well as find out what should be done to eliminate this trouble once and for all. Some professional advice system administrators often help to deal with problems even for an ordinary user. Let us, as soon as possible, begin to study our today's problem with you.
But let's start by figuring out what we're going to deal with at all. Only after that it will 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 know today? death is a kind of system error. And it appears when the operating system is loaded or directly during operation. At the same time, you get a blue screen for a while. Hence such a strange name. The blue screen of death codes are written on it. More precisely, the codification of the errors that have arisen. Based on them, you can figure out what is the cause of the problem. And sometimes even eliminate it.
But, as practice shows, the blue screen of death or some other) is the first sign that your computer is fading into oblivion. This means that you will have to quickly treat him. We can say that our phenomenon is a demonstration that the operating system and hardware devices 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.
Let's start with you exploring some of the common blue screen of death error codes. After all, they will help you not to be afraid when it appears, but to quickly move on to decisive action. For example, a blue screen of death occurs quite often, error code 0x00000116. You should not be afraid of this phenomenon.
The point is that this coding indicates that when the operating system was loaded, an attempt was made to reset and restart the display driver. And since we got an error, the action did not work. There are many ways to solve this problem. But there are some tips to help you save your data too.
For starters, you should try to reinstall the drivers on your computers. And that's all. And start with those that relate 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. They sometimes cause a blue screen of death. What to do? Windows 7 is known to be the most affected by this phenomenon. This means that you will have to be very careful with antiviruses in it.
It makes no sense to list all the blue screen of death codes. Windows 7, and so, if errors occur, it will give them to you. And then, based on the data obtained, it will be possible to use a special reference book of computer errors. This lists all codes that relate to the blue screen. But still, we will analyze one more option.
Quite often this blue screen of death appears: 0x0000007b. This error always occurs directly when the computer boots. If the previous version is able to appear while working with programs, applications, games, then this one always "does not let" into Windows.
The 0x0000007b code indicates that access to the system partition of the hard disk was lost during computer boot. The reasons can be different - from a banal virus to a major damage to the iron. But this problem always needs to be fixed.
Reinstallation of Windows with full formatting and redoing of hard disk partitions helps here. But sometimes the problem does not disappear even after such a radical step.
In this case, load the latest system configuration. To do this, when booting the computer, press F8, then select "Last Known Good Configuration". The computer will boot. You can enjoy the result.
Check the compatibility of the hard drive and other hardware. If not, replace the components. After that, the problem will disappear. Often the code 0x0000007b appears after connecting a new or additional hard drive.
Now it's worth finding out the general provisions on how to remove the blue screen of death. Sometimes all the tips are quite effective, regardless of the error that occurs. And the first option that can only be advised is to roll back the system. Reception is relevant in the case when the system boots initially.
In order to roll back, you need to go to "Start", "All Programs". Next, find the "Standard" section there, from there go to "System". Select "System Restore". You will see a window with a welcome and a warning about the irreversibility of the process. Agree and select the rollback point in the next menu that opens - at the moment when the computer was not bothered by the blue screen of death. Click "Next" and wait a while.
During the whole process, the computer will reboot itself about 2-3 times. This is fine. After a rollback, you should reset some settings. But all programs and personal data will remain in perfect order. Quite often, this technique helps to permanently fix the problem.
If you suddenly have a blue screen of death, what to do (Windows 7 or any other operating system) - you do not know, then it's time to check the complete set of your computer. Sometimes even an old train can bring a lot of inconvenience. Particular attention should be paid to accessories in cases where you have recently changed something in your computer.
As already mentioned, often blue screen of death problems arise from hardware conflict. This may even apply to a "flash drive". So be careful. If you suspect a hardware conflict in your computer and you 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. Including he will not let you see the blue screen of death. Why else does it arise? And how to deal with it?
For example, sometimes this phenomenon is seen when the computer or processor overheats. In the case of stationary versions, everything is fixed quickly and easily - either an additional cooler is installed, or the "hardware" is cleaned out (and 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. First, the device will have to be taken to a computer service for cleaning. Secondly, it may be necessary to additionally install a cooler (and this service is not so cheap). Third, put less strain on your computer while you work. This will help avoid overheating and its consequences.
Do you have a blue screen of death for some unknown reason? What to do? Windows 7 is an unrivaled leader in this regard. And also it was in this operating system that application conflicts and their incompatibility with each other began to arise. This may be the result of the appearance of the screen of death.
What to do in this case? First, remember after installing which program the problems started. After that, set the compatibility options. Sometimes this technique works. But you shouldn't rely on him too much.
If the compatibility mode did not help, then uninstall the installed application. Don't want to deal with the problem for a long time? 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.
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 began after that, then you will have to roll back the system, as well as disable the automation of the process.
Go to Windows Update. There go to settings. Select the option that is marked "not recommended". That is, do not automatically check, download and install updates. Never. This will help to avoid many problems in the future. And not necessarily they will be associated with the blue screen of death.
Another problem that can only arise and cause our today's phenomenon is nothing more than hardware drivers. Sometimes they are the ones that generate 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 avoid any inconvenience in the process, it is best to use the official websites of the manufacturers to download applications. They will not infect your computer. And there is always only high-quality content. After updating and installing all drivers, it is best to restart your computer. That's all. Now you will notice how the blue screen of death problem goes away. But this does not always happen. After all, there are other reasons for the occurrence of this phenomenon.
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 - it's antivirus. If you have it, then it is 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.
The owners of Avast and Kaspersky most often suffer from this phenomenon. As a last resort, replace your antivirus. Did it help? You can rejoice. No? Then remove the antivirus completely, and then take the computer for repair. Tell us about the problem - professionals will definitely help you there.
And of course, the blue screen of death can appear due to viruses on the computer. Some contagion is aimed just at this. Indeed, with this phenomenon, the entire operating system is destroyed. Is there a suspicion of infection? Then take and treat your computer.
Scan it with antivirus, antispyware and other healing content. Disinfect all dangerous objects, and then remove what did not succumb to the process. This is usually enough. Also, clean your computer's registry - this is important. Now look at the result. If all is useless, reinstalling the operating system will help. But first it's worth trying a rollback.
In this article, we will talk about such a phenomenon in the Windows operating system as - Blue screen of death or in our “ blue screen of death", Also called STOP error. Let's consider the main causes of occurrence and decipher the codes of these errors.
And first, let's give a definition of what “ Blue screen of death"Is a method of generating a fatal error message in Windows NT 4.0, Windows 2000, Windows 2003, Windows XP, Windows Vista and Windows 7, caused by malfunctioning of some programs or drivers, but still more often due to hardware failures of the computer.
A blue screen stops all processes in the operating system and freezes the computer after displaying a blue screen. In general, the blue screen helps us, you ask, but because it prevents the destruction of the operating system and the decommissioning of equipment. When “ blue screen of death»The error code and how to solve it are displayed. But it may be that the STOP error was caused, for example, by distortion of data packets transmitted over the local network, in this case a simple reboot helps. If the error appears every time you start the operating system, then this may already be a problem related to the hardware of the computer, for example, damaged drivers, file system, hard disk, RAM blocks. But to find out the causes of the error, you need to rewrite the first two lines of the STOP error. For example, as shown just below:
STOP 0x0000006B (0xC0000022, 0x00000000, 0x00000000, 0x00000000) PROCESS1_INITIALIZATION_FAILED
where 0xC0000022, 0x00000000, 0x00000000, 0x00000000- parameters that reveal the meaning of this BSoD.
By the way, there is a small feature, it lies in the fact that in the operating system, in order to see the blue screen, you must first enable this windows feature, or you simply will not see this screen, if an error occurs, the computer will simply reboot quickly (and so every time).
To enable this option, go to the properties "My Computer", select the "Advanced" tab. In the Startup and Recovery box, click the Options button. In the window that appears, uncheck the box next to "Perform automatic restart".
With the appearance of a STOP error in the text of the message, a method for solving it is briefly presented, though in English. But I can say for sure that at the present time a common cause of STOP errors is hardware problems with the hardware of the computer or its software parts, and sometimes due to a mismatch between one and the other.
Now let's go directly to the errors themselves and look at their causes and short solutions.
0x00000001: APC_INDEX_MISMATCH
Internal kernel error (kernel). The problem is most often associated with a driver malfunction, insufficient RAM or hard disk space.
0x0000000A: IRQL_NOT_LESS_OR_EQUAL
There was a tampering with virtual memory on an internal high IRQ process. The most common cause is a device driver using the wrong address. The error occurs due to bad drivers. Rarely occurs due to a malfunction of one of the devices in the system.
Options:
0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
This is a very common mistake. Usually, the excluded address points to the driver or function that caused the stop screen. Always pay attention not only to the specified driver, but also to the address itself or the image containing this error. This is usually the exception code 0x80000003. This error means that a breakpoint or handler was initialized when accessing memory, but the system booted with the / NODEBUG switch. This error may not appear too often. If the error appears constantly, make sure that the debugger is connected and the system boots with the / DEBUG key.
On non-Intel systems, if the exception address is 0XBFC0304, the error occurs due to processor caching. If the error persists, contact the processor manufacturer.
Typically, an analysis of the second parameter of this message is required, which indicates the address of the driver / function that caused the problem.
Options:
0x00000020: KERNEL_APC_PENDING_DURING_EXIT
The error name indicates a damaged / disabled APC counter. If you have such a situation, check all the file systems installed on the machine, for example using the EMRD rescue kit.
The current IRQL must be zero. If the IRQ is not zero, then a certain order of unloading drivers, when returning to a higher IRQ level, may cause an error. Try to remember what you were doing or which applications were closing, which drivers were installed when the blue screen occurred. This symptom indicates a serious problem with third-party drivers.
Options:
0x00000023: FAT_FILE_SYSTEM
FAT).
0x00000024: NTFS_FILE_SYSTEM
There was a failure to read or write to a hard disk partition formatted as NTFS... The failure can be associated with damage to the file system, or with the appearance of bad sectors on the disk. Also, the failure can be associated with software that changes the disk structure ( encryption programs and stuff).
0x0000002A: INCONSISTENT_IRP
I / O Request Packet (IRP) is not functional; occurs when a field or more than one field is invalid compared to the persistent state of the IRP. For example, the IRP was already disabled when a device driver was waiting for a command.
Options:
1 - the address at which the IRP was found in idle mode
0x0000002B: PANIC_STACK_SWITCH
This error occurs when the kernel stack area is full. The error occurs when the kernel driver uses too much stack space. Damage to the kernel itself could also be a possible cause of the error.
0x0000002E: DATA_BUS_ERROR
This STOP error most often occurs due to a failure in the RAM area. This can happen when a driver tries to access a memory address that does not exist.
Options:
0x00000031: PHASE0_INITIALIZATION_FAILED
System initialization could not be completed early (phase 0). It is necessary to study the error in more detail, since this error code does not say practically anything.
0x00000032: PHASE1_INITIALIZATION_FAILED
The system initialization could not be completed at a late stage (phase 1). It is necessary to study the error in more detail, since this error code does not say practically anything.
Options:
0x00000035: NO_MORE_IRP_STACK_LOCATIONS
The high-level driver tried to call the low-level driver through the IoCallDriver () interface, but the system did not have free space in the stack area, for this reason the low-level driver will not reach the required parameters, since there are no parameters for it at all. This is fatal because the high-level driver thinks it has filled in the parameters for the low-level driver (it must have done something to invoke the low-level driver). However, since there is no free stack space, the end of the packet was overwritten. This is often due to corruption of stack memory blocks. It is necessary to check memory and drivers for errors.
Options:
1 - IRP address
0x00000036: DEVICE_REFERENCE_COUNT_NOT_ZERO
The device driver tried to remove one of the components of its device from the system, but the counter of this component was not equal to zero, which means that there are some outstanding tasks behind this component (the counter indicates an error code, which is why this component cannot be unloaded). This is a driver call error.
Options:
1 - object address
0x0000003E: MULTIPROCESSOR_CONFIGURATION_NOT_SUPPORTED
The multiprocessor system is not symmetrical with respect to each other. For correct symmetry, processors must be of the same type and level. For example, trying to use a Pentium-level processor and an 80486 at the same time will throw an error. In addition, on x86 systems, floating point capability must be present on either all processors or none.
0x0000003F: NO_MORE_SYSTEM_PTES
Not enough PTE (page file entries - paging file access points). Usually the cause is a driver that does not clean up the swap file well and it overflows. Excessive fragmentation of the paging file may also be the cause.
0x00000040: TARGET_MDL_TOO_SMALL
The driver called the IoBuildPartialMdl () function and passed the MDL to it to identify the MDL source portion, but the MDL destination scope is not large enough to display the required address limits. This is a driver error.
0x00000041: MUST_SUCCEED_POOL_EMPTY
The system driver has requested a seat in the Must Suceed Pool. This function cannot be performed because the system does not allocate space in the Must Suceed Pool. Replace or update the faulty system driver.
Options:
0x00000044: MULTIPLE_IRP_COMPLETE_REQUESTS
The driver requested the completion of the IRP, but the package was already completed. This error is difficult to detect. Possible cause - the driver tries to complete the same operation several times. A rare reason - 2 different drivers are trying to take over the package and terminate it. The first usually works, but the second does not. It is difficult to trace which driver did this, as traces of the first driver were overwritten by the second.
Options:
1 - IRP address
0x00000048: CANCEL_STATE_IN_COMPLETED_IRP
This error indicates that the I / O Request Packet (IRP) to be completed has a cancellation order defined in it, i.e. this means that a packet in this mode can be canceled. However, the package is no longer related to the driver, since it has already entered the completion stage.
Options:
1 - IRP address
0x00000049: PAGE_FAULT_WITH_INTERRUPTS_OFF
Page error when accessing memory with disabled IRQ interrupts. The error description is the same as for 0x0000000A.
0x0000004C: FATAL_UNHANDLED_HARD_ERROR
Fatal unrecognized error. The most likely causes are described in 0xC0000218, 0xC000022A or
0xC0000221.
0x0000004D: NO_PAGES_AVAILABLE
No more free page memory to complete the operation. Check for free disk space. Replace the driver. Options:
0x0000004E: PFN_LIST_CORRUPT
The reason is a damaged / faulty driver I / O structure. Options:
0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Occurs when the requested information was not found in memory. The system is checking the page file, but the missing information has been indicated as not being written to the page file.
Options:
1.points to the memory address that made the error
0x00000051: REGISTRY_ERROR
An I / O error occurred with the registry when the system tried to read one of its files, it follows that the error could be caused by a hardware problem or damage to the system itself. It can also mean that the error is caused by an update operation that is used only by the security system and this error occurs when resources are running low. If this error occurs, check if the machine is a PDC or BDC and how many accounts are in the SAM (Account Security Manager) database, if the corresponding libraries are almost full.
Options:
1.value 1 (indicates where the error occurred)
2.value 2 (indicates where the error occurred)
3.may point to a library
4.may be the return code of HvCheckHive, if any
library corrupted
0x00000058: FTDISK_INTERNAL_ERROR
The system booted from the restored primary partition of the array, as a result of which the libraries report that the mirror is in order, but in fact it is not. Real library images are in shadow copy. You need to boot from them.
0x00000067: CONFIG_INITIALIZATION_FAILED
An error means that the registry cannot allocate space for the registry files to work. This error can never appear because the process of reserving such space occurs early in the system boot phase and sufficient space is allocated for the registry.
Options:
1.five
2. Indicates NTOS \ CONFIG \ CMSYSINI that failed.
0x00000069: IO1_INITIALIZATION_FAILED
Failed to initialize the I / O device for an unknown reason. This happens if the system installer has incorrectly detected the hardware during the installation of the system, or the user has incorrectly reconfigured the system.
0x0000006B: PROCESS1_INITIALIZATION_FAILED
Options:
1. reports to the code of the process that decided that the system initialization was not successful.
2. Reports to the location in NTOS \ PS \ PSINIT.C where the error was found.
0x0000006D: SESSION1_INITIALIZATION_FAILED 0x0000006E: SESSION2_INITIALIZATION_FAILED 0x0000006F: SESSION3_INITIALIZATION_FAILED 0x00000070: SESSION4_INITIALIZATION_FAILED 0x00000071: SESSATION_FAILED
These codes (SESSION1 - SESSION5) indicate the location in NTOS \ INIT \ INIT.C where the error was made.
Options:
1. reports the code of the session, which decided that the system initialization was not successful.
0x00000073: CONFIG_LIST_FAILED
Indicates that one of the registry files is damaged or unreadable. One of the following registry files is damaged: SOFTWARE, SECURITY, SAM (Account Security Manager). Possible reason is lack of disk space or insufficient RAM.
0x00000074: BAD_SYSTEM_CONFIG_INFO
This error can occur because the SYSTEM registry file loaded through the NTLDR component is damaged.
This error can also mean that some of the required and their parameters are missing. Loading into LastKnownGood will probably fix this problem. But it is possible that you will have to reinstall the system, or use the rescue disk.
0x00000075: CANNOT_WRITE_CONFIGURATION
This error can occur when additional data cannot be written to the system registry files (SYSTEM and SYSTEM.ALT) at the time of registry initializations at the time of the first phase (when access to file systems appears). This error means that there is no free space on the disk, and an attempt was made to save the registry to a read-only device.
0x00000076: PROCESS_HAS_LOCKED_PAGES
This error can be caused by a driver that is not completely unloaded after an I / O operation. Options:
1.process address
2.number of closed pages
3.number of reserved pages
4.zero
0x00000077: KERNEL_STACK_INPAGE_ERROR
Error reading one of the system kernel pages. The problem lies in a bad block of a virtual memory file or a disk controller error (very rarely, the cause may be a lack of system resources, or rather, a non-virtual memory reserve with status c0000009a may run out).
If the first and second parameters of the error code are 0, then this means that the location of the error in the kernel was not found. This means that the error is caused by bad hardware.
I / O status c000009c (STATUS_DEVICE_DATA_ERROR) or C000016AL (STATUS_DISK_OPERATION_FAILED) usually means the information cannot be read due to a bad block in memory. After reboot automatic check disk will try to determine the address of the bad block in memory. If the status is C0000185 (STATUS_IO_DEVICE_ERROR) and the virtual memory is on a SCSI disk, then check the connection and operation of the SCSI device.
Options:
1.zero
2.zero
3. PTE value at the time of error
4.address of kernel error, or
1.status code
2.I / O status code
3.virtual memory page number
4. Offset in the swap file
0x00000079: MISMATCHED_HAL
The HAL validation level and the HAL configuration type are not appropriate for the system kernel or machine type. This error is most likely caused by the user manually updating either NTOSKRNL.EXE or HAL.DLL. Or on the machine a multiprocessor HAL (MP) and a uniprocessor kernel (UP), or vice versa.
0x0000007A: KERNEL_DATA_INPAGE_ERROR
The page requested by the kernel is not read. The error is caused by a bad block in memory or a disk controller error. See also 0x00000077. Options:
1.type of frozen lock
2. error status (usually I / O code)
3.current process (virtual address for blocking type 3 or PTE)
4.address of virtual memory that cannot be moved to the paging file
0x0000007B: INACCESSIBLE_BOOT_DEVICE
During the installation of the I / O system, the boot device driver may not have been able to initialize the device from which the system was trying to boot, or the file system that should have read this device either failed to initialize or simply did not recognize the information on the device, as file system structure. In the above case, the first argument is the address of the unicode information structure, which is the ARC name of the device from which the boot was attempted. In the second case, the first argument is the address of the device object that cannot be mounted.
If this error occurred during the initial installation of the system, it is possible that the system was installed on a disk or SCSI controller that it does not support. Note that some controllers are only supported by Windows Drivers Libraries (WDL), which must be installed in Custom Install mode.
This error can also occur after installing a new SCSI adapter or controller, or after changing the system partitions. In this case, on x86 systems, you need to edit BOOT.INI.
Options:
1. a pointer to a device object or Unicode string, or ARC name.
0x0000007D: INSTALL_MORE_MEMORY
Not enough RAM to run Windows kernel (5 MB required)
Options:
1.number of physical pages found
2.bottom physical page
3.the top physical page
4.zero
0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
There is a hardware, driver, or low disk space problem. The error can also appear when trying to upgrade Windows XP to Service Pack 2 or Service Pack 3, or Windows Vista when trying to upgrade to Service Pack 1. The cause of the error may be related to the hardware drivers. You need to roll back the changes to the state at the time of the Service Pack installation, or uninstall the installed update. To solve this problem, you need to update the hardware drivers from the manufacturer's website.
0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP
An unexpected kernel-mode exception, or interrupt, has occurred that prevents the kernel from firing. Also, the cause of the error can be an interruption, which entailed immediate death in the form of a double fault - a double fault. The first number in the error code is the interrupt number (8 = double fault). To find out more about what this interrupt is, refer to the Intel x86 family manual.
In other words, an error occurs when the processor makes an error that the kernel cannot handle. Most often, the error occurs due to bad blocks of RAM, and sometimes due to overclocking the processor.
Try to disable the synchronous data transfer function in the BIOS.
0x00000080: NMI_HARDWARE_FAILURE
Kernel initialization error on this hardware. The HAL should provide any specific information it has and invite the user to contact the hardware vendor for technical support.
0x00000085: SETUP_FAILURE
The error occurs when loading the system installer in earlier versions of Windows NT. The setup'a text form no longer uses the bugcheck procedure, so as not to seriously interfere with the installation. Therefore, you will never encounter this error. All error checks have been replaced with friendlier and (where possible) more informative error messages.
0x0000008B: MBR_CHECKSUM_MISMATCH
An error occurs during the boot process when the MBR checksum calculated by the system does not match the bootloader checksum. This usually means a virus. Scan the boot sector with an antivirus program after booting from the CD.
KerBugCheckEx parameters:
1 - Disk signature in MBR
2 - MBR checksum recorded in osloader
3 - Checksum MBR recorded in the system
0x0000008E: PAGE_FAULT_IN_NON_PAGED_AREA
Incompatible or defective RAM memory blocks. Diagnose memory and replace faulty RAM modules.
0x0000008F: PP0_INITIALIZATION_FAILED
An error occurs during the initialization of phase zero of the Plug and Play manager in kernel mode. Check your hardware and system drive.
0x00000090: PP1_INITIALIZATION_FAILED
An error occurs during the initialization of the primary phase of the Plug and Play manager in kernel mode. At this point, the system files, drivers and registry have been initialized. Check your hardware and system drive.
0x00000092: UP_DRIVER_ON_MP_SYSTEM
The error occurs when a uniprocessor driver is loaded on a system where more than one active processor is present. KeBugCheckEx parameters: 1 - Base address of the uniprocessor driver
0x00000093: INVALID_KERNEL_HANDLE
The error appears when kernel code or other critical OS components try to close a handle that is not valid.
Options:
1 - Called handle NtClose
2 - 0 means the protected handle was closed
1 means the wrong handle was closed
0x00000094: KERNEL_STACK_LOCKED_AT_EXIT
This message appears when a thread exists while its stack is marked as blocked. The problem is caused by a hardware driver.
0x00000096: INVALID_WORK_QUEUE_ITEM
0x00000097: BOUND_IMAGE_UNSUPPORTED
The problem is caused by an incorrect hardware driver.
0x00000098: END_OF_NT_EVALUATION_PERIOD
The Windows demo version has ended. Options:
1 - Installation date (lower 32-bit)
2 - Installation date (upper 32-bit)
3 - Trial period in minutes.
0x00000099: INVALID_REGION_OR_SEGMENT
ExInitializeRegion or ExInterlockedExtendRegion was called with the wrong parameter set.
0x0000009A: SYSTEM_LICENSE_VIOLATION
A software license agreement violation has occurred. This could be either due to an attempt to change the product type of the system, or an attempt to change the trial period of the OS.
0x0000009B: UDFS_FILE_SYSTEM
Failed to read or write to UDFS media. The failure can be associated with damage to the file system, or with the appearance of bad sectors on the disk. Also, the failure can be associated with software that changes the structure of the disk (encryption programs, etc.).
0x0000009C: MACHINE_CHECK_EXCEPTION
Fatal Machine Check Exception. The error is associated with improper hardware configuration, processor overclocking, unstable operation of RAM units, overheating of system components, unstable operation of the power supply.
0x0000009F: DRIVER_POWER_STATE_FAILURE
The driver is in an inconsistent or invalid power consumption state. This usually happens due to power failures, reboots, waking from hibernation, etc. It is necessary to replace the faulty driver, or remove the software that controls the file system (antiviruses, encryption programs
0x000000A5: ACPI_BIOS_ERROR
This message is caused by persistent failures in the ACPI BIOS. This problem cannot be solved at the operating system level. A detailed analysis is required.
0x000000B4: VIDEO_DRIVER_INIT_FAILURE
Windows was unable to load the video driver. The problem is mostly related to the video drivers, or there was a hardware conflict with the video card. Reboot into safe mode and change the video driver to standard.
0x000000BE: ATTEMPTED_WRITE_TO_READONLY_MEMORY
The driver tried to write data to read-only memory (ROM), which cannot be written to. The problem is mainly related to the installation of a bad device driver, service, or firmware. Change your driver.
_MEMORY_CORRUPTION
The driver wrote data to an invalid section of memory. Change your driver.
0x000000C2: BAD_POOL_CALLER
The system kernel or driver issued an invalid memory access command. Typically, a bad driver or software caused this error. Change your driver.
0x000000C4: DRIVER_VERIFIER_DETECTED_VIOLATION
The driver checker has encountered a fatal error in the STOP error generating module. Accompanying parameters - parameters that are passed to KeBugCheckEx and displayed on a blue screen. Change your driver.
0x000000C5: DRIVER_CORRUPTED_EXPOOL
An attempt was made to access a high-level IRQL process from an invalid memory location. This error almost always occurs due to drivers that have destroyed the system pool. Change your driver.
0x000000C6: DRIVER_CAUGHT_MODIFYING_FREED_POOL
The driver tried to access a freed memory pool. Change your driver.
0x000000C7: TIMER_OR_DPC_INVALID
A kernel timer or Delayed Procedure Call (DPC) is present in a prohibited area of memory. This error occurs when the driver was unable to complete the kernel timer or Delayed Procedure Call (DPC) before unloading it from memory. Change your driver.
0x000000C9: DRIVER_VERIFIER_IOMANAGER_VIOLATION
This is a message from one of the driver verification managers. Change your driver.
0x000000CB: DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS
An error similar to STOP error 0x00000076. It differs from the latter only in that in this case the error was detected during kernel tracing. The error indicates that the driver or I / O manager cannot open locked pages after an I / O operation. Pay attention to the name of the application driver in the STOP error window. Change your driver.
0x000000CE: DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
The driver cannot undo the stuck state of the system components. The error usually occurs after installing bad drivers or service components. Change your driver.
0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
The system attempted to access paged memory using a kernel process through a high level IRQL. The most common cause is a bad device driver. It can also be caused by damaged RAM, or a corrupted paging file.
0x000000D8: DRIVER_USED_EXCESSIVE_PTES
The error occurs when the driver requests a large amount of kernel memory.
0x000000E3: RESOURCE_NOT_OWNED
Various crashes related to the file system lead to this STOP error. The problem may be related to the NTFS.SYS driver.
0x000000EA: THREAD_STUCK_IN_DEVICE_DRIVER
The problematic device driver has put the system in a hang state. This is usually caused by the display driver trying to enter standby mode. This problem is related to the video adapter, or a bad video driver.
A failure occurred while connecting the boot disk. The error can occur on computers with high-performance disk controllers that have not been correctly configured and installed, or are connected with a poor quality cable. After a normal reboot, the system can resume normal operation as if nothing had happened. Also, this error appears after an incorrect shutdown of Windows and the failure may be associated with damage to the file system.
0x000000F2: HARDWARE_INTERRUPT_STORM
This message appears if the kernel detects an interrupt storm, that is, when an interrupt-level device is unable to issue an interrupt request. This is usually caused by a bad device driver.
0x000000F3: DISORDERLY_SHUTDOWN
Windows shutdown crashed due to insufficient memory. Determine which program is "out of memory", try to find out why virtual memory does not provide the necessary system resources, and investigate if the program (or, sometimes, the driver) refuses to exit without freeing open pages in mind.
0x000000FA: HTTP_DRIVER_CORRUPTED
The system driver Http.sys is corrupted. It is necessary to restore this component from the original disk.
0x000000FC: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
An attempt was made to execute a function in non-executable memory. Options:
1 - Address from which an attempt was made to execute the function
2 - Contents of the page table entry (PTE)
0x000000FD: DIRTY_NOWRITE_PAGES_CONGESTION
There is no free page memory to continue basic system operations.
Options:
1 - The total amount of requested page memory
2 - The amount of paged memory requested with the inability to write.
3 —
4 - Status code at the time of the last write to page memory
0x000000FE: BUGCODE_USB_DRIVER
A fatal error has occurred in the operation of the USB controller and related devices. The problem is usually caused by incorrect operation of the USB controller, or a malfunction of the connected USB devices. Disconnect all USB devices from the computer, also try disabling the USB controller in the BIOS. Update USB drivers.
0x00000101: CLOCK_WATCHDOG_TIMEOUT
Indicates that an expected sync interrupt on a secondary processor on a multiprocessor system was not received within a specified interval. This processor does not handle interrupts. This usually happens when the processor is not responding or has entered an infinite loop.
Options:
1 - Interval of blocking interrupt time by sync pulses, in
nominal system clock ticks
2 - zero
3 - Address of the processor control block (PRCB) for non-responsive
processor
4 - zero
0x00000104: AGP_INVALID_ACCESS
An attempt was made by the GPU to write to memory that was not reserved for this. The error is related to the video driver or the old BIOS version.
Options:
1 - Offset (in ULONG) within AGP pages to first data
ULONG whose data is corrupted
2 - zero
3 - zero
4 - zero
0x00000105: AGP_GART_CORRUPTION
The error appears when the Graphics Aperture Remapping Table (GART) is damaged. The error is caused by improper operation of the DMA (Direct Memory Access) driver
Options:
1 - Base address (virtual) in GART
2 - Bias in GART where distortion is detected
3 - Base address (virtual) from GART cache (copy of GART)
4 - zero
0x00000106: AGP_ILLEGALLY_REPROGRAMMED
The error is caused by an unsigned or damaged video driver. Replace the video driver. Options:
1 - Original team
2 - Current team
3 - zero
4 - zero
0x00000108: THIRD_PARTY_FILE_SYSTEM_FAILURE
A fatal error has occurred in a third-party file system filter. The error can be caused by antivirus software, defragmentation software, data backup, and other third-party utilities. Also try increasing the paging file and RAM size.
0x00000109: CRITICAL_STRUCTURE_CORRUPTION
The system kernel has detected an invalid code or data integrity violation. 64-code systems are immune to this bug. The problem could have been caused by a malfunctioning RAM or by third party drivers.
0x0000010E: VIDEO_MEMORY_MANAGEMENT_INTERNAL
An internal video driver error has been detected. Video driver problem.
0x0000010F: RESOURCE_MANAGER_EXCEPTION_NOT_HANDLED
An exception occurred in the kernel-mode resource manager.
0x00000112: MSRPC_STATE_VIOLATION
The system component msrpc.sys returned an error code during runtime. The error code is specified in the first parameter.
0x00000113: VIDEO_DXGKRNL_FATAL_ERROR
The DirectX Graphics kernel has encountered a fatal error.
0x00000114: VIDEO_SHADOW_DRIVER_FATAL_ERROR
The shadow video driver has encountered a fatal error.
0x00000115: AGP_INTERNAL
A fatal error was detected in the AGP video interface by the video port driver.
0x00000116: VIDEO_TDR_ERROR
The video driver timed out was not successfully reset.
0x0000011C: ATTEMPTED_WRITE_TO_CM_PROTECTED_STORAGE
An attempt was made to write to the write-protected area of the configuration manager: Parameters:
1 - Virtual address of the attempted write command
2 - PTE content
3 - reserved
4 - Reserved The name of the driver attempting the write operation is printed as
the unicode string on the error screen.
0x00000121: DRIVER_VIOLATION
The driver has committed an access violation to one of the memory areas. Options:
1 - describes the type of violation
2 - reserved
3 - Reserved Use a kernel debugger and view the call stack to determine
the name of the driver that caused the access violation.
0x00000122: WHEA_INTERNAL_ERROR
An internal error has occurred in the hardware error detection architecture Windows tools(Windows Hardware Error Architecture (WHEA))
0x00000124: WHEA_UNCORRECTABLE_ERROR
An error has occurred in the hardware of the computer. This error was detected by the Windows Hardware Error Architecture (WHEA)
0x00000127: PAGE_NOT_ZERO
The memory page was not completely filled with zeros. This error occurs due to a hardware failure, or due to the activation of a privileged component of the operating system that made a premature page change in memory.
Options:
page.
3 - zero
4 - zero
0x0000012B: FAULTY_HARDWARE_CORRUPTED_PAGE
A single bit error was detected on a page of memory. This error is related to hardware RAM. Options:
1 - Virtual address in memory, which indicates an invalid
page.
2 - Physical page number
3 - zero
4 - zero
0x0000012C: EXFAT_FILE_SYSTEM
Failed to read or write to the exFat section of the media. The failure can be associated with damage to the file system, or with the appearance of bad sectors on the disk. Also, the failure may be associated with software that changes the structure of the disk (encryption programs, etc.). This failure applies to media formatted for Windows Vista Service Pack 1.
0x1000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
0x1000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
0xC000009A: STATUS_INSUFFICIENT_RESOURCES
The system kernel of the operating system has exhausted all system resources for its work, including the paging file. Check the disk for errors. Expand your hard disk and RAM.
0xC0000135: UNABLE TO LOCATE DLL
Windows tried to load DLL library and got error code. Possible cause - the file is missing or damaged. The system registry may also be damaged.
0xC0000142: DLL Initialization Failure
This error was caused by a damaged system DLL.
0xC0000218: UNKNOWN_HARD_ERROR
The required registry file cannot be loaded. The file may be damaged or missing (rescue disk or Windows reinstallation required). The registry files may have been destroyed due to damage to the hard drive. The driver may have corrupted the registry data when loaded into memory, or the memory where the registry was loaded has a parity error (turn off the external cache and check the RAM).
0xC000021A: STATUS_SYSTEM_PROCESS_TERMINATED
This occurs when Windows has switched to privileged mode and non-privileged mode subsystems such as Winlogon or Client Server Runtime Subsystem (CSRSS) have caused some kind of failure and protection cannot be guaranteed. Because Windows XP cannot function without Winlogon or CSRSS, this is one of the few situations where a non-privileged mode denial of service can cause the system to stop responding. This can also happen when the computer is restarted after the system administrator has changed the permissions so that the SYSTEM account no longer has adequate permissions to access system files and folders. The error can also be caused by a damaged user32.dll file or incorrect system drivers (.sys)
0xC0000221: STATUS_IMAGE_CHECKSUM_MISMATCH
the driver is damaged or the system library has been recognized as damaged. The system does everything to check the integrity of important system files. The blue screen shows the name of the damaged file. If this happens, boot into any other system or, if there are none, reinstall the system. Make sure that the version of the file that was detected as damaged matches the version of the file in the system distribution, and if so, replace it from the disk. Persistent errors with different file names indicate that there are problems with the storage media or with the disk controller where these files are located.
0xC0000244
STOP error occurs when the audit policy activates the CrashOnAuditFail parameter
0xC000026C
Usually indicates a problem with a device driver. More information about this error
0xDEADDEAD: MANUALLY_INITIATED_CRASH1
"It's dead, Jim!" (It's dead Jim!) This STOP error indicates that the user intentionally initiated 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 did not exist, the computer would simply break down. , and you would have to send your equipment for repair, or buy new, or maybe even the whole computer. Therefore, let's pay tribute to the developers of this operating system who take care of our wallets. This concludes our conversation about the famous " Blue screen of death».
Blue Screen of Death (aka BSOD - Blue Screen of Death) is a message on the screen with a blue background about a fatal error in Windows. This message usually contains the code for this stop error. BSOD stops all running processes and informs the user about some critical malfunction... This failure can be caused by various factors, for example, damage to drivers, hardware, improper file handling (file system corruption), etc.
There is no general solution here and each error has its own individual approach. However, we will give general recommendations on what to do in such a situation.
Usually, the first thing the user wants to do is to restart the system in the hope that the problem is not serious and that they can continue working in the Windows environment. We do not recommend do this until you find out the cause of the error that caused the blue screen.
In some cases, the system reboots itself when BSOD is triggered. In this case, you need to disable automatic reboot so that you can see the error.
V system properties(Win + PauseBreak) go to the advanced options section. 
In this window, the tab "Advanced", the item "" is of interest. Click on the Options button. 
In field " System failure»Remove the" checkbox "from the item" Perform automatic reboot "and confirm by pressing" OK ". 
Now you will have time to read and write the error code and the file that caused the error to load. 
Each BSOD contains a hexadecimal critical error code, most often several codes, as shown in the picture. More than 300 such codes are known. Let us consider the most common actions that a user must perform to eliminate them.
x00000001 - APC_INDEX_MISMATCH
There is a mismatch in the APC status index. Most likely BSOD is caused by a failure of one or more of the drivers: ndis.sys; raspppoe.sys; win32k.sys; psi.sys, or there is simply not enough resources on the HDD or RAM. The crash may appear after installing a third-party application. A likely solution is to install the most recent system updates.
0x0000000A- IRQL_NOT_LESS_OR_EQUAL
Diskdump.sys is using the wrong memory address or is incompatible with the OS. If this failure occurs during the installation of the system, then the problem is in the hardware of the PC. Check that the hardware resources being used meet the system requirements. Try reinstalling the OS again. Disable the Plug and Play function. Disable all BIOS antivirus protection functions.
If the error persists, test the RAM. If you have several planks, try working with one of them one at a time. If BSOD stops occurring, then the problem is clearly one of them.
If it did not work, remove all devices that are not urgently needed when installing the OS (network and sound card, expansion cards, video card, DVD drive, additional hard drives and drives, etc.).
0x0000001E- KMODE_EXCEPTION_NOT_HANDLED
The error handler did not catch a kernel-thrown exception. To solve the problem, you need to unambiguously determine which exception was thrown. First of all, try using a different video adapter, update the BIOS, disable the caching function. Check the hardware compatibility with the software you are installing. If you can identify the driver causing the failure, disable and uninstall it. You may need to start in safe mode for these purposes.
x00000020 - KERNEL_APC_PENDING_DURING_EXIT
APC was in idle mode while the thread finished executing.
First of all, you need to pay attention to the drivers installed before the error occurred. The BSOD occurs because Win32k.sys does not process the font parameters correctly, which prevents the APC process from being called asynchronously. Install the latest OS updates and the Symevent.sys driver.
x00000023 - FAT_FILE_SYSTEM
Damage to the FAT file system.
Probably damaged sectors of the drive or IDE driver. To find and fix bad sectors, try using the Chkdsk / f / r function in the console, or use a third-party program like Victoria HDD.
0x00000024- NTFS_FILE_SYSTEM
Damage to FS NTFS.
A malfunction in the ntfs.sys driver prevents the system from reading and writing data from NTFS media. Possible damage to the FS structure of the hard drive. Perform the actions described in the previous error.
0x0000002B- PANIC_STACK_SWITCH
The kernel stack is full. To eliminate it, you should adhere to the general recommendations for resolving the occurrence of BSOD.
0x0000002E- DATA_BUS_ERROR
The data bus is not working properly, the cause of which is a probable failure of the parity of the system memory. The problem is probably in the hardware resources of the PC - incorrect configuration, mismatch of the installed OS, or hardware failure. This code is often called due to defective RAM modules. Replace the failed hardware. Otherwise, follow the standard instructions described in the previous paragraph.
0x0000007B- INACCESSIBLE_BOOT_DEVICE
A very common mistake. Occurs during OS startup. The bootloader cannot detect access to the system partition. Boot device failure. The solution is to change the boot options.
Restart the system and press F8. A window for choosing a download method will open. Run Last Known Good Configuration. Check hardware and software compatibility.
0x00000050- PAGE_FAULT_IN_NONPAGED_AREA
An attempt was made to access invalid system memory. Most often associated with the installation of faulty hardware, namely RAM and video card. Check the device data for defects. In rare cases, the installation of a faulty system service may have caused the problem.
0x0000007A- KERNEL_DATA_INPAGE_ERROR
The required processor core data page cannot be loaded into memory. Most likely, there is a shortage of RAM resources or bad sectors of the hard disk. There may also be a problem with the cable connections. Test RAM and HDD for errors, fix them if possible. Check and clean the plugs of the connecting cables.
