Stop Messages
When Windows XP detects a problem
from which it cannot recover, it
displays Stop messages. These are
text-mode error messages that report
information about the condition.
Stop messages, sometimes referred to
as blue screens (BSoD), contain
specific information that can help you
diagnose and possibly resolve the
problem detected by the Windows
kernel.
This list describes these messages and
helps you understand and interpret
them.
This list is NOT exhaustive or meant to resolve EVERY error.
This list of messages is a guide to individual messages and their possible causes and
resolutions... Having a basic understanding of these error messages enables you to
communicate with your technical support professional more effectively too.
With all these Stop messages, you can pretty much assume someone else has
encountered the problem before you. That is why tying in the error message into
www.google.com , posting a notice for help on a relevant newsgroup and entering the
stop code into the "Microsoft Knowledge Base" can yield help just when you need it!
Here is the (long) list:
Stop 0x0000000A or IRQL_NOT_LESS_OR_EQUAL
The Stop 0xA message indicates that a kernel-mode process or driver attempted 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. This Stop message is typically due to
faulty or incompatible hardware or software.
Possible Resolutions:
- A Stop 0xA message might occur after installing a faulty device driver, system service,
or firmware. If a Stop message lists a driver by name, disable, remove, or roll back the
driver to correct the problem. If disabling or removing drivers resolves the issues, contact
the manufacturer about a possible update. Using updated software is especially important
for multimedia applications, antivirus scanners, and CD mastering tools.
- A Stop 0xA message might also be due to failing or defective hardware. If a Stop
message points to a category of devices (video or disk adapters, for example), try
removing or replacing the hardware to determine if it is causing the problem.
- If you encounter a Stop 0xA message while upgrading to Windows XPl, the problem
might be due to an incompatible driver, system service, virus scanner, or backup. To
avoid problems while upgrading, simplify your hardware configuration and remove all
third-party device drivers and system services (including virus scanners) prior to running
setup. After you have successfully installed Windows XP, contact the hardware
manufacturer to obtain compatible updates.
Microsoft KB articles:
Troubleshooting a Stop 0x0000000A Error in Windows XP
STOP 0x0000000A Error Message When You Change from AC Power to DC Power
STOP 0x0000000A Error Message When You Fast Switch Between Users
STOP 0x0000000A Irql_Not_Less_or... During Windows XP Upgrade
STOP 0x0000000A Windows XP restarts when you try to shut down your computer
STOP 0x0000000A Computer automatically restarts after upgrade to XP
top
Stop 0x0000001E or KMODE_EXCEPTION_NOT_HANDLED
The Stop 0x1E message indicates that the Windows XP kernel detected an illegal or
unknown processor instruction. The problems that cause Stop 0x1E messages share
similarities with those that generate Stop 0xA errors in that they can be due to invalid
memory and access violations. This default Windows XP error handler typically intercepts
these problems if error-handling routines are not present in the code itself.
Possible Resolutions:
- Stop 0x1E messages typically occur after installing faulty drivers or system services, or
they can indicate hardware problems, such as memory and IRQ conflicts. If a Stop
message lists a driver by name, disable, remove, or roll it back to correct the problem. If
disabling or removing applications and drivers resolves the issue, contact the hardware
manufacturer about a possible update. Using updated software is especially important for
multimedia applications, antivirus scanners, and CD mastering tools.
- If the Stop message mentions the file Win32k.sys, the source of the error might be a
third-party "remote control" program. If such software is installed, you might be able to
disable it by starting the system in safe mode. If not, use Recovery Console to manually
delete the system service file that is causing the problem.
- Problems can result from system firmware incompatibilities. Many Advanced
Configuration and Power Interface (ACPI) issues can be resolved by updating to the latest
firmware.
- Other possible causes include insufficient disk space while installing applications or
performing certain functions that require more memory. You can free up space by deleting
unneeded files. Use Disk Cleanup to increase available disk space. From Recovery
Console, remove temporary files (those with .tmp file extensions), Internet cache files,
application backup files, and .tmp files generated by Chkdsk.exe or Autochk.exe. You can
also choose to install additional applications to another hard disk with more free space or move data files, paging files, and so on.
- The problem might be due to a memory leak caused by an application or service that is
not releasing memory correctly. Poolmon (Poolmon.exe) helps you to isolate the
components that are causing kernel memory leaks.
For more information about troubleshooting memory leaks, see...
Microsoft KB articles:
Q177415, "How to
Use Poolmon to Troubleshoot Kernel Mode Memory Leaks," and Q298102, "Finding Pool
Tags Used by Third Party Files Without Using the Debugger."
Microsoft KB articles:
STOP 0x0000001E Error Message During Windows Setup
STOP 0x0000001E KMODE_EXCEPTION_NOT_HANDLED Error Message from Aspi32.sys
top
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. A similar Stop
message, 0x23, exists for the file allocation table (FAT16 or FAT32) file systems.
Possible Resolutions:
- Malfunctioning SCSI and Advanced Technology Attachment (ATA) hardware or drivers
can also adversely affect the system's ability to read and write to disk, causing errors. If
using SCSI hard disks, check for cabling and termination problems between the SCSI
controller and the disks. Periodically check Event Viewer for error messages related to
SCSI or FASTFAT in the System log or Autochk in the Application log.
- Verify that the tools you use to continually monitor your system, such as virus
scanners, backup programs, or disk defragmenters are compatible with Windows XP.
Some disks and adapters come packaged with diagnostic software that you can use to runhardware tests.
To test hard disk or volume integrity
Method 1:
- In the Run dialog box, in the Open box type: cmd
- tart the Chkdsk tool, which detects and attempts to resolve file system structural
corruption. At the command prompt type: chkdsk drive: /f
Method 2:
- Double-click My Computer, and then select the hard disk you want to check.
- 2. On the File menu, click Properties.
- Click the Tools tab.
- In the Error-checking box, click Check Now.
- In Check disk options, select the Scan for and attempt recovery of bad sectors check
box. You can also select the Automatically fix file system errors check box.
If the volume you are checking is in use, a message asks whether you want to delay disk
error checking until the next time you restart your computer. After you restart, disk error
checking runs and the volume chosen is not available to run other tasks during this
process. If you cannot restart the computer due to the error, use safe mode or Recovery
Console.
If you are not using the NTFS file system, and the system partition is formatted with the
file allocation table (FAT16 or FAT32) file system, long file name (LFN) information can be
lost if hard disk tools are started from an MS-DOS command prompt. A command prompt
appears when using a startup floppy disk or when using the command prompt startup
option on multiple boot systems that use FAT16 or FAT32 partitions with Microsoft
Windows 95 OEM Service Release 2 (OSR2), Microsoft Windows 98, or Microsoft Windows
Millennium Edition (Me) installed. Do not use tools meant for other operating systems on
Windows XP partitions!
- Nonpaged pool memory might be depleted, which can cause the system to stop. You
can resolve this situation by adding more RAM, which increases the quantity of nonpaged
pool memory available to the kernel.
Microsoft KB articles:
Troubleshooting Stop 0x24 or NTFS_FILE_SYSTEM Error Messages
STOP 0x23 (or STOP 0x24) When restarting PC after installing PC-Magic Encrypted Magic
Folders
top
Stop 0x0000002E or DATA_BUS_ERROR
The Stop 0x2E message indicates a system memory parity error. The cause is typically
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). A Stop 0x2E message can also indicate hard disk damage caused by
viruses or other problems.
Possible Resolutions:
- Stop 0x2E is typically due to defective, malfunctioning, or failed memory hardware,
such as memory modules, Level 2 (L2) SRAM cache, or video adapter RAM. If you added
new hardware recently, remove and replace it to determine if it is causing or contributing
to the problem. Run diagnostics software supplied by the system manufacturer to
determine if the component has failed.
- Stop 0x2E messages can also occur after installing faulty drivers or system services. If
a file name is given, you need to disable, remove, or roll back that driver. Disable theservice or application and confirm that this resolves the error. If so, contact the hardware
manufacturer about a possible update. Using updated software is especially important for
backup programs, multimedia applications, antivirus scanners, and CD mastering tools.
- Hard disk corruption can also cause this Stop message.
- The problem might also be due to cracks, scratched traces, or defective components on
the motherboard. If all else fails, take the system motherboard to a repair facility for
diagnostic testing.
top
Stop 0x0000003F or NO_MORE_SYSTEM_PTES
The Stop0x3F message indicates one or more of the following problems:
- The system Page Table Entries (PTEs) are depleted or fragmented due to the system
performing a large number of input/output (I/O) actions.
- A faulty device driver is not managing memory properly.
- An application, such as a backup program, is improperly allocating large amounts of
kernel memory.
Possible Resolutions:
- Stop 0x3F messages can occur after installing faulty drivers or system services. If a file
name is given, you need to disable, remove, or roll back that driver. Disable the service or
application and confirm that this resolves the error. If so, contact the hardware
manufacturer about a possible update. Using updated software is especially important for
backup programs, multimedia applications, antivirus scanners, and CD mastering tools.
- The system might not actually be out of PTEs, but a contiguous memory block of
sufficient size is not available to satisfy a driver or application request. Check for the
availability of updated driver or application files and consult the hardware or program
documentation for minimum system requirements.
- Another cause is excessive demands for system PTE by applications. This situation is
more common in server environments. Windows XP Professional provides a registry entry,
SystemPages, that you can use to increase the number of PTEs allocated.
Caution:
Do not edit the registry unless you have no alternative. The registry editor bypasses
standard safeguards, allowing settings that can damage your system, or even require you
to reinstall Windows. If you must edit the registry, back it up first...
To increase the number of PTEs allocated in the registry
- In the Run dialog box, and in the Open box, type: regedit
- In the registry editor, navigate to the subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory
Management.
- Double-click on PagedPoolSize and SystemPages to view the value for each entry.
- If PagedPoolSize is not zero, assign a value of 0.
- If SystemPages is not zero, assign a value of 40000 for systems with 128 MB (or less)
of memory, or 110000 for systems with 128 MB to 256 MB of memory. For systems with
more memory, do not increase the SystemPages value above 110000 without contacting
Microsoft technical support.
- Click OK, and then close the registry editor.
- Restart your computer.
top
Stop 0x00000050 or PAGE_FAULT_IN_NONPAGED_AREA
The Stop 0x50 message indicates that requested data was not in memory. The system
generates an exception error when using a reference to an invalid system memory
address. Defective memory (including main memory, L2 RAM cache, video RAM) or
incompatible software (including remote control and antivirus software) might cause Stop
0x50 messages.
Possible Resolutions:
- If you added new hardware recently, remove and replace the hardware to determine if
it is causing or contributing to the problem. Run diagnostics software supplied by the
hardware manufacturer to determine if the component has failed.
- Stop 0x50 messages can also occur after installing faulty drivers or system services. If
the file name is listed, you need to disable, remove, or roll back that driver. If not, disable
the recently installed service or application to determine if this resolves the error. If this
does not resolve the problem, contact the hardware manufacturer for updates. Using
updated drivers and software is especially important for network interface cards, video
adapters, backup programs, multimedia applications, antivirus scanners, and CD
mastering tools. If an updated driver is not available, attempt to use a driver from a
similar device in the same family. For example, if printing to a Model 1100C printer causes Stop 0x50 errors, using a printer driver meant for a Model 1100A or Model 1000 might
temporarily resolve the problem.
Microsoft KB articles:
STOP 0x00000050 PrtSeqRd deferencing null device object
STOP 0x50 Error starting Windows after connecting a scanner
top
Stop 0x00000077 or KERNEL_STACK_INPAGE_ERROR
The Stop 0x77 message indicates that a page of kernel data requested from the paging
(virtual memory) file could not be found or read into memory. This Stop message can also
indicate disk hardware failure, disk data corruption, or possible virus infection.
Possible Resolutions:
- Stop 0x77 messages can be caused by bad sectors in the virtual memory paging file or
a disk controller error. In extremely rare cases, depleted nonpaged pool resources can
cause this error. If the first and third parameters are zero, the stack signature in the
kernel stack is missing, which is an error typically caused by defective hardware. If the
I/O status is 0xC0000185 and the paging file is on a SCSI disk, check for cabling and
termination issues. An I/O status code of 0xC000009C or 0xC000016A indicates that the
requested data could not be found. You can try to correct this by restarting the computer.
If a problem with disk integrity exists, Autochk, a program that attempts to mark bad disk
sectors as defective so that they are not used in the future, starts automatically. If
Autochk fails to run, you can manually perform the integrity check yourself by following
the instructions to run Chkdsk provided in "Stop 0x00000024 or NTFS_FILE_SYSTEM" earlier in this list.
- Another cause of Stop 0x77 messages is defective, malfunctioning, or failed memory
hardware, such as memory modules, Level 2 (L2) SRAM cache, or video adapter RAM. If
you added new hardware recently, remove and replace it to determine if it is causing or
contributing to the problem. Run diagnostics software supplied by the system
manufacturer to determine if the component has failed.
- The problem might also be due to cracks, scratched traces, or defective components on
the motherboard. If all else fails, take the system motherboard to a repair facility for
diagnostic testing.
- Problems that cause Stop 0x77 messages can also cause Stop 0x7A messages. For
more information about Stop 0x7A zessages, see "Stop 0x0000007A or
KERNEL_DATA_INPAGE_ERROR" later in this list.
Microsoft KB articles:
Troubleshooting Stop 0x00000077 or KERNEL_STACK_INPAGE_ERROR
top
Stop 0x00000079 or MISMATCHED_HAL
The Stop 0x79 message indicates that the hardware abstraction layer (HAL) and the
kernel type for the computer do not match. This error most often occurs when ACPI
firmware settings are changed. For example, you might install Windows 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.
Possible Resolutions:
- A Stop 0x79 message occurs when the system is using out-of-date Ntoskrnl.exe or
Hal.dll files. This can occur after manual repairs that involve copying incorrect files to the
system. This error also occurs when using mismatched files, such as copying a
multiprocessor HAL on to a system using a single-processor kernel (or vice versa). The
kernel and HAL files for single-processor and multiprocessor systems are stored on the
Windows XP Professional operating system CD using two different file names. For
example, the single and multi-processor versions of the kernel, named Ntoskrnl.exe and
Ntkrnlmp.exe respectively. Setup copies either Ntoskrnl.exe or Ntkrnlmp.exe to your
system as Ntoskrnl.exe. In Recovery Console, you can use the Copy command to copy the
correct HAL or kernel files from the CD to the appropriate folder on the hard disk.
- If you experience Stop 0x79 messages after changing firmware settings, restore the
original settings used during Windows XP Professional Setup.
Because systems that use the ACPI HAL ignore IRQ assignments stored in firmware, you
can only manually change IRQ settings for non-ACPI (Standard PC HAL) systems. Some
x86-based provide the option to toggle ACPI zunctionality. To disable or re-enable ACPI,
you must change firmware settings and reinstall Windows XP. Because of the numerous
registry and system file changes required, you must run Setup again (an upgrade
installation does not work).
Because systems that use the ACPI HAL ignore IRQ assignments stored in firmware, you
can only manually change IRQ settings for non-ACPI (Standard PC HAL) systems. Some
x86-based provide the option to toggle ACPI functionality. To disable or re-enable ACPI,
you must change firmware settings and reinstall Windows XP. Because of the numerous
registry and system file changes required, you must run Setup again (an upgrade
installation does not work).
top
Stop 0x0000007A or KERNEL_DATA_INPAGE_ERROR
Possible Resolutions:
- Stop 0x7A can be caused by bad sectors in the virtual memory paging file, disk
controller error, virus infection, or memory hardware problems. In extremely rare cases,
depleted nonpaged pool resources can cause this error. If the first and third parameters
are zero, the stack signature in the kernel stack is missing, an error typically caused by
defective hardware. If the I/O status is 0xC0000185 and the paging file is on a SCSI disk,
check for cabling and termination issues. An I/O status code of 0xC000009C or
0xC000016A indicates that the requested data could not be found. You can try to correct
this by restarting the computer. If a problem with disk integrity exists, Autochk, a program that attempts to mark bad disk sectors as defective so that they are not used in
the future, starts automatically. If Autochk fails to run, you can manually perform the
integrity check yourself by following the instructions to run Chkdsk provided in "Stop
0x00000024 or NTFS_FILE_SYSTEM" earlier in this appendix.
- Another cause of Stop 0x7A messages is defective, malfunctioning, or failed memory
hardware, such as memory modules, Level 2 (L2) SRAM cache, or video adapter RAM. If
you added new hardware recently, remove and replace it to determine if it is causing or
contributing to the problem. Run diagnostics software supplied by the system
manufacturer to determine if the component has failed.
- # Check the hardware manufacturer's Web site for updates to disk adapter firmware or
drivers that improve compatibility. Verify that your disks and controller support the same
set of advanced features, such as higher transfer rates. If necessary, select a slower
transfer rate if an update is not yet available. Consult your hardware or device
documentation for more information.
Important
- You can install disk controller drivers not present on the Windows XP Professional
operating system CD by responding to the following prompt shortly after starting Setup:
- Press F6 if you need to install a third party SCSI or RAID driver.
- Press F6, and when prompted, provide the appropriate storage controller driver (ATA or
SCSI) supplied by the manufacturer.
- # The problem might also be due to cracks, scratched traces, or defective components on
the motherboard. If all else fails, take the system motherboard to a repair facility for
diagnostic testing.
- # Problems that cause Stop 0x7A messages can also cause Stop 0x77 messages. For
more information about Stop 0x77 messages, see "Stop 0x00000077 or
KERNEL_STACK_INPAGE_ERROR" earlier in this list.
top
Stop 0x00000079 or MISMATCHED_HAL
The Stop 0x79 message indicates that the hardware abstraction layer (HAL) and the
kernel type for the computer do not match. This error most often occurs when ACPI
firmware settings are changed. For example, you might install Windows 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.
Possible Resolutions:
- A Stop 0x79 message occurs when the system is using out-of-date Ntoskrnl.exe or
Hal.dll files. This can occur after manual repairs that involve copying incorrect files to the
system. This error also occurs when using mismatched files, such as copying a
multiprocessor HAL on to a system using a single-processor kernel (or vice versa). The
kernel and HAL files for single-processor and multiprocessor systems are stored on the
Windows XP Professional operating system CD using two different file names. For
example, the single and multi-processor versions of the kernel, named Ntoskrnl.exe and
Ntkrnlmp.exe respectively. Setup copies either Ntoskrnl.exe or Ntkrnlmp.exe to your
system as Ntoskrnl.exe. In Recovery Console, you can use the Copy command to copy the
correct HAL or kernel files from the CD to the appropriate folder on the hard disk
- If you experience Stop 0x79 messages after changing firmware settings, restore the
original settings used during Windows XP Professional Setup.
Because systems that use the ACPI HAL ignore IRQ assignments stored in firmware, you
can only manually change IRQ settings for non-ACPI (Standard PC HAL) systems. Some
x86-based provide the option to toggle ACPI functionality. To disable or re-enable ACPI,
you must change firmware settings and reinstall Windows XP. Because of the numerous
registry and system file changes required, you must run Setup again (an upgrade
installation does not work).
top
Article by: Marc Liron - Microsoft MVP |
