removing "virtual memory too low" message

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello, I have a configuration with 128 MB ram and I'm not using virtual
memory (paging disabled). For some reason, windows still keeps track of page
file usage and after some time (and many applications being opened and
re-opened) I get the "virtual memory too low message". I still have enough
available physical memory to run more applications, so I think this message
is not applicable to my configuration. Does anyone know how to get rid of
this message, or an explanation to why windows is even calculating page file
usage for my system?

Thanks,
Himanshu
 
I added these to the registry:
HKLM\System\CurrentControlSet\Windows\ErrorMode REG_DWORD 2
HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer\NoLowDiskSpaceCheck
REG_DWORD 1

The first blocks all error popups and answers them with the default.
The second disables the disk space check by explorer.

I don't see the virtual memory error anymore on my system. I think the
first registry entry takes care of it.

--
Regards.
Mark K Vallevand (e-mail address removed)

Beer is living proof that God loves us and wants us to be happy.
- Benjamin Franklin


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you received
this in error, please contact the sender and delete the e-mail and its
attachments from all computers.
 
Thanks for the input Mark. Unfortunately, I don't want to remove all errors
from the system. I've seen this registry modification before and was hoping
there was a way to just get rid of the virtual memory message without
sacrificing the rest of the system messages.
Thanks,
Himanshu
 
Himanshu,

Forgot to mention that there is no particular reg.key to turn off the Low Virtual Memory error (the string is coming from Ntdll.dll,
I think).

Basically, the MM (Memory Manager on XP) makes some checks on the pagefile size and free space within the pagefile and if a "limit"
value archived (IIRC, ~90% of the pagefile is not free) it throws out that error.

The error goes to the regular OS hard error pool and higher by chain which is process independently and controlled by the registry
values mentioned in the article Slobodan has provided the link to you.

KM
 
Back
Top