I think the high memory usage issue has been fixed, but I will keep an eye on it for several more days to see if it will come back. With several applications running, Task Manager shows about 30% RAM usage: Then I launched RAMMap and the result confirmed the non-paged pool is not high.
#POOLMON.EXE WDK DRIVERS#
The result shows no abnormal pool tag after the network drivers were updated. Run poolmon by going to the folder where WDK is installed, go to Tools (or C: Program Files (x86) Windows Kits 8.1 Tools 圆4) and click poolmon.exe.
#POOLMON.EXE WDK INSTALL#
I reboot my laptop after installing all available updates, then launched poolmon again: Poolmon.exe Windows Server 2012 R2 Install the Windows WDK, run poolmon, sort it via P after pool type so that non paged is on top and via B after bytes to see the tag which uses most memory. Surely enough, HP Support Assistant detected there is new version Bluetooth driver (yes, my laptop has Bluetooth).
#POOLMON.EXE WDK UPDATE#
I went to HP web site and updated my network drivers, then I remembered my laptop comes with HP Support Assistant which can detect update automatically, so I launched this software to see if I could find something helpful. Ndis.sys is related to network adapters, so it tells me that some network adapter is causing the memory leak. In this case, ndis.sys is using NDnd pool tag. The command may generate lots of gibberish in the window, but the first line usually tells you which driver uses the pool tag. While keeping poolmon running, open another Command Prompt with admin rights and type in the following command: findstr /s NDnd *.sys you can use the c switch on the 32bit version of Poolmon that comes with the WDK. Now let’s find out which driver uses the bad pool tag. Poolmon Columns Column Explanation Tag Fourbyte tag given to the pool.
poolmon -b -pįrom the poolmon result we can see that the pool tag “NDnd” is causing the most memory allocation, about 400MB!ģ. You can also add “-p” to the command to sort the result by pool and non pool as suggested in drigo’s comment below. Then launch a Command Prompt with administrator rights, then find the directory where poolmon.exe is located, and type in the following command to launch poolmon: poolmon -b
Poolmon.exe is under C:\Program Files (x86)\Windows Kits\8.1\Tools\圆4 (for my 64-bit Windows 8.1). By default, WDK 8.1 will be installed under C:\Program Files (x86)\Windows Kits\. However, Ndu.sys does not seem to be the root cause of my issue because the high memory usage issue came back again yesterday, and eventually my computer crashed with a blue screen shown below.Īfter some more searches, I decided to follow the suggestion in a post from Windows 8 Forum to use Poolmon to find out which driver is causing memory leak.Ģ. In my previous post regarding the high memory usage issue with my new HP Envy laptop, which runs on Windows 8.1 Pro with 8GB RAM, I disabled Ndu.sys which, according to some people’s experience, was said to be the culprit.
0 kommentar(er)
