Home > Hard Disk Repair > Common blue screen error messages in windows

Common blue screen error messages in windows

May 18th, 2010

Blue Screen Error Messages Blue Screen stop messages provide diagnostic information, such as Stop codes and driver names, that you can use to resolve the problem. However, this information disappears when you restart your computer. Therefore, it is important to record the information displayed for future reference.

The following are a list of the more common stop codes and potential resolutions in windows:

  1. Stop 0x0000000A or IRQL_NOT_LESS_OR_EQUAL
  2. Stop 0x0000001E or KMODE_EXCEPTION_NOT_HANDLED
  3. Stop 0x00000024 or NTFS_FILE_SYSTEM
  4. Stop 0x0000002E or DATA_BUS_ERROR
  5. Stop 0x0000003F or NO_MORE_SYSTEM_PTES
  6. Stop 0x00000050 or PAGE_FAULT_IN_NONPAGED_AREA
  7. Stop 0x00000077 or KERNEL_STACK_INPAGE_ERROR
  8. Stop 0x00000079 or MISMATCHED_HAL
  9. Stop 0x0000007A or KERNEL_DATA_INPAGE_ERROR
  10. Stop 0x0000007B or INACCESSIBLE_BOOT_DEVICE
  11. Stop 0x0000007F or UNEXPECTED_KERNEL_MODE_TRAP
  12. Stop 0x0000009F or DRIVER_POWER_STATE_FAILURE
  13. Stop 0xBE or ATTEMPTED_WRITE_TO_READONLY_MEMORY
  14. Stop 0xC2 or BAD_POOL_CALLER
  15. Stop 0x000000CE or DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
  16. Stop 0x000000D1 or DRIVER_IRQL_NOT_LESS_OR_EQUAL
  17. Stop 0x000000D8 or DRIVER_USED_EXCESSIVE_PTES
  18. Stop 0x000000EA or THREAD_STUCK_IN_DEVICE_DRIVER
  19. Stop 0x000000ED or UNMOUNTABLE_BOOT_VOLUME
  20. Stop 0x000000F2 or HARDWARE_INTERRUPT_STORM
  21. Stop 0xC000021A or STATUS_SYSTEM_PROCESS_TERMINATED
  22. Stop 0xC0000221 or STATUS_IMAGE_CHECKSUM_MISMATCH

Error Messages Related to Disks and File Systems:

These messages can provide more information for determining the cause of the Stop message. More specifically file system errors, viruses, hard disk corruption, or controller problems can cause the following Stop messages:

1. Stop 0x00000024 or NTFS_FILE_SYSTEM
This Stop message, also known as Stop 0x24, indicates that a problem occurred within Ntfs.sys, which is the driver file that allows the system to read and write to NTFS volumes.

2. Stop 0x00000050 or PAGE_FAULT_IN_NONPAGED_AREA
This Stop message, also known as Stop 0x50, occurs when requested data is not found in memory. The system generates a fault, which indicates that invalid system memory has been referenced. This fault can occur due to a variety of error conditions, such as bugs in antivirus software, a corrupted NTFS volume, or faulty hardware (typically related to defective RAM, be it main memory, L2 RAM cache, or video RAM).

3. Stop 0x00000077 or KERNEL_STACK_INPAGE_ERROR
This Stop message, also known as Stop 0x77, indicates that the requested page of kernel data from the paging file could not be read into memory. Stop 0x77 can be caused by a number of problems, such as:

  • Bad sectors on the hard disk.
  • Defective or loose cabling, improper SCSI termination, or the controller not seeing the hard disk.
  • Another device is causing a resource conflict with the storage controller.
  • Failing RAM.

4. Stop 0x0000007A or KERNEL_DATA_INPAGE_ERROR
This Stop message, also known as Stop 0x7A, indicates that the requested page of kernel data from the paging file could not be read into memory.

One of the following conditions usually causes a Stop 0x7A: a bad sector in a paging file, a virus, a disk controller error, defective hardware, or failing RAM. In rare cases, a Stop 0x7A occurs when nonpaged pool resources run out.

5. Stop 0x0000007B or INACCESSIBLE_BOOT_DEVICE
This Stop message, also known as Stop 0x7B, indicates that Windows XP Professional lost access to the system volume or boot volume during the startup process. This error always occurs while the system is starting and is often caused by one of the following:

  • Hardware problems
  • Corrupted or incompatible storage drivers
  • File system problems
  • Boot sector viruses
  • Outdated firmware

During I/O system initialization, this error can occur when:

  • The controller or driver for the startup device (typically the hard disk) failed to initialize the necessary hardware.
  • File system initialization failed because the system did not recognize the data on the boot device.
Comments are closed.