Page 1 of 1

STOP error messages and what to do if you get one Rate Topic: -----

#1 RandomlyKnighted   User is offline

  • D.I.C Lover
  • member icon

Reputation: 119
  • View blog
  • Posts: 1,384
  • Joined: 14-January 10

Posted 27 September 2010 - 07:11 PM

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 message indicates that a driver is in an inconsistent or invalid power state. If it points to a particular application, then uninstall that application. If it points to a particular driver then you should disable, remove, or rollback the driver. Then download an updated driver or updated version of the application from the manufacturer.

STOP 0x000000BE or ATTEMPTED_WRITE_TO_READONLY_MEMORY - The Stop 0xBE message indicates that a driver attempted to write to read-only memory. If it points to a particular driver then you should disable, remove, or rollback the driver. Then download an updated driver from the manufacturer.

STOP 0x000000C2 or BAD_POOL_CALLER - The Stop 0xC2 message is similar to the 0xBE. Follow the same guidelines as shown above. The 0xC2 error message could also be caused by hardware that is defective or is about to fail. I would start by checking any hardware that has been recently been to installed to see if it might be defective and then go from there.

STOP 0x000000CE or DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS - This Stop message indicates that a driver failed to cancel pending operations before exiting. It will usually point to a driver that is causing the problem. If it does then you should disable, remove, or rollback the driver. Then download an updated driver from the manufacturer.

STOP 0x000000D1 or DRIVER_IRQL_NOT_LESS_OR_EQUAL - The Stop 0xD1 message 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. If it points to a particular driver then you should disable, remove, or rollback the driver. Then download an updated driver from the manufacturer.

STOP 0x000000D8 or DRIVER_USED_EXCESSIVE_PTES - The Stop 0xD8 message typically occurs if your computer runs out of page table entries (PTEs) due to a driver that requests large amounts of kernel memory. I would start by running Memtest86+ to make sure that your RAM isn’t defective. It might be possible that you need to upgrade your RAM. Be sure to check your computer manufacturer’s website to see what the maximum amount of RAM that your motherboard can hold before you upgrade.

STOP 0x000000EA or THREAD_STUCK_IN_DEVICE_DRIVER - 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 usually means that there is a hardware problem with the video adapter or a faulty video driver. I would start by going to your computer’s manufacturer website to install the latest video driver. If you have a video card then visit the website of the manufacturer that made your video driver and install the latest video driver.

STOP 0x000000ED or UNMOUNTABLE_BOOT_VOLUME - The kernel mode I/O subsystem attempted to mount the boot volume and it failed. Make sure your ATA cable is the correct one for your computer. For example, if you need an 80pin cable don’t replace it with a 80 pin cable.

STOP 0xC0000221 or STATUS_IMAGE_CHECKSUM_MISMATCH - 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. I would start with a System Restore or Drive Rollback to restore a previous driver. You can also use one of the recovery features that come on the Windows CD to restore the Windows files to the way they are supposed to be.

mod: edited per request for link 2012.07.24
This link can be used as an additional reference to figure out the cause of a STOP error message:

This post has been edited by modi123_1: 24 July 2012 - 01:34 PM

Is This A Good Question/Topic? 4
  • +

Replies To: STOP error messages and what to do if you get one

#2 youbob1212   User is offline

  • D.I.C Head
  • member icon

Reputation: 16
  • View blog
  • Posts: 138
  • Joined: 31-October 10

Posted 13 November 2010 - 03:01 PM

Or just go to Linux. LOL

Nice Tutorial. I see these errors all the time, so that should help me.
Was This Post Helpful? 0
  • +
  • -

Page 1 of 1