Increase the
Windows PagedPoolSize value to allow a larger paged pool. A setting of 0xFFFFFFFF will allocate the maximum Paged Pool in lieu of other resources to the computer.
Suggestions from Microsoft:1. Use 0xFFFFFFFF for the
PagedPoolSize which is the maximum.
And the default
PoolUsageMaximum is 80, which means the Memory Manager trims pool memory at 80%.
2. Upgrading to a 64 bit platform will give a lot more pool resources (up to 128 GB instead of 256MB Non-paged and 470MB Paged Pool). The following Microsoft Article provides further information about pool resources on x64:
3. Examine PERFMON metrics
Perfmon will show that the system is critically low on Pool Paged memory with less than 20% available.
It may not yet have generated a 2020 / 2021 event but instead error 1450. The following Microsoft Article provides further information about these events:
Extract: 317249
Other components of the operating system may not work and may generate error messages that report a status code of 1450 in the data section of their event log message. That is, "Insufficient System Resources."
These events may be found in the System event log or in the Application event log. These messages may apply to the issue that is described in this article only if the underlying event was a connection to the server service. However, this fact is not easily determined. For example, there is Event ID 1055 that is generated by CLUSSVC. This event is from the cluster service that usually reports a failed connection to the server service.
Based on the symptoms I have seen in this case I would encourage the customer to move to x64. It is not possible for me now to see if it will delay the issue, however it is not very likely this will happen. Only with a memory dump we are able to get more grip on what is actually happening. Based on the Perfmon only, a x64 OS will relief the system. Fine tuning the current system is possible but may be a lengthy process.
