Windows NT 4.0 Traps with a Stop 0x24 or Stop 0xA

Last reviewed: February 26, 1998
Article ID: Q180648
The information in this article applies to:
  • Microsoft Windows NT Workstation version 4.0
  • Microsoft Windows NT Server version 4.0

SYMPTOMS

Under heavy file I/O, such as during backup or heavy file sharing, Windows NT 4.0 will display a blue screen stop message with a STOP 0x00000024 in NTFS.sys or a Stop 0x0000000A in NTOSKRNL.exe.

CAUSE

Ntfs.sys releases the file object when accessing a file with a large number of security descriptors.

RESOLUTION

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

This fix should have the following time stamp:

   10/21/97  12:05a                51,872 Hal.dll (Intel)
   10/21/97  12:05a                48,288 Hal486c.dll (Intel)
   01/05/98  04:08p                66,336 Halapic.dll (Intel)
   10/21/97  12:05a                46,048 Halast.dll (Intel)
   10/21/97  12:05a                82,144 Halcbus.dll (Intel)
   10/21/97  12:05a                80,256 Halcbusm.dll (Intel)
   10/21/97  12:05a                46,336 Halmca.dll (Intel)
   01/05/98  04:08p                68,448 Halmps.dll (Intel)
   01/05/98  04:08p                67,488 Halmpsm.dll (Intel)
   10/21/97  12:06a                78,944 Halncr.dll (Intel)
   10/21/97  12:05a                40,128 Haloli.dll (Intel)
   10/21/97  12:05a                56,512 Halsp.dll (Intel)
   10/21/97  12:06a                40,672 Halwyse7.dll (Intel)
   01/28/98  02:00p               360,560 Ntfs.sys (Intel)
   01/26/98  03:42p               938,880 Ntkrnlmp.exe (Intel)
   01/26/98  03:41p               918,976 Ntoskrnl.exe (Intel)

   01/28/98  02:02p                60,224 Hal.dll (Alpha)
   01/27/98  03:58p                60,224 Hal0jens.dll (Alpha)
   01/27/98  03:58p                81,088 Halalcor.dll (Alpha)
   01/27/98  04:00p                82,528 Halalp.dll (Alpha)
   01/27/98  03:59p                75,968 Halavant.dll (Alpha)
   01/27/98  03:59p                92,576 Haleb164.dll (Alpha)
   01/27/98  03:59p                82,400 Haleb64p.dll (Alpha)
   01/27/98  04:00p                89,824 Halflex.dll (Alpha)
   01/27/98  04:00p                89,568 Halgammp.dll (Alpha)
   01/27/98  03:59p                97,824 Hallego.dll (Alpha)
   01/27/98  03:59p                85,024 Hallx3.dll (Alpha)
   01/27/98  03:59p                79,808 Halmikas.dll (Alpha)
   01/27/98  03:59p                72,256 Halnonme.dll (Alpha)
   01/27/98  03:59p                95,776 Halpinna.dll (Alpha)
   01/27/98  03:59p                71,904 Halqs.dll (Alpha)
   01/27/98  03:59p                99,680 Halrawmp.dll (Alpha)
   01/27/98  03:59p                85,248 Halsabmp.dll (Alpha)
   01/27/98  04:00p                92,320 Haltimbr.dll (Alpha)
   01/27/98  04:00p                89,568 Halxl.dll (Alpha)
   01/28/98  01:57p               555,728 Ntfs.sys (Alpha)
   01/26/98  03:40p             1,399,872 Ntkrnlmp.exe (Alpha)
   01/26/98  03:39p             1,372,416 Ntoskrnl.exe (Alpha)

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 4.0. A supported fix is now available, but is not 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 Product Support Services for more information.

Keywords          : kbbug4.00 kbfix4.00 NTSrvWkst ntstop
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: February 26, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.