Can you obtain any clue as to just why Vegas stops responding? Is is a memory handling problem/leak? As most of my stop responding issues (V20/214) seem to be non immediately repeatable - repeat the same action and Vegas is OK until some other action crashes it again.
Since I started logging, I haven't had an interruption to my Vegas work. These events were all in the background to my other tasks. Still, I can't imagine getting six of these events are a good thing...
Source
VST Server
Summary
Stopped working
Date
11/3/2022 10:33 PM
Status
Report sent
Description
Faulting Application Path: C:\Program Files\VEGAS\VEGAS Pro 19.0\x86\sfvstserver.exe
Problem signature
Problem Event Name: APPCRASH
Application Name: sfvstserver.exe
Application Version: 19.0.0.643
Application Timestamp: 62a92692
Fault Module Name: KERNELBASE.dll
Fault Module Version: 10.0.19041.2130
Fault Module Timestamp: 3206f737
Exception Code: e0000001
Exception Offset: 0012df72
OS Version: 10.0.19045.2.0.0.256.48
Locale ID: 1033
Additional Information 1: e63f
Additional Information 2: e63fdc397cb77548c735d9e70192c7a2
Additional Information 3: e28b
Additional Information 4: e28ba84e5a0968370a6bc162a6c443df
Extra information about the problem
Bucket ID: bc39108cb2ed818bf5a9caa942de86af (1561001574180751023)
I haven't gotten any insight into the reason for the hangs that caused me to have to close Vegas in the Task Manager.
I did notice one thing a short while back, windows would give the Vegas is not responding message but it was Vegas doing something that was taking a tad longer, it eventually came back and continued normally.
Used Vegas Video Driver Update to download and install Radeon Adrenalin 22.5.1.
are you saying you downloaded that and your problems went away? or are you just noting which version you're currently running and still having issues?
Your thread caught my eye, as my Dell laptop crashes regularly during our edit lately, and I installed the "studio/creative" NVIDIA 3070ti laptop driver hoping it would help, but don't see a noteable difference :( (the release notes on that driver specifically mentioned Magix Vegas Pro)
Just loaded the version that was offered as a data point after reading of color distortion with some versions on some hardware. I passed on the Optional version.
I cleared the logs. This may be a thought experiment.
Just loaded the version that was offered as a data point after reading of color distortion with some versions on some hardware. I passed on the Optional version.
I cleared the logs. This may be a thought experiment.
Oh -- I was one of those users who had color issues several months back after installing a Radeon driver for my RX470 and indeed it resolved with a driver update (or roll-back.. don't recall which).
Gained some insight on the APPCRASH: sfvstserver.exe that fails in the background and sends reports but doesn't seem to affect anything that I'm doing with Vegas Pro 19-643.
Source
VST Server
Summary
Stopped working
Date
11/21/2022 4:01 PM
Status
Report sent
Description
Faulting Application Path: C:\Program Files\VEGAS\VEGAS Pro 19.0\x86\sfvstserver.exe
Problem signature
Problem Event Name: APPCRASH
Application Name: sfvstserver.exe
Application Version: 19.0.0.643
Application Timestamp: 62a92692
Fault Module Name: KERNELBASE.dll
Fault Module Version: 10.0.19041.2251
Fault Module Timestamp: 0d929ca0
Exception Code: e0000001
Exception Offset: 0012e062
OS Version: 10.0.19045.2.0.0.256.48
Locale ID: 1033
Additional Information 1: e63f
Additional Information 2: e63fdc397cb77548c735d9e70192c7a2
Additional Information 3: 53a4
Additional Information 4: 53a464fda6a8c1eb181d80597ea9deb7
Extra information about the problem
Bucket ID: 6854da0978c0efc2628d0702976d0bdc (1336732372110740444)
"Yes, but Peter explained what it was. This is a process that checks your VST’s. Before Sony started using this, if a VST was bad, it would hang Vegas or ACID. Now that they use a separate process to check VST’s, it can only hang that process and not Vegas. I’m guessing that you may have a bad VST which is causing this window to show when it should not have.
~jr"
In my case this Windows 10 system image and Vegas Pro 19-643 installation is out of the box and is very minimalist. I am working with projects from 2020, though.
I have no clue what Vegas might be looking for when sfvstserver.exe crashes.
2022-12-01 Was moving XAVC-S 1920x1080 files around on a simple timeline to recreate a transition for another Vegas user when I was greeted with this:
Details:
Source
VEGAS Pro
Summary
Stopped responding and was closed
Date
12/1/2022 7:28 AM
Status
Report sent
Description
A problem caused this program to stop interacting with Windows.
Faulting Application Path: C:\Program Files\VEGAS\VEGAS Pro 19.0\vegas190.exe
Problem signature
Problem Event Name: AppHangB1
Application Name: vegas190.exe
Application Version: 19.0.0.643
Application Timestamp: 62a9244f
Hang Signature: b992
Hang Type: 134217728
OS Version: 10.0.19045.2.0.0.256.48
Locale ID: 1033
Additional Hang Signature 1: b9926a173b538d410fc020714b9dd9ff
Additional Hang Signature 2: cc9a
Additional Hang Signature 3: cc9a2d52f7a96e640f1bb6880874a86b
Additional Hang Signature 4: b992
Additional Hang Signature 5: b9926a173b538d410fc020714b9dd9ff
Additional Hang Signature 6: cc9a
Additional Hang Signature 7: cc9a2d52f7a96e640f1bb6880874a86b
Extra information about the problem
Bucket ID: b6c8cd505d8dd1fcecc145c4165ff85d (2072014012058433629)
Source
VEGAS Pro
Summary
Stopped working
Date
12/1/2022 7:54 AM
Status
Report sent
Description
Faulting Application Path: C:\Program Files\VEGAS\VEGAS Pro 19.0\vegas190.exe
Problem signature
Problem Event Name: BEX64
Application Name: vegas190.exe
Application Version: 19.0.0.643
Application Timestamp: 62a9244f
Fault Module Name: amdocl64.dll
Fault Module Version: 10.0.3380.6
Fault Module Timestamp: 626a488d
Exception Offset: 000000000185aeb9
Exception Code: c0000409
Exception Data: 0000000000000007
OS Version: 10.0.19045.2.0.0.256.48
Locale ID: 1033
Additional Information 1: 5325
Additional Information 2: 532546d87b12fd7e7fdb793c671d54e6
Additional Information 3: f596
Additional Information 4: f5961c375ee52866b0a3ff561b7fbecc
Extra information about the problem
Bucket ID: b0a0184e7cc370c4ed585af7e25e9fc6 (2114540045751721926)
@john_dennis, curious. Do you think it's because of the video format you are using that is causing all of these issues? Working with "generic" MP4, or HEVC, does this also happen?
Side note: much appreciate your videos and sense of humor in the forum. It lightens what can be a stress inducing situation for some.
@Reyfox said, "Do you think it's because of the video format you are using that is causing all of these issues? Working with "generic" MP4, or HEVC, does this also happen?"
I'm uncertain if media is the primary source or even a factor in any of the Vegas Pro issues. If it is, there must be tens of millions of Sony camera users that have the potential for similar issues.
@john_dennis the reason for me asking about what type of footage you are using, I shoot with Panasonic and haven't experienced (at least as not to any great extent) what you have.
You posts have been informative, especially the videos, and your "humor" is brilliant, at least to me.
2022-06-19 Didn't finish my first cup of coffee. First file I explored from 2006.
Source
VEGAS Pro
Summary
Stopped responding and was closed
Date
12/3/2022 6:11 AM
Status
Report sent
Description
A problem caused this program to stop interacting with Windows.
Faulting Application Path: C:\Program Files\VEGAS\VEGAS Pro 19.0\vegas190.exe
Problem signature
Problem Event Name: AppHangB1
Application Name: vegas190.exe
Application Version: 19.0.0.643
Application Timestamp: 62a9244f
Hang Signature: a03e
Hang Type: 134217730
OS Version: 10.0.19045.2.0.0.256.48
Locale ID: 1033
Additional Hang Signature 1: a03e0e46e2cab71af5c0cdf973687435
Additional Hang Signature 2: 589f
Additional Hang Signature 3: 589f613978970beb0a3a2e5391c37b70
Additional Hang Signature 4: 31e1
Additional Hang Signature 5: 31e1ed7a27763fee8665ef20bd868a1b
Additional Hang Signature 6: d70a
Additional Hang Signature 7: d70af410e98db5c56238b1c3a64be775
Extra information about the problem
Bucket ID: 287007fa1f404970aa606dcfc8917f34 (1900639781940985652)
Solution
I installed Quicktime on the system and enabled in Vegas Pro 19-643 Options/Preferences/Deprecated Features/Enable the Quicktime Plugin.
2023-01-01 My first hang of the new year. I trimmed some crowd scenes in the Trimmer and pasted video only into a track above the main track. On adjusting the length of the top track, Vegas "went South". On restarting Vegas Pro, I hadn't lost any steps. I was somewhat reluctant to save the recovered file to the project out of concern for project corruption. We'll see.
Source
VEGAS Pro
Summary
Stopped responding and was closed
Date
1/1/2023 8:09 AM
Status
Report sent
Description
A problem caused this program to stop interacting with Windows.
Faulting Application Path: C:\Program Files\VEGAS\VEGAS Pro 19.0\vegas190.exe
Problem signature
Problem Event Name: AppHangB1
Application Name: vegas190.exe
Application Version: 19.0.0.648
Application Timestamp: 63915e2f
Hang Signature: e866
Hang Type: 134217728
OS Version: 10.0.19045.2.0.0.256.48
Locale ID: 1033
Additional Hang Signature 1: e866ab07e28a7c3106d26767d9e524b5
Additional Hang Signature 2: d4eb
Additional Hang Signature 3: d4eb1dc0f972d51f2f9eda7a2fd4f401
Additional Hang Signature 4: e866
Additional Hang Signature 5: e866ab07e28a7c3106d26767d9e524b5
Additional Hang Signature 6: d4eb
Additional Hang Signature 7: d4eb1dc0f972d51f2f9eda7a2fd4f401
Extra information about the problem
Bucket ID: 94b6169f38e13635fa07d61c211b10d8 (1875703186125951192)
2023-01-02 While editing this morning I had no interruptions to my progress. Looking at Reliability History, I found nine events logged that either were recoverable or otherwise had no effect on what I was doing.
Source
VEGAS Pro
Summary
Stopped working
Date
1/2/2023 7:35 AM
Status
Report sent
Description
Faulting Application Path: C:\Program Files\VEGAS\VEGAS Pro 19.0\vegas190.exe
Problem signature
Problem Event Name: BEX64
Application Name: vegas190.exe
Application Version: 19.0.0.648
Application Timestamp: 63915e2f
Fault Module Name: amdocl64.dll
Fault Module Version: 31.0.12027.7000
Fault Module Timestamp: 6351b8ba
Exception Offset: 00000000003a8d5d
Exception Code: c0000409
Exception Data: 0000000000000007
OS Version: 10.0.19045.2.0.0.256.48
Locale ID: 1033
Additional Information 1: 5325
Additional Information 2: 532546d87b12fd7e7fdb793c671d54e6
Additional Information 3: 8949
Additional Information 4: 8949bd2e55f8ca30eaf5a849a208bf1e
Extra information about the problem
Bucket ID: 93ac553f4375bb1a99360a2541f02b92 (1816650654826900370)
Personally, I'm sick of chasing drivers for a GPU that I don't use for decoding, timeline acceleration or rendering for my current work. As long as these events don't stop my work, Windows can continue to write them into the log. 99.938476% of PC users on the planet never look at Reliability History or the Windows Event Viewer. Many of them live happy, contented lives in their quest to become Tik-Tok "influencers".