Overclock.net banner
Cancel
Create thread New Forums

*Solved* Cannot find Pagefile.sys on C Drive

2 reading
Jump to Latest
1 - 20 of 24 Posts

Destrto

· Registered
Joined
·
2,321 Posts
Discussion starter · #1 ·
Hey guys, I was working on Mom's computer (Windows 7 Home Premium 32bit) earlier and noticed that at every restart she gets this Windows error page that states:

"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. The total paging file size for all disk drives may be somewhat larger than the size you specified."

Now, I have tried a few steps in fixing this, however, I have not been able to so successfully.

Things I have done already:
Selected "show hidden files and folders"
Unselected "Hide protected operating system files"
Unselected "Automatically manage paging file size" from Virtual memory options.

Oddly though, is that when I go into C: Drive I do not see pagefile.sys, nor does a search find it. However, I DO find one in the spare D: Drive that is installed. I have tried following the steps in THIS guide, but as I've just explained, there is no pagefile.sys file to be found on C: once I have gotten to Step 6.

I have selected "Custom size" within the Virtual Memory window and set it to 0Mb as per the guide's directions. And the directions states that after restarting, I should be able to locate the pagefile.sys file from within C: and delete it, well, when I do this on my machine, there is no pagefile.sys file found. WHen I reenable it, it shows up in the D: drive instead of Drive C:. Even though in the Virtual memory window, Drive D: is still set to "None" for its Pagefile.

What I want to do essentially, is get the C; Drive's pagefile.sys file back; stop the pagefile.sys from being created on the D: Drive, and stop this annoying warning window every time the desktop restarts.

Can anybody help me figure this out? Any help is appreciated.
 
#2 ·
Start > Computer (right click, choose properties) > Advanced System Settings > Performance (Settings) > Advanced > Virtual memory (Change).

You should see this which identifies the location and size of the pagefile(s)

 
Save
Reply Quote Rep+ Rep+
Discussion starter · #3 ·
Quote:
Originally Posted by billbartuska View Post

Start > Computer (right click, choose properties) > Advanced System Settings > Performance (Settings) > Advanced > Virtual memory (Change).

You should see this which identifies the location and size of the pagefile(s)
Click to expand...
Yes, I've gotten there. According to the guide I linked, I disabled (set the pagefile to 0Mb) on both drives.

This is what shows after a reboot. And I still get the warning popup.

Like I mentioned, when I go to look for the pagefile.sys file within C: Drive, there isn't one. According to the guide, there should be.
 
#4 ·
You really can't eliminate a pagefile. Even if you set it to be zero, Windows will make one, though small, somewhere.
Windows won't run without it.

You use the screen I posted to size the pagefile and put it where you want it.

Without knowing your setup, you usually make the maximum pagefile size 1.5 times the size of the installed memory. It's best to put it on a drive other than the one that has the Windows folder on it, if you have more than one drive.

Run the computer normally for a few days, go back and see what the current pagefile size is. Then set that as both the MAX and MIN size. Not allowing Windows to dynamically change the size will keep the pagefile from getting fragmented.
 
Save
Reply Quote Rep+ Rep+
Discussion starter · #5 ·
Quote:
Originally Posted by billbartuska View Post

You really can't eliminate a pagefile. Even if you set it to be zero, Windows will make one, though small, somewhere.
Windows won't run without it.

You use the screen I posted to size the pagefile and put it where you want it.

Without knowing your setup, you usually make the maximum pagefile size 1.5 times the size of the installed memory. It's best to put it on a drive other than the one that has the Windows folder on it, if you have more than one drive.

Run the computer normally for a few days, go back and see what the current pagefile size is. Then set that as both the MAX and MIN size. Not allowing Windows to dynamically change the size will keep the pagefile from getting fragmented.
Click to expand...
Like I said, there is not one visible. On either drive. I understand what you're saying, I've done a bit of research myself before posting here for help.

I'm not trying to resize the pagefile right now, I'm trying to figure out how I can remedy this warning page that I quoted in the OP. I get this warning page regardless of what I try right now, setting both drives to no pagefile, setting them to auto manage, and even setting them to a specific number in custom settings.
 
#6 ·
It's simply foolish to always have a pagefile as 1.5x the size of your memory - what if you have 16GB or 32GB of RAM? It's going to eat up your drive for nothing. Win7 also sets it that large by default, if there's not enough room on the drive the installation will fail.

I have a static 2GB pagefile which is more than enough
 
Discussion starter · #7 ·
Quote:
Originally Posted by linkin93 View Post

It's simply foolish to always have a pagefile as 1.5x the size of your memory - what if you have 16GB or 32GB of RAM? It's going to eat up your drive for nothing. Win7 also sets it that large by default, if there's not enough room on the drive the installation will fail.

I have a static 2GB pagefile which is more than enough
Click to expand...
Please try to stay On Topic guys, and refrain from flaming others about their personal settings/opinions/suggestions. If you don't agree with it, leave it be.
 
Discussion starter · #8 ·
Still cannot get this pagefile thing sorted out.

When I try to set it to a specific number, I still get the warning popup after a restart. Same goes for disabling it completely and setting it auto manage..
 
#9 ·
Quote:
Originally Posted by billbartuska View Post

You really can't eliminate a pagefile. Even if you set it to be zero, Windows will make one, though small, somewhere.
Windows won't run without it.
Click to expand...
Sorry to say, but this is simply not true. I like to run my computers with no page files at all. When properly disabled, there is no page file anywhere and Windows works just fine. This is just as summarized in the article the OP linked: "By temporarily turning off virtual memory, you allow yourself to delete the (now-corrupt) paging file. Then when you re-enable virtual memory, Windows automatically builds a new paging file from scratch, and voilà, problem solved."

@Destrto: How much space is free on C:\? The only time I experienced this error was when I tried to create a pagefile on a HDD partition that I had assigned to letter B:\. The pagefile would work in Windows immediately after setting it, but upon reboot, Windows would refuse to use the pagefile it had created on B:\, probably because of the unusual drive letter. It would boot and give the same warning that you're seeing, and then create itself a pagefile on C:\. After reassigning letter B:\ to letter G:\, the pagefile went on that partition with no difficulty. In your case, my guess is that something, either permissions on the root of the drive, or a lack of space, is keeping it from creating the page file normally on C:\.
 
Discussion starter · #10 ·
Quote:
Originally Posted by Techie007 View Post

Sorry to say, but this is simply not true. I like to run my computers with no page files at all. When properly disabled, there is no page file anywhere and Windows works just fine. This is just as summarized in the article the OP linked: "By temporarily turning off virtual memory, you allow yourself to delete the (now-corrupt) paging file. Then when you re-enable virtual memory, Windows automatically builds a new paging file from scratch, and voilà, problem solved."
Click to expand...
Quote:
@Destrto: How much space is free on C:\? The only time I experienced this error was when I tried to create a page file on a HDD partition that I had assigned to letter B:\. The page file would work in Windows immediately after setting it, but upon reboot, Windows would refuse to use the page file it had created on B:\, probably because of the unusual drive letter. It would boot and give the same warning that you're seeing, and then create another pagefile on C:\. After reassigning letter B:\ to letter G:\, the pagefile went on that partition with no difficulty. In your case, my guess is that something, either permissions on the root of the drive, or a lack of space, is keeping it from creating the page file normally on C:\.
Click to expand...
Currently around 90% free on C:, which is a 200GB drive. And the secondary drive (250GB) has absolutely nothing on it. SO insufficient space shouldn't be an issue. And the drive letters aren't anything weird, they are C and D.

What I've noticed is that when I do try to enable pagefile on either drive, reboot, and get the warning again, the pagefile has been added to the secondary drive. Regardless of which drive I state I want the pagefile to be implemented on, it gets placed on the D drive.

Odd thing is, even after disabling the pagefile like the guide suggests, I still get the error when I restart.
 
#11 ·
    Can you post a screenshot of the permissions on the root of C:\?  Right-click "Local Disk (C:)", click Properties, go to the Security tab, click [Advanced], and then press [Alt]+[PrintScrn] to take a cropped screenshot.
 
Discussion starter · #12 ·
Quote:
Originally Posted by Techie007 View Post

Can you post a screenshot of the permissions on the root of C:\? Right-click "Local Disk (C:)", click Properties, go to the Security tab, click [Advanced], and then press [Alt]+[PrintScrn] to take a cropped screenshot.
Click to expand...
Here you go.

 
#13 ·
Those look correct. The most important ones in this case (SYSTEM and Administrators) are granted Full Control as they should be. So it's not a problem with access permission to the root of C:\.

Open Registry Editor (press [Win]+[R], type "regedit" and press [Enter]), and navigate to "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management" and post a screenshot. Perhaps try setting the "PagingFiles" registry value to "?:\pagefile.sys" (without quotes; this is the Windows 7 default value) and reboot the computer and see what the values are after the reboot.
 
Discussion starter · #14 ·
Quote:
Originally Posted by Techie007 View Post

Those look correct. The most important ones in this case (SYSTEM and Administrators) are granted Full Control as they should be. So it's not a problem with access permission to the root of C:\.

Open Registry Editor (press [Win]+[R], type "regedit" and press [Enter]), and navigate to "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management" and post a screenshot. Perhaps try setting the "PagingFiles" registry value to "?:\pagefile.sys" (without quotes; this is the Windows 7 default value) and reboot the computer and see what the values are after the reboot.
Click to expand...
When you say set the paging files registry value, do you mean to simply enter that into the field that opens when I select "modify"?

Here is the screenshot.
 
Discussion starter · #15 ·
Here is the result within regedit after rebooting.


In the Virtual memory settings, things are reverted back to the default "automatically manage" setting. And the pagefile is set to the D drive again. I did not, however, get any warning popup this time.
 
#16 ·
Quote:
Originally Posted by Destrto View Post

Here is the result within regedit after rebooting.


In the Virtual memory settings, things are reverted back to the default "automatically manage" setting. And the pagefile is set to the D drive again. I did not, however, get any warning popup this time.
Click to expand...
In all honesty, you WILL get warnings completely removing a Pagefile IF the OS is forced to make a call to one. Applications can "Force" a call to utilize virtual memory pagefiles on drives.

It is a terrible idea to completely remove the Pagefile permanently. It has a tendency to make Windows buggy, as you can tell here it is struggling to just shift drives!

Anyways back on track:
In order to remove it off of F:\ drive.

Attempt to set one up under C:\ (small size) 2048 to 2048, but click SET before you click OK.

Then please reboot.

Do you still get an error when both are enabled?

My guess would be after if you didn't that you attempt removal of the F:\ drive, but in that order. Don't forget to click "Set" though.

Idea two:
Create your own pagefile.sys manually on the C:\, then attempt to do the same as described above.

There maybe a hiccup in the read/write permissions on the NTFS filesystem.

IF that is the case, you DO need to fix that.
My suggestion at this point would be run "sfc /scannow" in the CMD Prompt As Admin.
 
Discussion starter · #17 ·
SFC /Scannow has been ran. No change.

Again, it has been mentioned that I am only trying to remove pagefile in order to have a new, un-corrupted one created so that it might fix the warning.

I get a warning after rebooting in any situation. Here:
I set Virtual Memory to "Auto Manage" Warning occurs.
I set Virtual Memory to "custom value" on Drive D. Setting "no pagefile" on Drive C Warning occurs.
I set Virtual Memory to "custom value" on Drive C. Setting "no pagefile" on Drive D. Warning occurs.
I set Virtual Memory to "system managed" on Drive C. Warning occurs.
I set Virtual Memory to "system managed" on Drive D. Warning occurs.
You get the idea..

I keep referring back to the guide I linked because it seems you guys are missing the point I'm trying to make here.. When I get to step 6. It tells me to set the pagefile to 0Mb on each drive, essentially removing it. Then, I should reboot and see the pagefile.sys file in whichever drive it was previously set to be on and delete it. My issue is that this does not happen, I do not see a "pagefile.sys" in either Drive's root directory.

@RagingCain, your step one has been attempted, no change. Warning still occurs after a reboot. I have even physically removed the secondary drive. Same thing, Warning occurs. I will be attempting your step 2 later today, when I can get access to the computer again.

I don't mean to be the jerk here, but it seems some of you are more interested in stating the benefits of whether or not to have a pagefile.. I am not concerned with this knowledge. I am concerned with this warning message that persists, even through multiple methods of fixing it.
 
#18 ·
Quote:
Originally Posted by Destrto View Post

SFC /Scannow has been ran. No change.

Again, it has been mentioned that I am only trying to remove pagefile in order to have a new, un-corrupted one created so that it might fix the warning.

I get a warning after rebooting in any situation. Here:
I set Virtual Memory to "Auto Manage" Warning occurs.
I set Virtual Memory to "custom value" on Drive D. Setting "no pagefile" on Drive C Warning occurs.
I set Virtual Memory to "custom value" on Drive C. Setting "no pagefile" on Drive D. Warning occurs.
I set Virtual Memory to "system managed" on Drive C. Warning occurs.
I set Virtual Memory to "system managed" on Drive D. Warning occurs.
You get the idea..

I keep referring back to the guide I linked because it seems you guys are missing the point I'm trying to make here.. When I get to step 6. It tells me to set the pagefile to 0Mb on each drive, essentially removing it. Then, I should reboot and see the pagefile.sys file in whichever drive it was previously set to be on and delete it. My issue is that this does not happen, I do not see a "pagefile.sys" in either Drive's root directory.

@RagingCain, your step one has been attempted, no change. Warning still occurs after a reboot. I have even physically removed the secondary drive. Same thing, Warning occurs. I will be attempting your step 2 later today, when I can get access to the computer again.

I don't mean to be the jerk here, but it seems some of you are more interested in stating the benefits of whether or not to have a pagefile.. I am not concerned with this knowledge. I am concerned with this warning message that persists, even through multiple methods of fixing it.
Click to expand...
Its okay, it can be frustrating, my comments were more towards other viewers of the thread, never forget, that by posting here, someone may stumble upon this thread in the future looking for a fix or more info
smile.gif
That's why we volunteer extra information at times
smile.gif


I know, I know, this is about your issue.

You mentioned SFC was ran, and no change, but did it give you any feedback or errors found? If you don't remember it can be located in a log here: C:\Windows\Logs\CBS\CBS.log

I will be around later when you can get at the machine again.

The problem with that "guide" is that you don't have a pagefile.sys to remove. Even if the one on F: or D: drive exists AND is corrupt. It should not prevent you from creating one on C:\.

Therefore there is something wrong.

(Have you had a chance to do a Anti-Malware / AV scan?)

Another option in my mind is to revert to Safe Mode, I believe it doesn't use pagefile for the most part.
Set Page File to No on All Drives, Click Set, Click OK.

Reboot, but back into SAFE MODE, check the pagefile status.
If it has returned, do step 1 again, but this time don't reboot, then manually DELETE all PageFile.SYS files.
If settings have not returned, manually DELETE all PAGEFILE.SYS files from all drives.

Reboot, again, back into SAFE MODE, once more.
Manually configure the drive you with want with a MANUAL pagefile of 2048MB, minimum, max 2048. Click Set, Click OK.

Reboot computer as normal.
Verify settings have "stuck".
 
Discussion starter · #19 ·
Quote:
Originally Posted by RagingCain View Post

Its okay, it can be frustrating, my comments were more towards other viewers of the thread, never forget, that by posting here, someone may stumble upon this thread in the future looking for a fix or more info
smile.gif
That's why we volunteer extra information at times
smile.gif


I know, I know, this is about your issue.

You mentioned SFC was ran, and no change, but did it give you any feedback or errors found? If you don't remember it can be located in a log here: C:\Windows\Logs\CBS\CBS.log

I will be around later when you can get at the machine again.

The problem with that "guide" is that you don't have a pagefile.sys to remove. Even if the one on F: or D: drive exists AND is corrupt. It should not prevent you from creating one on C:\.

Therefore there is something wrong.

(Have you had a chance to do a Anti-Malware / AV scan?)

Another option in my mind is to revert to Safe Mode, I believe it doesn't use pagefile for the most part.
Set Page File to No on All Drives, Click Set, Click OK.

Reboot, but back into SAFE MODE, check the pagefile status.
If it has returned, do step 1 again, but this time don't reboot, then manually DELETE all PageFile.SYS files.
If settings have not returned, manually DELETE all PAGEFILE.SYS files from all drives.

Reboot, again, back into SAFE MODE, once more.
Manually configure the drive you with want with a MANUAL pagefile of 2048MB, minimum, max 2048. Click Set, Click OK.

Reboot computer as normal.
Verify settings have "stuck".
Click to expand...
I understand the information is volunteered, and it is appreciated. I would just rather not get into any e-peen discussions over who thinks who is right. But anyway..

When Sfc /scannow was ran it reported no errors of any kind.

AV and Anti-Malware scans were also clean.

I agree that something is not as it should be with this system and its pagefile.

I will try the steps you've mentioned here shortly.

I should add, that even though this pagefile warning pops up after every reboot, it does not seem to be affecting the performance of the machine. I am trying to remove this warning because it is a nuisance and should not be showing up at all. I am one of those people that believes "if it's not supposed to be there, it shouldn't be there."
 
Discussion starter · #20 ·
Update: set "no pagefile" to both drives, rebooted into safemode. No pagefile listed under either drive currently.

I am attempting to create one (256Mb-1024Mb) on the C drive and rebooting back into safemode.

Update 2: Rebooting into safemode gave the warning again. No pagefile on C drive where Virtual memory states it should be. Instead, a 3Gig pagefile has been created on the D drive. Even though I have D drive set to "No pagefile". I am also unable to delete it from within safemode.
 
1 - 20 of 24 Posts
About this Discussion
23 Replies
6 Participants
Last post:
anju123
Overclock.net
posts
28M
members
562K
Since
2004
The premier forum for overclocking experts and enthusiasts. Discuss hardware optimization, custom builds, benchmarking, cooling solutions, and pushing the boundaries of computing performance. From beginner guides to extreme overclocking, join our technical community to master system tuning.
Full Forum Listing
Explore Our Forums
Intel CPUs Hardware News NVIDIA PC Gaming Water Cooling