I've never used any other editing software - but I can't imagine any pro level software crashing as much as Vegas does.

If I'm editing 4K footage off my A7iii I will crash pretty often, while splitting / playing footage on timeline. This has happened for the past year, as long as I've had the camera. This was with Vegas Pro 16 as well as 17.

If I'm editing footage from my C100, I still will get crashes, usually happens right after a split, and press play.

Now - before live save feature, this would be extremely irritating as you would lose so much time, now with live save, it's still really annoying but not AS BAD as it was - but man what is going on with this software?

How can this be a professional level software with this many bugs and crashes?

This was my current crash message while editing my C100 footage.

Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 17.0 (Build 321)
   Problem:             Unmanaged Exception (0xc0000005)
   Fault Module:        C:\WINDOWS\SYSTEM32\ntdll.dll
   Fault Address:       0x00007FFBC5000853
   Fault Offset:        0x0000000000040853

Fault Process Details
   Process Path:        C:\Program Files\VEGAS\VEGAS Pro 17.0\vegas170.exe
   Process Version:     Version 17.0 (Build 321)
   Process Description: VEGAS Pro
   Process Image Date:  2019-09-18 (Wed Sep 18) 23:59:10

Let's get this one back on track, Iggy needs our help.

Fault Module:        C:\WINDOWS\SYSTEM32\ntdll.dll

Are you able to test this on another system to see if you still get crashes when using that same footage? I'm no computer expert, though I've fixed hundreds of issues over the 25 years I've been using them, and usually when you see faults dealing with the windows system folder, it means there could be a windows-level corruption causing issues. If you can test this on another system successfully, it may mean that a re-install of windows could help solve your issue. Or, you can try this fix suggested by Microsoft:

"

Have you tried running the system file checker and performing a clean boot? We truly recommend it.

On the other hand, you can try other options below if it did not work:

Method 1: Update Windows

Click Start button, and look for Control Panel.

Click System and Security, and select Windows Update.

Click Check for updates and click Install updates.

If you are experiencing the same after performing Windows Update try reinstalling the DLL.

Method 2: Reinstall the DLL

Type cmd in the search box, and then right click Command prompt select Run as Administrator.

Type this in command prompt:

regsvr32.exe /u ntdll.dll and press Enter key (this will uninstall the file)

regsvr32.exe ntdll.dll and press Enter key (this will reinstall the file)."

Some other, less invasive troubleshooting strategies would be to completely disable all GPU acceleration (preferences>video tab), decoding (preferences>file i/o tab), and rendering options (Render as render templates, select anything that doesn't say "NVENC" or "AMD VCE"), then see if you still get crashes. This will isolate if it is anything to do with GPU acceleration causing the issue.

Then you can try to make proxies for all your clips (right click on them in the project media and select "create video proxy), then set your preview quality to Preview or Draft, which will enable the proxy files, and see if you still have issues. This will isolate if it is a problem with decoding your media that is causing the issue.

If that last step helps stabilize things, you can download a program called mediainfo, which will then generate a report on the media you are having crashing issues with. Post that report on here, it will help us to isolate your issue a bit more and maybe we can work on a solution, a workaround, and/or we can notify the developers that there is a compatibility issue with that media.

Turning preview window from Best to Preview MAY have fixed the issue - I'd have to keep testing.

Still crashing randomly after newest update. This was 1080 footage from the C100. It just randomly crashes while cutting / playing on timeline. Preview window is set to "Preview" and not full. This is NOT 4K footage.

Extra Information
   File:                C:\Users\dmcgu\AppData\Local\VEGAS Pro\17.0\fileio_x64.log
   File:                C:\Users\dmcgu\AppData\Local\VEGAS Pro\17.0\dx_video_grovel_x64.log
   File:                C:\Users\dmcgu\AppData\Local\VEGAS Pro\17.0\svfx_video_grovel_x64.log
   File:                C:\Users\dmcgu\AppData\Local\VEGAS Pro\17.0\ocio_x64.log
   File:                C:\Users\dmcgu\AppData\Local\VEGAS Pro\17.0\dx_grovel_x64.log
   File:                C:\Users\dmcgu\AppData\Local\VEGAS Pro\17.0\gpu_video_x64.log
   File:                C:\Users\dmcgu\Desktop\Vegas Saves\Customs.veg

Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 17.0 (Build 353)
   Problem:             Unmanaged Exception (0xc0000005)
   Fault Module:        C:\WINDOWS\SYSTEM32\ntdll.dll
   Fault Address:       0x00007FFE00DC0853
   Fault Offset:        0x0000000000040853

Fault Process Details
   Process Path:        C:\Program Files\VEGAS\VEGAS Pro 17.0\vegas170.exe
   Process Version:     Version 17.0 (Build 353)
   Process Description: VEGAS Pro
   Process Image Date:  2019-10-31 (Thu Oct 31) 22:15:00

I've been having the same issues for 3 Vegas pro versions now. Like the OP it seems to happen after splitting and then playing. Vegas becomes unresponsive and if I let it go long enough it will crash. I'd say 5 times average per video edit, and I don't do that much editing.

It pains me to see the same responses all the time to these crashes. I just updated to the latest NVIDIA Studio driver and it's still crashing.

Intel Core i7-9700 w 16GB RAM

NVIDIA GeForce RTX 2080 w 8GB

I've been having the same issues for 3 Vegas pro versions now. Like the OP it seems to happen after splitting and then playing. Vegas becomes unresponsive and if I let it go long enough it will crash. I'd say 5 times average per video edit, and I don't do that much editing.

 

It pains me to see the same responses all the time to these crashes. I just updated to the latest NVIDIA Studio driver and it's still crashing.

Intel Core i7-9700 w 16GB RAM

NVIDIA GeForce RTX 2080 w 8GB

 

 

 

They obviously know about it unless I'm sending my crash reports to a bot someplace and they have never been looked at. I mean I probably send 10 crash reports a week.

@iggy097

I did as search on the database for your crash and found it. The crash is in the video driver. I recommend you to upgrade to the Studio driver 441.28. Not promising that will resolve your issues but considering the crash is in the driver, I would recommend the update.

For future reference, it would help us to diagnose specific people's issues if you added details in the text field on the crash dialog and potentially an email address as well. Luckily in this case you included your project file so I was able to track it down. In this specific case, it appeared that you were doing an edit and the crash occurred after a ripple operation.

@iggy097

I did as search on the database for your crash and found it. The crash is in the video driver. I recommend you to upgrade to the Studio driver 441.28. Not promising that will resolve your issues but considering the crash is in the driver, I would recommend the update.

For future reference, it would help us to diagnose specific people's issues if you added details in the text field on the crash dialog and potentially an email address as well. Luckily in this case you included your project file so I was able to track it down. In this specific case, it appeared that you were doing an edit and the crash occurred after a ripple operation.

I'll try the new driver and see if it helps.

Also - noted about the text field, will do.

*edit* - and apologies in advance if you actually have to see the weird stuff I edit for a living if you are able to view the project file.

@iggy097

I did as search on the database for your crash and found it. The crash is in the video driver. I recommend you to upgrade to the Studio driver 441.28. Not promising that will resolve your issues but considering the crash is in the driver, I would recommend the update.

For future reference, it would help us to diagnose specific people's issues if you added details in the text field on the crash dialog and potentially an email address as well. Luckily in this case you included your project file so I was able to track it down. In this specific case, it appeared that you were doing an edit and the crash occurred after a ripple operation.

@VEGASDerek

Could it be the auto-ripple causing the issue? I'm not the OP and I'm running 441.12 Studio drivers, which was the latest available as of yesterday. The 441.28 drivers were released today literally today.

Yes...it is very possible auto-ripple could be causing the issue. We have a number of reports of some instability in auto-ripple but to this point have not got a good handle on why this might be happening. In Iggy's crash, the command at the time of the crash was indeed an auto-ripple event, but the crash was unrelated, in the graphics driver. Potentially this could have been due to some bad memory access that is being caused by the auto-ripple. In situations like this, we just need to continue to get reports and hope to find that one elusive commonality that will help us solve the problem.

@VEGASDerek - I can't work anymore. A series of crashes. I've sent my Report through the email. I hope you can squash this one Derek. Please.

Well, potential USER Error and recognised that my Extyernal Control Surface uses memory:

1/- Reduced RAM Build from 500mb to 200mb

2/- Set Preview to Good Full

So far so very good. No falling over.

@VEGASDerek - I'll keep you updated.

I'm having similar crashes as @iggy097. I noticed that if I hit the space bar to start playing the video, that seemed to crash the program more often, but if I moused up and click the play button, I didn't crash as much. This is hit-or-miss, but I'm curious if anyone has had a similar experience.

I have this perception that if I do something that causes the program to have to call a file too quickly, or do some other I/O, that causes problems. For example, I have had several crashes if I do save with Ctrl-S, then immediately click a button or do something else.

I'm just speculating, hoping this might register with one of you as something you have similarly experienced.

I'm having similar crashes as @iggy097. I noticed that if I hit the space bar to start playing the video, that seemed to crash the program more often, but if I moused up and click the play button, I didn't crash as much. This is hit-or-miss, but I'm curious if anyone has had a similar experience.

I have this perception that if I do something that causes the program to have to call a file too quickly, or do some other I/O, that causes problems. For example, I have had several crashes if I do save with Ctrl-S, then immediately click a button or do something else.

I'm just speculating, hoping this might register with one of you as something you have similarly experienced.

I think it has something to do with working fast. If I'm cutting and splicing alot and moving quickly, using the space bar as you do, it crashes more often.

I think it has something to do with working fast. If I'm cutting and splicing alot and moving quickly, using the space bar as you do, it crashes more often.

I'd concur with that. I too get random freezes after deleting with auto ripple then playing and it does seem to happen if you playback too quickly after the ripple; it almost needs time to settle down (!). Unfortunately, mine crashes by freezing up with the screen going a sort of white fog (no idea how to describe that) and then it talks about sending a crash report to Microsoft, not Magix; the Magix error reporting box doesn't show up. I have to use Task Manager to exit Vegas.

I think it has something to do with working fast. If I'm cutting and splicing alot and moving quickly, using the space bar as you do, it crashes more often.

I'd concur with that. I too get random freezes after deleting with auto ripple then playing and it does seem to happen if you playback too quickly after the ripple; it almost needs time to settle down (!). Unfortunately, mine crashes by freezing up with the screen going a sort of white fog (no idea how to describe that) and then it talks about sending a crash report to Microsoft, not Magix; the Magix error reporting box doesn't show up. I have to use Task Manager to exit Vegas.

Mine does the white fog thing half the time as well.

I think it has something to do with working fast. If I'm cutting and splicing alot and moving quickly, using the space bar as you do, it crashes more often.

I'd concur with that. I too get random freezes after deleting with auto ripple then playing and it does seem to happen if you playback too quickly after the ripple; it almost needs time to settle down (!). Unfortunately, mine crashes by freezing up with the screen going a sort of white fog (no idea how to describe that) and then it talks about sending a crash report to Microsoft, not Magix; the Magix error reporting box doesn't show up. I have to use Task Manager to exit Vegas.

Ok, so I'm not crazy. Surely this is a clue as to what the problem is. Anyone from Magix care to comment?

Yes...it is very possible auto-ripple could be causing the issue. We have a number of reports of some instability in auto-ripple but to this point have not got a good handle on why this might be happening . . . Potentially this could have been due to some bad memory access that is being caused by the auto-ripple. In situations like this, we just need to continue to get reports and hope to find that one elusive commonality that will help us solve the problem.

AUTO RIPPLE ENGAGED

@VEGASDerek - Repro-ed whilst Scrubbing the T/L.

4x AutoRipple ENGAGED = Crash

4x AutoRipple DISENGAGED = No Crash

@VEGASDerek - I don't get the "Phone-Home" option coming up to allow me to send you a report.

What else can I do to assist y'all?

Ugh.... I’m now stress testing the AutoRipple: ON/OFF.... OFF/ON etc etc I had one hung collapse session, but this quite scary.

@VEGASDerek - If you need more from me?

This problem has been around for 15 years. A feature film could be made about problems with Auto-Ripple turned on.

If Vegas is not playing, everything is ok.

but.....

If I have 50 or more videos on the track and I delete some while playing, Vegas freezes for 3 minutes and then works on. Sometimes I manage to delete 10 files, sometimes I just need one, and Vegas freezes.

I don't use Project Manager or Storyboard. I always prepare shots only in Timeline. I have a project at the beginning and rough shots at the end.

Auto-riple makes my preparation much easier, because it automatically removes gaps when I delete. Fixing the freeze problem when deleting files while playing would help me a lot.

Update:
Auto-Ripple and deletion during playback only work great if you turn off the Video Preview window. The problem is that you don't see the video :-)

The Vegas playback engine is not so very robust/elastic in real time. I think people should take that as a given.

Every program has its "core" characteristics. You can push the Vegas playback engine, real time, only so far. There seems to be some "opening up" of that limitation at the uber-high end of video cards, i.e., Vega 64 (AMD) and the 2080 ti and above, taking for granted that at that level, one's CPU would also be in that 'high end' (Threadripper etc) range.

OTOH, Mr. Grazie seems to be hitting a "brick wall" even with such a "monster" machine. AS well as some others.

Someone used the word "settle in" -- i.e., a second or two "pause" before pressing play after a major re constituting of the timeline order -- and "while playing"= foggettaboudit.

That is my methodology, as well. Usually, if that is ignored, especially with a complex project, one will get a "freeze" as opposed to a crash, but that freeze might be well extended.

Am I happy about any of that? No, of course not, but it is what it is.

Again, this IS Vegas, this is not some sort of "out of character" performance.

The way I work, I won't, typically, use auto-ripple as a "default" (on all the time) setting. I NEVER would consider employing that feature during playback, unless I had a fairly simple timeline.
 

By reading the above posts, I really see that I am experiencing the same. Which, is some way is good news. It meens that I am not the only one. Using Auto-Ripple during editing fastly and starting playback quickly after a cut triggers a crash.

This has been a problem in Vegas for as long as I can remember back. Vegas does not like quick changes to the timeline while it is playing. Grabbing a clip and moving it while the play head is on it, such as an auto-ripple, or deleting a clip while the play head is on it, starting playback too fast after a change on the timeline, those things have always been a weakness for Vegas' stability.