View Full Version : Tech Question: Virtual Page File Memory yadda yadda
Henry4MVP
October 10th, 2004, 1:49:49 PM
For some reason, my comp gives me "Windows is low on virtual page filing memory" warning. My PF Usage under the Task Manager is over 1 GB! I've never had this problem before.
Can anybody give me a hand on understanding or fixing this? It's slowing down my comp but I'm not exactly sure what the problem is.
Forum21
October 10th, 2004, 3:08:14 PM
What os? If you are using over a gig of memory, my guess is that you have an application with a memory leak. Open up task manager, tab over to the process tab, and sort by memory utilization, note the image name that is using up all the memory. Try googling that name and see what application the process belongs to.
Does the issue go away when you reboot, but then appear again over time?
Henry4MVP
October 10th, 2004, 3:25:18 PM
I'm running Windows XP.
Yessir, it does disappear when I reboot, and then builds up again.
Forum21
October 10th, 2004, 7:45:25 PM
Memory leak.
Next time you get the error, do that task manager stuff I mentioned above to isolate the process, then go from there. Ultimatly, you will probably want to uninstall or patch (IF AVAILABLE) the offending software.
pigpen65
October 10th, 2004, 8:16:47 PM
Henry, how much virtual memory do you have allocated?
Also, if you go to start>run>type in: msconfig>startup tab you will see a list of programs that windows starts when it boots. Uncheck any program that you don't need. Should stop you're problem.
Henry4MVP
October 10th, 2004, 9:10:30 PM
Thanks, gentlemen. I've gotten that gig thing down to about 200mb maximum.
Dunno if that's good or not but my comp is at least moving along again. :)
Henry4MVP
October 10th, 2004, 9:12:07 PM
Chips donated, say thankya. :D
GOBILLSGO!!!
October 10th, 2004, 9:34:08 PM
a good rule of thumb for VM is about 1.5x the amount of RAM you have
Forum21
October 11th, 2004, 11:35:46 AM
Fair warning: I don't think you have solved your problem, just prolonged it.
Adjusting your virtual memory will not solve the problem if it is a memory leak. Windows XP sets the paging up for you at OS install as a range starting at the ammount of physical memory to 1.5 times physical, so you'll see 256 appear as 256 to 384 size of pagefile.sys. This makes total available memory 684 (talking megs here).
In the case of a memory leak, making this larger will just end in frustration, since as you run out of physical memory, your PC will begin to "swap" every operation to hard disk and your disk read/write will bring your system to a halt.
From what you described, you are going to want to solve the memory leak i.e. troubleshoot whatever application is causing your system poor performance. Of course this is harder than merely upping your swap file, but it is actually fixing the source of the problem. You can't throw hardware or OS tweaking at this problem , it's application related.
GOBILLSGO!!!
October 11th, 2004, 12:00:59 PM
agreed, find out what app is leaking...if its happening on your system, its happening on A LOT of systems and per chance the app actually has a support team, there "should" be a patch available fixxing the issue
Henry4MVP
October 11th, 2004, 12:27:00 PM
Fair warning: I don't think you have solved your problem, just prolonged it.
Adjusting your virtual memory will not solve the problem if it is a memory leak. Windows XP sets the paging up for you at OS install as a range starting at the ammount of physical memory to 1.5 times physical, so you'll see 256 appear as 256 to 384 size of pagefile.sys. This makes total available memory 684 (talking megs here).
In the case of a memory leak, making this larger will just end in frustration, since as you run out of physical memory, your PC will begin to "swap" every operation to hard disk and your disk read/write will bring your system to a halt.
From what you described, you are going to want to solve the memory leak i.e. troubleshoot whatever application is causing your system poor performance. Of course this is harder than merely upping your swap file, but it is actually fixing the source of the problem. You can't throw hardware or OS tweaking at this problem , it's application related.
I didn't adjust the VM. I shut down the app that was leaking (Kodak auto-updater for my crappy camera) and just bookmarked the homepage so I can update when necessary, since Kodak doesn't have a patch and takes forever responding to my e-mails.
I appreciate the help from all. If it happens again, I'll let ya know. :)
Forum21
October 11th, 2004, 12:49:37 PM
I didn't adjust the VM. I shut down the app that was leaking (Kodak auto-updater for my crappy camera) and just bookmarked the homepage so I can update when necessary, since Kodak doesn't have a patch and takes forever responding to my e-mails.
I appreciate the help from all. If it happens again, I'll let ya know. :)
Cool. Nothing worse the pre-installed 3rd party software causing the problem.
vBulletin® v3.7.0, Copyright ©2000-2008, Jelsoft Enterprises Ltd.