My Running Log of Vegas Pro Service Interruptions
Back to post
Comments
john_dennis
wrote on 1/29/2023, 6:17 PM
2023-01-9
I experienced my first Vegas Pro "Not Responding" event in some weeks just now. This one affected my work.
GPU Options
Source VEGAS Pro Summary Stopped working Date 1/29/2023 4:01 PM 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)
Source VST Server Summary Stopped working Date 1/29/2023 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.648 Application Timestamp: 63916045 Fault Module Name: KERNELBASE.dll Fault Module Version: 10.0.19041.2486 Fault Module Timestamp: ca518c9d Exception Code: e0000001 Exception Offset: 0012e292 OS Version: 10.0.19045.2.0.0.256.48 Locale ID: 1033 Additional Information 1: e63f Additional Information 2: e63fdc397cb77548c735d9e70192c7a2 Additional Information 3: 3e2c Additional Information 4: 3e2c5e2ec9754f59c451f088aef138fb Extra information about the problem Bucket ID: 812fe047bd9d4af35198ff282486a70b (1268043842981373707)
Source VEGAS Pro Summary Stopped working Date 1/29/2023 4:01 PM 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)
relaxvideo
wrote on 1/29/2023, 11:46 PM
Lucky man.
This clearly confirm, that the issue is NOT because of gpu decoding AND V19 b648 is still not stable, right?
Grazie
wrote on 1/29/2023, 11:49 PM
99.938476% of PC users on the planet never look at or the Windows Event Viewer. Many of them live happy, contented lives in their quest to become Tik-Tok "influencers".
@john_dennis - Thanks John! Can I add being a Tik-Tok "influencers" to my CV? Can I? . . Can I? I just looked at my Reliability History - I'm too embarrassed to share it here - nasty!
(NB: Eh..What're Tik-Tok "influencers".)
Reyfox
wrote on 1/30/2023, 5:07 AM
@relaxvideo wrote:
Lucky man.
This clearly confirm, that the issue is NOT because of gpu decoding AND V19 b648 is still not stable, right?
Let's see.... @john_dennis said this problem is the first one he has experienced in some weeks, and you come back with that VP19 is not stable? Really??
relaxvideo
wrote on 1/30/2023, 5:52 AM
Yes, really.
"Application Name: vegas190.exe"
Reyfox
wrote on 1/30/2023, 6:06 AM
So the software, after weeks of use has a crash, and you hang your hat on that. As if there is a perfect editing software where there are zero problems with it. I would love to know the name of it and if it is comparable to Vegas....
Do I want a "perfect", trouble free editor? Yes!!!! But even the OS you and I are using isn't bug free. I have no software on my computer that is as complex as Vegas Pro (including the much vaunted Resolve Studio) that has not crashed or had an issue.
VP19 I don't think will be patched much more. They've admitted that they will now spend more time with QC before releasing any further patches for VP20. That still doesn't mean it will be 100% bug free.
relaxvideo
wrote on 1/30/2023, 6:56 AM
Yes, by some users, like me, crash or not responde more often than by others.
Too bad we cannot have more V19 release :(
Dont get me wrong, i dont say every app is 100% bugfree, but there are difference between small bugs, which doesnt affect editing work much, and big errors, which does make headaches to the end users.
(just my opinion)
Reyfox
wrote on 1/30/2023, 7:56 AM
@relaxvideo understand. It is your personal experience. But it's not everyone's personal experience. I feel for those that have problems that impede their editing experience.
Getting software to work on the infinite variable number of computer configurations is a monumental task. Where it should work reliably is on a fresh install of OS and all necessary drivers (motherboard chipset, etc). What I would like to know out of curiosity is the configuration of the developers computers and what additional software they have installed. Most users have a plethora of software/drivers/hardware on their computer that can affect software.
john_dennis
wrote on 1/30/2023, 9:00 AM
If you have a current CV, by all means add TikTok influencer to it. I stopped updating mine.
john_dennis
wrote on 1/30/2023, 9:10 AM
The rationale behind my posting details of my Vegas Pro service interruptions is that the data is more scientific than anecdotal about what was going on in the machine when I was interrupted.
When posted in a code block here, it's searchable by anyone on the Internet, unlike the crash report that is sent off to Microsoft and/or Magix.
Reyfox
wrote on 1/30/2023, 12:48 PM
@john_dennis, I hope that all that you post is taken into consideration by the Vegas team. I look through the reliability once a week to see what has happened on my computer.
Do you think this is something that everyone should do along with explaining how/when it happened?
Since I am moving my software to a new install of Win11, I haven't used Vegas much other than to install and make sure it is running.
john_dennis
wrote on 1/31/2023, 8:31 AM
@Reyfox said "Do you think this is something that everyone should do along with explaining how/when it happened?"
I think most people should look at Reliability History periodically, especially when they might be having an issue with their system. Most people won't know how to interpret the entries, including me, but the data could provide clues. At a minimum, the data can be searched on the Internet for more clues. Having a log of what actually happened when Vegas Pro hung or crashed is far superior to saying:
"I was working along using media that I've always used, on a system that has never changed when Vegas stopped working. I'm so frustrated 'cause I've got a deadline and Vegas sucks!"
Notice I didn't recommend that everyone on the planet scroll through the Windows Event Logs. Though it could be useful, many people reach data overload there too quickly.