Event id 2017. The server was unable to allocate from the system nonpaged pool because the server reached the configured limit for nonpaged pool allocations
A local business upgraded their main PC to Windows 7 Pro, 64 bit, and shortly after, upgraded their main software suite.
Everything seemed to work OK, but after a few weeks, I started to get called about strange errors:
- Sometimes the backup would fail to copy backup logs from a second PC over the network
- Sometimes the second PC would just refuse to run the software suite.
The errors seem to point at a network outage, but after replacing the Ethernet cables, I was starting to suspect the ethernet hub.
Before committing to a hardware upgrade, which might or might not work, I decided to trawl through the windows event viewer, looking for any hints to the problem.
Sure enough, I noticed 2 error messages that started appearing soon after the software upgrade:
- Event Id 2017: The server was unable to allocate from the system nonpaged pool because the server reached the configured limit for nonpaged pool allocations
- Sessions circular kernel contact logger failed to start with the following error: 0xc0000035
I quickly find the error can be fixed by changing 2 registry keys:
HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\LargeSystemCache = 1
HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\Size = 3
It seems like Microsoft are up to their old tricks (like with XP), where less expensive versions of their OSare artificially hobbled by network limits, so that you will fork out more money for a server OS.