Sunday, July 21, 2013

The Anatomy of Blue Screen Error Codes - Technology

The Blue Screen, also known as BSOD or Blue Screen of Death, is known officially as a stop error or a bug check. This error screen is displayed by the Microsoft Windows family of operating systems upon encountering a critical error.

The error is non recoverable in nature and it causes the system to crash. The term is named after the color of the screen generated by the error. These errors are usually hardware or driver related. It causes the computer to stop responding in order to prevent damage to the hardware. In the latest version of Windows, the screen presents the information for diagnostic purposes that were collected as the operating system performed a bug check.

Some blue screen errors are caused by software errors in drivers. They can also be caused by physical hardware faults, such as faulty RAM memory or power supplies, overheating of components, or hardware which is run beyond its specification limits or what we call "overclocking".

There are four basic sections that comprise the blue screen of death. These are the following:

1. Actual Error Message - this contains an error code number, the addresses where the error occurred and a text code indicating the type of error. 2. List of Microsoft modules that are already loaded into memory - this lists the modules that are already loaded into memory and none of these modules are causing the problem. 3. List of Modules that were about to be loaded had the error not occurred - this section gives you an idea of which module is causing your problem. 4. List of the current status of the Kernel Debugger - this section indicates the current status of the kernel debugger.

List of Blue Screen Error Messages

a. IRQL_NOT_LESS_OR_EQUAL - this stop message indicates that a kernel-mode process or driver attempted to access a memory location to which it did not have permission, or at a kernel interrupt request level that was too high. This stop message is typically due to faulty or incompatible hardware or software.

b. KMODE_EXCEPTION_NOT_HANDLED - this stop message indicates that Windows has detected an illegal or unknown processor instruction. This can be due to invalid memory and access violations or an incorrectly configured device driver.

c. NTFS_FILE_SYSTEM - this stop error indicates hard disk corruption.

d. DATA_BUS_ERROR - this indicates a system memory parity error which is typically cased by failed or defective RAM, incompatible or mismatched memory hardware. This can also indicate a hard disk damage caused by viruses or other problems.

e. NO_MORE_SYSTEM_PTES - this indicates that the system Page Table Entries (PTEs) are depleted or fragmented due to the system performing a large number of input/output actions. Also, it can be caused by a faulty device driver that is not managing memory properly or an application, such as a back- up program, is improperly allocating large amounts of kernel memory.

f. PAGE_FAULT_IN_NONPAGED_AREA - this indicates that the requested data was not in memory.

g. KERNEL_STACK_INPAGE_ERROR - this indicates that a page of kernel data requested from the paging file could not be found or read into memory. This can also indicate disk hardware failure, disk data corruption or possible virus infection.

h. MISMATCHED_HAL - this indicates that the hardware abstraction layer (HAL) and the kernel type for the computer do not match. This often occurs when ACPI firmware settings are changed.

i. KERNEL_DATA_INPAGE_ERROR - indicates that a page of kernel data was not found in the paging (virtual memory) file and could not be read into memory. This might be due to incompatible disk or controller drivers, firmware or hardware.

j. INACCESSIBLE_BOOT_DEVICE - this indicates that Windows has lost access to the system partition or boot volume during the startup process.

k. UNEXPECTED_KERNEL_MODE_TRAP - this is typically due to defective, malfunctioning, or failed memory hardware.

l. DRIVER_POWER_STATE_FAILURE - this can occur after installing faulty application or drivers or system devices.

m. ATTEMPTED_WRITE_TO_READONLY_MEMORY - this indicates that a driver attempted to write to read-only memory.

n. BAD_POOL_CALLER - this indicates that a kernel-mode process or driver incorrectly attempted to perform memory operations.

o. DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS - this indicates that a driver failed to cancel pending operations before exiting.

p. DRIVER_IRQL_NOT_LESS_OR_EQUAL - this indicates that the system attempted to access pageable memory using a kernel process IRQL that was too high.

q. THREAD_STUCK_IN_DEVICE_DRIVER - this indicates that the device driver problem is causing the system to pause indefinitely.

r. UNMOUNTABLE_BOOT_VOLUME - this indicates that the kernel mode input/output subsystem attempted to mound the boot volume and it failed.

s. STATUS_IMAGE_CHECKSUM_MISMATCH - this indicates driver, system file or disk corruption problems.

The Blue Screen Error codes can be resolved by following certain troubleshooting steps.





No comments:

Post a Comment