The seventh version of the Windows operating system from Microsoft, although considered one of the most stable, is nevertheless not immune to critical failures. One of the most unpleasant phenomena is the Windows 7 Blue Screen of Death. Not every user knows what to do when it appears. Some people think that the problem will go away on reboot by itself (and for good reason). Others believe that a complete reinstallation of Windows 7 will be required. But before making a decision to fix the problem, you need to know what it is.
So, suppose the user has a blue screen of death. What to do? Windows 7, like any other system in this family, can offer several solutions to the problem, depending on what was the root cause.
But in some cases, in order to get rid of this misfortune in the future, you cannot do without special utilities. We will dwell on them a little later, but for now let's see what it is from the point of view of the system itself.
Roughly speaking, BSoD is a kind of Windows defensive reaction to a critical system failure when a memory dump is written. In other words, the system cannot neutralize the error in work by its own means and because of this it reports that this and that has happened. In each case, decoding the "blue screens of death" Windows 7 can say a lot. Typically, the message on the monitor begins with the word "STOP" followed by a fault code. What does this mean? Yes, only that at the moment some important process, vital for the functioning of the system as a whole, was stopped. How to remove the "blue screen of death" in Windows 7, we will consider a little later, but for now let's dwell on the reasons for its appearance.
When investigating possible problems, you need to clearly divide them into two large categories: failures software(including the system itself) and physical problems with the equipment (for example, when replacing a hard disk, video card, random access memory etc.).
In addition, in Windows 7, solving problems with such problems may also imply a moment related to the fact that there is simply not enough space on the hard drive, which is especially noticeable when automatic system updates are enabled.
Today there are two main groups of failures. Group "A" includes problems with updating or replacing hardware, updating drivers or the system itself, and damage to system components. Group "B" includes incompatible versions of the primary input / output system BIOS, inconsistency of drivers for a specific device, driver conflicts, lack of space on the hard drive, breakdown of hardware components of the computer system, overheating of the processor or power supply, power outages, malfunctions of the brackets RAM, problems with video cards, overclocking (overclocking) results, etc.
As you can see, there can be a lot of reasons for errors and failures. In any case, when such a screen appears, first of all, you should pay attention to the description that is present at the bottom of the message. Separately, we can highlight the most common codes that are most common:
Of course, the list is not limited only to these codes (you never know what situation may arise). However, the most common blue screen of death (0x0000007E) appears. Windows 7 in this case displays a description indicating that an exception was not handled.
But this is just a brief summary. To view the full description of the error or crash, it is best to use a small utility called Blue Screen View. It is this program that can give the key to understanding how to treat the "blue screen of death" of Windows 7. This can be done using the system's own means, which will be discussed further.
In the event that the failure is short-term, for example, due to a sudden power outage and a transition to an uninterruptible power supply, you can use a regular restart with a forced shutdown by long pressing the power button.
But if the "blue screen of death" appears when Windows 7 boots up again, this will already indicate serious damage. For starters, you can simply try to turn off dump and mini-dump recording. This is done through the properties section, called from the right-click menu on the computer icon, where you need to go to the boot and recovery item through the advanced settings tab. In the parameters window, you need to disable automatic reboot and write small dumps, and then perform a complete restart of the system.
If after that the problem is not resolved, it is very likely that this is no longer a software failure, but physical damage to the hardware (most often the problem lies in the hard drive and RAM).
One of the reasons for the appearance of failures can be viruses and malicious codes that target the system. They cause a lot of hassle, rewriting system components and replacing them with their own files, and can also cause a "blue screen of death". What to do? Windows 7 does not have any tools in this case, apart from its own primitive tools in the form of a defender and a firewall.
In the simplest case, you should check the system with a regular anti-virus scanner, but, most likely, you will have to use more powerful programs. The best option would be the free disk utility Kaspersky Rescue Disk, which can boot itself before starting the system and detect viruses that have penetrated deep into the RAM.
If the system itself is damaged, recovery may not work. In this case, it is best to boot into Safe Made mode using the F8 key at startup, and then, if you have constant access to the Internet, perform an online recovery using the command shown in the image below in the command line running as an administrator.
The process will take 5-10 minutes, after which you should register the sfc / scannow command and wait for the verification verdict. In the event of a violation of the integrity of Windows 7, the system files will be restored automatically.
The lack of space in the system partition can also lead to the appearance of the "blue screen of death" Windows 7. How to fix the situation? For this, the system has its own disk cleaning tool. It is advisable to use it, and not the modules of the optimizers, since the latter do not interfere with the system part.
In "Explorer", right-clicking on the disk or partition being scanned brings up the properties menu, in which, on the general settings tab, you can see the clear button. After pressing it in the window, you should select all the components to be removed and confirm your actions.
Incorrectly installed or underloaded updates are often the cause of BSoD. It makes no difference whether automatic updates are turned on, or the search for updates was performed in manual mode.
How to remove the "blue screen of death" Windows 7 in this case? You need to go to the appropriate section "Control Panel" and view the latest installed updates. They will have to be removed one by one, overloading the system each time after uninstalling. Perhaps the reason is precisely in them. As a last resort, if you do not want to do such things manually, you can try to roll back the system to a previous state. But it is worth considering that when automatic installation is enabled, the updates will be integrated into the system again.
But in the first case, having found out exactly which update failed, it can be excluded from the list when you search again in manual mode.
The most problematic is the situation when the cause of the failure lies in the hard drive. In the simplest case, you will have to check it for errors.
To do this, use the checker from the properties menu, but the settings activate the lines automatic fix bugs and fixes for bad clusters. The same procedure can be performed from the command console, where you need to write the chkdsk / x / f / r line.
If the damage to the hard drive is of a physical nature, there is nothing to be done, although some experts recommend using a special hard drive magnetization reversal program called HDD Regenerator. True, here there are legitimate doubts about the fact that it is possible to restore the disk (in the sense of using software). Nevertheless…
Another issue is outdated or incompatible BIOS firmware. The screen will be displayed immediately at startup. In this situation, nothing else remains but to turn to the manufacturer's resource on the Internet. As already clear, you need to download the firmware and install it.
BIOS version information can be found in the system information section, which is called by the msinfo32 command from the Run (Win + R) console.
But most often the appearance of the deadly screen is influenced by drivers or conflicts between them (the most common problems arise with video cards). At the same time, if you turn to the "Device Manager" (the devmgmt.msc command in the "Run" console or the section of the same name in the "Control Panel"), it is not recommended to update the drivers.
It is best to remove the problematic driver and then install it from scratch. In some cases, this may not give a positive result. Therefore, you will have to completely remove the device. When restarting the system, it is advisable not to use the installation of the most suitable driver from its own database, but to install it, for example, from the Driver Pack Solution catalog or pre-download the required driver from the equipment manufacturer's website.
But to search for the driver itself, first in the same "Device Manager" for the problem component, you need to find the VEN and DEV identifiers in the properties with the transition to the details tab, where the hardware ID display is selected from the drop-down list. For reliability, it is best to use the longest line in the description.
But suppose the "blue screen of death" reappears. What to do? Windows 7 seems to have exhausted its capabilities. Apparently, the problem is in the RAM.
It is possible to determine the cause of the failure, provided that the appropriate verification program is used. The most powerful utility is Memtest86 +. But there is also a downside to the coin. On stationary PCs, you can completely simply remove the memory strips from the slots on the motherboard one by one, overload the system and look at its behavior. You cannot do this in laptops, so you have to contact a service center.
Finally, albeit infrequently, there is a problem with programs remote access... In particular, this is an error in the Win32k.sys file. The way out of this situation can be the usual removal of the faulty application. Only uninstallation is best done not using system tools, but using programs like iObit Uninstaller for this, which can not only delete the main program files, but also completely clean the system of residual files, folders and even system registry entries.
As you can see from the above, there can be a lot of reasons for BSoD crashes. And it will not always be appropriate to reinstall Windows 7. Finally, it remains to give advice to the majority of users who believe that such a screen means a "crash" of the system. There is nothing too critical in this. In most cases, a simple reboot or reinstallation of drivers helps, of course, provided that there is no physical damage to the hardware.
In this article, we will talk about such a phenomenon in the Windows operating system as - Blue screen of death or in our “ blue screen of death", Also called STOP error. Let's consider the main causes of occurrence and decipher the codes of these errors.
And first, let's give a definition of what is “ Blue screen of death"Is a method of generating a fatal error message in Windows NT 4.0, Windows 2000, Windows 2003, Windows XP, Windows Vista and Windows 7, caused by malfunctioning of some programs or drivers, but still more often due to hardware failures of the computer.
A blue screen stops all processes in the operating system and freezes the computer after displaying a blue screen. In general, the blue screen helps us, you ask, but because it prevents the destruction of the operating system and the decommissioning of equipment. When “ blue screen of death»The error code and how to solve it are displayed. But it may be that the STOP error was caused, for example, by distortion of data packets transmitted over the local network, in this case a simple reboot helps. If the error appears every time you start the operating system, then this 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 reasons for the error that occurred, it is necessary to rewrite the first two lines of the STOP error. For example, as shown just below:
STOP 0x0000006B (0xC0000022, 0x00000000, 0x00000000, 0x00000000) PROCESS1_INITIALIZATION_FAILED
where 0xC0000022, 0x00000000, 0x00000000, 0x00000000- parameters that reveal the meaning of this BSoD.
By the way, there is a small feature, it lies in the fact that in the operating system, in order to see the blue screen, you must first enable this windows feature, or you simply will not see this screen, if an error occurs, the computer will simply reboot quickly (and so every time).
To enable this option, go to the properties "My Computer", select the "Advanced" tab. In the Startup and Recovery box, click the Options button. In the window that appears, uncheck the box next to "Perform automatic restart".
With the appearance of a STOP error in the text of the message, a method for solving it is briefly presented, though in English. But I can say for sure that at the present time a common cause of STOP errors is hardware problems with the hardware of the computer or its software parts, and sometimes due to inconsistencies of one with the other.
Now let's go directly to the errors themselves and look at their causes and short solutions.
0x00000001: APC_INDEX_MISMATCH
Internal kernel error. The problem is most often associated with a driver problem, insufficient RAM or hard disk space.
0x0000000A: IRQL_NOT_LESS_OR_EQUAL
There was a tampering with virtual memory on an internal high IRQ process. The most common cause is a device driver using the wrong address. The error occurs due to bad drivers. Rarely occurs due to a malfunction of one of the devices in the system.
Options:
0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
This is a very common mistake. Usually, the excluded address points to the driver or function that caused the stop screen. Always pay attention not only to the specified driver, but also to the address itself or the image containing this error. This is usually the exception code 0x80000003. This error means that a breakpoint or handler was initialized when accessing memory, but the system booted with the / NODEBUG switch. This error may not appear too often. If the error appears constantly, make sure that the debugger is connected and the system boots with the / DEBUG key.
On non-Intel systems, if the exception address is 0XBFC0304, the error occurs due to processor caching. If the error persists, contact the processor manufacturer.
Typically, analysis of the second parameter of this message is required, which indicates the address of the driver / function that caused the problem.
Options:
0x00000020: KERNEL_APC_PENDING_DURING_EXIT
The error name indicates a damaged / disabled APC counter. If you have such a situation, check all the file systems installed on the machine, for example using the EMRD rescue kit.
The current IRQL must be zero. If the IRQ is not equal to zero, then a certain order of unloading drivers, when returning to a higher IRQ level, may cause an error. Try to remember what you were doing or which applications were closing, which drivers were installed when the blue screen occurred. This symptom indicates a serious problem with third-party drivers.
Options:
0x00000023: FAT_FILE_SYSTEM
FAT).
0x00000024: NTFS_FILE_SYSTEM
There was a failure to read or write to a hard disk partition formatted as NTFS... The failure can be associated with damage to the file system, or with the appearance of bad sectors on the disk. Also, the failure can be associated with software that changes the disk structure ( encryption programs and stuff).
0x0000002A: INCONSISTENT_IRP
I / O Request Packet (IRP) is not functional; occurs when a field or more than one field is invalid compared to the persistent state of the IRP. For example, the IRP was already disabled when a device driver was waiting for a command.
Options:
1 - the address at which the IRP was found in idle mode
0x0000002B: PANIC_STACK_SWITCH
This error occurs when the kernel stack area is full. The error occurs when the kernel driver uses too much stack space. Damage to the kernel itself can also be a possible cause of the error.
0x0000002E: DATA_BUS_ERROR
This STOP error most often occurs due to a failure in the RAM area. This can happen when a driver tries to access a memory address that does not exist.
Options:
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 space in the stack area, the end of the packet was overwritten. This is often due to corruption of stack memory blocks. It is necessary to check the memory and drivers for errors.
Options:
1 - IRP address
0x00000036: DEVICE_REFERENCE_COUNT_NOT_ZERO
The device driver tried to remove one of the components of its device from the system, but the counter of this component was not equal to zero, which means that there are some outstanding tasks behind this component (the counter indicates an error code, due to which this component cannot be unloaded). This is a driver call error.
Options:
1 - object address
0x0000003E: MULTIPROCESSOR_CONFIGURATION_NOT_SUPPORTED
The multiprocessor system is not symmetrical with respect to each other. For correct symmetry, processors must be of the same type and level. For example, trying to use a Pentium-level processor and an 80486 at the same time will throw an error. Also, on x86 systems, floating point capability must be present on either all processors or none.
0x0000003F: NO_MORE_SYSTEM_PTES
Not enough PTE (page file entries - paging file access points). Usually the cause is a driver that does not clean up the swap file well and it overflows. Excessive fragmentation of the paging file may also be the cause.
0x00000040: TARGET_MDL_TOO_SMALL
The driver called the IoBuildPartialMdl () function and passed the MDL to it to identify the MDL source portion, but the MDL destination scope is not large enough to map 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 an IRP to be completed, but the package was already completed. This error is difficult to detect. Possible cause - the driver tries to complete the same operation several times. A rare reason - 2 different drivers are trying to take over the package and terminate it. The first usually works, but the second does not. It is difficult to trace which driver did this, as traces of the first driver were overwritten by the second.
Options:
1 - IRP address
0x00000048: CANCEL_STATE_IN_COMPLETED_IRP
This error indicates that the I / O Request Packet (IRP) to be completed has a cancellation order defined in it, i.e. this means that a packet in this mode can be canceled. However, the package is no longer related to the driver, since it has already entered the completion stage.
Options:
1 - IRP address
0x00000049: PAGE_FAULT_WITH_INTERRUPTS_OFF
Page error while accessing memory with disabled IRQ interrupts. The error description is the same as for 0x0000000A.
0x0000004C: FATAL_UNHANDLED_HARD_ERROR
Fatal unrecognized error. The most likely causes are described in 0xC0000218, 0xC000022A or
0xC0000221.
0x0000004D: NO_PAGES_AVAILABLE
No more free page memory to complete the operation. Check for free disk space. Replace the driver. Options:
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 a BDC and how many accounts are in the SAM (Account Security Manager) database, if the corresponding libraries are almost full.
Options:
1.value 1 (indicates where the error occurred)
2.value 2 (indicates where the error occurred)
3.may point to a library
4.may be the return code of HvCheckHive, if any
library corrupted
0x00000058: FTDISK_INTERNAL_ERROR
The system booted from the restored primary partition of the array, as a result of which the libraries report that the mirror is in order, but in fact it is not. Real library images are in shadow copy. You need to boot from them.
0x00000067: CONFIG_INITIALIZATION_FAILED
An error means that the registry cannot allocate space for the registry files to function. This error can never appear because the process of reserving such space occurs early in the system boot phase and sufficient space is allocated for the registry.
Options:
1.five
2. Indicates NTOS \ CONFIG \ CMSYSINI that failed.
0x00000069: IO1_INITIALIZATION_FAILED
Failed to initialize the I / O device for an unknown reason. This happens if the system installer has incorrectly detected the hardware during the installation of the system, or the user has incorrectly reconfigured the system.
0x0000006B: PROCESS1_INITIALIZATION_FAILED
Options:
1. reports to the code of the process that decided that the system initialization was not successful.
2. Reports to the location in NTOS \ PS \ PSINIT.C where the error was found.
0x0000006D: SESSION1_INITIALIZATION_FAILED 0x0000006E: SESSION2_INITIALIZATION_FAILED 0x0000006F: SESSION3_INITIALIZATION_FAILED 0x00000070: SESSION4_INITIALIZATION_FAILED 0x00000071: SESSATION_FAILEDIAL
These codes (SESSION1 - SESSION5) indicate the location in NTOS \ INIT \ INIT.C where the error was made.
Options:
1. reports the code of the session, which decided that the system initialization was not successful.
0x00000073: CONFIG_LIST_FAILED
Indicates that one of the registry files is damaged or unreadable. One of the following registry files is damaged: SOFTWARE, SECURITY, SAM (Account Security Manager). Possible reason is lack of disk space or insufficient RAM.
0x00000074: BAD_SYSTEM_CONFIG_INFO
This error can occur because the SYSTEM registry file loaded through the NTLDR component is damaged.
This error can also mean that some required and their parameters are missing. Loading into LastKnownGood will probably fix this problem. But it is possible that you will have to reinstall the system, or use the rescue disk.
0x00000075: CANNOT_WRITE_CONFIGURATION
This error can occur when additional data cannot be written to the system registry files (SYSTEM and SYSTEM.ALT) at the time of registry initializations at the time of the first phase (when access to file systems appears). This error means that there is no free space on the disk and an attempt was made to save the registry to a read-only device.
0x00000076: PROCESS_HAS_LOCKED_PAGES
This error can be caused by a driver that is not completely unloaded after an I / O operation. Options:
1.process address
2.number of closed pages
3.number of reserved pages
4.zero
0x00000077: KERNEL_STACK_INPAGE_ERROR
Error reading one of the system kernel pages. The problem lies in a bad block of a virtual memory file or a disk controller error (very rarely, the cause may be a lack of system resources, or rather, the non-virtual memory reserve with status c0000009a may run out).
If the first and second parameters of the error code are 0, it means that the location of the error in the kernel was not found. This means that the error is caused by bad hardware.
I / O status c000009c (STATUS_DEVICE_DATA_ERROR) or C000016AL (STATUS_DISK_OPERATION_FAILED) usually means the information cannot be read due to a bad block in memory. After 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. Also, the error may 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 the hardware drivers. You need to roll back the changes to the state at the time of the Service Pack installation, or uninstall the installed update. To solve this problem, you need to update the hardware drivers from the manufacturer's website.
0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP
An unexpected kernel-mode exception, or interrupt, has occurred that prevents the kernel from firing. Also, the cause of the error can be an interrupt, which entailed immediate death in the form of a double fault - a double fault. The first number in the error code is the interrupt number (8 = double fault). To find out more about what this interrupt is, refer to the Intel x86 family manual.
In other words, an error occurs when the processor makes an error that the kernel cannot handle. Most often, the error occurs due to bad blocks of RAM, and sometimes due to overclocking the processor.
Try to disable the synchronous data transfer function in the BIOS.
0x00000080: NMI_HARDWARE_FAILURE
Kernel initialization error on this hardware. The HAL should provide any specific information it has and invite the user to contact the hardware vendor for technical support.
0x00000085: SETUP_FAILURE
The error occurs when loading the system installer in earlier versions of Windows NT. The setup'a text form no longer uses a bugcheck procedure so as not to seriously interfere with the installation. Therefore, you will never encounter this error. All error checks have been replaced with friendlier and (where possible) more informative error messages.
0x0000008B: MBR_CHECKSUM_MISMATCH
An error occurs during the boot process when the MBR checksum calculated by the system does not match the bootloader checksum. This usually means a virus. Scan the boot sector with an antivirus program after booting from the CD.
KerBugCheckEx parameters:
1 - Disk signature in MBR
2 - MBR checksum recorded in osloader
3 - Checksum MBR recorded in the system
0x0000008E: PAGE_FAULT_IN_NON_PAGED_AREA
Incompatible or defective RAM memory blocks. Diagnose memory and replace faulty RAM modules.
0x0000008F: PP0_INITIALIZATION_FAILED
An error occurs during the initialization of phase zero of the Plug and Play manager in kernel mode. Check your hardware and system drive.
0x00000090: PP1_INITIALIZATION_FAILED
An error occurs during the initialization of the primary phase of the Plug and Play manager in kernel mode. At this point, the system files, drivers and registry have been initialized. Check your hardware and system drive.
0x00000092: UP_DRIVER_ON_MP_SYSTEM
The error occurs when a uniprocessor driver is loaded on a system where more than one active processor is present. KeBugCheckEx parameters: 1 - Base address of the uniprocessor driver
0x00000093: INVALID_KERNEL_HANDLE
The error appears when kernel code or other critical OS components try to close a handle that is not valid.
Options:
1 - Called handle NtClose
2 - 0 means the protected handle was closed
1 means the wrong handle was closed
0x00000094: KERNEL_STACK_LOCKED_AT_EXIT
This message appears when a thread exists while its stack is marked as blocked. The problem is caused by a hardware driver.
0x00000096: INVALID_WORK_QUEUE_ITEM
0x00000097: BOUND_IMAGE_UNSUPPORTED
The problem is caused by an incorrect hardware driver.
0x00000098: END_OF_NT_EVALUATION_PERIOD
The Windows demo version has ended. Options:
1 - Installation date (lower 32-bit)
2 - Installation date (upper 32-bit)
3 - Trial period in minutes.
0x00000099: INVALID_REGION_OR_SEGMENT
ExInitializeRegion or ExInterlockedExtendRegion were called with the wrong parameter set.
0x0000009A: SYSTEM_LICENSE_VIOLATION
A software license agreement violation has occurred. This could be either an attempt to change the product type of the system, or an attempt to change the OS trial period.
0x0000009B: UDFS_FILE_SYSTEM
Failed to read or write to UDFS media. The failure can be associated with damage to the file system, or with the appearance of bad sectors on the disk. Also, the failure may be associated with software that changes the structure of the disk (encryption programs, etc.).
0x0000009C: MACHINE_CHECK_EXCEPTION
Fatal Error Machine Check Exception. The error is associated with improper hardware configuration, processor overclocking, unstable operation of RAM units, overheating of system components, unstable operation of the power supply.
0x0000009F: DRIVER_POWER_STATE_FAILURE
The driver is in an inconsistent or invalid power consumption state. This usually happens due to power failures, reboots, waking from hibernation, etc. It is necessary to replace the faulty driver, or remove the software that controls the file system (antiviruses, encryption programs
0x000000A5: ACPI_BIOS_ERROR
This message is caused by persistent failures in the ACPI BIOS. This problem cannot be solved at the operating system level. A detailed analysis is required.
0x000000B4: VIDEO_DRIVER_INIT_FAILURE
Windows was unable to load the video driver. The problem is mostly related to the video drivers, or there was a hardware conflict with the video card. Reboot into safe mode and change the video driver to standard.
0x000000BE: ATTEMPTED_WRITE_TO_READONLY_MEMORY
The driver tried to write data to read-only memory (ROM), which cannot be written to. The problem is mainly related to the installation of a bad device driver, service, or firmware. Change your driver.
_MEMORY_CORRUPTION
The driver wrote data to an invalid section of memory. Change your driver.
0x000000C2: BAD_POOL_CALLER
The system kernel or driver issued an invalid memory access command. Typically, a bad driver or software has caused this error. Change your driver.
0x000000C4: DRIVER_VERIFIER_DETECTED_VIOLATION
The driver checker encountered a fatal error in the STOP error generating module. Accompanying parameters are parameters that are passed to KeBugCheckEx and displayed on a blue screen. Change your driver.
0x000000C5: DRIVER_CORRUPTED_EXPOOL
An attempt was made to access a high-level IRQL process from an invalid memory location. This error almost always occurs due to drivers that have corrupted the system pool. Change your driver.
0x000000C6: DRIVER_CAUGHT_MODIFYING_FREED_POOL
The driver tried to access a freed memory pool. Change your driver.
0x000000C7: TIMER_OR_DPC_INVALID
A kernel timer or Delayed Procedure Call (DPC) is present in a prohibited area of memory. This error occurs when the driver was unable to complete the kernel timer or Delayed Procedure Call (DPC) before unloading it from memory. Change your driver.
0x000000C9: DRIVER_VERIFIER_IOMANAGER_VIOLATION
This is a message from one of the driver verification managers. Change your driver.
0x000000CB: DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS
An error similar to STOP error 0x00000076. It differs from the latter only in that in this case the error was detected during kernel tracing. The error indicates that the driver or I / O manager cannot open locked pages after an I / O operation. Pay attention to the name of the application driver in the STOP error window. Change your driver.
0x000000CE: DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
The driver cannot undo the stuck state of the system components. The error usually occurs after installing bad drivers or service components. Change your driver.
0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
The system attempted to access paged memory using a kernel process through a high level IRQL. The most common cause is a bad device driver. It can also be caused by damaged RAM, or a corrupted paging file.
0x000000D8: DRIVER_USED_EXCESSIVE_PTES
The error occurs when the driver requests a large amount of kernel memory.
0x000000E3: RESOURCE_NOT_OWNED
Various crashes related to the file system lead to this STOP error. The problem may be related to the NTFS.SYS driver.
0x000000EA: THREAD_STUCK_IN_DEVICE_DRIVER
The problematic device driver has put the system into a hang state. This is usually caused by the display driver trying to enter standby mode. This problem is related to the video adapter, or a bad video driver.
A failure occurred while connecting 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 impossibility of writing.
3 —
4 - Status code at the time of the last write to page memory
0x000000FE: BUGCODE_USB_DRIVER
A fatal error has occurred in the operation of the USB controller and related devices. The problem is usually caused by incorrect operation of the USB controller, or a malfunction of the connected USB devices. Disconnect all USB devices from the computer, also try disabling the USB controller in the BIOS. Update USB drivers.
0x00000101: CLOCK_WATCHDOG_TIMEOUT
Indicates that an expected sync interrupt on a secondary processor on a multiprocessor system was not received within a specified interval. This processor does not handle interrupts. This usually happens when the processor is not responding or has entered an infinite loop.
Options:
1 - Interval of blocking interrupt time by sync pulses, in
nominal system clock ticks
2 - zero
3 - Address of the processor control block (PRCB) for non-responsive
processor
4 - zero
0x00000104: AGP_INVALID_ACCESS
An attempt was made by the GPU to write to memory that was not reserved for this. The error is related to the video driver or the old BIOS version.
Options:
1 - Offset (in ULONG) within AGP pages to first data
ULONG whose data is corrupted
2 - zero
3 - zero
4 - zero
0x00000105: AGP_GART_CORRUPTION
The error appears when the Graphics Aperture Remapping Table (GART) is damaged. The error is caused by improper operation of the DMA (Direct Memory Access) driver
Options:
1 - Base address (virtual) in GART
2 - Bias in GART where distortion is detected
3 - Base address (virtual) from GART cache (copy of GART)
4 - zero
0x00000106: AGP_ILLEGALLY_REPROGRAMMED
The error is caused by an unsigned or damaged video driver. Replace the video driver. Options:
1 - Original team
2 - Current team
3 - zero
4 - zero
0x00000108: THIRD_PARTY_FILE_SYSTEM_FAILURE
A fatal error has occurred in a third-party file system filter. The error can be caused by antivirus software, defragmentation software, data backup, and other third-party utilities. Try increasing the paging file and RAM as well.
0x00000109: CRITICAL_STRUCTURE_CORRUPTION
The system kernel has detected incorrect code or data integrity violation. 64-code based systems are immune to this bug. The problem could be caused by a malfunctioning RAM or third party drivers.
0x0000010E: VIDEO_MEMORY_MANAGEMENT_INTERNAL
An internal video driver error has been detected. Video driver problem.
0x0000010F: RESOURCE_MANAGER_EXCEPTION_NOT_HANDLED
An exception occurred in the kernel-mode resource manager.
0x00000112: MSRPC_STATE_VIOLATION
The system component msrpc.sys returned an error code during runtime. The error code is specified in the first parameter.
0x00000113: VIDEO_DXGKRNL_FATAL_ERROR
The DirectX Graphics kernel has encountered a fatal error.
0x00000114: VIDEO_SHADOW_DRIVER_FATAL_ERROR
The shadow video driver has encountered a fatal error.
0x00000115: AGP_INTERNAL
A fatal error was detected by the video port driver in the AGP video interface.
0x00000116: VIDEO_TDR_ERROR
The video driver timeout was not successfully reset.
0x0000011C: ATTEMPTED_WRITE_TO_CM_PROTECTED_STORAGE
An attempt was made to write to the write-protected area of the configuration manager: Parameters:
1 - Virtual address of the attempted write command
2 - PTE content
3 - reserved
4 - Reserved The name of the driver attempting the write operation is printed as
the unicode string on the error screen.
0x00000121: DRIVER_VIOLATION
The driver has committed an access violation to one of the memory areas. Options:
1 - describes the type of violation
2 - reserved
3 - Reserved Use a kernel debugger and view the call stack to determine
the name of the driver that caused the access violation.
0x00000122: WHEA_INTERNAL_ERROR
An internal error has occurred in the 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 - The virtual address in memory, which indicates an invalid
page.
2 - Physical page number
3 - zero
4 - zero
0x0000012C: EXFAT_FILE_SYSTEM
Failed to read or write to the exFat section of the media. The failure can be associated with damage to the file system, or with the appearance of bad sectors on the disk. Also, the failure may be associated with software that changes the structure of the disk (encryption programs, etc.). This failure applies to media formatted for Windows Vista Service Pack 1.
0x1000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
0x1000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
0xC000009A: STATUS_INSUFFICIENT_RESOURCES
The system kernel of the operating system has exhausted all system resources for its work, including the paging file. Check the disk for errors. Expand your hard disk and RAM.
0xC0000135: UNABLE TO LOCATE DLL
Windows tried to load DLL and got error code. Possible cause - the file is missing or damaged. The system registry may also be damaged.
0xC0000142: DLL Initialization Failure
This error was caused by a damaged system DLL.
0xC0000218: UNKNOWN_HARD_ERROR
The required registry file cannot be loaded. The file may be damaged or missing (rescue disk or Windows reinstallation required). The registry files may have been corrupted due to damage to the hard drive. The driver may have corrupted the registry data when loaded into memory, or the memory where the registry was loaded has a parity error (turn off the external cache and check the RAM).
0xC000021A: STATUS_SYSTEM_PROCESS_TERMINATED
This occurs when Windows has switched to privileged mode and non-privileged mode subsystems such as Winlogon or Client Server Runtime Subsystem (CSRSS) have caused some kind of failure and protection cannot be guaranteed. Because Windows XP cannot function without Winlogon or CSRSS, this is one of the few situations where a non-privileged mode denial of service can cause the system to stop responding. This can also happen when the computer is restarted after the system administrator has changed the permissions so that the SYSTEM Account no longer had adequate permissions to access system files and folders. The error can also be caused by a damaged user32.dll file or incorrect system drivers (.sys)
0xC0000221: STATUS_IMAGE_CHECKSUM_MISMATCH
the driver is damaged or the system library has been recognized as damaged. The system does everything to check the integrity of important system files. The blue screen shows the name of the damaged file. If this happens, boot into any other system or, if there are none, reinstall the system. Make sure that the version of the file that was detected as damaged matches the version of the file in the system distribution, and if so, replace it from the disk. Persistent errors with different file names indicate that there are problems with the storage media or with the disk controller where these files are located.
0xC0000244
STOP error occurs when audit policy activates the CrashOnAuditFail parameter
0xC000026C
Usually indicates a problem with a device driver. More information about this error
0xDEADDEAD: MANUALLY_INITIATED_CRASH1
"It's dead, Jim!" (It's dead Jim!) This STOP error indicates that the user intentionally initiated the crash, either from the kernel debugger or the keyboard.
Here is a small list of errors that can appear in the operating systems Windows NT 4.0, Windows 2000, Windows 2003, Windows XP, Windows Vista and Windows 7. Everyone is afraid of the blue screen of death, but in fact, if it did not exist, the computer would simply break down. , and you would have to send your equipment for repair, or buy new, or maybe even the whole computer. So let's pay tribute to the developers of this operating system who take care of our wallets. This is where we end our conversation about the famous " Blue screen of death».
Tweet
BSoD - Blue Sceen of Death, blue screen of death. It appears in the most critical situations when closing a faulty program cannot be avoided.
Operating room Windows system has several levels of running programs. We see only the topmost one - open windows programs and running services. It is them that the Task Manager shows. When one of the programs makes an error that it is unable to handle and work around, it, as many users say, "crashes". You can start again and work on.
Software modules running at a lower level (drivers) cannot restart on error. The Windows operating system tries to protect the user from many errors, but this does not always work out and it capitulates, showing a sad face or a set of characters on the computer screen.
You need to understand that drivers are an intermediary between the software and hardware of the computer. Drivers can fail (programmers are also people, they can fail to take into account or make mistakes), and the iron part of the computer.
1. Appearance of a blue screen with incomprehensible symbols or a sad emoticon.
In 99% of cases, the computer restarts itself due to a critical error (BSoD), but sometimes the situation is worse: problems with the power supply or the motherboard. If you have a desktop PC, check to see if it is bloated anywhere.
1. Overheating. Overheating of the video card, processor leads to a blue screen of death.
By the way, in Windows XP, when the video card overheats, BSoD always occurred, in Vista and newer the video driver simply reboots. If you see the inscription "The video driver stopped responding and was restored", then this is the overheating of the video card:
The newer Windows, the better the crash protection. Hopefully, in some Windows XV, instead of a blue screen, we will see an error notification that does not interfere with the work.
2. Failure of RAM. You can, but in order not to get your finger in the sky, first read on - perhaps the cause of your blue screen of death is in something else.
If you installed new RAM in your computer and got frequent BSoDs, change it to a working one in the store. There are no other ways to overcome blue screens of death when replacing RAM.
3. Failure of other hardware. Maybe the voltage in the power supply unit "sags". Maybe contact is lost somewhere. Maybe your computer doesn't like the full moon. There are many reasons, you can guess endlessly.
If, after you have analyzed the minidump (more on that below) and eliminated errors, the blue screen does not go anywhere, it is worth replacing all the components in turn. You can't just take and determine the cause of BSoD, if each time the error codes are different.
4. Overclocking. If you are an advanced overclocker, then you know what overclocking has to do with BSoD. If not, don't overclock your computer.
5. Failure of the driver (s). The BSoD is not necessarily a hardware issue. Unstable drivers are a frequent visitor to users' computers. How to identify a faulty driver, will be further.
6. Viruses. Be sure to check your computer with some or.
I am never tired of being surprised at the self-confidence of users who declare “ I have no viruses and no antivirus either! I have direct hands / I only sit on trusted sites / sometimes I check with a one-time antivirus and therefore everything is fine!". Leaving aside the debate about how you can live without antivirus, consider this: if a person sees BSoD, they have is no longer a normal situation. How can you say that there are no viruses and this is not the cause of the blue screen?
Also, do not think that if you have an antivirus installed with the most recent databases, there can be no viruses. Check with others to completely rule out the possibility.
7. Antiviruses. It's funny (and sad) that antivirus software can cause it to crash. Remove the antivirus for a while. Blue screens of death have stopped appearing? Install a new one so that blue screens do not appear due to reason # 6.
8. Windows Updates. The developers at Microsoft sometimes don't test updates well. Some, because of this, completely disable Windows Update and sit without updates, although this is not an option. Control Panel - Programs and Features - View installed updates- right click - Delete recently installed updates, then check Windows is working. Has everything returned to normal? Just do not install updates for a couple of weeks - usually some patching update comes out for the update during this time and everything becomes fine.
9. Failure of programs. This happens, but rarely. If you see BSoD while playing a game or while running a certain program, I advise you to check your computer for overheating, because most programs are not able to cause a blue screen, with the exception of installing drivers into the system (antiviruses, virtual disk emulators, game protection systems like PunkBuster, accounting programs working with digital keys).
10. Errors of the file system of the hard disk. It will not be superfluous
As you can see, there are quite a few reasons and it makes no sense to guess. Fortunately, the blue screen of death contains clues as to why Windows suddenly started crashing. Among the incomprehensible text will be error codes containing a direct indication of what caused the failure.
Most often BSoD you won't see since in Windows settings By default, computer restart is enabled on critical errors.
You can disable automatic Windows restart like this: Control Panel - System - Extra options Systems - Parameters- put / remove jackdaws as in the screenshot below:
Pay attention to the item "Small memory dump" - put it too.
The checkbox "Write event to the system log" is set by default, which means that the error codes will be in the Windows Log.
Go to Control Panel - Administration - Event Viewer - System- and look for the line in the list that coincides in time with the appearance of a blue screen or restarting the computer:
Look for the error code (in the screenshot above it is 0x0000009f) in Google and read the first few sites in the search results, follow the recommendations that helped others. If a driver is specified (a word ending with .sys, then it's generally great - the likely culprit is found right away, you need to install a driver for this device of an older / newer version. If there is no clear and clear indication of the BSoD reason for the indicated error code on the Internet, read my instructions further.
If there is nothing in the Windows Log, wait for the blue screen to appear and see the error there:
Just search Google for error code information and follow the recommendations.
Unfortunately, if the problem is in a faulty driver, it is not always displayed on the blue screen. The error code is also not always informative. It is necessary to analyze the minidump file generated during the BSoD occurrence and containing information about the crash, in particular which drivers reported the error. There are two programs for analyzing minidump: Windows Debugging Tools and BlueScreenView. Unfortunately, the first one is too difficult for novice users, although it gives a more informative result. In 99% of cases, a second, simple and free BlueScreenView is enough.
The BlueScreenView installer is available from this link.
After starting the program, you will see a window in which at the top there will be minidumps created by the system, information about them, at the bottom - a list of drivers. Failed drivers will be highlighted in yellow.
A blue screen appears with the text ATTEMPTED_WRITE_TO_READONLY_MEMORY. Watching the minidump:
The ATTEMPTED_WRITE_TO_READONLY_MEMORY error, judging by googling, is caused by some kind of driver. The likely culprit in this case is nv4_disp.sys. There are others, but they are part of the system, statistically unlikely that they are the cause. A google search showed that nv4_disp.sys is a graphics card driver from nVidia. Three steps:
1. Checking the video card for overheating.
2. Installing an older video card driver (new if there is an old one). This is done with any drivers, not just video cards.
3. Installing a video card in another computer.
4. If a blue screen appears on another computer, take the video card to the service center. If the warranty is still valid, you can replace it with a working one free of charge.
5. Doesn't the blue screen appear on the other computer? Try installing a different power supply on yours - the reason may be in it.
6. Doesn't it help? Reinstall Windows cleanly.
7. If this does not help, take it to the service center for diagnostics.
The blue screen labeled PAGE_FAULT_IN_NONPAGED_AREA comes with a lot of problems:
If ntfs.sys was the likely faulty driver, then I would recommend checking HDD for errors, and also replace the ribbon cable from the hard drive to the motherboard. In this case, BlueScreenView points to the USB port driver and this could be true, but where I took the dump from for example, the person is to blame motherboard- capacitors swelled on it. The solution is to hold the system unit in hand and stomp to the service center.
I found this minidump on the Internet:
The culprit was SRTSP.SYS, an antivirus component from Norton. It is solved by removing it.
A blue screen with MEMORY_MANAGEMENT is a sign that the RAM is unusable:
Reinstall Windows
I thought for a long time - whether to advise this. However, a quick run through popular forums showed that many users still use pirated Windows builds. So, if you have:
reinstall Windows clean! And put the normal, original Windows. If you have a laptop, the hard disk will contain a recovery partition with the Windows prepared by the manufacturer - read the instructions and install (restore) it!
Installing Windows is not a matter of five minutes, but even a novice user can handle it if they want to.
Nothing helps? There is an excellent forum thread: Eliminating Critical Windows Errors (read the rules first).
Just make sure you have done your best first: parsed the minidump, updated the faulty driver. If the problem is in the hardware, the only way out is to contact the service center.
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, you must carefully study the content of the blue screen. After all, it is on it that all the information the user needs is indicated, namely: the reason for the error and even recommendations for its elimination.
If the information that is indicated on the screen is not enough, then the computer can be configured specifically to diagnose the blue screen of death.
File corruption win32k sys provokes a blue screen. Therefore, be sure to check and scan other directories.
Windows blue screen or memory dump is a reflection of the working (or not quite) state of the operating system at a certain period of time. Since immediately after the appearance of a critical error, after which an abrupt shutdown of the device may follow, Windows displays all the necessary information on the famous blue screen, then for further diagnostics you just need to remember it: rewrite or photograph.
The main trouble is that the blue screen is shown for a strictly limited time. Then the reboot mechanism starts. Therefore, an unprepared user who does not know where to look may find it difficult to have time to rewrite the necessary information.
To disable auto-restart of the device, that is, when the computer or laptop immediately starts to reboot, immediately after the blue screen of death appears, it is necessary to activate the recording of small memory dumps, that is, part of its important content. This requires the following steps:
Now the blue screen of death when Windows 7 boots up will not immediately disappear, so you will have time to rewrite the necessary information.
Since any problem can cause the blue screen of death, it is necessary to identify it in order to fix the error.
As soon as you managed to take a picture of the blue screen when Windows boots or write down the information that appears on it, you can proceed to decrypting the error that caused it:
Knowing this information, it becomes clear how to remove the blue screen of death.
Problems with a blue screen in 90% of cases are the most commonplace and appear among users who are poorly versed in computers, therefore they often neglect the installation of system updates, drivers, the correct procedure for uninstalling programs, and so on.
Damage to the acpi sys file can cause a blue screen, so to fix the error, you must replace it with a workable one.
Even if the screen says that the error was caused by files like tcpip, ntoskrnl, fltmgr, netio, ntkrnlpa, the first thing to do is:
It will not be superfluous to defragment, check and clean the registry. This is best done using special software. One of these programs is.
With its help, it is also possible to check the presence of all files and libraries necessary for the stable operation of the operating system. If some of them are missing or damaged, the program will offer to download and replace them. If you wish, you can make a copy of the original files and save them in any convenient place on your hard drive.
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 a faulty internal storage device (HDD) or incorrect formatting. Do not neglect the standard procedure for checking the operability of the used OS image, disk or flash drive. All this information can be found on the screen. You fix other problems in the same way.
If you are not sure how to remove the blue screen of death due to missing or corrupt system files or libraries such as TCPIP.SYS, SPCMDCON.SYS, IGDPMD64.SYS, fltmgr, DXGKRNLl.SYS, NTKRNLPA.EXE, NETIO.SYS or error 0x00000116 then this method is for you. It is also suitable for errors caused by other files with extension .SYS, .DLL, .EXE. To do this, you can use a special third-party shareware utility. One of the most popular is.
After installing the program, you need to launch it and start scanning using the Start button. Next, the utility will offer to check 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 was considered: what is the blue screen of death, its causes. An explanation of the errors was given, as well as various options for eliminating the resulting breakdowns were proposed. Now, if you see the Windows 7 death screen again, then you already know what to do.
In case of critical errors in the operation of the operating system, as a result of which the PC is restarted without saving data, and further work with information becomes impossible, a blue background with white letters is displayed on the screen, which is called. The name is a literal translation of the English term Blue Screen of Death (abbreviation - BSoD).
You should not be afraid of the blue screen, since any mechanism may fail sooner or later, but it can be quite difficult to determine its cause. BSoD is a kind of protective reaction of the operating system and appears in case of detection of code that does not work correctly.
PC operation is not possible because the system is shutting down. The user only needs to carefully study the information received and then reboot the system.
Thus, the blue screen provides information about the type of error by encrypting it with a hexadecimal code. The identification of the cause of the failure (decoding of the code) can be found in the search engine.
Some breakdowns in the system are very frequent, others are quite rare. For example, 0x00000001 corresponds to the APC_INDEX_MISMATCH error. Upon entering the code, we find out that the problem occurs as a result of the first installation or reinstallation of a third-party application for MTP and WPD devices. This error can be fixed by downloading and reinstalling the latest update on the OS.
If the user, seeing what is happening on the screen, did not perform any action, Windows will automatically start to reload. In this mode, in the absence of technical knowledge and experience, it is difficult to understand the source of the failure. As a consequence, there is a need to delay the error on the PC screen.
To make it possible to decipher the sources of the failures that have occurred, you can go in several ways:
Writing the contents of the working memory is enabled after disabling the reboot in automatic mode. To do this, the "Properties" tab is activated in the "Computer" menu (by clicking on the right or by a quick combination of "Win + Pause"). In the position "Additional system parameters" located on the left side of the screen, open the "Additional" window.
In the selected tab, we find the item "Download and Restore" with a number of checkboxes. Next, you need to remove the parameter that performs auto-reboot, and check the box in the box that is responsible for registering the event in the system log ("Write event to the system log"). Now, when the blue screen is highlighted, the OS will not automatically reboot, and the necessary information about the dysfunction of the working system will be stored in memory.
The use of a special application is relevant for high-speed 
diagnosing the blue screen of death. For example, the Blue Screen View utility examines individual dumps and lists them.
The program thoroughly analyzes and collects information about the details of emerging critical failures and displays products in decrypted form with an indication of the version, bitness. Events are viewed in separate windows of the received report, which can be saved in text format or in an .html file.
On the blue screen of death, in a certain sequence, there is information in English that specifies the failure and how to fix it. In particular, we are talking about displaying:
Failures occurring as a result of a breakdown of an element of the PC hardware (hard disk, RAM, video card or power supply) are frequent. Conflicts that arise between devices in a computer or due to incompatibility of the connected equipment with the.
Inappropriate or incompatible drivers, lack of free working space on the disk, unsatisfactory operation of coolers leading to overheating, action malware- equally common circumstances leading to the appearance of the screen of death.
The appearance of the blue screen of death of Windows 7 when loading is a serious enough reason to analyze the work of the PC as a whole.
First, you can check how much disk space is left for the system data. If there is no space, you should delete unnecessary information in the usual way or using cleaning utilities.
From time to time it is necessary to scan the OS with antiviruses in order to destroy viruses, trojans and other software that can disrupt the operation of the PC.
If the activation of the blue screen is triggered by error codes in Windows 7, you can install the service pack in the latest version and periodically update the system in the future. For this purpose, in the "System Properties" menu, select the "Automatic update" item, in which the corresponding "Automatic (recommended)" button is activated.
If the error appears when you reload the program or driver, you can fix the error by rolling back the driver to a previous version or uninstalling the program. It is possible to use "Run Last Known Good Configuration".
The activation of the blue screen is associated with the connection to the PC of a new incompatible device. Then one of the components is replaced - either the device (for a compatible one) or the operating system that supports it.
If the device is initially compatible, but the OS still generates an error, new driver versions are installed from the manufacturer's website.
If you have the appropriate knowledge, you can configure the settings in the BIOS. A layman is better off not using this technique, as it can result in an even bigger problem than a blue screen.
The death screen may be the result of a malfunction in the RAM. A broken line is identified using one of the testing programs. So, the MemTest86 utility allows you to test memory without an OS or connecting other drivers. To connect it, a bootable USB flash drive (disk) is created. The program writes all the memory in blocks of data, and then reads and verifies what was written.
BSoD can be caused by bad sectors or errors on the hard disk. The problem is solved through standard operations: in the "Tools" menu, the volume is checked.
It will be useful to monitor the cleanliness of the PC, which will eliminate the problem of overheating, provoking the flashing of the blue screen of death. It is necessary to lubricate the cooling components of the processor, chipset, power supply with a special agent. If necessary, additional coolers are installed to normalize the passage of air flows.
To fix BSoD, you can reinstall operating system using its licensed version.
If there is a problem in the form of a blue screen, you can do without decoding the error code. To begin with, we analyze our recent actions with the computer. If their list includes a driver update, program installation, registry change, hardware replacement, access to a site with a dubious reputation, you can do it differently.
First, the OS is loaded using the Last Known Good Configuration mode. To do this, all discs are removed and the computer rebooted. During reboot, the F8 key is held down, which causes the Windows symbol to appear. Then the PC should be rebooted and, having received the message "Additional boot options" on the screen, select the "Last Known Good Configuration" item. 
If this attempt was unsuccessful and did not lead to the elimination of errors, the computer is booted in "Safe Mode" (alternatively - "... with loading network drivers").
After that, you can check the disk, the integrity of its system components and the presence of viruses.
So, the blue screen helps to identify failures that occur during the execution of code in the operating mode of the kernel. To do this, it is enough to monitor the cleanliness of the PC, use drivers and proven programs downloaded from the official resources of reliable manufacturers. Observing simple rules, you can reduce the possibility of interrupting the system operation by several times.
If BSoD began to periodically disrupt the usual rhythm of PC operation, you can easily decipher the error code, and then eliminate its cause.
