I even recall activating the feature, since it sounded like a great idea. So what the developer wrote for the first tag was PNTC, where TC is likely a reference to the “Tiered Cache” driver. When targeting a Little Endian machine (such as x86) the result will show up as a string "DCBA" inside the binary file. When writing tag names in C/C++ one usually uses something like 'ABCD', so a literal of these four letters. Going by the tag names, it even makes sense.
#Alse poolmon.exe driver#
The file description states TCE Storage Driver and another string from the version information resource mentions Tiered Cache for Enterprise. Then, using findstr, which conveniently comes with Windows and has shipped with Windows for ages, I found that these two tags belong to the same driver: C:\>findstr /m /l CTNP %SystemRoot%\System32\drivers\*.sysĬ:\>findstr /m /l CT-D %SystemRoot%\System32\drivers\*.sysįurther inspecting the driver turned out it belongs to a feature of Diskeeper 16 by Condusiv.
Using the tool poolmon.exe from the Windows Driver Kit, I figured out that the most offensive pool tags in terms of overall allocation size were CTNP (almost 12 GiB) and CT-D (approximately 6 GiB).
#Alse poolmon.exe install#
Heck, that’s why I install my RAM not out of some vanity motive to tell others just how much RAM I plugged into my machine. I’m not a cargo cultist who keeps perpetuating that using the RAM you installed is somehow a bad thing. Nothing wrong with using much RAM, if everything else doesn’t suddenly slow down due to resource pressure increased level of paging. I’ve even run an XP VM from a RAM disk and you should have seen just how quickly XP can install and boot 😉Īnyway, so from both the task manager which ships with Windows 7 as well as from the Sysinternals tool called RAMmap, I could see that huge amounts of NonPagedPool were being used.
My machine has 32 GiB of physical RAM, so there shouldn’t usually be a problem running even several virtual machines at once. So as of recently I started having issues with memory use.
0 kommentar(er)
