If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Virtual Memory Too Low
Win XP Pro. Physical 3.2G Available 1.2G Virtual 2.1G Why this message ? Virtual Memory Too Low |
Ads |
#2
|
|||
|
|||
Virtual Memory Too Low
On Sun, 23 Sep 2018 11:59:59 -0700, OGER wrote:
Win XP Pro. Physical 3.2G Available 1.2G Virtual 2.1G Why this message ? Virtual Memory Too Low It's when an application tries to allocate memory which is larger than the available physical or virtual memory. It depends on the application, since it can choose the memory storage between physical, or both physical and virtual. Check the virtual memory setting from the System control panel (or press WIN+Pause). Open the Advanced System Settings. Open the Performance Settings. On the Advanced tab, click the Change button. Tick/set the topmost checkbox to let the system manage the virtual memory size. |
#3
|
|||
|
|||
Virtual Memory Too Low
On Mon, 24 Sep 2018 02:52:15 +0700, JJ wrote:
Open the Advanced System Settings. That would be the Advanced tab, in Windows XP. |
#4
|
|||
|
|||
Virtual Memory Too Low
On 23/09/2018 19:59, OGER wrote:
Win XP Pro. Physical 3.2G Available 1.2G Virtual 2.1G Why this message ? Virtual Memory Too Low The optimal memory size should be 1.5 times your physical RAM. So if your ram is 2GB then your virtual amount should be 3GB and so you have 5GB to play with. Some would even go for twice the amount to make total available 6GB in my example of 2GB. I chose 2GB because this is what most people have on their XP machine. For Windows 10 people normally have 8GB so it is a good candidate to make it 1.5 times 8GB = 12GB; Total makes it 20GB. What were you doing to get this horrible message? It must be very memory hungry App. Hey OGER, how's life treating you? -- With over 950 million devices now running Windows 10, customer satisfaction is higher than any previous version of windows. |
#5
|
|||
|
|||
Virtual Memory Too Low
? Good Guy ? wrote:
On 23/09/2018 19:59, OGER wrote: Win XP Pro. Physical 3.2G Available 1.2G Virtual 2.1G Why this message ? Virtual Memory Too Low The optimal memory size should be 1.5 times your physical RAM. So if your ram is 2GB then your virtual amount should be 3GB and so you have 5GB to play with. Gibberish. Each process in your machine is allocated a virtual memory space to run in. For 32-bit machines, that space is 4GB. Half of that is reserved for the OS, the rest is available for the program. *Each* process has a 4GB virtual space. Clearly, if you have a lot of processes and not much physical memory, you're going to use your swap file a lot, and all that disk access is going to slow down your computer. The Windows OS handles the swap file efficiently. I'd guess GoodGuy is talking about manually setting the size of that file, but I'd let the OS handle it. I can't think of any reason to restrict the size of the swap file. -- Tim Slattery tim at risingdove dot com |
#6
|
|||
|
|||
Virtual Memory Too Low
OGER wrote:
Win XP Pro. Physical 3.2G Available 1.2G Virtual 2.1G Why this message ? Virtual Memory Too Low Virtual memory = pagefile (on disk) https://en.wikipedia.org/wiki/Virtual_memory Despite articles telling you that you can reduce the pagefile to [near] zero when you have gobs of system RAM, that causes many programs to fail or become crippled. For example, video games will often pre-load lots of textures and object into the pagefile so it is available on demand instead of having to do file I/O calls to open and read from files on the disk. Although the pagefile is also on the disk, accessing data from it is faster than doing file I/O. Many programs want to use virtual memory. They can make a minimal request which if disallowed means they fail to load their data and can error, crash, or become crippled along with asking for a maximum reserve which they might like to use but might not get depending on the current availability. https://www.howtogeek.com/126430/htg...ou-disable-it/ You should always have some pagefile space. Even the OS wants some. Ideally you would set it to the min() of the minimum request by all programs you run or may run later, including the OS; however, knowing that minimum value is tough to impossible. Just because the pagefile is set to, say, a maximum of 6GB doesn't mean it uses it all on the disk. Depends on how you have the min and max configured for pagefile size. With gobs of system RAM (4GB really is not gobs of RAM nowadays), some recommended setting the pagefile to half of the system RAM but that's just a guess. Could be too much, could be too little, depends on what you run under that OS. Looks like half is too little for you. You might have so many progams consuming the pagefile (fixed for its maximum size) that there is no more space for another program to request its minimum virtual memory allocation. As for the given example, could be you are loading a video game but there just isn't enough paging space left for it to use. No info on what processes were running at the time. Back in Windows XP, and without knowing what will want to use the pagefile (other than the OS), the recommendation was to set the pagefile size to 1.5 times the physical RAM size. You say you have 3.2GB. That looks like you probably have 4GB of physical system RAM of which the OS will allocate only up to 3.2GB to user-mode memory space (without tweaking some OS config which you shouldn't get into). Per the recommendation, your pagefile should be 6GB. However, that probably would likely be a waste of disk space unless you are running a program that wants huge amounts of pagefile space or running multiple programs with each wanting a large amount of pagefile space. 4GB of pagefile should be sufficient for you but 2.1GB for pagefile space is only about half of your system RAM. Is Windows XP configured to have it determine the size of the pagefile or did you fix it to a value of 2.1GB? https://www.geeksinphoenix.com/blog/...indows-XP.aspx If you set a different minimum and maximum (reserve) size for the pagefile, it can get fragmented. A trick to prevent fragmenting the pagefile is to set the minimum and maximum size to the same value. You then need to delete the current pagefile, defrag, and reboot Windows to have it create a new 1-fragment pagefile. You could leave the pagefile configured to let the OS figure out its size. That will result in fragmentation of the pagefile. You could use a min value to save some disk space unless needed up to the max value but that causes fragging. If, say, you wanted 2GB for min and 6GB for max, the difference is 4GB. If 4GB is so tight on free space for the drive even after cleanup, it's time to consider getting a newer and bigger drive. Did you configure just the drive for the OS partition to have a pagefile or did you split the pagefile across two, or more, drives? |
#7
|
|||
|
|||
Virtual Memory Too Low
You didn't say WHAT you tried to run that resulted in the "too low"
prompt. Here's an example of software that wants to use the pagefile and complains if there isn't enough: https://support.microsoft.com/en-us/...you-try-to-sta |
#8
|
|||
|
|||
Virtual Memory Too Low
In message , Tim Slattery
writes: ? Good Guy ? wrote: On 23/09/2018 19:59, OGER wrote: Win XP Pro. Physical 3.2G Available 1.2G Virtual 2.1G Why this message ? Virtual Memory Too Low The optimal memory size should be 1.5 times your physical RAM. So if your ram is 2GB then your virtual amount should be 3GB and so you have 5GB to play with. Gibberish. Each process in your machine is allocated a virtual memory [] This "page file should be x times actual RAM" is something I remember from the days of Windows 3.1 and typical memory sizes of 4 M (yes, M not G!). I never understood it even then: to me, the _more_ RAM you have, the _less_ you're likely to need virtual RAM. There was a slight reason for it, _if_ you agreed with the following suggestion: that someone who has x amount of real RAM is likely to _run_ certain types of application. As VanguardLH said, it's probably wise to have _some_ virtual RAM in case of the unexpected, and also to set minimum and maximum to the same - and delete the previous one - to ensure it is created, and remains, unfragmented. -- J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf You make it from scratch? Yep. Do you make your own scratch? -- "pyotr filipivich" in alt.windows7.general 2017-5-20 |
#9
|
|||
|
|||
Virtual Memory Too Low
OGER wrote:
Win XP Pro. Physical 3.2G Available 1.2G Virtual 2.1G Why this message ? Virtual Memory Too Low Even though nothing in your message appears to be copied verbatim from your WinXP setup, I'll toss this one out as an explanation for sudden demand like that. Apparently, Windows Media Player can act as a streaming server, and a video which doesn't parse properly causes WMP Network Sharing Service to go nuts and use up 2GB (the process grows until it cannot ask for any more memory). http://www.tomshardware.com/answers/...ory-usage.html Now, if that's not it, perhaps you can share with us, what's running on the system, and whether those items are using a lot of RAM or not. ******* These are some notifications for WinXP: 1) "Windows - Virtual Memory Minimum Too Low" 2) "Windows - Out of Virtual Memory" Paul |
#10
|
|||
|
|||
Virtual Memory Too Low
On Sun, 23 Sep 2018 23:30:38 +0100, J. P. Gilliver (John) wrote:
As VanguardLH said, it's probably wise to have _some_ virtual RAM in case of the unexpected, and also to set minimum and maximum to the same - and delete the previous one - to ensure it is created, and remains, unfragmented. Actually, the page file must be at least the same size as the memory allocated by kernel - which vary accross different system setups. That'll ensure successful dump when BSOD occured. Otherwise, either the dump would fail, or the system would crash completely. |
Thread Tools | |
Display Modes | |
|
|