-
Sony Vegas 8.0c Vista Launch Problems
Posted by Mat Tschirgi on January 1, 2008 at 6:01 pmHey, just purchased a laptop and decided to get Sony Vegas Movie Studio to go along with it since in college I loved using Sony Vegas 4.0
After installing, activating, and updating the software, my copy of DVD Architect is fine, but my copy of Vegas Movie Studio 8.0c stops working while it tries to load the program intially. It has a Windows Vista “Sony Vegas Movie Studio has stopped working” prompt when the program is loading “Creating file I/O manager”.
My computer is a Toshiba L45-S7409 upgraded to 2 Gigs of SDRAM.
I did submit a tech support complaint to Sony Customer Service, but have not received a response in 7 days and was wondering if any readers here might know a possible solution.
Thanks and happy new years!
— Mat
Dibyajyoti Deb replied 14 years, 6 months ago 7 Members · 9 Replies -
9 Replies
-
Sebastian Alvarez
January 2, 2008 at 11:38 pmI would check with either Toshiba or Microsoft to see if you can downgrade for free to Windows XP, even if you have to pay for the shipping of the CD. I had Vista installed for two months, and I’m good with computers, but Vista for now is junk. Parts of the new interface are pretty, but its performance is a disaster. It’s much slower than XP on everything, and has lots of problems doing file operations. You’d be much better off installing XP and then Vegas again.
-
Bob Myers
January 4, 2008 at 1:12 amHaving similar problem (including the lack of response from Sony) on an HP Pavilion Slimline desktop (purchased new in October with Vista Home Premium pre-installed). Installed Vegas 8.0 and got error. Then downloaded and installed 8.0c update, but with no change. After trying many other things ended up reverting to a previous restore point (thereby taking version back to 8.0 as seen below).
The only difference is I’m not getting the I/O message – here are the details from the error dialog:
Problem signature:
Problem Event Name: APPCRASH
Application Name: VegasMovieStudio80.exe
Application Version: 8.0.0.142
Application Timestamp: 4729fbd9
Fault Module Name: StackHash_e14d
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Code: c0000096
Exception Offset: 02d22a3b
OS Version: 6.0.6000.2.0.0.768.3
Locale ID: 1033
Additional Information 1: e14d
Additional Information 2: 26988f61b78658cdc06935d4c678943a
Additional Information 3: e506
Additional Information 4: b2d77884ec2a4eeb9f0aaf3a2d5990fd -
Bob Myers
January 4, 2008 at 11:35 amFound some info in another forum that helped me – here’s the link https://dvinfo.net/conf/showthread.php?t=104099
Basically the other post says there’s a problem with the AVI plugin. Since I’m not currently using any AVI files I was able to simply remove the aviplug.dll file from the FileIO folder and everything started working fine.
Don’t know if this will work for you, but it solved weeks of aggravation for me.
-
Mat Tschirgi
January 4, 2008 at 2:35 pmThanks so much, Bob, Vegas now works great. I am a much happier video editor now! 🙂
The best work around seemed to be:
1) Go to the Vid-Cap Plug In Folder and copy aviplug.dll
2) Go to the I/O Input Folder and replace the exisiting aviplug.dll with the one from the Vid-Cap folder (make a back up of the original first)
3) Run Vegas -
Bob Myers
January 9, 2008 at 1:34 amHere’s another update. I finally gat a reponse from Sony after I told them how I got the app running. It turns out my son did need to use AVI files. The “fix” allow Vegas to run, but the AVI files would only come in as audio, so I was hoping Sony would be able to help. Well, long story short is they said in order to use AVI files with Vegas you need to purchase a 3rd party codec. They provided the following info:
—————————–
In order to view the avi file in Vegas you have to install third party software. Here are the links for the Third party codec.https://www.morgan-multimedia.com/
https://www.pegasusimaging.com/index.htm
——————————
Well after trying several other freeware codecs (unsuccessfully) I finally tried the 60 trial at the morgan link above and it seems to work great (although I’m not thrilled about spending another $20 or so for functionality that seems should have been in the app to begin with). Althougth it is a codec for AVI files, it is the MPG codec.Hope this helps.
-
Timothy Carroll
May 19, 2008 at 1:32 amI found another workaround. In my case, the reason aviplug.dll was causing the crash was because Data Execution Prevention (DEP) was enabled for all programs. Usually Vista will tell you in a pop-up that DEP is the cause for the crash, but in this case it did not. On a whim I tried adding vegas80.exe to the DEP exceptions and it fixed the problem! Interestingly, the aviplug from the video capture (it’s an older version) would not crash, like everybody else, but the new one did. So something in the new one (perhaps the aforementioned virtualization check) was causing violating DEP. Very strange…
-
Adam Rose esq.
May 19, 2008 at 5:49 pmyep, that DEP solution was one I found too, though on reinstall of OS (vista64 business) for unrelated reasons, even that disappeared. Actually, IIRC, was DVDA that threw a hissy fit until DEP was removed for it…
now mine just works flawlessly. Mine not to reason why
🙂
-
Vivian Leung
October 5, 2009 at 2:34 amI’m having the same creating file I/O manager problem but on Vegas 7.0. I looked around the folders but I can’t find any vid-cap folder. Can someone help me?
-
Dibyajyoti Deb
November 5, 2011 at 5:07 amI recently got the new Sony Vegas Pro 11, and while opening it when it says Creating File I/O , it comes up with an error and crashes.
The details are as follows:
Problem Description
Application Name: Vegas Pro
Application Version: Version 11.0 (Build 424)
Problem: Unmanaged Exception (0xc0000005)
Fault Module: C:\Program Files\Sony\Vegas Pro 11.0\vegas110.exe
Fault Address: 0x5861BB89
Fault Offset: 0x5861BB89Fault Process Details
Process Path: C:\Program Files\Sony\Vegas Pro 11.0\vegas110.exe
Process Version: Version 11.0 (Build 424)
Process Description: Vegas Pro
Process Image Date: 2011-10-31 (Mon Oct 31) 04:49:34
Reply to this Discussion! Login or Sign Up