Change the size of virtual memory (Page file size) in Vista
If you're new here, you may want to subscribe to Windows Reference RSS feed Thanks for visiting!
A hidden file or files on the hard disk that Windows uses to hold parts of programs and data files that do not fit in memory. The paging file and physical memory, or random access memory (RAM), comprise virtual memory. Windows moves data from the paging file to memory as needed and moves data from memory to the paging file to make room for new data. Also known as a swap file.
If you receive warnings that your virtual memory is low, you’ll need to increase the minimum size of your paging file. Windows sets the initial minimum size of the paging file at the amount of random access memory (RAM) installed on your computer plus 300 megabytes (MB), and the maximum size at 3 times the amount of RAM installed on your computer. If you see warnings at these recommended levels, then increase the minimum and maximum sizes.
Change the size of virtual memory (Page file size) in Vista using the following procedure
click the Start button>Control Panel
click on System and Maintenance
click on System.
In the left pane, click Advanced system settings. If you are prompted for an administrator password or confirmation, type the password or provide confirmation.
On the Advanced tab, under Performance, click Settings.
Click the Advanced tab, and then, under Virtual memory, click Change.
Clear the Automatically manage paging file size for all drives check box.
Under Drive [Volume Label], click the drive that contains the paging file you want to change.Click Custom size, type a new size in megabytes in the Initial size (MB) or Maximum size (MB) box, click Set, and then click OK 3 times.
NOTE:-Increases in size usually don’t require a restart, but if you decrease the size, you’ll need to restart your computer for the changes to take effect. We recommend that you don’t disable or delete the paging file.
Random Posts
Did you enjoy this post? Why not leave a comment below and continue the conversation, or subscribe to my feed and get articles like this delivered automatically each day to your feed reader.
Trackbacks & Pingbacks
Comments
Leave a comment
Line and paragraph breaks automatic, e-mail address never displayed, HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>
I trully think that in vista that setting needs to be left to windows
very helping
thanks alot
i got much place freed by this pagefile
Hi!
I did this change in Vista and i got a problem. My vista wont start, it wants to do a repair when i start it but when i select it, vista try to load it and it just becomes a black screen. I’ve tried to boot in safe mode but it hangs on crc.sys or something like that. Tried to boot from cd but nothing happens. please reply an answer.
Best regards Alex
BAD IDEA
This appears to be a very confused article. I hope no one takes the screen shot where the page file size is shown seriously. The values shown are rediculous and don’t agree with the text.
Best advice: Set the pagefile to “System Managed Size”. Contrary to many uninformed sources, this configuration is NOT inefficient. The values chosen by Microsoft designers were not arbitary but the result of a great deal of research. The author has provided no reasons whatsoever why they should be changed.
If you receive warnings from Windows then manually set a higher initial value. There should be no need to change the maximum value. There is no need or benefit in setting the initial and maximum values the same.
Larry Miller
Microsoft MCSA
RE: Larry Miller/pagefile
Larry, I agree Windows is generally good with setting the pagefile at a reasonable size, however from what I understand, when Windows has the pagefile set to “System Managed Size”, Windows automatically increases and shrinks the pagefile based on the memory load. Isn’t this bad for fragmentation of the pagefile? Wouldn’t a better alternative to “System Managed Size” be to set the pagefile to a fixed size (setting the MIN/MAX to the same size)? This fixed size could be some value within the range of what “System Managed Size” would otherwise set the size to. With a fixed size, once the pagefile is defragmented, it will never be fragmented again because it will always remain on the same location on the harddisk. Larry, what are your thoughts on this?
There seems to be a great deal of confusion about what a “system managed” pagefile actually is. It is really very simple. On bootup Windows sets the initial pagefile size to 1.5 x Physical RAM with a maximum of 2 times this value. Of course, if RAM size has not changed no changes will be made. That is all “system managed” does. The pagefile does not grow and shrink according to need.
If the initial size is adequate, no expansion or fragmentation will ever occur, even after months of heavy continuous use. In most cases the system chosen value will accomplish this.
If the initial size should prove too small, then expansion will occur. But this is not normal operation, only a reaction to an exceptiopnal need. If this occurs during normal operatrion then the initial size should be adjusted upward. In any event this expansion is temporary, the pagefile will revert to it’s initial size during a reboot.
A fixed pagefile is fine, provided you have quessed right about it’s size. And you had better be right. If you guess wrong, you risk severe performance problems or an application failure. If you have allowed expansion this will be prevented. A system managed pagefile has all the advantages of a fixed pagefile, yet still retains the ability to expand to meet exceptional needs. This is a completely free safety net with no performance implications unless it is actually needed.
Windows designers have put a great deal of research into pagefile management and it has been tested more than most people can imagine. Many VERY experienced people use a system managed pagefile and are fully aware of all the arguments against it’s use. It is not just used by beginners who supposedly don’t know any better.
Larry Miller
Microsoft MCSA
I just built a brand new AMD Phenom II 940, 8GB OCZ RAM, 1TB HD, etc… To make a long story short, the person I built the PC for plays Second Life. Using System Managed Size is not sufficient to run these for some reason. I don’t know if it’s a memory leak in the new version or what, but the PC complained Low Virtual Memory, please close programs… Yada yada. I put the virtual memory initial size to 16000MB and max size to 50000MB. So far no problems. I mean, should the max size really be limited in System Managed Size?
John Sacul