DOCUMENT:Q172511 TITLE :Stop 0x0000000A w/ Services for Macintosh & McAfee Anti-Virus PRODUCT :Microsoft Windows NT PROD/VER:4.00 OPER/SYS:WINDOWS KEYWORDS:kbbug3.51 kbbug4.00 kbfix4.00 kbfile -------------------------------------------------------------------------- The information in this article applies to: - Microsoft Windows NT Server versions 3.51 and 4.0 -------------------------------------------------------------------------- SYMPTOMS ======== When a system runs Services for Macintosh and McAfee Anti-Virus software, you may receive a blue screen STOP 0xA error similar to the following: STOP: 0x0000000a (0x00000004, 0x00000002, 0x00000001, 0x8010b262) CAUSE ===== 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. RESOLUTION ========== Windows NT 4.0 -------------- To resolve this problem, contact Microsoft Technical Support to obtain the following fix, or wait for the next Windows NT service pack. This fix should have the following time stamp: 02/03/98 02:10p 130,352 Sfmsrv.sys (Intel) 02/03/98 03:07p 234,064 Sfmsrv.sys (Alpha) This hotfix has been posted to the following Internet location: 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.51 --------------- To resolve this problem, contact Microsoft Technical Support to obtain the following fix, or wait for the next Windows NT service pack. STATUS ====== Windows NT 4.0 -------------- Microsoft has confirmed this to be a problem in Windows NT version 4.0. 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. Windows NT 3.51 --------------- Microsoft 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. 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: ARTICLE-ID: Q166571 TITLE : Creating an SFM Volume on Large Partition Causes a Stop 0x24 ARTICLE-ID: Q170956 TITLE : SFM Time and Date Stamp Change Copying Between Volumes Locally ARTICLE-ID: Q177644 TITLE : Commenting Macintosh File Changes Date and Time Stamp ARTICLE-ID: Q178364 TITLE : Macintosh Clients See Files on WinNT Server Constantly Moving ARTICLE-ID: Q180622 TITLE : STOP:0x0000001E with STATUS_INSUFFICIENT_RESOURCES in Sfmsrv.sys ARTICLE-ID: Q180716 TITLE : SFM Fails to Accept Associations with Two-Character Extensions ARTICLE-ID: Q180717 TITLE : SFM: File Date and Time Stamp Change with Get Info ARTICLE-ID: Q180718 TITLE : SFM: Disconnect Macintosh Clients before Dismounting Volume ARTICLE-ID: Q185722 TITLE : SFM Rebuilds Indexes upon Restarting of Windows NT Additional query words: 4.00 3.51 sfm ============================================================================ 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.