Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 17.0 (Build 455)
   Problem:             Unmanaged Exception (0xc0000005)
   Fault Module:        
   Fault Address:       0x0000000219930522
   Fault Offset:        0x0000000219930522

Fault Process Details
   Process Path:        C:\Program Files\VEGAS\VEGAS Pro 17.0\vegas170.exe
   Process Version:     Version 17.0 (Build 455)
   Process Description: VEGAS Pro
   Process Image Date:  2021-04-29 (Thu Apr 29) 11:39:12

any driver change or older driver compatibility I should be aware of? any conflicting plugins?

The "VEGAS Pro won't start" FAQ, item 2.?

Maybe a long shot, but first restart your new PC (use the option restart - not shut down and power on), then when back up, wait a few minutes for the PC to settle down its other processes before (trying) to start up Vegas.

Make sure you have internet connection before starting up Vegas for the first time.

The "VEGAS Pro won't start" FAQ, item 2.?

Thanks vkmast, i'll give that a try. Got the exact same plugs installed as in my old PC tho, didn't create issues on that one. i'll report back.
Thanks Bitman, yes all Vegases are already activated, and I also usually wait until I start apps.

You could try Display Driver Removal (DDR), follow the directions including running from safe mode to double check it's not a driver problem. A driver problem that DDR might fix is usually more 'spectacular' though, monitors going black and resetting, blue screen or computer resetting

so...Bingo at the first shot. disabled OFX, and all Vegas versions now open. BUT...now all my OFX plugs are gone...not really a solution. Should I disable them one by one...?
EDIT:
inside the OFX folder, I narrowed it down to the plugins folder, renaming it makes vegas start. But inside that folder, renaming folders does not make a difference. Makes no sense to me...

Over the years, some on the forum have suggested to rename the third party OFX folder - C:\Program Files\Common Files\OFX to something else (e.g. 'OFX original' - but totally your choice) - so that Vegas Pro doesn't see those 3rd party OFX when opening. Then create a new C:\Program Files\Common Files\OFX folder which will of course be empty. Then copy/paste the OFX from the original OFX folder into the new OFX folder, but in small groups. After each copy/paste, open Vegas Pro. If it doesn't open, then you'll know that one of the OFX that you've just copy/pasted is the problem OFX for Vegas Pro and you can then delete the latest group and then add them one-by-one until Vegas Pro won't open - that then will be the problem OFX to leave out of the OFX folder. Of course, it may be more than one OFX - it could be a whole package from a 3rd party OFX company that isn't compatible with Vegas Pro.

I should add that a Vegas Pro feature request for some time has been for there to be some method of telling Vegas Pro to bypass/ignore any problem OFX it encounters on opening. At the moment, there is no way of solving this problem other than finding and removing the offending OFX from the OFX folder.

Thanks Dexcon...Jeez, I wonder why they all worked on my old PC...what a mess!😩

I wonder why they all worked on my old PC..

Just a 'needle in a haystack' possibility - perhaps there was some feature on your old computer that enabled a 3rd party OFX plugin to work but that feature is absent from your new computer so the OFX doesn't work. For example, a new Windows 10 install does not automatically install .NET Framework 3.5. That has to be done manually via Apps & Features / Related Settings (top RH corner heading)/ Programs and Features / Turn Windows features on or off - and then check both boxes for .NET framework 3.5 (xxxxxxxxx).

Ok so it's both the Ignite packages.

IgniteCore.ofx.bundle

IgnitePro.ofx.bundle

Shame, I really like those. What is it that makes them go wrong here and not on my old PC?
I filed a ticket support with FX home, I'll see what they say.

Some, including myself, have experienced many problems over the years with Ignite Pro because it randomly caused Vegas Pro (16 onwards) not to open. The solution was to uninstall Ignite Pro, start and then close Vegas Pro, and then re-install Ignite Pro. That worked ... until Ignite Pro became flaky again and the whole procedure needed to be repeated. The problem is so random and annoying that I ended up completely uninstalling Ignite Pro after successfully doing the workaround for VP18 - and then it appeared again on opening VP17. Grrrr!

The other thing is that Ignite Pro in Vegas Pro 17 and onwards needs to be version 4.1 at the very least because of coding changes in VP17 which switched the naming convention from Sony to Vegas. But then those with Ignite Pro 4.0 or earlier reported on the forum that Vegas Pro opened but the Ignite Pro plugins did not appear in VP.

You might want to do a forum search for IgniteCore.ofx.bundle to see the many posts about the problem.

Nonetheless, I am happy that you've discovered the problem OFX.

Thanks a lot Dexcon and all you people here in this thread. Your help actually saved my a**. I'll keep y'all posted about the Ignite issue. I actually tried version 5 and 4.1, both didn't work.

So I found the solution!
thanks to this post:
https://www.vegascreativesoftware.info/us/forum/looking-for-owners-of-previous-vegas-pro-suite-or-vegas-pro-ignite--117074/#ca730820

If the system language is NOT US English, Ignite pro plugs will crash Vegas!