System Properties Error - paging file configuration

Question

I get the following every time I start my computer. "Windows created a temporary paging file on your computer because of a problem that occured with your paging file configuration when you started your computer. Total pagin file size for all disk drives may be somewhat larger than the size  you specified." please help.

Answer 1

Hey schweitzer,

Thanks for posting in Microsoft answers!

The error message you receive is related to low Virtual memory. You may have to increase the virtual memory on your computer.

Virtual memory combines your computer’s RAM with temporary space on your hard disk. When RAM runs low, virtual memory moves data from RAM to a space called a paging file. Moving data to and from the paging file frees up RAM so your computer can complete its work.

Refer the link below for details on virtual memory:

What is virtual memory?http://windows.microsoft.com/en-US/windows7/What-is-virtual-memory

If you receive error messages that warn of low virtual memory, you need to either add more RAM or increase the size of your paging file so that you can run the programs on your computer. Windows usually manages this automatically, but you can manually change the size of virtual memory if the default size isn't large enough for your needs. For more information, refer the link below and fo9llw the steps mentioned in the article to increase the size of the paging file:

Change the Size of virtual memoryhttp://windows.microsoft.com/en-us/windows7/Change-the-size-of-virtual-memory

This error message may occur if Windows tries to create a paging file on an NTFS volume, but the System and Administrators accounts do not have the correct NTFS permissions on the volume.

You may also refer the link below and follow the steps mentioned in the KB article:

http://support.microsoft.com/kb/315270

The above link is for Windows XP, but the same may be carried out for Windows 7 as well.

Hope this helps!

Gokul – Microsoft Support

Answer 2

The correct answer steps can be found at: Jack Stromberg's Blog.

The only difference to the posted instructions in his blog would be at step 16, Click the drive you want your new paging file on, click 'System Managed Size', Click 'Set', Click OK on all boxes and close all windows and restart machine.

Answer 3

Hi all I recently upgraded my Laptop from Windows Vista Home Premium to Windows 7 professional.

I also upgraded a desktop from Windows XP to Windows 7 pro.

As usual as I have done in the past with previous versions of windows. I set up a separate logical partition (same physical drive) and defined  a paging file size for the partition.  generally 1.5 - 2.0 times

the size of the physical ram. (for both of these machines each has 4Gb of ram)

So when I did this for these two machines I now get this warning message and Windows creates a temporary pagefile.sys on the C drive where I don't want it.

In both cases I'm not using these partitions for anything else, both are GT 8 Gb in size, the laptop has a 12Gb partition and the desktop a 16 Gb partition.

Here's the kicker. The allocated size Windows creates on the C drives is ONLY 4Gb 2Gb smaller than the

recommended size.

When I adjust the min and max sizes to 6144 and 7168 megabytes and reboot.  Windows 7 essentially

ignores my settings and creates the temp paging file on the C drive and issues this warning msg.

To Wit:

 "Windows created a temporary paging file on your computer because of a problem that occurred with your paging file configuration when you started your computer. Total paging file size for all disk drives may be somewhat larger than the size  you specified."

Also on both  of these machines I'm only using between 25 and 30 % of the system RAM.

at any given time. I don't keep a lot of "windows" open. I don't do any gaming or run any

databases.

So I'm NOT low on memory.

Any Ideas on how I can force windows 7 from creating these temporary paging files and

only use the ones I have defined.

Thanks 2UWrangler

Answer 4

In my case, the error occured due to very low disk space on the system drive (around 20 MB) of my virtual machine (Windows 2008 R2). Expanding the disk and rebooting the system solved the problem.