MicroCenter Powerspec: Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz, 3696 Mhz, 6 Core(s), 12 Logical Processor(s)
Windows Version 10.0.19041 Build 19041

I have a video project which contains 123 audio and video assets, a collection of video clips for a performance group. It's a 66-minute production. Two days before the release deadline, and perhaps 4 hours of editing ant titling etc. Vegas Pro loaded the project to around 50 %, then issued the "Vegas Pro has stopped working (unmanaged exception error) message." Nothing I did would bring the project into Vegas. I have both v. 13 (which is what I routinely work in) and 15, and the problem persists in both versions.

After several hours of panicked attempts to move the project to another drive and other random tactics, I finally stumbled on the solution. I renamed the folders which contained the various project elements, forcing Vegas to prompt for its first asset location. (That was an attempt to determine if it was a particular file or graphic that was crashing the program.)

As it turns out, it wasn't necessary to rename all the folders and patiently step through every file as it loaded. At the first prompt, I specified the newly named folder and file name (the file wasn't re-named, just the folder it was in). I was then informed that several other files were also found there, and I accepted "yes to all" option. Voila, the project file opened without further problems.

It's modestly annoying to keep toggling the name of a folder every time I want to work on it, but the solution has been reliable. I could find no reference to this bahavior anywhere on the net, hence my posting it here.

First, I have no clue as to what triggers it. The day it first happened, I'd left the p[roject open overnight and when I resumed editing in the morning, the mouse movements were jerky and playing the project was slow and hesitant, so I saved the project, re-booted then re-loaded it, which is when it crashed.

When I quit for the day, I first save the project, then again in "Save as..." to a new file name, thus keeeping a trail of incremental backups. None of those backups loads (without using the folder-rename trick), including very early ones which were fine before this phenomenon first occurred. Way fewer assets in those, so complexity probably isn't the problem.

I hope the rest of the world hasn't encountered this problem, but if you have, I hope this post is helpful to you.

If anyone out there has an idea what this problem is, of if it's somehow a corruption of the project file, is therer a way to troubleshoot the file and locate the point of the corruption.

I have never run into this on any of hundreds of much more complex productions so I'm baffled.

Any insight would be appreciated.