Have you checked for a heat problem. Clean out the vents and fans or even open the side of the computer.

https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-stop-vegas-pro-hanging-or-crashing-during-rendering--104786/

OK I was able to get a render off. Here are some more details

Drive crasjed last week so I had a fresh instasll
all of the data files were on an external drive and safe
Vegas is now on the new C drive with the OS (win 10)
I'm using New BlueFX Titler Pro3 for some tutling and effects
This is a video of highlights from a conference, so there are a lot of clips and editing
This is version 3 ( to give an idea of how much editing m,ay be involved. I'm not sure how to give details without getting crazy)
This particular project frequently crashes
I rebooted several times
I was rendering MP4 1080 30fps, Tried 720, and even the Internet NTSC widescreen....still crashed
I WAS going to try rendering in chunks to see if I could isolate a particular problem area.
I was rendering to the external drive
I decided to try rendering to the desktop (C drive) and that seemed to go through without a crash!!!!!
There was a track muter that should not have been.... so I'm going to give it another test and hopefully I can get consistent renders

Thanks for the help. I will report back later!!!

Have you checked for a heat problem. Clean out the vents and fans or even open the side of the computer.

 

Yes,,, I keep my desktop open and blow it out refularly

What version of Dell i7, GPU, disk types, memory type and speeds? Maybe post a "speccy" text output of the hardware or share the .SPECCY file on the machine.

I would run memtest, and try a new external storage rig all together. Possibly installing a new external controller and disabling the onboard external interface.

Follow the suggestions in this post - https://www.vegascreativesoftware.info/us/forum/faq-troubleshooting-crashing-and-stability--104785/

When troubleshooting render issues. Move effects to separate tracks, then disable/mute tracks until you determine what is failing.

Titles and what not can be done in a separate project, then applied to the main project as photoshop, or PNG image sequences. That would be more stable than 3rd party titlers.

"Mission critical" renders for me are almost always in chunks of an easily rerenderable format (uncompressed avi, image sequence, mpeg2, etc) just in case what happens to you happens to me. Then I would put them in a master project and make my final render from that.

If it is random crashes could be a ram or drive issue.

Well this is interesting. I'm so exhausted I can't even be mad. 4 jobs today... I'm bear, Before I left I set the job to render again. Last time it took... I think maybe 40 minutes ?? but I left muted a track I meeded... so I unmuted and rendered with the exact same paramaters...came home.,, sat down and.....
Tlapsed time - 12:20:15
Time left 04:32:22

I'm not even going to ask.,,, I'm just going to bed. Report back tomorrow. :-D

and just to let you know....it IS running... at 74% now. The progress bar moving.. So it's not frozen.

Congrats?

And the beat goes on. Thought i was ok but...

I needed another render. So fired it up and.... again...it gets to 99% complete then crashes. 3 times. So I took Friar's advice and decided to render in 3 sections. While doing that I went to Nick's link (thank you Nick) and looked at trouble shooting.

I've hesitated to render in chunks before just because I was concerned about missing frames. What I came up with and think I will implement in the future is to overlap each chunk by a minute or so... and let PlarelEyes sync. IT was flawless.

The first 2 chunks rendered without an issue. The third one crashed, just like the big render.

Going through the trouble shooting I realized, this is a new install of VP13 and I THINK I remember having problems before with GPU enabled. I disabled that, Now I'm putting my chunks together and once that's done (and I have a deliverable product) I'm going to try the big render again and see if that works.

Once everything is done I'll report back again (maybe this will help someone in the future).

OK.
I ran a render of the full file with GPU turned off... and it finished without a hitch. Now that's not to say there's a solution because it did that once before and then started acting up again. But I'm recalling when I disabled GPU before it solved my problem, so I'm hoping that's what is it.

This is an older PC (At least 6..maybe even 10 years),and I want to upgrade eventually, but it still works well. I did a memory test and it passed.

 

As astar asked previously, what GPU? (and what driver version for it?)

It works! Yeah! :)

As astar asked previously, what GPU? (and what driver version for it?)

My Graphic card is GeForce GT630
Driver Version 22.21.13.8205

My Graphic card is GeForce GT630
Driver Version 22.21.13.8205

Thanks. That's 382.05 (just take the last 5 digits and move the decimal place).

The GT 630 is based on Fermi2 architecture. It might work better with Vegas with an older driver such as 376.33. xberk has a Fermi2 GTX560ti card and is happy with 372.90. Robbif2 rolled from 378.49 all the way back to 344.11 to get his working.

Things went very pear-shaped at 378.XX (as described in that last link) but might have righted themselves a little since 381.XX, as the number of reports on the forum has dropped off.