-
crashing on renders
My project in Vegas Pro 12 is about 10 minutes. Output settings DVD WIdescreen. Every time I try to render this project, Vegas crashes. Tried rendering to a new track. It gets stuck. Rendering in three parts of under 4 minutes: it gets stuck. Rendering in six parts, with bottom en top channels separate: it gets stuck.
I’ve tried selective prerender. Works fine. Then render: it gets stuck.
Press cancel: it’s stuck and stays that way. Only way to go on is to close Vegas through Windows and start it up again.
Of course I restarted my computer several times, closed down even more processes that I know I could do without, but every time I try to render to an output file, Vegas crashes. An output file is created, but it is corrupted and won’t play or import in Vegas. Judging by the size, it is not the entire project by a long shot.So how do I render this project?
Please help…. -
18 Replies
-
What O/S?
Which Processor?
How much RAM?
How many hard disk drives?
How much free space?
How many Displays?
How many Display Adpter cards?
Same brand?
What virus scan program are you using?
Media Manager turned on?
How much Preview RAM?
Wacom tablet?
GPU support on or off?
HOW does the crash present?
Error message?
What is the source of the media?
Does the media play will with VLC Media Player or Wondershare videoplayer/? (both free)
What “Render As” template are you using?
Did you change the default configuration?
Have you previously completed similar projects?Steve Mann
MannMade Digital Video
http://www.mmdv.com -
What O/S? Windows 7
Which Processor? Intel i7
How much RAM? 32Gb
How many hard disk drives? 3 internal, 1 usb
How much free space? 92Gb on C, 129 Gb on destination drive
How many Displays? 2
How many Display Adpter cards? 1
Same brand?
What virus scan program are you using? none; edit computer isn’t online
Media Manager turned on? don’t know; which one do you mean?
How much Preview RAM? 1020; increased to double, but no better
Wacom tablet? no
GPU support on or off? off, but worse with it onHOW does the crash present? At first the systems just hangs. Although the “time passed” counter is still counting, nothing happens after a while. A rendered media file is created but can’t be played in media player or imported in Vegas. Error message says “corrupted file”. Lateron Windows reported problems with Vegas and cues to cease operation and report or not report the problem.
What is the source of the media? Media comes from multiple sources: 2 hd camera’s and dvd.
Does the media play will with VLC Media Player or Wondershare videoplayer/? (both free) all media playes without problems in Vegas and in media player
What “Render As” template are you using? avi pal dvd widescreen; also tried hd 1440×1018 50i but no better
Did you change the default configuration? working in default configuration meant not being able to preview properly, so I adjust settings to fit the media
Have you previously completed similar projects? Yes. The problem gets worse the more channels I use. Simple 1 or 2 track video with same audio presents no problem. This project uses 9 video tracks, one with track motion, 6 with pan/crop adjustments, and 3 audio track, one with track effects. Rendering 3 track to one new one, also crashes. Prerendering works, but previewing or rendering afterwards crashes.
-
Since your project has 9-tracks, try making a test project (use save-as) and delete half of the tracks and remove the unused media from the project media window. What I am suggesting is that one of the tracks may contain a problem, so let’s narrow it down and see if you can identify the offending track.
Other thoughts:
I have seen renders stall out in older versions of Vegas because I had unused media in the project, but that doesn’t seem to be happening any longer, but it’s easy to test.
I have also seen this happen if one of your system folders is running out of space.
In Vegas, click on Options, hold the Shift key and click on Preferences then select the Internal tab.
Do not change anything in this tab unless you know what you are doing – you can truly screw up Vegas here.
On the “Show Only Prefs Containing” box, enter “Path”. Here you will see the folders needed by Vegas. Make sure the paths all have plenty of space. Any folder on your SSD can probably be moved to your HDD safely, as long as the folder exists. (Vegas won’t create the folder for you).Make sure your Windows temp folders aren’t on the SSD. In a command window, (start/cmd), type “set t” and you will see where Windows is setting your TMP and TEMP folders. If this is on your SSD, then you probably want to move the TMP and TEMP folders to your HDD.
Go to Control Panel, System, Advanced System Settings. This will open a System Properties window. Click on the “Advanced” tab. Here you can edit the TMP and TEMP paths to your HDD. Do not put them on a removable drive or you could crash Windows if that drive is not available the next time you start Windows. You can change only the TMP and TEMP User Variables, or both the User and System Variables to a temp folder on your HDD. Click OK, OK to get out of the Control Panel.
Also, you can safely delete anything more than a day old from the TEMP/TMP folders.Memory errors can sometimes cause the program to hang, but there’s almost always an error message. But it can’t hurt to run memtest86 overnight to stress the RAM. You could also stress the CPU by running Prime95 for an hour.
Your specs look good, but what is your pagefile size? If your pagefile fills (it shouldn’t with your specs) your PC can slow to a crawl while pagefile data is being swapped in and out of hard-disk.
Have you looked into your system logs to see if there’s a clue – something occurring when the PC crashes?
I am inclined to think either memory or a bad video card driver. Preview RAM is supposed to be used only with Shift-B preview, or preview on a region, but tests have demonstrated that Vegas does need *some* preview RAM for ordinary renders. 1024 seems to be the sweet spot. Adding tracks shouldn’t make a significant difference in memory – I have one project with over 100 tracks and lost of track motion.
If you installed a codec pack, you may have replaced a good codec with really inferior ones, some of which are pretty sloppy with memory management.
Run Malwarebytes. It can’t hurt, and even though your PC isn’t on the web, many of the programs on it came from there.
Other than that, I am out of ideas.
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
Thanks very much for this extensive reply. I’ll start trying out the several ideas.
In the mean time, maybe this helps narrowing the field. Every time I start up Vegas, after the main window appears but before any tracks are visible in it, it flashes. No other software on this computer does that.
Also, in this project, after working in the fx-window or any other either in or outside of Vegas, returning to the main screen/timeline takes some time. The waiting symbol is visible, then a short flash and I’m back to work the timeline.
Vegas also crashed quite a lot when work on this project was well on the way. After a while this would happen so often that I shut it down, disconnected the computer from the mains and start over some time later.When the system hangs after starting rendering, the cpu reports zero activity. After selective prerendering it said to only take 29 seconds for the complete render of the project. Of course, well before the 29 seconds passed, the system hanged again.
Thanks again and I’ll let you know how it works out.
J.J.
-
That flash says that there’s something wrong in your video device drivers. Either it’s out of date or conflicting with another driver.
Just because you see something on the screen doesn’t mean that the device drivers are OK. The device drivers contain a library of system calls (subroutines) that an application (Vegas) can use. If your driver is out of date, then a plug-in or codec may be making a call to a non-existent or malfunctioning routine in the driver DLL. (The last L in DLL is “Library”).
Also, zero CPU activity just means that the CPU is waiting for something to happen.
When Vegas hangs, start/run Resmon and on the Overview tab look for the Vegas image. Right click on the Vegas image and then on “Analyze Wait Chain”. If there’s a process running that Vegas is waiting on, write down the process name – it may be a clue. Then kill the process that Vegas is waiting on. Vegas should return to normal.
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
Joost, make sure your drivers are up to date and approved by Vegas. There are specific drivers for nVidea for example, and cards, that have been tested. If all is well there, then try this. (discussing on another thread also at present)
Turn off GPU acceleration. Go back to OFF and let the CPU handle it. If that doesn’t fix it, then try closing your video preview window prior to rendering.
Let us know if that helps.
Al
-
Excellent! Thanks. Will do. You’ll hear again.
-
Here’s what I’ve seen so far.
To get Vegas to hang, I started a render. During this there were 3 attempts at network activity (this is a stand alone system; no connection to any other), average 60% memory use, lots of disc activity. Resmon showed one 100% hard memory error. The render seemed complete, but sony problem report said Vegas Pro didn’t work anymore; resmon said Vegas Pro was running normally.Render stopped at 99%, but the file was written and could be played as well. Sound and image were however not always correct, sometimes repeated, sometimes left out. Not what is on the timeline, and quite unusable.
When I got Vegas to hang, Sony problem report stated:
Vegas 120 exe (PID: 4188) Thread: 5220
FileIOSurrogate.exe (PID: 5084) Thread: –When I pressed cancel, svchost.exe got busy as seen in resmon.
So I couldn’t do anything with Vegas. Most memory then seemed to be used by explorer.exe
On termination of Vegas the disc activity peaked at 100%At startup Vegas doesn’t just flash anymore with the bigger projects, the screen gets all white for several seconds. After that there seem to be several interruptions before I can work again. With very small projects it is still just a flash.
Never could I see a message that Vegas was waiting for something. Resmon always said Vegas was running normally. When the message was it didn’t react, I tried to find out why. Before I could status had changed to “running normally”.
At computer shut down often the message is displayed that a process is going on in the background. So something is clearly messing with things. I don’t know how to isolate what it is, though.
I hope this clarifies my trouble to you, because I’m slowly getting desperate with a deadline arriving next week.
-
I am still inclined toward the Video Device Drivers.
I’ll try to address various issues in your list.
Network activity: Just because you are unplugged from the net, it won’t stop Vegas or some plug-ins from checking for a new version.Just for grins – What file paths does Vegas use?
In the Options tab hold the shift key and click on Options.
WARNING – Changing anything on the Internal tab can truly screw up Vegas
At the bottom there is an option to filter your preferences. Enter “Path” here. In the “Value” column, you want to make sure that all of the paths listed are accessible and have plenty of free space. If you have an SSD for your system drive, space could be getting tight. Also, due to the nature of some SSD drives, you could be getting into a racetrack condition where one process could be dependent on the data that another hasn’t moved from the SSD RAM buffer to the SSD storage yet. You can safely change these to a folder on your hard disk with two warnings. First, never use an external drive for Vegas paths. If the external drive is not present, or assigned a different drive letter by Windows, then Vegas will crash. Second, you must create the folder on the HDD before you change the path in the Internal Preferences tab. Vegas will not create them for you.” average 60% memory use, lots of disc activity. ” – As I said before, CPU % use and Drive % use are extremely poor metrics for system performance. Besides, they are only useful when 0% or 100%. 100% only means you hardware isn’t fast enough.
” Resmon showed one 100% hard memory error” – Could be a problem, but if the error didn’t abort the program, it probably worked on retry by the program. Still, did you run MEMTEST86?
“Render stopped at 99%, but the file was written and could be played as well. ” The disk activity at the end of a render is where Vegas is cleaning up the temporary files and finalizing the output file.
“Sound and image were however not always correct, sometimes repeated, sometimes left out.” This one is a head scratcher. What render template are you using? Have you tried a different one?
“FileIOSurrogate.exe”
See: https://www.custcenter.com/app/answers/detail/a_id/5121/~/fileiosurrogate-error“Most memory then seemed to be used by explorer.exe” This is normal when nothing else is active.
“At startup Vegas doesn’t just flash anymore with the bigger projects, the screen gets all white for several seconds. After that there seem to be several interruptions before I can work again. With very small projects it is still just a flash.” – This is screaming Driver Error. Those white flashes could be the driver trying to load a function then giving up.
“At computer shut down often the message is displayed that a process is going on in the background.” – What process is still running? Cancel the shutdown and open the task manager to see what is still running.
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
Got the news on a crash now:
vegas 120exe wait for FileIOSurrogate.exe
vegas120.exe (PID:2584) Thread: 3964
FileIOSurrogate.exe (PID: 4196) Thread: –Then I had a look at FileIOSurrogate in resmon:
one or more threads of FileIOSurrogate.exe are waiting
FileIOSurrogate.exe (PID: 4196) Thread: 5436
FileIOSurrogate.exe (PID: 4196) Thread: 5860I terminated one of the FileIOSurrogate operations. Vegas then finished the render. What was to be expected though, the render was missing quite a lot by way of sound and image.
Thanks for your respons before. I go about checking your suggestions.
As Arnie Schwarzenegger said: I’ll be back.
Reply to this Discussion! Login or Sign Up