Fix for Vegas Pro 13 crash on launch (GPU)

chandigital wrote on 5/13/2014, 8:59 AM

In case anybody else had this problem, new installation of VP13 suite with all packages installed, on launch of Vegas I would get "Vegas Pro has stopped working" after "Initializing GPU-accelerated video processing". Tried switching between Intel and Radeon 7970M graphics card, no difference.

The fix for me was to hold the SHIFT key while launching Vegas with the mouse. After that initial launch, I was able to quit and relaunch without needing to hold the SHIFT key. So far Vegas is working great with this workaround.

Hope this info is helpful to somebody out there

Comments

Steve Mann wrote on 5/14/2014, 9:09 PM

Holding Ctrl + Shift while starting Vegas will reset all preferences and delete cached data prior to loading the program. If you have recently installed new hardware (especially a new graphics card), this is necessary because Vegas may be loading settings for your old hardware.

Greg Bryant wrote on 8/8/2015, 8:05 AM

This has been happening to me for a while. I usually fire up a debugger and get past the crash, but today it started crashing again during rendering, non-recoverable at that point. I found this and tried it, but it still shows the same symptoms at startup. I also updated to the current build (13.0.453) with the same symptoms. Very frustrating. If anyone has other pointers, love to hear them.

Greg Bryant wrote on 8/8/2015, 8:12 AM

Never mind, a link or two down in Google turned up a YouTube video someone posted, suggesting to uninstall part of the AMD catalyst manager, that worked.

Downunder wrote on 8/8/2015, 8:37 AM

Do you have a link to the video?

SamAt wrote on 9/26/2015, 12:22 PM

Nice tip,but does not work for me. I have tried uninstall/reinstall twice, including removing all residual settings left after uninstall. Immediate crash, unusable. I added another monitor, but not vid card. I tried disabling the third display, and launching and crashed. However, this time the Ctrl+Shift did work - in that I got the option to restore all settings to defaults, but after this it crashed again (GPU load as usual).

<Vent>This is out of the blue- no hardware changes. The inability to even clean and launch is unbelievable - after 25 years in the industry, I can't think of an app so prone to corruption and crashing. Unfortunately - I like the product when it's working, and I have hundreds of projects I don't want to abandon. But boy, it ticks me off. </Vent>

OldSmoke wrote on 9/26/2015, 3:38 PM

How many GPU card do you have in your system and what is your motherboard spec?

Arthur.S wrote on 9/27/2015, 7:11 AM

Notice chandigital said hold down the shift key - not shift+ctrl. Never heard of that actually doing anything!

SamAt wrote on 9/27/2015, 12:37 PM

I have two GPUs, but neither has changed. However, I did add a third monitor, though I also tried disabling it. But after restoring C drive back to earlier state I realized that it could not be OS but had to be hardware (which in my mind had not changed, but there was that monitor...). The new monitor is a 24", vs a pair of identical 22", so I reasoned that the app might be getting confused about geometry of work area. Sure enough, I was able to bring Vegas up on the new monitor only. But to make the other two work, I isolated the larger monitor on one card, and hooked up the two 22" on the other and Vegas is back.

In 25 years I've never seen a monitor crash an App. Once again, Vegas wins first prize for most fragile error handling. Sheesh!

SamAt wrote on 9/27/2015, 12:38 PM

Re: Shift+Ctrl: confirm that results in opportunity to reset to defaults, Shift alone did nothing.

tharindu-w wrote on 7/4/2017, 12:47 PM

This happened to me, I quit MSI Afterburner and RivaTuner Statistics Server