STOP 0x0000000A May Occur on Multiprocessor Systems

Last reviewed: February 11, 1998
Article ID: Q159909
The information in this article applies to:
  • Microsoft Windows NT Workstation versions 3.51 and 4.0
  • Microsoft Windows NT Server versions 3.51 and 4.0

SYMPTOMS

During the normal operation of a multiprocessor system, it is possible that that Windows NT may produce a STOP 0x0000000A error.

On your computer running Windows NT Server, the following stop error message is displayed:

   STOP 0x0000000A (0xFE5AB000, 0x00000002, 0x00000001, 0x8013D41A)

Note: The first parameter may vary, but the last three should always be the same on a multiprocessor system.

CAUSE

When the system is performing a fast call interlock operation in the nonpaged data segment on a multiprocessor system, it is possible that Windows NT will stop with a STOP 0x0000000A error as the result. This error happens during the removal of an entry from the front of a singly linked list. It is possible that a second processor will change the link list head while the other processor is using it.

RESOLUTION

The previous code relied on the processor faulting and Windows NT handling the access violation. The routine was changed so that a lock is now put on the address of the next entry in the list.

STATUS

Microsoft has confirmed this to be a problem in Windows NT versions 3.51 and 4.0. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.


Additional query words: trap 0xA multi-processor
Keywords : kbbug3.51 kbbug4.00 NTSrvWkst ntstop
Version : WinNT:3.51,4.0
Platform : winnt
Issue type : kbbug


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: February 11, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.