![poolmon.exe for windows 10 64 bit poolmon.exe for windows 10 64 bit](https://latestuploads.net/wp-content/uploads/2017/08/DVDFab-10-Free-Download-Loader.jpg)
- #Poolmon.exe for windows 10 64 bit install#
- #Poolmon.exe for windows 10 64 bit drivers#
- #Poolmon.exe for windows 10 64 bit update#
- #Poolmon.exe for windows 10 64 bit driver#
- #Poolmon.exe for windows 10 64 bit 32 bit#
Knowing that such a simple act as starting word could trigger tens of thousands of registry operations, I dare not think about what happens when the system boots and a user tries to open his profile.įurther analysis identified the following registry keys (and their subkeys) to be the culprits: What happens is that every operation trying to do something in the registry that would require the HKLM software hive to grow a bit fails miserably. This is usually not a problem, as most registry hives can be measured in tens of megabytes, not thousands. Dangerously because the fixed limit for all registry hives except system is 2048MB. A quick look in the corresponding folder on the servers revealed that the software hive was dangerously close to 2048MB on the affected servers. I concluded it had to be something else asking the kernel to reserve memory, but what? It took a lot of googling and asking around to identify it, and finally it was a developer who put me on the right track: CM is Configuration Manager, which is another name for the registry or at least registry access related. Of course, finding a kernel leak in Windows would be fun, but I seriously doubted this to be the issue. Sadly it pointed back at the kernel itself: Russinovich and used the strings.exe from Sysinternals to try to identify the culprit. Process explorer is able to identify the current limit, but that requires symbols and I didn’t have the time or energy to get the necessary firewall and proxy exceptions approved to download symbols on my servers.
![poolmon.exe for windows 10 64 bit poolmon.exe for windows 10 64 bit](https://4.bp.blogspot.com/-y8-uHy0CJm0/WDhE6PGcscI/AAAAAAAAAWQ/5XSxkRsXznc-pkg2f4WeuLcRTQvYKAIUgCLcB/s1600/10-1-Inch-OGS-2560-1600-Chuwi-HIBook-Pro-font-b-Tablet-b-font-PC-Dual.jpg)
Research shows that in theory the limit is something like 50% of the physical RAM or 128GB, none of which have been reached on this particular server containing 256gigs of RAM. But has it reached a limit? There seemed to be a 2048MB roof that was never reached, until I checked another server were the paged pool was way beyond 3000MB.
![poolmon.exe for windows 10 64 bit poolmon.exe for windows 10 64 bit](https://online.aspirecig.com/bmz_cache/5/5bc2d039865b8bbc22f0ba5e4a447303.image.500x359.jpg)
Running poolmon on one of the troubled servers gave this result:įor more information on tracing pool leaks, see this post on Mark Russinovich’s blog: ĬM31 seems to be the tag using all my paged pool memory. (I won’t bother listing a URL to this, as MS changes the location every 6 months.
#Poolmon.exe for windows 10 64 bit driver#
I spent half a day downloading the Windows Driver Development Kit (WDK) into our environment to get a hold of Poolmon.exe. I started with one server with problems, but so far I have detected the issue to some degree on all servers running MSSQL 2012 SP1.
#Poolmon.exe for windows 10 64 bit drivers#
I quickly established that installing the drivers didn’t help, but I still believe that the missing drivers was somehow related to which servers ended up with the biggest problems. They were all the same make and model, only a couple of weeks old, and they differed only in RAM. In the beginning I got sidetracked by the fact that all of the servers experiencing the problem were missing the correct chipset drivers. The bloated kernel memory pool seemed to me like the best bet, so I started looking closer at that problem.
#Poolmon.exe for windows 10 64 bit 32 bit#
NET Runtime Optimization, failed to compile something in the 32 bit SQL server installation folder: Normally for SQL servers of this size (128-256G RAM) this metric is somewhere between 256MB and 512MB, servers experiencing this problem have a value of 1024-3000MB: The Kernel memory paged pool is bloated.It seems to be attacking the entire server all at once, and the only common denominator is they are all running MS SQL 2012 SP1. It’s as if they have contracted ebola or the swine flu or some other strange virus. Yet the server fails, and a couple of days later another one goes down with the same symptoms. But a couple of days before everything was hunky-dory, and you are absolutely 100% sure nothing has changed since then.
#Poolmon.exe for windows 10 64 bit update#
Maybe random services start to fail, Windows Update refuses to apply updates, and if you boot the server it might refuse to start SQL server at all or just greet you with a friendly BSOD. Maybe you are unable to start management studio, or if you’re really unfortunate you can’t log in to the server at all.
#Poolmon.exe for windows 10 64 bit install#
Some time after you install MSSQL 2012 SP 1 strange things start to happen on the server. Or to be more exact: seven days of my life, with every waking hour spent troubleshooting and finally reinstalling servers.