Vegas Pro 21 - MAGIX AVC/AAC + HEVC codecs all crash during renders

Bree-Baugh wrote on 4/22/2024, 4:10 PM

Hello friends,

So as of this recent build, I've run into an issue where I absolutely cannot render anything using the MAGIX AVC?AAC codec or the HEVC ones either. I tried the old MainConcept AVC, and it sometimes works, but often I end up with a crash as well.

Previously, there was a random chance that these crashes would also cause BSODs, which led me to believe it must absolutely be a hardware or driver issue. However, after doing basically all the troubleshooting I can thing of, nothing has helped.

Below are my PCs specifications:

  • CPU: Intel Core i9 14900k 3.2Ghz
  • Mobo: ASUS ROG Strix Z790-A Gaming LGA 1700
  • RAM: G.SKILL Trident Z5 DDR5 RAM 64GB 6000MT/s (clocked at 5700mhz in xmp profile)
  • GPU: RTX 3090 Founder's Edition
  • PSU: ROG Thor 1200W Platinum II
  • Drive: SAMSUNG 990 PRO

 

Here's everything I've tried so far to troubleshoot

  • Check for driver conflicts
  • Remove/Reinstall/update all hardware drivers
  • Thorough experimentation with Vegas' Preferences and Internal settings
    • I would list everything specifically but I've tried so many different settings and combinations that I wouldn't be able to remember all of them.
  • Updated BIOS
  • Run diagnostic checks on all hardware (2 tests on the ram - Windows Memory Check and memtest 86) -- No errors were found
  • Check windows for corrupt files and subsequently repaired them
  • Examined all .DMP given to me from windows BSOD crashed
    • It led me to which system file it said was causing the crashes so I repaired it, but it didn't help.
    • Can't remember the file name, so I'll update this once I've found it again
    • BSOD main error was "CLOCK_WATCHDOG_TIMEOUT" which made me think it was hardware, but after all the diagnostic checks and stress tests/benchmarks I did, I'm not sure how else to check my hardware.
  • Fresh install of windows on formatted drive
    • So far, no BSODs on new Windows install, but Vegas is still crashing while rendering AVC codecs
  • Again, reinstalled all driver from fresh install of windows

 

I'm getting pretty exhausted trying to find a solution, and I still need to try doing this on the previous build to see if I still get those crashes. In the meantime, is there anything you guys would recommend I try?

 

Thank you in advance,

Bree

Comments

j-v wrote on 4/22/2024, 4:50 PM

First of all, reset Vegas to its situation right after install by following this exactly; 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)

 

RogerS wrote on 4/22/2024, 7:08 PM

You have the latest drivers for the Intel IGPU and also the latest NVIDIA studio driver?

Blue screen does suggest something beyond VEGAS alone.

Can it pass stress tests like Intel Extreme Tuning and GPU- 3DMark (free versions)?

I have two benchmark projects in my signature you can use for tests of VEGAS. Many users render with no problems.

Wolfgang S. wrote on 4/23/2024, 2:14 AM

Fresh install of windows on formatted drive

So far, no BSODs on new Windows install, but Vegas is still crashing while rendering AVC codecs

At least it should not be an Windows issue - so maybe a hardware/driver issue.

Last changed by Wolfgang S. on 4/23/2024, 2:15 AM, changed a total of 1 times.

Desktop: PC AMD 3960X, 24x3,8 Mhz * RTX 3080 Ti (12 GB)* Blackmagic Extreme 4K 12G * QNAP Max8 10 Gb Lan * Resolve Studio 18 * Edius X* Blackmagic Pocket 6K/6K Pro, EVA1, FS7

Laptop: ProArt Studiobook 16 OLED * internal HDR preview * i9 12900H with i-GPU Iris XE * 32 GB Ram) * Geforce RTX 3070 TI 8GB * internal HDR preview on the laptop monitor * Blackmagic Ultrastudio 4K mini

HDR monitor: ProArt Monitor PA32 UCG-K 1600 nits, Atomos Sumo

Others: Edius NX (Canopus NX)-card in an old XP-System. Edius 4.6 and other systems

bitman wrote on 4/23/2024, 5:01 AM

@Bree-Baugh It could be due to thermal throttling. Software nowadays is more optimized to use multi core, and motherboard manufactures are relaxing their TDP in BIOS way beyond what the processor (and the cooling capability can handle), using XMP profiles is basically overclocking the memory. This the perfect storm for thermal throttling. Vegas is no exception.

You can test the memory, and the memory itself perhaps can handle the overclock also thermally, but do not forget that the memory controller nowadays is not on the separate supporting chipset any more (like a north or southbridge) but integrated into the CPU which will heat up the neighboring cores extra due to the higher speed when using XMP... I noticed I crashed sometimes in starfield (game) when moving fast in different environments, which requires a lot of memory swapping. I lowered the TDP, but it did not help, but the game never crashed anymore after I disabled XMP.

On the part of Vegas, check your BIOS for the TDP settings, we have similar systems, I reduced my TDP from infinite to 200 Watt, then to 125W (including Turbo power limits).

HWiNFO64 can help a lot to see it you are thermal throttling or not when you crash.

More on this on my post:

https://www.vegascreativesoftware.info/us/forum/solution-to-vegas-crashes-on-modern-high-end-cpu-s-e-g-i9-13900k--144004/

Last changed by bitman on 4/23/2024, 5:05 AM, changed a total of 3 times.

APPS: VIDEO: VP 365 suite (VP 22 build 194) VP 21 build 315, VP 365 20, VP 19 post (latest build -651), (uninstalled VP 12,13,14,15,16 Suite,17, VP18 post), Vegasaur, a lot of NEWBLUE plugins, Mercalli 6.0, Respeedr, Vasco Da Gamma 17 HDpro XXL, Boris Continuum 2025, Davinci Resolve Studio 18, SOUND: RX 10 advanced Audio Editor, Sound Forge Pro 18, Spectral Layers Pro 10, Audacity, FOTO: Zoner studio X, DXO photolab (8), Luminar, Topaz...

  • OS: Windows 11 Pro 64, version 24H2 (since October 2024)
  • CPU: i9-13900K (upgraded my former CPU i9-12900K),
  • Air Cooler: Noctua NH-D15 G2 HBC (September 2024 upgrade from Noctua NH-D15s)
  • RAM: DDR5 Corsair 64GB (5600-40 Vengeance)
  • Graphics card: ASUS GeForce RTX 3090 TUF OC GAMING (24GB) 
  • Monitor: LG 38 inch ultra-wide (21x9) - Resolution: 3840x1600
  • C-drive: Corsair MP600 PRO XT NVMe SSD 4TB (PCIe Gen. 4)
  • Video drives: Samsung NVMe SSD 2TB (980 pro and 970 EVO plus) each 2TB
  • Mass Data storage & Backup: WD gold 6TB + WD Yellow 4TB
  • MOBO: Gigabyte Z690 AORUS MASTER
  • PSU: Corsair HX1500i, Case: Fractal Design Define 7 (PCGH edition)
  • Misc.: Logitech G915, Evoluent Vertical Mouse, shuttlePROv2

 

 

Bree-Baugh wrote on 4/23/2024, 11:50 AM

@Bree-Baugh It could be due to thermal throttling. Software nowadays is more optimized to use multi core, and motherboard manufactures are relaxing their TDP in BIOS way beyond what the processor (and the cooling capability can handle), using XMP profiles is basically overclocking the memory. This the perfect storm for thermal throttling. Vegas is no exception.

You can test the memory, and the memory itself perhaps can handle the overclock also thermally, but do not forget that the memory controller nowadays is not on the separate supporting chipset any more (like a north or southbridge) but integrated into the CPU which will heat up the neighboring cores extra due to the higher speed when using XMP... I noticed I crashed sometimes in starfield (game) when moving fast in different environments, which requires a lot of memory swapping. I lowered the TDP, but it did not help, but the game never crashed anymore after I disabled XMP.

On the part of Vegas, check your BIOS for the TDP settings, we have similar systems, I reduced my TDP from infinite to 200 Watt, then to 125W (including Turbo power limits).

HWiNFO64 can help a lot to see it you are thermal throttling or not when you crash.

More on this on my post:

https://www.vegascreativesoftware.info/us/forum/solution-to-vegas-crashes-on-modern-high-end-cpu-s-e-g-i9-13900k--144004/

I was actually just sent some info regarding this being the case for many of the 13th and 14th gen intel processors! I'm doing some research right now on the most stable settings for my PC and I'll report back whether or not the crashing continues.

Bree-Baugh wrote on 4/23/2024, 12:10 PM

UPDATE #1: So I messed with some setting in my mobo's BIOS to prevent my processor and ram from "Turbo" clocking themselves near their marketed capacities. I set all the maximum clock speeds a bit lower while also using Asus' AI Optimizer to make some changes for me that I then adjusted to fit me needs. So far, NO CRASHES!!! I'll keep running my stress tests and benchmarks then report back to see if this was indeed the solution. 😊

john_dennis wrote on 4/23/2024, 12:29 PM

@Bree-Baugh

My perhaps overly-conservative UEFI settings for the i9-13900K.

You could pick a poison closer to 100 degrees C if you like.

The thread is a long and winding road.

Shogun__Gaming wrote on 4/24/2024, 1:52 AM

not sure if its all working now, but i also know that vegas isnt always to happy about editing in the HEVC codec, i swtich back to the H264 which is more stable