Article ID: 172511 - View products that this article applies to.
This article was previously published under Q172511
This article has been archived. It is offered "as is" and will no longer be updated.
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
McAfee Anti-Virus software uses a filter driver. The presence of a filter driver requires system drivers to allocate additional stack space in I/O request packets (IRPs). An IRP in use by Services for Macintosh had insufficient space for insertion of filter driver stack information. The result was the STOP 0xA error message.
Windows NT 4.0To 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
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/NOTE: The above link is one path; it has been wrapped for readability.
Windows NT 3.51To resolve this problem, contact Microsoft Technical Support to obtain the following fix, or wait for the next Windows NT service pack.
Windows NT 4.0Microsoft 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.51Microsoft has confirmed this to be a problem in Windows NT version 3.51. A supported fix is now available, but has not been 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 Technical Support for more information.
The third-party products discussed here are manufactured by vendors independent 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 Microsoft Knowledge Base:
(http://support.microsoft.com/kb/166571/EN-US/ )Creating an SFM Volume on Large Partition Causes a Stop 0x24
(http://support.microsoft.com/kb/170956/EN-US/ )SFM Time and Date Stamp Change Copying Between Volumes Locally
(http://support.microsoft.com/kb/177644/EN-US/ )Commenting Macintosh File Changes Date and Time Stamp
(http://support.microsoft.com/kb/178364/EN-US/ )Macintosh Clients See Files on WinNT Server Constantly Moving
(http://support.microsoft.com/kb/180622/EN-US/ )STOP:0x0000001E with STATUS_INSUFFICIENT_RESOURCES in Sfmsrv.sys
(http://support.microsoft.com/kb/180716/EN-US/ )SFM Fails to Accept Associations with Two-Character Extensions
(http://support.microsoft.com/kb/180717/EN-US/ )SFM: File Date and Time Stamp Change with Get Info
(http://support.microsoft.com/kb/180718/EN-US/ )SFM: Disconnect Macintosh Clients before Dismounting Volume
(http://support.microsoft.com/kb/185722/EN-US/ )SFM Rebuilds Indexes upon Restarting of Windows NT
Contact us for more help
Connect with Answer Desk for expert help.