Article ID: 888928 - View products that this article applies to.
After you install McAfee VirusScan Enterprise Version 8.0i, your Microsoft Windows Server 2003-based or Microsoft Windows 2000-based computer may occasionally stop responding. You may receive error messages that are similar to the following in the System log:
Event ID 2019
Event Type: Error
Event Source: Srv
Event Category: None
Event ID: 2019
The server was unable to allocate from the system nonpaged pool because the pool was empty.
For more information, see Help and Support Center at http://support.microsoft.com.
This problem occurs because a leak occurs in the system non-paged memory pool. The pool tags that indicate the location of the memory leak are McOp and McFN.
To resolve this problem, contact Network Associates to obtain the Patch 7 for McAfee VirusScan Enterprise 8.0i. For additional information, visit the following McAfee Web site to see the McAfee Knowledge Base Article Solution ID KB45505:
https://knowledge.mcafee.com/SupportSite/search.do?cmd=displayKC&docType=kc&externalId=KB45505&sliceId=SAL_Public&dialogID=566275&stateId=0%200%20562644Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
This memory leak can be monitored by using the Memory Pool Monitor utility, Poolmon.exe, and the GFlags tool. These utilities are available in the \Support\Tools folder of the Windows Server 2003 CD.
For additional information about how to use the Memory Pool Monitor, click the following article number to view the article in the Microsoft Knowledge Base:
177415The third-party products that are discussed in this article are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.
(http://support.microsoft.com/kb/177415/ )How to use Memory Pool Monitor (Poolmon.exe) to troubleshoot kernel mode memory leaks
Article ID: 888928 - Last Review: February 22, 2007 - Revision: 4.3
Contact us for more help
Connect with Answer Desk for expert help.