Crashes almost every time I render

Momo-Mojangles wrote on 5/22/2023, 3:46 PM

Unfortunately I missed the Vegas upgrade by perhaps a day or two and was stuck with version 18. I've had nothing but continuous problems after upgrading on a custom built PC with an MSI motherboard, 64GB of RAM, SSD drive and plenty of Intel CPU firepower (i7-11700k) on Windows 11. I recall the old days when odd/even upgrades were like versions of Star Trek, and I recall the odd providing better results (I've been around since Vegas 5.)

About 80% of the time when I render using the Magix templates, my computer will automatically restart at some point during the rendering process. I'll use templates like 1080 with 60fps equivalent, 30fps or the 2160 version. Two pass can create more problems. I am NOT choosing the wrong CPU (e.g. AMD) It is absolutely infuriating. I haven't been able to isolate the problem. I can have no other applications open and it also will break the rendering process. Could anyone advise? At the moment, I've had to consider using an alternative since I can only get 1 of several attempts to render.

 

 

Comments

j-v wrote on 5/22/2023, 4:04 PM

For me on laptop from signature with Windows 11 and 16 GB RAM no problem to edit and render my files in VPro 18.

How your problems come I have no idea, maybe you have to give more information following this link: https://www.vegascreativesoftware.info/us/forum/important-information-required-to-help-you--110457/
Mostly a first step to overcome problems is to reset Vegas to its state right after installation following this : https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-reset-vegas-pro-to-default-settings--104646/

Last changed by j-v on 5/22/2023, 4:06 PM, changed a total of 1 times.

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 24H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti with driver 566.14 Studiodriver and Intel HD graphics 630 with driver 31.0.101.2130
Laptop  :Asus ROG Str G712L, W11 home version 23H2, CPU i7-10875H, 16 GB RAM, NVIDIA GeForce RTX 2070 with Studiodriver 576.02 and Intel UHD Graphics 630 with driver 31.0.101.2130
Vegas software: VP 10 to 22 and VMS(pl) 10,12 to 17.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEM CELL DONOR!!! (because it saved my life in 2016)

 

john_dennis wrote on 5/22/2023, 4:39 PM

@Momo-Mojangles

"...my computer will automatically restart at some point during the rendering process."

Time out! Vegas won't cause the system to reboot without some underlying system problem.

Do this and show us the screen shots...

 

... of the Windows Reliability Monitor.

Steve_Rhoden wrote on 5/22/2023, 4:47 PM

@Momo-Mojangles From all that you have described, Something else is throwing your system out of whack.

RogerS wrote on 5/23/2023, 1:22 AM

Maybe a voltage issue or hitting power supply limits? Try providing the info requested above and do stress tests on the CPU and system to see what flaw Vegas is uncovering.

Reyfox wrote on 5/23/2023, 2:37 AM

As soon as I read what @RogerS wrote, I was too was thinking the same thing. Vegas will not cause your computer to restart. What does is a hardware issue. Even if you are running into thermal throttling, it would cause your computer to reboot.

@Momo-Mojangles as for your comment about AMD being the wrong CPU... well, plenty of people in this forum are using it, including me and have never experienced any issues with the CPU or AMD GPU.

Momo-Mojangles wrote on 5/27/2023, 9:21 PM

@Momo-Mojangles

"...my computer will automatically restart at some point during the rendering process."

Time out! Vegas won't cause the system to reboot without some underlying system problem.

Do this and show us the screen shots...

 

... of the Windows Reliability Monitor.

Fascinating - had no idea this existed. Unfortunately, none of the stop points shows Vegas.

Momo-Mojangles wrote on 5/27/2023, 9:24 PM

Maybe a voltage issue or hitting power supply limits? Try providing the info requested above and do stress tests on the CPU and system to see what flaw Vegas is uncovering.

I was guessing it was more likely choking on something in the video file or filter (only using Vegas filters.) I say this because the reboot kept occurring at around the same time period. It's definitely not an overheat as I've used other more intensive software and I also have heat monitoring.

I also do get some strange other behavior such as freezing that requires force quit while editing. Vegas will also not start up at times and I must reboot. It's an odd issue of constant, regular problems I didn't have with the prior version. That was rock solid.

Momo-Mojangles wrote on 5/27/2023, 9:25 PM

As soon as I read what @RogerS wrote, I was too was thinking the same thing. Vegas will not cause your computer to restart. What does is a hardware issue. Even if you are running into thermal throttling, it would cause your computer to reboot.

@Momo-Mojangles as for your comment about AMD being the wrong CPU... well, plenty of people in this forum are using it, including me and have never experienced any issues with the CPU or AMD GPU.

Regarding the first part, see above. Thanks regarding the second. I thought that the CPU preference was to take advantage of the video graphics such as as each rivals special hardware.

RogerS wrote on 5/27/2023, 10:54 PM

Maybe a voltage issue or hitting power supply limits? Try providing the info requested above and do stress tests on the CPU and system to see what flaw Vegas is uncovering.

I was guessing it was more likely choking on something in the video file or filter (only using Vegas filters.) I say this because the reboot kept occurring at around the same time period. It's definitely not an overheat as I've used other more intensive software and I also have heat monitoring.

No, that isn't possible. That could crash Vegas but not force a system shutdown. It's unlikely an overheat issue either as CPUs and GPUs automatically throttle to reduce performance and prevent shutdowns.

Try Intel Extreme Tuning and run a CPU stress test while watching the data.

Assuming it passes that keep it open (or use software like HWInfo64) as you do the next test.

Try one of the two know good benchmarks in my signature and do renders to 4K with Mainconcept and then a GPU encoder (MagixAVC with QSV, VCE or NVENC). See if you hit power limits or thermal limits. See what voltage the CPU is running at. If you experience any shutdowns note if GPU usage is starting to increase when that happens.

If you have an NVIDIA 30XX GPU they're known to create transient spikes that trip power supplies to suddenly shut off. If it's not the GPU, try increasing voltage offset a bit for the CPU in the Intel tool and see if that helps. I can easily trigger shutdowns in my systems with too low CPU voltage, especially when overclocked.

john_dennis wrote on 5/27/2023, 11:23 PM

“...none of the stop points shows Vegas.”

You’re going to have to shoot the bug where the bug exists.

Former user wrote on 5/28/2023, 5:17 AM

I was guessing it was more likely choking on something in the video file or filter (only using Vegas filters.) I say this because the reboot kept occurring at around the same time period. It's definitely not an overheat as I've used other more intensive software and I also have heat monitoring.

No, that isn't possible. That could crash Vegas but not force a system shutdown. It's unlikely an overheat issue either as CPUs and GPUs automatically throttle to reduce performance and prevent shutdowns.

@RogerS Probably not in this situation, but it is possible for VP19 versions after b550 and VP20 to bring down Windows due to eating up all the ram. It happened to me today while playing around with Vegas AI FX. Vegas became unresponsive, Windows unresponsive, Black screen of death, OBS and other windows apps bringing up GPU related errors. Although windows didn't shut down or restart it must have been close to it.

When I was trying to recreate the error, this is as close as I came to replicating what Task Manager looked like

Ran out of Vram, so Vegas ate up all 'shared GPU memory' plus Vegas was using more ram then in this example. This created a GPU hardware error relating to LiveKernelEvent, and that's what basically brought down windows forcing me to restart.

So Vegas caused a GPU hardware error due to eating up all my ram which brought down windows. I don't think this user is running out of Ram, maybe GPU driver problem or the other reasons people have suggested.

 

... of the Windows Reliability Monitor.

Fascinating - had no idea this existed. Unfortunately, none of the stop points shows Vegas.

@Momo-Mojangles What critical errors does it show when Vegas causes windows to crash?

Look for something like 'CRITICAL EVENT: Windows: Hardware error.

Double click that message for more information.

RogerS wrote on 5/28/2023, 5:31 AM

Interesting, I've had AI crashes but never all ram getting consumed.

I've see Vegas l lead to GPU BSODs and then a system crash. A sudden restart with no warning sounds like it's just uncovering other system stability issues, potentially power related.

Former user wrote on 5/28/2023, 7:30 AM

Interesting, if Style Transfer is added, then each time the style was changed the dedicated ram increased,

even when playback has stopped it's high, & 65° is hot for my GPU, I didn't let it keep running,

Momo-Mojangles wrote on 6/6/2023, 9:02 AM

I appreciate the incredible interest, suggestions, recommendations and advice and analysis - and especially the sharing from all of you. I did what I should have done a while ago and we'll see where this leads me - I've completely uninstalled the software, rebooted, reinstalled. We'll see whether problems will continue to occur.

One odd issue - Starting Vegas would sometimes result in not starting at all. I'd try to launch it again and I would have a second instance of Vegas running in Task Manager. If I ended the task that was slightly smaller (3.6MB or so), Vegas would launch with the slightly larger instance (4MB or so.) This worked often but, at times, after the application would quit this wouldn't work and I'd have to reboot.