[Caitlin Smith] “Fault Address: 0x000007FED74138D1
FX used: Chroma keyer, text, Sony checkerboard, Sony noise texture, Sony gradient, crop, transitions”
Caitlin, unfortunately I can’t see the FAULT Module, (you’ve drawn that RED line through it), which sometimes, for me, identifies, indicates just what Vegas could be choking on.
You could could try:
1]By-passing all the FXs, and see if it still chokes
2]Add-back the FX-ing one-by-one till you discover just which FX is choking Vegas.
3] Try doing segmented Rendering. Sometimes I’ve needed to go down to render-sets of 10 Seconds to determine that I had had a nasty high-math or math-rich render going on. It happens to ALL of us.
Remember, Rendering is THE most CPU<>GPU intensive procedure that Vegas needs to perform . . . which reminds me:
What are you rendering FROM and what are you rendering TO?
Maybe we should start from here – yes? If you have issues with your Media to Project Settings and/or your PC is groaning under the weight of the render, it is going to be here that you’re going to hear the “Pips Squeak” and squeal.
Grazie
Video Content Creator and Potter
PC 7 64-bit 16gb * Intel® Core™i7-2600k Quad Core 3.40GHz * 2GB NVIDIA GEFORCE GTX 560 Ti
Cameras: Canon XF300 + PowerShot SX50HS Bridge