Constants shutdowns & render failures since the beginning

Gid wrote on 9/11/2025, 4:44 PM

My system is powerful - AMD Ryzen 9 9850X3D CPU, NVidia Geforce RTX 5070Ti 16GB video card, 64GB RAM

Google -

Yes, the hypothetical AMD Ryzen 9 9850X3D would feature integrated Radeon Graphics, similar to other AMD Ryzen 9000-series processors, although the model number "9850X3D" has not been released and likely refers to the Ryzen 7 9800X3D or the Ryzen 9 9950X3D. These integrated graphics are not for serious gaming but can handle non-gaming tasks like web browsing, media playback, and office application

Download the Trial of Vegas Pro 23 first.

I have a post where I am asking about render speeds. The people who have Intel CPU's are getting good render speeds but myself & 2 other with AMD CPU's are getting slower render times than we were getting n Vegas Pro 22. You're CPU does apparently have some basic integrated graphics whereas ours don't. So If you do download the trial would you render a short 2-3min unedited clip with no fxs in Vegas Pro 22 & then try it in Vegas Pro 23 & post your results on my post, I'd appreciate it, it'll be interesting & informative to know how you get on. 👍

My post - https://www.vegascreativesoftware.info/us/forum/vp22-vs-vp23-rendering-speed-vp23-slower-than-vp22--149593/?page=1

Saying that Vegas Pro 23 does seem to be better than previous versions, also I must add that since Vegas Pro 21 - 22 I have next to no crashes, the previous Vegas Pro 18,19 & 20 crashed constantly, so why you are getting crashes is curious.. I think the MediaInfo & your project/render settings would be needed?

RogerS wrote on 9/11/2025, 5:11 PM

My guess is this is an issue where VEGAS is having trouble decoding the media. Please share MediaInfo as requested and perhaps tweaks on the capture side would lead to a better editing experience.

23 does have many decoding improvements and bugfixes over 22 so consider the trial.

For crashes are there any hints in problem details in the crash reporter or in Windows Reliability History?

Lee-James wrote on 9/11/2025, 5:53 PM

Ok,

Not sure what you mean by MediaInfo. I capture video and audio using NVidia ShadowPlay and it's in MP4 format. I then import each piece of MP4 video into the programme and then drag it onto the time line and edit on the fly, I believe the term is.

Right now, with the GPU acceleration ON, I get regular crashes, so I turn it OFF when I edit - then when I'm ready to render a final video, the output is in MP4 and I then turn ON to render because the render just seems to really struggle every time it encounters any transition! But it seems to cope better when I have GPU acceleration ON. I out put the video in INTERNET HD 1080p 29.97 fps (NVENC).

Interestingly, the Preview window seems to default to 1120 x 630 x 32 - is this correct?

Hope this helps

Lee

EricLNZ wrote on 9/11/2025, 6:22 PM

@Lee-James https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/

RogerS wrote on 9/11/2025, 6:55 PM

Thanks Eric.

Shadowplay recordings are often variable framerate and fine for viewing but not great for editing.

Would you consider OBS?

One workaround could be doing a conversion. Download the free ShutterEncoder, select your video, go to output format h264 and in advanced options limit the GOP to 60 (I assume your framerate). Try replacing the old media with the new one in VEGAS project media. Keep the GPU on and my bet is you won't have crashes.

Your render format looks good.

I'd be happy to test a Shadowplay video if you could make one available for download.

Lee-James wrote on 9/11/2025, 8:04 PM

Sorry guys,

This is all way above me!

Eric - My source media - I assume you mean the MP4 files of video I have captured using ShadowPlay? If I right click the file there is no option to open with TEXT, so I tried selecting Notepad to open the file and the thing just hung up!

Roger S - I actually have OBS but I find it really confusing to use - which is why I went for ShadowPlay which I have used for years. Yes, I might try a conversion and use a different format as you suggest.

I'll give ShutterEncoder a try for next next review video - which I'm going to do this weekend.

Ok three attempts to upload a ShadowPlay MP4 file - all failed I'm afraid - (19 seconds of footage and 154k). . . .

sorry

Lee

EricLNZ wrote on 9/11/2025, 8:43 PM

@Lee-James You need to download MediaInfo as per the link in Nick Hope's thread which gives you https://mediaarea.net/en/MediaInfo Then follow Nick's instructions.

It is a small, free, useful utility used extensively by forum members to assist with resolving problems. Alternatively if you have MPC-BE or MPC-HC player installed the MediaInfo tab they have provides the same extensive information which looks like this which is from MPC-BE

RogerS wrote on 9/11/2025, 11:53 PM

To share a file you need a service like Google Drive or Dropbox, etc.

If you want to try OBS we could recommend settings.

Lee-James wrote on 9/12/2025, 8:11 AM

Ok,

Downloaded MediaInfo and here is the TEXT output from one MP$ video file :-

______________________________________________________________

General
Complete name : C:\Users\LeeJames\Videos\NVIDIA\Microsoft Flight Simulator\KAVALA-LGKV-MM-SIMS-INTRO.mp4
Format : MPEG-4
Format profile : Base Media / Version 2
Codec ID : mp42 (isom/mp42)
File size : 799 MiB
Duration : 1 min 46 s
Overall bit rate : 63.2 Mb/s
Frame rate : 59.940 FPS
Recorded date : 2025
Encoded date : 2025-09-09 11:59:18 UTC
Tagged date : 2025-09-09 11:59:18 UTC

Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L5.2
Format settings : CABAC / 3 Ref Frames
Format settings, CABAC : Yes
Format settings, Reference frames : 3 frames
Format settings, GOP : M=1, N=30
Codec ID : avc1
Codec ID/Info : Advanced Video Coding
Duration : 1 min 46 s
Source duration : 1 min 46 s
Bit rate : 63.0 Mb/s
Width : 2 880 pixels
Height : 1 620 pixels
Display aspect ratio : 16:9
Frame rate mode : Variable
Frame rate : 59.940 (59940/1000) FPS
Minimum frame rate : 59.133 FPS
Maximum frame rate : 60.647 FPS
Original frame rate : 60.000 FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.225
Stream size : 797 MiB (100%)
Source stream size : 797 MiB (100%)
Title : VideoHandle
Encoded date : 2025-09-09 11:59:18 UTC
Tagged date : 2025-09-09 11:59:18 UTC
Color range : Limited
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709
mdhd_Duration : 106006
Codec configuration box : avcC

Audio
ID : 2
Format : AAC LC
Format/Info : Advanced Audio Codec Low Complexity
Codec ID : mp4a-40-2
Duration : 1 min 45 s
Source duration : 1 min 45 s
Bit rate mode : Constant
Bit rate : 192 kb/s
Nominal bit rate : 96.0 kb/s
Channel(s) : 2 channels
Channel layout : L R
Sampling rate : 48.0 kHz
Frame rate : 46.875 FPS (1024 SPF)
Compression mode : Lossy
Stream size : 2.42 MiB (0%)
Source stream size : 2.42 MiB (0%)
Title : SoundHandle / System sounds
Encoded date : 2025-09-09 11:59:18 UTC
Tagged date : 2025-09-09 11:59:18 UTC
mdhd_Duration : 105920

______________________________________________________________

Ok, I have Dropbox so I'll put up this same file for Roger to access. Hopefully it will work.

Thanks guys,

Lee

Lee-James wrote on 9/12/2025, 8:27 AM

Ok,

RogerS - here is the LINK to the MP4 file in DropBox, created with ShadowPlay:-

https://www.dropbox.com/scl/fi/1stdk3wi3lz09bqhvmkn4/KAVALA-LGKV-MM-SIMS-INTRO.mp4?rlkey=ln77qe3z7ahc03vgo3wezhsu4&dl=0

Lee-James wrote on 9/12/2025, 10:43 AM

Well,

Wow! Firstly, I downloaded ShutterEncoder and found two desktop shortcuts - ShutterEncoder and ShutterEncoder OpenGL. I tried ShutterEncoder and found that after a few seconds, it all went white on me, as if the GUI was just breaking down on the desktop! I could not see the various items in the GUI and had to shut it down.

So next, I tried the OpenGL version and that seemed to be stable. To be honest, I don't fully understand how it works, however I found the Output option and selected H264, but I don't know what GOP is and I could not find any "advanced options" anywhere on the GUI. I did, however set the NVidia acceleration option at the bottom.

I selected each of the ShadowPlay recorded MP4 files and did the conversion and placed each NEW MP4 file in a separate folder. Next, I ran Vegas Pro 22 and loaded my pre-saved review format layout. I added my footage and began editing on the timeline. However, after a few minutes, Vegas Pro once again froze on me!

So - I have downloaded and installed and registered the Vegas Pro 23 trial version. Once again, I loaded my review layout and imported the old *.veg file containing my current project from version 22, into Vegas 23. I made sure that I worked with a copy of the project, not the original.

Within 5 seconds, Vegas pro 23 froze on me!

I do not know what is going on here! it's really driving me mad! I have a new desktop PC, fully updated with Windows 11 and I cannot account for this.

Sorry to rant. Thanks for your continuing help.

Lee

andyrpsmith wrote on 9/12/2025, 11:43 AM

Lee, tried your file in V23 and it plays perfectly. What exactly is being loaded into V23 and then it crashes in 5 seconds? I added the clip twice and used a blinds transition which at Best Full made the new engine in V23 slow down during the transition. My system is comparable to yours in PC power. At Best Quarter it ran at full frame rate. I see you have a 50 series GPU, I not sure V23 is optimised for the 50 series yet.

Lee-James wrote on 9/12/2025, 12:59 PM

Andy,

Here's what I can tell you....

I simply ran V23 and then loaded the V22 project I was working on, directly into V23 from a separate copy of the V22 project, not the original. I started the video on the time line and when I simply wanted to move a piece of footage in the timeline, V23 froze solid!

Maybe I should set up V23 and then recreate the project, piece by piece from scatch instead of importing it into V23 ?

**********

I am working in V22 at the moment, on another review project and here is what I see . . .

When I have the GPU acceleration set to ON, it is not long before V22 freezes. I get maybe 10 minutes or so and it stops and I have to bring up Task Manager to shut it down. What I also notice is that any transitions I use on the time line, the preview window seems to struggle a bit.

Right now I get the most longevity in V22 if I turn the GPU Acceleration to OFF. Ok, when I use a transition and run it on the timeline to view the effect - watching it the Preview window the Preview really struggles!! And to be honest with the GPU Acceleration OFF, when I attempt a render of a finished project, usually somewhere along the line, the render stops . . . and I have to again stop the programme by using Task Manager (Vegas just sits there not responding - I have to shut it down).

Now if I turn GPU acceleration ON for the rendering process, the render has a much better chance of succeeding - but the downside is that with it ON, editing results in more frequent crashes, so right now I am turning GPU OFF when editing and then back ON for rendering the project - subject to the various freezes that may occur during the editing session.

I'm still getting freezes in V22 using these methods - but the situation varies. Right now, I cannot think of any one time where an editing session in any of the Vegas Pro versions (I purchased and used Pro 17, 18, 19, 20 and 22) has not resulted in a freeze - meaning shutdown using Task Manager and restarting the programme.

Someone mentioned Intel as opposed to AMD ? I have used Intel PC's all my computing career. But this year I went with AMD Ryzen, the fastest CPU I could buy because they are out-performing Intel and there is still the Intel bug . . ..

**********************

So I will try over the weekend, to re-construct a project from scratch in V23 and see if that can work.

As ever, any advice here would be greatly appreciated.

Thank you,

Lee

andyrpsmith wrote on 9/12/2025, 2:23 PM

What we really need is for you to upload a small project, a few clips that you normally work with and the various edits that you do that ends in a crash and the veg file so we can run it and see what is going on. Also what render template you are using and the settings. It would be good to keep it under 5GB.

andyrpsmith wrote on 9/12/2025, 2:37 PM

The other thing we can do is to look at the file Vegas produces when it's evaluating your GPU, it will tell you if Vegas can use it. In V22 it can be found here:

C:\Users\username\AppData\Local\VEGAS Pro\22.0\gpu_video_x64.log (if your version is V22.0, if not it will be V??.0)

As V23 is so new I will have to see if it has the same file in the same location. Anyway look for the V22 one. It can be opened in notepad.

Update: yes there is a file for V23, please post the contents on here as you did with mediainfo data.

andyrpsmith wrote on 9/12/2025, 2:48 PM

Here is my V23 GPU file output:

INFO 2025-09-12 16:35:50 *** Start of GPU-accelerated video processing log ***
INFO 2025-09-12 16:35:50 VEGAS Pro 23.0
INFO 2025-09-12 16:35:50 Version 23.0 (Build 278)
INFO 2025-09-12 16:35:50
INFO 2025-09-12 16:35:50 [system device log] **************************************************************************************
INFO 2025-09-12 16:35:50 [system device log]
INFO 2025-09-12 16:35:50 [system device log] -- NVIDIA GeForce RTX 4080 SUPER --
INFO 2025-09-12 16:35:50 [system device log] MX ID: 0x27c1d5d4
INFO 2025-09-12 16:35:50 [system device log] DXGI description: NVIDIA GeForce RTX 4080 SUPER
INFO 2025-09-12 16:35:50 [system device log] LUID: 0x0:0x27c1d5d4
INFO 2025-09-12 16:35:50 [system device log] Vendor: 0x10de
INFO 2025-09-12 16:35:50 [system device log] ID/SubSys/Rev: 0x2702, 0xf30510b0, 0xa1
INFO 2025-09-12 16:35:50 [system device log] Memory: 15.671 / 0 / 47.846 GB (video/system/shared)
INFO 2025-09-12 16:35:50 [system device log] Flags: 0
INFO 2025-09-12 16:35:50 [system device log]
INFO 2025-09-12 16:35:50 [system device log]
INFO 2025-09-12 16:35:50 [system device log] -- Microsoft WARP device --
INFO 2025-09-12 16:35:50 [system device log] MX ID: 0x12d1b
INFO 2025-09-12 16:35:50 [system device log] DXGI description: Microsoft Basic Render Driver
INFO 2025-09-12 16:35:50 [system device log] LUID: 0x0:0x12d1b
INFO 2025-09-12 16:35:50 [system device log] Vendor: 0x1414
INFO 2025-09-12 16:35:50 [system device log] ID/SubSys/Rev: 0x8c, 0x0, 0x0
INFO 2025-09-12 16:35:50 [system device log] Memory: 0 / 0 / 47.846 GB (video/system/shared)
INFO 2025-09-12 16:35:50 [system device log] Flags: 2
INFO 2025-09-12 16:35:50 [system device log]
INFO 2025-09-12 16:35:50 [system device log] **************************************************************************************
INFO 2025-09-12 16:35:50 OpenGL_Initialize
INFO 2025-09-12 16:35:50 GLEW Init OK
INFO 2025-09-12 16:35:50 WGLEW Init OK
INFO 2025-09-12 16:35:50 GLC: 0000000000010000
INFO 2025-09-12 16:35:50 GL 10-bit Available: FALSE
INFO 2025-09-12 16:35:50 GL 10-bit Pixel Format Index: 0
INFO 2025-09-12 16:35:50 GL_VENDOR: NVIDIA Corporation
INFO 2025-09-12 16:35:50 GL_RENDERER: NVIDIA GeForce RTX 4080 SUPER/PCIe/SSE2
INFO 2025-09-12 16:35:50 GL_VERSION: 4.6.0 NVIDIA 581.15
INFO 2025-09-12 16:35:50 Dib_OpenGL Init OK
INFO 2025-09-12 16:35:50
INFO 2025-09-12 16:35:50 OpenCL_Initialize
INFO 2025-09-12 16:35:51 Platforms: 1
INFO 2025-09-12 16:35:51 Platform: 0
INFO 2025-09-12 16:35:51 Vendor: NVIDIA Corporation
INFO 2025-09-12 16:35:51 Name: NVIDIA CUDA
INFO 2025-09-12 16:35:51 Version: OpenCL 3.0 CUDA 13.0.84
INFO 2025-09-12 16:35:51 Profile: FULL_PROFILE
INFO 2025-09-12 16:35:51 Extensions: cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_fp64 cl_khr_3d_image_writes cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll cl_nv_d3d10_sharing cl_khr_d3d10_sharing cl_nv_d3d11_sharing cl_nv_copy_opts cl_nv_create_buffer cl_khr_int64_base_atomics cl_khr_int64_extended_atomics cl_khr_device_uuid cl_khr_pci_bus_info cl_khr_external_semaphore cl_khr_external_memory cl_khr_external_semaphore_win32 cl_khr_external_memory_win32 cl_khr_semaphore
INFO 2025-09-12 16:35:51
INFO 2025-09-12 16:35:51 [system device log] initializing MxGpuDevice...
INFO 2025-09-12 16:35:51 [system device log] found DX12 support - initializing MultiGPU
INFO 2025-09-12 16:35:51 [system device log] create DX12 device. feature level=49408, HRESULT=0
INFO 2025-09-12 16:35:51 [system device log] create DX11 device. HRESULT=0
INFO 2025-09-12 16:35:51 [system device log] setting private data - . HRESULT=0
INFO 2025-09-12 16:35:51 [system device log] CreateDevice: switching multithread protection ON

INFO 2025-09-12 16:35:51 [system device log] IDXGIAdapter4: isSoftware 0

INFO 2025-09-12 16:35:51 [system device log] IDXGIAdapter4: is ACG compatible 1

INFO 2025-09-12 16:35:51 [system device log] IDXGIAdapter4: has monitored fences 1

INFO 2025-09-12 16:35:51 [system device log] IDXGIAdapter4: has non monitored fences 0

INFO 2025-09-12 16:35:51 [system device log] IDXGIAdapter4: has keyed mutex conformance 1

INFO 2025-09-12 16:35:51 [system device log] .. end initializing MxGpuDevice
INFO 2025-09-12 16:35:51 [system device log] initializing MxGpuDevice...
INFO 2025-09-12 16:35:51 [system device log] found DX12 support - initializing MultiGPU
INFO 2025-09-12 16:35:51 [system device log] create DX12 device. feature level=49408, HRESULT=0
INFO 2025-09-12 16:35:51 [system device log] create DX11 device. HRESULT=0
INFO 2025-09-12 16:35:51 [system device log] setting private data - . HRESULT=0
INFO 2025-09-12 16:35:51 [system device log] CreateDevice: switching multithread protection ON

INFO 2025-09-12 16:35:51 [system device log] IDXGIAdapter4: isSoftware 1

INFO 2025-09-12 16:35:51 [system device log] IDXGIAdapter4: is ACG compatible 1

INFO 2025-09-12 16:35:51 [system device log] IDXGIAdapter4: has monitored fences 1

INFO 2025-09-12 16:35:51 [system device log] IDXGIAdapter4: has non monitored fences 0

INFO 2025-09-12 16:35:51 [system device log] IDXGIAdapter4: has keyed mutex conformance 1

INFO 2025-09-12 16:35:51 [system device log] .. end initializing MxGpuDevice
INFO 2025-09-12 16:35:51 Devices: 1
INFO 2025-09-12 16:35:51 Device: 0
INFO 2025-09-12 16:35:51 Type: GPU
INFO 2025-09-12 16:35:51 Vendor: NVIDIA Corporation
INFO 2025-09-12 16:35:51 Name: NVIDIA GeForce RTX 4080 SUPER
INFO 2025-09-12 16:35:51 Profile: FULL_PROFILE
INFO 2025-09-12 16:35:51 Version: OpenCL 3.0 CUDA
INFO 2025-09-12 16:35:51 C version: OpenCL C 1.2
INFO 2025-09-12 16:35:51 Extensions: cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_fp64 cl_khr_3d_image_writes cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll cl_nv_d3d10_sharing cl_khr_d3d10_sharing cl_nv_d3d11_sharing cl_nv_copy_opts cl_nv_create_buffer cl_khr_int64_base_atomics cl_khr_int64_extended_atomics cl_khr_device_uuid cl_khr_pci_bus_info cl_khr_external_semaphore cl_khr_external_memory cl_khr_external_semaphore_win32 cl_khr_external_memory_win32 cl_khr_semaphore
INFO 2025-09-12 16:35:51 Driver version: 581.15
INFO 2025-09-12 16:35:51 Available: Yes
INFO 2025-09-12 16:35:51 Compiler: Yes
INFO 2025-09-12 16:35:51 Image support: Yes
INFO 2025-09-12 16:35:51 Unified memory: No
INFO 2025-09-12 16:35:51 Vendor ID: 4318
INFO 2025-09-12 16:35:51 Compute units: 80
INFO 2025-09-12 16:35:51 Work dimensions: 3
INFO 2025-09-12 16:35:51 Clock Frequency: 2580
INFO 2025-09-12 16:35:51 Image reads: 256
INFO 2025-09-12 16:35:51 Image writes: 32
INFO 2025-09-12 16:35:51 Samplers: 32
INFO 2025-09-12 16:35:51 Workgroup size: 1024
INFO 2025-09-12 16:35:51 Image width: 32768
INFO 2025-09-12 16:35:51 Image height: 32768
INFO 2025-09-12 16:35:51 Parameter size: 32764
INFO 2025-09-12 16:35:51 Maximum alloc: 4292739072
INFO 2025-09-12 16:35:51 Memory size: 17170956288
INFO 2025-09-12 16:35:51 Local memory: 49152
INFO 2025-09-12 16:35:51 Work item sizes: 1024, 1024, 64
INFO 2025-09-12 16:35:51 Out of order Q: Yes
INFO 2025-09-12 16:35:51 Profiling Q: Yes
INFO 2025-09-12 16:35:51 NV compute (maj):8
INFO 2025-09-12 16:35:51 NV compute (min):9
INFO 2025-09-12 16:35:51 NV warp size: 32
INFO 2025-09-12 16:35:51 NV overlap: Yes
INFO 2025-09-12 16:35:51 NV integ. mem: No
INFO 2025-09-12 16:35:51 Device is compatible.
INFO 2025-09-12 16:35:51 This is the selected device.
INFO 2025-09-12 16:35:51
INFO 2025-09-12 16:35:51 Attempting to create CL<->DX11 interop context on device 'NVIDIA GeForce RTX 4080 SUPER'
INFO 2025-09-12 16:35:51 CL<->DX11 context: 0000000015947040
INFO 2025-09-12 16:35:51 Command queue: 000000002722ABC0
INFO 2025-09-12 16:35:51 Buffer write mapping flags: 0x4
INFO 2025-09-12 16:35:51 2DWGO: 16x16
INFO 2025-09-12 16:35:51 HWBL: 1
INFO 2025-09-12 16:35:51 OCL compile, bin: 91426185, kernels: kddb9a9580 kddb9a9581 kddb9a9582
INFO 2025-09-12 16:35:52 CPWB successful
INFO 2025-09-12 16:35:52 BP successful
INFO 2025-09-12 16:35:52 OCL compile, bin: 8a7f119a, kernels: k4fce1a180 k4fce1a181 k4fce1a182 k4fce1a183 k4fce1a184
INFO 2025-09-12 16:35:52 CPWB successful
INFO 2025-09-12 16:35:52 BP successful
INFO 2025-09-12 16:35:52 OCL compile, bin: 6311d26d, kernels: k13650b260 k13650b261 k13650b262 k13650b263
INFO 2025-09-12 16:35:52 CPWB successful
INFO 2025-09-12 16:35:52 BP successful
INFO 2025-09-12 16:35:52 OCL compile, bin: b5443ede, kernels: kf2c0fea20 kf2c0fea21 kf2c0fea22 kf2c0fea23 kf2c0fea24 kf2c0fea25 kf2c0fea26 kf2c0fea27 kf2c0fea28 kf2c0fea29 kf2c0fea210 kf2c0fea211 kf2c0fea212 kf2c0fea213 kf2c0fea214 kf2c0fea215 kf2c0fea216
INFO 2025-09-12 16:35:52 CPWB successful
INFO 2025-09-12 16:35:52 BP successful
INFO 2025-09-12 16:35:52 OCL compile, bin: 21e52674, kernels: k201db7240 k201db7241 k201db7242 k201db7243 k201db7244 k201db7245 k201db7246 k201db7247 k201db7248 k201db7249 k201db72410 k201db72411 k201db72412 k201db72413 k201db72414 k201db72415 k201db72416 k201db72417 k201db72418 k201db72419 k201db72420 k201db72421 k201db72422 k201db72423 k201db72424 k201db72425 k201db72426 k201db72427 k201db72428 k201db72429 k201db72430 k201db72431 k201db72432 k201db72433 k201db72434 k201db72435 k201db72436 k201db72437 k201db72438 k201db72439 k201db72440 k201db72441 k201db72442 k201db72443 k201db72444 k201db72445 k201db72446 k201db72447 k201db72448 k201db72449 k201db72450 k201db72451 k201db72452
INFO 2025-09-12 16:35:52 CPWB successful
INFO 2025-09-12 16:35:52 BP successful
INFO 2025-09-12 16:35:57 DX12_HDR_Initialize
INFO 2025-09-12 16:35:57 DX12 HDR Available: FALSE
INFO 2025-09-12 16:35:57
INFO 2025-09-12 16:36:02 OCL compile, bin: 4ce99973, kernels: k2c14d5f30
INFO 2025-09-12 16:36:02 CPWB successful
INFO 2025-09-12 16:36:02 BP successful
INFO 2025-09-12 16:41:35 OCL compile, bin: d29e8d1d, kernels: k556c32f70
INFO 2025-09-12 16:41:35 CPWB successful
INFO 2025-09-12 16:41:35 BP successful

RogerS wrote on 9/12/2025, 7:01 PM

Well,

Wow! Firstly, I downloaded ShutterEncoder and found two desktop shortcuts - ShutterEncoder and ShutterEncoder OpenGL. I tried ShutterEncoder and found that after a few seconds, it all went white on me, as if the GUI was just breaking down on the desktop! I could not see the various items in the GUI and had to shut it down.

So next, I tried the OpenGL version and that seemed to be stable. To be honest, I don't fully understand how it works, however I found the Output option and selected H264, but I don't know what GOP is and I could not find any "advanced options" anywhere on the GUI. I did, however set the NVidia acceleration option at the bottom.

I selected each of the ShadowPlay recorded MP4 files and did the conversion and placed each NEW MP4 file in a separate folder. Next, I ran Vegas Pro 22 and loaded my pre-saved review format layout. I added my footage and began editing on the timeline. However, after a few minutes, Vegas Pro once again froze on me!

So - I have downloaded and installed and registered the Vegas Pro 23 trial version. Once again, I loaded my review layout and imported the old *.veg file containing my current project from version 22, into Vegas 23. I made sure that I worked with a copy of the project, not the original.

Within 5 seconds, Vegas pro 23 froze on me!

I do not know what is going on here! it's really driving me mad! I have a new desktop PC, fully updated with Windows 11 and I cannot account for this.

Sorry to rant. Thanks for your continuing help.

Lee

Here's what it should look like in ShutterEncoder. In general I'd use with hardware acceleration set to none to preserve more quality and avoid potential issues with the NVIDIA encoder you may also be experiencing with Shadowplay. Let's get a nice clean x264 render for testing. Here's a rencode I did: https://www.dropbox.com/scl/fi/zlby4u4vu1hptjy6h74dk/KAVALA-LGKV-MM-SIMS-INTRO_H.264.mp4?rlkey=j2m2ekaex7clh4qv2zbwocgag&dl=0

For crashes I agree with what John wrote. Please see what if anything is under Windows Reliability History (assuming there was no crash report from VEGAS itself under "show problem details.").

chell wrote on 9/12/2025, 10:26 PM

Hello.

I have not posted for some time in this forum, despite being a Vegas Pro user and a Movie Studio user before that. I have been using Vegas Pro since version 17 and am currently using version 22.

I have suffered shutdowns in every version up to now! I have had to set the autosave function, but even then recovering the file using this option does not always return me to where I was before. I edit directly on the time line, producing videos for YouTube in the Flight Simulation genre. I have watched many videos on how I might mitigate these shutdowns, but mostly they do not work for me. The best option I have now is to disable GPU Acceleration in the OPTIONS/PREFERENCES/VIDEO section. Mostly, this allows me a long time before I get a shutdown. The downside of this option is that rendering often stops mid-render, so I turn the option back to ON to render and mostly it works. But I still suffer shutdowns and the occasional failure to complete a render.

My system is powerful - AMD Ryzen 9 9850X3D CPU, NVidia Geforce RTX 5070Ti 16GB video card, 64GB RAM and a 4TB Samsung Evo SSD. Could the problem be the preview screen? I keep it at GOOD/AUTO so I get to see something of what the output would be like upon rendering. During rendering, I often notice the preview screen struggling to show a transition for example and often I have to remove a transition and do something else to get the render to get past this point where it failed.

***************************

Now I am getting adverts to upgrade to Vegas Pro 23. I am very reluctant to do this, while I suffer these shutdowns. But if upgrading fixes this, then I am prepared to do it.

I'm sorry if this has been posted elsewhere. Like I said, I have not visited this forum for some time and I have reached a point where the frustration is really getting to me, so I would really appreciate some help and useful comments on this matter. I really like Vegas Pro - you do not charge a stupid monthly subscription and the software is easy to use, compared to some of the more expensive and often complicated options out there. I hope someone can help.

Thanks for listening,

regards,

Lee James

West Sussex UK

virtualairlinepilot.org

My specs are similar to yours (look at my signature) - I've had similar issues, and it ended up being related dGPU memory not being released. My fix for 22 was to set my dynamic ram preview to 0% - but on 23 there's an internal setting to "Release inactive image buffer GPU memory" and that completely fixed it for me. I don't think 22 has the same internal setting. I can't be certain you're having the same issue but this did cause numerous crashes for me. It could also just be your footage being either VBR or too compressed but I hope this helps!

Lee-James wrote on 9/13/2025, 6:05 AM

The other thing we can do is to look at the file Vegas produces when it's evaluating your GPU, it will tell you if Vegas can use it. In V22 it can be found here:

C:\Users\username\AppData\Local\VEGAS Pro\22.0\gpu_video_x64.log (if your version is V22.0, if not it will be V??.0)

As V23 is so new I will have to see if it has the same file in the same location. Anyway look for the V22 one. It can be opened in notepad.

Update: yes there is a file for V23, please post the contents on here as you did with mediainfo data.

Andy,

Ok, I found the log file and here is the output :-

*****************************************************

INFO 2025-09-12 22:33:02 *** Start of GPU-accelerated video processing log ***
INFO 2025-09-12 22:33:02 VEGAS Pro 22.0
INFO 2025-09-12 22:33:02 Version 22.0 (Build 250)
INFO 2025-09-12 22:33:02
INFO 2025-09-12 22:33:02 [system device log] **************************************************************************************
INFO 2025-09-12 22:33:02 [system device log]
INFO 2025-09-12 22:33:02 [system device log] -- NVIDIA GeForce RTX 5070 Ti --
INFO 2025-09-12 22:33:02 [system device log] MX ID: 0x10d91
INFO 2025-09-12 22:33:02 [system device log] DXGI description: NVIDIA GeForce RTX 5070 Ti
INFO 2025-09-12 22:33:02 [system device log] LUID: 0x0:0x10d91
INFO 2025-09-12 22:33:02 [system device log] Vendor: 0x10de
INFO 2025-09-12 22:33:02 [system device log] ID/SubSys/Rev: 0x2c05, 0xf3221569, 0xa1
INFO 2025-09-12 22:33:02 [system device log] Memory: 15.534 / 0 / 30.829 GB (video/system/shared)
INFO 2025-09-12 22:33:02 [system device log] Flags: 0
INFO 2025-09-12 22:33:02 [system device log]
INFO 2025-09-12 22:33:02 [system device log]
INFO 2025-09-12 22:33:02 [system device log] -- AMD Radeon(TM) Graphics --
INFO 2025-09-12 22:33:02 [system device log] MX ID: 0x121f0
INFO 2025-09-12 22:33:02 [system device log] DXGI description: AMD Radeon(TM) Graphics
INFO 2025-09-12 22:33:02 [system device log] LUID: 0x0:0x121f0
INFO 2025-09-12 22:33:02 [system device log] Vendor: 0x1002
INFO 2025-09-12 22:33:02 [system device log] ID/SubSys/Rev: 0x13c0, 0x88771043, 0xc9
INFO 2025-09-12 22:33:02 [system device log] Memory: 1.9646 / 0 / 30.829 GB (video/system/shared)
INFO 2025-09-12 22:33:02 [system device log] Flags: 0
INFO 2025-09-12 22:33:02 [system device log]
INFO 2025-09-12 22:33:02 [system device log]
INFO 2025-09-12 22:33:02 [system device log] -- Microsoft WARP device --
INFO 2025-09-12 22:33:02 [system device log] MX ID: 0x121b5
INFO 2025-09-12 22:33:02 [system device log] DXGI description: Microsoft Basic Render Driver
INFO 2025-09-12 22:33:02 [system device log] LUID: 0x0:0x121b5
INFO 2025-09-12 22:33:02 [system device log] Vendor: 0x1414
INFO 2025-09-12 22:33:02 [system device log] ID/SubSys/Rev: 0x8c, 0x0, 0x0
INFO 2025-09-12 22:33:02 [system device log] Memory: 0 / 0 / 30.829 GB (video/system/shared)
INFO 2025-09-12 22:33:02 [system device log] Flags: 2
INFO 2025-09-12 22:33:02 [system device log]
INFO 2025-09-12 22:33:02 [system device log] **************************************************************************************
INFO 2025-09-12 22:33:02 OpenCL_Initialize
INFO 2025-09-12 22:33:02 Platforms: 2
INFO 2025-09-12 22:33:02 Platform: 0
INFO 2025-09-12 22:33:02 Vendor: NVIDIA Corporation
INFO 2025-09-12 22:33:02 Name: NVIDIA CUDA
INFO 2025-09-12 22:33:02 Version: OpenCL 3.0 CUDA 13.0.48
INFO 2025-09-12 22:33:02 Profile: FULL_PROFILE
INFO 2025-09-12 22:33:02 Extensions: cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_fp64 cl_khr_3d_image_writes cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll cl_nv_d3d10_sharing cl_khr_d3d10_sharing cl_nv_d3d11_sharing cl_nv_copy_opts cl_nv_create_buffer cl_khr_int64_base_atomics cl_khr_int64_extended_atomics cl_khr_device_uuid cl_khr_pci_bus_info cl_khr_external_semaphore cl_khr_external_memory cl_khr_external_semaphore_win32 cl_khr_external_memory_win32 cl_khr_semaphore
INFO 2025-09-12 22:33:02
INFO 2025-09-12 22:33:02 [system device log] initializing MxGpuDevice...
INFO 2025-09-12 22:33:02 [system device log] found DX12 support - initializing MultiGPU
INFO 2025-09-12 22:33:02 [system device log] create DX12 device. feature level=49408, HRESULT=0
INFO 2025-09-12 22:33:02 [system device log] create DX11 device. HRESULT=0
INFO 2025-09-12 22:33:02 [system device log] setting private data - . HRESULT=0
INFO 2025-09-12 22:33:02 [system device log] CreateDevice: switching multithread protection ON

INFO 2025-09-12 22:33:02 [system device log] IDXGIAdapter4: isSoftware 0

INFO 2025-09-12 22:33:02 [system device log] IDXGIAdapter4: is ACG compatible 1

INFO 2025-09-12 22:33:02 [system device log] IDXGIAdapter4: has monitored fences 1

INFO 2025-09-12 22:33:02 [system device log] IDXGIAdapter4: has non monitored fences 0

INFO 2025-09-12 22:33:02 [system device log] IDXGIAdapter4: has keyed mutex conformance 1

INFO 2025-09-12 22:33:02 [system device log] .. end initializing MxGpuDevice
INFO 2025-09-12 22:33:02 [system device log] initializing MxGpuDevice...
INFO 2025-09-12 22:33:02 [system device log] found DX12 support - initializing MultiGPU
INFO 2025-09-12 22:33:02 [system device log] create DX12 device. feature level=49408, HRESULT=0
INFO 2025-09-12 22:33:02 [system device log] create DX11 device. HRESULT=0
INFO 2025-09-12 22:33:02 [system device log] setting private data - . HRESULT=0
INFO 2025-09-12 22:33:02 [system device log] CreateDevice: switching multithread protection ON

INFO 2025-09-12 22:33:02 [system device log] IDXGIAdapter4: isSoftware 0

INFO 2025-09-12 22:33:02 [system device log] IDXGIAdapter4: is ACG compatible 1

INFO 2025-09-12 22:33:02 [system device log] IDXGIAdapter4: has monitored fences 1

INFO 2025-09-12 22:33:02 [system device log] IDXGIAdapter4: has non monitored fences 0

INFO 2025-09-12 22:33:02 [system device log] IDXGIAdapter4: has keyed mutex conformance 1

INFO 2025-09-12 22:33:02 [system device log] .. end initializing MxGpuDevice
INFO 2025-09-12 22:33:02 [system device log] initializing MxGpuDevice...
INFO 2025-09-12 22:33:02 [system device log] found DX12 support - initializing MultiGPU
INFO 2025-09-12 22:33:02 [system device log] create DX12 device. feature level=49408, HRESULT=0
INFO 2025-09-12 22:33:02 [system device log] create DX11 device. HRESULT=0
INFO 2025-09-12 22:33:02 [system device log] setting private data - . HRESULT=0
INFO 2025-09-12 22:33:02 [system device log] CreateDevice: switching multithread protection ON

INFO 2025-09-12 22:33:02 [system device log] IDXGIAdapter4: isSoftware 1

INFO 2025-09-12 22:33:02 [system device log] IDXGIAdapter4: is ACG compatible 1

INFO 2025-09-12 22:33:02 [system device log] IDXGIAdapter4: has monitored fences 1

INFO 2025-09-12 22:33:02 [system device log] IDXGIAdapter4: has non monitored fences 0

INFO 2025-09-12 22:33:02 [system device log] IDXGIAdapter4: has keyed mutex conformance 1

INFO 2025-09-12 22:33:02 [system device log] .. end initializing MxGpuDevice
INFO 2025-09-12 22:33:02 Devices: 1
INFO 2025-09-12 22:33:02 Device: 0
INFO 2025-09-12 22:33:02 Type: GPU
INFO 2025-09-12 22:33:02 Vendor: NVIDIA Corporation
INFO 2025-09-12 22:33:02 Name: NVIDIA GeForce RTX 5070 Ti
INFO 2025-09-12 22:33:02 Profile: FULL_PROFILE
INFO 2025-09-12 22:33:02 Version: OpenCL 3.0 CUDA
INFO 2025-09-12 22:33:02 C version: OpenCL C 1.2
INFO 2025-09-12 22:33:02 Extensions: cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_fp64 cl_khr_3d_image_writes cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll cl_nv_d3d10_sharing cl_khr_d3d10_sharing cl_nv_d3d11_sharing cl_nv_copy_opts cl_nv_create_buffer cl_khr_int64_base_atomics cl_khr_int64_extended_atomics cl_khr_device_uuid cl_khr_pci_bus_info cl_khr_external_semaphore cl_khr_external_memory cl_khr_external_semaphore_win32 cl_khr_external_memory_win32 cl_khr_semaphore
INFO 2025-09-12 22:33:02 Driver version: 580.88
INFO 2025-09-12 22:33:02 Available: Yes
INFO 2025-09-12 22:33:02 Compiler: Yes
INFO 2025-09-12 22:33:02 Image support: Yes
INFO 2025-09-12 22:33:02 Unified memory: No
INFO 2025-09-12 22:33:02 Vendor ID: 4318
INFO 2025-09-12 22:33:02 Compute units: 70
INFO 2025-09-12 22:33:02 Work dimensions: 3
INFO 2025-09-12 22:33:02 Clock Frequency: 2452
INFO 2025-09-12 22:33:02 Image reads: 256
INFO 2025-09-12 22:33:02 Image writes: 32
INFO 2025-09-12 22:33:02 Samplers: 32
INFO 2025-09-12 22:33:02 Workgroup size: 1024
INFO 2025-09-12 22:33:02 Image width: 32768
INFO 2025-09-12 22:33:02 Image height: 32768
INFO 2025-09-12 22:33:02 Parameter size: 32764
INFO 2025-09-12 22:33:02 Maximum alloc: 4273618944
INFO 2025-09-12 22:33:02 Memory size: 17094475776
INFO 2025-09-12 22:33:02 Local memory: 49152
INFO 2025-09-12 22:33:02 Work item sizes: 1024, 1024, 64
INFO 2025-09-12 22:33:02 Out of order Q: Yes
INFO 2025-09-12 22:33:02 Profiling Q: Yes
INFO 2025-09-12 22:33:02 NV compute (maj):12
INFO 2025-09-12 22:33:02 NV compute (min):0
INFO 2025-09-12 22:33:02 NV warp size: 32
INFO 2025-09-12 22:33:02 NV overlap: Yes
INFO 2025-09-12 22:33:02 NV integ. mem: No
INFO 2025-09-12 22:33:02 Device is compatible.
INFO 2025-09-12 22:33:02 This is the selected device.
INFO 2025-09-12 22:33:02
INFO 2025-09-12 22:33:02 Platform: 1
INFO 2025-09-12 22:33:02 Vendor: Advanced Micro Devices, Inc.
INFO 2025-09-12 22:33:02 Name: AMD Accelerated Parallel Processing
INFO 2025-09-12 22:33:02 Version: OpenCL 2.1 AMD-APP (3640.0)
INFO 2025-09-12 22:33:02 Profile: FULL_PROFILE
INFO 2025-09-12 22:33:02 Extensions: cl_khr_icd cl_khr_d3d10_sharing cl_khr_d3d11_sharing cl_khr_dx9_media_sharing cl_amd_event_callback cl_amd_offline_devices
INFO 2025-09-12 22:33:02
INFO 2025-09-12 22:33:02 Devices: 1
INFO 2025-09-12 22:33:02 Device: 0
INFO 2025-09-12 22:33:02 Type: GPU
INFO 2025-09-12 22:33:02 Vendor: Advanced Micro Devices, Inc.
INFO 2025-09-12 22:33:02 Name: gfx1036
INFO 2025-09-12 22:33:02 Profile: FULL_PROFILE
INFO 2025-09-12 22:33:02 Version: OpenCL 2.0 AMD-APP (3640.0)
INFO 2025-09-12 22:33:02 C version: OpenCL C 2.0
INFO 2025-09-12 22:33:02 Extensions: cl_khr_fp64 cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_int64_base_atomics cl_khr_int64_extended_atomics cl_khr_3d_image_writes cl_khr_byte_addressable_store cl_khr_fp16 cl_khr_gl_sharing cl_amd_device_attribute_query cl_amd_media_ops cl_amd_media_ops2 cl_khr_d3d10_sharing cl_khr_d3d11_sharing cl_khr_dx9_media_sharing cl_khr_image2d_from_buffer cl_khr_subgroups cl_khr_gl_event cl_khr_depth_images cl_khr_mipmap_image cl_khr_mipmap_image_writes cl_amd_copy_buffer_p2p cl_amd_planar_yuv
INFO 2025-09-12 22:33:02 Driver version: 3640.0 (PAL,LC)
INFO 2025-09-12 22:33:02 Available: Yes
INFO 2025-09-12 22:33:02 Compiler: Yes
INFO 2025-09-12 22:33:02 Image support: Yes
INFO 2025-09-12 22:33:02 Unified memory: Yes
INFO 2025-09-12 22:33:02 Vendor ID: 4098
INFO 2025-09-12 22:33:02 Compute units: 1
INFO 2025-09-12 22:33:02 Work dimensions: 3
INFO 2025-09-12 22:33:02 Clock Frequency: 2200
INFO 2025-09-12 22:33:02 Image reads: 128
INFO 2025-09-12 22:33:02 Image writes: 64
INFO 2025-09-12 22:33:02 Samplers: 16
INFO 2025-09-12 22:33:02 Workgroup size: 256
INFO 2025-09-12 22:33:02 Image width: 16384
INFO 2025-09-12 22:33:02 Image height: 16384
INFO 2025-09-12 22:33:02 Parameter size: 1024
INFO 2025-09-12 22:33:02 Maximum alloc: 21102548582
INFO 2025-09-12 22:33:02 Memory size: 26974011392
INFO 2025-09-12 22:33:02 Local memory: 65536
INFO 2025-09-12 22:33:02 Work item sizes: 1024, 1024, 1024
INFO 2025-09-12 22:33:02 Out of order Q: No
INFO 2025-09-12 22:33:02 Profiling Q: Yes
INFO 2025-09-12 22:33:02 Device is compatible.
INFO 2025-09-12 22:33:02
INFO 2025-09-12 22:33:02 Low-performance system configuration, differing OpenCL and OpenGL providers.
INFO 2025-09-12 22:33:02 Attempting to create CL<->DX11 interop context on device 'NVIDIA GeForce RTX 5070 Ti'
INFO 2025-09-12 22:33:02 CL<->DX11 context: 0000000016005DA0
INFO 2025-09-12 22:33:02 Command queue: 0000000015FA0E00
INFO 2025-09-12 22:33:02 Buffer write mapping flags: 0x4
INFO 2025-09-12 22:33:02 2DWGO: 16x16
INFO 2025-09-12 22:33:02 HWBL: 1
INFO 2025-09-12 22:33:02 OCL compile, bin: 91426185, kernels: kddb9a9580 kddb9a9581 kddb9a9582
INFO 2025-09-12 22:33:02 CPWB successful
INFO 2025-09-12 22:33:02 BP successful
INFO 2025-09-12 22:33:02 OCL compile, bin: 8a7f119a, kernels: k4fce1a180 k4fce1a181 k4fce1a182 k4fce1a183 k4fce1a184
INFO 2025-09-12 22:33:02 CPWB successful
INFO 2025-09-12 22:33:02 BP successful
INFO 2025-09-12 22:33:02 OCL compile, bin: 6311d26d, kernels: k13650b260 k13650b261 k13650b262 k13650b263
INFO 2025-09-12 22:33:02 CPWB successful
INFO 2025-09-12 22:33:02 BP successful
INFO 2025-09-12 22:33:02 OCL compile, bin: b5443ede, kernels: kf2c0fea20 kf2c0fea21 kf2c0fea22 kf2c0fea23 kf2c0fea24 kf2c0fea25 kf2c0fea26 kf2c0fea27 kf2c0fea28 kf2c0fea29 kf2c0fea210 kf2c0fea211 kf2c0fea212 kf2c0fea213 kf2c0fea214 kf2c0fea215 kf2c0fea216
INFO 2025-09-12 22:33:02 CPWB successful
INFO 2025-09-12 22:33:02 BP successful
INFO 2025-09-12 22:33:02 OCL compile, bin: f9312813, kernels: k201db7240 k201db7241 k201db7242 k201db7243 k201db7244 k201db7245 k201db7246 k201db7247 k201db7248 k201db7249 k201db72410 k201db72411 k201db72412 k201db72413 k201db72414 k201db72415 k201db72416 k201db72417 k201db72418 k201db72419 k201db72420 k201db72421 k201db72422 k201db72423 k201db72424 k201db72425 k201db72426 k201db72427 k201db72428 k201db72429 k201db72430 k201db72431 k201db72432 k201db72433 k201db72434 k201db72435 k201db72436 k201db72437 k201db72438 k201db72439 k201db72440 k201db72441 k201db72442 k201db72443 k201db72444 k201db72445 k201db72446 k201db72447 k201db72448 k201db72449 k201db72450 k201db72451 k201db72452 k201db72453 k201db72454
INFO 2025-09-12 22:33:02 CPWB successful
INFO 2025-09-12 22:33:02 BP successful
INFO 2025-09-12 22:33:06 Readback profiling: [16, 15], selected 0
INFO 2025-09-12 22:33:06 DX12_HDR_Initialize
INFO 2025-09-12 22:33:06 DX12 HDR Available: FALSE
INFO 2025-09-12 22:33:06
INFO 2025-09-12 22:33:22 OCL compile, bin: 94b9988a, kernels: k2b39dd750 k2b39dd751 k2b39dd752 k2b39dd753 k2b39dd754 k2b39dd755 k2b39dd756 k2b39dd757 k2b39dd758 k2b39dd759 k2b39dd7510 k2b39dd7511 k2b39dd7512 k2b39dd7513 k2b39dd7514
INFO 2025-09-12 22:33:22 CPWB successful
INFO 2025-09-12 22:33:22 BP successful
INFO 2025-09-12 22:33:22 OCL compile, bin: 6cfdbc5a, kernels: k1f6702930
INFO 2025-09-12 22:33:22 CPWB successful
INFO 2025-09-12 22:33:22 BP successful
INFO 2025-09-12 22:33:22 OCL compile, bin: e66263e1, kernels: kea0252530 kea0252531
INFO 2025-09-12 22:33:22 CPWB successful
INFO 2025-09-12 22:33:22 BP successful
INFO 2025-09-12 22:33:22 OCL compile, bin: 62c3355e, kernels: k4b14e2180
INFO 2025-09-12 22:33:22 CPWB successful
INFO 2025-09-12 22:33:22 BP successful
INFO 2025-09-12 22:33:22 OCL compile, bin: e364c41d, kernels: k210018fc0
INFO 2025-09-12 22:33:22 CPWB successful
INFO 2025-09-12 22:33:22 BP successful
INFO 2025-09-12 22:33:22 OCL compile, bin: 4947ea4b, kernels: k7b598a4d0
INFO 2025-09-12 22:33:22 CPWS successful
INFO 2025-09-12 22:33:22 BP successful
INFO 2025-09-12 22:47:10 OpenCL_Shutdown
INFO 2025-09-12 22:47:10
INFO 2025-09-12 22:47:10 *** End of GPU-accelerated video processing log ***

*********************************************

Regarding your suggestion, I think perhaps I'll set up a project and just film what I do - and when V22 crashes you'll see what happens.

Interestingly enough, late last night I finished a review video with only one crash during the editing session ! Go figure, as our American friends would say 😏

Chell,

Thank you for chiming in! I'll try your settings in V23 and see what happens.

With the next crash, I'll try and get the Windows log file.

Lee

Lee-James wrote on 9/13/2025, 10:17 AM

Ok,

Sorry to be late - I was pretty tired last night but managed to complete a video project in V22 and upload it to YouTube before I went to bed.

So today, I had another go at using V23 - but using Chell's suggestion, I set the Dynamic Ram Preview to ZERO; Then I entered the INTERNAL part of Options/Preferences and changed the RELEASE INACTIVE IMAGE BUFFER GPU MEMORY - to TRUE (there were two entries for this, both the same named FALSE, so I set them both to TRUE).

I then set about re-doing yesterday's Review Video that I did in V22 and that I had uploaded last night - but this time using V23. Upon opening V23, this time, it seemed very stable and I did the first 13 minutes of the video (editing took about 35 minutes but with no shutdowns and I rendered it right after the edit was done - normally I have to shutdown Vegas pro and restart it). And this was the output option suggested by Vegas Pro 23 for use on my YouTube channel:-

_________________________________________________________________________________________

Internet HD 1080p 29.97 fps; MP4 (AVC/AAC)
Video - 29.97 fps; 1920x1080; 16:9; Progressive; 1.000; 32 bit; Unspecified; 12.0 Mb/s;
Audio - 48,000 Hz; 16 bit; Stereo; audio/aac; 192.0 kb/s

_________________________________________________________________________________________

The render went through fine, very quick and with no issues looking at the Preview window inside the programme. So next, I decided to continue the exercise and complete the whole project. During what was a 2.5 hour editing session, I had three shutdowns, but the first one only happened after about and hour and 50 minutes or so. This was a big improvement for me. After the last shutdown and restart, loading from the saved point, I completed the edit and then again, decided to render right away. Normally I shut down Vegas pro and restart it before attempting this. After 18 minutes and 37 seconds, V23 had easily rendered the 46 minute MP4 video with no issues and no problems with transitions or crossovers slowing down in the Preview window.

_________________________________________________________________________________________

So now the Windows Reliability Monitor - This was the output from that utility :-

Problem
Stopped Responding - 13/09/2025 - 15:07

Description -
The program vegas230.exe version 23.0.278 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
__________________________________________________________________________________________

For some reason, I don't seem to get any more detail (as in John Dennis's example video in the link above).

Lastly, here is the output from the GPU-accelerated video processing log, this time in Vegas pro 23:-

INFO 2025-09-13 15:07:46 *** Start of GPU-accelerated video processing log ***
INFO 2025-09-13 15:07:46 VEGAS Pro 23.0
INFO 2025-09-13 15:07:46 Version 23.0 (Build 278)
INFO 2025-09-13 15:07:46
INFO 2025-09-13 15:07:46 [system device log] **************************************************************************************
INFO 2025-09-13 15:07:46 [system device log]
INFO 2025-09-13 15:07:46 [system device log] -- NVIDIA GeForce RTX 5070 Ti --
INFO 2025-09-13 15:07:46 [system device log] MX ID: 0x10d91
INFO 2025-09-13 15:07:46 [system device log] DXGI description: NVIDIA GeForce RTX 5070 Ti
INFO 2025-09-13 15:07:46 [system device log] LUID: 0x0:0x10d91
INFO 2025-09-13 15:07:46 [system device log] Vendor: 0x10de
INFO 2025-09-13 15:07:46 [system device log] ID/SubSys/Rev: 0x2c05, 0xf3221569, 0xa1
INFO 2025-09-13 15:07:46 [system device log] Memory: 15.534 / 0 / 30.829 GB (video/system/shared)
INFO 2025-09-13 15:07:46 [system device log] Flags: 0
INFO 2025-09-13 15:07:46 [system device log]
INFO 2025-09-13 15:07:46 [system device log]
INFO 2025-09-13 15:07:46 [system device log] -- AMD Radeon(TM) Graphics --
INFO 2025-09-13 15:07:46 [system device log] MX ID: 0x121f0
INFO 2025-09-13 15:07:46 [system device log] DXGI description: AMD Radeon(TM) Graphics
INFO 2025-09-13 15:07:46 [system device log] LUID: 0x0:0x121f0
INFO 2025-09-13 15:07:46 [system device log] Vendor: 0x1002
INFO 2025-09-13 15:07:46 [system device log] ID/SubSys/Rev: 0x13c0, 0x88771043, 0xc9
INFO 2025-09-13 15:07:46 [system device log] Memory: 1.9646 / 0 / 30.829 GB (video/system/shared)
INFO 2025-09-13 15:07:46 [system device log] Flags: 0
INFO 2025-09-13 15:07:46 [system device log]
INFO 2025-09-13 15:07:46 [system device log]
INFO 2025-09-13 15:07:46 [system device log] -- Microsoft WARP device --
INFO 2025-09-13 15:07:46 [system device log] MX ID: 0x121b5
INFO 2025-09-13 15:07:46 [system device log] DXGI description: Microsoft Basic Render Driver
INFO 2025-09-13 15:07:46 [system device log] LUID: 0x0:0x121b5
INFO 2025-09-13 15:07:46 [system device log] Vendor: 0x1414
INFO 2025-09-13 15:07:46 [system device log] ID/SubSys/Rev: 0x8c, 0x0, 0x0
INFO 2025-09-13 15:07:46 [system device log] Memory: 0 / 0 / 30.829 GB (video/system/shared)
INFO 2025-09-13 15:07:46 [system device log] Flags: 2
INFO 2025-09-13 15:07:46 [system device log]
INFO 2025-09-13 15:07:46 [system device log] **************************************************************************************
INFO 2025-09-13 15:07:46 OpenGL_Initialize
INFO 2025-09-13 15:07:46 GLEW Init OK
INFO 2025-09-13 15:07:46 WGLEW Init OK
INFO 2025-09-13 15:07:46 GLC: 0000000000010000
INFO 2025-09-13 15:07:46 GL 10-bit Available: FALSE
INFO 2025-09-13 15:07:46 GL 10-bit Pixel Format Index: 0
INFO 2025-09-13 15:07:46 GL_VENDOR: NVIDIA Corporation
INFO 2025-09-13 15:07:46 GL_RENDERER: NVIDIA GeForce RTX 5070 Ti/PCIe/SSE2
INFO 2025-09-13 15:07:46 GL_VERSION: 4.6.0 NVIDIA 580.88
INFO 2025-09-13 15:07:46 Dib_OpenGL Init OK
INFO 2025-09-13 15:07:46
INFO 2025-09-13 15:07:46 OpenCL_Initialize
INFO 2025-09-13 15:07:46 Platforms: 2
INFO 2025-09-13 15:07:46 Platform: 0
INFO 2025-09-13 15:07:46 Vendor: NVIDIA Corporation
INFO 2025-09-13 15:07:46 Name: NVIDIA CUDA
INFO 2025-09-13 15:07:46 Version: OpenCL 3.0 CUDA 13.0.48
INFO 2025-09-13 15:07:46 Profile: FULL_PROFILE
INFO 2025-09-13 15:07:46 Extensions: cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_fp64 cl_khr_3d_image_writes cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll cl_nv_d3d10_sharing cl_khr_d3d10_sharing cl_nv_d3d11_sharing cl_nv_copy_opts cl_nv_create_buffer cl_khr_int64_base_atomics cl_khr_int64_extended_atomics cl_khr_device_uuid cl_khr_pci_bus_info cl_khr_external_semaphore cl_khr_external_memory cl_khr_external_semaphore_win32 cl_khr_external_memory_win32 cl_khr_semaphore
INFO 2025-09-13 15:07:46
INFO 2025-09-13 15:07:46 [system device log] initializing MxGpuDevice...
INFO 2025-09-13 15:07:46 [system device log] found DX12 support - initializing MultiGPU
INFO 2025-09-13 15:07:46 [system device log] create DX12 device. feature level=49408, HRESULT=0
INFO 2025-09-13 15:07:46 [system device log] create DX11 device. HRESULT=0
INFO 2025-09-13 15:07:46 [system device log] setting private data - . HRESULT=0
INFO 2025-09-13 15:07:46 [system device log] CreateDevice: switching multithread protection ON

INFO 2025-09-13 15:07:46 [system device log] IDXGIAdapter4: isSoftware 0

INFO 2025-09-13 15:07:46 [system device log] IDXGIAdapter4: is ACG compatible 1

INFO 2025-09-13 15:07:46 [system device log] IDXGIAdapter4: has monitored fences 1

INFO 2025-09-13 15:07:46 [system device log] IDXGIAdapter4: has non monitored fences 0

INFO 2025-09-13 15:07:46 [system device log] IDXGIAdapter4: has keyed mutex conformance 1

INFO 2025-09-13 15:07:46 [system device log] .. end initializing MxGpuDevice
INFO 2025-09-13 15:07:46 [system device log] initializing MxGpuDevice...
INFO 2025-09-13 15:07:46 [system device log] found DX12 support - initializing MultiGPU
INFO 2025-09-13 15:07:47 [system device log] create DX12 device. feature level=49408, HRESULT=0
INFO 2025-09-13 15:07:47 [system device log] create DX11 device. HRESULT=0
INFO 2025-09-13 15:07:47 [system device log] setting private data - . HRESULT=0
INFO 2025-09-13 15:07:47 [system device log] CreateDevice: switching multithread protection ON

INFO 2025-09-13 15:07:47 [system device log] IDXGIAdapter4: isSoftware 0

INFO 2025-09-13 15:07:47 [system device log] IDXGIAdapter4: is ACG compatible 1

INFO 2025-09-13 15:07:47 [system device log] IDXGIAdapter4: has monitored fences 1

INFO 2025-09-13 15:07:47 [system device log] IDXGIAdapter4: has non monitored fences 0

INFO 2025-09-13 15:07:47 [system device log] IDXGIAdapter4: has keyed mutex conformance 1

INFO 2025-09-13 15:07:47 [system device log] .. end initializing MxGpuDevice
INFO 2025-09-13 15:07:47 [system device log] initializing MxGpuDevice...
INFO 2025-09-13 15:07:47 [system device log] found DX12 support - initializing MultiGPU
INFO 2025-09-13 15:07:47 [system device log] create DX12 device. feature level=49408, HRESULT=0
INFO 2025-09-13 15:07:47 [system device log] create DX11 device. HRESULT=0
INFO 2025-09-13 15:07:47 [system device log] setting private data - . HRESULT=0
INFO 2025-09-13 15:07:47 [system device log] CreateDevice: switching multithread protection ON

INFO 2025-09-13 15:07:47 [system device log] IDXGIAdapter4: isSoftware 1

INFO 2025-09-13 15:07:47 [system device log] IDXGIAdapter4: is ACG compatible 1

INFO 2025-09-13 15:07:47 [system device log] IDXGIAdapter4: has monitored fences 1

INFO 2025-09-13 15:07:47 [system device log] IDXGIAdapter4: has non monitored fences 0

INFO 2025-09-13 15:07:47 [system device log] IDXGIAdapter4: has keyed mutex conformance 1

INFO 2025-09-13 15:07:47 [system device log] .. end initializing MxGpuDevice
INFO 2025-09-13 15:07:47 Devices: 1
INFO 2025-09-13 15:07:47 Device: 0
INFO 2025-09-13 15:07:47 Type: GPU
INFO 2025-09-13 15:07:47 Vendor: NVIDIA Corporation
INFO 2025-09-13 15:07:47 Name: NVIDIA GeForce RTX 5070 Ti
INFO 2025-09-13 15:07:47 Profile: FULL_PROFILE
INFO 2025-09-13 15:07:47 Version: OpenCL 3.0 CUDA
INFO 2025-09-13 15:07:47 C version: OpenCL C 1.2
INFO 2025-09-13 15:07:47 Extensions: cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_fp64 cl_khr_3d_image_writes cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll cl_nv_d3d10_sharing cl_khr_d3d10_sharing cl_nv_d3d11_sharing cl_nv_copy_opts cl_nv_create_buffer cl_khr_int64_base_atomics cl_khr_int64_extended_atomics cl_khr_device_uuid cl_khr_pci_bus_info cl_khr_external_semaphore cl_khr_external_memory cl_khr_external_semaphore_win32 cl_khr_external_memory_win32 cl_khr_semaphore
INFO 2025-09-13 15:07:47 Driver version: 580.88
INFO 2025-09-13 15:07:47 Available: Yes
INFO 2025-09-13 15:07:47 Compiler: Yes
INFO 2025-09-13 15:07:47 Image support: Yes
INFO 2025-09-13 15:07:47 Unified memory: No
INFO 2025-09-13 15:07:47 Vendor ID: 4318
INFO 2025-09-13 15:07:47 Compute units: 70
INFO 2025-09-13 15:07:47 Work dimensions: 3
INFO 2025-09-13 15:07:47 Clock Frequency: 2452
INFO 2025-09-13 15:07:47 Image reads: 256
INFO 2025-09-13 15:07:47 Image writes: 32
INFO 2025-09-13 15:07:47 Samplers: 32
INFO 2025-09-13 15:07:47 Workgroup size: 1024
INFO 2025-09-13 15:07:47 Image width: 32768
INFO 2025-09-13 15:07:47 Image height: 32768
INFO 2025-09-13 15:07:47 Parameter size: 32764
INFO 2025-09-13 15:07:47 Maximum alloc: 4273618944
INFO 2025-09-13 15:07:47 Memory size: 17094475776
INFO 2025-09-13 15:07:47 Local memory: 49152
INFO 2025-09-13 15:07:47 Work item sizes: 1024, 1024, 64
INFO 2025-09-13 15:07:47 Out of order Q: Yes
INFO 2025-09-13 15:07:47 Profiling Q: Yes
INFO 2025-09-13 15:07:47 NV compute (maj):12
INFO 2025-09-13 15:07:47 NV compute (min):0
INFO 2025-09-13 15:07:47 NV warp size: 32
INFO 2025-09-13 15:07:47 NV overlap: Yes
INFO 2025-09-13 15:07:47 NV integ. mem: No
INFO 2025-09-13 15:07:47 Device is compatible.
INFO 2025-09-13 15:07:47 This is the selected device.
INFO 2025-09-13 15:07:47
INFO 2025-09-13 15:07:47 Platform: 1
INFO 2025-09-13 15:07:47 Vendor: Advanced Micro Devices, Inc.
INFO 2025-09-13 15:07:47 Name: AMD Accelerated Parallel Processing
INFO 2025-09-13 15:07:47 Version: OpenCL 2.1 AMD-APP (3640.0)
INFO 2025-09-13 15:07:47 Profile: FULL_PROFILE
INFO 2025-09-13 15:07:47 Extensions: cl_khr_icd cl_khr_d3d10_sharing cl_khr_d3d11_sharing cl_khr_dx9_media_sharing cl_amd_event_callback cl_amd_offline_devices
INFO 2025-09-13 15:07:47
INFO 2025-09-13 15:07:47 Devices: 1
INFO 2025-09-13 15:07:47 Device: 0
INFO 2025-09-13 15:07:47 Type: GPU
INFO 2025-09-13 15:07:47 Vendor: Advanced Micro Devices, Inc.
INFO 2025-09-13 15:07:47 Name: gfx1036
INFO 2025-09-13 15:07:47 Profile: FULL_PROFILE
INFO 2025-09-13 15:07:47 Version: OpenCL 2.0 AMD-APP (3640.0)
INFO 2025-09-13 15:07:47 C version: OpenCL C 2.0
INFO 2025-09-13 15:07:47 Extensions: cl_khr_fp64 cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_int64_base_atomics cl_khr_int64_extended_atomics cl_khr_3d_image_writes cl_khr_byte_addressable_store cl_khr_fp16 cl_khr_gl_sharing cl_amd_device_attribute_query cl_amd_media_ops cl_amd_media_ops2 cl_khr_d3d10_sharing cl_khr_d3d11_sharing cl_khr_dx9_media_sharing cl_khr_image2d_from_buffer cl_khr_subgroups cl_khr_gl_event cl_khr_depth_images cl_khr_mipmap_image cl_khr_mipmap_image_writes cl_amd_copy_buffer_p2p cl_amd_planar_yuv
INFO 2025-09-13 15:07:47 Driver version: 3640.0 (PAL,LC)
INFO 2025-09-13 15:07:47 Available: Yes
INFO 2025-09-13 15:07:47 Compiler: Yes
INFO 2025-09-13 15:07:47 Image support: Yes
INFO 2025-09-13 15:07:47 Unified memory: Yes
INFO 2025-09-13 15:07:47 Vendor ID: 4098
INFO 2025-09-13 15:07:47 Compute units: 1
INFO 2025-09-13 15:07:47 Work dimensions: 3
INFO 2025-09-13 15:07:47 Clock Frequency: 2200
INFO 2025-09-13 15:07:47 Image reads: 128
INFO 2025-09-13 15:07:47 Image writes: 64
INFO 2025-09-13 15:07:47 Samplers: 16
INFO 2025-09-13 15:07:47 Workgroup size: 256
INFO 2025-09-13 15:07:47 Image width: 16384
INFO 2025-09-13 15:07:47 Image height: 16384
INFO 2025-09-13 15:07:47 Parameter size: 1024
INFO 2025-09-13 15:07:47 Maximum alloc: 21102548582
INFO 2025-09-13 15:07:47 Memory size: 26974011392
INFO 2025-09-13 15:07:47 Local memory: 65536
INFO 2025-09-13 15:07:47 Work item sizes: 1024, 1024, 1024
INFO 2025-09-13 15:07:47 Out of order Q: No
INFO 2025-09-13 15:07:47 Profiling Q: Yes
INFO 2025-09-13 15:07:47 Device is compatible.
INFO 2025-09-13 15:07:47
INFO 2025-09-13 15:07:47 Attempting to create CL<->DX11 interop context on device 'NVIDIA GeForce RTX 5070 Ti'
INFO 2025-09-13 15:07:47 CL<->DX11 context: 000000001EA2FDC0
INFO 2025-09-13 15:07:47 Command queue: 000000003EB73CF0
INFO 2025-09-13 15:07:47 Buffer write mapping flags: 0x4
INFO 2025-09-13 15:07:47 2DWGO: 16x16
INFO 2025-09-13 15:07:47 HWBL: 1
INFO 2025-09-13 15:07:47 OCL compile, bin: 91426185, kernels: kddb9a9580 kddb9a9581 kddb9a9582
INFO 2025-09-13 15:07:47 CPWB successful
INFO 2025-09-13 15:07:47 BP successful
INFO 2025-09-13 15:07:47 OCL compile, bin: 8a7f119a, kernels: k4fce1a180 k4fce1a181 k4fce1a182 k4fce1a183 k4fce1a184
INFO 2025-09-13 15:07:47 CPWB successful
INFO 2025-09-13 15:07:47 BP successful
INFO 2025-09-13 15:07:47 OCL compile, bin: 6311d26d, kernels: k13650b260 k13650b261 k13650b262 k13650b263
INFO 2025-09-13 15:07:47 CPWB successful
INFO 2025-09-13 15:07:47 BP successful
INFO 2025-09-13 15:07:47 OCL compile, bin: b5443ede, kernels: kf2c0fea20 kf2c0fea21 kf2c0fea22 kf2c0fea23 kf2c0fea24 kf2c0fea25 kf2c0fea26 kf2c0fea27 kf2c0fea28 kf2c0fea29 kf2c0fea210 kf2c0fea211 kf2c0fea212 kf2c0fea213 kf2c0fea214 kf2c0fea215 kf2c0fea216
INFO 2025-09-13 15:07:47 CPWB successful
INFO 2025-09-13 15:07:47 BP successful
INFO 2025-09-13 15:07:47 OCL compile, bin: 21e52674, kernels: k201db7240 k201db7241 k201db7242 k201db7243 k201db7244 k201db7245 k201db7246 k201db7247 k201db7248 k201db7249 k201db72410 k201db72411 k201db72412 k201db72413 k201db72414 k201db72415 k201db72416 k201db72417 k201db72418 k201db72419 k201db72420 k201db72421 k201db72422 k201db72423 k201db72424 k201db72425 k201db72426 k201db72427 k201db72428 k201db72429 k201db72430 k201db72431 k201db72432 k201db72433 k201db72434 k201db72435 k201db72436 k201db72437 k201db72438 k201db72439 k201db72440 k201db72441 k201db72442 k201db72443 k201db72444 k201db72445 k201db72446 k201db72447 k201db72448 k201db72449 k201db72450 k201db72451 k201db72452
INFO 2025-09-13 15:07:47 CPWB successful
INFO 2025-09-13 15:07:47 BP successful
INFO 2025-09-13 15:07:49 DX12_HDR_Initialize
INFO 2025-09-13 15:07:49 DX12 HDR Available: FALSE
INFO 2025-09-13 15:07:49
INFO 2025-09-13 15:07:52 OCL compile, bin: 4ce99973, kernels: k2c14d5f30
INFO 2025-09-13 15:07:52 CPWB successful
INFO 2025-09-13 15:07:52 BP successful
INFO 2025-09-13 15:07:54 OCL compile, bin: 94b9988a, kernels: k2b39dd750 k2b39dd751 k2b39dd752 k2b39dd753 k2b39dd754 k2b39dd755 k2b39dd756 k2b39dd757 k2b39dd758 k2b39dd759 k2b39dd7510 k2b39dd7511 k2b39dd7512 k2b39dd7513 k2b39dd7514
INFO 2025-09-13 15:07:54 CPWB successful
INFO 2025-09-13 15:07:54 BP successful
INFO 2025-09-13 15:07:55 OCL compile, bin: 6cfdbc5a, kernels: k1f6702930
INFO 2025-09-13 15:07:55 CPWB successful
INFO 2025-09-13 15:07:55 BP successful
INFO 2025-09-13 15:07:55 OCL compile, bin: e66263e1, kernels: kea0252530 kea0252531
INFO 2025-09-13 15:07:55 CPWB successful
INFO 2025-09-13 15:07:55 BP successful
INFO 2025-09-13 15:07:55 OCL compile, bin: 62c3355e, kernels: k4b14e2180
INFO 2025-09-13 15:07:55 CPWB successful
INFO 2025-09-13 15:07:55 BP successful
INFO 2025-09-13 15:07:55 OCL compile, bin: e364c41d, kernels: k210018fc0
INFO 2025-09-13 15:07:55 CPWB successful
INFO 2025-09-13 15:07:55 BP successful
INFO 2025-09-13 15:41:47 OpenCL_Shutdown
INFO 2025-09-13 15:41:48 OpenGL_Shutdown
INFO 2025-09-13 15:41:48
INFO 2025-09-13 15:41:48 *** End of GPU-accelerated video processing log ***

I hope this helps and I really appreciate all the help here. I have 28 days left on the V23 Trial, but I may just go ahead and buy it after this much better performance.

Regards,

Lee

andyrpsmith wrote on 9/13/2025, 10:30 AM

Good news Lee. Looking at the GPU files they both show that Vegas found both your AMD (on your CPU and the RTX 5070ti CPU and both were compatible. Very interesting about the RELEASE INACTIVE IMAGE BUFFER GPU MEMORY - to TRUE setting as this probably needs a bit of discussion why it is set to FALSE by default and are there any negatives in setting it to TRUE. In general it is best to keep the Dynamic RAM preview set at the default. Many people are confused as to what it does. It sets some of your system RAM aside to allow you to render a small section on the timeline to this set aside ram which gives you a faster quick render of the selection. The disadvantage is that it takes ram away from your system ram. As Vegas allows you to set large amounts of system ram to this setting it can severely reduce your PC performance especially if you only have limited ram in the first place. Most people find the default setting gives best performance with zero and larger settings causing a drop in performance.

Lee-James wrote on 9/13/2025, 11:10 AM

Thanks for your thoughts Andy,

I am a total novice at this. Ok, I have been editing video for a few years now, but I do not profess to understand all the technical stuff. The Windows log files were new to me.

So I have reset the Dynamic Ram. I have 64GB of very fast ram (this is a new PC, specifically bought for Flight Simulator and for Video Editing - 4TB Samsung Evo 990 SSD on board too!) so I'm happy with it al.

It does however look like Vegas Pro 23 has gone from the offer price of £149, back up to £219 😒 Ah well . . .

Lee

andyrpsmith wrote on 9/13/2025, 11:20 AM

Never pay more than £149 for an upgrade, Vegas offers discounts regularly. I have got upgrades consistently for £99/$99 just wait and keep an eye open.

Lee-James wrote on 9/13/2025, 11:33 AM

Ok,

I got the upgrade price at £149 instead of £219 so I'm happy. I can use it without the nagging logo.

Lee