Vegas 23 CONSTANTLY CRASHES.

Mark-Hinson wrote on 9/25/2025, 11:57 AM

I am now at my wits end with this so called video editing program. Just recently updated to a brand new PC for video editing and so far I have not been able to do anything other than look for remedies and cobbled together workarounds to try, unsuccessfully, to get this peice of garbage running for longer than 5 minutes!

No matter what I attempt, import video, drag files to the timeline, create an adjust ment layer and drag a vid FX to it, Vegas Pro stops responding and I then have to force close it. I have tried disabling GPU support, increased the allocated RAM to 50% of my rig, I have performed a clean start with cache files cleared and defaults applied. I have uninstalled and reinstalled. No change.

I have other editing programs which run with no issue so why is Vegas Pro 23 not capable of doing the same!!?

My rig is as follows.

Windows 11 22H2

32GB DDR5 5600mhz RAM

Intel Ultra 7 265k

MSI RTX 5070Ti 16GB

Has anyone else experienced constant crashing and has anyone managed to figure out how to prevent them. I get a feeling that Magix do not care two hoots about this application other than rolling out GUI updates rather than fixing the inherant bugs that infect this piece of garbage.

I really need to get this application working to finish my projects.

Please anyone....help.

Comments

VEGASDerek wrote on 9/25/2025, 12:39 PM

increased the allocated RAM to 50% of my rig,

That is probably not a good thing to do, assuming you are referring to the dynamic ram preview option.

Reyfox wrote on 9/27/2025, 5:04 AM

Can't say I am experiencing constant crashing at all on my computer. My windows is up to date with 23H2, not 24H2.

I am working on three different projects and bounce back and forth in loading them to work on them. No crashing yet!

bitman wrote on 9/27/2025, 7:45 AM

@Mark-Hinson you may want to update your windows 11 - 22H2 to the latest windows 11 (24H2), 22H2 is ancient...
I have no issue with VP23 crashing (at least not with the source material and project setting I use).
As VegasDerek mentioned, do not increase it's default of 5%, if anything, rather put it to zero if experiencing crashes (will however impact performance).

Thinks to check or temporary try out:

thermal throttling of the CPU (use HWiNFO64 to check this)
set number of rendering threads to 1 in preferences
keep dynamic ram preview at 5% or even 0
upgrade to windows 11 24H2
enable legacy AVC decoding in IO tab of preferences (bypasses the newer decoding engine)
Do not overclock any part of your system (including memory - disable XMP)

RogerS wrote on 9/27/2025, 9:40 AM

I wonder if this is an issue with VEGAS and your media. Can you share MediaInfo?

Mark-Hinson wrote on 9/29/2025, 10:42 AM

Thanks Bitman. I will try your suggestions first. I did notice once I was lookiung at the media that it was HEVC encoded. I converted this to H264 which seems to have made a slight improvement but not much. Once I have time, I will upload a complete system breakdown and update my profile thanks for everyones patience.

fr0sty wrote on 9/30/2025, 9:38 PM

increased the allocated RAM to 50% of my rig,

That is probably not a good thing to do, assuming you are referring to the dynamic ram preview option.

Another reason this feature needs a rename or a removal... For those of you who do not know, Dynamic Ram Preview is NOT the amount of RAM VEGAS is using for your project preview/playback/rendering. It specifically affects dynamic ram preview, which is just a way of pre-rendering a portion of your timeline to RAM so you can play back sections of the timeline that won't play smoothly otherwise. It is never recommended to mess with this setting's default state unless you are trying to use that specific feature, which few of us do. The best practice is to just leave it alone.Set it too high, and you're actually removing available RAM for VEGAS to use, and making VEGAS run slower.

AlienOnVacation wrote on 10/22/2025, 11:07 PM

You know... I loved Vegas 21, it was my go to program. Can't answer same about 23 as I have YET to get it past adding MEDIA without a crash... terrible.. I have switched to davinci resolve... I did love this program once as I was very proficient at it.

RogerS wrote on 10/23/2025, 5:12 AM

@AlienOnVacation Could you share what media it crashes with? Even if it's too late for you, I'd like to see that fixed for others!

A sample for download would be great.

fifonik wrote on 10/23/2025, 5:26 AM

> I really need to get this application working to finish my projects.

For me the solution I'm using right now (VP22, not sure if this works in VP23) to finish my projects is:

1. Enable 'Legacy AVC decoding' and disable 'Experimental HEVC Decoding' in File I/O

2. Disable 'HW decoder to use' in File I/O

3. Create proxy (if you working with 4K): select all your footage in 'Project Media' | RMB | 'Create Video Proxy'. This till take a while. If you already have proxy created when option 'Experimental HEVC ...' was enabled you will need to re-create proxy.

4. RMB over video preview and enable 'Adjust Size and Quality...'

Yes, I know it will not be very smooth and preview quality will suffer, but in my case I have zero crashes with the above settings and able to finish my projects.
Still thinking what to do next, testing other NLEs after ~15 years of using VP :(

Mark-Hinson wrote on 10/23/2025, 8:51 AM

Thanks Bitman. I can happily say that the issue is resolved after following your advice. I also found that a number if files were HEVC and others in H264 in one project. Once I had converted the files to H264, all is now well. Thank you to all who contributed.

paul-marshall wrote on 10/23/2025, 9:51 AM

the render time was double the length of the timeline, compared to VP22

I noticed that in the new rendering options window the default did not use the NVENC GPU hence slower rendering using CPU. Also the default field width of the title of each option didnt allow the '(NVENC)' part of the caption to show up.

Reyfox wrote on 10/23/2025, 12:54 PM

@paul-marshall if you select Video and it's drop down menu you will see NVENC as an option for rendering.

Here is AMD VCE rendering which I use. You should see NVENC in yours.

paul-marshall wrote on 10/23/2025, 5:06 PM

@Reyfox I didnt make my point very well, which is that someone coming to VP23 and it's new look render window might select say 'YouTube' as a render option without realizing that GPU is not enabled by default and hence the render time is longer. I'm not seeing longer render times that some have reported once the correct options are set up. Just a thought.

Reyfox wrote on 10/24/2025, 5:37 AM

@paul-marshall, I am a user just like you are. For myself, I've come to expect with new UI changes, everything isn't sometimes where it used to be. But I understand where you are coming from. I didn't find it difficult to find. I explore whatever window is open and see if I can find it myself. Then, as usual, when I am "lost", I'll ask here and get an answer.

Someone coming to Vegas and its new UI will, like when I first came to Vegas, have to spend time in the user manual, search the internet or ask questions. It is true, what is obvious for some might not be for others. It's a difficult balance for sure.

While I agree, rendering times will be slower because it is being processed by the CPU, but that does remove any issues that some have experienced with GPU's and their drivers.