The current time is:  

 


HOME  LINKS  PRODUCTS  SERVICES  ABOUT US  GUARANTEE DOWNLOADS  TECHSUPPORT  CONTACT INFO  HINTS & TIPS

TROUBLESHOOTING
WINDOWS STOP MESSAGES
 

STOP Messages literally mean Windows has stopped! These appear only in the NT-based operating systems: Win NT, Win 2000, and Win XP. Most are hardware issues. STOP messages are identified by an 8-digit hexadecimal number, but also commonly written in a shorthand notation; e.g., a STOP 0x0000000A may also be written Stop 0xA. Four additional 8-digit hex numbers may appear in parentheses, usually unique to your computer and the particular situation.

NOTE: Many users search this site for the word minidump which often accompanies these Stop Message errors. The fact that a memory minidump occurred tells you nothing except what you already know — that there was an error. It is the name of the error condition and its 8-digit number that help you determine the actual error condition.

If a message is listed below, but has no articles or explanation (nothing but its number and name), post a request on the AumHa Forums asking about it. STOP messages of this type are rare, obscure, and usually only of interest to programmers debugging their code. Real-life scenarios of a computer user encountering them are unlikely, so I’ve made it a lower priority to document them here; but we’ll be happy to address this in the Forum (which also will tip me off that I should add more to this present page).


 

General Troubleshooting of STOP Messages

If you can’t find a specific reference to your problem, running through the following checklist stands a good chance of resolving the problem for you. This checklist is also usually the best approach to troubleshooting some specific Stop messages, such as 0x0A and 0x50.

  1. Examine the “System” and “Application” logs in Event Viewer for other recent errors that might give further clues. To do this, launch EventVwr.msc from a Run box; or open “Administrative Tools” in the Control Panel then launch Event Viewer.
  2. If you’ve recently added new hardware, remove it and retest.
  3. Run hardware diagnostics supplied by the manufacturer.
  4. Make sure device drivers and system BIOS are up-to-date.
  5. However, if you’ve installed new drivers just before the problem appeared, try rolling them back to the older ones.
  6. Open the box and make sure all hardware is correctly installed, well seated, and solidly connected.
  7. Confirm that all of your hardware is on the Hardware Compatibility List. If some of it isn’t, then pay particular attention to the non-HCL hardware in your troubleshooting.
  8. Check for viruses.
  9. Investigate recently added software.
  10. Examine (and try disabling) BIOS memory options such as caching or shadowing.

NOTE: When a STOP message occurs, Windows can create a debug file for very detailed analysis. To do this, it needs a workspace equal to the amount of physical RAM you have installed. If you resize your Win XP pagefile minimum to less than the size of your physical RAM, you will get an advisory message that your system may not be able to create a debugging information file if a STOP error occurs. My advice is to go ahead with this change if you want, but simply remember the limitation so that you can change it back if you need to troubleshoot STOP messages. Some general troubleshooting principles are suggested in the Resource Kit for approaching STOP messages overall.


 

0x00000001: APC_INDEX_MISMATCH MSDN article
0x00000002: DEVICE_QUEUE_NOT_BUSY MSDN article
0x00000003: INVALID_AFFINITY_SET MSDN article
0x00000004: INVALID_DATA_ACCESS_TRAP MSDN article

0x00000005: INVALID_PROCESS_ATTACH_ATTEMPT
(Click to consult the online MSDN article.)
Generally, use the General Troubleshooting of STOP Messages checklist above to troubleshoot this problem. A specific problem is known to exist with Win XP SP2 and Server 2003 in combination with certain antivirus programs, firewalls, and similar software; see the article linked below for details and current status of a fix from Microsoft.

0x00000006: INVALID_PROCESS_DETACH_ATTEMPT MSDN article
0x00000007: INVALID_SOFTWARE_INTERRUPT MSDN article
0x00000008: IRQL_NOT_DISPATCH_LEVEL MSDN article
0x00000009: IRQL_NOT_GREATER_OR_EQUAL MSDN article

0x0000000A: IRQL_NOT_LESS_OR_EQUAL
(Click to consult the online Win XP Resource Kit article, or see Windows 2000 Professional Resource Kit, p. 1539.)
Typically due to a bad driver, or faulty or incompatible hardware or software. Use the General Troubleshooting of STOP Messages checklist above. Technically, this error condition means that a kernel-mode process or driver tried 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.)

0x0000000B: NO_EXCEPTION_HANDLING_SUPPORT MSDN article
0x0000000C: MAXIMUM_WAIT_OBJECTS_EXCEEDED MSDN article
0x0000000D: MUTEX_LEVEL_NUMBER_VIOLATION MSDN article
0x0000000E: NO_USER_MODE_CONTEXT MSDN article
0x0000000F: SPIN_LOCK_ALREADY_OWNED MSDN article
0x00000010: SPIN_LOCK_NOT_OWNED MSDN article
0x00000011: THREAD_NOT_MUTEX_OWNER MSDN article

0x00000012: TRAP_CAUSE_UNKNOWN
(Click to consult the online MSDN article.)
By its very nature, this error means that the cause of the identified problem is unknown. Start with the General Troubleshooting of STOP Messages checklist above. Read the MSDN article linked here. Especially try to track it down by noting the history of the problem, when it appeared, and what changes were made to the system since the problem first appeared, as well as noting what activity you are attempting at the time the error message appears.

0x00000013: EMPTY_THREAD_REAPER_LIST MSDN article
0x00000014: CREATE_DELETE_LOCK_NOT_LOCKED MSDN article
0x00000015: LAST_CHANCE_CALLED_FROM_KMODE MSDN article
0x00000016: CID_HANDLE_CREATION MSDN article
0x00000017: CID_HANDLE_DELETION MSDN article
0x00000018: REFERENCE_BY_POINTER MSDN article
0x00000019: BAD_POOL_HEADER MSDN article

0x0000001A: MEMORY_MANAGEMENT
(Click to consult the online MSDN article.)
This memory management error is usually hardware related. See the General Troubleshooting of STOP Messages checklist above. If this occurs while installing Windows, also check the Windows system requirements including the amount of RAM and disk space required to load the operating system. If none of the above resolves the problem, see the MSDN article linked above for further steps.

0x0000001B: PFN_SHARE_COUNT MSDN article
0x0000001C: PFN_REFERENCE_COUNT MSDN article
0x0000001D: NO_SPIN_LOCK_AVAILABLE MSDN article

0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
(Click to consult the online Win XP Resource Kit article, or see Windows 2000 Professional Resource Kit, p. 1541.)
The Windows kernel detected an illegal or unknown processor instruction. A Stop 0x1E condition can be caused by invalid memory and access violations similar to those that generate Stop 0xA errors. This default Windows error handler typically intercepts these problems if error-handling routines are not present in the code itself.

0x0000001F: SHARED_RESOURCE_CONV_ERROR MSDN article
0x00000020: KERNEL_APC_PENDING_DURING_EXIT MSDN article
0x00000021: QUOTA_UNDERFLOW MSDN article
0x00000022: FILE_SYSTEM MSDN article

0x00000023: FAT_FILE_SYSTEM
(Click to consult the online MSDN article.)
A problem occurred within a read or write to a FAT16 or FAT32 file system drive. There may be a physical problem with the disk, or an Interrupt Request Packet (IRP) may be corrupted. Other common causes include heavy hard drive fragmentation, heavy file I/O, problems with some types of drive-mirroring software, or some antivirus software. I suggest running ChkDsk or ScanDisk as a first step; then disable all file system filters such as virus scanners, firewall software, or backup utilities. Check the file properties of FASTFAT.SYS to ensure it matches the current OS or SP version. Update all disk, tape backup, CD-ROM, or removable device drivers to the most current versions.

0x00000024: NTFS_FILE_SYSTEM
(Click to consult the online Win XP Resource Kit article, or see Windows 2000 Professional Resource Kit, p. 1543.)
A problem occurred within NTFS.SYS, the driver file that allows the system to read and write to NTFS file system drives. There may be a physical problem with the disk, or an Interrupt Request Packet (IRP) may be corrupted. Other common causes include heavy hard drive fragmentation, heavy file I/O, problems with some types of drive-mirroring software, or some antivirus software. I suggest running ChkDsk or ScanDisk as a first step; then disable all file system filters such as virus scanners, firewall software, or backup utilities. Check the file properties of NTFS.SYS to ensure it matches the current OS or SP version. Update all disk, tape backup, CD-ROM, or removable device drivers to the most current versions.

0x00000025: NPFS_FILE_SYSTEM MSDN article
0x00000026: CDFS_FILE_SYSTEM MSDN article

0x00000027: RDR_FILE_SYSTEM
(Click to consult the online MSDN article.)
This is a rare and fairly obscure error condition. Memory management issues can be one cause, and adding additional RAM commonly will resolve this version of the problem. The articles below give the best information on troubleshooting and resolving the problem.

0x00000028: CORRUPT_ACCESS_TOKEN MSDN article
0x00000029: SECURITY_SYSTEM MSDN article
0x0000002A: INCONSISTENT_IRP MSDN article
0x0000002B: PANIC_STACK_SWITCH MSDN article
0x0000002C: PORT_DRIVER_INTERNAL MSDN article
0x0000002D: SCSI_DISK_DRIVER_INTERNAL MSDN article

0x0000002E: DATA_BUS_ERROR
(Click to consult the online Win XP Resource Kit article, or see Windows 2000 Professional Resource Kit, p. 1545.)
This indicates a system memory parity error, 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 also can indicate hard disk damage caused by viruses or other problems.

0x0000002F: INSTRUCTION_BUS_ERROR MSDN article
0x00000030: SET_OF_INVALID_CONTEXT MSDN article
0x00000031: PHASE0_INITIALIZATION_FAILED MSDN article
0x00000032: PHASE1_INITIALIZATION_FAILED MSDN article
0x00000033: UNEXPECTED_INITIALIZATION_CALL MSDN article
0x00000034: CACHE_MANAGER MSDN article

0x00000035: NO_MORE_IRP_STACK_LOCATIONS
(Click to consult the online MSDN article.)
In theory, this is a driver or other software issue, which encounters a stack problem. (See the MSDN article linked here.) In practice, it has historically pointed to a driver problem and also occurs when RAM itself is flawed.

0x00000036: DEVICE_REFERENCE_COUNT_NOT_ZERO MSDN article
0x00000037: FLOPPY_INTERNAL_ERROR MSDN article
0x00000038: SERIAL_DRIVER_INTERNAL MSDN article
0x00000039: SYSTEM_EXIT_OWNED_MUTEX MSDN article
0x0000003A: SYSTEM_UNWIND_PREVIOUS_USER MSDN article
0x0000003B: SYSTEM_SERVICE_EXCEPTION MSDN article
0x0000003C: INTERRUPT_UNWIND_ATTEMPTED MSDN article
0x0000003D: INTERRUPT_EXCEPTION_NOT_HANDLED MSDN article
0x0000003E: MULTIPROCESSOR_CONFIGURATION_NOT_SUPPORTED MSDN article

0x0000003F: NO_MORE_SYSTEM_PTES
(Click to consult the online Win XP Resource Kit article.)
Indicates one or more of the following problems: (1) The system Page Table Entries (PTEs) are depleted or fragmented due to the system performing a large number of input/output (I/O) actions. (2) A faulty device driver is not managing memory properly. (3) An application, such as a backup program, is improperly allocating large amounts of kernel memory. Remove any recently installed software (especially disk-intensive applications) and recently installed drivers.

0x00000040: TARGET_MDL_TOO_SMALL MSDN article
0x00000041: MUST_SUCCEED_POOL_EMPTY MSDN article
0x00000042: ATDISK_DRIVER_INTERNAL MSDN article
0x00000043: NO_SUCH_PARTITION MSDN article

0x00000044: MULTIPLE_IRP_COMPLETE_REQUESTS
(Click to consult the online MSDN article.)
See the articles linked here for a technical discussion of what this error message means. In practice, it is usually a hardware driver issue.

0x00000045: INSUFFICIENT_SYSTEM_MAP_REGS MSDN article
0x00000046: DEREF_UNKNOWN_LOGON_SESSION MSDN article
0x00000047: REF_UNKNOWN_LOGON_SESSION MSDN article
0x00000048: CANCEL_STATE_IN_COMPLETED_IRP MSDN article
0x00000049: PAGE_FAULT_WITH_INTERRUPTS_OFF MSDN article
0x0000004A: IRQL_GT_ZERO_AT_SYSTEM_SERVICE MSDN article
0x0000004B: STREAMS_INTERNAL_ERROR MSDN article
0x0000004C: FATAL_UNHANDLED_HARD_ERROR MSDN article
0x0000004D: NO_PAGES_AVAILABLE MSDN article

0x0000004E: PFN_LIST_CORRUPT
(Click to consult the online MSDN article.)
This indicates that the memory management Page File Number list is corrupted. Can be caused by corrupt physical RAM, or by drivers passing bad memory descriptor lists.

0x0000004F: NDIS_INTERNAL_ERROR MSDN article

0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
(Click to consult the online Win XP Resource Kit article, or see Windows 2000 Professional Resource Kit, p. 1548.)
Requested data was not in memory. An invalid system memory address was referenced. Defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software (including remote control and antivirus software) might cause this Stop message, as may other hardware problems (e.g., incorrect SCSI termination or a flawed PCI card). Use the General Troubleshooting of STOP Messages checklist above.

0x00000051: REGISTRY_ERROR
(Click to consult the online MSDN article.)
This indicates a Registry or Configuration Manager problem. An I/O error may have occurred while the Registry was trying to read one of its files (caused by hardware or file system problems). This message might also appear due to a memory management error (more common in earlier versions of Windows NT).

0x00000052: MAILSLOT_FILE_SYSTEM MSDN article
0x00000053: NO_BOOT_DEVICE MSDN article
0x00000054: LM_SERVER_INTERNAL_ERROR MSDN article
0x00000055: DATA_COHERENCY_EXCEPTION MSDN article
0x00000056: INSTRUCTION_COHERENCY_EXCEPTION MSDN article
0x00000057: XNS_INTERNAL_ERROR MSDN article

0x00000058: FTDISK_INTERNAL_ERROR
(Click to consult the online MSDN article.)
Indicates an inconsistency between pages in the primary and secondary data caches, which usually means the failure of the primary drive in a fault-tolerance set. If a reboot doesn’t resolve the problem, use the General Troubleshooting of STOP Messages checklist above. If this doesn’t identify the problem, restart your computer from the mirrored (secondary) system drive using a startup floppy disk, press F8 at the startup screen, and select the Last Known Good Configuration option.

0x00000059: PINBALL_FILE_SYSTEM MSDN article

0x0000005A: CRITICAL_SERVICE_FAILED
(Click to consult the online MSDN article.)
A critical service failed to initialize while starting the LastKnownGood control set. If this is the first time you have booted after installing new hardware, remove the hardware and boot again. Check the Hardware Compatibility List to verify that the hardware and its drivers are compatible with your version of Windows. If Windows is loaded and no new hardware has been installed, reboot with recovery options set to create a dump file. If the message recurs, press F8 and select the Last Known Good option when you reboot. If there is no Last Known Good configuration, try using the Emergency Repair Disk.

0x0000005B: SET_ENV_VAR_FAILED MSDN article
0x0000005C: HAL_INITIALIZATION_FAILED MSDN article
0x0000005D: UNSUPPORTED_PROCESSOR MSDN article
0x0000005E: OBJECT_INITIALIZATION_FAILED MSDN article
0x0000005F: SECURITY_INITIALIZATION_FAILED MSDN article
0x00000060: PROCESS_INITIALIZATION_FAILED MSDN article
0x00000061: HAL1_INITIALIZATION_FAILED MSDN article
0x00000062: OBJECT1_INITIALIZATION_FAILED MSDN article
0x00000063: SECURITY1_INITIALIZATION_FAILED MSDN article
0x00000064: SYMBOLIC_INITIALIZATION_FAILED MSDN article
0x00000065: MEMORY1_INITIALIZATION_FAILED MSDN article
0x00000066: CACHE_INITIALIZATION_FAILED MSDN article
0x00000067: CONFIG_INITIALIZATION_FAILED MSDN article
0x00000068: FILE_INITIALIZATION_FAILED MSDN article
0x00000069: IO1_INITIALIZATION_FAILED MSDN article
0x0000006A: LPC_INITIALIZATION_FAILED MSDN article
0x0000006B: PROCESS1_INITIALIZATION_FAILED MSDN article
0x0000006C: REFMON_INITIALIZATION_FAILED MSDN article
0x0000006D: SESSION1_INITIALIZATION_FAILED MSDN article
0x0000006E: SESSION2_INITIALIZATION_FAILED MSDN article

0x0000006F: SESSION3_INITIALIZATION_FAILED
(Click to consult the online MSDN article.)
The process creation failure indicated by this error message can only happen during the fairly brief time that the Windows Executive is being initialized, which is during phase 4 of Windows startup. Typically there is a problem with a device driver or with a missing or corrupt system file used during Windows startup.

0x00000070: SESSION4_INITIALIZATION_FAILED
0x00000071: SESSION5_INITIALIZATION_FAILED
0x00000072: ASSIGN_DRIVE_LETTERS_FAILED
0x00000073: CONFIG_LIST_FAILED
0x00000074: BAD_SYSTEM_CONFIG_INFO
0x00000075: CANNOT_WRITE_CONFIGURATION

0x00000076: PROCESS_HAS_LOCKED_PAGES
(Click to consult the online MSDN article.)
This error message is caused by a driver failing to release locked pages after an I/O operation. The article linked here contain a method to track the problem if it recurs, and identify the problem driver. (The third parameter of the error message shows the number of locked pages.)

0x00000077: KERNEL_STACK_INPAGE_ERROR
(Click to consult the online Win XP Resource Kit article, or see Windows 2000 Professional Resource Kit, p. 1549.)
A page of kernel data requested from the pagefile could not be found or read into memory. This message also can indicate disk hardware failure, disk data corruption, or possible virus infection.

0x00000078: PHASE0_EXCEPTION

0x00000079: MISMATCHED_HAL
(Click to consult the online Win XP Resource Kit article, or see Windows 2000 Professional Resource Kit, p. 1552.)
The Hardware Abstraction Layer (HAL) and the kernel type for the computer do not match. This most often occurs when ACPI firmware settings are changed. For example, you might install Win 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
(Click to consult the online Win XP Resource Kit article, or see Windows 2000 Professional Resource Kit, p. 1553.)
A page of kernel data was not found in the pagefile and could not be read into memory. This might be due to incompatible disk or controller drivers, firmware, or hardware.

0x0000007B: INACCESSIBLE_BOOT_DEVICE
(Click to consult the online Win XP Resource Kit article, or see Windows 2000 Professional Resource Kit, p. 1555.)
Windows lost access to the system partition or boot volume during the startup process. Typical causes: Installing incorrect device drivers when installing or upgrading storage adapter hardware, or a virus.

0x0000007C: BUGCODE_NDIS_DRIVER
0x0000007D: INSTALL_MORE_MEMORY

0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
(Click to consult the online MSDN article.)
A system thread generated an exception which the error handler did not catch. There are numerous individual causes for this problem, including hardware incompatibility, a faulty device driver or system service, or some software issues. Check Event Viewer (EventVwr.msc) for additional information.

0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP
(Click to consult the online Win XP Resource Kit article, or see Windows 2000 Professional Resource Kit, p. 1558.)
One of three types of problems occurred in kernel-mode: (1) Hardware failures. (2) Software problems. (3) A bound trap (i.e., a condition that the kernel is not allowed to have or intercept). Hardware failures are the most common cause (many dozen KB articles exist for this error referencing specific hardware failures) and, of these, memory hardware failures are the most common.

0x00000080: NMI_HARDWARE_FAILURE
(Click to consult the online MSDN article.)
This general indication of a hardware failure is often quite difficult to pin down. Follow usual hardware troubleshooting protocols, in particular: Roll-back any recent hardware or driver changes; ensure that RAM sticks are matched and undamaged; check for viruses or hard drive damage; run ChkDsk to identify file system problems; ensure that all connections are sound inside the computer and all cards well-seated. In tough cases you may need to consult a professional shop for hardware diagnosis and repair.

0x00000081: SPIN_LOCK_INIT_FAILURE MSDN article
0x00000082: DFS_FILE_SYSTEM MSDN article
0x00000083: OFS_FILE_SYSTEM
0x00000084: RECOM_DRIVER
0x00000085: SETUP_FAILURE MSDN article
0x00000086:
0x00000087:
0x00000088:
0x00000089:
0x0000008A:
0x0000008B: MBR_CHECKSUM_MISMATCH MSDN article
0x0000008C:
0x0000008D:

0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
(Click to consult the online MSDN article.)
A kernel mode program generated an exception which the error handler didn’t catch. These are nearly always hardware compatibility issues (which sometimes means a driver issue or a need for a BIOS upgrade).

0x0000008F: PP0_INITIALIZATION_FAILED
0x00000090: PP1_INITIALIZATION_FAILED
0x00000091: WIN32K_INIT_OR_RIT_FAILURE
0x00000092: UP_DRIVER_ON_MP_SYSTEM
0x00000093: INVALID_KERNEL_HANDLE
0x00000094: KERNEL_STACK_LOCKED_AT_EXIT
0x00000095: PNP_INTERNAL_ERROR
0x00000096: INVALID_WORK_QUEUE_ITEM
0x00000097: BOUND_IMAGE_UNSUPPORTED
0x00000098: END_OF_NT_EVALUATION_PERIOD
0x00000099: INVALID_REGION_OR_SEGMENT
0x0000009A: SYSTEM_LICENSE_VIOLATION
0x0000009B: UDFS_FILE_SYSTEM
 

0x0000009C: MACHINE_CHECK_EXCEPTION
(Click to consult the online MSDN article.)
This is a hardware issue: an unrecoverable hardware error has occurred. The parameters have different meanings depending on what type of CPU you have but, while diagnostic, rarely lead to a clear solution. Most commonly it results from overheating, from failed hardware (RAM, CPU, hardware bus, power supply, etc.), or from pushing hardware beyond its capabilities (e.g., overclocking a CPU).

0x0000009D:
0x0000009E:

0x0000009F: DRIVER_POWER_STATE_FAILURE
(Click to consult the online Win XP Resource Kit article.)
A driver is in an inconsistent or invalid power state. Typically occurs during events that involve power state transitions, such as shutting down, or moving into or out of standby or hibernate mode.

0x000000A0: INTERNAL_POWER_ERROR
0x000000A1: PCI_BUS_DRIVER_INTERNAL
0x000000A2: MEMORY_IMAGE_CURRUPT
0x000000A3: ACPI_DRIVER_INTERNAL
0x000000A4: CNSS_FILE_SYSTEM_FILTER

0x000000A5: ACPI_BIOS_ERROR
(Click to consult the online MSDN article.)
The cause of this message is always errors in the ACPI BIOS. Usually, nothing can be done at an operating system level to fix the problem. See the articles linked here for more details.

0x000000A6:
0x000000A7: BAD_EXHANDLE
0x000000A8:
0x000000A9:
0x000000AA:
0x000000AB: SESSION_HAS_VALID_POOL_ON_EXIT
0x000000AC: HAL_MEMORY_ALLOCATION
0x000000AD:
0x000000AE:
0x000000AF:
0x000000B0:
0x000000B1:
0x000000B2:
0x000000B3:

0x000000B4: VIDEO_DRIVER_INIT_FAILURE
(Click to consult the online MSDN article.)
Windows was unable to enter graphics mode, because no video drivers were able to start. Commonly this is a video driver issue, or a hardware conflict with the video card. Reboot in Safe Mode (which uses a default VGA driver) and see if this resolves the problem. If so, try to correct the problem by disabling, removing, or rolling back the video driver.

0x000000B5:
0x000000B6:
0x000000B7:
0x000000B8: ATTEMPTED_SWITCH_FROM_DPC
0x000000B9: CHIPSET_DETECTED_ERROR
0x000000BA: SESSION_HAS_VALID_VIEWS_ON_EXIT
0x000000BB: NETWORK_BOOT_INITIALIZATION_FAILED
0x000000BC: NETWORK_BOOT_DUPLICATE_ADDRESS
0x000000BD:
 

0x000000BE: ATTEMPTED_WRITE_TO_READONLY_MEMORY
(Click to consult the online Win XP Resource Kit article.)
A driver attempted to write to read-only memory. Commonly occurs after installing a faulty device driver, system service, or firmware. If a driver file is named in the error message, try to correct the problem by disabling, removing, or rolling back the driver.

0x000000BF: MUTEX_ALREADY_OWNED
0x000000C0:

0x000000C1: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
(Click to consult the online MSDN article.)
A driver wrote to an invalid section of the special memory pool. You need a new driver!

0x000000C2: BAD_POOL_CALLER
(Click to consult the online Win XP Resource Kit article.)
A kernel-mode process or driver incorrectly attempted to perform memory operations. Typically, a faulty driver or buggy software causes this.

0x000000C3:

0x000000C4: DRIVER_VERIFIER_DETECTED_VIOLATION
(Click to consult the online MSDN article.)
This is the general bug check code for fatal errors that the Driver Verifier finds. The accompanying parameters are the parameters that are passed to KeBugCheckEx and displayed on a blue screen.

0x000000C5: DRIVER_CORRUPTED_EXPOOL
(Click to consult the online MSDN article.)
An attempt occurred to touch invalid memory at a process IRQL that is too high. This is almost always caused by drivers that have corrupted the system pool. If you’ve recently installed any new software, check to see if it’s properly installed; and check for updated drivers on the manufacturer’s web site.

0x000000C6: DRIVER_CAUGHT_MODIFYING_FREED_POOL
(Click to consult the online MSDN article.)
A driver tried to access a freed memory pool. Replace the driver.

0x000000C7: TIMER_OR_DPC_INVALID
(Click to consult the online MSDN article.)
A kernel timer or Delayed Procedure Call (DPC) was found somewhere in memory where it is not permitted. This is usually caused by a driver’s failure to cancel the timer or the DPC before freeing the memory in which the timer or DPC resides.

0x000000C8: IRQL_UNEXPECTED_VALUE

0x000000C9: DRIVER_VERIFIER_IOMANAGER_VIOLATION
(Click to consult the online MSDN article.)
As the title says, this signals a warning from one of the driver verifier I/O managers. See especially the article linked above for additional information.

0x000000CA: PNP_DETECTED_FATAL_ERROR

0x000000CB: DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS
(Click to consult the online MSDN article.)
This is related to Stop Code 0x76. It appears instead of 0x76 if diagnostic tracking is enabled as described in the General Discussion article below. It indicates that a driver or the I/O manager failed to release locked pages after an I/O operation. Note the name of the problem driver on the blue error screen.

0x000000CC: PAGE_FAULT_IN_FREED_SPECIAL_POOL
0x000000CD: PAGE_FAULT_BEYOND_END_OF_ALLOCATION

0x000000CE: DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
(Click to consult the online Win XP Resource Kit article.)
A driver failed to cancel pending operations before exiting. Commonly occurs after installing faulty drivers or system services.

0x000000CF: TERMINAL_SERVER_DRIVER_MADE_INCORRECT_MEMORY_REFERENCE
0x000000D0: DRIVER_CORRUPTED_MMPOOL

0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
(Click to consult the online Win XP Resource Kit article.)
The system attempted to access pageable memory using a kernel process IRQL that was too high. The most typical cause is a bad device driver (one that uses improper addresses). It can also be caused by caused by faulty or mismatched RAM, or a damaged pagefile.

0x000000D2: BUGCODE_ID_DRIVER
0x000000D3: DRIVER_PORTION_MUST_BE_NONPAGED
0x000000D4: SYSTEM_SCAN_AT_RAISED_IRQL_CAUGHT_IMPROPER_DRIVER_UNLOAD
0x000000D5: DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL
0x000000D6: DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION
0x000000D7: DRIVER_UNMAPPING_INVALID_VIEW

0x000000D8: DRIVER_USED_EXCESSIVE_PTES
(Click to consult the online Win XP Resource Kit article.)
Typically occurs if your computer runs out of Page Table Entries (PTEs) due to a driver that requests large amounts of kernel memory.

0x000000D9: MUTEX_ALREADY_OWNED
0x000000DA: SYSTEM_PTE_MISUSE
0x000000DB: DRIVER_CORRUPTED_SYSPTES
0x000000DC: DRIVER_INVALID_STACK_ACCESS
0x000000DD:
0x000000DE: POOL_CORRUPTION_IN_FILE_AREA MSDN article KB 304208
0x000000DF: IMPERSONATING_WORKER_THREAD
0x000000E0: ACPI_BIOS_FATAL_ERROR
0x000000E1: WORKER_THREAD_RETURNED_AT_BAD_IRQL
0x000000E2: MANUALLY_INITIATED_CRASH

0x000000E3: RESOURCE_NOT_OWNED
(Click to consult the online MSDN article.)
Various failures involving the NTFS file system cause this condition, as explained in the individual articles below. (All documented causes involve actual bugs in Windows.)

0x000000E4: WORKER_INVALID
0x000000E5:
0x000000E6: DRIVER_VERIFIER_DMA_VIOLATION
0x000000E7: INVALID_FLOATING_POINT_STATE
0x000000E8: INVALID_CANCEL_OF_FILE_OPEN
0x000000E9: ACTIVE_EX_WORKER_THREAD_TERMINATION

0x000000EA: THREAD_STUCK_IN_DEVICE_DRIVER
(Click to consult the online Win XP Resource Kit article.)
A device driver problem has caused the system to pause indefinitely (hang). Typically, this 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.

0x000000EB: DIRTY_MAPPED_PAGES_CONGESTION
0x000000EC: SESSION_HAS_VALID_SPECIAL_POOL_ON_EXIT

0x000000ED: UNMOUNTABLE_BOOT_VOLUME
(Click to consult the online Win XP Resource Kit article.)
The kernel mode I/O subsystem attempted to mount the boot volume and it failed. This error also might occur during an upgrade to Win XP 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.

0x000000EE:
0x000000EF: CRITICAL_PROCESS_DIED
0x000000F0:
0x000000F1: SCSI_VERIFIER_DETECTED_VIOLATION

0x000000F2: HARDWARE_INTERRUPT_STORM
(Click to consult the online Win XP Resource Kit article.)
This error message appers if the kernel detects an interrupt storm i.e., when a level-interrupt-triggered device fails to release an IRQ. Usually, this is caused by a bad device driver. (See the link above for more details.)

0x000000F3: DISORDERLY_SHUTDOWN
(Click to consult the online MSDN article.)
A Windows shutdown failed due to lack of memory. Two avenues of troubleshooting: Treat it as any other “out of memory” problem and try to discover why virtual memory wasn’t able to support the system needs, and/or investigate whether a program (or, sometimes, a driver) is refusing to terminate and thus continuing to demand more memory pages that it is possible to provide.

0x000000F4: CRITICAL_OBJECT_TERMINATION
(Click to consult the online MSDN article.)
One of the many processes or threads crucial to system operation has unexpectedly exited or been terminated. As a result, the system can no longer function. Specific causes are many, and often best resolved by a careful history of the problem and the circumstances of the error message. One user, who experienced this on return from Standby mode on Win XP SP2, found the cause was that Windows was installed on a slave drive; compare KB 330100.

0x000000F5:
0x000000F6: PCI_VERIFIER_DETECTED_VIOLATION
0x000000F7: DRIVER_OVERRAN_STACK_BUFFER
0x000000F8: RAMDISK_BOOT_INITIALIZATION_FAILED
0x000000F9: DRIVER_RETURNED_STATUS_REPARSE_FOR_VOLUME_OPEN
0x000000FA:
0x000000FB:

0x000000FC: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY

0x000000FD:
0x000000FE: BUGCODE_USB_DRIVER
0x000000FF:
 

0x1000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
(Click to consult the online MSDN article.)
Essentially the same error as 0x7E.

0x1000007F: UNEXPECTED_KERNEL_MODE_TRAP_M

0x1000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
(Click to consult the online MSDN article.)
Essentially the same error as 0x8E.

0x100000EA: THREAD_STUCK_IN_DEVICE_DRIVER_M

0xC000009A: STATUS_INSUFFICIENT_RESOURCES
The Windows kernel has allocated all of its allotted paged-pool memory.

0xC0000135: UNABLE TO LOCATE DLL
Windows attempted to load a DLL file and encountered some error condition. Among the many possible causes are that the file is missing or damaged, or that there is Registry corruption.

0xC0000142: DLL Initialization Failure
Its instances all appear to indicate that an application failed to initialize properly. Usually this is traceable to a DLL initialization failure.

0xC0000218: UNKNOWN_HARD_ERROR
(Click to consult the online MSDN article.)
A necessary Registry hive file couldn’t be loaded. The file may be corrupt or missing (requiring either an Emergency Repair Disk or a Windows reinstallation). The Registry files may have been corrupted because of hard disk corruption or some other hardware problem. A driver may have corrupted the Registry data while loading into memory, or the memory where the Registry is loading may have a parity error (turn off the external cache and check the physical RAM).

0xC000021A: STATUS_SYSTEM_PROCESS_TERMINATED
(Click to consult the online Win XP Resource Kit article, or see Windows 2000 Professional Resource Kit, p. 1561.)
This occurs when Windows 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. Because Win XP can’t run without Winlogon or CSRSS, this is one of the few situations where the failure of a user-mode service can cause the system to stop responding. This Stop message also can occur when the computer is restarted after a system administrator has modified permissions so that the SYSTEM account no longer has adequate permissions to access system files and folders.

0xC0000221: STATUS_IMAGE_CHECKSUM_MISMATCH
(Click to consult the online Win XP Resource Kit article, or see Windows 2000 Professional Resource Kit, p. 1563.)
Indicates driver problems, system file problems, disk corruption problems (such as a damaged pagefile), or faulty memory hardware.

0xC0000244
 

0xC000026C
Usually indicates device driver problems.

0xDEADDEAD: MANUALLY_INITIATED_CRASH1
(Click to consult the online MSDN article.)
“It’s dead, Jim!” This Stop message indicates that the user deliberately initiated a crash dump from either the kernel debugger or the keyboard. Perhaps it goes without saying that you don’t ever want to see this error message unless you did it on purpose!

 

 

Unit 4, 369 Victoria Street Wetherill Park NSW 2164   Ph: (02) 9756 6866  Fax (02) 9756 6447
Last Updated: Friday, 25 February 2005 10:50 AM   COPYRIGHT© 1995-2005
Pacstar the Computer Doctor Pty Ltd   ABN 82 086 695 767 Privacy Policy

Top of Page