@Mindmatter I don't get crashes but Boris fx's, some Boris fx's, slow down VP playback & rendering. Sometimes the native VP version of an fx will play at full fps but instead use a Boris fx that does the same thing & playback can falter. NewBlue fxs also play well compared to Boris fxs 🤷‍♂️

Do you need Boris FX? I never used or missed those FX in 20 years VegasPro.

Do you need Boris FX? Everyone must decide this for themselves, but I certainly do, it is my bread and butter for editing. It has evolved over the last few years to become quite stable and work well with Vegas, and they do offer a lot of improvements, new features and fixes over each running year. As @MikeS mentioned, their support is exemplary, Magix could learn a few things on that point. Compared to Boris FX, Magix support is like a black hole in space. As @Gid mentioned some Boris plugins (especially some using AI) can be pretty heavy on your system and slow down your system, but I wrote some one click scripts to disable them while editing, and enable them all just before rendering. The only Boris FX plugin I need to be on my toes for crashes is the particle illusion. In the past I invested in quite some NewBlue FX, although great plugins, it is now lightyears behind Boris FX.

@Mindmatter There are 2 things you may want to try, the latest Vegas 22 (b250) I assume has already some work done on the graphical engine towards a more elaborate rewrite in the future versions.
You may want to avoid issues by disabling HW accelerated decoding (put it to off) in the IO- preference tab.
This may help with editing and rendering (as decoding also is used in rendering - obviously).
For rendering issues in particular, you could try to set the number of rendering threads to 1 only.

Thanks for the input everyone!

@Mindmatter There are 2 things you may want to try, the latest Vegas 22 (b250) I assume has already some work done on the graphical engine towards a more elaborate rewrite in the future versions.
You may want to avoid issues by disabling HW accelerated decoding (put it to off) in the IO- preference tab.
This may help with editing and rendering (as decoding also is used in rendering - obviously).
For rendering issues in particular, you could try to set the number of rendering threads to 1 only.

Thamnks, I'll try that right now. I just had another render crash, and it seems I can't get around rendering every single BCC event to an extra intermediate...oh well.

Extra Information
   File:                C:\Users\Ultraman\AppData\Local\VEGAS Pro\22.0\gpu_video_x64.log
   File:                C:\Users\Ultraman\AppData\Local\VEGAS Pro\22.0\fileio_x64.log
   File:                C:\Users\Ultraman\AppData\Local\VEGAS Pro\22.0\persist.prefs
   File:                
   File:                C:\Users\Ultraman\AppData\Local\VEGAS Pro\22.0\dx_video_grovel_x64.log
   File:                C:\Users\Ultraman\AppData\Local\VEGAS Pro\22.0\svfx_video_grovel_x64.log
   File:                C:\Users\Ultraman\AppData\Local\VEGAS Pro\22.0\ocio_x64.log
   File:                C:\Users\Ultraman\AppData\Local\VEGAS Pro\22.0\dx_grovel_x64.log
   File:                C:\Users\Ultraman\AppData\Local\VEGAS Pro\22.0\vst_grovel.log
   File:                C:\Users\Ultraman\AppData\Local\VEGAS Pro\22.0\vegas_script_x64.log
   File:                D:\vegas projects\pierrseche V22-9.veg
   File:                F:\vegas projects\pierrseche V22-9.veg

Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 22.0 (Build 250)
   Problem:             Unmanaged Exception (0xc0000005)
   Fault Module:        C:\Program Files\VEGAS\VEGAS Pro 22.0\OFX Video Plug-Ins\Vfx1.ofx.bundle\Contents\Win64\Vfx1.ofx
   Fault Address:       0x00007FFBD017951F
   Fault Offset:        0x000000000071951F

Fault Process Details
   Process Path:        C:\Program Files\VEGAS\VEGAS Pro 22.0\vegas220.exe
   Process Version:     Version 22.0 (Build 250)
   Process Description: VEGAS Pro
   Process Image Date:  2025-04-29 (Tue Apr 29) 15:59:48

@Mindmatter What BCC fxs are you using & causing the problems, also how are you applying them to what media?

I've been using Boris effects for several years now. I have their current version that is fully up to date. Not one crash because of using it. I experiment with it to learn new things about it, but it is essential in my video editing workflow. Go to Boris forum and make a post there if you strongly believe it is Boris that is at fault.

@Mindmatter Best to lodge the issue over in the BCC User forum with full details, they are very responsive and quick to solve issues with Vegas Pro. Currently i am using their latest version with absolutely no issues at all..... Which of their filter triggers this crash?

I just did another round of troubleshooting and exported tracks one by one to see which one is problematic.

The crashes occur alweays around the same area on a specific track that has events with BCC magic sharp in them. Those events really need magic sharp as the now disfuntional eye AF on my Sony FX3 had messed up an entire sequence.
Yet another crash report points to BCC. I did send them a report now, I'll see what they say.

Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 22.0 (Build 250)
   Problem:             Unmanaged Exception (0xc0000005)
   Fault Module:        C:\Program Files\Common Files\OFX\Plugins\BorisFX\Continuum\BCCPlus\BCC+.ofx.bundle\Contents\Win64\BCC+.ofx
   Fault Address:       0x0000000071B37327
   Fault Offset:        0x0000000001287327

Fault Process Details
   Process Path:        C:\Program Files\VEGAS\VEGAS Pro 22.0\vegas220.exe
   Process Version:     Version 22.0 (Build 250)
   Process Description: VEGAS Pro
   Process Image Date:  2025-04-29 (Tue Apr 29) 15:59:48