In this tutorial will discuss the infamous Blue Screen Of Death (BSOD) error codes and basic strategies for dealing with blue screen error codes, and will let you know what some of the most common codes mean.
Blue Screen Error
A stop error, alternatively known as the blue screen of death, blue screen, or BSOD, is an error screen displayed on a Windows computer system following a fatal system error. It indicates an error from which the system cannot recover, and which will not allow Windows to load. Physically, it consists of white text on a blue background; the text tells you that there’s been an unrecoverable error, and gives you the name and/or code that identifies the error.
You might see a blue screen with a message that your device ran into a problem and needs to restart.
The Error Codes
When You see a blue screen error, in Windows NT through XP, Vista, and Windows 7 it included the name of the error, along with a hexadecimal code representing the error (followed long hexadecimal numbers representing parameters which may be relevant to the error), along with some general information about the error, and possibly some specific information about drivers or other components of system which may be affected by the error.
As per Microsoft document the error codes known as common bug check codes, that are displayed on the blue bug check screen. Microsoft has a full list of bug codes here, and here will discuss few known and mostly seen blue screen error codes.
If you receive an error IRQL_NOT_LESS_OR_EQUAL(code 0x0000000A) . This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at an invalid address while at a raised interrupt request level (IRQL). This is typically the result of either a bad pointer or a pageability problem. if you installed a device or BIOS driver (or a system service) not too long before this error occurred, your first step should be to uninstall it, or roll back to a previous good version.
DRIVER_IRQL_NOT_LESS_OR_EQUAL ( erro code 0x000000D1). This is very similar to the previous error; it basically says that it’s a driver that’s trying to address the wrong area of memory. The solution is to uninstall the offending driver. If you’re a developer, and it’s the driver that you’re working on that’s at fault, check to be sure that it (or anything it’s calling) can’t be paged.
Exception Not Handled (KMODE_EXCEPTION_NOT_HANDLED)
The error KMODE_EXCEPTION_NOT_HANDLED (code 0x0000001E) this indicates that a kernel-mode program generated an exception that the error handler did not catch. This error may occur due to faulty device driver or system service might be responsible for this error. Hardware issues, such as BIOS incompatibilities, memory conflicts, and IRQ conflicts can also generate this error.
Below are some error codes involved in memory related issues.
DATA_BUS_ERROR (error code 0x0000002E). This is typically (but not always) the result of a hardware problem, and very often, the problem is defective memory; in most cases, you can start by swapping out (or removing) RAM to see if the problem goes away. It can also be caused by hard drive errors, cache errors, or in some situations, driver problems.
PAGE_FAULT_IN_NONPAGED_AREA (error code 0x00000050). This generally means that a system service or driver tried to access invalid memory; it is frequently a hardware error, although it can also be a driver error; you can usually handle it much like the preceding error.
NTFS_FILE_SYSTEM (error code 0x00000024).Disk or file system errors can show up in a variety of ways (including as memory errors, due to paging). The following error indicates a problem has occurred in ntfs.sys, the driver file that allows the system to read and write to NTFS drives.
One possible cause of this bug check is disk corruption. Corruption in the NTFS file system or bad blocks (sectors) on the hard disk can indicate this error. Corrupted hard drive drivers can also adversely affect the system’s ability to read and write to disk, thus this error causes.
Few of the troubleshooting steps:
- Remove unsupported or possibly malfunctioning hardware.
- Try disabling any virus scanners, backup programs, or disk defragmenter tools that continually monitor the system.(if you get NTFS_FILE_SYSTEM error)
- You should also run hardware diagnostics supplied by the system manufacturer related to the storage sub system.
- If hardware has recently been added to the system, remove it to see if the error recurs.(Memory error)
- Remove external hardware.
- Uninstall an incompatible piece of software, such as an old program or third-party antivirus, is likely the root of the problem.
- Uninstall third-party software. Some third-party antivirus software has been known to cause blue screen errors.
These are only a few of the most common errors we discussed, i don’t have the space to cover all of them as there are lot of error codes, or to go into detail about the best ways to respond to BSOD errors. and follow Microsoft document.