Render freezes - I have tried EVERYTHING

Hazmat-Ftw wrote on 2/3/2024, 7:33 AM

Alright, I am losing my mind. The render freezes at a certain percentage no matter what I do. I have tried EVERYTHING to get this program to render:

  • Updating/rerolling my GPU driver.
  • Running in Admin mode.
  • Running in compatibility mode.
  • Disabling/Enabling GPU render.
  • Dynamic RAM from 0 to 90%.
  • Disabling/enabling multi-core rendering.
  • Enable/Disable So4 Hardware Decoding.
  • OpenCL off/on.
  • Disabling/enabling one or several cores on the Vegas application.
  • Setting the system priority of the program to high.
  • Rendering the project as a highlighted section.
  • Rendering one entire section as batch files through a script.
  • Rendering divided sections as batch files through a script.
  • Rendering as MXF or other file-types than MP4 (that doesn't render either).
  • Exporting the entire project and then importing it as one media block.
  • Rendering parts of the project to determine where the error is - doesn't work either, the render freezes no matter what.
  • Resetting Vegas to factory default.

If you can think of it - I have most likely tried it. This is insane. No matter what I do, the program will freeze and the file will not be rendered. It says So4 hardware detection error in the log - but I can't figure out what the problem is.

Someone, for the love of god - help me! I have used this program for ages, but I'm seriously on the verge of completely discarding Vegas for something else.

What do I do?

Extra Information
   File:                \AppData\Local\VEGAS Pro\21.0\gpu_video_x64.log
   File:               \AppData\Local\VEGAS Pro\21.0\fileio_x64.log
   File:               \AppData\Local\VEGAS Pro\21.0\persist.prefs
   File:                \AppData\Local\MAGIX\FileIO\1.0\So4HardwareDetectionError.log
   File:                \AppData\Local\MAGIX\FileIO\1.0\So4HardwareDetectionOutput.xml
   File:                \AppData\Local\VEGAS Pro\21.0\dx_video_grovel_x64.log
   File:                \AppData\Local\VEGAS Pro\21.0\svfx_video_grovel_x64.log
   File:                \AppData\Local\VEGAS Pro\21.0\ocio_x64.log
   File:                \AppData\Local\VEGAS Pro\21.0\dx_grovel_x64.log
   File:                \AppData\Local\VEGAS Pro\21.0\vst_grovel.log
   File:                \AppData\Local\VEGAS Pro\21.0\vegas_script_x64.log
   File:                \AppData\Local\VEGAS Pro\21.0\hub.log
   File:                \Documents\HuntLoreSheriffHardin.veg

Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 21.0 (Build 208)

Fault Process Details
   Process Path:        C:\Program Files\VEGAS\VEGAS Pro 21.0\vegas210.exe
   Process Version:     Version 21.0 (Build 208)
   Process Description: VEGAS Pro
   Process Image Date:  2023-11-30 (Thu Nov 30) 05:19:46
 

Comments

j-v wrote on 2/3/2024, 7:54 AM

I miss in your EVERYTHING the reset option.
Resetting the program brings it back to the situation right after the installation.
To do a reset follow exactly this: https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-reset-vegas-pro-to-default-settings--104646/

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)

 

mark-y wrote on 2/3/2024, 9:14 PM

The render freezes at a certain percentage no matter what I do.

A "certain" percentage? Meaning the same place every time? Then you need to tell us exactly what is on the timeline at that place. Everything.

https://www.vegascreativesoftware.info/us/forum/important-information-required-to-help-you--110457/

RogerS wrote on 2/3/2024, 10:40 PM

It's likely the source media causing issues in VEGAS, not any of these settings you are attempting to manipulate (most of which are irrelevant to render crashes). Try to return all those to defaults as J-v describes.

MediaInfo and info about your system is a great place to start!

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

You can also try two known good projects in my signature which will likely render without issue.

Hazmat-Ftw wrote on 2/4/2024, 3:24 AM

I miss in your EVERYTHING the reset option.
Resetting the program brings it back to the situation right after the installation.
To do a reset follow exactly this: https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-reset-vegas-pro-to-default-settings--104646/

Already done a reset - that didn't work either.

The render freezes at a certain percentage no matter what I do.

A "certain" percentage? Meaning the same place every time? Then you need to tell us exactly what is on the timeline at that place. Everything.

https://www.vegascreativesoftware.info/us/forum/important-information-required-to-help-you--110457/

The percentage changes according to the settings. Without GPU it's usually at 25%, with GPU it is 90%, with internal settings changed it varies between 2, 25, 83, 90 and 91%. I'm not sure if it has anything to do with what is on the timeline.

It's likely the source media causing issues in VEGAS, not any of these settings you are attempting to manipulate (most of which are irrelevant to render crashes). Try to return all those to defaults as J-v describes.

MediaInfo and info about your system is a great place to start!

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

You can also try two known good projects in my signature which will likely render without issue.

Alright, I'll try and take a look. I'll try to reset everything again before I render it.

Thank you all for your replies - I'm wondering if maybe it could be a hardware issue?

RogerS wrote on 2/4/2024, 4:02 AM

I highly doubt it's a hardware issue and wouldn't advise trying to upgrade to fix it. See if the projects in my signature render with the recommended settings and then we can take a look at your media/project.

For this purpose keep dynamic ram preview at the default (5%), GPU on and update GPU drivers (go to help/driver update in VEGAS) and update any that are old.

Last changed by RogerS on 2/4/2024, 8:33 PM, changed a total of 1 times.

Custom PC (2022) Intel i5-13600K with UHD 770 iGPU with latest driver, MSI z690 Tomahawk motherboard, 64GB Corsair DDR5 5200 ram, NVIDIA 2080 Super (8GB) with latest studio driver, 2TB Hynix P41 SSD and 2TB Samsung 980 Pro cache drive, Windows 11 Pro 64 bit https://pcpartpicker.com/b/rZ9NnQ

ASUS Zenbook Pro 14 Intel i9-13900H with Intel graphics iGPU with latest ASUS driver, NVIDIA 4060 (8GB) with latest studio driver, 48GB system ram, Windows 11 Home, 1TB Samsung SSD.

VEGAS Pro 21.208
VEGAS Pro 22.239

Try the
VEGAS 4K "sample project" benchmark (works with VP 16+): https://forms.gle/ypyrrbUghEiaf2aC7
VEGAS Pro 20 "Ad" benchmark (works with VP 20+): https://forms.gle/eErJTR87K2bbJc4Q7

fr0sty wrote on 2/4/2024, 10:15 AM

When updating the GPU driver, make sure you aren't using a driver intended for gaming. Use the driver update utility in VEGAS help, as mentioned above.

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Geforce RTX 3090

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

VEGASDerek wrote on 2/5/2024, 10:13 AM

@Hazmat-Ftw You have provided all the different things you have tried, but you have provided virtually nothing in regards to your hardware, media in your project, and the effects you are using. Could you please provide this? Providing your persist.prefs file could also be useful. A freeze during a render usually is due to some resource running out during the render process. With that has a hypothesis, we need to know what you are doing in this project and the hardware you have to get an idea of what the true cause of the problem is. Otherwise, we are only throwing darts with a blindfold on in an attempt help you out.