V13 crashing on any render attempt - ideas?

ken c wrote on 5/9/2014, 1:08 PM
Hi,

Just bought/installed V13, it won't render anything though without crashing. Even small royalty free video clip, file/render/crash:

Problem Description
Application Name: Vegas Pro
Application Version: Version 13.0 (Build 310) 64-bit
Problem: Unmanaged Exception (0xc0000374)
Fault Module: C:\Windows\SysWOW64\ntdll.dll
Fault Address: 0x0000000077E2E753
Fault Offset: 0x00000000000CE753

Fault Process Details
Process Path: C:\Program Files\Sony\Vegas Pro 13.0\x86\FileIOSurrogate.exe
Process Version: Version 13.0 (Build 310)
Process Description: File I/O surrogate (not visible)
Process Image Date: 2014-04-29 (Tue Apr 29) 18:37:24


win7 high end 64bit, always ran fine w/V7-12...any ideas? thanks --

Comments

Lovelight wrote on 5/9/2014, 2:27 PM
Hi, try rendering to different formats matching the project properties.
larry-peter wrote on 5/9/2014, 2:43 PM
When you say, "won't render anything" do you always get the same error message regardless of source footage or render template?

FileIOSurrogate errors can be caused by the Quicktime version you have installed. In the past, Vegas didn't always like the most current QT installation. I'm not running VP13 yet, but you can do a forum search to see what Quicktime versions others are using successfully in VP13. 7.6.2 was recommended for a while, but the new version may want a different version of Quicktime.

You can check this thread: http://www.sonycreativesoftware.com/Forums/ShowMessage.asp?Forum=4&MessageID=861878 and see if this information applies.
dxdy wrote on 5/9/2014, 2:54 PM
This error often has to do with driver problems. So...

What version of Windows are you running?

What is your video card? What driver version are you using?

Does this issue occur on this machine with Vegas 12?

dxdy wrote on 5/9/2014, 3:01 PM
Also: are you rendering to a SSD? Was it installed as IDE or AHCI? Googling around the web shows some discussions of this.

http://forums.anandtech.com/showthread.php?t=2235433
ChrisDolan (SCS) wrote on 5/9/2014, 4:34 PM
ken c,
This crash is occurring in the 32-bit helper app where Vegas runs codecs that aren't 64-bit compatible. The Microsoft error code "c0000374" is saying that Vegas has asked the helper to free some memory (e.g. a preset) that it no longer needs, but the helper app fails to do so, perhaps because it's already been freed or the memory has been corrupted. So, driver and/or GPU is likely not at fault.

Do you have any 3rd-party file plugins installed? Probably not on a fresh VP13 install, but worth asking...

By "file/render/crash", I assume you mean you never even see the render dialog. So Vegas is likely failing while trying to ask the 32-bit plugins for their list of render templates. Perhaps you have an old template copied from VP12?

Also, QuickTime version is worth checking, but my gut says that's not the answer here...
ken c wrote on 5/9/2014, 5:18 PM
Hi - thanks... the V13 is a brand new install today, it and only it crashes when I try to render; even from same V10/11/12 projects that all rendered fine w/same drivers/identical as worked in earlier versions of Vegas.

The VST plugins I had it scan/cache are identical to what's in earlier versions of Vegas. I can try and reinstall QT, though no render issues in earlier versions of Vegas w/same exact machine/drivers.

V13 is installed on my SSD just like V10/11/12 are, all of which work fine. Maybe I should try uninstalling/reinstall, not reference any VST plugins at all to see if that works.. though the subdirectories I'm including for VST plugins are identical to those I use in V10/11/12.
Soulmansblue wrote on 8/22/2014, 11:37 PM
This I am sorry to say sounds familiar. I am having what appears to be the same problem.

Every time I attempt a render Vegas Pro 13 just simply stops responding after a length of time and just sits there. I then have a problem of getting out of the program to reset and try again. Message says that an operation is taking place would I like to cancel and it will not let me. I have to force it.

I have tried every combination of template settings and formats with the same no response result. I have also tried burning direct to disc with the same result.

I am now going to try and render my project in regions without audio and reassemble them along with the audio in DVD Architect Pro 6 and see if that works as I do have a length of time that passes before the program hangs or does whatever it appears to want. I guess it could just be lazy.

I have tried new graphic card drivers, chipsets you name it. In fact the more I have tried to solve the issue the worst it appears to get. Argh - that's another render attempt gone west. Okay its region time. Here is hoping I just have to finish this project, time is marching on.
Steve Mann wrote on 8/23/2014, 8:57 AM
Check this:
If Vegas terminates abnormally, the FileIOSurrogate process may be left running in memory. This can prevent a new instance of the program from starting up.

Exit Vegas then open the 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, the program should start up normally and relaunch a new copy of FileIOSurrogate.

There should be no fileIOSurrogate process running if Vegas is not. There should be only one instance of FileIOSurrogate running for each instance of Vegas (Vegas120.exe in the process list). You may need to refresh the task manager window to make sure.
Laurence wrote on 8/23/2014, 10:06 AM
Does it crash before or after the render dialog comes up? If it is before, I used to get this all the time in V12 (but never so far in V13). When it would happen, restarts, reboots, even uninstalling and reinstalling of Vegas wouldn't help.

Here's what would work: Start a new project. Insert a blank video track from the top menu. Call up the render dialog. As soon as the render dialog appeared, reload an actual project and try rendering again. I don't know why, but that would fix it. With V12 on my system it was so bad that I would routinely do this at the beginning of every editing session. Otherwise it would lock up and crash when I finally went to render.
NCARalph wrote on 8/23/2014, 12:53 PM
Are you using GPU rendering? If so there have been several discussions about how VP13 seems to have problems with GPU's, at least NVidia ones. You could try turning off GPU rendering or setting the Prerender RAM setting to zero.