Constants shutdowns & render failures since the beginning

Lee-James wrote on 9/11/2025, 4:25 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

Back to post

Comments

bitman wrote on 9/13/2025, 12:10 PM

@Lee-James First make sure your CPU is not thermal throttling, on beefy systems it can be triggered by inadequate cooling, high multicore usage (like rendering) or memory which is set to XMP in BIOS (which is basically an overclock). You mentioned that your system has fast memory, this fast memory is also pushing your CPU as the memory controller is usually on the CPU die in modern CPU's. Rendering or using your PC for gaming like a flight simulator, are 2 different things. Gaming much more depends on the GPU, and stresses the CPU less than video rendering like Vegas.
If Thermal throttling occurs, your performance goes down, and the chances of Vegas crashing due to the throttling increases, and I am speaking from my own experience. I am not saying this is your issue, but surely something to check: this is best done by running the free app HWiNFO64 which will readout all your sensors, and inform you about pretty much everything, including individual Core thermal throttling.
If you do throttle during heavy rendering, then you need to improve your cooling and/or put some limits to the CPU power draw in BIOS or lower your memory speed.

andyrpsmith wrote on 9/13/2025, 12:35 PM

Yes Bitman is right about thermal throttling. When I started using the trial of V23 to test the new AV1 codec which is my go to export, I found the template only allows CPU encoding despite the GPU having NVENC hardware encoding. My PC fans ran at 100% with the CPU (i9 13900K) using all 24 cores. Using HWinfo64 I could see max temps were 85-90C and that is with a 420mm water Cooler. I like to use Happy Otter Render + to render AV1 using the GPU, it runs 2-3x faster and much lower temps.

RogerS wrote on 9/13/2025, 8:41 PM

Modern CPUs may not throttle until 97C or even 100C+ so even temperatures of 90C on all cores don't necessarily represent a problem.

chell wrote on 9/14/2025, 3:24 AM

@Lee-James I'm really glad that my suggestion aided you in some way. On more complex timelines, when I have it set to FALSE my GPU usage spikes upward of 90% and other applications begin failing. The longer I played a video on the timeline, the more and more other things would fail. My audio drivers for example, would begin crashing - then my mouse would freeze up and windows as a whole would start dying because Vegas wasn't releasing any dGPU mem to be used by other services. As @andyrpsmith said, it does raise the question why on earth this isn't set to true by default. Surely it will cause more problems than not.

Lee, when you have some time could you perhaps run a little test? Put a random video on the timeline and press space, let it play for a minute or so and watch the performance tab in your task manager - then take a screenshot as the video plays. Then turn the settings back to FALSE and try the same thing, take a screenshot and then compare the usage percentages and watch the dGPU memory. At least then you could have some certainty that this is definitely part of the issue.

Here's mine on a 1 track timeline with a singular video, 1080p 60fps.

Idle:

True:

False:

I did all that and forgot to screen cap the most important bit to keep an eye on when you do this:

Lee-James wrote on 9/14/2025, 7:50 AM

Ok Chell,

I will try that at some point.

Bitman - So I will try and show the results from running HWinFo64 in an image . . .

I'm not certain how to interpret all this. Maybe you guys can tell me. What I do find is that the fan noise inside my case often seems to go mental! But I need to do another video project to look more closely at that. It's hard to tell if it's the CPU fan, the GPU or the case fans. I do have Artic paste on the CPU and I went for a full set of case fans, 3 on the top and 3 at the side.

Thanks guys,

Lee

chell wrote on 9/14/2025, 7:57 AM

@Lee-James You could check your CPU temps with HWmonitor or similar softwares - Good way to stress test and check for throttling. Do you have liquid cooling or just the paste and fans?

andyrpsmith wrote on 9/14/2025, 10:59 AM

Hi James, just click the sensors tab in HWinfo64 to get to the monitoring table and all will become clear.

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

@Lee-James You could check your CPU temps with HWmonitor or similar softwares - Good way to stress test and check for throttling. Do you have liquid cooling or just the paste and fans?

I have just the paste and fans. Andy, this is the warning I got from Hwinmonitor :-

As for the Sensor Status, there is a long line of data in the window. Anything else I need to look at ? I also need to edit another video using V23 and see what the effect is on the PC. Particularly how the FANS react . . .

Lee

andyrpsmith wrote on 9/14/2025, 2:52 PM

Just click do not monitor this sensor. The data will read down and show info from all your readable sensors in your PC. Go down to CPU temps and run your video render and it will monitor your current , min and max temps for all cores. Do not close the app while rendering or it will stop recording.