I've been rendering fine in 32 bit Vegas Pro 9.0 for a very, very long time (like a year or two)while updating all the time. However, just a week ago, the same exact problem happened to me, for HD or SD, depending on how large of a file it was rendering.
Sometimes it says "system memory low", and other times, it says "Sony Vegas has stopped working" and the program closes. I've heard that customer service isn't much help either...
By the way, I recently upgraded to a 64 bit OS, so I installed the 64bit version of Vegas Pro 9.0. It's been going fine for 64-Bit Vegas...
And, apparently there's another trick you can do with the 32 bit version of Sony Vegas (which most people have).
Here's the Trick:
Download "CFF Explorer" (just google it, it's free and safe) and install it. What CFF Explorer does is it can tweak ".exe" files and make them handle more than the standard 2 Gigabytes that all 32 bit applications usually handle on your PC.
FOR 64-BIT OS USERS:
These instructions are from a Sims 3 Forum where the 32 bit application for the game was also tweaked.
There are multiple ".exe" ending files in Vegas Pro, but tweaking just one of them apparently helps:
1) Download and install CFF Explorer(http://www.ntcore.com/exsuite.php)
2) Run the program, click the folder icon or go to FILE >> OPEN and browse your PC for the FileIOSurrogate.exe usually found at C:\Program Files (x86)\Sony\Vegas Pro 9.0\FileIOSurrogate.exe
IMPORTANT: Make a backup of your original exe because you will need to swap it back into your Vegas folder whenever you apply updates.
3) Click on "File Header" at the left, look at the list at the right and click the "Click here" blue button.
4) Tick "App can handle >2GB address space"
5) "Ok" that and save by clicking the disk icon or going to FILE >> SAVE. Overwrite the file when it asks you to.
Note: You need to modify the exe file that you play your game off of - meaning TS3SP01.exe for HELS, TS3EP01.exe for WA, etc.
FOR 32-BIT OS USERS:
Try this only if you have AT LEAST 2 GByte of RAM and at your own risk.
- First download the explorer from
http://www.ntcore.com/exsuite.php
- Next make a copy of FileIOSurrogate.exe found in "C:\Program Files\Sony\Vegas Pro 9.0\FileIOSurrogate". Then start "CFF Explorer" and open the original FileIOSurrogate.exe file.
- Now go to "NT Header/File Header" and click "File Header". There you will find a button labeled "click here". Click it. And select the checkbox "App can handle> 2GB address space"
- Now press the "ok"'s and when back on the main menu, click on the disk button thing (looks like Microsoft Word's "Save" button) and save the modified ".exe" file, overwrite the orginal one. (Note in Vista and 7 you must be running CFF Explorer in Administrator Mode).
- Now we need to make Windows Vista or 7 (32-Bit) ready to support more than 2 GB's (see below for XP option)
- Open command prompt with Administration rights. You find it under "Programs->Accessories->Command prompt", right click and select "run as administrator".
- Enter "bcdedit /set IncreaseUserVA 3072" (without quotes) in the command window and press enter.
After that RESTART windows
- For WINDOWS XP, don't go to command prompt. Go to "C:\boot.ini" and see where there is:
"[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect"
-TO THE END OF THE LINE (after "fastdetect"), add " /maxmem=3072" (with the space in the front, I didn't make a mistake). Also, depending on your OS, it could say "\WINDOWS="Microsoft Windows XP Home Edition" " or something (just being anal about this so that you don't ask later hehehe)
CRITICALLY IMPORTANT: The 32-bit OS method could make your system unsafe if you manage to screw up, or the information I gathered on this was screwed up (as in your computer may not boot!). So, do at your own risk please. The 64-bit OS method always works (I did it myself a few times over again to make sure), but I've never tried the 32-bit OS method before since I don't have a computer with a 32-bit OS.
I think Sony Vegas for me is working now, but I'll have to see about that later if there's yet ANOTHER bug.
Apologies for such a long post, but I hope it was helpful.