... will not start ...

Earl_J wrote on 10/3/2013, 1:16 PM
Okay fellas. . .
I have Sony Vegas 8.0; Vegas 9.0; Vegas 10.0; Movie Studio 8.0; Movie Studio 9.0 . . .
I just now downloaded Movie Studio 12.0. . .

Every program I try stops abruptly at the start and indicates that the program has stopped.
Can any of you provide an English translation of the techspeak below...?
I'm willing to post the responses of the other programs if it'll help. . .
Perhaps the "I/O surrogate not visible" might have some bearing...?

It appears everything Sony is being specifically targeted on my computer...
Can that really be the case...?

{EDIT}Just today, uninstalled the old MovieStudio 12 and reinstalled the download I accomplished today...

* * * * * * * * * *

Problem Description
Application Name: Movie Studio Platinum
Application Version: Version 12.0 (Build 1184) 64-bit
Problem: Unmanaged Exception (0xc0000005)
Fault Module: C:\Program Files\Sony\Movie Studio Platinum 12.0\x86\FileIOSurrogate.exe
Fault Address: 0x000000007741CC49
Fault Offset: 0x000000007741CC49

Fault Process Details
Process Path: C:\Program Files\Sony\Movie Studio Platinum 12.0\x86\FileIOSurrogate.exe
Process Version: Version 12.0 (Build 1184)
Process Description: File I/O surrogate (not visible)
Process Image Date: 2013-08-21 (Wed Aug 21) 17:26:36

Comments

Steve Grisetti wrote on 10/3/2013, 1:23 PM
You don't say what operating system you're using or what format of file you're editing -- but have got the latest version of Quicktime installed?

Also see this:
https://www.custcenter.com/app/answers/detail/a_id/5121/~/fileiosurrogate-error
Earl_J wrote on 10/3/2013, 1:33 PM
How intriguing. . .

I just tried every button Sony/Vegas on my desktop. . .

Vegas Pro 9.0 opened and in full resolution. . . (sigh)

{EDIT}
Spoke too soon. . . it runs. It just won't let me add any tracks... (sigh)

I'm looking into the QT aspect...
Earl_J wrote on 10/3/2013, 1:35 PM
The info is correct in my system information tab...

I'm running Win 7, 64-bit. . .

I lost the full-sized external monitor view a few weeks ago...
It has returned today.
* * *
You may be onto something with the QT. . .
let me check it out. . .
ChrisDolan (SCS) wrote on 10/3/2013, 1:55 PM
the "File I/O Surrogate" is where all of the 32-bit plugins run so they don't interfere with the rest of the 64-bit app. It's marked as "not visible" because it has no GUI. The highest-profile plugin that runs 32-bit is indeed QuickTime which has a whole plugin infrastructure of its own, but also MP3 and a few other audio formats.

When we see crashes like this, it's most often due to a QuickTime plugin, but I'd need to get my hands on an error report to know for sure.
Earl_J wrote on 10/3/2013, 2:23 PM
Steve. . .
you're a genius, my friend...
* * *
I looked up the qt file as your link suggested...
I have two Program Files folders... the qt.dll thing was in one and not the other...
I cut it from one (x86) and placed it into the other (where my Movies Studio 12 program resides)...

Viola. . .!

Movie Studio works - well, apparently... I haven't tried any manipulations just yet...

not sure if any of the other ones will get fixed...

your recommendation has helped tremendously...

I have lots of time on my hands now - can you pronounce furlough. . .? (grin)
Gary James wrote on 10/3/2013, 3:49 PM
Many times after a Vegas crash, the Vegas process is closed by Windows, but the FileIOSurrogate module is left running in memory. This can prevent a new instance of Vegas from starting up.

Open up Task Manager, and look in the Processes Tag. Sort the list by Name. If you see FileIOSurrogate running, right-click and tell Task Manager to Kill the process. After that, Vegas should start up normally and relaunch a new copy of FileIOSurrogate.
Earl_J wrote on 10/3/2013, 11:10 PM
Hello Chris,
hmmm... well, Movie Studio Platinum 12 is working now...
haven't tried my Vegas Pro 11 just yet. . .

I have a series of those error reports over the last week or so...
Each time it stopped, I indicated send details and blasted it off to who knows where...
well, maybe you know where. . . (grin)

Until that time . . . Earl J.
Earl_J wrote on 10/3/2013, 11:11 PM
I'll try that next time around, Gary...

Thanks for helping out. . .

Until that time . . . Earl J.