Vegas keeps crashing upon Initializing GPU-accelerated video processin

Former user wrote on 12/28/2019, 5:30 PM

More specifically Vegas Pro 14 (Build 270) 64-bit keeps crashing upon Initializing GPU-accelerated video processing. I tried find AMD Catalyst Control Center, because on this page I tried following Step 16 and went here and as far I can tell AMD Catalyst Control Center is now AMD Radeon Software and the whole UI of the software or whatever changed because of an update and now that tutorial is useless to me. So, basically my question is how do get Vegas Pro working again?

P.S. Feel free to ask me if something I said wasn't clear.

Edit: I forgot to mention that before I installed new AMD Drivers, I would get a blue screen of death every week or 2, so, it seems like I either have Vegas Pro working, but get BSoDs every week OR Vegas Pro doesn't work, but I don't get BSoDs every week, is there not a solution to have Vegas Pro working AND I don't get BSoDs every week?

System details:

OS Name   Microsoft Windows 10 Home
Version   10.0.17763 Build 17763
System Manufacturer   Dell Inc.
System Model   Inspiron 5575
System Type   x64-based PC
System SKU   0812
BIOS Version/Date   Dell Inc. 1.1.6, 7/26/2018
SMBIOS Version   3.1
Embedded Controller Version   255.255
BIOS Mode   UEFI
BaseBoard Manufacturer   Dell Inc.
BaseBoard Product   0M0Y6P
BaseBoard Version   X01
Platform Role   Mobile
Secure Boot State   On
PCR7 Configuration   Binding Not Possible
Windows Directory   C:\Windows
System Directory   C:\Windows\system32
Boot Device   \Device\HarddiskVolume1
Hardware Abstraction Layer   Version = "10.0.17763.831"
Installed Physical Memory (RAM)   8.00 GB
Total Physical Memory   7.64 GB
Available Physical Memory   2.14 GB
Total Virtual Memory   9.64 GB
Available Virtual Memory   2.62 GB
Page File Space   2.00 GB
Page File   C:\pagefile.sys
Kernel DMA Protection   Off
Virtualization-based security   Not enabled
Device Encryption Support   Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and device is not InstantGo, Un-allowed DMA capable bus/device(s) detected, TPM is not usable
Hyper-V - VM Monitor Mode Extensions   Yes
Hyper-V - Second Level Address Translation Extensions   Yes
Hyper-V - Virtualization Enabled in Firmware   Yes
Hyper-V - Data Execution Protection   Yes

GPU - AMD Radeon(TM) Vega 8 Graphics - Primary/Integrated
VRAM - 256 MB - DDR4 1200 MHz
Graphics Card Manufacturer - Powered by AMD
Graphics Chipset - AMD Radeon(TM) Vega 8 Graphics
Device ID - 15DD
Vendor ID - 1002
SubSystem ID - 0812
SubSystem Vendor ID - 1028
Revision ID - C4
Bus Type - PCI
Current Bus Settings - PCI
BIOS Version - 016.002.000.004
BIOS Part Number - 113-RAVEN-102
BIOS Date - 2017/09/05 18:58
Usable Memory Size - 256 MB
Memory Type - DDR4
Memory Clock - 1200 MHz
Core Clock - 1101 MHz
Total Memory Bandwidth - 38 GByte/s
Memory Bit Rate - 2.40 Gbps
2D Driver File Path - /REGISTRY/MACHINE/SYSTEM/CurrentControlSet/Control/Class/{4d36e968-e325-11ce-bfc1-08002be10318}/0000
OpenGL® API Version - 4.6
OpenCL™ API Version - 2.0

Other Details:

Extra Information
File: C:\Users\USER\AppData\Local\VEGAS Pro\14.0\dx_video_grovel_x64.log
File: C:\Users\USER\AppData\Local\VEGAS Pro\14.0\svfx_video_grovel_x64.log
File: C:\Users\USER\AppData\Local\VEGAS Pro\14.0\ocio_x64.log
File: C:\Users\USER\AppData\Local\VEGAS Pro\14.0\dx_grovel_x64.log
File: C:\Users\USER\AppData\Local\VEGAS Pro\14.0\gpu_video_x64.log

Problem Description
Application Name: VEGAS Pro
Application Version: Version 14.0 (Build 270) 64-bit
Problem: Unmanaged Exception (0xc0000005)
Fault Module: C:\Windows\System32\DriverStore\FileRepository\c0327778.inf_amd64_14d19eb83774a0f4\B327509\amdocl64.dll
Fault Address: 0x00007FFFA61B2D54
Fault Offset: 0x0000000002022D54

Fault Process Details
Process Path: C:\Program Files\VEGAS\VEGAS Pro 14.0\vegas140.exe
Process Version: Version 14.0 (Build 270) 64-bit
Process Description: VEGAS Pro
Process Image Date: 2017-06-12 (Mon Jun 12) 22:05:46

Comments

fr0sty wrote on 12/28/2019, 5:32 PM

Have you tried going to AMD's site and downloading the latest drivers for it?

Musicvid wrote on 12/28/2019, 5:34 PM

Yep. Not ready for prime time, apparently even in latest versions. Magix should leave it off by default.

https://www.vegascreativesoftware.info/us/forum/crashing-intel-chip-ez-fix--118233/

https://www.vegascreativesoftware.info/us/forum/faq-graphics-cards-gpu-acceleration-for-vegas-pro--104614/?page=1

The test for any graphics/driver combination is, "Will it scrub at 4x?"

It's one of those "wish" features that everyone would like to see work, not just for some.

fr0sty wrote on 12/28/2019, 5:47 PM

Don't wanna amputate over a hangnail...

I've been using GPU accel without issue for years. Once in a while it requires a driver update, or a driver update will break it, but for the most part it does what it should for me. Running around telling people to turn it off by default is robbing them of useful performance that works for most people, so the better option would be to tell them to make sure their GPU drivers are up to date, which solves the vast majority of GPU related issues.

BruceUSA wrote on 12/28/2019, 6:39 PM

frosty..1000% right on. Happily enjoy GPU Accel since VP11. For those who anti GPU ACCEL in Vegas is simply because they have never had the awesome experience with it. I absolutely love mine. I own two systems both are working beautifuly. One of my system is old, 6 cores with old R9 290X still work great with no problem like some of the unfortunate people.

Musicvid wrote on 12/28/2019, 6:54 PM

Different strokes, @fr0sty

I won't judge your posts if you don't judge mine.

fr0sty wrote on 12/28/2019, 7:43 PM

Don't take it as a personal attack, nobody is judging anybody here. We're all just trying to make sure that this user gets over their GPU issues while retaining as much functionality as possible, rather than jumping to the nuclear option right of the bat. My money says they just need a driver update, but we'll see.

Musicvid wrote on 12/28/2019, 7:57 PM

We're all just trying to make sure that this user gets over their GPU issues while retaining as much functionality as possible,

I agree 100%. I don't think that cross-referencing divergent opinions is a purposeful means to achieving that shared goal. A term we use in counseling students to better peer relationships is "co-independence."

BTT.

Former user wrote on 12/28/2019, 11:35 PM

@fr0sty I recently updated my drivers and haven't been able to use Vegas since, and it sounds like I should maybe turn off GPU accel if nothing else works, anything else I could try.

matthias-krutz wrote on 12/29/2019, 11:07 AM

Dell strongly recommends a BIOS update on the Inspiron 5575 support page:
Updated the Video BIOS (VBIOS) to support the new Video RAM (VRAM).
No guarantee that it will work, but to me it sounds logical.

fr0sty wrote on 12/29/2019, 11:16 AM

Do the above, and:

"I recently updated my drivers and haven't been able to use Vegas since"

If updating a driver breaks compatibility, then roll it back to the previous version.

Former user wrote on 12/29/2019, 1:09 PM

@matthias-krutz I updated my BIOS, Vegas still doesn't work.

@fr0sty There's was a detail I glossed over and forgot to mention (It has been added to the post for the record) that before I installed new AMD Drivers, I would get a blue screen of death every week or 2, so, it seems like I either have Vegas Pro working, but get BSoDs every week OR Vegas Pro doesn't work, but I don't get BSoDs every week, is there not a solution to have Vegas Pro working AND I don't get BSoDs every week? I might just get a newer version of Vegas or ask what I should do on either Microsoft's own forms or AMD's.

fr0sty wrote on 12/29/2019, 1:23 PM

That brings it into the realm of a hardware defect being a possibility. If I were in your shoes, I'd be trying various AMD driver versions to see if any of them produces a result that doesn't produce a BSOD or crash upon opening... but usually BSODs are indicative of hardware conflicts or malfunctions.

To get you going, you might try installing the driver that triggers the BSOD, then disabling GPU acceleration in Vegas' preferences once you are able to get it to open. Vegas can operate without your GPU, so if it turns out that the GPU is malfunctioning and causing these issues, you can still edit.

AllRiledUp wrote on 12/29/2019, 1:44 PM

@fr0sty That's probably what I'll end up doing, if I can't find any other solution.

matthias-krutz wrote on 12/29/2019, 3:13 PM

In the log file I see that despite 8 GB of physical RAM, very little memory is available. This could be due to the dyn. RAM Preview setting. This memory is reserved for preview only and is not available for Vegas or Windows. If the memory becomes scarce then the swap file is needed.
In Windows, the paging file size also appears to be set to a fixed value. That's not a good idea. Windows should set this size itself, as is the default. Otherwise, instabilities can arise if the available memory becomes scarce.