So, I understand that it says up to ver. 17 but I have Vegas pro 18.

A side note: "up to ver. 17" applies only to VEGAS Movie Studio versions. The V Effects and V Images subforums are for discussions on VEGAS Post add-on software. I've moved your posts to Vegas Pro Video forum.

Does that only happen for one specific clip? Or can you render other footage - if you do not have this clip in the timeline?

I would also suggest that you do a quick scan to ensure the the windows key files including ntdll.dll have not been corrupted in any way. To do this go to the cmd prompt and go to directory C:/windows/system32 and run sfc /scannow this will do a file integrity check.

Also see this posted by Vegas Team:
 

VEGASDerek also wrote on 3/24/2021, 1:22 PM

The crash is in the File I/O Surrogate which is used to properly handle some older codecs such as QuickTime, which is a deprecated feature due to the instability it has in Windows 10. You may have turned this on. If so, you would suggest resetting your preferences so VEGAS does not load that codec plugin anymore.

Another user had same issue and found this worked for him:

For me VEGAS Pro 20.0 also crashed everytime I clicked "Render as..." and the fault process details also featured FileIOSurrogate.exe. I was able to fix my problem by changing the settings of the executable File I/O Surrogate.exe such that it is always being run as admin.

Does the VEGAS benchmark project in my signature render?

FileIOSurrogate.exe suggests an issue with the QuickTime 32-bit plugin? What media are you using exactly?

 

I'm using an .mp4 file that I recorded. Of my screen. It's an instant replay made with AMD

Does that only happen for one specific clip? Or can you render other footage - if you do not have this clip in the timeline?

No it happens to all of them, no matter what. I've tried a lot, even just pictures

Another user had same issue and found this worked for him:

For me VEGAS Pro 20.0 also crashed everytime I clicked "Render as..." and the fault process details also featured FileIOSurrogate.exe. I was able to fix my problem by changing the settings of the executable File I/O Surrogate.exe such that it is always being run as admin.

I will try that!

Does the VEGAS benchmark project in my signature render?

FileIOSurrogate.exe suggests an issue with the QuickTime 32-bit plugin? What media are you using exactly?

 

I'm using an .mp4 file that I recorded. Of my screen. It's an instant replay made with AMD

Try disabling Quicktime under preferences/ deprecated features. For this media try re-encoding with https://www.shutterencoder.com/ to output codec h264 and see if it works to render to MagixAVC.

Another user had same issue and found this worked for him:

For me VEGAS Pro 20.0 also crashed everytime I clicked "Render as..." and the fault process details also featured FileIOSurrogate.exe. I was able to fix my problem by changing the settings of the executable File I/O Surrogate.exe such that it is always being run as admin.

That is actually strange, when I just started Vegas it offered me run as admin then I opened my project and rendered -- everything was fine, after that I merely opened a project -- it didn't run as admin and I had a frozen video rendering. Maybe it is the solution for many of people with rendering problem. I will try it tomorrow.

@Kou3 That possibly suggests a permissions problem,

Google - Administrators have the highest level of access to an account. If you want to be one for an account, you can reach out to the Admin of the account. A general user will have limited access to the account as per the permissions given by the Admin.

Try having a look at the permissions of your media & folders, Right click - Properties - Security, or try changing your account n see

1. How to Change Administrator via Control Panel
2. First, type Control Panel in the Windows search bar.
3. Click on the app in the search results.
4. Then click on Change account type under the User Accounts section.
5. Click on the user that you want to change.
6. Then choose Change the account type.

@Kou3 That possibly suggests a permissions problem,

I know how to be a root/admin. :)
I said it would be good for FAQ: you should run the programme as an admin to render videos properly/ without freezes or something like that.

@Demontera Try using the Batch render script (Tools > Scripting > Batch Render), and see if you are then able to do your renders.

Hello everyone. Thank you for all your answers, sadly I have yet not been able to fix it. I've run through everything in this forum but the same error persists. My Vegas 14.0 works perfectly fine, so I'll just use that for now, but it's disheartening that my Vegas 18.0 does not render. It works fine otherwise. :(

Try this... open a new project. Go into the media generators tab of VEGAS, and drop any piece of media in there (checkerboard, etc) onto the timeline. Click Render As... does it let you render?

If you have success there, then cancel the render, and open one of your projects. Try to click Render As now... does that work?

On my system, if I don't do this trick first of clicking render as on an empty project with a piece of generated media on the timeline, it can often crash. Hopefully that helps.

Another user had same issue and found this worked for him:

For me VEGAS Pro 20.0 also crashed everytime I clicked "Render as..." and the fault process details also featured FileIOSurrogate.exe. I was able to fix my problem by changing the settings of the executable File I/O Surrogate.exe such that it is always being run as admin.

That is actually strange, when I just started Vegas it offered me run as admin then I opened my project and rendered -- everything was fine, after that I merely opened a project -- it didn't run as admin and I had a frozen video rendering. Maybe it is the solution for many of people with rendering problem. I will try it tomorrow.

Admin privileges didn't help, although I rendered 5 small pieces instead of one big, and rendered a problem moment (45 sec) without any problem. I believe the problem was with a media file, and not with a Vegas itself. All others projects rendered nice and smooth.