Paging Files on Multiple Volumes

By martinkuetzing ·
For years now, and across numerous XP Prof and W3KS systems, I've observed a curiosity and nuisuance regarding paging files. The objective is to set up paging files on volumes other than on the C: volume. The issue is that on alternate startups Windows will shoehorn itself into a ridiculously small paging file on C: and ignore the settings specified in Advanced Settings for a correctly sized paging file elsewhere. Once starup is complete, Windows complains about low virtual memory. The only reliable fix I've found is to reboot a second time, at which time the paging files correctly reflect the Advanced Settings entries.

This nuisance seems to follow most W3KS servers and power XPP workstations that I manage.

In scouring the web on paging files, I have read about and tried setting C: volume paging sized from say 1 MB to 20 MB, while keeping the main paging file on other volumes or drives in line with installed RAM sizes, 2GB, 16 GB, etc. And, unless I'm missing somehting, I've tried it all in trying to select a C: volume size that Windows startup ignores.

If for instance, I specify no paging file on C:, on alternate startups, Windows will put one there anyway of a size of its own choosing. On a second reboot, the arbitrary C: paging file will go away in favor of the Advanced Settings one specified for placement elsewhere. If I specify a minimum sized C: volume paging file - say 1 MB (or larger) - on alternate startups, Windows will shoehorn itself into that size and complain later about insufficient virtual memory. But, a second, succesive reboot will fix things.

Thus, when I take down one of our primary W3KS servers or power workstations, I always plan on two, successive re-starts to overcome this issue and have the Virtual Memory settings corrected implemented.

One other thing, generally I do not use the C: volume as the SysVol. It's a personal preference that provides me more flexibility in the management of these systems. However, I still fail to see the connection between where the SysVol is and the paging files are.

To complicate the matter, this issue is not reflected on every system that I have personally or on systems that I manage professionally. But, many to most have this problem.

What I am hoping for is that someone who reads this has experienced the identical issue and has a surefire fix for it: a registry setting, additional registry entry or KB doc, etc. Thanks in advance!

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Answers

Collapse -

W3KS ? 1MB pagefile ? Shoehorn ? Non C sysvol ? ...

by OldER Mycroft In reply to Paging Files on Multiple ...

You've lost me.

All this kerplunk!

To prove what?


Collapse -

W3KS, etc.

by martinkuetzing In reply to W3KS ? 1MB pagefile ? S ...

W3KS = Windows 2003 Server
Pagefile = Virtual Memory on disk (equivalent to Unix/Linux swap file)
sysvol = system volume, ie., in this case where the boot loader finds the Windows folder
shoehorn = verbal expression to emphasize that something is forced to fit into too small a space; there are rules-of-thumb for determining how large a pagefile should be available to Windows; in the cases I have described with my orginal post, Windows has "chosen on its own" to ignore Advanced Settings entries in favor of its own which make a pagefile that's too small.

Collapse -

My questions were not of semantics ...

by OldER Mycroft In reply to W3KS, etc.

My point in question, which you have yet to answer was:

What is the point of your rant?

That, and the fact that I find it difficult, nay implausible, to consider the comprehension of a one megabyte pagefile - that would be like a car having a one millilitre petrol tank - entirely possible but totally impractical and unusable.

As for Windows shoe-horning itself into 'any' space - PAH!

Collapse -

I have noticed that too....

by ---TK--- In reply to Paging Files on Multiple ...

I have always put my page file on a different drive, and I have always set C to no Paging. I have noticed the green that always sticks around (even though you told it to go away), but I have never experienced the error that you are having... The old rule of thumb was to multiply (amount of RAM x 1.5)= page file size... which has always worked great for me...

Although, I have scene/researched programs not completely removing them selfs from the page file. And after awhile of that happening it will consume everything... Gotta run... ill post the registry key later that forces programs out of ram and pagefile... might help...

Related Discussions

Related Forums