Comments

OldSmoke wrote on 6/3/2015, 11:59 AM
Press CTRL+SHIFT when launching Vegas and reset it to default. You may have old GPU settings in it but we wouldn't know because you don't have your system specs filled in.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

TheHappyFriar wrote on 6/3/2015, 12:09 PM
Reinstalling Windows shouldn't leave any settings at all.

Could be an update not done that Vegas needs?
ccliffy wrote on 6/3/2015, 5:49 PM
didn't work of course as it was a fresh install
spec wise I should be OK
DirectX 11
Win 8.1
i7 -370, 8 MB RAM
AMD Radeon 7570
larry-peter wrote on 6/3/2015, 6:00 PM
Did Vegas make it as far as the M$ .net Framework install? Or did you install the correct one on your system prior to Vegas install?
ccliffy wrote on 6/3/2015, 6:24 PM
sorry it did install but when I go to launch for the first time - right after I get confirmation Serial No. it OK - it crashes
larry-peter wrote on 6/4/2015, 9:00 AM
I would recommend first checking the .net build that Vegas 11 requires, and installing it manually from the M$ download site. There could be several reasons for Vegas not firing up after install, but this particular issue bit me once.
Tech Diver wrote on 6/4/2015, 10:11 AM
@ccliffy - It would be most helpful if you filled out your system specs in your forum user profile rather than just send it in a post.

Peter
ccliffy wrote on 6/4/2015, 12:49 PM
done
OldSmoke wrote on 6/4/2015, 12:57 PM
ccliffy

You have to make your specs visible to the forum; there is a check box somewhere.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

vkmast wrote on 6/4/2015, 1:07 PM
Sticky 4 on the Topic Subject page.
ccliffy wrote on 6/4/2015, 1:44 PM
got it
ccliffy wrote on 6/5/2015, 7:42 AM
worth trying to install an older build?
OldSmoke wrote on 6/5/2015, 7:54 AM
Just a few questions. How did you re-install Windows? Did you install over the existing one or did you do a complete hard drive wipe and a new install? Is there an error message when VP11 crashes?

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

ccliffy wrote on 6/5/2015, 10:20 AM
I didnt wipe hard drive but it was a fresh install . Long story but my Dell had no disk and partition w/recovery corrupt so I took it to a repair shop and they installed from an image but were able to get licence #

crash results in this mseeage: http://futurekidsottawa.com/vegas.png
then this meesage to go here which is silly as I already have that build
http://www.mediasoftwareapps.com/notify/update.asp?id=6070
OldSmoke wrote on 6/5/2015, 4:57 PM
ccliffy

[I]crash results in this message[/I]

Check the two boxes, "Include extra information..." and "Problem details" the next time VP crashes. This may give us more details why it crashed. On my system, error reporting is in this folder: "C:\Users\YourUserName\AppData\Local\Sony\ErrorReport"

YourUserName = your actual user name.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

ccliffy wrote on 6/7/2015, 12:23 PM
what is FileIOSurrogate.exe?
------------------------------------
Extra Information

Problem Description
Application Name: Vegas Pro
Application Version: Version 11.0 (Build 701) 64-bit
Problem: Unmanaged Exception (0xc0000005)
Fault Module: C:\Program Files\Sony\Vegas Pro 11.0\x86\FileIOSurrogate.exe
Fault Address: 0x000000006671CCF9
Fault Offset: 0x000000006671CCF9

Fault Process Details
Process Path: C:\Program Files\Sony\Vegas Pro 11.0\x86\FileIOSurrogate.exe
Process Version: Version 11.0 (Build 701)
Process Description: File I/O surrogate (not visible)
Process Image Date: 2012-09-24 (Mon Sep 24) 19:54:26
rs170a wrote on 6/7/2015, 1:32 PM
From the Sony Knowledgebase


FileIOSurrogate error

This problem has to do with the version of QuickTime you are using. Please see the following steps for both the workaround and solution.

The workaround:

Rename the QuickTime .dll file for Vegas, so that Vegas will no longer make use of it. This will mean that you will no longer be able to open or render QuickTime (.MOV) files with Vegas. If you don't use such files in the first place, this should be a more or less seamless workaround.

1) Depending on the filepath displayed under Fault Module, the plug-in will be in one of two locations:

C:\Program Files\Sony\Vegas Pro [version number]\FileIOPlugins\qt7plug\qt7plug.dll

-or-

C:\Program Files (x86)\Sony\Vegas Pro [version number]\FileIOPlugins\qt7plug\qt7plug.dll

Navigate to either of these locations by opening the start menu, clicking on "Computer" and then finding the C drive, and the relevant subfolders.

2) Once you have found the .dll file, right-click on it. Select "Rename" from the dropdown list. Click once at the very end of the file name (after the letters .dll). Add the phrase .hide to the end of the file name. This ensures that the actual name of the file has not changed, so that should you wish to carry out the complete solution in future, it will be easy to undo this measure.

The solution:

Current versions of Vegas require QuickTime 7.1.6 or later to open and render QuickTime (.MOV) files. If you are getting this error message, and must either open or render such files, you must find a version of QuickTime that will work well with Vegas. The following steps may require trial and error:

1) Uninstall the version of QuickTime you currently have. To do this, go to Start > Control Panel > Programs > Uninstall a program. Find QuickTime, right-click on it, and select "Uninstall" (which may incidentally be the only option when right-clicking).

2) Test installing different versions of QuickTime and then trying to open Vegas. The earliest version that will work with Vegas Pro 11.0 and 12.0 is 7.1.6. You may find a variety of QuickTime versions here.

It may be necessary to test more than one version of QuickTime. It is typically best to go about this systematically, from earliest to latest. After each install of QuickTime, attempt to open Vegas to see if the issue has been resolved.
ccliffy wrote on 6/8/2015, 8:56 AM
thanks - that did the trick

I'd upgrade but vegas/Catalyst uncertainty makes me gun shy and I have been using Vegas since 1999