V23 render crashes and render freezes now back again!

Mindmatter wrote on 9/16/2025, 7:25 AM

The first 3 renders of my project were fine. The last one yesterday evening was fine. I had it shut down PC after render, For some reason V23 then renames and resaves the project with the extension "Rendershutdown". Why? I pray to god it didn't corrupt the file in any way.Today I didn't change a thing except correct a few events and add an EQ to an audio file. Now V23 either freezes at 20% or crashes at 80%.

I had one single crash today with - you guessed it - BCC optical stabilizer. I then just kicked it out and it's not even in the project anymore.

Same old error report, svfx, IO etc etc

Also, I just canceled a render because I had forgotten an edit, and V23 then just crashed and disappeared.

At any rate, I'm seriously getting annoyed now. This does not make any sense anymore.Why were the first 3 renders just fine?? It's like Vegas 23 corrupts itself and accumulates some sort of errors somehow over time when you work with it. And why does V21 render OK, and 22 and 23 crash? I'll probably have to try and reinstall and see if that helps.

Comments

Dexcon wrote on 9/16/2025, 7:42 AM

... and add an EQ to an audio file

A native Vegas EQ FX or a 3rd party EQ FX? Either way, which audio EQ FX was added?

Also, after an editing session, do you save a backup of the project .veg file to drive such as an another internal drive, an external HDD/SSD, memory card or stick, or the Cloud? Or use Advanced Save under the Tools menu? Or even rename the project (e.g. v1, v2, v3) after an editing session? Doing so means that a corrupted project file - while annoying - can be alleviated by going back to the backup project file saved at the end of the previous editing session.

Reyfox wrote on 9/16/2025, 7:52 AM

I don't agree with you on Vegas corrupting itself. I've been using it every day since its release, and never an issue exiting the software and having it change the name of the the project. Never. And since you, at least for the moment, are the only one reporting this type of issue, maybe something with your installation of Vegas and/or Windows? Have you run sfc scannow?

You seem to continue to have the same issues version to version. Problems with boris FX Optical Stabilizer.

Here is the version of Optical Stabilizer that I have.

Mindmatter wrote on 9/16/2025, 8:03 AM

@Dexcon yes I always save twice, each on separate drives. What happened here was I had automatically "last project on open" feature on, so I continued working on the version V23 had saved the night before without noticing it.

A native Vegas EQ FX or a 3rd party EQ FX?
It's a plugin called modern EQ, which was already on several audio events. I just added it to a couple more.

@Reyfox I don't have another logical explanation though. V21 renders the project just fine, so that does point to a V22 and 23 issue, wouldn't you agree? Why does it not render without crashing after 3 good renders anymore?
The BCC is not the issue here, as I mentioned I threw it out and don't use it in this project after the crash.
The issue is unpredictable crash behaviour that is NOT present in V21 with the exact same project.

Reyfox wrote on 9/16/2025, 8:11 AM

@Mindmatter, without having your exact project to test, I'm not sure that anyone can give a definitive answer as to why you are experiencing this issue.

Is it only with this particular project?

Mindmatter wrote on 9/17/2025, 3:22 AM

An update - I've done 4 more renders of this project and they went fine! Go figure. Of course I'm relieved as the deadline is this week, but I remain cautiously, slightly paranoid. For now, I really like V23 otherwise.

As to the project itself, it is an 18 minute mini docu with several hundred gigs of XAVCI 4k footage and DJI 4k H265 .mov clips.For someone else to test that, it would take enormous data transfers as well as the exact replika of my FX, plugins and setup. Which is why I never went down that route.

Thanks to all of you for your input nonetheless.

Gid wrote on 9/17/2025, 5:04 AM

@Mindmatter Hi, as you have an AMD Ryzen 9 5900X that doesn't have integrated graphics would you do me a favour & render a short 2-3min unedited clip with no fxs in VP22, then try the same clip in VP23 with the same render settings & post whether you see if it's slower or faster on my post, thanks 👍

VP22 vs VP23 rendering speed, VP23 ½ slower than VP22...?

Reyfox wrote on 9/17/2025, 5:16 AM

@Mindmatter what I've experienced, with projects that aren't even complex, is that I have to monitor Task Manager and make sure that there is no activity for Vegas 23 in it. IF the project seems to load on the timeline, and all the thumbnails are populated, if I click on the Render button, Vegas does a silent crash to desktop. I get the "Not responding" and then, gone.

I've learned to be more patient. Something Vegas is accessing that is causing the CPU and GPU to still be active. Not sure if it is Bitdefender (anti virus) trolling in the background, but this wasn't an issue with VP22.

More testing is needed on my part to see what is happening.

bitman wrote on 9/17/2025, 11:16 AM

@Mindmatter I got a gut feeling there could be something wrong with the combination of the new decoder (in case of NVDEC) methods/pipeline if used with OFX which depend on look-ahead forward/backward of frames (I think it is called of temporal nature) such as stabilization software, noise cancelling, and anti flicker control OFX, (there maybe others). I am speculating here, but maybe it is possible that the decoding offers the frames to those applications in the wrong sequence and thus causes all sort of issues.

Mindmatter wrote on 9/21/2025, 1:28 PM

and we're back to render crashes.

I'm about to go back to V21 or even 20. This is not a way to get a job done.

File: C:\Users\Ultraman\AppData\Local\VEGAS Pro\23.0\gpu_video_x64.log
File: C:\Users\Ultraman\AppData\Local\VEGAS Pro\23.0\fileio_x64.log
File: C:\Users\Ultraman\AppData\Local\VEGAS Pro\23.0\persist.prefs
File: C:\Users\Ultraman\AppData\Local\VEGAS Pro\23.0\fileio_x64.log
File: C:\Users\Ultraman\AppData\Local\VEGAS Pro\23.0\dx_video_grovel_x64.log
File: C:\Users\Ultraman\AppData\Local\VEGAS Pro\23.0\svfx_video_grovel_x64.log
File: C:\Users\Ultraman\AppData\Local\VEGAS Pro\23.0\ocio_x64.log
File: C:\Users\Ultraman\AppData\Local\VEGAS Pro\23.0\dx_grovel_x64.log
File: C:\Users\Ultraman\AppData\Local\VEGAS Pro\23.0\vst_grovel.log
File: C:\Users\Ultraman\AppData\Local\VEGAS Pro\23.0\vegas_script_x64.log
File: C:\Users\Ultraman\AppData\Local\VEGAS Pro\23.0\hub.log
File: D:\vegas projects\Les Bâtisseurs du nord final4.veg

Problem Description
Application Name: VEGAS Pro
Application Version: Version 23.0 (Build 278)
Problem: Unmanaged Exception (0xc0000005)
Fault Module: C:\Windows\System32\DriverStore\FileRepository\nv_dispsi.inf_amd64_9cefe84c51ec4d1b\nvopencl64.dll
Fault Address: 0x00007FFB92649E60
Fault Offset: 0x0000000000149E60

Fault Process Details
Process Path: C:\Program Files\VEGAS\VEGAS Pro 23.0\vegas230.exe
Process Version: Version 23.0 (Build 278)
Process Description: VEGAS Pro
Process Image Date: 2025-09-04 (Thu Sep 04) 15:43:08

RogerS wrote on 9/21/2025, 6:20 PM

I still think we need a project with media to test. Even just the part where the render crashes could help.