Muhammad Khan’s Answer:
I’ll assume you’re running Windows XP, and see a message stating “Your system is low on virtual memory. Windows is increasing the size of your paging file Virtual Memory. “Unless you have very little physical memory (RAM) in your system, this message indicates a request for a buggy with a memory leak.
A computer memory leak is a basic trouble caused by poorly written or sick debugged app where they continually apply storage many until you end the program, all the process manually or restart Microsoft Windows.
Virtual storage, also known as a page file or swap file is a file on your disk drive (C: \ pagefile.sys by default) that Windows and applications apply some physical storage (RAM) required. The default and recommended size of this file is 1.5 times the amount of physical memory. Virtual memory is the sum of physical memory and the swap file. So if your computer has 512MB of RAM, it will have a 768MB file the default page for a total of 1.25GB physical + virtual memory.
Find the source of the problem
You must first determine which application is causing the problem.
Hit Control-Alt-Del to bring up Task Manager (on certain XP Professional configurations you’ll need to click the Task Manager Button after hitting Ctrl-Alt-Del). You can too access the Task Manager by pressing Ctrl and Shift and pressing Escape.
Attend the Processes tab of Task Manager. Here you’ll view a list of complete processes (applications or parts thereof) that are keeping going your system. You’ll look the storage usage here, but in my experience this is very rare has nothing to do with the problems of lack of virtual memory.
Click View, Select Columns.
Check the size of the virtual memory, as circled in the screenshot below and click OK.
Now you have a VM Size column in your Processes tab. Click the top of the column size VM (as circled below) twice to arrange the processes by their VM size largest to smallest.
You will see in this Task Manager shot that Mozilla Firefox are the most virtual memory at about 237 MB, with Internet Explorer next largest at about 81 MB. (The number of KB divided by 1024 equals MB) For both, it’s the effect of leaving them open for many than a week straight. Virtually complete app apply a few storage, the a few you leave it open, even if some are worse than others. This is one reason that Windows becomes increasingly insensitive that the more you run, and why you end up ending to restart your computer regularly.
Once you determine what process is using more virtual memory than it should, you must determine what the process is. Some are fairly obvious, like winword.exe is Microsoft Word, iexplore.exe is Internet Explorer, and so on. Others are not so obvious. The best way to determine the source of a specific process is to use a search engine to find the name of the image as shown in the Task Manager.
Now that you know where the demand is the problem, we will solve it.
A common thing is to try to uninstall and reinstall the offending app if possible. Research on the Internet and checking the support site of the software vendor would be two steps I would try. Without knowing which application is at fault, it is difficult to recommend a specific solution.
Thank you to Chris Buechler for his invaluable help with this tricky puzzle.