Unmanaged exception error

JRey wrote on 11/2/2020, 10:12 AM

I upgraded to 17 452 on Win10 with Nvidia GTX card from 13 hoping the exception error might disapear. Nope! Its back and haunts me.

Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 17.0 (Build 452)
   Problem:             Unmanaged Exception (0xc0000005)
   Fault Module:        C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_edab19158bdd0d0a\nvoglv64.dll
   Fault Address:       0x00007FFC5858A270
   Fault Offset:        0x0000000000A7A270

I have checked the posts on this subject, installed new drivers all around, turned GPU acceleration off, clicked my heels together and turned around three times. Nothing works!

Did anyone ever come up with a difinitive answer for this isssue?

Comments

andyrpsmith wrote on 11/2/2020, 10:21 AM

try and source a new version of this file. google it.

andyrpsmith wrote on 11/2/2020, 10:29 AM

I have version 27.21.14.5671

JRey wrote on 11/2/2020, 10:36 AM

Thank you for the reply. Do you mean this file nvoglv64.dll

JRey wrote on 11/2/2020, 10:41 AM

Just did a search for that driver. Although I can't see one I am clearly not alone. You would think with so many problems being highlighted on line Nvidia would just fix the problem.....

andyrpsmith wrote on 11/2/2020, 10:47 AM

I could send over my version via PM. I would need to change the extension from .dll to jpg as PM only accepts some file types. You would just need to change it back to .dll.

andyrpsmith wrote on 11/2/2020, 10:50 AM

I just sent it, did you receive it?

andyrpsmith wrote on 11/3/2020, 8:56 AM

Shame the file cannot be sent via PM. I do not know where it came from. If you have downloaded the latest Nvidia driver and this file still causes an error then maybe another issue is causing the problem. Did you check the version you have compared to mine - see above.

j-v wrote on 11/3/2020, 9:34 AM

@JRey
What is your hardware precisely concerning CPU and GPU?
I have an Intel processor and a nvidia GPU, but the file causing your error is not available on my system.

JRey wrote on 11/4/2020, 6:56 AM

Shame the file cannot be sent via PM. I do not know where it came from. If you have downloaded the latest Nvidia driver and this file still causes an error then maybe another issue is causing the problem. Did you check the version you have compared to mine - see above.

Yours is 27.21.14.5671 Mine is 27.21.14.5167 so I am guessing an ealier version? Yet I am running the driver package so does this file come with a driver download or is a windows .dll.

Really appreciate your help by the way

JRey wrote on 11/4/2020, 7:00 AM

@JRey
What is your hardware precisely concerning CPU and GPU?
I have an Intel processor and a nvidia GPU, but the file causing your error is not available on my system.

I also have an Intel processor and nvida GPU. Its is on my system I just checked try using the link above and see if its there. How weird...

j-v wrote on 11/4/2020, 7:07 AM

@JRey
I also have an Intel processor and nvida GPU.

In that case the number you told here is the newest driver for your Nvidiacard.
- Which driverversion do you use for the Intel?

- What is the number of the Intel ( or processor)?
- What is the number of your Nvidia card?

JRey wrote on 11/4/2020, 7:56 AM

@JRey
I also have an Intel processor and nvida GPU.

In that case the number you told here is the newest driver for your Nvidiacard.
- Which driverversion do you use for the Intel?

- What is the number of the Intel ( or processor)?
- What is the number of your Nvidia card?

The number for the Intel is i7-4770

The card is GTX 970 with the driver 27.21.14.5167

As for the intel driver 10.0.19041.546

j-v wrote on 11/4/2020, 9:41 AM

As for the intel driver 10.0.19041.546

Your Intel GPU is the Intel 4600 the latest driversversion for that stated on their website is version 15.40.47.9166 of 10/23/2020.
Install that one trying to overcome your error message.

andyrpsmith wrote on 11/4/2020, 10:12 AM

I found this info : Errors related to nvoglv64.dll can arise for a few different different reasons. For instance, a faulty application, nvoglv64.dll has been deleted or misplaced, corrupted by malicious software present on your PC or a damaged Windows registry.

andyrpsmith wrote on 11/4/2020, 10:16 AM

JRey I can send you the file via airbridge, I will need your email. You can send me this via PM if you wish.

JRey wrote on 11/4/2020, 10:30 AM

As for the intel driver 10.0.19041.546

Your Intel GPU is the Intel 4600 the latest driversversion for that tated on their website is version 15.40.47.9166 of 10/23/2020.
Install that one trying to overcome your error message.

I installed the intel driver update tool. Turns out I have the i7 4700 the tool found a couple of things that needed an update one of which was

Intel graphics 4600 and it updated to Version 20.19.15.5166 Date8/8/2020

I will let you know if it solves the problem and thank you for your help

JRey wrote on 11/5/2020, 9:57 AM

As for the intel driver 10.0.19041.546

Your Intel GPU is the Intel 4600 the latest driversversion for that tated on their website is version 15.40.47.9166 of 10/23/2020.
Install that one trying to overcome your error message.

I installed the intel driver update tool. Turns out I have the i7 4700 the tool found a couple of things that needed an update one of which was

Intel graphics 4600 and it updated to Version 20.19.15.5166 Date8/8/2020

I will let you know if it solves the problem and thank you for your help

JRey wrote on 11/5/2020, 9:59 AM

After my first render - closed Vegas and...

Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 17.0 (Build 452)
   Problem:             Unmanaged Exception (0xc0000005)
   Fault Module:        C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_edab19158bdd0d0a\nvoglv64.dll
   Fault Address:       0x00007FF93B66A270
   Fault Offset:        0x0000000000A7A270

Is this a vegas oproblem or windows?

j-v wrote on 11/5/2020, 10:21 AM

I think not Vegas because that file is a Windows file.
You can try to temporarily rename that file to old nv_...... and try again.

andyrpsmith wrote on 11/5/2020, 2:59 PM

Worth moving the current file to desktop (as J-V says) and try again and also then adding the file I have just sent over.

andyrpsmith wrote on 11/6/2020, 8:55 AM

Just to update anyone following this thread.

It is very difficult to change the file nvoglv64.dll I needed to use a nice little utility called unlocker which give info on what application is locking a file and give options to unlock. It showed a magix application was locking this file and unlocker could rename it only on next reboot so i opted to change the file to .bak. I found it in three locations in repository filestore so I changed it in one location (each file version had a different file version). the effect was V18 posted a message that I was low on GPU memory when trying to load my NewBlue Titler 4 Title (this is an accelerated title) and I should reinstall the titler program. Same message low gpu mem after reinstall. Changing the .bak to .dll titler now working correctly. Locations:

C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_8dccece3a1276290

C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_7c6629f3404619ed

C:\Windows\System32\DriverStore\FileRepository\nv_dispsi.inf_amd64_4aa4d6f191cff485

Versions:

1) 27.21.14.5671

2) 27.21.14.5655

3) 27.21.14.5638

andyrpsmith wrote on 11/6/2020, 9:02 AM

Unlocker shows

File 1) is being locked by Magix updater, Titler pro, Vegas18

No lock on 2) or 3) while Vegas running

andyrpsmith wrote on 11/6/2020, 2:00 PM

JRey, any luck with disabling Opencl/gl in internal menu?

andyrpsmith wrote on 11/9/2020, 10:20 AM

Update, I have been working with JRey via PM to help resolve the issues and we have made progress to the extent that V17 is running with no error and using GPU. the Strategy has been:

1. Get Vegas stable at the editing stage so you can add clips, play back the timeline reasonably using the Graphics card, be able to move clips about, resize, add filters like levels to optimise the image, add stabilization, use pan/crop all with Vegas freezing. Forget about rendering at this stage. To help with this:

2. Disable any Intel HD Graphics in device manager (no Intel GPU should appear in Task Manager).

3. Download the Nvidia driver 456.71 from the Nvidia site and find the studio version.

4. Set dynamic ram preview to 0 and the number of rendering threads to the same as the number of cores your CPU has.

5. Start with only a few clips on the timeline - say 10 max. Save the Veg file.

6. Once Vegas is stable with this we can look at some rendering templates starting with CPU only first and then trying GPU accelerated if CPU renders OK.

7. Taking it step by step in sorting out crashes will I think lead to progress in getting V17 to work.

Please if you would let me know how you go with each stage and what issues arise.

We were able to get clips in and running well with a range of effects, we were able to render out without errors and at this stage no GPU acceleration.

We found that JRey clips were MPEG-2 and AVC with MPEG-2 using compoundplug and also AVC.

We were able to get everything stable timeline and render.

Looking at the internal tab showed that So4compound plug for AVc was set to FALSE changing this to TRUE enable So4 and GPU acceleration.

No crashes or errors.

So we then enabled Intel GPU to see how things went - so far no crashes.

I think JRey is happy with V17 so far.