Knowledge Base

NTFS May Cause Windows NT to Fail During a Rename

Article ID: 164267

Article Last Modified on 11/1/2006

Microsoft Windows NT Workstation 3.5
Microsoft Windows NT Workstation 3.51
Microsoft Windows NT Server 3.5
Microsoft Windows NT Server 3.51

This article was previously published under Q164267

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: kbbug kbfix kbnetwork KB164267