Oh man, that's going to be rough. I've already rendered the walkthrough into separate parts before when I decided to put them on youtube individually. But I deleted all those separate videos to free up space afterwards. You're telling me I'm going to have render all those videos separately again?

Why do you think rendering them separately and combining them back together would work? I'm asking because that walkthrough was split into 45-50 parts. That's a lot of rendering to do again.

Several instances of vp open rendering the various parts. To be fair I have only ever used 3 max but it did work.

Sounds like you're running out of disk space. The final storage size is nowhere near the scratch disc space needed to get it there.

I don't see how. When the file crashes at the same spot, the failed un-rendered file is sitting at 76GB. I check my space and I still have 324GB left. You're saying the estimated file size is far bigger than 168GB?

It can't be that much bigger. Even if the estimated file size was off, I still got 324gb left. I thought it was a memory issues at first. When I first started rendering the file and had it crashing at the same spot, I had around 300gb and removed some things to get up to 400gb. But even with an extra 100 more gigs, it still crashes at the same spot.

What would you suggest I have? Do I need 500-600gb available?

Just a wild guess: what's on your timeline at around 50%, when it crashes? You sure that media file is not corrupted?

Just video game footage. No crazy effects or anything. The characters are just walking around. I know the file isn't corrupted as it plays fine and has no issues playing in vegas. The same spot where it keeps crashing at, I have already rendered it before separately. As I stated above, when I make video game walkthroughs, I structure each chapter the same way it is in the game and I batch rendered all my videos.

That specific file with the crash spot, I rendered that level out which was 1.3 hours of footage. It took over an hour or so to render with no crashes. I could just re-record that same footage again and insert it into the project but I don't believe that's the problem. Otherwise, it should have crashed before when I rendered from that same footage separately.

I'm currently using the advice frosty and diverg stated. I'm rendering out the walkthrough again and going to combine them together to see if that works.

Sir, in addition to the rendered size, the virtual memory often must accomodate hundreds of GBs of buffers, and quite often a .tmp file which is the same size as the render. Figure three times the rendered file size to be safe on disk space.

I don't "assume" that is the cause of your problem, but assuming it "isn't" the cause does not rule it out either, speculation notwithstanding. And I certainly didn't reply to trigger a rebuttal, just something to consider. Another thing to consider is corrupt frames near tho lockup point. Best of success going forward, and welcome to the forum.

You can get a 2TB portable for around $50. And looking at the size of your renders, you'll need it.

One thing you could try... render just the area that is crashing to a magix intermediate file (this will keep any perceptible quality loss from happening). make sure the template you choose matches your project resolution and framerate, but instead of rendering it the old fashioned way, select "render to new track" from the Tools menu. This will put the new rendered file on its own track, above the original video. Then delete the original part that it kept locking up on, and render the whole thing out.

@Musicvid: I took your advice and removed more footage. I had around 400gb available and I removed more things to get 720gb available. Unfortunately, that didn't solve the problem and I still keep getting the same crash error at around 50% percent. Didn't work but I'll keep your advice in mind when I render out larger files in the future. And thanks for the welcome. Glad to be here. I just hope I can figure out this issue.

@fr0sty: I took your advice of rendering the walkthrough into several parts and combining them together and still had crash issues. Matter of fact, I took into consideration that the base footage might be corrupt. So, I removed all of footage that happens at the crash spot. I took it out the project and was hoping that would solve the issue. Well, instead of crashing at 50% percent, it went past the crash spot onto the next piece of footage. This time, it hit 51% percent and then it crashed again.

I would have tried your magix intermediate file solution but I don't believe it's going to help. Since I removed the crash footage out and it still crashed onto the next piece of footage, it doesn't seem the footage is actually corrupt. That's considering I was able to render this walkthrough into five parts with each video lasting 6 hours with no crash issues.

So I looked back at the issue it keeps giving me. Make sure you have write access to the file/folder and that there is enough free space. Since my renders go to my documents, I actually right clicked on documents, enter properties and clicked on security. And I noticed for me as a user, there are permissions for full control, modify, read and execute, list folder contents, read and write. And the write part was not checked under me as a user. So I went into the edit section and gave myself permission to write. I figured this might be the solution. Well it turns, out still gave me the same error. Then I actually logged as administrator and tried to render the project and still got the crash error.

I am completely out of solutions and don't know what to do.

Do you have an antivirus or other security software running in the background? When it quits, does it leave a partial file in Documents, or nothing?

Norton is usually running in the background. The others I have is malware bytes, cc cleaner, and super anti-spyware. They're usually all running. I might have closed 1-2 of them out except norton when I was rendering the file though.

Also, it leaves a partial file. It's suppose to render 168gb and when it crashes at 50%, the partially rendered file is usually at 76gb and it won't play.

Maybe a power management issue? I'm about out of ideas here.

. Well, instead of crashing at 50% percent, it went past the crash spot onto the next piece of footage. This time, it hit 51% percent and then it crashed again.

Have you been around in the 40%'s . Is your system or encoding drive getting inexplicably full, is ram use high?

Do you have sleep turned off? Not that vegas should sleep, unless it stops rendering, is your target drive some how going to sleep? My non system drives go to sleep, although they wouldn't if I was writing to them. Maybe it's just a vegas bug

Running multiple anti-virus apps at once can cause all kinds of problems (each constantly scanning your files, slowing you down), especially Norton. I'd get rid of that entirely.

As for your issue, one other user did report success by going to c:/program files/VEGAS/18.0/X86/fileIoSurrigate.exe, and enabling permissions on it like you did with your my documents folder. Give that a shot.

What is your heat management? I had a problem like this a long time ago, and then I went to 6 8" fans and liquid cooling and never had that problem again.

Okay everybody, I believe I see what the problem is. It's not the footage that's corrupt, no heat management or lack of space.

I did several more test rendering the footage at extremely low bitrates to make it render faster. I had the bitrate very low to the point where it said a 26-27 hour file would be 5GB when finished rendering. And the crash error still happened. So I decided to remove about a good 6 hours of footage to where the crashing was happening. The spot where it crashes it, all of that footage is removed including tons of footage ahead. Typically, I get the crash at 50% rendering. This time with a lot of footage removed, the video rendered up to 63% at a different spot and still crashed.

But I noticed one thing. It's the frame count when the video is rendering. When it crashes, the frame count is around 1,430,000 and that's when it crashes. It doesn't matter if you're rendering at a high or low bitrate. It doesn't matter what spot the video is at. As soon as the frames reach 1,430,000 while rendering, the crash happens. It also keeps giving me that same error: An error occurred writing the file. Make sure you have write access to the file/folder and that there is enough free space

Why are high frames causing it to crash? I did these rendering test on two different computers. My main and backup computer both keep getting the same results. I am using the Sony AVC/MVC format in case I didn't state this before. This format has been working fine with me for over 3 years.

Someone did mention there being an issue in certain windows configurations regarding the permissions that the installer assigns to "fileiosurogate.exe", an app that VEGAS relies on for reading and writing files, and that was causing them render errors. To fix it, they went into c:/program files/VEGAS/18.0/x86 and changed the permissions on "fileiosurrogate.exe" to full. To do this, right click on the file, click properties, go to the security tab, click "edit", and assign full permissions to that file (all categories will be checked). Since that app's job is to manage input and output of files, perhaps that means it could be related to your problem, especially since your error mentions lacking permissions to write. See if that helps.

Okay, I'll try it. Although, I don't believe that's the issue as I've already logged on as the administrator and tried to render the file and it still failed.

Well, I did what you said and it just crashed again still giving me the same error. I have full control over my documents and edited file surrogate with full control as well. Still keeps crashing at 1,430,000 frames. As I've stated above, I logged in as the administrator a week back and tried to render it but still crashed.

Do you think I need to change formats? Any more solutions?

I've done about everything I can and have spent three weeks on this program and still haven't figured out the issue. Surely somebody has experienced this before and can tell me what's going on.