Function of Kernel

The kernel is the essential center of a computer operating system, the core that provides basic services for all other parts of the operating system. A synonym is nucleus. A kernel can be contrasted with a shell, the outermost part of an operating system that interacts with user commands. Kernel and shell are terms used more frequently in Unix operating systems than in IBM mainframe or Microsoft Windows systems.

In computer science, the kernel is the central component of most computer operating system(OS). Its responsibilities include managing the system's resources (the communication between hardware and software components). As a basic component of an operating system, a kernel provides the lowest-level abstraction layer for the resources (especially memory, processors and I/O devices) that application software must control to perform its function. It typically makes these facilities available to application programs through interprocess communication mechanisms and system calls.
These tasks are done differently by different kernels, depending on their design and implementation. While monolithic kernels will try to achieve these goals by executing all the code in the same address space to increase the performance of the system, microkernels run most of their services in user space, aiming to improve maintainability and modularity of the codebase. A range of possibilities exists between these two extremes.

Stop Error Screen (BSoD)

A stop error screen or bug check screen, commonly called a blue screen of death (also known as a BSoD, bluescreen, or "blue screen of doom"), is caused by a fatal system error and is the error screen displayed by the Microsoft Windows family of operating systems upon encountering a critical error, of a non-recoverable nature, that causes the system to "crash." The common expression blue screen of death comes from the color of the screen generated by the error.

 
0x0000000A IRQL_NOT_LESS_OR_EQUAL 0xA

The Stop 0xA 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 (IRQL) that was too high. A kernel-mode process can access only other processes that have an IRQL lower than, or equal to, its own. This Stop message is typically due to faulty or incompatible hardware or software.


0x0000001E KMODE_EXCEPTION_NOT_HANDLED 0x1E

The Stop 0x1E message indicates that the Windows XP kernel detected an illegal or unknown processor instruction. The problems that cause Stop 0x1E messages share similarities with those that generate Stop 0xA errors in that they can be due to invalid memory and access violations. This default Windows XP error handler typically intercepts these problems if error-handling routines are not present in the code itself.


0x00000023 FAT_FILE_SYSTEM & 0x00000024
NTFS_FILE_SYSTEM

The Stop 0x24 message indicates that a problem occurred within Ntfs.sys, the driver file that allows the system to read and write to NTFS file system drives. A similar Stop message, 0x23, exists for the file allocation table (FAT16 or FAT32) file systems.


0x0000002E DATA_BUS_ERROR 0x2E

The Stop 0x2E message indicates a system memory parity error. The cause is typically failed or defective RAM (including motherboard, Level 2 cache, or video memory), incompatible or mismatched memory hardware, or when a device driver attempts to access an address in the 0x8xxxxxxx range that does not exist (does not map to a physical address). A Stop 0x2E message can also indicate hard disk damage caused by viruses or other problems.


0x0000003F NO_MORE_SYSTEM_PTES 0x3F

The Stop 0x3F message indicates one or more of the following problems:
The system Page Table Entries (PTEs) are depleted or fragmented due to the system performing a large number of input/output (I/O) actions.
A faulty device driver is not managing memory properly.
An application, such as a backup program, is improperly allocating large amounts of kernel memory.


0x00000044 MULTIPLE_IRP_COMPLETE_REQUESTS

0x00000050 PAGE_FAULT_IN_NONPAGED_AREA 0x50

The Stop 0x50 message indicates that requested data was not in memory. The system generates an exception error when using a reference to an invalid system memory address. Defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software (including remote control and antivirus software) might cause Stop 0x50 messages.


0x00000051- 0x51

0x0000006B PROCESS1_INITIALIZATION_FAILED

0x00000073 CONFIG_LIST_FAILED 0x73

0x00000074 BAD_SYSTEM_CONFIG_INFO 0x74

0x00000076 PROCESS_HAS_LOCKED_PAGES

0x00000077 KERNEL_STACK_INPAGE_ERROR 0x77

The Stop 0x77 message indicates that a page of kernel data requested from the paging (virtual memory) file could not be found or read into memory. This Stop message can also indicate disk hardware failure, disk data corruption, or possible virus infection.


0x00000079 MISMATCHED_HAL 0x79

The Stop 0x79 message indicates that the hardware abstraction layer (HAL) and the kernel type for the computer do not match. This error most often occurs when ACPI firmware settings are changed. For example, you might install Windows XP on an x86-based computer with the firmware ACPI enable option enabled and later decide to disable it. This error can also result when mismatched single and multi-processor configuration files are copied to the system.


0x0000007A KERNEL_DATA_INPAGE_ERROR 0x7A

The Stop 0x7A message 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.
Frequently, the cause of this error can be determined from the second parameter, the I/O status code. Some common status codes are:
0xC000009A, or STATUS_INSUFFICIENT_RESOURCES, indicates a lack of nonpaged pool resources.
0xC000009C, or STATUS_DEVICE_DATA_ERROR, indicates bad blocks (sectors) on the hard disk.
0xC000009D, or STATUS_DEVICE_NOT_CONNECTED, indicates defective or loose data or power cables, a problem with SCSI termination, or improper controller or disk configuration.
0xC000016A, or STATUS_DISK_OPERATION_FAILED, indicates bad blocks (sectors) on the hard disk.
0xC0000185, or STATUS_IO_DEVICE_ERROR, indicates improper termination, defective storage controller hardware, or defective disk cabling, or two devices attempting to use the same resources.


0x0000007B INACCESSIBLE_BOOT_DEVICE 0x7B

The Stop 0x7B message indicates that Windows XP has lost access to the system partition or boot volume during the startup process. Installing incorrect device drivers when installing or upgrading storage adapter hardware typically causes stop 0x7B errors. Stop 0x7B errors could also indicate possible virus infection.
The second parameter is very important because it can indicate whether the 0x7B Stop message was caused by file system issues or problems with storage hardware and drivers. Values of 0xC000034 or 0xC000000E typically indicate:
Disks or storage controllers that are failing, defective, or improperly configured.
Storage-related drivers or programs (tape management software, for example) that are not fully compatible with Windows XP Professional.


0x0000007E SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x7E

0x0000007F UNEXPECTED_KERNEL_MODE_TRAP 0x7F

The Stop 0x7F message indicates that one of three types of problems occurred in kernel-mode:
A condition that the kernel is not allowed to have or intercept (also known as a bound trap).
Software problems.
Hardware failures.


0x0000008E KERNEL_MODE_EXCEPTION_NOT_HANDLED 0x8E

0x0000009C MACHINE_CHECK_EXCEPTION 0x9C

0x0000009F DRIVER_POWER_STATE_FAILURE 0x9F

The Stop 0x9F message indicates that a driver is in an inconsistent or invalid power state.


0x000000A5 - 0xA5

0x000000BE ATTEMPTED_WRITE_TO_READONLY_MEMORY 0xBE

The Stop 0xBE message indicates that a driver attempted to write to read-only memory.


0x000000C2 BAD_POOL_CALLER 0xC2

The Stop 0xC2 message indicates that a kernel-mode process or driver incorrectly attempted to perform memory operations in the following ways:
By allocating a memory pool size of zero bytes.
By allocating a memory pool that does not exist.
By attempting to free a memory pool that is already free.
By allocating or freeing a memory pool at an IRQL that was too high.
This Stop message is typically due to a faulty driver or software.


0x000000C4 DRIVER_VERIFIER_DETECTED_VIOLATION

0x000000CA PNP_DETECTED_FATAL_ERROR

0x000000CB

0x000000CE DRIVER_UNLOADED_WITHOUT_CANCELLING... 0xCE

This Stop messages indicates that a driver failed to cancel pending operations before exiting.


0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL 0xD1

The Stop 0xD1 messages indicates that the system attempted to access pageable memory using a kernel process IRQL that was too high. Drivers that have used improper addresses typically cause this error.


0x000000D5 RIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL

0x000000D8 DRIVER_USED_EXCESSIVE_PTES 0xD8

0x000000E3 - 0xE3

0x000000EA THREAD_STUCK_IN_DEVICE_DRIVER 0xEA

A device driver problem is causing the system to pause indefinitely. Typically, this problem is caused by a display driver waiting for the video hardware to enter an idle state. This might indicate a hardware problem with the video adapter or a faulty video driver.


0x000000ED UNMOUNTABLE_BOOT_VOLUME 0xED

The kernel mode I/O subsystem attempted to mount the boot volume and it failed. This error might also occur during an upgrade to Windows XP Professional on systems that use higher throughput ATA disks or controllers with incorrect cabling. In some cases, your system might appear to work normally after you restart.


0x000000F2 HARDWARE_INTERRUPT_STORM 0xF2

0x000000F4 - 0xF4

0x000000FE BUGCODE_USB_DRIVER - 0xFE

0x4000008A

0xC000021A STATUS_SYSTEM_PROCESS_TERMINATED 0x21A

0xC0000218 UNKNOWN_HARD_ERROR 0x218 & C0000135

0xC0000221 STATUS_IMAGE_CHECKSUM_MISMATCH 0x221

This Stop message indicates driver, system file, or disk corruption problems (such as a damaged paging file). Faulty memory hardware can also cause this Stop message to appear.


0xC0000244 STATUS_AUDIT_FAILED

0xC000026C

0xC0000415

0x00000003 UNSYNCHRONIZED_ACCESS

0x05 INVALID_PROCESS_ATTACH_ATTEMPT