If there is an OFX plug-in that can crash Vegas, it can happen early on while Vegas is checking what plug-ins are available, then loading each of them to ask what it does, even with an empty timeline.

I would try moving all plug-ins to a different directory and see if Vegas still crashes. If so, the plug-ins are not the cause, so I would move them all back and look for other problems. If, however, it does not crash without the plug-ins, I would quit Vegas, move one plug-in back and load Vegas to see if it crashes. Then I would quit, move another one back and try again, and repeat until I knew which plug-in was causing the crash.

Right - I have de- and re-installed V14 already - and I am not quite convinced that some OFX'es will make V14 crash about 4 minutes after start up.

I have no problems, however, to use V13 - and as it works reliably here with precisely the same FX'es etc - that is what I will do.

I have sent the 4-5 "Vegas Stopped Working" data to Magix - and from these data it should be possible to see where the program crashes - and hopefully to improve the issue for the next V14 build.

Mine does that too. It has been very unstable. Crashes when rendering, crashes arbitrarily when editing. Crashes if I leave it for 10 minutes with nothing happening. I come back, it has frozen up... The latest update 211 has helped some but still the most unstable software I've ever used...

My experience is the opposite. 211 has been very stable. No problem leaving it for hours. No random crashes. Extremely stable. I use Mercalli, NewBlueFx, Neat video, PluralEyes, some stuff from HitFilm and GPU acceleration with my Nvidia GTX 560 TI card. I can't say I've never crashed, but frankly, I don't remember the last time.

My build 211 is very stable too.

There are some suggestions to work through in this post, that include Red Prince's fine suggestion about moving plugins: https://www.vegascreativesoftware.info/us/forum/faq-troubleshooting-crashing-and-stability--104785/

Sounds like it might be a memory issue. Try running your Windows Resource Monitor while starting Vegas and see what happens with the memory usage for vegas140.exe.

I have sent the 4-5 "Vegas Stopped Working" data to Magix - and from these data it should be possible to see where the program crashes - and hopefully to improve the issue for the next V14 build.

Unfortunately, as things stand, I think (not 100% sure) such submissions go nowhere other than a big black hole. You need to use this procedure to submit crash reports, and even that process is flawed, if you read my comments in that thread.

Red Prince's fine suggestion

Thanks, Nick. 😎😍

FWIW, on my MSI GT 72s 6QE Dominator Pro G laptop Vegas Pro 14/211 has been very stable as well.

Thank you all.

Luckily I have done only a few projects in V14 - and have no problems going back to good old reliable V13

(Hmmm - did we not say the same about V12... V10... and specially about the last of many updates of V8 :- )

I always buy the new versions of Vegas to support that really incredible good (IMHO) piece of software - but I should remember to wait for more than just a few updates before I change to the new version....

I am sorry to hear Nicks suspicion about the Vegas Stopped submissions not getting proper attention - in this case 5 submissions within hours of the very same type of crash - 2 of them even without anything on the TL - should be a dream scenario for the developers giving them a possibility to pinpoint what might have caused the error.

I have been a software developer for 40+ years using many languages from before Cobol to C# and several assemblers too - and in my department we would have been more than happy to get such clear data of a possible cause for a crash.

Crashes do happen - programmers are only humans - the problem is when such crashes are not taken care of asap.

Your report and Trails-of-Doom's report in this thread are the first I've read about this type of crash.

Just updated Vegas 14 to build 211 from 201 and so far it has stopped working 15 times in the last few hours. Build 201 was very stable, but this is driving me up the wall. It happens when editing mostly when using standard elements like applying brightness or contrast and other times when using NewBlueFX Elements, Sometimes it stops when simply playing the veg file, the audio continues, but the picture freezes then it comes up with the 'stopped working' message. None of this happened before in build 201. Is it possible to roll back to build 201?

Just updated Vegas 14 to build 211 from 201 and so far it has stopped working 15 times in the last few hours. Build 201 was very stable, but this is driving me up the wall. It happens when editing mostly when using standard elements like applying brightness or contrast and other times when using NewBlueFX Elements, Sometimes it stops when simply playing the veg file, the audio continues, but the picture freezes then it comes up with the 'stopped working' message. None of this happened before in build 201. Is it possible to roll back to build 201?

There is a download link to build 201 in section 2c of this post. If you uninstall 211 you should be able to install 201 from that installer. I would do a clean uninstall as described in section 18 of this post. There were not a lot of changes between 201 and 211 and you might find that the issue is unrelated to the build. You might also try some of the other suggestions in that thread.