I was unable to render out a wmv file from a 14-minute project (out of memory error). Upgraded to 6.0d. I also thought I found the problem - a clip with a velocity envelope, so I removed that - rendering would stop and just count down time remaining at that spot, then time elapsed would continue incrementing, but no progress. I cleaned up the project (muted tracks, etc) - now the next try stopped at 9% into rendering. When it stops, cpu usage drops to 0. I'm running another render test now to a smaller wmv (all have been low resolution, mulimedia preview size, 320x240 or smaller).

Here's the new addition with 6.0d, cancelling render doesn't work - I have to kill Vegas in Task Manager. This is only the case when rendering hangs (cpu usage at 0).

I have 2G Ram and just set the page file to 4G, fixed, but only 1.5G are used, max - 1.2G when rendering last stopped. I've tried changing the Ram preview settings per previous threads on their impact on render times, and there was a slight difference in time predicted, but none rendered to completion. I was hoping the memory hang fix in 6.0d would solve the problem I was seeing, but it doesn't seem to be the same issue.

FYI, with wmv renders, ram preview still makes a difference - with 0, I only get 60% cpu usage and longer render times. With 128, it runs 98%+ on both cpus (X2 4400).

Any ideas? So far I've only tried rendering to wmv as I don't have time to wait for a full res render - have to get a preview to a client this morning.