Continued crashing of Vegas Pro 22 on new system

Jon-Conley wrote on 5/11/2025, 12:31 PM

Long time user of Vegas Pro, and I am about to give up and go and buy and teach myself Adobe Premiere due to the untenable crashes that I continue to get with this software. I recently have even built a new system(specs below), and the crashing during editing continues. On the new system, it isn't even allowing me to generate crash reports to send to Magix. It simply freezes, and I have to "control, Alt, Delete" to close the program.

I have a brand new computer, with fresh Windows install and nothing installed on the system but Vegas 365 Pro apps, I'm not even running anything but the internal Windows antivirus.

  • Asus Z890 Nova Motherboard
  • Intel Ultra 9 -285 CPU
  • 96 GB Ram
  • PCI 5 NvMe SSD hard drives
  • Gigabyte GeForce 4070 GPU

I mostly edit 4k footage shot on a Panasonic GH5 M4/3 camera, DJI Mavic 2 Zoom 4k and GoPro 11 black. I did have some issues on my previous system editing GoPro footage shot in HEVC, so I have converted all my old footage to MP4s, and all my new footage is shot with HEVC turned off. This is getting ridiculous, in that I can work for maybe 10 minutes at a sitting, and then no matter what I am working on, the system crashes. 

I'm using about 50% of my available memory for Vegas, and have set it to high priority in the system manager for Windows, but the issue is only when editing. I am able to render videos with no problem.

 

Any thoughts.. I just spent nearly $3k on this new system and hate that I am still experiencing similar issues to before, albeit my older system did have issues with rendering which the increased horsepower I have thrown at my work seems to help there.

Comments

RogerS wrote on 5/11/2025, 1:13 PM

Do you have crashes with the priority on normal and dynamic ram preview at 5%?

Does Windows reliability history give a hint as to what's happening when it crashes?

To get VEGAS to send a crash report, hold shift, go to the options menu and see internal at the bottom. Type in hang and change hang detection to TRUE.

Jon-Conley wrote on 5/11/2025, 2:14 PM

It crashed with Priority on Normal, and RAM allocation set from 5% all the way up to 50%, no difference. I've enable reporting on Hang so will see if I can get an error code, or can get some data on the crash I can share.

 

Here is the Windows Reliability Details from one of the crashes:

Description
A problem caused this program to stop interacting with Windows.
Faulting Application Path:    D:\Program Files\VEGAS\VEGAS Pro 22.0\vegas220.exe

Problem signature
Problem Event Name:    AppHangB1
Application Name:    vegas220.exe
Application Version:    22.0.0.248
Application Timestamp:    67f55391
Hang Signature:    63f6
Hang Type:    134217728
OS Version:    10.0.26100.2.0.0.768.101
Locale ID:    1033
Additional Hang Signature 1:    63f644890d298d45f2f9bfb65ac84347
Additional Hang Signature 2:    6253
Additional Hang Signature 3:    6253f17c4ded8de412b5c79934e0a706
Additional Hang Signature 4:    63f6
Additional Hang Signature 5:    63f644890d298d45f2f9bfb65ac84347
Additional Hang Signature 6:    6253
Additional Hang Signature 7:    6253f17c4ded8de412b5c79934e0a706
 

RogerS wrote on 5/11/2025, 4:32 PM

Thanks for that testing. If VEGAS gives a fault module in thr error report it could be a clue. Sometimes we'll see a GPU driver or Fx name there.

VEGASDerek wrote on 5/11/2025, 8:55 PM

If the application is hanging, I would suggest going into the internal preferences and turn on the hang detection, which should generate a crash dialog which we can use to diagnose the problem.