Stop 0x0000000A with Services for Macintosh and McAfee Anti-Virus

This article was previously published under Q172511
This article has been archived. It is offered "as is" and will no longer be updated.
Symptoms
When a system runs Services for Macintosh and McAfee Anti-Virus software,you may receive a blue screen STOP 0xA error or errors similar to the following:
STOP: 0x0000000a (0x00000004, 0x00000002, 0x00000001, 0x8010b262)
STOP: 0x0000000a (0x00000004 0x00000002 0x00000001 0x8010b262)IRQL_NOT_LESS_OR_EQUAL
STOP: 0x00000024 (0x001901f9 0xf5c27c0c 0xf5c27a48 0x8010b260)NTFS_FILE_SYSTEM
Cause
McAfee Anti-Virus software uses a filter driver. The presence of a filterdriver requires system drivers to allocate additional stack space in I/Orequest packets (IRPs). An IRP in use by Services for Macintosh hadinsufficient space for insertion of filter driver stack information. Theresult was the STOP 0xA error message.
Resolution

Windows NT 4.0

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 theMicrosoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack



For your convenience, the English version of this post-SP3 hotfix has beenposted to the following Internet location. However, Microsoft recommendsthat you install Windows NT 4.0 Service Pack 4 to correct this problem.NOTE: The above link is one path; it has been wrapped for readability.

Windows NT 3.51

To resolve this problem, contact Microsoft Technical Support to obtain thefollowing fix, or wait for the next Windows NT service pack.
Status

Windows NT 4.0

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.

Windows NT 3.51

Microsoft has confirmed this to be a problem in Windows NT version 3.51. Asupported fix is now available, but has not been fully regression-testedand should be applied only to systems experiencing this specific problem.Unless you are severely impacted by this specific problem, Microsoftrecommends that you wait for the next Service Pack that contains this fix.Contact Microsoft Technical Support for more information.
More information
The third-party products discussed here are manufactured by vendorsindependent of Microsoft; we make no warranty, implied or otherwise,regarding these products' performance or reliability.

For more information, please see the following articles in the MicrosoftKnowledge Base:
166571 Creating an SFM Volume on Large Partition Causes a Stop 0x24

170956 SFM Time and Date Stamp Change Copying Between Volumes Locally

177644 Commenting Macintosh File Changes Date and Time Stamp

178364 Macintosh Clients See Files on WinNT Server Constantly Moving

180622 STOP:0x0000001E with STATUS_INSUFFICIENT_RESOURCES in Sfmsrv.sys

180716 SFM Fails to Accept Associations with Two-Character Extensions

180717 SFM: File Date and Time Stamp Change with Get Info

180718 SFM: Disconnect Macintosh Clients before Dismounting Volume

185722 SFM Rebuilds Indexes upon Restarting of Windows NT
sfm
Properties

Article ID: 172511 - Last Review: 10/26/2013 03:23:00 - Revision: 3.0

Microsoft Windows NT Server 3.51, Microsoft Windows NT Server 4.0 Standard Edition

  • kbnosurvey kbarchive kbhotfixserver kbqfe kb3rdparty kbbug kbfix KB172511
Feedback