• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 727
  • Last Modified:

Need help reading poolmon due - event id 2019

Approx. every 2 weeks into the uptime of my server I start to get memory leaks.  I noticed the problem shortly after installing a new app so I feel that most likely it is causing the memory leaks.  I'm running poolmon to watch which tags are paged and which are non-paged.  I really don't know what I'm looking at and need help reading the data that is being displayed within poolmon.  As I understand I can do a search in the \windows\system32\drivers folder for *.sys.  This will return a list of 3rd party tags, or, possible tags for some of these are false positives.  I've contacted the manufacturer of the software that I just recently installed to see if they have a .sys file in the \windows\system32\drivers folder.  This will let me know which tag to look for.  

How do I know which should be paged, and what should be is non-paged?  I have the tags sorted from largest to smallest.  And I know how to toggle between paged and non-pages columns.  Should a certain tag only get so large before releasing the memory?!  I just don't know what to look for.
0
gopher_49
Asked:
gopher_49
  • 2
1 Solution
 
HyonyCommented:
As per Microsoft: "Nonpaged pool pages cannot be pages out to the paging file, but instead remain in main memory as long as they are allocated. An application is probably incorrectly making system calls and using up all allocated nonpaged pool. You might also see the following error on a local or remote system: Not enough storage available to process this command". See http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Windows%20Operating%20System&ProdVer=5.2&EvtID=2019&EvtSrc=NCP%20Server&LCID=1033 for more information.  

If still not solve, plz tell me!
0
 
gopher_49Author Commented:
I give this a shot today.  I recently installed a program that had it's own pre-configured MSDE instance.  It was set to use dynamic memory allocation.  I changed it to be static and will now only allocated up to 1.2 gigs of memory.  The memory leaks have gone away since then, however, I will follow the instructions listed in your link to verify.

thanks.
0
 
gopher_49Author Commented:
Hyony,

I followed the instructions in the link and I was able to determine that the memory leak is no longer occuring.  It quit when I changed the dynamic memory allocation in MSDE to fixed.

thanks.
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now