Skip navigation
Currently Being Moderated

Memory or Resource Errors - Windows Virtual Memory

May 5, 2010 4:53 PM

Tags: #memory #windows #errors #resources #virtual_memory #page_file

Users occasionally get “Out of Memory,” or “Low Resources,” messages, or something similar, when doing video editing. Usually, the first thought is “hey, I have a lot of RAM. What’s the deal here?” Well, RAM is part of the system’s memory, but is not the whole story. There is also Windows Virtual Memory, the Page File. This is HDD (Hard Disk Drive) space that serves as an overflow for RAM usage, and really comes into play with intense operations, like video editing, where everything cannot fit into RAM. Having a 64-bit OS with 64-bit programs and 24GB of fast RAM will diminish the need and use for Virtual Memory, but until all of us are running super computers with only 64-bit OS’s and programs, it is very important.

 

Now, the Virtual Memory is setup upon installation of the OS, and it defaults to being placed on the system drive, C:\, having Windows dynamically manage it (expanding and contracting it, as is needed, but more on this later), and a general size, based on the detected, installed physical RAM. For most general computing, that works fine. For video editing, things can be improved upon.

 

In XP-Pro, one would change these default settings by going to Control Panel>System>Advanced>Performance>Advanced>Change. The location of the settings will probably be similar in other versions of Windows, but one might have to poke around a bit to get there.

 

Now, let’s talk about some better settings. First, the location, will probably depend on a couple of factors. If one only has one physical HDD, then it’s a no-brainer. It will be placed on C:\. If one has two physical HDD’s, then it might be better to locate it on D:\, but one should test to see if there are any performance gains. If one has 3, or more physical HDD’s, then I would definitely locate it on the least used HDD. The idea is to spread the load amongst as many HDD’s, as is possible. With C:\, you have the OS and the programs fighting for reads and writes. If you can move the Page File to another HDD, you cut down on the fighting, however, if you move it to the HDD with your Project files, your Scratch Disks and your media, there might still be some struggle for HDD usage. If you can locate it away from the OS, the programs, the Projects and Scratch Disks and the Media, you will be doing well. Also, as the Page File is created at boot up, if you can get it onto a seldom used HDD, then you benefit in that it will be placed at the head of that HDD, which is faster, and when you defragment, it will be easy to keep this space clean and defragmented. Because the management of the Page File also plays a role here, that is our next subject.

 

With a dynamically managed Page File, the OS must anticipate the size required, and be one step ahead of the program in getting it expanded in time. This takes CPU cycles and requires a lot of monitoring by the OS. Yes, when no longer needed, the OS will contract it, but unless one has very limited HDD space, this really saves nothing, and for video editing, HDD space is extremely important, and one should not have to worry about a constant, large Page File. By being statically managed, one also gets the same size Page File written at boot up, making that defragmenting easier.

 

As to the size of the statically managed Page File, the old thinking was about 2.5x the installed physical RAM, meaning that if one had 4GB RAM, the Page File should be about 10GB. With newer OS’s, and especially 64-bit with much more RAM, that is not necessary, and a more 1:1 ratio would be fine - maybe even overkill. For 12GB RAM, a 10GB Page File is probably adequate, but if one gets Memory, or Resource messages, just bump it up to 12 - 14GB.

 

If one is receiving “Out of Memory,” or “Low on Resources,” the Page File should be one of the first things considered. The next would be the possibility of a bad stick of RAM.

 

Good luck,

 

Hunt

 
Replies
  • Currently Being Moderated
    Dec 12, 2010 12:50 AM   in reply to Bill Hunt

    Good morning. I am encountering the same issues in Elements 9  and have read your article with interest. As I am new to changing my windows 7 system settings I wondered if you could advise. Within the advanced options both C and D rrives are shown. I can select D and set up a custom min and max paging file at 10Gb. The C drive is still showing with 4Gb of paging file. How do I get the premiere elements to use D.if I set C to zero it warns that the OS may not run. Or does it automatically default to D even if C is showing?

     

    Roger

     
    |
    Mark as:
  • Currently Being Moderated
    Feb 11, 2012 3:24 PM   in reply to Bill Hunt

    Hi Bill,

    I continue to have the low memory issues that have been referred to above. 

    I have a Pentium I5 processor with 8 GB RAM

    OS Windows 7  64 bit

    System disk 1268 GBYTE SSD

    User disk with all Adobe files 1TB  Fragmented 0%  500 MB free space

    Video NVIDIA GeForce GTX 550 Ti

    Running Windows 7

     

    My project is quite small (about 10 minutes of HD video).

    Below is a screencap of one file.  They are all the same. 

    CODEC 264

    Codec.jpg

     

    I've increased the memory size using the bcdedit command as per instruction to 3072

     

    When I try and render the timeline, it seems to run ,but only a few of the red bars turn green.

    All of the video that has a red bar shows no video(only black).

    When I insert a video and hit enter, it tries to render but the bar doesn't turn green.

    I've spent many hours digging through all the forums and I seem to have done everything suggested with no results.

    Anything you can think of?

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (1)