Vegas Pro 20 - error occurs when clicking the Render button

Chaily wrote on 12/17/2023, 9:44 AM

Can anyone help? I believe my computer pretty decent, but when I tried Vegas Pro 18 and 20, it crashesh as soon as I press the Render icon. Such a glich never happened when using Vegas Pro 14.

My PC specs:
- Intel Core i9-12900K
- 128GB RAM
- NVIDIA GeForce RTX 3070 Ti

Trouble shoot info:

Problem Description
Application Name: VEGAS Pro
Application Version: Version 20.0 (Build 411)
Problem: Unmanaged Exception (0x40010006)
Fault Module: C:\WINDOWS\SYSTEM32\ntdll.dll
Fault Address: 0x000000007743FB3D
Fault Offset: 0x000000000009FB3D

Fault Process Details
Process Path: C:\Program Files\VEGAS\VEGAS Pro 20.0\x86\FileIOSurrogate.exe
Process Version: Version 20.0 (Build 411)
Process Description: File I/O surrogate (not visible)
Process Image Date: 2023-06-12 (Mon Jun 12) 11:32:58

Comments

Jack S wrote on 12/17/2023, 10:50 AM

@Chaily ntdll.dll is a Windows system file. Do a Google search on ntdll.dll to find advice on how to solve the problem.

andyrpsmith wrote on 12/17/2023, 2:34 PM

Have you installed the correct deep learning files?

Chaily wrote on 12/17/2023, 3:24 PM

I accidentally found a user's recommendation on checking on properities of the "Surrogate" file, and the crash stopped. Well, that's wierd.

David-Williamson wrote on 4/12/2024, 4:00 PM

I also stumbled upon this also, and for Vegas Pro 21, setting the FileIOSurrogate to run as admin fixed it for me. Quite ridiculous that this kind of workaround is required for a program that we're paying for and is *supposed* to be a professional program...things got far worse when Magix took over.

Steve_Rhoden wrote on 4/13/2024, 2:58 AM

@David-Williamson Things did not get far worse when Magix took over, quite the opposite, they saved Vegas and improved it dramatically, taking it far beyond the stagnant path Sony had it on

JHomer wrote on 5/7/2024, 11:52 PM

I also stumbled upon this also, and for Vegas Pro 21, setting the FileIOSurrogate to run as admin fixed it for me. Quite ridiculous that this kind of workaround is required for a program that we're paying for and is *supposed* to be a professional program...things got far worse when Magix took over.

This fixed my program but my problem was on launch of the application after updating to the latest Pro v21 (build 300). Changed FileIOSurrogate to run as administrator and program launches. Anyone have an explanation why this fix is required? I uninstalled and installed as admin to see if that would change the default run status. Still had to change the file property to run the program.

JHomer wrote on 9/17/2024, 11:38 PM

UPDATE: I figured I'd update my comment as I found another approach for this that I can't explain. After installing VegasPro 22 I got the same error message. My error message was:

Problem Description
Application Name: VEGAS Pro
Application Version: Version 22.0 (Build 122)
Problem: Unmanaged Exception (0x40010006)
Fault Module: C:\Windows\SYSTEM32\ntdll.dll
Fault Address: 0x0000000077CD083D
Fault Offset: 0x00000000000A083D

Fault Process Details
Process Path: C:\Program Files\VEGAS\VEGAS Pro 22.0\x86\FileIOSurrogate.exe
Process Version: Unknown
Process Description: Unknown
Process Image Date: 2024-08-17 (Sat Aug 17) 06:16:18

After searching online I was more confused as there seemed to be all kinds of suggestions going back many versions of VP. I decided it wouldn't hurt to rename FileIOSurrogate.exe to FileIOSurrogate2.exe and try launching VP22. Surprisingly it launched just fine. Concerned that FileIOSurrogate.exe was required for loading certain file times (32bit .mov... etc) I renamed it back to it's original name. I rebooted my machine and tested VP22. Now VegasPro22 seems to start-up without any issues. I haven't opened any former projects or created a new project yet but I can now at least start the application.

So without changing the properties of FileIOSurrogate to run as administrator I was able to resolve this issue by changing the name to something new starting VP22, exiting VP22, and changing the file's name back to the original name.