Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
Windows NT 4.0 Traps with a Stop 0x00000024 in NTFS or Stop 0x0000000a
Article ID: 180648 - View products that this article applies to.
This article was previously published under Q180648
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. For example:
Stop 0x00000024 (0x001901f9, parameter, parameter, parameter)
Ntfs.sys releases the file object when accessing a file with a large number of security descriptors.
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/152734/EN-US/ )How to Obtain the Latest Windows NT 4.0 Service Pack
On uniprocessor Compaq computers running Compaq's System Manager driver, Sysmgmt.sys, the system may fail to reboot after you install a post-SP3 Hotfix Ntoskrnl.exe dated 11/20/97 or later. The system will stop responding (hang) at the blue screen listing the Windows NT version and service pack information. Obtain the latest version of Sysmgmt.sys from Compaq to resolve this problem.
For additional information, please see the following article in the Microsoft Knowledge Base:
TITLE : Windows NT 4.0 Fails to Start on a Uniprocessor Compaq
A hotfix that addresses this problem in Windows NT 4.0 Terminal Server is currently available.
Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.
Article ID: 180648 - Last Review: November 1, 2006 - Revision: 1.3