STOP: 0x0000001E with STATUS_INSUFFICIENT_RESOURCES with More Than 800,000 Files on a Macintosh Volume

View products that this article applies to.

This article was previously published under Q180622

Expand all | Collapse all

SYMPTOMS

A STOP: 0x0000001E error message may happen on a computer running both Windows NT Server and Services for Macintosh with a Macintosh volume with more than 800,000 files. The arguments passed to the STOP screen may look like

STOP: 0x0000001E (c000009a, 8010a77f, 0000298c, 80135f6c)

where c000009a is mapped to the status code of STATUS_INSUFFICIENT_RESOURCES.

Back to the top

CAUSE

The Windows NT kernel is running out of paged-pool memory. When Windows NT starts up, it calculates the amount of paged-pool memory available to the kernel based on the amount of physical RAM in the system. The maximum this value can be is 192 MB. If the kernel allocates all of its allotted paged- pool memory, it will not be able to perform many tasks and will instead return a STATUS_INSUFFICIENT_RESOURCES (0xC000009A).

Back to the top

RESOLUTION

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:

152734 (http://support.microsoft.com/kb/152734/EN-US/ ) How to Obtain the Latest Windows NT 4.0 Service Pack

For your convenience, the English version of this post-SP3 hotfix has been posted to the following Internet location. However, Microsoft recommends that you install Windows NT 4.0 Service Pack 4 to correct this problem.

ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/NT40/hotfixes-postSP3/sfm-fix/ (ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/NT40/hotfixes-postSP3/sfm-fix/)

Back to the top

STATUS

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.

Back to the top

MORE INFORMATION

For more information, please see the following articles in the Microsoft Knowledge Base:

ARTICLE-ID: 166571 (http://support.microsoft.com/kb/166571/EN-US/ )
TITLE : Creating an SFM Volume on Large Partition Causes a Stop 0x24

ARTICLE-ID: 170956 (http://support.microsoft.com/kb/170956/EN-US/ )
TITLE : SFM Time and Date Stamp Change Copying Between Volumes Locally

ARTICLE-ID: 172511 (http://support.microsoft.com/kb/172511/EN-US/ )
TITLE : Stop 0x0000000A w/ Services for Macintosh & McAfee Anti-Virus

ARTICLE-ID: 177644 (http://support.microsoft.com/kb/177644/EN-US/ )
TITLE : Commenting Macintosh File Changes Date and Time Stamp

ARTICLE-ID: 178364 (http://support.microsoft.com/kb/178364/EN-US/ )
TITLE : Macintosh Clients See Files on WinNT Server Constantly Moving

ARTICLE-ID: 180716 (http://support.microsoft.com/kb/180716/EN-US/ )
TITLE : SFM Fails to Accept Associations with Two-Character Extensions

ARTICLE-ID: 180717 (http://support.microsoft.com/kb/180717/EN-US/ )
TITLE : SFM: File Date and Time Stamp Change with Get Info

ARTICLE-ID: 180718 (http://support.microsoft.com/kb/180718/EN-US/ )
TITLE : SFM: Disconnect Macintosh Clients before Dismounting Volume

ARTICLE-ID: 185722 (http://support.microsoft.com/kb/185722/EN-US/ )
TITLE : SFM Rebuilds Indexes upon Restarting of Windows NT

Back to the top