Heavy File I/O Causes Windows NT Server to Hang

Last reviewed: July 20, 1998
Article ID: Q189330

The information in this article applies to:
  • Microsoft Windows NT Server version 4.0
  • Microsoft Windows NT Server, Enterprise Edition version 4.0 - Microsoft Cluster Server

SYMPTOMS

The system stops responding (hangs) during heavy file I/O, such as multiple file copy sessions. The only option is to restart the computer.

MORE INFORMATION

Examination of the System process threads reveals the following cache manager related call stack:

   ChildEBP RetAddr  Args to Child
   f4047c04 801181ec 00000001 ntkrnlmp!KiSwapThread+0x1b1
   f4047c28 80101ebd f4047c78 ntkrnlmp!KeWaitForSingleObject+0x1b8
   f4047c8c 80219a55 80ce9f48 ntkrnlmp!CcCanIWrite+0x175
   f4047d30 8016f2b8 80ce9f48 Ntfs!NtfsCopyWriteA+0x50
   f4047de0 8013fa99 00000090 ntkrnlmp!NtWriteFile+0x3d2
   f4047de0 e12ef000 00000090 ntkrnlmp!KiSystemService+0xc9
   00000000 00000000 00000000 +0xe12ef000

Also, examination of the system locks will reveal this same thread.

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 4.0. We are researching this problem and will post additional information here in the Microsoft Knowledge Base as it becomes available.

Keywords          : kbbug4.00 kbfix4.00
Version           : WinNT:4.0
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: July 20, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.