Speed up your PC – Run Windows kernel in RAM

Posted on 2 March, 2007
This item is filed under [Productivity Tips, Tips & Tricks, Windows XP]

March 2, 2007 · 6 comments

It is a known fact that anything that runs in the RAM will be much faster than something that has to access the hard disk or the virtual memory. The same is the case with the Windows Kernel which is the heart of Windows.

Normally the kernel uses the slower Paging Executive functions to run. But if you could somehow make it run from the RAM then you can really get a considerable boost in your computer speed. Here is how you can do that with just a simple Registry hack. But this hack is advisable only if you have atleast 256 MB of RAM.

Note: Always make a backup of your registry before attempting any kind of changes to it.

Windows Kernel RAM

Go to Start>Run. Type ‘Regedit‘ and hit enter.

In the registry editor go to the following key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\DisablePagingExecutive and change the value to “1“.

Close the editor and restart Windows. Your computer should perform faster now.

If for some reason you want to revert back, just change the value back to ‘0‘.

Enjoyed this post? Share it with others.
  • email
  • Print
  • Digg
  • StumbleUpon
  • Technorati
  • Reddit
  • del.icio.us
  • Facebook
  • Mixx
  • Google Bookmarks
  • FriendFeed
  • BlinkList
  • Diigo
  • LinkedIn
  • Propeller
  • IndianPad
  • MySpace
  • Slashdot

Subscribe Now

If you enjoyed this post, you will definitely enjoy our others. Subscribe to the feed to get future posts delivered right to your mailbox or feedreader.

Powered by Thesis

Thesis Theme

An amazing WordPress Theme, nothing beats the versatility and SEO friendliness of the Thesis framework.

From beginners, to the most advanced WordPress developers, Thesis makes it easy for anyone to customize it.


{ 6 comments… read them below or add one }

Atul April 3, 2007 at 2:48 pm

i couldnt find this key in my registry ..+
:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management
the only option under memory management is PrefetchParameters
: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\PrefetchParameters

Reply

Suresh April 3, 2007 at 4:23 pm

@Atul: If the key does not exist you can create a new key by the name ‘DisablePagingExecutive’ under Memory Management and set it’s value to 1.

Reply

Atul April 13, 2007 at 11:12 am

doenst seems to make any diffrence ..

Reply

cjw March 1, 2008 at 6:12 am

The key is inside the Memory Management folder, alongside the sub folder Prefetch Parameters.

On the left window pane, select Memory Management. Now in the right window pane look for the DPE key.

Thanks Suresh.

Reply

traderv August 2, 2008 at 10:16 pm

I have read this proposed action in s several places. I have not found anyone who has successfully used it. I have tried it three or more times, and it never makes a difference in the amount of kernel in RAM or on disk. The amounts remain the same. Typical kernel is 200MB paged and 29MB unpaged. These numbers may change with time, but appear to be independent of the registry entry described above.

I would really like to be able to try this change. Does anyone have a suggestion as to how to make it work?

Reply

Larry Miller December 20, 2008 at 11:27 pm

The authors description of this setting is confused and best ignored. The setting applies only to a small portion of the kernel. Paging of the kernel is no different than that of anything else. Code and data that is frequently accessed will be kept in RAM, while that which is not will be unloaded to disk. This is known as paging and is as normal and necessary as breathing is to you and I. This was designed to enhance system performance and it works very well. The “DisablePagingExecutive” setting prevents this normal behaviour for a small portion of the kernel. If memory is adequate this will do very little if anything. If memory is short the setting will probably impair performance. The setting was primarily intended for servers with a small and well defined application load. It is generally not useful on wokstations. Larry Miller, Microsoft MCSA

Reply

Leave a Comment

Previous post:

Next post: