Home > Knowledge Ba > Error Messages > Here
TROUBLESHOOTING
WINDOWS STOP MESSAGES
Last updated May 2, 2006
Hold mou here for list of most recent changes.
Receive notice whenever this page is updated.
STOP Messages literally mean Windows has stopped! The appear only in the NT-bad 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 parenthes, usually unique to your computer and the particular situation.
NOTE: Many urs arch this site for the word minidump which often accompanies the 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 ur 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 prent 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 ated, 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 virus.
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.
z Troubleshooting Stop messages: General Strategies
z Troubleshooting Specific Stop Messages
z MSDN List of Win XP STOP Messages (If not a complete list, this one certainly is extensive!)
z Blue Screen Preparation Before Contacting Microsoft {KB 129845} Win NT, Win 2000, Win XP
(General remarks on STOP messages)
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, u 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; e the article linked below for details and current status of a fix from Microsoft.
z You receive the Stop error “Stop 0x05 (INVALID_PROCESS_ATTACH_ATTEMPT)” in Win XP SP2 or Server 2003 {KB 887742} Win XP SP2 (all subversions); Server 2003; Tablet PC Edition 2005
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 e Windows 2000 Professional Resource Kit, p. 1539.)
Typically due to a bad driver, or faulty or incompatible hardware or software. U 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 process that have an IRQL lower than, or equal to, its own.)
z Troubleshooting “Stop 0x0A” Messages in Windows {KB 165863} Win NT, Win 2000, Win XP
z Troubleshooting a Stop 0x0000000A Error in Windows XP {KB 314063} Win XP
z Possible Resolutions to STOP 0x0A, 0x01E, and 0x50 Errors {KB 183169} Win NT, Win 2000, Win XP
z During upgrade to Win XP {KB 311564} Win XP
z STOP 0x0000000A Error Message When You Change from AC Power to DC Power {KB 316676} Win XP
z“Stop 0x0000000A” Error Message When You Fast Switch Between Urs {KB 310918} Win XP z While booting NT on same partition as Win 2000 or XP {KB 227301} Win NT, Win 2000, Win XP z Windows XP Restarts When You Try to Shut Down Your Computer {KB 311806}
z“Fatal System Error” When You Try to U a Hewlett-Packard 5100C ScanJet {KB 307129} Win XP (with Brother printer)
z Computer May Hang During a Heavy Load with an Ericsson HIS Modem {KB 319810} Win 2000, Win XP
z STOP 0x4E, STOP 0x1A, STOP 0x50, and STOP 0xA Errors Occur When You Try to Start the Computer {KB 271955} Win NT 4.0 (corrupt physical RAM)
z“Stop: 0x0000000A (00000063, 0000001c, 00000000, parameter4)” error message on a
Windows 2000-bad computer {KB 837384} Win 2000 (program error, hotfix available) z How to U Driver Verifier to Troubleshoot Windows Drivers {KB 244617} Win 2000, Win XP, Server 2003
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 cau 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.
z Problems When You U Sound Blaster Live Driver {KB 297088} Win 2000
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, e the MSDN article linked above for further steps.
z How to Troubleshoot a STOP 0x0000001A MEMORY_MANAGEMENT Error Message {KB 282504} Win 2000
z STOP 0x4E, STOP 0x1A, STOP 0x50, and STOP 0xA Errors Occur When You Try to Start the Computer {KB 271955} Win NT 4.0 (corrupt physical RAM)
z STOP 0x0000001E Caud by Pool Corruption or STOP 0x00000050 or STOP 0x0000001A with Special Pool Enabled {KB 260831} Win NT 4.0
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 e Windows 2000 Professional Resource Kit, p. 1541.)
The Windows kernel detected an illegal or unknown processor instruction. A Stop 0x1E condition can be caud by invalid memory and access violations similar to tho that generate Stop 0xA errors. This default Windows error handler typically intercepts the problems if error-handling routines are not prent in the code itlf.
z Possible Resolutions to STOP 0x0A, 0x01E, and 0x50 Errors {KB 183169} Win NT, Win 2000, Win XP
z During Setup {KB 161703} Win NT, Win 2000, Win XP
z During Setup {KB 314451} Win XP
z An ASPI32.SYS issue (with SCSI hardware) {KB 307128} Win XP
z Caud by Open Handles while closing an application {KB 195857} Win NT, Win 2000, Win XP z Stop 0x1E in PROTCLS.SYS When You Undock a Toshiba Tecra 8100 {KB 284154} Win XP
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 caus 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.
z General Discussion {KB 290182} Win 2000
z A “Stop 0x23” Error Message Appears When You U Removable Media with the Same
Attributes {KB 305358} Win 2000
z STOP Errors 0x00000023 & 0x0000000A in FASTFAT.SYS When a Program Queries the File System {KB 289205} Win 2000
0x00000024: NTFS_FILE_SYSTEM
(Click to consult the online Win XP Resource Kit article, or e Windows 2000 Professional Resourc
e 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 caus 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.
z General Discussion {KB 228888} Win 2000, Win XP
z Caud by Open Handles while closing an application {KB 195857} Win NT, Win 2000, Win XP
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 cau, 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.
z How to Troubleshoot a “STOP 0x00000027 RDR_FILE_SYSTEM” Error Message {KB 290185} Win 2000
z“Stop 0x00000027 RDR_FILE_SYSTEM” Error Message During Shutdown {KB 261939} Win 2000 Server
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 e Windows 2000 Professional Resource Kit, p. 1545.)
This indicates a system memory parity error, typically caud 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 caud by virus or other problems.
z Windows NT 4.0 Setup Troubleshooting Guide {KB 126690} NT 4 (Recommendations for the
current error message are buried down inside this article, which isn’t necessarily limited to NT 4.)
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 itlf is flawed.
z STOP 0x00000035 When Using TDITrace from the Windows NT Resource Kit {KB 228911} Win NT 4.0 (using NT4 Resource Kit)
z Problems Changing Mou in Windows NT with IntelliPoint 2.0 {KB 155935} Win NT 3.51 & 4.0
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.
z“Stop 0x00000044 Multiple_IRP_Complete_Requests” Error Message During a Shutdown or Standby Operation {KB 294876} Win 2000 (during shutdown, hibernation, or standby)
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 arblank" class="tiny">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 caud by corrupt physical RAM, or by drivers passing bad memory descriptor lists.
z How to Troubleshoot a “STOP 0x0000004E PFN_LIST_CORRUPT” Error Message {KB 291806} Win 2000
z STOP 0x4E, STOP 0x1A, STOP 0x50, and STOP 0xA Errors Occur When You Try to Start the Computer {KB 271955} Win NT 4.0 (corrupt physical RAM)
0x0000004F: NDIS_INTERNAL_ERROR MSDN article
0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
(Click to consult the online Win XP Resource Kit article, or e 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 re
mote control and antivirus software) might cau this Stop message, as may other hardware problems (e.g., incorrect SCSI termination or a flawed PCI card). U the General Troubleshooting of STOP Messages checklist above.
z You receive a Stop 0x00000050 error on a Blue Screen {KB 894278} Win 2000, Win XP, Server 2003 (with concurrent 1003/System entry in Event Viewer: possible Rootkit spyware infestation)
z Possible Resolutions to STOP 0x0A, 0x01E, and 0x50 Errors {KB 183169} Win NT, Win 2000, Win XP
z During tup {KB 171003} Win NT, Win 2000, Win XP
z Easy CD Creator 5.0 Does Not Function In Windows XP {KB 310628} Win XP
z How to U Driver Verifier to Troubleshoot Windows Drivers {KB 244617} Win 2000, Win XP, Server 2003
z STOP Error When You Start Windows After You Connect a Scanner {KB 310869} Win XP
z Stop 0x1E in PROTCLS.SYS When You Undock a Toshiba Tecra 8100 {KB 284154} Win XP
z STOP 0x4E, STOP 0x1A, STOP 0x50, and STOP 0xA Errors Occur When You Try to Start the Computer {KB 271955} Win NT 4.0 (corrupt physical RAM)
z“STOP 0x00000050” Error Message in Stac97.sys After You Upgrade Your Panasonic
Toughbook to Win XP Service Pack 1 {KB 329832} Win XP SP1
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 (caud 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).
z How to Troubleshoot a “STOP 0x00000051 REGISTRY ERROR” Error Message {KB 282501} Win 2000
z You Receive a “Stop 0x51 (REGISTRY_ERROR)” Error Message {KB 321771} Win 2000
z“Stop 0x00000051 REGISTRY_ERROR” Error Message When You Log On {KB 810558} Win 2000 SP3 (during logon or Registry backup)
z Windows NT 4.0 Setup Troubleshooting Guide {KB 126690} NT 4 (Recommendations for the
current error message are buried down inside this article, which isn’t necessarily limited to NT 4.)
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 condary data caches, which usually means the failure of the primary drive in a fault-tolerance t. If a reboot doesn’t resolve the problem, u the General Troubleshooting of STOP Messages checklist above. If this doesn’t identify the problem, restart your computer from the mirrored (condary) system drive using a startup floppy disk, press F8 at the startup screen, and lect 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 rvice failed to initialize while starting the LastKnownGood control t. 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 t to create a dump file. If the message recurs, press F8 and lect 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
