Force windows to load the kernel in memory

Posted on February 5th, 2008 by Jason

This one is the best tweak for windows XP I ever found, and it works very well. With this tweak we will force windows to load kernel and drivers in memory.

Here is what you have to do :

1) Open the regedit tool (Start -> Run -> regedit.exe )

2) Use the navigation in the left and go to HKEY LOCAL MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management

3) Double click the DisablePagingExecutive attribute, and put 1 in the decimal value field This will make the drivers and the XP kernel run in memory.

4) Double click the LargeSystemCache attribute, and put 1 in the decimal value field
This will improve performance of the kernel

5) Double click the IOPageLockLimit attribute. On some later versions of windows XP that doesn’t exists, so if this is the case you’re done. Otherwise you have to put to the hex value : 4000 for pcs with 128 mb ram, 10000 for 256 mb ram and if you have more put 40000. This value specifies how many bytes can be used for I/O operations in your system.

Tags: , , , , , ,

This entry was posted on Tuesday, February 5th, 2008 at 3:26 pm and is filed under Windows XP. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

Related posts

2 Responses to “Force windows to load the kernel in memory”

  1. stooge on 06 Feb 2008 at 6:58 pm #

    It has been proved that this tweak is totally useless and does nothing!
    Here is proof in your own words:
    “IOPageLockLimit attribute. On some later versions of windows XP that doesn’t exists”. That is why M/Soft removed this attribute

  2. Larry Miller on 24 Dec 2008 at 9:22 am #

    LargeSystemCache:
    This setting is NOT recommended for general use. With rare exceptions this should be used on servers only. It means that memory for caching has priority over memory for application use. This is good for file servers but can kill application performance.

    This setting is potentially dangerous with some common hardware configurations. It produces an environment that many hardware devices and drivers were not designed for. Some users have reported severe performance problems, system instability, and data corruption. It is deadly with some common video cards amd other devices.

    DisablePagingExecutive:
    This setting forces portions of the kernel to remain in RAM at all times, even when they are not needed. Much of the kernel is used ony under relatively rare conditions. By default portions of the kernel are paged in as necessary, then remain in RAM until it is needed for other purposes. Do not impose arbitrary constraints on this activity, it was designed for optimum performance.

    IOPageLockLimit:
    Support for this setting was dropped in Windows 2000 SP1. It is not supported on any version of XP or Vista.

    Contrary to popular opinion, Windows actually manages memory very well on it’s own. Do not be misled by the numbers in Task Manager. Some critical values have very diffirent meanings than commonly believed.

    PF Usage: This is not actual pagefile usage but only potential usage. Actual usage will typically be much lower.
    Available Memory: The majority of this is not free. It is actually in use by the system or applications, but since it has already been saved to disk it is immediately available if needed.

    Larry Miller
    Microsoft MCSA

Leave a Reply