Vegas12 keeps crashing with nvoglv64.dll exception

PeteM wrote on 6/23/2014, 9:55 PM
I constantly get the following crash in VegasPro 12:

Problem: Unmanaged Exception (0xc0000005)
Fault Module: C:\Windows\system32\nvoglv64.DLL

It happens while editing, during stabilization of media and sometimes even when starting Vegas up. I have the latest video card drivers, GPU Acceleration in Vegas turned off with Dynamic Preview buffers set to Zero.

This is of course much better than the crash festival I experienced when I installed the Vegas Pro 13 trial a few months ago.


OldSmoke wrote on 6/24/2014, 8:02 AM
I have the latest video card drivers

There might as well be the answer to your question. Try and roll back the driver if you can. For my Gforce card I use 296.10 and of lately 334.89; nothing else works as good on my system.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

Steve Mann wrote on 6/24/2014, 8:28 AM
Unmanaged Exception is *always* a driver issue. In this case, an nVidia driver. Are you using any 32-bit plug-ins?
ChrisDolan (SCS) wrote on 6/24/2014, 1:08 PM
Steve Mann,
"Unmanaged" means the crash was in native code, i.e. C++. "Managed" means the crash occurred in a virtual machine language, i.e. C#. Most of the Vegas crashes are in unmanaged code, whether Sony code or 3rd party code. In this case, "nvogl64" is Nvidia's 64-bit OpenGL driver.
Steve Mann wrote on 6/24/2014, 11:02 PM
Chris, let me expand. In the many years of building, programming and maintaining PCs, I have never seen an "Unmanaged Exception" in mature code that was *not* due to a driver.

So, I left out "almost". Unmanaged Exceptions are almost always a driver issue.
pwppch wrote on 6/25/2014, 7:34 AM
The unmanaged exception 0xc0000005 means that some process - whether is in driver code or application code - attempted to access memory it should not. In this case, it is a driver dll. There is nothing about drivers that make this unique to them.

So while it can be a driver, it is not always a driver.

NormanPCN wrote on 6/25/2014, 11:09 AM
I have never seen an "Unmanaged Exception" in mature code that was *not* due to a driver.

I have had bugs show up in ten year old code, and they were access violations which is an exception. Depending on the degrees of freedom of input it is easy to have latent bugs in code that go unfound for ages.

I guess my question is what exactly do you mean by unmanaged?

To me an exception is just an exception. Where an exception originates is not really relevant since we can pass garbage to something and unless they validate all input a problem can occur, which may or may not result in an exception being raised.
Steve Mann wrote on 6/25/2014, 11:08 PM
"Unmanaged" simply means there is no error handler to process the exception, so the O/S has no choice but to crash.
dlion wrote on 6/26/2014, 7:53 AM
+1 smoke.

try a different driver. 377 was no good for me, had to roll back to 375. lots of folks are still running 296...

no loss of face for not running the latest.