this is all i get ..

Problem Description
Application Name: Vegas Pro
Application Version: Version 13.0 (Build 290) 64-bit
Problem: Unmanaged Exception (0xc0000005)
Fault Module: C:\WINDOWS\SYSTEM32\ff_vfw.dll
Fault Address: 0x00007FFC64A65255
Fault Offset: 0x0000000000005255

It freezes during the "Creating Video plug-in factory . . ."

Problem Description
Application Name: Vegas Pro
Application Version: Version 13.0 (Build 290) 64-bit
Problem: Unmanaged Exception (0xc0000005)
Fault Module: C:\Program Files\Sony\Vegas Pro 13.0\vegas130.exe
Fault Address: 0x0000000C01E73A10
Fault Offset: 0x0000000C01E73A10

Fault Process Details
Process Path: C:\Program Files\Sony\Vegas Pro 13.0\vegas130.exe
Process Version: Version 13.0 (Build 290) 64-bit
Process Description: Vegas Pro
Process Image Date: 2014-04-10 (Thu Apr 10) 14:27:08

ff_vfw.dll = FFDshow VFW Module

uninstall FFDShow... then install without the VFW module

i get an error for syswow64 tscc. uninstalled camtasia and the tscc codec by itself, veg 13 still won't start.

Problem solved! Saw in another thread to update an older version of NewBlueTitler. Now Vegas opens with no problems.

Check out http://www.newbluefx.com/support/search-forum. It will have a box toward the top of the screen with the downloads.

djehall

I still get a crash at startup.. I don't even have new blue titler on my computer..
Application Name: Vegas Pro
Application Version: Version 13.0 (Build 290) 64-bit
Problem: Unmanaged Exception (0xc0000005)
Fault Module: C:\WINDOWS\SYSTEM32\ff_vfw.dll
Fault Address: 0x00007FFC64A65255
Fault Offset: 0x0000000000005255

Fault Process Details
Process Path: C:\Program Files\Sony\Vegas Pro 13.0\vegas130.exe
Process Version: Version 13.0 (Build 290) 64-bit
Process Description: Vegas Pro

I still get a crash at startup.. I don't even have new blue titler on my computer..
Application Name: Vegas Pro
Application Version: Version 13.0 (Build 290) 64-bit
Problem: Unmanaged Exception (0xc0000005)
Fault Module: C:\WINDOWS\SYSTEM32\ff_vfw.dll
Fault Address: 0x00007FFC64A65255
Fault Offset: 0x0000000000005255

Fault Process Details
Process Path: C:\Program Files\Sony\Vegas Pro 13.0\vegas130.exe
Process Version: Version 13.0 (Build 290) 64-bit
Process Description: Vegas Pro

As I mentioned in another couple of threads, I can't get Vegas Pro 13 to launch but the DLL that crashes is CFHD.DLL, which is the Cineform codec. I don't have FFDSHOW installed on this machine, so I don't have an FF_VFW.DLL file.

I have just installed an evaluation copy to see if it is worth the upgrade. It crashed right at the start, too. So, for the first time in many years, I will not be upgrading.

So, John, that's two third party codecs that crash the new version of Vegas at startup.

<edit>Correction. Three third party codecs and one stale version of third party plug-in application.</edit>

I don't have any of the codecs installed but maybe I can break it if I install Cineform? I'll give that a try.

(Time passes...) I installed GoPro Studio (don't see where they list the version number but I assume it's the most current version as of 15 minutes ago. Installed it and then loaded Vegas 13. No crashes, no faults. I then closed Vegas 13, opened GoPro Studio and flailed around with it to render a couple of files (an mp4 and an AVI.) Opened VP13 again without issue. Loaded the two rendered files into the project and onto the timeline. No crashes, but no image in the files either, which I'm sure is operator error on the GPStudio side of things.

I can render to Cineform from within Vegas.

Maybe you need to reinstall GoProStudio after installing VP13?

Rob

I installed it on my Win 8 system and it seems to open fine but I'm concerned about my Win 7 system that has Cineform installed. Will try later today and feedback. Even if this works for me it's incredible that so any of you are having problems right from the start of this new release. How can a new release have so many incompatibilities with older software? Hasn't Sony learnt anything?

First time I am not updating, too. Vote with your dollars is my motto.

I had the same problem and removed the dll but all it did was crash a couple of seconds later than previously. You would think at least they would have tested the installer without having to use all these workarounds some of which don't work anyway. At least you saved me having to uninstall Camtasia Studio.

You would think at least they would have tested the installer without having to use all these workarounds some of which don't work anyway.

The thing is, it should not crash, no matter what. Windows has a very good system of structured exception handling, and all professional software should be using it. They actually are using it, but all they do is pop up the report dialog, and quit the software afterwards.

That is not graceful handling of problems. If there is a problem, especially with various plugins and codecs, the rest of the software should still work. Just turn off the plugin/codec and work without it.

It is not our job to find workarounds, it is theirs.

i installed titler 2 and started having startup problems w/ vegas 13. uninstalled titler 2, everything working fine again.

I totally agree. It doesn't exactly inspire confidence in the company. Vegas seems to be the only software which won't install on my computer.

Hi there,

I recently upgraded to Vegas Pro 13 and upon first runs, it always crashed on startup. The problem was always the same - at first, the Sony VST Plug-in Handler crashed and after that, the program wouldn't start at all.

Now, I'm an old user of the VP family, so this was an all-too-familiar bug from some previous versions of VP (starting from v10 or v11 if I recall correctly) - the thing is that there's some VST Plugins in the VST folder that cause Vegas a hard time when it's doing the initial VST plugin scan.

This shouldn't be a reason for the program for not to start however, I still blame Sony for bad coding on this behalf, but I found a workaround from the old forum posts (related to VP11 or VP12 .. Sony, how about fixing the start-up routine??).

When starting the program (= clicking the icon), PRESS AND HOLD DOWN THE CTRL KEY. In addition to that, try to click away any VST plugin error announcements that might pop-up as quickly as you possibly can (it seems that the VST Plug-in Handler thinks that the whole program has frozen up if it takes too long to respond). That was the old forum tip and it worked perfectly for me, VP13 finally started, after which I closed the program and re-started it. Everything has worked perfectly since!

PS: I have to admit that VP13 has a way faster GPU-accelerated preview compared to VP12 and basically all of the full-quality MXF/other full HD preview glitches from previous version(s) are gone! I'm running an i7 Core desktop with AMD FirePro v7900 video card, using OpenCL GPU acceleration.

So, although VP13 might not hold that many new features for the old Vegas user, at least the it now runs noticeably faster and smoother -- once you get it running, lol. Anyway, apart from that VST Plug-in Handler startup bug, the VP13 upgrade was worth the ~120 EUR or so, at least for now ...

Right after installing Vegas Pro 13 in Win8.1 Pro I had Vegas crash on opening. The offending file was reported to be ff_vrw.dll as other users also experienced.
------------
THE FIX: (re)Install K-lite Mega Pack
http://www.codecguide.com/download_k-lite_codec_pack_mega.htm
------------
This pack checks for inconsistencies in the registry. It reported about 12-15 Sony plugins with inconsistent/missing registry entries. I accepted each of them to be fixed ... and voila, Vegas pro 13 starts up normally!!
I haven't tried to deinstall the K-lite pack but I have a hunch it has fixed the Sony problem inherently.
Quote from K-lite: "The installer is able to detect broken codecs and DirectShow filters on your system, and helps you to fix those problems. This unique functionality has helped thousands of people solve problems they were unable to fix themselves or with other packs". Yes-Siree! Thanks!
http://www.codecguide.com/about_kl.htm
There are smaller K-lite packs also, available are Basic, Standard, Full, Mega
http://www.codecguide.com/download_kl.htm
If they all fix the problem, I haven't tried.

I just fixed the issue and have not checked yet if I miss any Vegas features due to the registry cleanup but if it does, I will try reinstalling Vegas 13 (keeping my VP12 untouched as a fall-back).

I'm glad to hear that installing the K-lite codec pack solved your problem, but codec packs have traditionally caused more problems than they have fixed and the recommendations here on the Vegas forum have been to avoid them completely. Rather than installing the entire codec pack, perhaps it would be safer just running their Codec Tweak Tool by itself:

http://www.codecguide.com/download_other.htm#codectweaktool

I had the same general problem as overwhelming number of other VP13 early adopters here - ie : persistent crash at startup after installation of VP v13.

Reasons and error messages vary wildly between different people.

For me - the fix was to remove a sub-folder named "aviplug" from the following folder :

C:\Program Files\Sony\Vegas Pro 13.0\FileIO Plug-Ins

9 out of 10 attempts - VP would crash if that folder is left in its default location.
1 out of 10 attempts - the startup process would hang for the whole 1 minute at the stage of "Initializing UI" after which it would eventually continue to a successful app launch.

I haven't tried yet but I would imagine I won't be able to handle .avi files without the files contained within the removed folder.
Not a biggie, as I mostly work with .MTS and .MOV files.

Although a crap one, it's a solution nevertheless (for now).

I'm beyond frustrated by this situation, however.

I seem to be but one in a legion of individuals who have just spent upwards of £100 in upgrade fees only to waste hours troubleshooting what was was supposed to be a release where (in the exact words of SCS engineer Cris Dolan posted here :
www.sonycreativesoftware.com/forums/ShowMessage.asp?MessageID=888234 ) "We've fixed a HUGE number of stability bugs since Vegas 12 was first released in September 2012. Many of those fixes are already present in VP12 b770, since we don't hold back bugs for new releases. For those of you who have called for stability before features, I hope that you'll really love VP13 and notice that we've been listening."

Erm ...
If we could successfully start the application first we might be in position to evaluate that.
So far, from my own experience and so many other calls on this forum, it seems VP13 launch in the wild is an embarrassing anti-climax.

Are there any QC jobs going at SCS, Chris ?

In any case - I hope this "fix" helps someone.

I would guess that the testers have not actually had this problem - otherwise the would not have been able to test, and if encountered would have fixed it !

So we should try and isolate what some users have on their computers that is causing a problem. (I see that some installed plugins etc seem to be already being identified)

geoff

Thanks RealGigReel.com

I removed Aviplug folder and VeasPro 13 finally, after four days of tearing my hair out, opened!!!

Why would that be??? How did you come to that conclusion to try it?

I tried putting Aviplug folder from 12 in 13 folder and it failed again...
Sadly, I need avi files to open and edit...

I'm in Windows 8.1 - maybe a conflict with microsoft codec?
Anyway, Thanks again