severe PC crashes after build 643 (or driver update?)

Mindmatter wrote on 7/11/2022, 1:20 PM

Hi all
so stil on my problematic randomly crashing DJI project, I today encountered a new weird issue I've never seen before.
After recommendation, I had updated to Nvidia studio driver 516.59 yesterday via the Vegas built in update driver tool, worked on the project for a bit and called it a day.
Today, my system went haywire several times. Totally black screens, then back but without the secondary screen , weird seconds of lines and static like when the screen or GPU dies. Then, total hang of the PC, I had to switch off restart manually a few times.

Then I reinstalled 512.96 with a clean install, although not sure if that was my previous version.
The total crashes continued, and at one point the preview went red and a message popped up " your system is low on memory, Vegas at 45%."
This is like a next level crash, and I'm not sure where the problem is.
I'll go back to a yet earlier driver and possibly to an earlier V19.
My system is usually dead solid, one of my last projects was a complex and track heavy compositing clip without any issues.
Any ideas, otherwise?
Thanks!
 

Last changed by Mindmatter

AMD Ryzen 9 5900X, 12x 3.7 GHz
32 GB DDR4-3200 MHz (2x16GB), Dual-Channel
NVIDIA GeForce RTX 3070, 8GB GDDR6, HDMI, DP, studio drivers
ASUS PRIME B550M-K, AMD B550, AM4, mATX
7.1 (8-chanel) Surround-Sound, Digital Audio, onboard
Samsung 970 EVO Plus 250GB, NVMe M.2 PCIe x4 SSD
be quiet! System Power 9 700W CM, 80+ Bronze, modular
2x WD red 6TB
2x Samsung 2TB SSD

Comments

Gid wrote on 7/11/2022, 2:56 PM

Don't know if your low on memory is GPU or RAM but @Reyfox & i have commented in another post about Vegas's weird use of RAM

Here in this pic, 68GB usage, nothing on the timeline, nothing in the project list, no proxies, no prerender or Dynamic ram set,

closing Vegas cleared this down to my usual 10-14%, I’m lucky to have plenty of RAM but for others…

Last changed by Gid on 7/11/2022, 2:58 PM, changed a total of 1 times.

Vegas Pro 21 
Magix Movie Studio Platinum 2024 - from 2004-ish - Latest version,
Magix VPX14
Boris Continuum & Sapphire, 
Silhouette Standalone + Plugin, 
Mocha Pro Standalone + Plugin, 
Boris Optics,
Desktop PC Microsoft Windows 10 Pro - 64-Bit
ASUS PRO WS WRX80E-SAGE SE WIFI AMD Motherboard
AMD Ryzen Threadripper PRO 3975WX 3.5GHz 32 Core
Corsair iCUE H150i RGB PRO XT 360mm All-in-One Liquid CPU Cooler
RAM 256GB ( 8x Micron 32GB (1x 32GB) 2666MHz DDR4 RAM )
2x Western Digital Black SN850 2TB M.2-2280 SSD, 7000MB/s Read, 5100MB/s Write
(programs on one, project files on the other)
Graphics MSI GeForce RTX 3090 SUPRIM X 24GB OC GPU
ASUS ROG Thor 1200W Semi-Modular 80+ Platinum PSU 
Fractal Design Define 7 XL Dark TG Case with 3 Fans
Dell SE3223Q 31.5 Inch 4K UHD (3840x2160) Monitor, 60Hz, 

I'm 55, I've been a UK joiner for 39yrs, apprentice trained & time served, I make videos about my work & post them on Youtube so that I can share what I've learnt over the yrs,
https://www.youtube.com/c/Gidjoiner

At the moment my filming is done with a Samsung Galaxy S23 Ultra 

j.razz wrote on 7/11/2022, 5:35 PM

I too updated my video drivers (twice) with the most current build of Vegas 19 and am experiencing crazy amounts of instability while working on the timeline and rendering (I only updated them because I was having stability issues after updating to the latest version of Vegas 19). I'm using an Asus ROG Zephyrus G14 with the following specs:

Windows 11 64
Processor    AMD Ryzen 9 5900HS with Radeon Graphics           3.30 GHz
Installed RAM    40.0 GB (39.4 GB usable)
Device ID    9606A7EA-2617-4398-BA92-F71151E235C1
Product ID    00325-82064-22743-AAOEM
System type    64-bit operating system, x64-based processor
Pen and touch    Pen support

I'm currently about to roll back to a 2021 nVidia driver for my device just for troubleshooting. Is there a way to roll back to the previous build of Vegas before the 643 Build?

I did find that if I use Intel QSV as my render option under HVEC I can get a stable render, but it takes soooo long to render out. using the AMD results in weird things in my render, like a fade getting stuck so that the entirety of the graphic's opacity is never shown, then it moves on to the next scene. nVidia renders typically result in crashes, either hard where the program disappears and the screen goes black, or I'm unable to even get task manager to show up, or it will end with the Vegas reporting window.

Just adding to this thread in case someone else has ideas or Magix takes note.

Eric-Berger wrote on 7/11/2022, 6:39 PM

I am having this exact same issue on build 643, I thought I was going crazy. I am trying to edit 10-bit HEVC footage from a Panasonic HC-X1500. These files are not the most edit friendly, but have been quite okay in proxy mode on all versions of 19 Pro - until now. I can't even make it a minute before the screens go black and an error appears referencing mxhevcplug\mxvideoallocator.dll

I am on an Intel I7-6700k, 32 GB RAM, and RTX 3080 graphics card.

8 Bit and other types of footage working okay, only crashing with 10 bit footage.

Gid wrote on 7/11/2022, 7:17 PM

@Eric-Berger Hi, have a look at this recent post about 10bit video & see if it's similar to your problem, https://www.vegascreativesoftware.info/us/forum/stuttering-playback-of-h-265-10-bit-4k-video-footage--136169/?page=1

Vegas Pro 21 
Magix Movie Studio Platinum 2024 - from 2004-ish - Latest version,
Magix VPX14
Boris Continuum & Sapphire, 
Silhouette Standalone + Plugin, 
Mocha Pro Standalone + Plugin, 
Boris Optics,
Desktop PC Microsoft Windows 10 Pro - 64-Bit
ASUS PRO WS WRX80E-SAGE SE WIFI AMD Motherboard
AMD Ryzen Threadripper PRO 3975WX 3.5GHz 32 Core
Corsair iCUE H150i RGB PRO XT 360mm All-in-One Liquid CPU Cooler
RAM 256GB ( 8x Micron 32GB (1x 32GB) 2666MHz DDR4 RAM )
2x Western Digital Black SN850 2TB M.2-2280 SSD, 7000MB/s Read, 5100MB/s Write
(programs on one, project files on the other)
Graphics MSI GeForce RTX 3090 SUPRIM X 24GB OC GPU
ASUS ROG Thor 1200W Semi-Modular 80+ Platinum PSU 
Fractal Design Define 7 XL Dark TG Case with 3 Fans
Dell SE3223Q 31.5 Inch 4K UHD (3840x2160) Monitor, 60Hz, 

I'm 55, I've been a UK joiner for 39yrs, apprentice trained & time served, I make videos about my work & post them on Youtube so that I can share what I've learnt over the yrs,
https://www.youtube.com/c/Gidjoiner

At the moment my filming is done with a Samsung Galaxy S23 Ultra 

john_dennis wrote on 7/11/2022, 7:54 PM

@j.razz

“Is there a way to roll back to the previous build of Vegas before the 643 Build?”

Save a system image for free before installing each Vegas build or video driver.

https://www.macrium.com/reflectfree

https://www.aomeitech.com/download.html

My main system:
Motherboard: ASUS ProArt Z790-CREATOR WIFI
CPU: Intel Core i9-13900K - Core i9 13th Gen Raptor Lake 24-Core (8P+16E) P-core Base Frequency: 3.0 GHz E-core Base Frequency: 2.2 GHz LGA 1700 125W Intel UHD Graphics 770 Desktop Processor - BX8071513900K
GPU: Currently intel on-die video adapter
RAM: CORSAIR Vengeance 64GB (2 x 32GB) 288-Pin PC RAM DDR5 5600 (PC5 44800) Desktop Memory Model CMK64GX5M2B5600C40
Disk O/S & Programs: WD Black SN850 NVMe SSD WDS100T1X0E - SSD - 1 TB - PCIe 4.0 x4 (NVMe)
Disk Active Projects: 1TB & 2TB WD BLACK SN750 NVMe Internal PCI Express 3.0 x4 Solid State Drives
Disk Other: WD Ultrastar/Hitachi Hard Drives: WDBBUR0080BNC-WRSN, HGST HUH728080ALE600, 724040ALE640, HDS3020BLA642
Case: LIAN LI PC-90 Black Aluminum ATX Full Tower Case
CPU cooling: CORSAIR - iCUE H115i RGB PRO XT 280mm Radiator CPU Liquid Cooling System
Power supply: SeaSonic SS-750KM3 750W 80 PLUS GOLD Certified Full Modular Active PFC Power Supply
Drive Bay: Kingwin KF-256-BK 2.5" and 3.5" Trayless Hot Swap Rack with USB 3
Sound card: Realtek S1220A on motherboard. Recording done on another system.
Primary Monitor: ASUS ProArt 31.5" 1440p HDR10 Monitor PA328QV
O/S: Windows 10 Pro 10.0.19045 Build 19045
Camera: Sony RX10 Model IV

https://www.youtube.com/user/thedennischannel

Magix Service Center

https://www.vegascreativesoftware.info/us/forum/mpg-file-sound-track-absent-on-timeline--135335/#ca895123

View Reliability History

https://www.vegascreativesoftware.info/us/forum/not-responding--142806/#ca893148

j.razz wrote on 7/11/2022, 8:07 PM

I have gotten too comfortable with the stability of 17 and 19 that I thought those days were over and I became lax :)

I remember all the way back to Vegas 4 through 7 being stable, then with 8-16 or so stability issues almost moved me to DaVinci Resolve. 17 changed that for me.

Thanks for the reminder John! Hopefully stability is just around the corner again.

fr0sty wrote on 7/11/2022, 8:34 PM

I just tried to update to the latest studio driver and had issues as well, it's possible the driver is buggy.

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)

j.razz wrote on 7/11/2022, 8:53 PM

I just tried to update to the latest studio driver and had issues as well, it's possible the driver is buggy.

I went back to the previous driver from nVidia (it was still in my download folder), and still have issues unfortunately.

RogerS wrote on 7/11/2022, 10:42 PM

I rolled back NVIDIA drivers and then reinstalled the latest one and haven't had issues with 19 so I think the driver is likely fine and the issues are elsewhere.

J.razz, I don't have Radeon Graphics but those drivers have had a lot of issues over the last year. Perhaps try rolling back a few versions and see if it helps?

Also, "I did find that if I use Intel QSV as my render option under HVEC" - well that confuses me as your system has no Intel iGPU; does that just fall back to a slow software encoder?

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, Windows 11 Pro 64 bit

Dell XPS 15 laptop (2017) 32GB ram, NVIDIA 1050 (4GB) with latest studio driver, Intel i7-7700HQ with Intel 630 iGPU (latest available driver), dual internal SSD (256GB; 1TB), Windows 10 64 bit

VEGAS Pro 19.651
VEGAS Pro 21.108

VEGAS 4K "sample project" benchmark: https://forms.gle/ypyrrbUghEiaf2aC7
VEGAS Pro 20 "Ad" benchmark: https://forms.gle/eErJTR87K2bbJc4Q7

j.razz wrote on 7/11/2022, 11:50 PM

 

Also, "I did find that if I use Intel QSV as my render option under HVEC" - well that confuses me as your system has no Intel iGPU; does that just fall back to a slow software encoder?

Apparently, as it is painfully slow. While everything else that successfully completed the render (with artifacts) within minutes, Intel QSV took over an hour and a half to complete the render process.

I'll see what I can figure our regarding the radeon graphics. Thanks for the tip!

Mindmatter wrote on 7/12/2022, 2:37 AM

Bummer...I reinstalled build 550 and V19 won't load the project I made in build 643.
I knew this to happen from one issue of Vegas to the next, but within the same version?? Really?
So I'll be stuck with the buggy build.

AMD Ryzen 9 5900X, 12x 3.7 GHz
32 GB DDR4-3200 MHz (2x16GB), Dual-Channel
NVIDIA GeForce RTX 3070, 8GB GDDR6, HDMI, DP, studio drivers
ASUS PRIME B550M-K, AMD B550, AM4, mATX
7.1 (8-chanel) Surround-Sound, Digital Audio, onboard
Samsung 970 EVO Plus 250GB, NVMe M.2 PCIe x4 SSD
be quiet! System Power 9 700W CM, 80+ Bronze, modular
2x WD red 6TB
2x Samsung 2TB SSD

fr0sty wrote on 7/12/2022, 5:49 AM

Unfortunately, sometimes adding features or fixing bugs requires this. They did put a warning with the download, but I personally feel it should pop up during installation as well.

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)

Eric-Berger wrote on 7/12/2022, 2:12 PM

@Gid; I browsed that thread and found it helpful. I did a reset of V19 (Control + Shift + Open) and unchecked "Enable legacy HEVC decoding" and set "Hardware Decoder to Use" to Off in the File I/O preferences. Currently no crashes and proxying out and playback of the 10-bit footage is working fine. Hopefully the OP has similar luck with flipping of similar settings, thanks!

baksideDisaster_Flicks wrote on 7/12/2022, 6:45 PM

Very similar to what was happening to me. Seemed like Vegas was crashing the video driver, monitor would black out, sometimes flash white, secondary monitor would go out and I'd have to reboot. I'm using same version of the Nvidia studio graphics driver but I don't think it's the driver as all was fine in 550. In fact, I've rolled back to 550 and haven't had issue since. If you share an error.zip file I'll crack it open and get callstack see if it's the same issue, you'll see problem with MXVideoAllocator.dll.

I did notice that Vegas was consuming massive amounts of memory for the project I was working it before it would crash. To the order of 28GB and not releasing the memory. This version has a serious bug and nobody from Vegas is talking about it. At least they could acknowledge the problem and let us know someone is working on it.

https://www.vegascreativesoftware.info/us/forum/vegas-pro-19-crashing-since-upgrading-to-build-643--136130/

Former user wrote on 7/12/2022, 8:32 PM

Very similar to what was happening to me. Seemed like Vegas was crashing the video driver, monitor would black out, sometimes flash white, secondary monitor would go out and I'd have to reboot. I'm using same version of the Nvidia studio graphics driver but I don't think it's the driver as all was fine in 550.

@baksideDisaster_Flicks That is interesting. The identical thing happened to me with 643 with Video going black on Main monitor, then the same on 2nd Monitor when loading Vegas. Traditionally when that happens you would expect a GPU hardware or driver problem, this is because traditional thinking is software alone can't cause this. It's only happened once so far, but the first time Vegas has done this.

The memory problem is most likely bad code causing memory leaks due to the huge amount of changes made in version 636/643