i usually use sony's mp4 with good results

Me too. I only use Sonys MP4

/Ulf

Built-in graphics. Oh dear. Never mind. There have been numerous threads on dealing with low memory render crashes, but I haven't come across this on 64 bit. 10c. You could try downloading and running Large Address Aware from the techPowerUp forum on one of your Vegas exe's and see if that fixes the problem - it works well for VMS. (backup first). Please let us know what happens.

In the past many Vegas users have had this memory problem.

Can you play the incomplete video?
Does it crash on a specific large JPG?

If you are rendering using Vegas 10 32 bit, your render has available the same amount of memory as you had on your old PC. Try 64 bit.

/jerry

I, too, have had this problem often - including on my 64-bit versions of Vegas (on an i7 w/12GB RAM). But I found a 100% foolproof solution (at least, ever since 64-bit Win7 became available). I do this:

1. Render all clips to Cineform before putting them on the TL - I always edit in Vegas 8C-32 bit.
2. After editing the project in 8c, I open the project in 9c-64 bit and render out to Cineform.
3. Then I put the Cineform render on the TL, again in 9c-64 and render to whatever format I choose (I'm now beginning to render to DNxHD in order to use Handbrake to create the .MP4 file for the web).

Even my most complicated, 1-hour 40 min. progressive projects render rock-solid stable by following this (admittedly cumbersome) procedure (in those rare instances where I begin with an interlaced clip, I render it to Cineform progressive using Mike Crash Smart Deinterlace). The only time in my memory that this procedure failed was when I had an .MP3 audio file on the TL; replacing it with a .WAV version solved that problem.

Incidentally, I prefer .PNGs on the TL, but usually wind up with lots of .JPGs. Only occasionally does an exceptionally large .JPG cause a problem (during editing in 8c, not during rendering).

I think I got it. It has to do with the video files you are using within the project. I noticed that my buddies files that he sent me were driving up my memory use till it crashed. It was a re-muxed .MP4 that was made from a ustream .FLV. I noticed that if you "right click" the file in the "Project Media" and check out the properties, on my buddies files it looked like this;
_________________________
General
Name: 01.mp4
Folder: R:\ejn\2014-04-06 EJN Citrus
Type: Sony AVC
Size: 38.89 MB (39,820,181 bytes)
Created: Sunday, April 27, 2014, 4:16:35 PM
Modified: Sunday, April 27, 2014, 4:17:37 PM
Accessed: Wednesday, May 07, 2014, 4:22:57 PM
Attributes: Archive

Streams
Video: 00:07:12.000, 120.000 fps progressive, 854x480x12, AVC
Audio: 00:07:11.968, 44,100 Hz, Stereo, AAC

ACID information
ACID chunk: no
Stretch chunk: no
Stretch list: no
Stretch info2: no
Beat markers: no
Detected beats: no

Other metadata
Regions/markers: no
Command markers: no

Media manager
Media tags: no

Plug-In
Name: compoundplug.dll
Folder: C:\Program Files\Sony\Vegas Pro 11.0\FileIO Plug-Ins\compoundplug
Format: Sony AVC
Version: Version 11.0 (Build 701) 64-bit
Company: Sony Creative Software Inc.
_____________________________
It says in there "120 FPS" and when I noticed this I was like WTF!
Something is jacked up cause my memory would be running around 50% and within about 3 minutes (clip time) of rendering that file my memory usage ramped up to 100%. So unfortunately I had to re-render the file in a different app, like Format Factory. LAME! Especially cause the codex listed on the file seems to be a sony format. Doesn't do it with my files, so he must have screwed something up in his Wirecast format that he was streaming with.
Hope it helps. ~J