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.

 

AMD Ryzen 9 5900X, 12x 3.7 GHz
32 GB DDR4-3200 MHz (2x16GB), Dual-Channel
NVIDIA GeForce RTX 3070, 8GB GDDR6, HDMI, DP, studio drivers
ASUS PRIME B550M-K, AMD B550, AM4, mATX
7.1 (8-chanel) Surround-Sound, Digital Audio, onboard
Samsung 970 EVO Plus 250GB, NVMe M.2 PCIe x4 SSD
be quiet! System Power 9 700W CM, 80+ Bronze, modular
2x WD red 6TB
2x Samsung 2TB SSD

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.

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition; Samsung S23 Ultra smart phone

Installed: Vegas Pro 13, 15, 16, 17, 18, 19, 20, 21, 22 & 23, HitFilm Pro 2021.3, DaVinci Resolve Studio 20.2, BCC 2025.5, Mocha Pro 2025.5, NBFX TotalFX 7, Neat NR 6, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 12, iZotope RX11 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11:

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 2TB Samsung 990 PCIe 4.0 NVMe M.2 PCIe SSD

D: drive: 4TB Samsung 870 SATA SSD (used for media for editing current projects)

E: drive: 2TB Samsung 870 SATA SSD

F: drive: 6TB WD 7200 rpm Black HDD 3.5"

Dell Ultrasharp 32" 4K Color Calibrated Monitor

 

LAPTOP:

Dell Inspiron 5310 EVO 13.3"

i5-11320H CPU

C Drive: 1TB Corsair Gen4 NVMe M.2 2230 SSD (upgraded from the original 500 GB SSD)

Monitor is 2560 x 1600 @ 60 Hz

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.

Newbie😁

Vegas Pro 22 B250 (VP18-21 also installed)

Win 11 Pro

AMD Ryzen 9 5950X 16 cores / 32 threads

32GB DDR4 3200

Sapphire RX6700XT 12GB Driver: 25.5.1

Gigabyte X570 Elite Motherboard

Panasonic G9, G7, FZ300

Boris FX Continuum Complete 2025.5.1, Newblue FX Total FX360, Ignite Pro V5

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.

AMD Ryzen 9 5900X, 12x 3.7 GHz
32 GB DDR4-3200 MHz (2x16GB), Dual-Channel
NVIDIA GeForce RTX 3070, 8GB GDDR6, HDMI, DP, studio drivers
ASUS PRIME B550M-K, AMD B550, AM4, mATX
7.1 (8-chanel) Surround-Sound, Digital Audio, onboard
Samsung 970 EVO Plus 250GB, NVMe M.2 PCIe x4 SSD
be quiet! System Power 9 700W CM, 80+ Bronze, modular
2x WD red 6TB
2x Samsung 2TB SSD

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?

Newbie😁

Vegas Pro 22 B250 (VP18-21 also installed)

Win 11 Pro

AMD Ryzen 9 5950X 16 cores / 32 threads

32GB DDR4 3200

Sapphire RX6700XT 12GB Driver: 25.5.1

Gigabyte X570 Elite Motherboard

Panasonic G9, G7, FZ300

Boris FX Continuum Complete 2025.5.1, Newblue FX Total FX360, Ignite Pro V5