I don't want to turn this into a Premiere vs Vegas thread , but I'm actually very glad that this forced me to try Premiere, as I am quite enjoying it. Haven't had one crash or lockup since I started using it, and there are several things I enjoy much more than Vegas - I do miss the simplicity of Vegas at times though.

I've been with Vegas since I started editing, almost 10 years ago. Maybe it was time for a switch.

Hope they can get it sorted out for the rest of you.

I Maybe it was time for a switch.

Hope they can get it sorted out for the rest of you.

For me luckely nothing has to be sorted out. 😁
Thanks for the wishes for some others and happy editing with Premiere

I too had a problem with only Vegas crashing on a system that had been very stable. Both V13 and V16 were unusable. I even did a clean install of Windows 10 where Vegas was the only program installed and it still crashed. I thought it might be an over heating M.2 drive but then I remembered all the problems we used to have with graphics drivers back in the V4 days. So, back to the future. I installed an old driver and everything has worked perfectly since then.

It would be interesting to know which old version of the driver you have installed. Personally, I also have big stability problems with versions 16 and 17. These are usually the same problems that other users report (the temporal cursor advances while the graph is blocked, it is then necessary to kill the application).

@JeanPierre-Lugarini and @flyingski

So, back to the future. I installed an old driver and everything has worked perfectly since then.

It would be interesting to know which old version of the driver you have installed.

Which GPU driver is that old one and for which task are you using your GPU?
Which GPU (s) are you using?

I'm using an ancient GTX 560Ti card which has served me well for routine Vegas tasks. I work only with HD footage so my needs aren't great. The Nvida driver that works for me is 382.33 May 22, 2017. With the latest driver Vegas was completely unusable, with the old driver I can apply any chain of FX , crops or motion to my 60p footage.

@flyingski
For which task do you use that GPU?
In VP13 it is only used by Acceleration of added FX and maybe a little ( but not so good) for rendering with CUDA.
In VPro 16 for Acceleration of OFX plugins and for rendering by some codecs.

Just got back from filming a festival in Mexico. One of my colleagues, who uses Premiere exclusively, said he's been having a lot of issues with it crashing in recent months as well, which leads me to wonder if maybe something in this latest Windows Update has been screwing things up on the video end... For me Vegas is mostly stable, but I do get the odd crash from time to time, but it's still interesting to hear we're not the only ones dealing with this lately.

Just got back from filming a festival in Mexico. One of my colleagues, who uses Premiere exclusively, said he's been having a lot of issues with it crashing in recent months as well, which leads me to wonder if maybe something in this latest Windows Update has been screwing things up on the video end... For me Vegas is mostly stable, but I do get the odd crash from time to time, but it's still interesting to hear we're not the only ones dealing with this lately.

Since I've started using it it's crashed twice on me so far, only when I had closed the program though, so not while working, just a random crash screen after the project was already closed.

i forget, did you disable that SO4compound.dll yet?

I did, then reset mine to full factory, even left GPU enabled, and it is all running fine now.

Probably be the last time I post on this board - I hope the rest of you get this sorted out. Vegas crashing was probably the best thing to happen to my editing workflow, forcing me to learn Adobe.

I was with Vegas for 8 years or so? I used to rant about it to everyone - and I still might as it is very easy to pickup and learn how to use, which is what I needed as a beginning editor moving from Windows Movie Maker.

I've used Premiere for the last month now, and only crashed once. Once - and that was with no data loss.

I haven't tried any 360 videos with Premiere yet - so I can't comment on that, but everything else is much better in my opinion, and I never thought I'd say that.

I can't tell you how much I love the Adobe Media Encoder! That alone was worth the switch - for someone who needs to render out at least 3 versions of the same project every time, it is SO NICE and actually uses my Threadripper the way it should - as well as my 64GB of RAM.

No editing suite is perfect, and Vegas served me well as I was building up my business, and I hope they get the bugs worked out for you guys!

The rest of us? I have nothing to sort out, Vegas is great for me and many others.... Since this is your last time posting on this board as you say, its probably for the best....Farewell!

For most of 2019 I stayed with Vegas 15 for paid work & used Vegas 16 only after the last/final update was released when I got it as a bonus when purchasing V17... Therefore I just started using Vegas 17 over the holidays for family videos and I had no issues. So at the beginning of the year I loaded an old project for a client who wanted new renders, and it crashed. I installed the latest AMD VEGA GPU driver from 1-9-2020 and it was stable again. I always create a list of know good drivers for each workstation & then make an image of the entire OS drive... I then prevent Windows from updating, which became harder in Windows 10...

I charge clients by the job vs. hour & get projects out the door much faster in Vegas than Premiere Pro, FCP, etc. If I were stuck using Premiere or FCP I would be working 7 days a week to do what I can accomplish in 4-5... AND sound work is super great in Vegas... 80% of a good film is getting the sound right...

boys boys, lets al chill. I've been using Vegas for years and its been crashing for years. I generally  build my own systems and have assumed it was hardware issues but I always arrived at a place sooner or later that things would go pretty smoothly and the recovery saves help a lot. Things did get worse with 16 but it functioned. With 17 the problem was insurmountable. The program would crash every few minutes. One system has an i7 chip 64GB RAM on an intel motherboard. The other is an hp Z620 workstation with two Xeon chips and 96GB RAM. I got so frustrated that I installed premiere and media composer. During the installations BOTH of these programs halted the installation and told me I needed a different driver from NVIDIA for my quadro4000 and quadro5000, The hp workstation has software called hp performance monitor that is stunning in its comprehensive evaluation of your system. HP has really gone down the tubes on consumer lines but their commercial stuff is still awesome. I got my workstation refurbished on amazon for $600! Anyway, the hp program identifies the graphics card and then lists about 20 drivers each certified by different software manufacturers. For mine they listed one driver that they hadn't tested but that had been certified by AVID for media composer and the hp software downloaded and installed it on request automatically. When installing Premiere on the other machine it stopped me and said I needed driver 353.91(which was the same driver the hp needed) from NVIDIA I couldn't find that driver on NVIDIA and neither could the NVIDIA support person but while they continued to look I went on AVIDs site and searched for the Quadro graphics cards and found a link to the driver. After installing the driver on both machines both premiere and media composer worked so I fired up Vegas pro and it worked on both computers too. Still crashes sometimes but its usable. I am plagued with another issue but I'll go there on another thread. I feel stupid that both media composer and premiere are so hard for me to grasp but I do all live music videos requiring several cams to be synchronized (Vegas sound synching still doesn't compare to pleural eyes which Vegas doesn't accept as a plugin anymore) and Vegas seems better designed for multi-cam editing of synched tracks. Moral of the story - Vegas Pro needs to identify graphics problems on installation like AVID and Adobe do. They came this close to losing my business with 17 and only have their competitors to thank for me sticking around..

Ziphler, Where you got that intel that Vegas does not accept Plural Eyes as a plugin anymore? Plural Eyes is fully compatible with Vegas Pro 17.... Have it here working flawlessly, along with everything else.... And i have here using simple/basic build computer systems and laptops, (No Xeon chips, No NVIDIA GPU cards, nor the whole download latest GPU drivers mess).

...Moral of the story - Vegas Pro needs to identify graphics problems on installation like AVID and Adobe do. They came this close to losing my business with 17 and only have their competitors to thank for me sticking around..

Although this is a good idea when trouble-shooting, I'm pretty certain they are slow at testing new drivers so you end-up with a really old driver that works, but there also may be much newer drivers that work even better including much better in other apps that require newer drivers that fix GPU driver bugs, etc...

For instance, your Nvidia driver 353.91 is from 2015. I think the newest driver for the Quadro 4000/5000 series is from 2018, driver 377.83. Along the way, key issues were addressed. For instance, update 377.83 addressed "Random driver crashes occur when running the OpenGL application"... That'll make programs crash...

Well whata you know? THANKS Steve_Rhoden I got pleural eyes installed and showing up in the menu just like old times! .Support had to give me a special workaround to use with 15 and then magix came op with their own (excruciatingly slow) sound synch that couldn't sync a nursery rhyme and pleural eyes wasn't showing up in extensions any more. II just want to be able to render in high def with multiple cams. You can't really do that with basic computers.

My apologies, I meant 353.82 (not 91) in my last post on the driver that works with the NVIDIA Quadro cards and Mr Rhino, I had 377.83 intalled and all three video editors rejected it. What I probably really need is a newer graphics card (or cards) but they're so damned expensive.;

Well whata you know? THANKS Steve_Rhoden I got pleural eyes installed and showing up in the menu just like old times! .Support had to give me a special workaround to use with 15 and then magix came op with their own (excruciatingly slow) sound synch that couldn't sync a nursery rhyme and pleural eyes wasn't showing up in extensions any more. II just want to be able to render in high def with multiple cams. You can't really do that with basic computers.

You should find“C:\ProgramData\VEGAS Pro\17.0\Application Extensions\PE4VegasLoader14.dll”. This file is Pluraleyes' loader for VEGAS Pro 17.

ziphler, i render in high def with multiple cams almost daily for Broadcast and Media houses on basic built computers!.... Not only that, but larger than 4K output for outdoor Digital Media boards at varied larger than 4K resolutions with none of the usual GPU and GPU Card headaches..... The number one rule is that when it comes to Vegas, CPU Processing is key, when you throw overbearing GPU processing at Vegas it most often defeats the purpose.

@Steve_Rhoden, I saw this months ago, but plan to try it now. Thank you.

UPDATE after turning OFF GPU Acceleration (Sept 1, 2020): I was able to edit much longer before the freeze occurred by turning OFF GPU Acceleration, but it still froze. @Musicvid had also recommended turning OFF GPU Acceleration. This problem has happened to me on two different PC systems.

My next test will be to turn OFF my CPU Overclocking.

PS: Is there an easy way to reduce the time between Auto Saves? (Automatically Save more often.) That would help. I lose a lot of time and effort when these freezes occur, because I cannot recover like @michael-harrison, below.

UPDATE (Sept 2): Overclocking ON and GPU Acceleration ON do not seem to be what is causing the freezes, so I am turning them back ON. The only thing that I have not tried is the disabling of SO4compound.dll . Does anyone have the link to that procedure or the procedural explanation? TIA and grateful.

UPDATE (Sept 18): Disabling So4compound.dll did not help (IF I did it correctly). I'm back to running everything again, but still getting freezes. One BIG thing that I found is that I now use LIVE SAVE and turn OFF Auto Save. It saves every edit! YAY! So when I have these freezes, I keep almost every edit when I restart. That saves me time, but the freezing requires a quick restart. I hope that this is fixed soon. Tapping the Spacebar seems to be when most freezes occur. (LIVE SAVE is turned ON via TOOLS. Then turn OFF AutoSave at the bottom of Preferences. It will then Save each and every edit decision as you edit.)

Couldn't send a crash log as the client just froze up with the white screen again, but I had just moved a clip left on the time line, up against a previous one, went to the previous one and clicked play to check the transition and Vegas locked up.

This is the most frequent lockup that I think we all experience.

Auto ripple was NOT turned on.

No Video FX are being used either, and the Nvidia drivers are the most recent studio drivers.

This type of crash has been with me on versions 16 and 17 too. Cutting or trimming directly on timeline and hitting spacebar for play - then freezing and washed out colors (semi-white) view. Sometimes it has triggered Vegas error reporting and I have submitted several reports.
It occured on old Intel / AMD Fury system and also on newest Ryzen 3950x / Nvidia 2070 Super system (has been clean Windows installs at some point).
It doesn't matter if material is from Panasonic GH5, Sony A7II, Gopro or DJI Phantom. But I have settled to believe it is too hard to edit with Long GOP codecs although I am usually using proxies and preview quality. But still it has been frustrating to crash also this newest system just hitting spacebar over straight cuts without FX.

This crash is nasty because it always hits when you are having best flow on editing (and somehow being too fast for system).