Crash after about 3 minutes of editing "nvopencl64.dll" error

joseph-desaavedra wrote on 8/9/2019, 8:10 AM

Hangs and crashes after about 3 minutes of editing, done all the check lists updated and back dates drivers, everything and still this same error I sent off to tech support. No one responds and tech support does not exist. is this a working software or a scam? I just want it to work and have run out of options. I have used all versions 14 through 17 and it only got worse as the software matured. Help!

Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 17.0 (Build 284)
   Problem:             Unmanaged Exception (0xc0000005)
   Fault Module:        C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispsi.inf_amd64_bc5f9e8455cb216b\nvopencl64.dll
   Fault Address:       0x00007FFD24E73E94
   Fault Offset:        0x0000000000243E94

Fault Process Details
   Process Path:        D:\programs\vegas\vegas170.exe
   Process Version:     Version 17.0 (Build 284)
   Process Description: VEGAS Pro
   Process Image Date: 2019-07-30 (Tue Jul 30) 10:16:54

Extra Information
   File:                C:\Users\Joe\AppData\Local\VEGAS Pro\17.0\fileio_x64.log
   File:                C:\Users\Joe\AppData\Local\VEGAS Pro\17.0\dx_video_grovel_x64.log
   File:                C:\Users\Joe\AppData\Local\VEGAS Pro\17.0\svfx_video_grovel_x64.log
   File:                C:\Users\Joe\AppData\Local\VEGAS Pro\17.0\ocio_x64.log
   File:                C:\Users\Joe\AppData\Local\VEGAS Pro\17.0\dx_grovel_x64.log
   File:                C:\Users\Joe\AppData\Local\VEGAS Pro\17.0\gpu_video_x64.log
   File:                E:\sonic-Philly Cheesesteak\data\sonic philly cheese-01.veg

Problem Description
   Application Name:    VEGAS Pro
   Application Version: Version 17.0 (Build 284)
   Problem:             Unmanaged Exception (0xc0000005)
   Fault Module:        C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_547eeefb57db4499\nvopencl64.dll
   Fault Address:       0x00007FFEF19B3CE4
   Fault Offset:        0x0000000000243CE4

Fault Process Details
   Process Path:        C:\Program Files\VEGAS\VEGAS Pro 17.0\vegas170.exe
   Process Version:     Version 17.0 (Build 284)
   Process Description: VEGAS Pro
   Process Image Date: 2019-07-30 (Tue Jul 30) 10:16:54

amd 950x CPU
32 gig of ram
Nvidea Gforce GTX 1660 TI 6 gig ram
Gigabyte x399 extreem

Back to post

Comments

joseph-desaavedra wrote on 10/18/2019, 2:08 PM

Update

apparently tech support only answers messages on Friday afternoon which makes for an excessive turn around.

Fact:

1: Crashes at random times during edit in normal mode.

2: Stops crashing when all source files are proxied

Tech Support in spite of this information tech support still wants trouble report (and tell then what I was doing) when I have a crash so they can try to figure out what I am doing to makes it crash. Sometimes I am making it do several things at once other I am making it just run a preview and it crashes. when I do a proxy It is stable.

The only thing I have done that consistently makes it crash is edit in normal mode, I make it stop by proxy.

fr0sty wrote on 10/19/2019, 2:29 AM

So we know it is the media causing the issue, at least.

joseph-desaavedra wrote on 10/19/2019, 2:50 PM

or at least something related to the decoding of the media or the NVIDIA decoder not the media itself.

Sylk wrote on 10/19/2019, 3:00 PM

Sometimes I am making it do several things at once other I am making it just run a preview and it crashes. when I do a proxy It is stable.

For each crash note the last action(s) you did. At least :)

fr0sty wrote on 10/19/2019, 3:04 PM

If you disable nvdec, does it still crash?

joseph-desaavedra wrote on 10/19/2019, 3:49 PM

where to disable it in VP? just to make sure we are on the same page..

j-v wrote on 10/19/2019, 3:58 PM

That's only in VP 17

And again: first learn the program and how it works (best)!

joseph-desaavedra wrote on 10/19/2019, 4:02 PM

yes is crashed ether way..tried both on and off

joseph-desaavedra wrote on 10/19/2019, 4:06 PM

the only thing that has made any real measurable difference is doing a proxy on all source files prior to editing a video. and this is only in 17.. nothing else installed on system to make sure there is no interference from other versions.

fr0sty wrote on 10/19/2019, 5:11 PM

So we know it isn't anything to do with the GPU decode, and everything to do with the media. What is your media coming from?

joseph-desaavedra wrote on 10/20/2019, 7:58 AM

It comes from three cannon camera's, an SL2 and two g7x mark 2s. I have stated that previously. Why would you think it is the media? I can use one camera, two cameras in any combination or all three and it still crashes. There is nothing weird or abnormal about my media.

joseph-desaavedra wrote on 10/20/2019, 8:01 AM

Just because it is not the GPU decode does not mean it is is the media, could not VP be having issues decoding during edit whether it is using the CPU or GPU?

NickHope wrote on 10/20/2019, 9:33 AM

The problem appears to be due to your media format because it doesn't happen if you use proxies. Proxies are a different format of media.

Sylk wrote on 10/20/2019, 11:30 AM

@joseph-desaavedra try with media files moved (or copied) to C drive.

joseph-desaavedra wrote on 10/20/2019, 2:43 PM

The problem appears to be due to your media format because it doesn't happen if you use proxies. Proxies are a different format of media.

I understand that. Are you saying it is my source files that are at fault or something internal to VP that has trouble processing. These are pretty common media nothing fancy.

joseph-desaavedra wrote on 10/20/2019, 2:44 PM

@joseph-desaavedra try with media files moved (or copied) to C drive.

No harm in trying that I guess, does everyone park the source files and project on the c drive?

joseph-desaavedra wrote on 10/20/2019, 2:50 PM

I got a question..what format and container is VP using when it re encodes to the proxy files it makes? That would be interesting to know.

j-v wrote on 10/20/2019, 3:07 PM

You can find it yourself at the same location as your sourcefile and look for the MediaInfo of that file without the sfvp0 extension

Sylk wrote on 10/20/2019, 3:28 PM

@joseph-desaavedra try with media files moved (or copied) to C drive.

No harm in trying that I guess, does everyone park the source files and project on the c drive?

Not question to C drive, but question to put working files on the faster drive. Generally it's the C drive, so...

Also, proxies are created on the C drive, if i'm not wrong.

If you want to be sure, perform CrystalMark for all your drives.

joseph-desaavedra wrote on 10/20/2019, 3:54 PM

@joseph-desaavedra try with media files moved (or copied) to C drive.

No harm in trying that I guess, does everyone park the source files and project on the c drive?

Not question to C drive, but question to put working files on the faster drive. Generally it's the C drive, so...

Also, proxies are created on the C drive, if i'm not wrong.

If you want to be sure, perform CrystalMark for all your drives.

All the drives are the same speed. they are NVME drives of the same make and model Samsung 960 if I am correct. you can see my stats for that. They are all very fast.

Proxy's are made in the same folder as the source files where every they are at.

I can run CrystalMark but there is nothing slow about the build I am using.

Joe

Sylk wrote on 10/20/2019, 5:39 PM

Is Vegas installed on Windows drive?

NickHope wrote on 10/20/2019, 11:10 PM

The problem appears to be due to your media format because it doesn't happen if you use proxies. Proxies are a different format of media.

I understand that. Are you saying it is my source files that are at fault or something internal to VP that has trouble processing. These are pretty common media nothing fancy.

Impossible to know which, but I'm not necessarily saying that there is something "faulty" with your source files. It might be that you are using them in a way that causes VEGAS a problem.

@joseph-desaavedra try with media files moved (or copied) to C drive.

No harm in trying that I guess, does everyone park the source files and project on the c drive?

No. Traditional wisdom is to keep media on a separate drive. But it's perfectly feasible to store them on C: if you have space, especially now that drives are so fast. It's a reasonable thing to try in your troubleshooting, when all more likely causes have been ruled out.

I got a question..what format and container is VP using when it re encodes to the proxy files it makes? That would be interesting to know.

See section 9 of this. That section also deals with alternatives methods and formats for proxies.

joseph-desaavedra wrote on 10/21/2019, 7:16 AM

Is Vegas installed on Windows drive?

Absolutely covered that one a long time ago..

joseph-desaavedra wrote on 11/15/2019, 11:44 AM

New version out, crashes even doing proxy. if doing two video tracks starts stuttering a freezes.. reverted back to last build where stable doing proxy.. Tech support was responding... but now gone dead stick again. Tired of trouble shooting Vegas. I am getting worn down. Just want to make videos. FYI to any of you developers out there watching..