Comments on: Where is my memory going? http://analyze-v.com/?p=181 Windows, WinDBG, IDA, and Oxford commas Wed, 08 Sep 2010 16:15:40 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: snoone http://analyze-v.com/?p=181&cpage=1#comment-19 snoone Wed, 01 Jul 2009 13:25:16 +0000 http://analyze-v.com/?p=181#comment-19 Thanks for the added info Pavel! Interesting that they've broken the working sets out, definitely makes more sense. We're running Win7 for our everyday use computer at home, I'll have to check out the !vm improvements and the new working set breakdown. Thanks for the added info Pavel!

Interesting that they’ve broken the working sets out, definitely makes more sense.

We’re running Win7 for our everyday use computer at home, I’ll have to check out the !vm improvements and the new working set breakdown.

]]> By: Pavel Lebedinsky http://analyze-v.com/?p=181&cpage=1#comment-18 Pavel Lebedinsky Wed, 01 Jul 2009 07:29:16 +0000 http://analyze-v.com/?p=181#comment-18 !vm has some additional flags that can be useful when troubleshooting memory allocation failures. For example, 32-bit Vista and Win7 support !vm 0x21 which dumps statistics about kernel space VA usage. This is useful for example when you get a pool allocation failure yet the system seems to have plenty of available commit and physical memory. Another win7 change is that MmSystemCacheWs is now split into 3 separate working sets: MmSystemCacheWs, MmPagedPoolWs and MmSystemPtesWs. !vm has some additional flags that can be useful when troubleshooting memory allocation failures. For example, 32-bit Vista and Win7 support !vm 0×21 which dumps statistics about kernel space VA usage. This is useful for example when you get a pool allocation failure yet the system seems to have plenty of available commit and physical memory.

Another win7 change is that MmSystemCacheWs is now split into 3 separate working sets: MmSystemCacheWs, MmPagedPoolWs and MmSystemPtesWs.

]]>