Hi. Yes, I am using ver 302. I don't have these issues with VP22, at least when it comes to rendering. My system details are in my signature, as well as the types of files I am using. I am not doing anything extraordinary within Vegas, but I do use a lot of text and animated text events.

The details for the files I am using are as follows (from MediaInfo):

General
Complete name                            : F:\Sony HDR-CX405\2025-10-17\2025-10-17 Barbie Pinball CAM A.MP4
Format                                   : XAVC
Codec ID                                 : XAVC (XAVC/mp42/iso2)
File size                                : 15.7 GiB
Duration                                 : 43 min 12 s
Overall bit rate mode                    : Variable
Overall bit rate                         : 52.0 Mb/s
Frame rate                               : 59.940 FPS
Encoded date                             : 2025-10-17 17:04:50 UTC
Tagged date                              : 2025-10-17 17:04:50 UTC

Video
ID                                       : 1
Format                                   : AVC
Format/Info                              : Advanced Video Codec
Format profile                           : High@L4.2
Format settings                          : CABAC / 2 Ref Frames
Format settings, CABAC                   : Yes
Format settings, Reference frames        : 2 frames
Format settings, GOP                     : M=1, N=30
Format settings, Slice count             : 4 slices per frame
Codec ID                                 : avc1
Codec ID/Info                            : Advanced Video Coding
Duration                                 : 43 min 12 s
Bit rate mode                            : Variable
Bit rate                                 : 49.9 Mb/s
Maximum bit rate                         : 60.0 Mb/s
Width                                    : 1 920 pixels
Height                                   : 1 080 pixels
Display aspect ratio                     : 16:9
Frame rate mode                          : Constant
Frame rate                               : 59.940 (60000/1001) FPS
Standard                                 : NTSC
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 8 bits
Scan type                                : Progressive
Bits/(Pixel*Frame)                       : 0.402
Stream size                              : 15.1 GiB (96%)
Writing library                          : AVC Coding
Encoded date                             : 2025-10-17 17:04:50 UTC
Tagged date                              : 2025-10-17 17:04:50 UTC
Color range                              : Limited
Color primaries                          : BT.709
Transfer characteristics                 : xvYCC
Matrix coefficients                      : BT.709
Metas                                    : 3
Codec configuration box                  : avcC

Audio
ID                                       : 2
Format                                   : PCM
Format settings                          : Big / Signed
Codec ID                                 : twos
Duration                                 : 43 min 12 s
Bit rate mode                            : Constant
Bit rate                                 : 1 536 kb/s
Channel(s)                               : 2 channels
Sampling rate                            : 48.0 kHz
Bit depth                                : 16 bits
Stream size                              : 475 MiB (3%)
Encoded date                             : 2025-10-17 17:04:50 UTC
Tagged date                              : 2025-10-17 17:04:50 UTC

Other
ID                                       : 3
Type                                     : meta
Format                                   : Sony Real Time Metadata
Codec ID                                 : rtmd
Duration                                 : 43 min 12 s
Bit rate mode                            : Constant
Time code of first frame                 : 83:01:01;02
Stream size                              : 152 MiB (1%)
Encoded date                             : 2025-10-17 17:04:50 UTC
Tagged date                              : 2025-10-17 17:04:50 UTC
AutoExposureMode_FirstFrame              : Full Auto
AutoFocusSensingAreaSetting_FirstFrame   : Center Sensitive Auto
ShutterSpeed_Time_FirstFrame             : 1/60 s
CameraMasterGainAdjustment_FirstFrame    : 9.00 dB
ElectricalExtenderMagnification_FirstFra : 100%
AutoWhiteBalanceMode_FirstFrame          : Automatic

Typical timeline screenshot (From VP22 as I cannot complete this project in VP23)

It seems every time it crashes and I get the report error dialog, this is the culprit:

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:       0x00007FFB2EEF9E60
   Fault Offset:        0x0000000000149E60
 

I guess that indicates a problem with the video card? (RTX 5060 8 GB - latest studio driver)

As you mentioned old Sony Vegas, you may try to turn off HW decoder (the old Sony Vegas did not have it). You should be fine with your FullHD footage (well, I'm not sure as your timeline looks much more complicated than mine).

At least check if you have the same settings related to HW in VP23 as in VP22 ('File I/O' & 'Video' tabs)

From my personal experience HW decoder is "the thing" that causing issues. I do not have issues with it while editing 1080-60p, but with 4K-60p VP22 is crashing quite often when HW decoder is ON (not using VP23 yet).

Thanks for the detailed information. My system isn't so different from yours. I have a 5070, current studio driver and have NVDEC on. I use mostly XAVC S media from Sony cameras.

I've never seen that error message. Are there any Fx in use, esp. third party Fx that could be causing problems?

Roger - of interest if your system isn't so different, do you have the file mentioned in the crash report?

\WINDOWS\System32\DriverStore\FileRepository\nv_dispsi.inf_amd64_9cefe84c51ec4d1b\nvopencl64.dll

Out of interest my version of nvopencl64.dll is 32.0.15.8115 dated 23 aug 25 not causing an issue with V22/V23 GPU is 4080 super driver 581.15 of 28 aug 25. in general all my drivers are game drivers which I have not had issues with Vegas. Would be interesting to see details of Roger's driver. would also be nice to Know why Anthony has not upgraded (or tried ?) to V23 302?

Updating to latest game driver 581.57 changes the nvopencl64.dll file to version 32.0.15.8157. V23 loads and runs fine with it.

I've been using studio driver 581.29 for the past month without issue. I see a more recent studio driver is out so will try that too (581.57).

I installed the new driver. My file location is slightly different:

C:\Windows\System32\DriverStore\FileRepository\nvmdsi.inf_amd64_3c06e86fd1dde89a

NVopencl64.dll is now 32.0.15.8157 and is CUDA 13.0.97. Former ones were CUDA 12.

I installed the new driver. My file location is slightly different:

C:\Windows\System32\DriverStore\FileRepository\nvmdsi.inf_amd64_3c06e86fd1dde89a

NVopencl64.dll is now 32.0.15.8157 and is CUDA 13.0.97. Former ones were CUDA 12.

My nvopencl64.dll file is also version 32.0.15.8157

I forgot to mention, I don't use any 3rd part FX, just whatever is included with Vegas. I use PIP a lot, I generally use Titles & Text, with many animated Titles & text events, sometimes Flicker Control (which I positively CANNOT use in VP23), Brightness & contrast, Occasional levels and color balance, and I use the included transitions. And many PNG stills taken from the video.

trvke

@anthony-chiappette Please clarify which VP23 build you are on. You indicated early on it was 302 but your crash report says 278?

@anthony-chiappette Please clarify which VP23 build you are on. You indicated early on it was 302 but your crash report says 278?

Hi. I am on ver 302. That may have been an older crash report before I installed 302. I think I just picked the first one I could find.

@anthony-chiappette The Vegas has worked a lot on improving playback, especially with HW decoding, new pipelines etc.., however, for some video formats and in combination with a 5000 series GPU (which means new HW and immature drivers) that could potentially be a recipe for decoding and associated rendering issues.
I would take up the advice of @fifonik and eighter disable HW decoding in the IO options of Vegas, or/and enable Legacy ACV decoding, and see how it goes from there.
If the rendering keeps on failing, one thing that may help is to set the number of rendering threads to just 1 in the Vegas options.
One more thing, before rendering, close Vegas, launch it again, do not play or do anything, wait a few minutes until Vegas settles, and then start rendering.

I agree with the original poster. I'm not an advanced user by any means. I've only use it to create slides and simple editing. In the two days I've used it, I've come across Vegas Pro 23 freezing, mis-behaving, and moving at snail pace twice when editing and moving clips in the timeline editor. My PC is not a slouch. My specs are: Intel 13900 CPU, 96gb DDR5, RTX 4090, SSDs, etc. Closing and re-opening Vegas gets it back into an operating state again, but it's buggy and not stable like Vegas Pro 22. I hope these problems will be sorted out on the next patch release.

@anthony-chiappette I can't use any version of vp23 for some things but it's been great for me editing, grading, and rendering multicam video projects on an 11900k with a 5080 using the same version driver you mentioned. Maybe you're issue is with png's which I only use a little bit. Or animated text which I tend to render to an intermediate video clip. Other things I might do differently is to disable my igpu driver in Windows or turn it off in bios. And not use vp23 nvenc renders on the timeline... vp23 seems to optimize nvenc renders exclusively for streaming and not for editing... they're fine for upload to YouTube but if I need to put an intermediate on the timeline, I render it with MainConcept.

Thanks, Howard. I'm sure all the issues I have are with NVEnc, because it always points to nvidia DLL file causing the fault. If I use MainConcept, it takes quite a bit longer to render. I create these videos to upload to YouTube.

My iGPU is diabled in BIOS. I use PNG and animated text extensively in my videos, but don't have these problems in VP22. Another issue I face in 23 is having to render several times before it's successful. It seems random because most times I can render once without issue. Other times, VP23 will crash while rendering, at different points, so I can't attribute it to a specific event on the timeline causing the crash. Sometimes it will work the 2nd time, sometimes it works the 3rd time, etc. It doesn't matter if I reboot between attempts or not. The other night the render failed 3 times, at different points. On the 4th attempt, the video rendered completely.

At this point, the only reason I am still using 23 is because of the significant increase in render speeds.

The other night the render failed 3 times, at different points. On the 4th attempt, the video rendered completely.

At this point, the only reason I am still using 23 is because of the significant increase in render speeds.

Sounds quite contradicting. What sense does it make to use VP23 because it renders faster, when you have to make 4 attempts to get a completed render? Where is the advantage? One attempt with a slower render that completed, is much faster than 4 attempts with a faster render.

@anthony-chiappette did you try my advice on enable Legacy AVC decoding in the I/O file options?
Render crashes do not necessarily originate from NV encoding, but the root cause could be decoding.
The encoding engine needs to decode first the source material before the encode...

I run VP23 with legacy AVC decoding enabled. I have to, to avoid decoding issues with my RTX 5090 in the new Vegas engine.
 

J'utilise Vegas depuis des années. Je n'ai jamais eu de problème avec la version Sony. Au fil du temps, Magix Vegas s'est légèrement amélioré. En revanche, VP23 est tout le contraire.

Je peux monter une vidéo pendant 5 heures sans problème. Puis, soudain, le logiciel se bloque et les problèmes s'enchaînent. Quant au rendu, c'est aléatoire : soit ça marche, soit ça ne marche pas. Je peux essayer de rendre mon projet trois fois, Vegas plante à différentes étapes du processus. Je peux réessayer, et là, miracle ! Le rendu se fait correctement. J'imagine mal qu'un professionnel de la diffusion puisse être satisfait de ce logiciel.

Je sais que c'est nouveau, mais j'ai du mal à croire que les tests ont été concluants. Ce logiciel n'était pas prêt à être commercialisé et aurait dû être retardé. À quoi sert un moteur de rendu plus rapide si le rendu est impossible ?

Excusez-moi si je froisse quelqu'un, mais j'en ai assez du 23.

Pour que ça fonctionne correctement avec vegas 23 il faut une machine nouvelle avec windows 11 etc.cette machine fonctionne mal avec vegas 18, mais dès que j'ai utiliser Vegas 23 avec ma machine windows 11 tout a changé et c'est ultra rapide . exemple un montage de 24 minutes en 4K le rendu c'est fait en 10 minutes en utilisant NVENC de Nvidia, alors qu'avec Vegas 18 ça plantait tout le temps.

Donc pour la nouvelle version de Vegas 23 ça prend une machine nouvelle et pour un vieux Vegas comme la version 18 ça prend une vielle machine les deux vont ensemble.

Bonne chance

Serge

I have to agree.

My method is to upgrade to the next version of Vegas JUST before they close it off and release the next major release.

Its at that point the old one is almost stable.

That said every version I can think of and Ive been using since v8 is a crashfest. They need to do an Apple and halt the gizmos and just spend a year either rewriting the code properly or fixing the bugs of which there are many.

The users here are great but the advice seen a lot of "turn off the latest encode and decode support" which kills the whole point of spending £1000-2000 on a fast GPU is backward and the equiv of saying "drive your car in limp home mode" to get the thing to run.

I really hope they get their finger out and sort it. Stuff the AI crap. Forget all the whizz bang stuff. Make it work reliably.