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 9/26/2019, 7:12 AM

Did clean install of windows 10, unplugged from the internet so win10 could not install the drivers for my hardware for me and I used most current from hardware manufactures ect ect ... installed vp17 again, it actually ran better with less frequent crashing and a little improvement after turning the dymanic ram preview limit to 0. any other number would result in a crash or a red screen on the preview window. Slogged through tech support for two weeks (they closed out my ticket without telling me) with them asking for system information and crash reports and the usual no response.. Then... they finally responded telling me to download the newest build which I did and of course it still crashes. Don't know if anyone cares. (seems like a number of folks in here get pretty defensive when I am critical of the platform) but the fact that I persist should say something to you hardcore defenders in light of the obvious instability of the platform , I may be critical but I am persistent and will prevail in the end if I can get tech support to take me serious or a least be forthcoming and upfront. I have new hardware in great condition. Maybe it is an issue with NVIDEA and driver support (I don't know). Anyway if anyone here cares (I sort of doubt it). I did not give up and continue the fight churning out 1 to 3 Youtube videos a week with the VP17 crashing on average 5 to 7 times in an 8 minute video, I hit the save key a lot. It takes me about 4 to 8 hours to edit a video. I think how much faster it would be if it was not crashing. I care nothing for the fancy video effects. I like the interface, I just wish it would not crash. I keep hoping Tech support will come up with a fix, but at this moment it seems like i am throwing money in a slot machine on a prolonged loosing streak and keep hoping irrationally for the big win. If I had a frequent open dialog with them it would help but feel like I am being played off with them hoping I get tired and give up and go away. if there was some hardware that would make a stable super beast of an editing machine, I would build it even know I just dropped about 4k on this editing box which should perform quite well after the exhaustive research I did before building it. Oh well. For the people that really tried to help me.. Thanks! for your time (and I mean that). For all others that immediately went on the defensive or just set out to subtly flame me and ultimately waste my time.. Oh well.. If anyone got any more ideas I am all ears because my ultimate goal is to make this thing work not stoke my ego or protect a platform with obvious issues.

Sylk wrote on 9/26/2019, 10:30 AM

You paid a product you can't use, you are legitimate to complain you, critique the product and asking solutions.
However, your case seems isolated, so it's complicated for us to reproduce it. The strange thing is that you get crash with various cpu and gpu setups.
I would like to see exactly what you are doing and what's happenning. If possible try to capture screen from start until the crash, and share it. Maybe a clue will appears.

fr0sty wrote on 9/26/2019, 11:12 AM

The red screen is definitely a GPU problem. There is something about the configuration of your hardware, drivers, system, media, and project (including everything from fx used to other things that are fx but aren't labeled as such, such as track motion and pan/crop) that are uniquely causing this issue to occur, and there's a lot of variables in there that can be the one culprit. We do know others with your exact hardware config do not have this issue.

Windows 10 fresh install doesn't affect it, so we can rule out the OS.

Vegas version update doesn't affect it, and the issue isn't present on other versions of Vegas running on similar hardware, so for the most part, that clears a good bit of what Vegas could be causing... however maybe we should dive deeper into exactly what media, project settings, preferences settings, decoder settings, encoder settings, fx used, even seemingly unrelated things like audio, something in there is triggering this to happen.

One thing that may help to isolate things is to try to edit media of a different kind from another source.

I can DM you a few clips from my cameras, if you like, and you can use those to test to see if you still get crashes. Try editing just those clips, and if you add any text or effects, only use what comes stock with Vegas. Let's see if you still have issues. That will help narrow down the culprit.

joseph-desaavedra wrote on 9/26/2019, 1:57 PM

Frosty, thanks..

There is yet a newer version of Studio Drivers now. will try that. Version 437.70 vs 437.86 using DDU from safe mode.

Also I will use the matching feature for "Match Media Settings button" to make sure I am using the proper project template for editing and playback.

I would very much like trying another media source if the above comes to nothing

I do not use many effects other than text cropping and key framing the crops and text and often cropping video, seems to make it worse. If you look at one of my videos you can see what I do is actually limited. I don't use the image stabilizer in VP I actually use resolve for that.

Joe d

joseph-desaavedra wrote on 9/26/2019, 1:59 PM

You paid a product you can't use, you are legitimate to complain you, critique the product and asking solutions.
However, your case seems isolated, so it's complicated for us to reproduce it. The strange thing is that you get crash with various cpu and gpu setups.
I would like to see exactly what you are doing and what's happenning. If possible try to capture screen from start until the crash, and share it. Maybe a clue will appears.

Hmm. perhaps I can use a video screen grab programs and make a video of me editing a video. I will work on that after I get through the two things I am going to try tonight. in my other answer.

Joe d thanks

joseph-desaavedra wrote on 9/26/2019, 2:04 PM

The red screen is definitely a GPU problem. There is something about the configuration of your hardware, drivers, syste

And that only happens when I set the Dynamic RAM preview max to something other than zero

fr0sty wrote on 9/26/2019, 2:48 PM

I usually use OBS studio to do screencaps of vegas bugs.

joseph-desaavedra wrote on 9/26/2019, 2:55 PM

thanks it has been since the early 90s since I did screen grabs and those were for game reviews. will give it a shot. doing a video right now with current drivers and project config with the automatic tool mentioned above.. fingers crossed.

Sylk wrote on 9/26/2019, 3:08 PM

There is yet a newer version of Studio Drivers now. will try that. Version 437.70 vs 437.86 using DDU from safe mode.

You mean 431.70 vs 431.86, right?

And that only happens when I set the Dynamic RAM preview max to something other than zero

Not matter. Set Dynamic RAM to zero means Auto, so Vegas use what it needs, so zero stays the best value.

joseph-desaavedra wrote on 9/26/2019, 3:14 PM

yes of course the newer one 431.86

I sort of figure that about the dynamic ram setting. don't know why it would default to 200.

j-v wrote on 9/26/2019, 3:22 PM

I sort of figure that about the dynamic ram setting. don't know why it would default to 200.

The program sets that amount to the default so you can see what a very smal portion of the timeline looks as was it was rendered out.
If you want to see a bigger part of the timeline you can increase it, but if you don't use that Dynamic Preview , as I always did and do, you can set it for ever on 0 and that saves RAM for other tasks ( as rendering or normal previewing).

joseph-desaavedra wrote on 9/26/2019, 3:33 PM

I don't want to get happy yet, so far it is behaving well although it is only a single track video if you do not consider the text. I am doing plenty cropping. Not my usual food video that usually is filmed with three cameras. Just a video about me cleaning my mower up after a hard day. I do enjoy editing when the editor does not crash..

joseph-desaavedra wrote on 9/26/2019, 3:39 PM

"but if you don't use that Dynamic Preview , as I always did and do, you can set it for ever on 0 and that saves RAM for other tasks ( as rendering or normal previewing)."

at risk of sounding stupid at this point in the game how do I know if I have it set to dynamic preview

j-v wrote on 9/26/2019, 3:51 PM

You have to switch it on, but "Selectively Prerender Video" or "" Render to New Tracks" do the same.

joseph-desaavedra wrote on 9/26/2019, 4:02 PM

mine is greyed out.

joseph-desaavedra wrote on 9/26/2019, 4:13 PM

well got my first crash, no crash report just stopped working so it is time to break out the screen capture program

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

mine is greyed out.

Because you have probably set it to o, try to set it to an amount and controle again.

joseph-desaavedra wrote on 9/26/2019, 4:17 PM

set it 1/3 of total ram and continue to be greyed out. pre rendering helps the playback for you?

joseph-desaavedra wrote on 9/26/2019, 4:19 PM

getting obs studio setup and then going back to editing

j-v wrote on 9/26/2019, 4:32 PM

set it 1/3 of total ram and continue to be greyed out. pre rendering helps the playback for you?

Do you have a selected region of one or two tracks with events?
I think it is much better for you to read the manual at least one time.😉

joseph-desaavedra wrote on 9/26/2019, 4:35 PM

yes and yes.. will do

joseph-desaavedra wrote on 9/26/2019, 4:44 PM

when I get done reading all 586 pages I will let you know. 😵

joseph-desaavedra wrote on 9/26/2019, 4:57 PM

well followed the directions and it is working, I was really not having playback issues, the hole thing was crashing randomly during edit. when I set a value to 0 for the dynamic ram it seemed much less prone to crashing. when I set it to a number higher than zero the system becomes more unstable. when the value is not 0 I will get blank screen and red screens in the playback window.

joseph-desaavedra wrote on 9/26/2019, 5:07 PM

it does look like a cool tool when you have a complex section

1 … 5 6 7 … 11

of 11