Paged kernel memory windows xp

Surely you have read the myths and legends about this feature and how to use it appropriately. You can certainly make the adjustment and hopefully do some timing measurements to see if things get better or worse and it would be interesting to know what happens. After you conduct some before and after benchmarking performance tests to see what effect it has on your system, get back to us with the results.

If you can pinpoint a specific issue you are having and why you think this might help, let us know about that too. Was this reply helpful? Yes No. Sorry this didn't help. Thanks for your feedback. I've followed the instructions from the link and it does not work at all.

So, in. I've set the key DisablePagingExecutive entry to 1, but with no result at all. Note that the Base value in the key is Hexadecimal, so not Decimal. In the Taskmanager it is clear that the kernel keeps on being paged out to disk all the time and only a smaller portion of the kernel stays in RAM, even when no applications are running. There is another very peculiar thing though.

Alongside the folder Hi, I've followed the instructions from the link and it does not work at all. That inherently caps the upper bound for nonpaged pool or any type of system virtual memory at 2GB, but it has to share that space with other types of resources such as the kernel itself, device drivers, system Page Table Entries PTEs , and cached file views. Prior to Vista, the memory manager on bit Windows calculates how much address space to assign each type at boot time.

Its formulas takes into account various factors, the main one being the amount of physical memory on the system. Paged pool limits are therefore primarily dictated by the amount of system address space the memory manager assigns to paged pool, as well as the system commit limit. On bit Windows XP, the limit is calculated based on how much address space is assigned other resources, most notably system PTEs, with an upper limit of MB.

Since bit Windows Vista and later have dynamic kernel address space, they simply set the limit to 2GB. Paged pool will therefore run out either when the system address space is full or the system commit limit is reached. Here again is the screenshot from the bit Windows XP system, which shows that the paged pool limit is exactly four times that of nonpaged pool:.

Because the kernel pools are used by almost every kernel operation, exhausting them can lead to unpredictable results. If you want to witness first hand how a system behaves when pool runs low, use the Notmyfault tool. It has options that cause it to leak either nonpaged or paged pool in the increment that you specify.

After nonpaged pool ran out on a bit Windows XP system, for example, trying to launch a command prompt resulted in this dialog:. On a bit Windows Server system where I already had a command prompt running, even simple operations like changing the current directory and directory listings started to fail after nonpaged pool was exhausted:.

On one test system, I eventually saw this error message indicating that data had potentially been lost. See here for more info. Also on p22 of this we see how to do this. Finally this discuss here we see that the data segment should be non pagagable by default. You can also use the device extension when you call IoCreateDevice , it is always allocated from NonPaged memory.

Another good answer that I find is: "Nonpaged pool is kernel memory which can't be paged out into the pagefile when Windows runs out of free physical memory. It is used by drivers to allocate memory which they need. How are we doing? Please help us improve Stack Overflow. Take our short survey. Stack Overflow for Teams — Collaborate and share knowledge with a private group.

Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Paged pool memory or Nonpaged pool memory?? Asked 12 years, 8 months ago. Active 2 years, 10 months ago. Viewed 9k times.