AppHangB1 - Not responding error

Tony_A wrote on 11/18/2023, 4:15 PM

I had been getting the typical AppHangB1 and Not Responding freezes, so out of all of the popular fixes increasing the Options >Dynamic Ram and leaving GPU 4070ti settings works best for me, however, a random less frequent freeze happens now and again. I also run RDC at the same time, has anyone had issues running RDC and using Vegas Pro? Would an exception show up in Reliability History. Unsure what this error is...

Description
A problem caused this program to stop interacting with Windows.
Faulting Application Path:    C:\Program Files\VEGAS\VEGAS Pro 21.0\vegas210.exe

Problem signature
Problem Event Name:    AppHangB1
Application Name:    vegas210.exe
Application Version:    21.0.0.187
Application Timestamp:    6543d35e
Hang Signature:    afec
Hang Type:    134217728
OS Version:    10.0.22631.2.0.0.256.48
Locale ID:    1033
Additional Hang Signature 1:    afecba28028e238acc4b3f4ebbf625e4
Additional Hang Signature 2:    10c2
Additional Hang Signature 3:    10c2f20da11171a3f5164f1f88719afc
Additional Hang Signature 4:    afec
Additional Hang Signature 5:    afecba28028e238acc4b3f4ebbf625e4
Additional Hang Signature 6:    10c2
Additional Hang Signature 7:    10c2f20da11171a3f5164f1f88719afc

Extra information about the problem
Bucket ID:    06e4db5444f19e5b685a2a6762db8f31 (1754761628342783793)

Comments

J-Toresen wrote on 11/18/2023, 4:41 PM

What is RDC?

Tony_A wrote on 11/18/2023, 4:59 PM

What is RDC?

Oh, running Remote Desktop, connecting to remote, work system, etc. I'm assuming it shouldn't affect Vegas Pro performance, but again, was wondering if anyone knew.

john_dennis wrote on 11/18/2023, 5:59 PM

I've configured Remote Desktop Protocol hundreds of times and never once noticed that the Windows app was called "Remote Desktop Connection".

Most of us mortals on this forum are unable to decode the logs from the Windows Event Log or Reliability History. We're forced to ask Microsoft and/or Vegas Creative Software developers. Sometimes the data provides clues, but not always.

VEGASDerek wrote on 11/19/2023, 7:23 AM

You may consider turning on the hang detection option in VEGAS...this would allow VEGAS to send and error report to the development team if it detects the process has hung.

john_dennis wrote on 11/19/2023, 9:28 AM

@Tony_A @VEGASDerek

I powered on my machine and opened Vegas right away this morning and got the same error when I hit play. (I normally hit the power button and go downstairs to make coffee.)

Source
VEGAS Pro

Summary
Stopped responding and was closed

Date
‎11/‎19/‎2023 7: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 21.0\vegas210.exe

Problem signature
Problem Event Name:    AppHangB1
Application Name:    vegas210.exe
Application Version:    21.0.0.187
Application Timestamp:    6543d35e
Hang Signature:    afec
Hang Type:    134217728
OS Version:    10.0.19045.2.0.0.256.48
Locale ID:    1033
Additional Hang Signature 1:    afecba28028e238acc4b3f4ebbf625e4
Additional Hang Signature 2:    fb6d
Additional Hang Signature 3:    fb6d6b37dbd9196518e5bbce0906efa5
Additional Hang Signature 4:    afec
Additional Hang Signature 5:    afecba28028e238acc4b3f4ebbf625e4
Additional Hang Signature 6:    fb6d
Additional Hang Signature 7:    fb6d6b37dbd9196518e5bbce0906efa5

Extra information about the problem
Bucket ID:    06e4db5444f19e5b685a2a6762db8f31 (1754761628342783793)

Back in the Reliability History log, I noticed a very coincidental update:

Continuing with the project produced another failure.

ChrisD wrote on 11/19/2023, 2:32 PM

I also run RDC at the same time, has anyone had issues running RDC and using Vegas Pro?

You're a little light on the RDP details, but I'm curious.

Assuming you are are trying to run Vegas locally, and not the remote system? And does Vegas work when not connected?

And how are you connected to the RDP session, through a VPN or natively? On the same network? And the session's local resources setting?

Personally I use RDP a lot, through a VPN, but seldom run anything local, except for maybe Teams. Among other things I have always had issues when my PC's resources collide with those on the remote system -- especially through a VPN where names and file locations resolve against the remote network first, hit and miss, severely affecting local performance, or breaking it entirely.

Tony_A wrote on 11/19/2023, 3:27 PM

I've configured Remote Desktop Protocol hundreds of times and never once noticed that the Windows app was called "Remote Desktop Connection".

Most of us mortals on this forum are unable to decode the logs from the Windows Event Log or Reliability History. We're forced to ask Microsoft and/or Vegas Creative Software developers. Sometimes the data provides clues, but not always.

I've configured Remote Desktop Protocol hundreds of times and never once noticed that the Windows app was called "Remote Desktop Connection".

Most of us mortals on this forum are unable to decode the logs from the Windows Event Log or Reliability History. We're forced to ask Microsoft and/or Vegas Creative Software developers. Sometimes the data provides clues, but not always.

Ok. Just wondering if RDC or RDP (my app is called RDC on my win11) causes any conflicts.
 

Tony_A wrote on 11/19/2023, 3:35 PM

I also run RDC at the same time, has anyone had issues running RDC and using Vegas Pro?

You're a little light on the RDP details, but I'm curious.

Assuming you are are trying to run Vegas locally, and not the remote system? And does Vegas work when not connected?

And how are you connected to the RDP session, through a VPN or natively? On the same network? And the session's local resources setting?

Personally I use RDP a lot, through a VPN, but seldom run anything local, except for maybe Teams. Among other things I have always had issues when my PC's resources collide with those on the remote system -- especially through a VPN where names and file locations resolve against the remote network first, hit and miss, severely affecting local performance, or breaking it entirely.

Yes, I have to run Vegas locally, my remote work system is 11 years old. I run Teams locally and RDC through a fixed IP natively. I am just wondering if anyone else out there has noticed issues because I work remotely but also need the connection running for other tasking on the remote system. Probably not ideal, I get it, but again just wondering. If it's a known issue then I will build another offline system just for Vegas/Video editing.

john_dennis wrote on 11/19/2023, 6:50 PM

I used to connect to my media server using RDC to manipulate files without going there, but I changed it to run with a limited user logged on and I needed to have more rights that the user type allowed so I seldom do it now. I messed up the recording scheduler more than once and missed my wife's soap opera. I can't afford that!

With my previous edit machine, I used to connect remotely from the laptop to check on long render jobs, but now 1) the renders go faster and 2) I care less about how long renders take these days.

I still might use RDC on occasion to get a file from another machine rather than go there to share the folder.

Tony_A wrote on 11/19/2023, 7:02 PM

I used to connect to my media server using RDC to manipulate files without going there, but I changed it to run with a limited user logged on and I needed to have more rights that the user type allowed so I seldom do it now. I messed up the recording scheduler more than once and missed my wife's soap opera. I can't afford that!

With my previous edit machine, I used to connect remotely from the laptop to check on long render jobs, but now 1) the renders go faster and 2) I care less about how long renders take these days.

I still might use RDC on occasion to get a file from another machine rather than go there to share the folder.

I tested today without RDC and nothing else running, seemed good. I then left Vegas running for a while and came back and it was not responding. I swear this program is haunted :-(