Vegas Pro 16 always crashes on exit

john-bollenbacher wrote on 4/15/2019, 3:50 PM

Hey All,

Wondering if anyone has encountered this problem, and found a fix? I just got Vegas Pro 16 (365) - and after some experimenting got it working pretty well - but it crashes every time I quit (Alt+F4). If I save the project, I don't lose anything, but have to reset preferences every time I re-open. Just kinda annoying. I'm on Win 10. Dell 9570. Run PPR and Resolve without issue on the machine. I've deleted temp files, updated all drivers, etc.

Here is the problem description -

Problem Description
Application Name: VEGAS Pro
Application Version: Version 16.0 (Build 361)
Problem: Unmanaged Exception (0xc0000005)
Fault Module: C:\WINDOWS\System32\DriverStore\FileRepository\nvdmci.inf_amd64_7df1bd005f09a6f8\nvoglv64.dll
Fault Address: 0x000000005D737BF9
Fault Offset: 0x0000000000AF7BF9

Fault Process Details
Process Path: C:\Program Files\VEGAS\VEGAS Pro 16.0\vegas160.exe
Process Version: Version 16.0 (Build 361)
Process Description: VEGAS Pro
Process Image Date: 2019-01-07 (Mon Jan 07) 22:54:52

Thanks in advance for any help.

Comments

j-v wrote on 4/15/2019, 4:30 PM

I see you use the same videocard as on my laptop, where I saw the same with the newest drivers for the Nvidia. Installing driverversion 399.24 did resolve that anoying popup and that fault error. I hope that the next Vegas update will repair this.
The fault error pop up is not the worst thing that happened, but trying to start a next instance froze because of remains of the former Vegas editing, that I had first to delete in the taskmanager before the new start of Vegas 16 was allowed.

aboammar wrote on 4/16/2019, 5:16 AM

I encounter this problem from time to time but I am not sure what exactly trigger it because it seems random to me.

JackW wrote on 4/16/2019, 12:58 PM

I have found this will occur if I save, then exit immediately. I suspect the computer has not had time to process the "save" before attempting to shut down Vegas, resulting in a crash. No crash if I save, wait a few seconds, then close or exit.

john-bollenbacher wrote on 4/16/2019, 1:29 PM

Sorry JackW. Just tested that, and still crashing on quit.

David Johns wrote on 4/16/2019, 4:42 PM

I had the same issue, both in (Sony) Vegas Pro 13 and still when I recently updated to Magix Vegas Pro 16. If I opened the program and closed it immediately, no problem. If I opened and added an audio track then exited, no problem. But if I opened it and added a video track then closed it would crash with the same error. Even a blank video track.

other posts on this forum suggested the nVidia drivers but I had the latest ones and still the same issue.

Finally "solved" - worked around - by going into preferences, Video and setting the GPU acceleration to use the integrated Intel graphics (a 4600 on my laptop) instead of the GTX870M. Now Vegas closes properly. And what's more, playback is better than it was with the nVidia setting too.

adimatis wrote on 4/17/2019, 2:37 AM

I can tell you for a fact that once I went back to Nvidia driver 399.24 it did indeed solve the same problem that I had. In my case, I had the feeling that somehow the driver update I tried (two different later drivers, the latest being 419) did not complete correctly, even though it would show ok in the applications.

Anyway, going back to driver 399.24 solved it for me.

j-v wrote on 4/17/2019, 3:27 AM

It has to be the solution because I can trigger that behaviour and see in Windows/System32/..... etc what the changes and differences are in those nvam...../nvoglv64 systemdrivers listed there. But only on laptop with the Intel and NVidia GPU's.
No problem at all on desktop where I use the latest 419.67-notebook-win10-64bit-international-crd-whql drivers.
I cannot get why the Nvidia drivers changes those drivers, but the installing of 399.24 drivers have to be be a "clean" install to change also those "nvam" files.
They change and the one signed out by the error message of Vegas does not exist anymore.

john-bollenbacher wrote on 4/17/2019, 12:02 PM

D. Johns - that indeed solved the issue for me. Frustrating to have this nice Nvidia GPU - but doesn't seem to want to work with Vegas. Oh well. All is working now.

animagic wrote on 4/17/2019, 12:41 PM

My impression is that Nvidia updates drivers to support the latest games. I've had a similar problem with other software, so I'm still on v. 417.35. This is an exception to the rule "always use the latest drivers..."

john-bollenbacher wrote on 4/17/2019, 2:03 PM

Well - I switched over to the "Creator" drivers that are supposed to be designed for folks like you and me; but apparently still no good.

j-v wrote on 4/17/2019, 2:19 PM

Well - I switched over to the "Creator" drivers that are supposed to be designed for folks like you and me; but apparently still no good.

What is the result if you now install that older driver I mentioned with a clean install in de settings and using the Nvidia normal als your main GPU?

David Johns wrote on 4/17/2019, 3:55 PM

D. Johns - that indeed solved the issue for me. Frustrating to have this nice Nvidia GPU - but doesn't seem to want to work with Vegas. Oh well. All is working now.

Strangely, I can still happily use the nVidia card when rendering, it's just when it's selected for the preview that it seems to cause issues. That said, I get slightly faster encodes on the Intel chip than I do with the graphics card anyway so I've just ditched the GTX from my workflow entirely!

fr0sty wrote on 4/17/2019, 7:14 PM

Well - I switched over to the "Creator" drivers that are supposed to be designed for folks like you and me; but apparently still no good.

The creator drivers have not yet pass windows driver certification and should not be used in a Vegas production environment. Try to roll back to an older driver, see if that helps anything.

YesMaestro wrote on 4/17/2019, 8:38 PM

I've been having the same problem. Along with that, Vegas never remembered the last project that I opened as well as any changes I made to the internal preferences. Once I turned the GPU acceleration off, it started to work again.

adimatis wrote on 4/18/2019, 5:59 AM

^^^ that happened to me too.

Anyway, when trying to update the "default" nVidia driver (and by that I understand the Windows driver for 1050ti, which was installed with the Windows fresh install) and which is 399.24, to ANY other newer driver, I had issues with Vegas, crashes while editing sometimes, often, but each exit will result in a crash without exception.

Once I rolled back to 399.24, after trying 419 creators as well, all is good. And I do not plan on updating anything - I don't want to risk the stability I've finally achieved, after many headaches and frustrations and with the help of fellow forumists.

Now all is working fine. I am happy. :)

mintyslippers wrote on 4/18/2019, 7:21 AM

Except for those of us on RTX 2060 cards which are only supported from the later drivers :)