Problem: Vegas Pro 16 Has stopped working while rendering

RetroMyth wrote on 4/10/2020, 5:24 AM

I have a GTX 1050 TI, Intel Core I5-4590 and 16 gb of ram ddr3. I try to render a video, and after a while it randomly crashes. Another bug is that one of the tracks on Vegas just doesn't show, it's all black. Problem details:

Application Version: Version 16.0 (Build 248)
Problem: Unmanaged Exception (0xc0000005)
Fault Module: D:\Vegas Pro 16\OFX Video Plug-Ins\Vfx1.ofx.bundle\Contents\Win64\Vfx1.ofx
Fault Address: 0x00007FFAE28EC4A0
Fault Offset: 0x00000000006EC4A0

Fault Process Details
Process Path: D:\Vegas Pro 16\vegas160.exe
Process Version: Version 16.0 (Build 248)
Process Description: VEGAS Pro

Comments

j-v wrote on 4/10/2020, 5:50 AM

Better to upgrade to build 424, the latest and delete your older Vegas Pro 16 first.
After a restart don't install the latest build on your D drive but on the C/: where also windows has to be installed. Vegas likes that also to provide conflicts as you have now.

RetroMyth wrote on 4/10/2020, 7:52 AM

Better to upgrade to build 424, the latest and delete your older Vegas Pro 16 first.
After a restart don't install the latest build on your D drive but on the C/: where also windows has to be installed. Vegas likes that also to provide conflicts as you have now.

i did what you said but it still doesn't work :/

j-v wrote on 4/10/2020, 8:05 AM

The same error message?

RetroMyth wrote on 4/10/2020, 8:08 AM

The same error message?

Yup

j-v wrote on 4/10/2020, 8:44 AM

My last known possibilty:
From the message it looks that something is wrong with your installed OFX effects. Which one it could be, you must find out yourself.
First step is make them invisible for the program by renaming this map on your hardware : C:\Program Files\VEGAS\VEGAS Pro 16.0\FileIO Plug-Ins to
C:\Program Files\VEGAS\VEGAS Pro 16.0\OLDFileIO Plug-Ins.
When most of your problems are gone exept messages of missing FX's you have to give that map its old name back and search which FX is causing the problems.

RetroMyth wrote on 4/10/2020, 8:48 AM

My last known possibilty:
From the message it looks that something is wrong with your installed OFX effects. Which one it could be, you must find out yourself.
First step is make them invisible for the program by renaming this map on your hardware : C:\Program Files\VEGAS\VEGAS Pro 16.0\FileIO Plug-Ins to
C:\Program Files\VEGAS\VEGAS Pro 16.0\OLDFileIO Plug-Ins.
When most of your problems are gone exept messages of missing FX's you have to give that map its old name back and search which FX is causing the problems.

that might be it, thx!

VEGASDerek wrote on 4/10/2020, 9:12 AM

Looks as if this installation is improper. Please uninstall, download the most recent version from VEGAS Creative Software, reinstall the product and enter your serial number after installing.

RetroMyth wrote on 4/11/2020, 7:16 AM

My last known possibilty:
From the message it looks that something is wrong with your installed OFX effects. Which one it could be, you must find out yourself.
First step is make them invisible for the program by renaming this map on your hardware : C:\Program Files\VEGAS\VEGAS Pro 16.0\FileIO Plug-Ins to
C:\Program Files\VEGAS\VEGAS Pro 16.0\OLDFileIO Plug-Ins.
When most of your problems are gone exept messages of missing FX's you have to give that map its old name back and search which FX is causing the problems.

That was the problem, thank you!

RetroMyth wrote on 4/11/2020, 11:54 AM

Looks as if this installation is improper. Please uninstall, download the most recent version from VEGAS Creative Software, reinstall the product and enter your serial number after installing.

No, it couldn't be it, as this problem has never happened before

RetroMyth wrote on 4/11/2020, 11:56 AM

My last known possibilty:
From the message it looks that something is wrong with your installed OFX effects. Which one it could be, you must find out yourself.
First step is make them invisible for the program by renaming this map on your hardware : C:\Program Files\VEGAS\VEGAS Pro 16.0\FileIO Plug-Ins to
C:\Program Files\VEGAS\VEGAS Pro 16.0\OLDFileIO Plug-Ins.
When most of your problems are gone exept messages of missing FX's you have to give that map its old name back and search which FX is causing the problems.

Nevermind, it didn't work. I downgraded to Vegas 14, reinstalled the FX, remade my project, still, the problem was there. I renamed the files to OLDFileIO Plug-Ins, but when I try to open my project, it says that I can no longer open it. When I change it to FileIO Plug-Ins however, I can open it

RetroMyth wrote on 4/11/2020, 12:02 PM

My last known possibilty:
From the message it looks that something is wrong with your installed OFX effects. Which one it could be, you must find out yourself.
First step is make them invisible for the program by renaming this map on your hardware : C:\Program Files\VEGAS\VEGAS Pro 16.0\FileIO Plug-Ins to
C:\Program Files\VEGAS\VEGAS Pro 16.0\OLDFileIO Plug-Ins.
When most of your problems are gone exept messages of missing FX's you have to give that map its old name back and search which FX is causing the problems.

Nevermind, it didn't work. I downgraded to Vegas 14, reinstalled the FX, remade my project, still, the problem was there. I renamed the files to OLDFileIO Plug-Ins, but when I try to open my project, it says that I can no longer open it. When I change it to FileIO Plug-Ins however, I can open it

I tried the same thing even in Vegas 16

j-v wrote on 4/11/2020, 12:08 PM

Did you already tried to reset build 424 of VPro 17?

RetroMyth wrote on 4/11/2020, 12:11 PM

Did you already tried to reset build 424 of VPro 17?

Ye I also did that, but I think that I've got something here. So the project was a gameplay video, and I had an introduction of text with s_shake popping out of the screen. When I removed them, the video is now rendering perfectly fine, instead of crashing at like 2-3% and now it's at like 10%.

RetroMyth wrote on 4/11/2020, 12:15 PM

AND this time I turned off GPU acceleration, keep in mind that when I had GPU acceleration off but with the text, it crashed.