STOP 0x0000000A on ALR Revolution

Last reviewed: March 24, 1997
Article ID: Q142649
The information in this article applies to:
  • Microsoft Windows NT Workstation version 3.51
  • Microsoft Windows NT Server version 3.51

SYMPTOMS

ALR Revolution Quad P6 systems running Windows NT 3.51, and possibly other systems from other manufacturers, may experience the following kernel mode stop error message:

   STOP 0x0000000A

CAUSE

This is due to a problem with Ntfs.sys. During a particular kind of internal operation involved in extending a file, the Windows NT File System (NTFS) thread that is performing the extension must have exclusive access to certain internal data structures. The thread may or may not already have exclusive ownership of the resources before it begins this function, and should only release the resources after performing the extension if it did not already own the resources. The STOP 0x0000000A is caused by the NTFS thread releasing the resources before it should, allowing other thread(s) an opportunity to interfere with the work it is doing.

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 3.51. This problem was corrected in the latest Windows NT 3.51 U.S. Service Pack. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K


Additional query words: prodnt 0xa
Keywords : kbbug3.51 ntfilesys
Version : 3.51
Platform : WinNT
Resolution Type : kbfix


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: March 24, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.