Blue Scree Error

Stop Errors are those Blue Screens of Death (BSOD) you get with Windows XP, Windows 2000, Windows 2003, 2008 and Windows 7 & Vista - normally occurring on boot up. Similar to the BSODs in Windows 9x and ME, except they do not say "Stop".

I will explain as simply as I can what each Stop Error means . Most of these Stop Error messages will also include the name of the file or driver responsible for the Stop Error. If you know the file name you should be able to do a search on your favorite search engine and discover what hardware or software is causing the problem.

I am not going to be able to tell you how to go about fixing these errors, but I can tell you generally what is causing them; putting you on the right track to fix them. Normally when I use to get one, I just reinstalled XP because I was to lazy to bather fixing the problem. These days I will attempt to fix them with out reinstalling. I have found that just doing a repair, the R option when reinstalling never seems to fix my problem, so your best option maybe to track down the error and fix it.

Stop 0x0000000A or IRQL_NOT_LESS_OR_EQUAL - This message is typically due to faulty or incompatible hardware or device driver. It could be cause by software being incompatible, requesting use of too high of an IRQ .

Stop 0x000000A5 - This message is typically caused because the bios in this system is not fully ACPI compliant. Updated bios or you can turn off ACPI mode during text mode setup. To do this,press the F7 key when you are prompted to install storage drivers.

Stop 0x0000001E or KMODE_EXCEPTION_NOT_HANDLED - This message indicates that there is not enough free space on the drive, the BIOS is incompatible or needs upgrading, or you are using a third party hardware driver that is not compatible.

Stop 0x00000023 or FAT_FILE_SYSTEM - This message indicates that a program is using an out dated function to query for a file or drive, the function is not supported by the Fastfat.sys file. You need to install a Windows update.

Stop 0x00000024 or NTFS_FILE_SYSTEM - This message indicates that a problem with Ntfs.sys, this driver reads and writes to NTFS drives. A similar Stop message, 0x23, exists for the file allocation table (FAT16 or FAT32) file systems.

Stop 0xC000026C or STATUS_IMAGE_CHECKSUM_MISMATCH - See Stop Error 0x221

Stop 0x0000002E or DATA_BUS_ERROR - This message is caused by a system memory parity error. Defective RAM, Level1 or Level 2 cache , a bad motherboard, or other defective memory such as video memory. It can also mean that the hard drive is damage caused by viruses or the drive is failing.

Stop 0x0000003F or NO_MORE_SYSTEM_PTES - This message is a little harder to explain, basically what it means is that a program or device driver is a memory hog. The following is a list of possible causes:

• 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.

0xA - Page Table Entry (PTE) type: 0 = system expansion, 1 = non-paged pool expansion

0xB - Requested size

0xC - Total free system PTEs

0xD - Total system PTEs

Stop 0x00000050 or PAGE_FAULT_IN_NONPAGED_AREA - This message occurs when you install a faulty or incompatible device driver or a driver for a system service. Uninstall the newly installed device or service, obtain the correct driver for your version of Windows.

Stop 0x00000077 or KERNEL_STACK_INPAGE_ERROR - This message indicates that the requested page from virtual memory could not be found or read into RAM or physical memory. It can also indicate disk hardware failure, disk data corruption, or possible virus infection of the master boot record.

Stop 0x00000079 or MISMATCHED_HAL - This message occurs when you are using an out of date Ntoskrnl.exe or HAL.dll file. HAL, hardware abstraction layer 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 Professional on an x86-based computer with the firmware ACPI enable option enabled and later decide to disable it. This error can also results when mismatched single and multi-processor configuration files are copied to the system.

Stop 0x0000007A or KERNEL_DATA_INPAGE_ERROR - This message is almost the same as 0x0000077 but is cause by incompatible disk or controller drivers, firmware, or hardware.

Stop 0x0000007B or INACCESSIBLE_BOOT_DEVICE - This message indicates that Windows has lost access to the system partition or boot sector during the boot up process, an incorrect device driver was installed for some storage adapter, hard drive or other type of drive that you are booting to. It also could be that possible a virus has infected the boot sector of the hard drive.

Stop 0x0000007F or UNEXPECTED_KERNEL_MODE_TRAP - This message occurs if you over clock your system, hardware has become defective, or an incompatible system or device driver is installed

Stop 0x0000009F or DRIVER_POWER_STATE_FAILURE - This message indicates that a driver is in an inconsistent or invalid power state. An example would be if a driver is not powered down during the start of suspending to the hibernate state or standby, or shut down.

Stop 0xBE or ATTEMPTED_WRITE_TO_READONLY_MEMORY - This message indicates that a system or device driver attempted to write to read-only memory.

Stop 0x000000C2 or BAD_POOL_CALLER - This message indicates that a kernel-mode process or driver incorrectly attempted to perform memory operations. The message is typically due to a faulty driver.

Stop 0x000000C4 or DRIVER_VERIFIER_DETECTED_VIOLATION - This message is display if Norton Anitvirus is installed and Deadlock Detection in Driver Verifier Is Turned on.

Stop 0x000000CE or DRIVER_UNLOADED_WITHOUT _CANCELING_PENDING_OPERATIONS - This Stop message occurs when you install a faulty device driver or system service, the driver failed to cancel pending operations before exiting.

Stop 0x000000D1 or DRIVER_IRQL_NOT_LESS_OR_EQUAL - This message is the same as 0x000000CE but is caused by the driver tried to access memory using a process with to high of an IRQL

Stop 0x000000D8 or DRIVER_USED_EXCESSIVE_PTES - See Stop 0x0000003F

Stop 0x000000EA or THREAD_STUCK_IN_DEVICE_DRIVER - This message indicates that there is a problem with the Display Adapter (Video) driver. Update your driver or replace the video hardware.

Stop 0x000000ED or UNMOUNTABLE_BOOT_VOLUME - The Stop message occurs if you are using Ultra DMA with a 40 wire cable instead of the 80 wire cable or BIOS is set to use Ultra DMA . It is also possible that the File System is damaged by loading some piece of hardware.

Stop 0x000000F2 or HARDWARE_INTERRUPT_STORM - This one is going to be a stuff one to explain so here is what MS says. If the kernel detects an interrupt storm . An interrupt storm occurs when a level-interrupt-triggered device fails to release an interrupt request ( IRQ ). This can result from the following causes:

• A device fails to respond to an interrupt release signal sent from a driver.
• An incorrectly written device driver fails to send an interrupt release request to a device. The driver fails to determine that the interrupt was hardware initiated.
• An incorrectly written device driver claims an interrupt request meant for a different device. This occurs only for multiple devices sharing an IRQ.
• The edge level control register is set incorrectly by system firmware.
• Edge level and level-interrupt-triggered devices are incorrectly assigned the same IRQ (for example, a serial port and a Peripheral Component Interconnect (PCI) SCSI controller).

Stop 0xC000021A or STATUS_SYSTEM_PROCESS_TERMINATED - The message can occur when the computer is restarted after a system administrator has modified permissions in such a way that the SYSTEM account no longer has adequate permissions to access system files and folders.Or if the OS switches into kernel mode and a user-mode subsystem, such as Winlogon or the Client Server Runtime Subsystem (CSRSS), is compromised and security can no longer be guaranteed.

Stop 0xC0000218 or UNKNOWN_HARD_ERROR - {Registry File Failure} This Stop message indicates that one of the Registry file could not be loaded. See our newletter for help on this Stop Error.

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