VST plugin error (Access violation at address 004F4D4A in module)

SpartaYoshi wrote on 2/16/2019, 3:58 AM

Okay so I recently upgraded from Vegas Pro 14 to 15, and ever since I upgraded, I have encountered many problems.

This problem is the weirdest and the most annoying one. I have never had this error in Vegas Pro 14 plus i've always used the same VST plugin for VP 13 and 14. It's called "You Wa Shock!", made in 2007. It basically improves the bass in audios.

The weirdest thing about this error is that there is kind of like a 70% chance I get this error when I boot the program. There's occassions when the vst plugin boots correctly and works fine, like nothing ever happened, until I reboot the program, which leads back to the 70% chance thing.

I've been looking for a solution for 3 days with no success whatsoever. That is why i'm seeking help in this forum.

Things i've tried:
- Reinstalling program (3 times)

- Clearing all cache (lost count, more than 15 times maybe)

- Reinstalling VST plugin (lost count too, probably twice as much as clearing cache)

- Windows system scan (to fix corrupted system files)

- Changed compatibility on the properties of the exe file.

- Tried on another computer (SAME error, so i'm guessing it's whether within Vegas Pro 15 or Win10. Like I said, VP14 never had this issue)

- Replaced sfvstserver.exe from VP15 to the VP14 version.

- Updated VP15 to latest build (416)

I don't know if the things i've tried have influenced in some way so that the error wouldn't happen, but I don't know at this point.

SPECS:

Windows 10 x64 bits

RAM: 8GB

Intel Core i5-4460 CPU @ 3.20GHz

120GB SSD card

GPU: NVIDIA GeForce GTX 1050Ti

Vegas Pro 15.0 (build 177)

Comments

vkmast wrote on 2/16/2019, 4:16 AM

Have you tried updating to the last build?

https://www.vegascreativesoftware.info/us/forum/vegas-pro-15-update-8-build-416--113806/

SpartaYoshi wrote on 2/16/2019, 9:40 AM

Have you tried updating to the last build?

https://www.vegascreativesoftware.info/us/forum/vegas-pro-15-update-8-build-416--113806/

I just updated it to the latest build. Error still pops up :(

rraud wrote on 2/17/2019, 10:59 AM

When you uninstalled (prior to reinstalling), did you use a third-party uninstaller? The built-in Windows uninstaller leaves many of the problem causing registry entries behind. I usually use the Revo Uninstaller which can remove the leftover reg entries.

SpartaYoshi wrote on 2/17/2019, 11:04 AM

When you uninstalled (prior to reinstalling), did you use a third-party uninstaller? The built-in Windows uninstaller leaves many of the problem causing registry entries behind. I usually use the Revo Uninstaller which can remove the leftover reg entries.

I did use Revo Uninstaller as well as deleting leftover reg entries

j-v wrote on 2/17/2019, 11:26 AM

What is your selected audiodevice in Options/Preferences?

SpartaYoshi wrote on 2/17/2019, 11:37 AM

What is your selected audiodevice in Options/Preferences?

Default one (Microsoft Sound Mapper)

j-v wrote on 2/17/2019, 12:36 PM

Did you try another one that is listed there, it solved with me some issues with the latest Windows 10 update.

rraud wrote on 2/17/2019, 2:43 PM

Yes, try the 'Windows Classic Wave Driver' in "Options> Preferences> Audio Device"

SpartaYoshi wrote on 2/22/2019, 3:36 PM

Yes, try the 'Windows Classic Wave Driver' in "Options> Preferences> Audio Device"

Did you try another one that is listed there, it solved with me some issues with the latest Windows 10 update.

None of the rest of the audio devices worked. Apparently i have this error too on sony vegas pro 14

Zaither-P wrote on 3/1/2019, 9:11 AM

Vegas' VST support just be like that.

AlexsMidis wrote on 6/19/2020, 10:04 PM

Don't Worry. Its Just YWS. The plugin was made weirdly and also does that sometimes in FL studio