STOP Error Messages (BSOD)
The STOP error, or as it is more commonly called the Blue Screen of Death (BSOD) is a blue error screen that Windows displays when it has encountered a critical error. Usually when you hear people say that their Windows computer crashed, then they mean that it showed them a STOP error message.
The error messages shown below are the most commonly found in Windows XP; however, several have been found and are common in Windows Vista.
STOP 0x0000000A or IRQL_NOT_LESS_OR_EQUAL - The Stop 0xA is usually caused by faulty or incompatible hardware or software. Try running Memtest86+ to see if your RAM is faulty.
STOP 0x0000001E or KMODE_EXCEPTION_NOT_HANDLED - The Stop 0x1E message is similar to the 0xA error. I would try running Memtest86+ when receiving this error as well.
STOP 0x00000024 or 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. Try running the Chkdsk tool, this will check the integrity of the hard drive and of the volume. If an error is found when running the Chkdsk tool, then more than likely a hard drive would need to be replaced.
STOP 0x0000002E or DATA_BUS_ERROR - The Stop 0x2E message is typically caused by 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). It can also indicate hard disk damage caused by viruses or other problems.
STOP 0x0000003F or NO_MORE_SYSTEM_PTES - The Stop 0x3F message can occur after installing a faulty driver. If the message displays a particular driver, then try to disable, remove or rollback that particular driver. Check to see if there is an updated version of that driver, if so then install it.
STOP 0x00000050 or PAGE_FAULT_IN_NONPAGED_AREA - The Stop 0x50 message is most commonly caused by a hard drive that is going bad. I would find out who the manufacturer of your hard drive is and then go to their website and download their hard drive diagnostic tool. The scan usually takes a couple hours but it can tell you if there is anything wrong with your hard drive.
STOP 0x00000077 or KERNEL_STACK_INPAGE_ERROR - The Stop 0x77 message can indicate disk hardware failure, disk data corruption, or possible virus infection. I would try the Chkdsk tool to test the disk integrity and then I would run an antivirus scan.
STOP 0x00000079 or MISMATCHED_HAL - The Stop 0x79 message occurs when the system is using out-of-date Ntoskrnl.exe or Hal.dll files. This can happen after a System Repair that has copied incorrect files to the system. In Recovery Console, you can use the Copy command to copy the correct files from the Windows CD to the appropriate folder on the hard disk.
STOP 0x0000007A or KERNEL_DATA_INPAGE_ERROR - 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. I would start by running the Chkdsk tool, then run antivirus scan, and finally perform a hard drive diagnostic scan that you got from your hard drive manufacturer’s website.
STOP 0x0000007B or INACCESSIBLE_BOOT_DEVICE - The Stop 0x7B message indicates that Windows XP Professional has lost access the file that allows it to boot. STOP 0x7B errors could also indicate possible virus infection. I would start opening the Recovery Console and see if I could copy and replace the boot.ini file. If this works, then I work run an antivirus scan.
STOP 0x0000007F or UNEXPECTED_KERNEL_MODE_TRAP - The Stop 0x7F message is caused by faulty hardware, usually RAM. If you are overclocking your RAM, I would start buy reverting it to the recommended specifications. If you continue to get the error, then I would run Memtest86+ to see if the ram is faulty.
STOP 0x0000009F or DRIVER_POWER_STATE_FAILURE - The Stop 0x9F messag