What Nvidia driver version are you using? Try version 376.33.

Hey thanks for the replies :)

I'm using 378.49, won't be rolling back though. Fraps source? Nup.👀

I had a  good streak where I worked normally for a hour or so but some audio channels will only play for a few seconds when all the tracks are turned on then a major blue screen incident.

Very disheartening.

I'm using 378.49, won't be rolling back though.

I've read 5 reports on this forum of serious issues with the 378.XX drivers and Vegas. I've read just 1 report of those drivers being OK, and that was with the GTX Titan-x.

On the other hand I've read 5 positive reports for the 376.33 driver, including with the same card as you.

Worth a try, I'd say.

Recent, related report: https://www.vegascreativesoftware.info/us/forum/sms-11-projects-crashing-vms-14-build-105-when-opened--105998/

Thanks Nick , that's very interesting , I hope Nvidia and Magix , together can get things back in line, moving forward. :)

... 5 reports on this forum of serious issues with the 378.XX drivers and Vegas.

Count me in!
378.xx unusable in VP14 due to absence of Preview with GPU=On. In SLI mode either.

...VP11 feels OK, though...

Yeah that grovel thing seems to come up when the VST server crashes ( so it appears). Maybe there's a problem there, it may be linked to the display of the vst through Vegas using the Nvidia drive ( I don't know anything about this stuff) . Maybe this additional note might provoke another angle of exploration.

Hi guys , rolled back that driver.... red herring . All that did was make some other programs complain.

The crashing is even more present, so blaming Nvidia is not going to wash... nice effort though Nick 😉. I fell for that hook , line and sinker 🎣

These crashes I'm sure have everything to do with VST effects. Almost all of them gripe in V14... new ones , old ones bundled with Vegas ones.

So before we start blaming ALL the vsts , maybe let's consider that is could 'possibly' be....ummmmmmm oh yeah VEGAS 14 ! 💸

The only other thing I can think of is if it is the Elastique? Is it pitch change that's causing it?

Something that has changed between 13 and 14 has not been tested enough.... what is it guys?

Glad we've ruled out the Nvidia driver. Sorry it didn't work. Which driver versions exactly did you start with, roll back to, and end up with?

If you think it's VSTs then move them all out of your VST folder, see if Vegas starts, then put them back in batch by batch until you find the one causing the problems. If you get Vegas started, check and understand what settings you have in Options>Preferences>VST Effects.

General crashing troubleshooting tips are here: https://www.vegascreativesoftware.info/us/forum/faq-troubleshooting-crashing-and-stability--104785/

You might also try #11 in this https://www.vegascreativesoftware.info/us/forum/faq-vegas-pro-won-t-start-what-can-i-do--104784/

I tried the nvidia you suggested. I must say though Nick, I don't think it is any of my VSTs. I think , actually I'm pretty certain it is the Vegas VST server that is the problem. When I make changes in the vst ( any of them )  it may take several seconds for the update to take effect. This may be due to the fact that I had to increase my audio buffer to get rid of the stuttering ( present only in V14 and not before) .

SO when Vegas hangs. I check my task manager and I can see the background processes I have 'VEGAS VST server 32 bit ' running -I'm using 64 bit Vegas so that is an odd looking match already , that's not so weird but I have seen two instances of it running at the same time. Also when I stop that task ( having already got Vegas hanging) a report gets sent to Vegas. Now if I had just stopped Vegas I get no such cooperation... this just tends to point me toward it ( vegas VST server) being the culprit. I'm not going to goose chase my vst effects, because that is obviously just another way of shifting blame from the true culprit, it is so obvious that it is Vegas that is at fault here.

Anyway I have stuff to do and unnecessary bug spraying every vst I have is going to waste more of my time and I could become pretty freakn annoyed 👾 , so maybe that's for someone with more time up their sleave to play with.

Maybe a developer paid by Magix could fix this bug?

I check my task manager and I can see the background processes I have 'VEGAS VST server 32 bit ' running -I'm using 64 bit Vegas so that is an odd looking match already...

Vegas will use 32-bit VSTs as well as 64-bit VSTs.

I'm not going to goose chase my vst effects, because that is obviously just another way of shifting blame fro the true culprit, it is so obvious that it is Vegas that is at fault here.

It's far more likely to be an issue with your specific system/installation, as the errors you are seeing are not common.

Wow dude, now it's my computer? Funny for the last three years Vegas and all my plugins and apps have worked fine, Now I install Vegas 14 and my computer has some specific issue?  So it's anything but Vegas 14 fault? There's so much swerving going on here that it's actually got pretty surreal. No matter what I write , the last word will be 'it's not V14's fault' and it doesn't need fixing. Ok then whatever you say.

Can't wait for the next update... I'll have my fingers crossed.

 Now your turn Nick  ;)

Perhaps I should format my hard drive?... yeah I'll try that , that should keep me busy for a while😁

I'm more than happy to accept it's a generic issue with Vegas Pro 14, but if it is then it's likely we would be seeing more error reports like this on the forum. The few related error reports that I can trace are sprinkled down the years and mostly appear to be GPU-related.

Anyway I've covered all the suggestions I have. I suggest you make a support request here. You'll need to give them more specific details than you've given us in this post. If they reply requesting information or making suggestions, I suggest you comply otherwise you'll have no chance. I doubt they'll have anything for you that isn't covered in the posts I linked to above, but you never know. If you get it sorted, please come back and let us know what worked so we can help others. Good luck.

Yep , no worries Nick . Thanks for taking time to humour me anyway.🖖