In some instances you possibly can see some troubles with reminiscence overflow on computer systems and servers working Windows associated to the leak of a system driver that shops its information in the non-paged reminiscence. Non-paged reminiscence pool is the a part of the pc’s RAM, which is utilized by the kernel and the drivers of the operation system. Non-paged pool is rarely swapped to the disk (to the paging file), it’s at all times saved solely in the bodily reminiscence.
You can see the present measurement of the non-paged reminiscence in the Memory part of the Performance tab in the Task Manager. The screenshot beneath exhibits that the majority reminiscence of the server is busy, and essentially the most a part of it’s occupied by the non-paged pool four.2GB. Normally, the scale of the non-paged pool not often exceeds 200-400MB. This often signifies that there’s a reminiscence leak in some system part or driver.
With this reminiscence overflow downside on the server, the next messages might seem in the occasion log:
The server was unable to allocate from the system Non-Paged pool as a result of the pool was empty.
In most instances, the rationale of the reminiscence leak described above is a few issues with the third-party drivers put in in the system. As a rule, these are community drivers. Please, take note of the pool habits when downloading giant recordsdata (it’s more likely to develop quick as much as 128GB or 75% of bodily reminiscence in x64 techniques). Only the Windows reboot helps to wash up the pool. It could also be acceptable for a house laptop, however you must discover a higher resolution for a server working 24/7.
Install the Latest Versions of Network Adapter Drivers
Try to obtain and set up the latest driver variations to your community adapters from the seller’s web site.
If the automated driver replace is enabled, be sure that the issues didn’t seem after the set up of the brand new drivers. Try to roll again to the earlier driver model and see if the issue persists. If the issue is solved, disable automated driver replace.
Disable the Network Data Usage Driver
Quite usually the incompatibility of the Network Data Usage (NDU) and community adapter drivers could be the motive of the reminiscence leak in the non-paged pool. This service could be disabled with out a lot lack of Windows performance.
The service could be stopped utilizing this command:
sc config NDU begin= disabled
Or by the registry:
- Open the Registry Editor (regedit.exe);
- Go to registry key HKEY_LOCAL_MACHINESYSTEMControlSet001ServicesNdu;
- Change the worth of the Start parameter to four.
After making modifications it’s essential to restart your laptop.
Disable the Hyper-V Role
In some instances the put in Hyper-V position outcomes in reminiscence leak to the non-paged pool. If you don’t want this position, we suggest to disable it.
Using PoolMon to Find a Kernel-Mode Memory Leak
If the strategies described above didn’t assist, you possibly can attempt to discover out, which driver causes the reminiscence leak to the non-paged pool utilizing a console software Poolmoon.exe (included in Windows Driver Kit – WDK). Download and set up WDK to your Windows model from Microsoft web site. Then begin Poolmon.exe (in case of WDK for Windows 10, the software is situated in C:Program Files (x86)Windows Kits10Tools folder).
After you’ve gotten began the software, press P. In the second column the tags of processes utilizing non-paged reminiscence will likely be left (Nonp attribute), then kind the drivers listing by the Bytes column (by urgent B).
You can see that in our instance the drivers with Nr22, ConT and smNp tags are utilizing essentially the most a part of RAM in the non-paged pool.
You can discover the precise driver recordsdata associated to those processes utilizing the next instructions:
findstr /m /l /s Nr22 %Systemroot%System32drivers*.sys
findstr /m /l /s ConT %Systemroot%System32drivers*.sys
findstr /m /l /s smNp %Systemroot%System32drivers*.sys
So we’ve got acquired the listing of driver recordsdata which will trigger the issue. Now you need to decide what drivers and system elements these recordsdata confer with by their names. To do it, you need to use sigcheck by Sysinternals.
The software returns the title, description and model of the motive force or Windows part.
Now you possibly can attempt to uninstall/replace/reinstall the issue driver or service.
This information is relevant each for Windows Server 2008/2012R2/2016, in addition to for desktop Windows 10, eight.1 and seven.