General Information on STOP 0x0000000A

ID: Q130802

The information in this article applies to:

Microsoft Windows NT operating system version 3.5
Microsoft Windows NT Advanced Server version 3.5
Microsoft Windows NT Workstation versions 3.51, 4.0
Microsoft Windows NT Server versions 3.51, 4.0
Microsoft Windows NT Server version 4.0, Enterprise Edition
Microsoft BackOffice Small Business Server version 4.0
Microsoft Windows NT version 4.0, Terminal Server Edition

SUMMARY

One of the more frequent trap codes generated by Windows NT is STOP 0x0000000A. This STOP message can be caused by both hardware and software problems. To determine the specific cause, you must debug the STOP. However, some general information can be learned by examining the parameters of the STOP message and the STOP screen information.

MORE INFORMATION

STOP 0x0000000A indicates a kernel mode process or driver attempted to access a memory address that it did not have permission to access. The most common cause of this error is a bad or corrupt pointer that references an incorrect location in memory. A pointer is a variable used by a program to refer to a block of memory. If the variable has a bad value in it, then the program tries to access memory that it should not. When this occurs in a user mode application, it generates an access violation. When it occurs in kernel mode, it generates a STOP 0x0000000A message.

To determine what process or driver tried to access memory it should not, look at the parameters displayed on the STOP screen information. For example, in the following STOP message


   STOP 0x0000000A(0xWWWWWWWW, 0xXXXXXXXX, 0xYYYYYYYY, 0xZZZZZZZZ)
   IRQL_NOT_LESS_OR_EQUAL
   ** Address 0xZZZZZZZZ has base at <address>- <driver>

The four parameters inside the parenthesis have the following meaning:


   0xWWWWWWWW   Address that was referenced improperly
   0xXXXXXXXX   IRQL that was required to access the memory
   0xYYYYYYYY   Type of access, 0=Read, 1=Write
   0xZZZZZZZZ   Address of instruction which attempted to reference
                the memory at 0xWWWWWWWW

If the last parameter (0xZZZZZZZZ) falls within the address range of one of the device drivers loaded on the system, you will know which device driver was running when the memory access occurred. This driver is often identified in the third line of the STOP screen:

**Address 0xZZZZZZZZ has base at <address>- <driver name>

If <driver name> is a specific driver, search in the Microsoft Knowledge Base on the keyword 0x0000000A and the driver name. If you don't find any relevant articles, contact Microsoft Product Support.

Additional query words: 3.50 3.51 prodnt tshoot blue screen trap irql_not_less_or_equal


Keywords          : 
Version           : 
Platform          : 
Issue type        :

Last Reviewed: February 24, 1999