I would also move up to Vegas Pro 8.0c... you never know what bugs could have been fixed to help in your situation.

~jr

Many thanks guys, I'll do all suggestions. Just downloaded "c" and will install it.
ST

be sure to play it safe: 8.0c projects don't work in previous versions (at least I don't think so). Be sure to save as a new filename, just in case!

Thanks!
ST

Is Quicktime involved in your media? I had this message recently trying to play mov files. I had both the Apple Quicktime and Quicktime Alternative installed on this PC. I uninstalled both and reinstalled Quicktime. That fixed the messages for me. I had no reason to believe I had an actual memory shortage problem.

Not sure if any of this applies in your case, but thought it was worth mentioning.

Just a note which may or may not be the case here. Not all low memory erros in Winodws have anything to do with the amount of ram. If too many "handles" are open, Windows reports low memory...
This article explains it better than I could, and gives some ways of alleviating the problem: http://weblogs.asp.net/mikedopp/archive/2008/05/16/increasing-user-handle-and-gdi-handle-limits.aspx

The Low on Memory error is Windows trying to tell you that it could not find the memory it needs to complete a task. It almost never means that you don't have enough RAM. Thank Microsoft for yet another meaningless error message.

A GDI flood is one way that a poorly written driver or program can cause a system reboot. Every program creates some GDI (Graphics Device Interface). Basically, anything written, printed or drawn on the screen, printer paper or other output device has some GDI's, so there could be thousands at any time. Go to http://www.nirsoft.net/ and download their freeware program called GDIView.exe. It will tell you which applications and processes have created GDI's, and how many. If this is your problem, one of the programs will have several thousands of GDI's. As expected, any graphically intense program such as Photoshop, Vegas, etc, will have thousands of GDI's, so don't freak out. Unless the total only goes up every time you check, then the program may have a GDI leak.

However, "System Low on Memory" can also be caused by a badly fragged pagefile. When Windows needs to swap to a pagefile, it looks for a contiguous piece of RAM in the pagefile. [Note, Windows doesn't *need* a contiguous block of RAM, it just looks for one when it manages the pagefile because it's easier to manage.] One way to fix this is to use a fixed pagefile size. Windows will run faster because it doesn't have to manage the pagefile size, and it doesn't have to look for a contiguous block of RAM.

I didn't notice this in the article I ref'ed: sometimes just minimizing the application will free up handles. It's visible controls that eat the handles. You'll see this effect sometimes when restoring a minimized window...it spends an inordinate amount of time showing back up. That's the handles being reallocated (among other things, of course. The OS may just be busy with other things, too.)