2

We have a windows server 2003 R2 machine, 4GB RAM, 32 bit.

The paged pool limit is set to 354 MB. We have been having crashes twice in the last month and it is due to event ID : 2020 - The server was unable to allocate paged pool memory. We also confirmed the same using pagemon and other tools.

The question that I have is, is it advisable to increase the paged pool size (via setting in registry). I read a lot about these to be system set limits and advised not to change. We are on a 32 bit OS for now and hence I am thinking increasing the limit set is not a bad idea. But I am not very clear the consequences of this and is this something that is recommended ?

Thanks Mani

Mani
  • 121
  • 2
  • 8
  • Wouldn't it be better to find and resolve the cause of the paged pool exhaustion? – joeqwerty Jul 31 '13 at 16:51
  • That's what we are attempting now. But I am curious to understand why not attempt to increase the limit. – Mani Jul 31 '13 at 17:01
  • 2
    Yes, you can increase it *slightly*. Something like 650MB is the limit on 32bit Server 2003. PS - Get off of 32bit Server 2003. – Ryan Ries Jul 31 '13 at 17:44

1 Answers1

4

You're on a Windows OS that is 10 years old. If you can, move to a 64-bit platform and/or fix the application/driver/whatever that is causing it. Have you identified what it is? If not, here's some help on that score.

If not, you're just trying to deal with the situation as-is. You can set it; it might not be able to be set much higher than you've already got. In fact, your OS might already be configured for that to be dynamic and maybe 354 MB is the max you'll ever get.

Also, if it's the kernel or a driver leaking the pool, it will always end up running out and you need to start doing prophylactic system reboots or fixing the root cause.

mfinni
  • 36,144
  • 4
  • 53
  • 86
  • Thanks. Yes the link points to the choices. But I take your point on the 32 bit machines, I am fighting to get it replaced but we know how cost saving companies plan work ! – Mani Aug 01 '13 at 08:30