Permanent blue screen windows 7. "Blue screen of death" error codes

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

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

"Blue Lantern" turns on unexpectedly

Blue screens of death occur at any stage of loading and operating a computer. And it leads to the following:

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

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

What can be learned from the information on the blue screen

Hardware bruises often occur under the same conditions (for example, when the load on the video card is increased, when trying to open a large file) and have different codes. Or these codes indicate problems with specific equipment, such as: device access errors, inability to read, recognition.

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

Windows 10 blue screen of death looks like this:

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

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

• On computer forums.
• In reference books on various error codes, in particular, and in .

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

How to enable the small memory dump creation and saving feature

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

• Login through context menu in the folder properties Computer».

• Click on the " Additional system settings».

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

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

How to analyze the contents of minidumps

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

The interface of the utility, despite the lack of the Russian language, is very friendly. The main window is divided into 2 halves. Above - a table of minidumps - files from the Windows\Minidump folder with the date and time of creation (column crash time), error code in hexadecimal format (column Bug Check Code), its four parameters, and other information. However, it is more convenient to view data on a specific failure in a separate window, which is opened by double-clicking on the line of interest (shown below). The main window gives more information about the problem in general if BSoDs have happened repeatedly. It is easy to track the dates of incidents and error codes, the frequency of which can be used to judge the nature of the problem.

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

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

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

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

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

Let's consider another case of the blue screen of death caused by Kaspersky antivirus. BSoD intermittently occurred during the startup of Windows 10 and when the computer resumed from sleep mode.

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

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

After removing Kaspersky, the blue screens no longer popped up.

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

The function to select a folder with dump files is located in the menu " Options» – « advanced options” (opened with the keyboard shortcut Ctrl + O) and is called “ Load from the following minidump folder».

"In a nutshell", blue screen appears at the moment of occurrence of a stop error (error of the operating system kernel) in which the system can no longer continue its work. The problem is typical for any failures - from software incompatibility to exceeding the temperature of the processor. In order to more or less accurately determine the cause of the failure, analysis is needed based on the text and code of the error itself. Desktop or laptop - it doesn't matter, the approach to solving problems is the same.

Disabling automatic reboot

Analysis of the problem by code

After receiving the code, we will be able to find information describing the cause of the problem and ways to solve it.

Get the code in Windows 8 and later

More modern codes have less description and technical information, and the code itself is represented by a sad emoticon and a text description, for example, CLOCK_WATCHDOG_TIMEOUT:

also, in addition to the error (sometimes, and without inscriptions and text), a QR code may be present:

Codes in Windows 7 and older

When a blue screen appears, you need to find the error code. It has the form 0x0000..., for example 0x0000008D:

* codes in parentheses are additional parameters and serve to clarify the localization of the error. They can be individual and, as a rule, are not taken into account in further analysis.

Online analysis

Now we open sites with error codes, for example:

You can also enter the error code directly into search string Google or Yandex. And if you have a QR code, you can consider it a reader and go to the description of the problem.

When solving a problem, you must carefully read about the causes of the failure and follow the recommendations.

Dump Analysis

In the case when automatic reboot is enabled or we analyze the problem later, you can use the dump − special file, which contains information about the last state of the system before the error with all the necessary descriptions and codes.

Default, given file located along the path %SystemRoot%\MEMORY.DMP (usually C:\Windows\MEMORY.DMP). You can view or change the path in the same place where automatic restart is disabled - right click mice by This computer - Properties - Additional system settings -

You can read the dump special utility, for example, BlueScreenView. You can download it on the official website.

After running the utility, we should see (if there were problems) a list of stop errors with codes, reports and additional information:

Having received the error code, we analyze using search engines or specialized sites using the .

TOP error codes

• 0x00000109. General error caused by incorrect work RAM or disk storage. Sometimes, because of the virus.
• 0x00000050. A problem with the device driver or incorrect operation of the hardware.
• 0x0000007B. You need to check the media and boot order of the system in the BIOS.
• 0x0000007e. Generic code that combines a large number of different problems. Read the article below about common problems and how to solve them.
• 0x00000012. The system failed to understand the cause of the failure. Also use the text below to solve.

Typical causes that lead to the appearance of an error and methods for their elimination

Consider the TOP problems that cause an operating system kernel error, as well as methods for solving them:

1. There is a problem with the device driver. If the error appears after installing a new driver or updating it, you need to roll back the driver to the previous version.
2. Unsuccessful update Windows. It usually happens when installing a large number of updates or installing a low-quality patch. Solved by rolling back installed packages.
3. Incorrect operation of the equipment. To find out, you need to conduct a stress test with the AIDA64 program or analogues. It is also necessary to test the RAM and the operation of the disk media.
4. Reset BIOS settings. When changing the operating mode of the drive (AHCI, IDE, RAID), the system will stop booting, giving a stop error. The parameter may be lost due to a dead BIOS battery or manual reset settings.
5. Viruses. Many problems can be attributed to them. But it's worth checking the computer, for example, with the CureIt program.
6. Incompatible software. If installing or updating any software causes a problem, reinstall software or install a previous version.
7. Violation of the license agreement. In some cases, a blue screen may appear every hour or two. As a rule, this is due to the fact that an unactivated Windows is used.
8. The problem is in the video card or its overheating. As a rule, it is observed in games or when watching videos. For diagnostics, you need to update the driver and conduct a stress test. You should also pay attention to the temperature of the video card.

If the system does not boot

In some cases, BSOD appears when Windows boot. This greatly complicates the diagnosis. In the case when the system cannot be booted, and the blue screen appears for a moment, or does not appear at all, it is necessary to disable automatic reboot at power on.

Another option is to use boot Windows LiveCD, which contains a large number of utilities for diagnosing the problem.

How to find out the cause of the appearance blue screen of death (BSOD), as well as options for eliminating BSOD from a computer

Blue Screen of Death (BSOD) Windows. Theory.

Blue screen of death(Blue Screen of Death, Blue Screen of Doom, BSoD) is a message about a critical system error Windows, as a result of which the operating system cannot continue to work and goes into a forced restart without saving data.

Preparing for the Blue Screen of Death (BSOD)

It can be caused due to a malfunction of any hardware or software failure (drivers most often) Death screen errors are displayed on a screen with a blue background, on which the REASON for it is written. Therefore, the most important task will be to extract from this message the lines after the second or third paragraph, written in CAPITAL LETTERS with an underscore PAGE_FAULT_IN_NONPAGED_AREA) and the lines after Technical information: that start with *** For example:
*** STOP: 0x00000050 (0x8872A990, 0x00000001, 0x804F35D7, 0x00000000)
*** SPCMDCON.sys - Address FBFE7617 base at FBFE5000, Date Stamp 3d6dd67c)
Lines to remember in the blue screen of death:

An equally important task is to save a dump file that contains an error report. blue screen of death (BSOD). By default, it is enabled in both Windows Xp and Windows Seven (7), but if you have it disabled then:
If the operating Windows system 7: Right-click on "My Computer" -> Properties -> Advanced system settings -> "Advanced" tab -> After the lines "Start and restore" click on "Settings" -> check the box "Write an event to the system log" and uncheck the "Perform automatic restart" checkbox. We do as in the picture

If the operating system is Windows Xp: Right-click on "My Computer" -> Properties -> "Advanced" tab -> After the lines "Start and restore" click on "Settings" -> check the box "Log event to the system log" and Uncheck the "Perform automatic restart" checkbox.

At the next blue screen of death (BSOD) the computer, firstly, will not automatically go into reboot, and secondly, it will save a dump file in which information about the blue screen of death (BSOD) will be stored

We determine the cause of the occurrence from the blue screen of death (BSOD)

After the steps taken, turn on the computer and try to boot Windows.
If at boot it immediately knocks out the blue screen of death, then at the next reboot we boot in safe mode, just choose not safe mode, but "Disable automatic restart on system failure"


Let's write down the lines that we need on a piece of paper.

In this case, as you can see, the SPCMDCON.sys system file is to blame. Therefore, the first step is to remove it or, on the contrary, restore it. To do this, boot from a bootable Live Cd or bootable live usb and delete it manually (or restore). Search through Live boot disk on the disk with Windows SPCMDCON.sys and rename it, for example, to SPCMDCON(2).sys. We restart the computer. If it helped and everything is OK, I congratulate you, if not, we continue to fight the blue screen of death (BSOD) in the same way until we defeat it.
If the blue screen of death (BSOD) does not immediately knock out and Windows is loaded, then check the Dump file. To do this, download BlueScreenView
Run BlueScreenView.exe. Those drivers that caused the blue screen are highlighted in red.


They must be removed manually and then installed newer ones (often causes a blue screen of death of the video card driver)

Blue screen of death (BSOD) during games or after a different period of time (reinstalling Windows does not help)

If such a situation that everything has already been experienced and reinstalling Windows and other methods, but the blue screen does not go away, then the problem is in the computer hardware. Here you will be helped by tests of the processor, RAM. This may be the reason for buying a new video card without replacing a power supply that is not designed for such a load, or a faulty RAM bar. To make things easier, here is a list of the most common Blue Screen of Death (BSOD) errors.

Most common Blue Screen of Death (BSOD) errors - taken from the Microsoft website

1. KMODE_EXCEPTION_NOT_HANDLED- A kernel-mode process attempted to execute an invalid or unknown processor instruction. May be due to hardware incompatibility, hardware failure, driver or system service errors.
2. NTFS_FILE_SYSTEM- Crash while executing ntfs.sys file system driver code. The reason may be a violation of the integrity of the data on the disk (bad cluster) or in memory, damage to the IDE or SCSI drivers.
3. DATA_BUS_ERROR- A parity error has been detected in the RAM. The reason is defective or incompatible hardware, for example, a failure in the second-level cache chip, in the video memory. It can also be related to a malfunctioning or misconfigured driver, or a disk failure.
4. IRQL_NOT_LESS_OR_EQUAL- A kernel-mode process attempted to access a region of memory using an unacceptably high IRQL (Interrupt Request Level) for it. May be caused by errors in a driver, system service, BIOS, or an incompatible driver, service, software (such as antivirus).
5. PAGE_FAULT_IN_NONPAGED_AREA- the requested data is not in memory (for example, the system looks for the necessary data in the paging file, but does not find it). Usually associated with a hardware failure (defective memory), file system corruption, system service or antivirus error.
6. KERNEL_STACK_INPAGE_ERROR- Unable to read the requested memory page from the paging file into physical memory. Causes - defective sector of the file virtual memory, controller failure hard drives, insufficient disk space, incorrect hard disk connection, interrupt conflict, defective RAM, virus.
7. MISMATCHED_HAL- the hardware abstraction level (HAL) and the system kernel do not match the type of computer. Most often associated with a situation where a second processor is installed in the original system, forgetting to manually update the HAL and ntoskrnl. May also be caused by version mismatch between hal.dll and ntoskrnl.exe.
8. KERNEL_DATA_INPAGE_ERROR- Unable to read the requested data page into physical memory. Causes - defective sector of the virtual memory file, hard disk controller failure, RAM failure, virus, disk controller failure, defective RAM.
9. INACCESSIBLE_BOOT_DEVICE- during the boot process, the OS could not access the system partition. There can be many reasons for this common failure: a defective boot disk or disk controller; equipment incompatibility; boot virus; an error in the file system, for example - in the Partition Table; damage or absence of a file necessary for loading, for example - NTLDR; lack of hard disk controller driver or inconsistency of the current driver installed equipment; included in BIOS mode DMA; DRIVE SWAPPING mode enabled in CMOS Setup; resource allocation conflict between the disk controller and another device; corruption of data about loaded drivers in system registry; installation of the system in a partition outside the first 1024 cylinders of the hard disk; error in boot.ini file.
10. UNEXPECTED_KERNEL_MODE_TRAP- the occurrence of a trap not supported by the kernel (trap) or a fatal error (such as division by zero). Hardware failure or software failure.
11. STATUS_SYSTEM_PROCESS_TERMINATED- Crash in a service running in user mode. Failure may be due to incorrect operation application programs, drivers, third-party system services.
12. STATUS_IMAGE_CHECKSUM_MISMATCH- damaged or lost driver or system library file. May be caused by a file system crash or accidental deletion of a system file.

If there are any questions, ask them in the comments. We will be happy to help!

The blue screen of death is familiar to every user of operating systems of the Windows family. For some users, it appears so often that they begin to think that this is a normal phenomenon. But it's not. Let's understand what the blue screen of death is. This is an error that appears when booting up or after a sudden shutdown of the computer. It indicates the presence of problems with the operating system or internal hardware. Only by understanding the causes of occurrence, you can eliminate it as effectively as possible.

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

Blue screen of death, its causes

The causes of the blue screen can be divided into two main groups:

• Systemic. Operating system issues: no desired files necessary for the correct operation of Windows, an incorrectly installed OS, malware or file infection, and so on.
• Hardware. Problems with computer hardware: hard drive or video card failure, processor overheating, and so on.

In order to accurately determine the cause of the error, you must carefully examine the contents of the blue screen. After all, it is on it that all required by the user information, namely: the cause of 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 causes a blue screen. Therefore, it is definitely worth checking and scanning other directories.

Diagnostics

The 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 a sharp 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 it or take a picture.

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

To disable the auto-reboot of the device, that is, when the computer or laptop immediately starts to reboot, immediately after the blue screen of death appears, you need to activate the recording of small memory dumps, that is, part of its important content. To do this, you need to do the following:

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

Error decoding

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

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

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

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

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

Corrupt acpi sys file can cause a blue screen, so in order to fix the error, you need to replace it with a working 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. It is best to do this with the help of special software. One of these programs is .

With its help, it is also possible to check the availability of all the 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 desired, you can make a copy of the original files and save it in any convenient place on your hard drive.

Screen of death when loading or installing Windows

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 only occur in three cases if:

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

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

Blue screen during installation or Windows recovery may occur due to a faulty internal storage(HDD) or formatted incorrectly. should not be neglected and standard procedure checking the health of the used OS image, disk or flash drive. All this information can be found on the screen. Correct other problems in the same way.

Missing or corrupted system files

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 distributed shareware utility. One of the most popular is .

After installing the program, you need to run 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. If you are sure that it was the nvlddmkm sys file that caused the blue screen of Windows 7 or any other whose name you must know for sure, then you can check it.

Once the scan is completed, it will prompt:

• replace the file if it was really damaged;
• proceed to check other system files if specified file not damaged;
• only delete the faulty file if you want to replace it yourself;
• do nothing, but at the same time open the folder with the damaged file for independent solution Problems.

Optionally, you can install other applications for automatic search damaged system files and their replacement. Some of them similarly identify and fix driver-related problems.

Reset BIOS

If recently produced BIOS changes or tried to overclock the processor, then it is possible that the problem is caused by this. Therefore, you should definitely try to return its default settings. You can do this in several ways:

Conclusion

And this article was considered: what is the blue screen of death, its causes. A decoding of the errors was given, as well as suggestions various options elimination of breakdowns. Now, if you get the Windows 7 death screen again, then you already know what to do.

Related videos

Many of you have probably already heard from friends and acquaintances more than once about such a concept as Windows 7 blue screen of death, which appeared on their computer, it is also called BSOD ( Blue Screen of Death).

With the appearance of a blue screen, Windows warns us that, and it is advisable to eliminate them in a timely manner. The death screen shows error codes that can be used to understand why it is happening, and from this to conclude which component of the computer is failing or a software problem.

If your computer with Windows 7 started to issue a BSOD, then you and I need to understand why it appears, and for this you need to write the error code in your notebook or take a picture of the monitor screen, and then, having filled in the error data, in the search bar or, we are looking for what it means or we read the article in full, in it you will find the codes of the most common errors due to which the blue screen of death appears. But first, we will carry out preparatory work with you.

In order for us to have time to write down or photograph the blue screen error code, we need to do some system settings.

It is necessary to turn off the restart of the PC when an error occurs, as well as enable the recording of debugging information in a memory dump.

• Memory dump- the contents of RAM at a certain point in time, let's say a special image.
• Small memory dump - portion of memory that is written to HDD during failures, only the most important information remains there.

In order to go to the system settings, open "Start", select "Computer", right-click on it and select "Properties"

A new window will open, in which we select the "Advanced" tab and click the "Options" button in the "Download and Recovery" item

Next, we look at the section "Write debugging information" there you need to select "Small memory dump 256 KB"

Now your computer is set up, the next time it crashes, it will not restart, and you can safely write down the error code or take a picture of it.

Blue Screen of Death, Windows 7 error codes

Let's now look at the most common error codes.

• KMODE EXCEPTION NOT HANDLED - the computer gives such an error if there is a problem with the hardware (for example, any component of the computer has failed) or a problem with the drivers.
• NTFS FILE SYSTEM - problems with file system hard drive, this problem may occur in several cases:

* the presence of viruses in the boot area of ​​the hard drive

* damage to the structure of the file system.

• INACCESSIBLE BOOT DEVICE - when this error occurs, the Windows operating system says that it could not access boot partition disk. There can be many problems causing this error. For example, a problem in the PC hardware: the hard drive is damaged, the controller is faulty, individual computer components are faulty, or a software problem: viruses or file system errors.
• IRQL NOT LESS OR EQUAL - this error may appear when there is a problem with drivers or some Windows system service

• PAGE FAULT IN NONPAGED AREA - a blue screen of death with this code means that the data that the system is looking for is not in memory, respectively, when the operating system accesses, for example, data in the paging file, but there is nothing there, such an error will appear. The error often appears due to problems with RAM, system errors Windows Services or because of a corrupted file system.

• KERNEL DATA INPAGE ERROR - operating system Unable to read data from memory. This error can be caused by failing RAM, hard drive problems due to unreadable sectors, or problems with the HDD controller.
• KERNEL STACK INPAGE ERROR - The OS was unable to read the paging file and write data to the hard drive. The main reasons for this error: a problem with RAM or hard drive.
• UNEXPECTED KERNEL MODE TRAP is an error that appears at the kernel level of the system. The reasons that caused it can be both hardware and software.
• STATUS SYSTEM PROCESS TERMINATED - an error caused by software failure, problems with system services, drivers or applications
• DATA BUS ERROR - a blue screen appears when there is a RAM failure or a video adapter failure.

Windows 7 blue screen of death, what to do?

After we have determined what kind of error we have, we need to establish the reason for which our computer began to crash. For this, it is necessary to remember which last changes happened on your computer. You may have installed new program or updated drivers for some device. To eliminate the human factor, you need to remove the last installed programs, as well as roll back the drivers to previous versions. If errors began to appear after installing new hardware in system unit, then you need to turn it off and observe the operation of the computer.

In order to resolve the error caused by a software failure, you need to try the following steps.

• Roll back installed new drivers to the previous version;
• Run Windows startup with last known good configuration;
• Perform a system restore using standard function Windows.

I advise you to check the amount of remaining free space on the system section of the hard disk, as a small amount of memory can cause system malfunctions. Do not forget to check your computer for viruses, for this you can use the free Dr.Web Cureit utility or the KVRT utility from Kaspersky Lab. If the blue screen of death continues to appear, I recommend installing the latest package Windows updates 7.

reset BIOS settings by default, incorrect overclocking of computer components may have been performed, due to which the hardware runs on wrong settings that differ from the factory ones, thereby giving malfunctions during operation. To reset the settings, you need to go into the BIOS, press the F5 key and to save the settings, F10. The computer should restart and apply the new settings.