Work through these links for Troubleshooting:

https://www.vegascreativesoftware.info/us/forum/faq-troubleshooting-crashing-and-stability--104785/

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

Thanks for your comments. I have tried turning off the GPU acceleration and so far so good. Intel would render but crash out at a random point for rendering which is a shame as it is around 3 times faster than CPU rendering even at 4k :-( Using the K600 for GPU acceleration it would crash most of the time as soon as you went to render. Drivers for both graphics systems have been updated to the latest possible. I have also set the video ram to 0 for the render period only.

During editing, I have now found the K600 most stable whilst providing good working performance. The Intel just throws those random crashes everywhere :-( Such a shame as the gpu acceleration is really nice to have on....but i have a cold sweat all the time whist having one hand permanently over ctrl+S !

Maybe one day I can get my work department to buy some up to date GPUs and hope these help. Does anyone have any good recommendations for a GPU that wont crash out all the time with GPU acceleration enabled, and does Vegas 16 favour AMD or nvidia ?

Thanks for the help.

Does anyone have any good recommendations for a GPU that wont crash out all the time with GPU acceleration enabled, and does Vegas 16 favour AMD or nvidia ?

I have no problems editing, previewing (almost all with preview full in my previewscreen) and rendering on both hardware of my signature.
Most used sourcefiles are AVC 50p, GoPro and DJI 50p, Samsung smartphone types A5, S8, S9.
Rendering to Magix AVC with NVENC option goes 6-8 times faster than with the same older Mainconcept AVC codec that has no NVENC option.

Does anyone have any good recommendations for a GPU that wont crash out all the time with GPU acceleration enabled, and does Vegas 16 favour AMD or nvidia ?

I can tell you two (separate systems) where Vegas is super crash-happy, even with GPU disabled and other fixes from Grazie's list - Nvidia GeForce 1080 Ti, and Intel HD 630.

I was looking at the 1050TI as its a fair price with 4GB RAM. Good to know you are having a nice stable experience. I will have to talk with the people in charge at my work place :-)

Thanks Tony, I will cross them off my list for now not to mention the price.

I'm noticing many people reporting problems are using Intel GPUs. Wasn't there an issue that was solved by disabling onboard GPU in the bios?

I can tell you two (separate systems) where Vegas is super crash-happy, even with GPU disabled and other fixes from Grazie's list - Nvidia GeForce 1080 Ti, and Intel HD 630.

When I read this kind of messages (without proof) I always becomes curious about these complaints, but also realize that without any kind of proof or example vegs or other specifications those problems are not possible for also trying to trigger the program to anyting or by anyone.
Maybe you can, if you are so sure about the statement you made here?

NB. If you are looking for my proof and examples search the forum posts with my name.

Mostly Pilot error.

Maybe you can, if you are so sure about the statement you made here?

I have written all this up extensively and specifically in other threads, mainly the 162-post thread called: VEGAS Pro 16 Update 2 (build 307) - General Discussion, where many crashes have been reported by others, and Magix has been sent the crash logs and various tickets (when there are actual crash logs, which is often not the case).

In Studio A the main system is i7, 32GB, SSD, Nvidia 1080 Ti, and in Studio B it's i5, 16GB with Intel HD 630. We experience the same crashes on both systems, except that the i5 system also adds an additional crash type that turns all the monitors cloudy white.

We've been doing pro shooting/editing for 25 years and had not run into these kinds of problems until V15. Both studios run a lot of hours daily and these crashes tend to disrupt things, as well as affecting client confidence when they are present and one of the various random crash types happens. We've identified, and sent to Magix, three specific types of crash, together with full system reports.

So after a 10 hour render there are drop outs everywhere to a black screen !! Right now i am so angry I am lost for words that i cant politely put here. I had used one of the standard magix h264 presets for an mp4, no intel or nvidia acceleration and gpu acceleration off. I will leave it rendering over night to one of the sony xavc intra mxf formats and see how it goes. Failing that I will try the sony xavc long gop to an mp4. Massive files but used to work perfectly under Vegas 14.

10hours......... :-/

@Richard-JT The number 1 way to resolve black frames is to restart Vegas immediately before rendering, and don't do anything else before rendering.

Thanks Nick, I always tend to do this. I done the render using sony xavc intra mxf format, which came out fine, no drop outs, but with a massive file, sony xavc s long is what i normally use in Vegas 14. So I decided to render off the project again but in XAVC S long. And yes, it too suffers badly from sections that are blank with the audio still present just like the magix avc option i first tried. What is very interesting is i took the mxf file, dropped this onto the timeline and rendered this down to mp4 using the magix avc mp4 and the intel qsv option (i had the onboard intel graphics selected in the options this time as every other time i disable it) and now this rendered off fast and with no issues in the video !!!! What gives with that logic. Rendering the project direct gave drop outs, but rendering it to mxf and then to magix avc mp4 was fine !! Im lost for words.

And i am quite disappointed that the xavc s long doesnt work properly as I found this to be a nice balance between file size and image quality for 4k video. Though i am open to suggestions to try/use something else.

Thanks again.

The logic is quite simple. Vegas doesn’t process all fx and transitions on the MFX file. It also would mean that your system has issues processing FX and so on during the render process and higher compression codecs. I would check all my hardware especially RAM modules and speed, make sure it cooling is sufficient and the power supply is sufficient.

Anyways, XAVC-I (MFX) is higher quality and I even use it for intermediated. It also plays much better in Vegas.

Which transitions and fx would not be included ? Do you have information where i can read up about this ? In my video i rendered to mxf, i had used the color corrector and sharpness fx along with color curves. Very basic.

I didnt realise that Vegas 16 can now be so picky/fussy with hardware. Cooling is fine as is psu, system stability is not an issue outside of Vegas 16. At work I used to use Vegas 13 without a problem, rock solid and no issues with any format I would render to. When the option to purchase Vegas 16 was available, I grabbed it and its been farily unstable on the edit and poor on the render front :-(

Appreciating the help/info though, thanks.

In Studio A the main system is i7, 32GB, SSD, Nvidia 1080 Ti, and in Studio B it's i5, 16GB with Intel HD 630. We experience the same crashes on both systems, except that the i5 system also adds an additional crash type that turns all the monitors cloudy white.

We've been doing pro shooting/editing for 25 years and had not run into these kinds of problems until V15. Both studios run a lot of hours daily and these crashes tend to disrupt things, as well as affecting client confidence when they are present and one of the various random crash types happens. We've identified, and sent to Magix, three specific types of crash, together with full system reports.

Happy for not being a client. 😁

@Richard-JT

As a diagnostic approach, have you considered breaking the heavy work of decoding, filter application and encoding into two operations? Perhaps, consider rendering to a lossless codec like Magic YUV RGB, UTVideo or Sony YUV. Then take that output back into Vegas or any other encoder for the final delivery format. If the results were different, it might be telling.

Which transitions and fx would not be included ? Do you have information where i can read up about this ? In my video i rendered to mxf, i had used the color corrector and sharpness fx along with color curves. Very basic.

I didnt realise that Vegas 16 can now be so picky/fussy with hardware. Cooling is fine as is psu, system stability is not an issue outside of Vegas 16. At work I used to use Vegas 13 without a problem, rock solid and no issues with any format I would render to. When the option to purchase Vegas 16 was available, I grabbed it and its been farily unstable on the edit and poor on the render front :-(

Appreciating the help/info though, thanks.

Maybe I miss read your post but didn't you say rendered a XAVC-I (MFX) file from the project and then put it into an new project and it rendered fine? If so, all you FX, Transitions and so on are already processed, all Vegas has to do is a re-encode.

There is a huge difference between VP14 and earlier versions, 15 and 16 are more taxing on the system and yes, are even pickier when it comes to hardware because of the changes in GPU acceleration.

I believe (yes, believe as I do not have enough proofs) that all these Vegas issues that can be fixed by disabling GPU are graphic card hardware related or driver related.

1. Check you hardware. Install FurMark (graphics card stress test) and run it for a while. System should be stable and you should not experience any visual glitches. You may have HW issue and not experience any glitches in your typical PC normal usage like browsing, office, not very resource expensive games etc.

2. Update graphics card drivers. When reporting back that you updated it, provide exact GPU info and driver version you installed. Sometimes it is very hard to find the most recent installer so you might think that you have the most recent version while you are not. Sometimes not the most recent version needed. Driver update tools like DriverEasy & similar might help with updating drivers to the most recent version, but never install everything they recommend you until you know what are you doing! And never allow the tool to update your system automatically! Choose only graphics driver and update manually.