NTFS: System Process - Lost Delayed-Write Data on Lazy Write

• Microsoft Windows NT Workstation versions 3.51 and 4.0
• Microsoft Windows NT Server versions 3.51 and 4.0

SYMPTOMS

The following error may occur during disk-intensive writes to an NTFS partition:

   Application popup: System Process - Lost Delayed-Write Data : The system
   was attempting to transfer file data from buffers to
   \Device\Harddisk0\Partition2\Directory\File.ext. The write operation
   failed, and only some of the data may have been written to the file.

CAUSE

A test that was being performed on a lazy write to an NTFS partition failed.

RESOLUTION

To resolve this problem, obtain the following fix or wait for the next Windows NT service pack.

This fix should have the following timestamp:

      11/17/97  04:21p               358,736 Ntfs.sys     (Intel)
      11/13/97  09:03p               938,176 Ntkrnlmp.exe (Intel)
      11/13/97  09:02p               918,272 Ntoskrnl.exe (Intel)

      11/17/97  04:18p               553,072 Ntfs.sys     (Alpha)
      11/13/97  09:00p             1,399,360 Ntkrnlmp.exe (Alpha)
      11/13/97  09:00p             1,371,904 Ntoskrnl.exe (Alpha)

Apply Ntfs.sys and Ntoskrnlmp.exe if the target computer is a multiprocessor system.

NOTE: After copying Ntkrnlmp.exe to the computer, rename it to Ntoskrnl.exe.

NOTE: Service Pack 3 must be applied to Windows NT 4.0 before applying this fix.

A fix also exists for Windows NT 3.51. The only affected file is Ntfs.sys.

This fix should have the following timestamp:

      11/13/97  07:38p               327,184 Ntfs.sys     (Intel)

      11/13/97  07:36p               482,320 Ntfs.sys     (Alpha)

STATUS

Microsoft has confirmed this to be a problem in Windows NT versions 3.51 and 4.0. 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.