STOP 0x0000000A May Occur on Multiprocessor SystemsLast reviewed: February 11, 1998Article ID: Q159909 |
The information in this article applies to:
SYMPTOMSDuring 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.
CAUSEWhen 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.
RESOLUTIONThe 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.
STATUSMicrosoft 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
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |