Author: MastoidMan
Subject: RamMap - Nonpaged Pool
Posted: 07 August 2013 at 8:24pm
The biggest nonpaged pooltag is the MirD, which is the kernel dump mirror, or something like that. It's size was basically the entire memory that was in use then I ran the dump. I'm not sure how I can get into that segment to dig to the next level.
Edited by MastoidMan - 18 hours 26 minutes ago at 8:34pm
Subject: RamMap - Nonpaged Pool
Posted: 07 August 2013 at 8:24pm
The biggest nonpaged pooltag is the MirD, which is the kernel dump mirror, or something like that. It's size was basically the entire memory that was in use then I ran the dump. I'm not sure how I can get into that segment to dig to the next level.
Here's what part of the rub is. The system makes this big huge nonpaged pool, but nothing ever shows to actually use a whole lot of it. It's as if the system looks, sees the 32GB of RAM, allocates a huge portion (not maxed) to be used, but never frees it up for use. It's just sitting there in case I need it. I never approach the max of the machine, so I never do. I'd probably be better off yanking my sticksout and replacing them with 2gb sticks X 4.
That's what I suspect, anyhow. I think we had a couple leaks to deal with early on, but since then it seems to be behaving.
The other comment which I think I need to think about is at the very beginning of an article that I cannot find right now, but was written by one of the sysinternal founder creator types. He mentioned that memory manager or whatever creates the nonpaged pool will create a bigger one if there is an excess of interrupts and DPCs. I'm not sure what is excessive. I run at 0.01 - 0.02 CPU most of the time on interrupts. Maybe I have an issue there? Is that a lot, considering it's a percentage of a very powerful machine?
EDIT: If the nonpage pooled is based off algorithm and otherwise doing it's job, given my excesses of the machine, perhaps circumventing the algorithm is the step needed? Alternatively, if I knew what the LiveKD did during it's big dump that dropped the nonpaged pool down .80GB, if it's a command-line action and is otherwise a safe thing to do, I could create a bat file and point to it on start-up. I certainly would not want to run a 15 minute dump on start-up, but a 10-120 second process is just fine if it works. Just a thought. :)
Edited by MastoidMan - 18 hours 26 minutes ago at 8:34pm