Page file windows 2008 location

Not an IT pro? Resources for IT Professionals. Sign in. United States English. Ask a question. Quick access. Why would the amount of ram you have present dictate the size you should set your page file to? That seems counter intuitive and may even make the system unstable. For instance if my computer had 8 gigabytes of ram and I wanted to open a giant 20 gigabyte TIF picture. My system might very well crash if we use the logic of 8 gigabyte maximum Virtual memory. Reviewing the mini-dump file and logs will illuminate the root cause is most cases.

Follow these steps to move pagefile from C: to another drive:. Now specify a new page file on another drive you have. To do that, select the desired drive from the list and choose the System managed size option. Again, the system-managed page file will be increased to back this kind of crash dump. If the system is configured to have a page file or a dedicated dump file of a specific size, make sure that the size is sufficient to back the crash dump setting that is listed in the table earlier in this section together with and the peak system commit charge.

Computers that are running Microsoft Windows or Microsoft Windows Server usually must have a page file to support a system crash dump. System administrators now have the option to create a dedicated dump file instead. A dedicated dump file is a page file that is not used for paging. Dedicated dump files can be put on any disk volume that can support a page file.

We recommend that you use a dedicated dump file if you want a system crash dump but you do not want a page file. To learn how to create it, see Overview of memory dump file options for Windows. By default, page files are system-managed. This means that the page files increase and decrease based on many factors, such as the amount of physical memory installed, the process of accommodating the system commit charge, and the process of accommodating a system crash dump.

For example, when the system commit charge is more than 90 percent of the system commit limit, the page file is increased to back it. This continues to occur until the page file reaches three times the size of physical memory or 4 GB, whichever is larger. This all assumes that the logical disk that is hosting the page file is large enough to accommodate the growth. The following table lists the minimum and maximum page file sizes of system-managed page files in Windows 10 and Windows Several performance counters are related to page files.

This section describes the counters and what they measure. The following performance counters measure hard page faults which include, but are not limited to, page file reads :. Hard page faults are faults that must be resolved by retrieving the data from disk. Such data can include portions of DLLs,. These faults might or might not be related to a page file or to a low-memory condition.