Vista Kernel Memory uses 6GB of Paging RRS feed

  • Question

  • Hi,

    I'm running Windows Vista and after a few days of uptime my system gets pretty slow. I checked the processes and nothings wrong there. But then I took al look at the memory usage and I saw that that the Kernel Memory was using almost 6GB of my pagefile...


    Can anybody tell me why?


    Sunday, December 2, 2007 1:09 PM

All replies

  • I haven't the least idea but a similar problem though.


    And nothing done except surfing the internet and a bit Google Earth and Java-apps.
    Tuesday, April 1, 2008 1:37 PM
  • Since I installed the RC of SP1 the problem is solved. My kernel memoty now stabalizes around 260MB.
    Tuesday, April 1, 2008 10:11 PM
  • I have and had SP1 from Windows Update installed. This is by the way a Windows Vista Business.
    Now I have (re)activated Superfetch - amongst the first things I deactivated because testing showed me it doesn't do anything FOR speed gain - and set pagefile-handling back to Windows-managed - also previously deactivated and set to 2 GB fixed - but nothing changed.
    Still 456 MB kernel-mem overall and 398 MB of this non-paged. Commited charge flies arround 1033 MB and working set size is at 753 MB with 784 MB in-cache and 54 MB free - what from my point of view is a bit on the low side for launching new apps, hence my deactivation of superfetch. So Windows hasn't to invalidate Superfetch'ed memory in order to launch my app. And all this growing over time, uptime is only 82 hours.
    I am on my wits end here and about to wipe Vista of off my hd wouldn't I need it to cross-check things that my customers with Windows Vista ask me.
    Sunday, April 6, 2008 9:34 AM
  • The thing that disapoints me the most is the fact no Microsoft employee has taken the effort to reply to this post or to look for a good explanation or solution to the problem.
    Sunday, April 6, 2008 11:01 AM
  • The exact same thing disappoints me too. Sad
    Tuesday, April 8, 2008 2:39 PM
  • This is almost always caused by drivers leaking memory.  Non-paged leaks can be especially damaging to performance.


    You have two options:

    1.  Start unplugging and disabling devices and updating drivers until the leak gets "plugged" (i.e. the memory usage stops increasing)


    2. Use Driver Verifier to directly identify where the leak is occuring.  A really cool tool, but definitely for advanced users who aren't afraid of BSODs or debugging. If you don't know what a BSOD is, stick to #1. Smile






    John E [MSFT]

    Monday, April 14, 2008 3:45 PM