Come on Vegas... give us a break. Fix this constant "Not Responding" issue we've been dealing with for years and years now. It's the only program on my computer that crashes and it does it constantly. I'm soooo tired of having to ctrl.alt.del and start it up over and over and over again during an editing session.
If you want to express your frustration, you've done that.
If you want mere mortal users to help you to the extent that we can, do this...
Hi John, Didn't know that even existed. I appreciate your response.
Here is one of them.
Description
Faulting Application Path: C:\Program Files\VEGAS\VEGAS Pro 21.0\vegas210.exe
Problem signature
Problem Event Name: BEX64
Application Name: vegas210.exe
Application Version: 21.0.0.108
Application Timestamp: 64d189ec
Fault Module Name: ucrtbase.dll
Fault Module Version: 10.0.19041.789
Fault Module Timestamp: 2bd748bf
Exception Offset: 000000000007286e
Exception Code: c0000409
Exception Data: 0000000000000007
OS Version: 10.0.19045.2.0.0.256.48
Locale ID: 1033
Additional Information 1: ad90
Additional Information 2: ad90f168ed2990d0df3e842880afdf8f
Additional Information 3: d805
Additional Information 4: d8057f6f700b2a672f5935e715916df5
Extra information about the problem
Bucket ID: 5d554351fd3ac0ac952d227f94dec548 (1525913780102284616)
===========================================
Well, after opening Vegas again, this happened making the entire project no good. Even the .bak file won't work. Fortunately I have the project on a second drive so I am safe but it shouldn't be this way. This is ridiculous that we have to keep going through this all the time.
I don't remember the last time (or if I ever lost a project file) but I have resorted to this when I really felt under the gun.
Are, were your project files on a local disk as opposed to a USB or network attached disk?
I didn't know about this either. Here's one of my recent crashes.
Source
VEGAS Pro
Summary
Stopped responding and was closed
Date
9/29/2023 6:31 PM
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.651
Application Timestamp: 64539a48
Hang Signature: d90d
Hang Type: 134217728
OS Version: 10.0.19045.2.0.0.768.101
Locale ID: 1033
Additional Hang Signature 1: d90dff83644e053effe9185762f95dca
Additional Hang Signature 2: 87d9
Additional Hang Signature 3: 87d9fd68d37deaebe06f40f40ef6c0a6
Additional Hang Signature 4: d90d
Additional Hang Signature 5: d90dff83644e053effe9185762f95dca
Additional Hang Signature 6: 87d9
Additional Hang Signature 7: 87d9fd68d37deaebe06f40f40ef6c0a6
Extra information about the problem
Bucket ID: c0d8107a878ca1870224c134b715d40d (1307382223998407693)
Crash, crash and crash everywhere.
Without question, i don't like to see any new features at all until this is not fixed!
If you want to express your frustration, you've done that.
If you want mere mortal users to help you to the extent that we can, do this...
I don't remember the last time (or if I ever lost a project file) but I have resorted to this when I really felt under the gun.
Are, were your project files on a local disk as opposed to a USB or network attached disk?
They were on a 4 TB external HD.
Crash, crash and crash everywhere.
Without question, i don't like to see any new features at all until this is not fixed!
Yes, I agree. Don't need the mesh warp and some of those things and I know I'm complaining but the not responding thing has simply been happening for way too long. I'm beginning to think the US congress is running Vegas. Vegas, do your job. Sorry to be so negativity but it's really been far too long for this crash stuff to keep happening.
There are many reasons VEGAS crashes and while the symptom is the same that doesn't tell us the cause. Xberk and Roger's crashes have different causes according to the reports above, and probably different hardware and media (though those weren't specified).
If you want to help the devs get to the bottom of it, submit the crash reports, include your email, and link back to the forum if you made a thread about it.
As far as what we can do here, if you have a problem that you can explain and get others here to replicate it will get fixed much faster. I'm always happy to test projects, media, etc. and many others here are willing to do the same.
Sure I'd like all the crashing and instability to disappear but it doesn't seem that will happen without us playing an active role.
There are many reasons VEGAS crashes and while the symptom is the same that doesn't tell us the cause. Xberk and Roger's crashes have different causes according to the reports above, and probably different hardware and media (though those weren't specified).
If you want to help the devs get to the bottom of it, submit the crash reports, include your email, and link back to the forum if you made a thread about it.
As far as what we can do here, if you have a problem that you can explain and get others here to replicate it will get fixed much faster. I'm always happy to test projects, media, etc. and many others here are willing to do the same.
Sure I'd like all the crashing and instability to disappear but it doesn't seem that will happen without us playing an active role.
Most of the time I get the "not responding" the report box does not come up even after waiting a while. It's just locked so then the only option is to restart the program. Sometimes the report to Vegas box does appear and I often report the crash but then again if I were to do that every time it would just take that much time out ofwhat is already frustrating. Seems like all those reports in the past haven't done much good as Ive been clicking and submitting those crash reports for years and years now.
The Shade Tree Diagnostician responds:
Here is a BEX64 which was one of five that went to Reliability History on my machine yesterday.
Source VEGAS Pro Summary Stopped working Date 9/30/2023 8:10 PM Status Report sent Description Faulting Application Path: C:\Program Files\VEGAS\VEGAS Pro 21.0\vegas210.exe Problem signature Problem Event Name: BEX64 Application Name: vegas210.exe Application Version: 21.0.0.108 Application Timestamp: 64d189ec Fault Module Name: libmfx64-gen.dll Fault Module Version: 23.6.12.3975 Fault Module Timestamp: 6486c4e1 Exception Offset: 0000000000977c15 Exception Code: c0000409 Exception Data: 0000000000000007 OS Version: 10.0.19045.2.0.0.256.48 Locale ID: 1033 Additional Information 1: 18dc Additional Information 2: 18dcb70360839c50decc4b476d565433 Additional Information 3: 2335 Additional Information 4: 23350ec6eb4e69541a3dab7c5bca42b3 Extra information about the problem Bucket ID: 2e21027929a1f6b53205114e12d90860 (1298463094587590752)
It appears to have a different source .dll than yours. Yours was Fault Module Name: ucrtbase.dll, but likely the effect on the workflow was similar.
The Shade Tree Diagnostician responds:
Here is a BEX64 which was one of five that went to Reliability History on my machine yesterday.
Source VEGAS Pro Summary Stopped working Date 9/30/2023 8:10 PM Status Report sent Description Faulting Application Path: C:\Program Files\VEGAS\VEGAS Pro 21.0\vegas210.exe Problem signature Problem Event Name: BEX64 Application Name: vegas210.exe Application Version: 21.0.0.108 Application Timestamp: 64d189ec Fault Module Name: libmfx64-gen.dll Fault Module Version: 23.6.12.3975 Fault Module Timestamp: 6486c4e1 Exception Offset: 0000000000977c15 Exception Code: c0000409 Exception Data: 0000000000000007 OS Version: 10.0.19045.2.0.0.256.48 Locale ID: 1033 Additional Information 1: 18dc Additional Information 2: 18dcb70360839c50decc4b476d565433 Additional Information 3: 2335 Additional Information 4: 23350ec6eb4e69541a3dab7c5bca42b3 Extra information about the problem Bucket ID: 2e21027929a1f6b53205114e12d90860 (1298463094587590752)It appears to have a different source .dll than yours. Yours was Fault Module Name: ucrtbase.dll, but likely the effect on the workflow was similar.
Hi John, You're way, way ahead of me when it comes to this kind of information as I really have no idea what it is or means. Just wish there were a way to have Vegas run and users like myself to not have to worry about the crashes. I feel like a people reading these posts think of me as just a complainer but Vegas should work much smoother. I might expect an occasional crash but it happens constantly.
Description
Faulting Application Path: C:\Program Files\VEGAS\VEGAS Pro 21.0\vegas210.exeProblem signature
Problem Event Name: BEX64
Application Name: vegas210.exe
Application Version: 21.0.0.108
Application Timestamp: 64d189ec
Fault Module Name: ucrtbase.dll
Fault Module Version: 10.0.19041.789
Fault Module Timestamp: 2bd748bf
@Roger Bansemer the Fault Module here is pointing to a M$ issue with it pointing to an issue with M$ Visual C++ and not Vegas. Read THIS for a possible fix to this particular issue. I generally run t he SFC scan once a month to check on things. And of course, Bitdefender (paid) and Malwarebytes Pro are on their job as always.
@john_dennis being the "shade tree diagnostician" that you are, I know you've done a google search on that fault module, which seem to point to Intel iGPU.
[edit: see this is John's machine. ucrtbase.dll points to Microsoft C++]
libmfx64-gen.dll is the clue John's giving- try searching for it.
I'd uninstall the Intel GPU drivers and install the latest one cleanly and see if it helps. For most of us VEGAS isn't constantly crashing so I hope you can resolve it.
@Reyfox said:
"... the Fault Module here is pointing to a M$ issue with it pointing to an issue with M$ Visual C++ and not Vegas. Read THIS for a possible fix to this particular issue. I generally run the SFC scan once a month to check on things."
I'm not certain that M$ is alone in this issue since application developers can choose to use a certain version of this .dll. I found 21 files on my machine in various places and various states of being installed. It's interesting that I didn't find a version that I recognized as being put there by Vegas.
"... being the "shade tree diagnostician" that you are, I know you've done a google search on that fault module, which seem to point to Intel iGPU."
I hope you're not conflating my BEX64 error, Fault Module Name: libmfx64-gen.dll that I used for example with the OP BEX64 error, Fault Module Name: ucrtbase.dll. While video driver is always suspect, I haven't proven that or fixed it.
I've wasted more time analyzing this than I ever wasted restarting Vegas Pro.
Speaking of glue. @Roger Bansemer and I are at the same Windows OS Version:
OS Version: 10.0.19045.2.0.0.256.48
@Roger Bansemer As you are long time Vegas Pro user, i am sorry to see the deep frustration you are now having.
Where you experiencing anything similar to this when you were using Vegas Pro 20? And which Windows OS are you currently using?
I got confused with the iGPU, I see it's a different DLL.
I'm on 10.0.19045.2.0.0.768.101 My recent VEGAS crashes haven't pointed to either of these DLLs.
For what it's worth the Visual C++ library is on version 14.36.23532.0, though I also have older ones installed and am not sure which VEGAS uses.
@Roger Bansemer As you are long time Vegas Pro user, i am sorry to see the deep frustration you are now having.
Where you experiencing anything similar to this when you were using Vegas Pro 20? And which Windows OS are you currently using?
Hi Steve,
I'm using windows 10. I've had these not responding issues for years and years and years. Never seems to improve. I did read the suggestion above about C++ about reinstalling, etc. but I'm simply not that good at that sort of thing and it usually doesn't go well, often worse. I do have a paid program called Driver Easy that updates my drivers but getting into doing all that manually with dll files, it's just not my thing. As I've said before, Vegas is the one and only program that gives me issues and seems like Vegas always wants me instead of them to fix issues.
It's not like I'm using an ancient computer. I have tons of ram, new video card, new mother board, etc. If vegas is choking because of something other than vegas itself then it would seem that other programs would have issues which they don't. For me, I think Vegas is not working, not some other component. I'm probably wrong. I just want Vegas to work for a change.
Enough complaining, I guess.
I am having problems with this program. The video won't play but the audio will. I am behind and need to get these videos made but can't get any help. How can I get a live tech support person to help?
@Cynthia-Carter you will need information from HERE, B and C. Otherwise no one can begin to help you.
For support, see this LINK.
This forum is faster, so I suggest you answer B and C.
I am having problems with this program. The video won't play but the audio will. I am behind and need to get these videos made but can't get any help. How can I get a live tech support person to help?
@Cynthia-Carter Please make a new thread as this isn't the topic here. Most likely it's an unsupported format (audio hasn't changed much over the years but video has). A new camera with an old version of VEGAS will give you a result like that.
I'm having similar issues with vegas pro 20. The log points to mc_demux_mp4.dll. Any suggestions?
I also have this problem with "Not Responding". The frames work and at some point they get stuck. I want an answer and a solution please.