Memory Leak, Pool Nonpaged Bytes Error eventid 2019

Hi all.
    My System WINDOWS 2000 SP4 (Domain Controller, File Server)
    On last Week MyServer is error eventid 2019 - The server was unable to allocate from the system nonpaged pool because the pool was empty.
    when i restart server, it's ok but on 1 day it's down 4-5 time.

   SOLUTIONS Attempted:
        Changed Reg. setting to start memory clean up of PoolUsageMax at 40% instead of 80%.
        See MS article:
        I reverted PagedPoolSize to 0 from suggested ffffffff (4,294,967,295), because multiple errors.

   who any suggestions to me.
Who is Participating?
Zaheer IqbalConnect With a Mentor Technical Assurance & ImplementationCommented:
bcpprnAuthor Commented:
Now I use poolmon for monitor memory , i found tag Ddk used memory 40,000,000 bytes in nonpaged and every hour it's use more than.
   What is tag Ddk ?
Zaheer IqbalTechnical Assurance & ImplementationCommented:
At two different jobs now I have had this problem with antivirus agents on the server. One was Symantec about two years ago and just last week it happened again with the McAfee Enterprise agent. If you are running a version of VirusScan Enterprise less than version 8.0 PATCH 7, you will be suseptible to a nonpaged memory pool error which will render the server useless until you reboot it. Where I work, it only seemed to affect servers with high volume printer traffic. You can find your version information by launching VirusScan Enterprise and then clicking the About menu item. Patches will be listed on the last line of the information. If you are on version 7.0.0, upgrade to 8.0.0 and apply patch 10, which was the latest at the time I wrote this...
Here is the Microsoft KB article for the McAfee memory leak:;en-us;888928
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.