NTFS May Cause Windows NT to Fail During a Rename

 Last reviewed: December 1, 1997
Article ID: Q164267
The information in this article applies to:
  • Microsoft Windows NT Workstation versions 3.5 and 3.51
  • Microsoft Windows NT Server versions 3.5 and 3.51

SYMPTOMS

NTFS can cause a system to fail during a rename. The STOP message will vary, but the most common is STOP 0x0000000A.

CAUSE

Under certain circumstances, a code path can be executed twice during a rename. When this happens, NTFS calculates the buffer for the file name incorrectly and tries to copy 4 GB of RAM. The system will STOP with varying messages, depending on what memory is overwritten and what else is running on the system.

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 3.5x. A supported fix is now available, but has not been fully regression- tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information.

Additional query words: prodnt move file system crash crashed hang hung
freeze frozen lock locked up filename
Keywords : kbbug3.50 kbbug3.51 NTSrvWkst ntstop kbnetwork
Version : WINNT:3.5 3.51
Platform : winnt
Issue type : kbbug
Solution 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: December 1, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.