Windows 7 / Page File Disabled / 12 GB RAM / 2+ GB RAM free and “your computer is running low on memory”
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
So I am running on Windows 7 (64-bit) Home Premium with 12 GB RAM (Intel Core i7 920).
I have restricted the Page File to 400MB since it was eating up a lot of space om my SSD (that is 80GB).
After that I sometimes get the "low memory"-warning, like this, except for the behold-comment:
When I get those warning I have usually a lot of RAM available; when I check Resource Manager I have over 2GB "Free" and over 2GB "Available" - usually more than that.
The diskspace on all my drives have over 10GB free.
So the question is - why does Windows complain? It actually restarted by computer (hard boot) when it happened, and as I said - lots or RAM available.
windows-7 memory pagefile
asked May 27 '11 at 7:27
TedTed
13612
add a comment |
So I am running on Windows 7 (64-bit) Home Premium with 12 GB RAM (Intel Core i7 920).
I have restricted the Page File to 400MB since it was eating up a lot of space om my SSD (that is 80GB).
After that I sometimes get the "low memory"-warning, like this, except for the behold-comment:
When I get those warning I have usually a lot of RAM available; when I check Resource Manager I have over 2GB "Free" and over 2GB "Available" - usually more than that.
The diskspace on all my drives have over 10GB free.
So the question is - why does Windows complain? It actually restarted by computer (hard boot) when it happened, and as I said - lots or RAM available.
windows-7 memory pagefile
asked May 27 '11 at 7:27
TedTed
13612
I recon this is a windows issue. Windows Vista and 7 actually cache a lot of the RAM memory. Can you ignore the warning and continue with your normal work or it forces you to close the program?
– xciter
May 27 '11 at 9:04
If I am at the computer I can usuallyt press cancel, but that shouldnt be necessary in the first place. Also, it did happen once (when I was not at the computer) that the computer did a hard reboot...
– Ted
May 28 '11 at 18:38
add a comment |
So I am running on Windows 7 (64-bit) Home Premium with 12 GB RAM (Intel Core i7 920).
I have restricted the Page File to 400MB since it was eating up a lot of space om my SSD (that is 80GB).
After that I sometimes get the "low memory"-warning, like this, except for the behold-comment:
When I get those warning I have usually a lot of RAM available; when I check Resource Manager I have over 2GB "Free" and over 2GB "Available" - usually more than that.
The diskspace on all my drives have over 10GB free.
So the question is - why does Windows complain? It actually restarted by computer (hard boot) when it happened, and as I said - lots or RAM available.
windows-7 memory pagefile
asked May 27 '11 at 7:27
TedTed
13612
So I am running on Windows 7 (64-bit) Home Premium with 12 GB RAM (Intel Core i7 920).
I have restricted the Page File to 400MB since it was eating up a lot of space om my SSD (that is 80GB).
After that I sometimes get the "low memory"-warning, like this, except for the behold-comment:
When I get those warning I have usually a lot of RAM available; when I check Resource Manager I have over 2GB "Free" and over 2GB "Available" - usually more than that.
The diskspace on all my drives have over 10GB free.
So the question is - why does Windows complain? It actually restarted by computer (hard boot) when it happened, and as I said - lots or RAM available.
windows-7 memory pagefile
windows-7 memory pagefile
asked May 27 '11 at 7:27
TedTed
13612
asked May 27 '11 at 7:27
TedTed
13612
asked May 27 '11 at 7:27
TedTed
13612
asked May 27 '11 at 7:27
TedTed
13612
asked May 27 '11 at 7:27
TedTed
13612
13612
I recon this is a windows issue. Windows Vista and 7 actually cache a lot of the RAM memory. Can you ignore the warning and continue with your normal work or it forces you to close the program?
– xciter
May 27 '11 at 9:04
If I am at the computer I can usuallyt press cancel, but that shouldnt be necessary in the first place. Also, it did happen once (when I was not at the computer) that the computer did a hard reboot...
– Ted
May 28 '11 at 18:38
add a comment |
I recon this is a windows issue. Windows Vista and 7 actually cache a lot of the RAM memory. Can you ignore the warning and continue with your normal work or it forces you to close the program?
– xciter
May 27 '11 at 9:04
If I am at the computer I can usuallyt press cancel, but that shouldnt be necessary in the first place. Also, it did happen once (when I was not at the computer) that the computer did a hard reboot...
– Ted
May 28 '11 at 18:38
I recon this is a windows issue. Windows Vista and 7 actually cache a lot of the RAM memory. Can you ignore the warning and continue with your normal work or it forces you to close the program?
– xciter
May 27 '11 at 9:04
I recon this is a windows issue. Windows Vista and 7 actually cache a lot of the RAM memory. Can you ignore the warning and continue with your normal work or it forces you to close the program?
– xciter
May 27 '11 at 9:04
If I am at the computer I can usuallyt press cancel, but that shouldnt be necessary in the first place. Also, it did happen once (when I was not at the computer) that the computer did a hard reboot...
– Ted
May 28 '11 at 18:38
If I am at the computer I can usuallyt press cancel, but that shouldnt be necessary in the first place. Also, it did happen once (when I was not at the computer) that the computer did a hard reboot...
– Ted
May 28 '11 at 18:38
add a comment |
2 Answers
2
active
oldest
votes
Your problem is with Virtual Memory.
Applications ask windows to commit a certain amount of virtual memory to it. This does not mean the application will use all the memory committed, only that Windows promises to make it available if need be. When you look at memory usage only memory actually being used is show, not how much virtual memory has been committed to the process.
The commit limit of windows is RAM plus pagefile, because windows won't make a commitment it can't keep. So you have a commit limit of 12.4GB. Since committed virtual memory that isn't actually used does not occupy any physical space anywhere, applications aren't afraid to ask for large commitments. So it is quite common to have the virtual memory usage a lot larger than the actual memory usage.
As you I've shrunk my pagefile to make more room on my SSD. I set the initial size to 512, but the maximum size to 8GB, just so that windows can grow it if need be. Currently it is 1.4GB so the initial 8.5GB of virtual memory I had hasn't been quite enough.
You can also go hunting down the application that is using all the virtual memory. In task manager set it to show you the commit size of the running processes.
As an example: Catalyst Control Center has a Private Working Set (memory usage) on my machine of 3MB but a Commit Size of 112MB.
edited Mar 9 at 0:31
Jamie Hanrahan
19k34280
answered May 27 '11 at 13:12
Mr AlphaMr Alpha
6,23621925
Hmm, i will take a look at it nex time it happens... but its weird that windows complains that its low on memory if the apps dont reallyt use it...
– Ted
May 28 '11 at 18:38
5
The confusion comes from thinking about RAM as memory, when in many ways it isn't. Apps never use RAM, only Virtual Memory; they have no access to the RAM itself. Windows then stores some of the content of Virtual Memory in RAM for performance reasons. It is just one of many things Windows stores in RAM. In reality Widows strives to use all available RAM all the time, for content in virtual memory or to cache other things. So the complaint about memory has nothing to do with RAM. This means you can't even tell how much RAM you need on the basis of how much is used.
– Mr Alpha
May 28 '11 at 20:31
Sorry to say that, but the truth is that the windows 7 memory management is poorly written. You cannot disable or have smaller paging file, whatever be the size of RAM. Even if I enable paging file, I do not expect the paging to happen when RAM is still free (or used for cache), unless the memory manager is stupid.
– user1969104
Apr 14 '14 at 11:11
1
@user1969104 The paging doesn't happen, nor it is used for cache. It just needs to be available. The memory manager is being smart and safe. It won't write checks it can't cash, even if it's very unlikely that all its checks will be cashed at once.
– David Schwartz
Apr 24 '14 at 17:38
I believe that the memory used for cache is not reused as fast for the real memory needs. If there is lot of RAM, most memory is used for cache most of the times, and any new memory need is not immediately served from the cache leading to the low memory display and unnecessary paging. I did not analyze this, but cannot reason why, in-spite of David's effort to explain the difference between check and money. @David, I think backing store is RAM+Paging size and you seem to explain backing store as something independent of RAM size.
– user1969104
Jul 21 '14 at 22:19
|
show 14 more comments
Using a page file so much smaller than your RAM is probably the issue. Windows will be trying to pass idle app memory off onto disk and it'll get upset.
Usually the auto settings work out well, but you do seem to have a high ratio of RAM to disk space so I understand why that may be a problem.
answered May 27 '11 at 10:04
Rory AlsopRory Alsop
3,0871531
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f289302%2fwindows-7-page-file-disabled-12-gb-ram-2-gb-ram-free-and-your-computer-i%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Your problem is with Virtual Memory.
Applications ask windows to commit a certain amount of virtual memory to it. This does not mean the application will use all the memory committed, only that Windows promises to make it available if need be. When you look at memory usage only memory actually being used is show, not how much virtual memory has been committed to the process.
The commit limit of windows is RAM plus pagefile, because windows won't make a commitment it can't keep. So you have a commit limit of 12.4GB. Since committed virtual memory that isn't actually used does not occupy any physical space anywhere, applications aren't afraid to ask for large commitments. So it is quite common to have the virtual memory usage a lot larger than the actual memory usage.
As you I've shrunk my pagefile to make more room on my SSD. I set the initial size to 512, but the maximum size to 8GB, just so that windows can grow it if need be. Currently it is 1.4GB so the initial 8.5GB of virtual memory I had hasn't been quite enough.
You can also go hunting down the application that is using all the virtual memory. In task manager set it to show you the commit size of the running processes.
As an example: Catalyst Control Center has a Private Working Set (memory usage) on my machine of 3MB but a Commit Size of 112MB.
edited Mar 9 at 0:31
Jamie Hanrahan
19k34280
answered May 27 '11 at 13:12
Mr AlphaMr Alpha
6,23621925
Hmm, i will take a look at it nex time it happens... but its weird that windows complains that its low on memory if the apps dont reallyt use it...
– Ted
May 28 '11 at 18:38
5
The confusion comes from thinking about RAM as memory, when in many ways it isn't. Apps never use RAM, only Virtual Memory; they have no access to the RAM itself. Windows then stores some of the content of Virtual Memory in RAM for performance reasons. It is just one of many things Windows stores in RAM. In reality Widows strives to use all available RAM all the time, for content in virtual memory or to cache other things. So the complaint about memory has nothing to do with RAM. This means you can't even tell how much RAM you need on the basis of how much is used.
– Mr Alpha
May 28 '11 at 20:31
Sorry to say that, but the truth is that the windows 7 memory management is poorly written. You cannot disable or have smaller paging file, whatever be the size of RAM. Even if I enable paging file, I do not expect the paging to happen when RAM is still free (or used for cache), unless the memory manager is stupid.
– user1969104
Apr 14 '14 at 11:11
1
@user1969104 The paging doesn't happen, nor it is used for cache. It just needs to be available. The memory manager is being smart and safe. It won't write checks it can't cash, even if it's very unlikely that all its checks will be cashed at once.
– David Schwartz
Apr 24 '14 at 17:38
I believe that the memory used for cache is not reused as fast for the real memory needs. If there is lot of RAM, most memory is used for cache most of the times, and any new memory need is not immediately served from the cache leading to the low memory display and unnecessary paging. I did not analyze this, but cannot reason why, in-spite of David's effort to explain the difference between check and money. @David, I think backing store is RAM+Paging size and you seem to explain backing store as something independent of RAM size.
– user1969104
Jul 21 '14 at 22:19
|
show 14 more comments
Your problem is with Virtual Memory.
Applications ask windows to commit a certain amount of virtual memory to it. This does not mean the application will use all the memory committed, only that Windows promises to make it available if need be. When you look at memory usage only memory actually being used is show, not how much virtual memory has been committed to the process.
The commit limit of windows is RAM plus pagefile, because windows won't make a commitment it can't keep. So you have a commit limit of 12.4GB. Since committed virtual memory that isn't actually used does not occupy any physical space anywhere, applications aren't afraid to ask for large commitments. So it is quite common to have the virtual memory usage a lot larger than the actual memory usage.
As you I've shrunk my pagefile to make more room on my SSD. I set the initial size to 512, but the maximum size to 8GB, just so that windows can grow it if need be. Currently it is 1.4GB so the initial 8.5GB of virtual memory I had hasn't been quite enough.
You can also go hunting down the application that is using all the virtual memory. In task manager set it to show you the commit size of the running processes.
As an example: Catalyst Control Center has a Private Working Set (memory usage) on my machine of 3MB but a Commit Size of 112MB.
edited Mar 9 at 0:31
Jamie Hanrahan
19k34280
answered May 27 '11 at 13:12
Mr AlphaMr Alpha
6,23621925
Hmm, i will take a look at it nex time it happens... but its weird that windows complains that its low on memory if the apps dont reallyt use it...
– Ted
May 28 '11 at 18:38
5
The confusion comes from thinking about RAM as memory, when in many ways it isn't. Apps never use RAM, only Virtual Memory; they have no access to the RAM itself. Windows then stores some of the content of Virtual Memory in RAM for performance reasons. It is just one of many things Windows stores in RAM. In reality Widows strives to use all available RAM all the time, for content in virtual memory or to cache other things. So the complaint about memory has nothing to do with RAM. This means you can't even tell how much RAM you need on the basis of how much is used.
– Mr Alpha
May 28 '11 at 20:31
Sorry to say that, but the truth is that the windows 7 memory management is poorly written. You cannot disable or have smaller paging file, whatever be the size of RAM. Even if I enable paging file, I do not expect the paging to happen when RAM is still free (or used for cache), unless the memory manager is stupid.
– user1969104
Apr 14 '14 at 11:11
1
@user1969104 The paging doesn't happen, nor it is used for cache. It just needs to be available. The memory manager is being smart and safe. It won't write checks it can't cash, even if it's very unlikely that all its checks will be cashed at once.
– David Schwartz
Apr 24 '14 at 17:38
I believe that the memory used for cache is not reused as fast for the real memory needs. If there is lot of RAM, most memory is used for cache most of the times, and any new memory need is not immediately served from the cache leading to the low memory display and unnecessary paging. I did not analyze this, but cannot reason why, in-spite of David's effort to explain the difference between check and money. @David, I think backing store is RAM+Paging size and you seem to explain backing store as something independent of RAM size.
– user1969104
Jul 21 '14 at 22:19
|
show 14 more comments
Your problem is with Virtual Memory.
Applications ask windows to commit a certain amount of virtual memory to it. This does not mean the application will use all the memory committed, only that Windows promises to make it available if need be. When you look at memory usage only memory actually being used is show, not how much virtual memory has been committed to the process.
The commit limit of windows is RAM plus pagefile, because windows won't make a commitment it can't keep. So you have a commit limit of 12.4GB. Since committed virtual memory that isn't actually used does not occupy any physical space anywhere, applications aren't afraid to ask for large commitments. So it is quite common to have the virtual memory usage a lot larger than the actual memory usage.
As you I've shrunk my pagefile to make more room on my SSD. I set the initial size to 512, but the maximum size to 8GB, just so that windows can grow it if need be. Currently it is 1.4GB so the initial 8.5GB of virtual memory I had hasn't been quite enough.
You can also go hunting down the application that is using all the virtual memory. In task manager set it to show you the commit size of the running processes.
As an example: Catalyst Control Center has a Private Working Set (memory usage) on my machine of 3MB but a Commit Size of 112MB.
edited Mar 9 at 0:31
Jamie Hanrahan
19k34280
answered May 27 '11 at 13:12
Mr AlphaMr Alpha
6,23621925
Your problem is with Virtual Memory.
Applications ask windows to commit a certain amount of virtual memory to it. This does not mean the application will use all the memory committed, only that Windows promises to make it available if need be. When you look at memory usage only memory actually being used is show, not how much virtual memory has been committed to the process.
The commit limit of windows is RAM plus pagefile, because windows won't make a commitment it can't keep. So you have a commit limit of 12.4GB. Since committed virtual memory that isn't actually used does not occupy any physical space anywhere, applications aren't afraid to ask for large commitments. So it is quite common to have the virtual memory usage a lot larger than the actual memory usage.
As you I've shrunk my pagefile to make more room on my SSD. I set the initial size to 512, but the maximum size to 8GB, just so that windows can grow it if need be. Currently it is 1.4GB so the initial 8.5GB of virtual memory I had hasn't been quite enough.
You can also go hunting down the application that is using all the virtual memory. In task manager set it to show you the commit size of the running processes.
As an example: Catalyst Control Center has a Private Working Set (memory usage) on my machine of 3MB but a Commit Size of 112MB.
edited Mar 9 at 0:31
Jamie Hanrahan
19k34280
answered May 27 '11 at 13:12
Mr AlphaMr Alpha
6,23621925
edited Mar 9 at 0:31
Jamie Hanrahan
19k34280
edited Mar 9 at 0:31
Jamie Hanrahan
19k34280
edited Mar 9 at 0:31
Jamie Hanrahan
19k34280
19k34280
answered May 27 '11 at 13:12
Mr AlphaMr Alpha
6,23621925
answered May 27 '11 at 13:12
Mr AlphaMr Alpha
6,23621925
answered May 27 '11 at 13:12
Mr AlphaMr Alpha
6,23621925
6,23621925
Hmm, i will take a look at it nex time it happens... but its weird that windows complains that its low on memory if the apps dont reallyt use it...
– Ted
May 28 '11 at 18:38
5
The confusion comes from thinking about RAM as memory, when in many ways it isn't. Apps never use RAM, only Virtual Memory; they have no access to the RAM itself. Windows then stores some of the content of Virtual Memory in RAM for performance reasons. It is just one of many things Windows stores in RAM. In reality Widows strives to use all available RAM all the time, for content in virtual memory or to cache other things. So the complaint about memory has nothing to do with RAM. This means you can't even tell how much RAM you need on the basis of how much is used.
– Mr Alpha
May 28 '11 at 20:31
Sorry to say that, but the truth is that the windows 7 memory management is poorly written. You cannot disable or have smaller paging file, whatever be the size of RAM. Even if I enable paging file, I do not expect the paging to happen when RAM is still free (or used for cache), unless the memory manager is stupid.
– user1969104
Apr 14 '14 at 11:11
1
@user1969104 The paging doesn't happen, nor it is used for cache. It just needs to be available. The memory manager is being smart and safe. It won't write checks it can't cash, even if it's very unlikely that all its checks will be cashed at once.
– David Schwartz
Apr 24 '14 at 17:38
I believe that the memory used for cache is not reused as fast for the real memory needs. If there is lot of RAM, most memory is used for cache most of the times, and any new memory need is not immediately served from the cache leading to the low memory display and unnecessary paging. I did not analyze this, but cannot reason why, in-spite of David's effort to explain the difference between check and money. @David, I think backing store is RAM+Paging size and you seem to explain backing store as something independent of RAM size.
– user1969104
Jul 21 '14 at 22:19
|
show 14 more comments
Hmm, i will take a look at it nex time it happens... but its weird that windows complains that its low on memory if the apps dont reallyt use it...
– Ted
May 28 '11 at 18:38
5
The confusion comes from thinking about RAM as memory, when in many ways it isn't. Apps never use RAM, only Virtual Memory; they have no access to the RAM itself. Windows then stores some of the content of Virtual Memory in RAM for performance reasons. It is just one of many things Windows stores in RAM. In reality Widows strives to use all available RAM all the time, for content in virtual memory or to cache other things. So the complaint about memory has nothing to do with RAM. This means you can't even tell how much RAM you need on the basis of how much is used.
– Mr Alpha
May 28 '11 at 20:31
Sorry to say that, but the truth is that the windows 7 memory management is poorly written. You cannot disable or have smaller paging file, whatever be the size of RAM. Even if I enable paging file, I do not expect the paging to happen when RAM is still free (or used for cache), unless the memory manager is stupid.
– user1969104
Apr 14 '14 at 11:11
1
@user1969104 The paging doesn't happen, nor it is used for cache. It just needs to be available. The memory manager is being smart and safe. It won't write checks it can't cash, even if it's very unlikely that all its checks will be cashed at once.
– David Schwartz
Apr 24 '14 at 17:38
I believe that the memory used for cache is not reused as fast for the real memory needs. If there is lot of RAM, most memory is used for cache most of the times, and any new memory need is not immediately served from the cache leading to the low memory display and unnecessary paging. I did not analyze this, but cannot reason why, in-spite of David's effort to explain the difference between check and money. @David, I think backing store is RAM+Paging size and you seem to explain backing store as something independent of RAM size.
– user1969104
Jul 21 '14 at 22:19
Hmm, i will take a look at it nex time it happens... but its weird that windows complains that its low on memory if the apps dont reallyt use it...
– Ted
May 28 '11 at 18:38
Hmm, i will take a look at it nex time it happens... but its weird that windows complains that its low on memory if the apps dont reallyt use it...
– Ted
May 28 '11 at 18:38
5
5
The confusion comes from thinking about RAM as memory, when in many ways it isn't. Apps never use RAM, only Virtual Memory; they have no access to the RAM itself. Windows then stores some of the content of Virtual Memory in RAM for performance reasons. It is just one of many things Windows stores in RAM. In reality Widows strives to use all available RAM all the time, for content in virtual memory or to cache other things. So the complaint about memory has nothing to do with RAM. This means you can't even tell how much RAM you need on the basis of how much is used.
– Mr Alpha
May 28 '11 at 20:31
The confusion comes from thinking about RAM as memory, when in many ways it isn't. Apps never use RAM, only Virtual Memory; they have no access to the RAM itself. Windows then stores some of the content of Virtual Memory in RAM for performance reasons. It is just one of many things Windows stores in RAM. In reality Widows strives to use all available RAM all the time, for content in virtual memory or to cache other things. So the complaint about memory has nothing to do with RAM. This means you can't even tell how much RAM you need on the basis of how much is used.
– Mr Alpha
May 28 '11 at 20:31
Sorry to say that, but the truth is that the windows 7 memory management is poorly written. You cannot disable or have smaller paging file, whatever be the size of RAM. Even if I enable paging file, I do not expect the paging to happen when RAM is still free (or used for cache), unless the memory manager is stupid.
– user1969104
Apr 14 '14 at 11:11
Sorry to say that, but the truth is that the windows 7 memory management is poorly written. You cannot disable or have smaller paging file, whatever be the size of RAM. Even if I enable paging file, I do not expect the paging to happen when RAM is still free (or used for cache), unless the memory manager is stupid.
– user1969104
Apr 14 '14 at 11:11
1
1
@user1969104 The paging doesn't happen, nor it is used for cache. It just needs to be available. The memory manager is being smart and safe. It won't write checks it can't cash, even if it's very unlikely that all its checks will be cashed at once.
– David Schwartz
Apr 24 '14 at 17:38
@user1969104 The paging doesn't happen, nor it is used for cache. It just needs to be available. The memory manager is being smart and safe. It won't write checks it can't cash, even if it's very unlikely that all its checks will be cashed at once.
– David Schwartz
Apr 24 '14 at 17:38
I believe that the memory used for cache is not reused as fast for the real memory needs. If there is lot of RAM, most memory is used for cache most of the times, and any new memory need is not immediately served from the cache leading to the low memory display and unnecessary paging. I did not analyze this, but cannot reason why, in-spite of David's effort to explain the difference between check and money. @David, I think backing store is RAM+Paging size and you seem to explain backing store as something independent of RAM size.
– user1969104
Jul 21 '14 at 22:19
I believe that the memory used for cache is not reused as fast for the real memory needs. If there is lot of RAM, most memory is used for cache most of the times, and any new memory need is not immediately served from the cache leading to the low memory display and unnecessary paging. I did not analyze this, but cannot reason why, in-spite of David's effort to explain the difference between check and money. @David, I think backing store is RAM+Paging size and you seem to explain backing store as something independent of RAM size.
– user1969104
Jul 21 '14 at 22:19
|
show 14 more comments
Using a page file so much smaller than your RAM is probably the issue. Windows will be trying to pass idle app memory off onto disk and it'll get upset.
Usually the auto settings work out well, but you do seem to have a high ratio of RAM to disk space so I understand why that may be a problem.
answered May 27 '11 at 10:04
Rory AlsopRory Alsop
3,0871531
add a comment |
Using a page file so much smaller than your RAM is probably the issue. Windows will be trying to pass idle app memory off onto disk and it'll get upset.
Usually the auto settings work out well, but you do seem to have a high ratio of RAM to disk space so I understand why that may be a problem.
answered May 27 '11 at 10:04
Rory AlsopRory Alsop
3,0871531
add a comment |
Using a page file so much smaller than your RAM is probably the issue. Windows will be trying to pass idle app memory off onto disk and it'll get upset.
Usually the auto settings work out well, but you do seem to have a high ratio of RAM to disk space so I understand why that may be a problem.
answered May 27 '11 at 10:04
Rory AlsopRory Alsop
3,0871531
Using a page file so much smaller than your RAM is probably the issue. Windows will be trying to pass idle app memory off onto disk and it'll get upset.
Usually the auto settings work out well, but you do seem to have a high ratio of RAM to disk space so I understand why that may be a problem.
answered May 27 '11 at 10:04
Rory AlsopRory Alsop
3,0871531
edited Jan 9 '14 at 7:58
answered May 27 '11 at 10:04
Rory AlsopRory Alsop
3,0871531
answered May 27 '11 at 10:04
Rory AlsopRory Alsop
3,0871531
answered May 27 '11 at 10:04
Rory AlsopRory Alsop
3,0871531
3,0871531
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f289302%2fwindows-7-page-file-disabled-12-gb-ram-2-gb-ram-free-and-your-computer-i%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I recon this is a windows issue. Windows Vista and 7 actually cache a lot of the RAM memory. Can you ignore the warning and continue with your normal work or it forces you to close the program?
– xciter
May 27 '11 at 9:04
If I am at the computer I can usuallyt press cancel, but that shouldnt be necessary in the first place. Also, it did happen once (when I was not at the computer) that the computer did a hard reboot...
– Ted
May 28 '11 at 18:38