Vegas Pro 20 / 23 Crash on start

GaryX wrote on 9/20/2025, 12:13 PM

Hello, since days i try to investigate, why vegas pro crashes on start.

My last successful project i did was on 28. july. i "guess" since september i am not able to use it anymore. I thought vegas pro 20 might have an windows update problem, so today i bought v23 and it crashes the same! (it does not display the vegas logo screen, crashes instandly)

 

Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 23.0 (Build 278)
   Problem:             Unmanaged Exception (0xc0000005)
   Fault Module:        C:\Windows\SYSTEM32\ntdll.dll
   Fault Address:       0x00007FFC96A7A9C0
   Fault Offset:        0x000000000002A9C0

Fault Process Details
   Process Path:        C:\Program Files\VEGAS\VEGAS Pro 23.0\vegas230.exe
   Process Version:     Version 23.0 (Build 278)
   Process Description: VEGAS Pro
   Process Image Date:  2025-09-04 (Thu Sep 04) 15:43:08

 

When i try to run it in safe mode i come further, the vegas logo comes, plugin factory does it's job and the UI opens and then it crashes too.

 

Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 23.0 (Build 278)
   Problem:             Unmanaged Exception (0xe0434352)
   Fault Module:        C:\Windows\System32\KERNELBASE.dll
   Fault Address:       0x00007FFDA2905369
   Fault Offset:        0x0000000000025369

Fault Process Details
   Process Path:        C:\Program Files\VEGAS\VEGAS Pro 23.0\vegas230.exe
   Process Version:     Version 23.0 (Build 278)
   Process Description: VEGAS Pro
   Process Image Date:  2025-09-04 (Thu Sep 04) 15:43:08

 

What i aleady did:

  • removed all vc++ and only instlaled the latest x86/x64
  • sfc /scannow and dism restore health
  • re-downloaded .net 4.8.1 and latest net 9.0.9
  • re-installed directX June 2020 redist

 

  1. my System:
  2. amd 5950x
  3. amd 6900xt driver 25.Q3
  4. 64gb DDR4 3600mhz
  5. Win 10 Pro 22H2 build 19045.6332

 

I couldn't figure out what is the problem, i hope someone can help me.

I remember vegas 20 had a crash problem and was fixed with build 411 - so i thought it could be a Windows update problem again.

Thanks.

Comments

jetdv wrote on 9/20/2025, 3:45 PM

What happens if you try running VEGAS as an "Administrator"?

GaryX wrote on 9/20/2025, 4:33 PM

What happens if you try running VEGAS as an "Administrator"?

Same, crash.

I have debugged the "crash" and it looks like a forced "exit", programmed in vegas.

Maybe Versions Check or OS check.

When i bought v23 it clearly stated: win10/11, thats why i bought it.

 

as my v20 build 411 also crashes the same way i wonder what was done.

Steve_Rhoden wrote on 9/20/2025, 5:07 PM

That's not normal behavior, Vegas is crashing because it's conflicting with a specific driver, component or program you have installed on your system.... The VC++ Redistributable, the .Net frameworks and Directx are not the problem.

GaryX wrote on 9/20/2025, 5:40 PM

That's not normal behavior, Vegas is crashing because it's conflicting with a specific driver, component or program you have installed on your system.... The VC++ Redistributable, the .Net frameworks and Directx are not the problem.

How can you say that when i have debugged the dumb in Windbg?

there's no entry in events, it "crashes" instandly and it says:

Failure.Bucket : BREAKPOINT_80000003_ucrtbase.dll!exit_or_terminate_process
...
ERROR_CODE: 0x80000003 - {AUSNAHME} Haltepunkt
...
STACK_TEXT:
ucrtbase!exit_or_terminate_process
ucrtbase!common_exit
vegas230!MxOSAL::MxFileFind::IsFindValid+0x25184

 

I had to use Procdump to find out what's going on..

It also crashes in min. safe mode where kinda no drivers are loaded.

Steve_Rhoden wrote on 9/20/2025, 6:06 PM

I can say that because i know what i am talking about and i am trying to help you!.

A (C:\Windows\SYSTEM32\ntdll.dll) error can also be caused from a corrupt file in the Windows Operating system. So doing a System File Checker (SFC) or a check disc (chkdsk) at startup would be something you could try.

GaryX wrote on 9/20/2025, 6:15 PM

I can say that because i know what i am talking about and i am trying to help you!.

A (C:\Windows\SYSTEM32\ntdll.dll) error can also be caused from a corrupt file in the Windows Operating system. So doing a System File Checker (SFC) or a check disc (chkdsk) at startup would be something you could try.

Well, thank you, i really just lost all nerves today.(trying to get it running the whole day!) i have already done a sfc /scannow and also dism health check and restore with a fresh dl 22H2, system is ok.

I can only tell you what the crash dumb says.

RogerS wrote on 9/20/2025, 7:14 PM

Why not try the official support?