I don't have vegas, just DVD architech, I've tried to transcode my video to native DVD format with handbreak but doesn't seem to help, perhaps you know a better way of doing this ?

Then, you are using DVDA Studio, not DVDA Pro?

Nontheless, if you go to the Vegas forum and search for "Low Memory", you will find dozens of posts. Basically, it's a PC problem.

OK, it's been a while since I posted this on the DVDA forum, so here it is. Again.

Low Memory or Out of Memory does not mean "Not enough RAM", though adding RAM can sometimes fix a "Low Memory" waning. A "Low Memory" warning usually means that you have exceeded your commit limit. You need either a bigger page file, more physical memory, or both.

One of the biggest sources of confusion over Windows memory usage is the whole concept of virtual memory compared to physical memory. Windows organizes memory, physical and virtual, into pages. Each page is a fixed size (typically 4 KB). To make things more confusing, there’s also a page file (sometimes referred to as a paging file and dynamic RAM). Many Windows users still think of this as a swap file, a bit of disk storage that is only called into play when you absolutely run out of physical RAM. In versions of Windows starting with Vista, that is no longer the case. The most important thing to realize is that physical memory and the page file added together equal the commit limit, which is the total amount of virtual memory that all processes can reserve and commit.

Start the Task Manager, click on the "Processes" tab, then click on "Commit Size" to sort by size. This will show you which processes are memory hogs that you may be able to shut down.

All Windows since XP (and Unix/Linux for that matter) always wants to have page space. Always. Programs (including drivers and codecs) like to and are allowed to pre-allocate as much memory as they want. Even if they are never ever going to actually use it. Sometimes those programs properly deallocate memory, sometimes they don't (resulting in "memory leak"). Sometimes, programs leave parts of themselves in allocated memory just in case you are going to run that program again. (MS Word, Excel and other Office programs are particularly adept at this). If you have no page file and a program wants to commit some for itself, your PC will crash (AKA, BSOD, or Blue Screen of Death).

Paging file configuration is in the System properties, which you can get to by typing "sysdm.cpl" into the Run dialog, clicking on the Advanced tab, clicking on the Performance Options button, clicking on the Advanced tab, and then clicking on the Change button. I would suggest a value of 1.5X the currently allocated value. The old advice of 2X or 3X your RAM is, well, old advice when a few MB of RAM was normal. 64-bit Windows can having paging files that are up to 16TB in sizeand supports up to 16 paging files, where each must be on a separate volume."


Also, Windows supports up to 16 paging files, but each must be on a separate volume, so if you have more than one internal disk drive you could try enabling a Paging File on your second hard-disk. DO NOT put a paging file on an external drive because if it's not present when Windows boots, then Windows will crash.

For more information, see http://blogs.technet.com/b/markrussinovich/archive/2008/11/17/3155406.aspx