Microsoft KB Archive/253229

From BetaArchive Wiki
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
Knowledge Base

PSS ID Number: 253229

Article Last Modified on 10/16/2002

The information in this article applies to:

  • Microsoft Windows NT Server 4.0
  • Microsoft Windows NT Workstation 4.0

This article was previously published under Q253229


After you fill an NTFS volume to capacity, the volume may be marked "dirty", even though Chkdsk finds no problems with the volume.


This issue can occur if an NTFS volume is filled to capacity in such a way that the file system cannot allocate disk space for its own internal data structures.


A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Windows NT 4.0 service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English-language version of this fix should have the following file attributes or later:

   Date      Time       Size    File name     Platform
   02/02/2000  07:50p   363,056 ntfs.sys      i386
   02/02/2000  07:49p   556,368 ntfs.sys      alpha


Microsoft has confirmed that this is a problem in Windows NT 4.0.


This problem does not result in data loss, but can result in unexpected and unnecessary downtime. Because there is no way to determine the cause of the bit having been set, you must run Autochk or Chkdsk in order to verify that the volume is, in fact, clean.

Keywords: kbbug kbHardware kbQFE KB253229
Technology: kbWinNT400search kbWinNTS400 kbWinNTS400search kbWinNTsearch kbWinNTSsearch kbWinNTW400 kbWinNTW400search kbWinNTWsearch