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

fr0sty wrote on 11/15/2019, 8:08 PM

There could be a number of things, including issues that exist outside of Vegas in windows or even hardware malfunctions causing your issue. Being that your case isn't widespread and easily repeatable, it is difficult to diagnose exactly what is causing it.

fr0sty wrote on 11/15/2019, 8:14 PM

This is old, for Vegas 13, but it could help.

joseph-desaavedra wrote on 11/17/2019, 7:18 PM

This is old, for Vegas 13, but it could help.

Saw it..did it... didn't t work.. way back in the beginning when I first started having the issue. Even before I came to the forum. thanks for trying.

joseph-desaavedra wrote on 11/17/2019, 7:30 PM

There could be a number of things, including issues that exist outside of Vegas in windows or even hardware malfunctions causing your issue. Being that your case isn't widespread and easily repeatable, it is difficult to diagnose exactly what is causing it.

Actually Tech Support Acknowledged it was an issue with multiple users, having machine with high core counts is causing the Video Card to crash and are working on it although the newest build 353 turned out to be unusable for me. Obviously they did something that did not work for me. At least they finally talked to me.

I found a copy of the previous build and downgraded and continue to do proxies and the crashing has almost completely stopped. (as long as I proxy all video basically decompressing it before editing)

I blocked Vegas through the firewall to get rid of the annoying upgrade popup to next build.

I have trouble shot my hardware until I needed CPR. I just have trouble beating that dead horse anymore. Only time will tell if tech support and the developers will ever get it fixed.

Thanks for responding Fr0sty..Your a good guy.. I just want to edit videos and get past all this.

joseph-desaavedra wrote on 12/13/2019, 4:08 PM

well... update... no fix.. just closed trouble ticket out again with out communicating with me. no fix... tech support.. wow...right...I guess this is finally end game..perhaps they will accidentally fix the crashing issue on a future update.. not holding breath..tech support...wow..that's all I can say ..wow.. and not in a good way.

joseph-desaavedra wrote on 12/19/2019, 6:02 PM

another trouble ticket getting started, so they can ignore me and eventually close the ticket with fixing nothing

Vincent-Mesman wrote on 12/21/2019, 4:06 AM

Thank you (all) for taking the trouble to find the cause of all this. This thread is interesting in so many ways.

High core counts have been mentioned on this page. Just wanted to say that Vegas is not the only application that has problems with this. I've seen problems with 3D rendering in combination with high core counts (Ryzen Threadripper) that could be solved by disabling cores or limiting the number of threads.

Indirectly this thread has answered my question, to upgrade or not to upgrade. I will upgrade my VP14 to VP17 this weekend, but for now I'll wait with any hardware upgrades until Threadripper and nvidia related issues are solved for all other applications as well.

joseph-desaavedra wrote on 12/25/2019, 9:32 AM

Thank you (all) for taking the trouble to find the cause of all this. This thread is interesting in so many ways.

High core counts have been mentioned on this page. Just wanted to say that Vegas is not the only application that has problems with this. I've seen problems with 3D rendering in combination with high core counts (Ryzen Threadripper) that could be solved by disabling cores or limiting the number of threads.

Indirectly this thread has answered my question, to upgrade or not to upgrade. I will upgrade my VP14 to VP17 this weekend, but for now I'll wait with any hardware upgrades until Threadripper and nvidia related issues are solved for all other applications as well.

Interesting to know that this is not the only editing package with the issues. Too bad tech support failed me on so many levels. Fortunately they did let it slip what the true issues were before shutting my trouble ticket out yet again with no hint of timeline for a fix after telling me they would leave the ticket open. Perhaps I will down grade to 14 and see what happens. If I knew of a similar NLE without these issues I would move.

joseph-desaavedra wrote on 12/25/2019, 9:47 AM

On second thought I have tried disabling cores and or limiting threads to add stability and got nothing for my troubles. All I have is the word of tech support that the issues have to do with cores vs NVIDEA issue (and with their behavier and lack of responsiveness) I sort of question that although it kind of makes since in a way . The only thing that has added any stability over these many months of tribulations (and that is not perfect) is to pre-render prior to editing session (in the case of VP it is called Proxy). None of the many fixes and trouble shooting guides and fixes and advice from this group have helped.

j-v wrote on 12/25/2019, 12:00 PM

is to pre-render prior to editing session

That's not is pre-rendering, but with a proxy the videopart is renderd to a XDCAM EX file with much lower proportions to make it easier to read and to decode.
With pre-rendering as it is called in Vegas you can render a part (region) of edited files into whatever codec and template you are able to choose.

joseph-desaavedra wrote on 12/25/2019, 1:49 PM

yes, but it points to the decoding of video to the preview screen as being the source of the crashing what ever vernacular you want to use, it bypasses normal decoding on the fly while editing which seems to be the source of the crashing and according to tech support an issue with core count vs NVIDEA I have worked so long on to fix, and to date no closer to resolving.

I am familiar with the what VP calls pre-rendering as I use it frequently (useful tool) but has no effect on the frequent crashing turned on or off as suggested as a fix months ago.

joseph-desaavedra wrote on 1/3/2020, 9:02 AM

well did the latest build and got crashing again even with proxy, did get improvement in crashing after making the preview output 30 fps rather than matching the 60 fps in the source video files, but newest version still crash prone. submitted multiple crash reports to tech support after having to open my case yet again. I reverted back to build 321 and dropped fps in preview window to 30 fps stopped doing proxy (which eats a serious hunk of editing time) and did not have a single crash when editing a video last night. so until they fix this thing, I am stuck on build 321. Hopefully they are focused on making the base package stable rather that messing around with the whistles and bells and other useless gimmicks like warp.

joseph-desaavedra wrote on 1/14/2020, 10:07 PM

Thank you all for your help... but after many months and the absence of tech support, I am done with this NLE if you can even call it that. Perhaps years ago this was a stable well supported platform but from my point of view this is just not the case. I am looking for something stable, something that does not exist in this platform. I am tired of holding my breath thinking the next update will fix things. The Joke is on me.

joseph-desaavedra wrote on 2/14/2020, 10:31 AM

This Thread seems pretty dead now and if anyone comes across this in the future I would like to let folks know how it ended. After many months of trying to resolve this crashing issue and enduring frustration the issue has to do with decoding video while in preview mode during the edit and using multiple text video streams during edit. The fix is once you realize what you are doing that plays on the instability of this NLE avoiding doing it as the flaws in this application are sadly not going to be fixed anytime soon as far as I can tell. I will tell you what I do to mitigate crashing while editing. Another thing I have learned over the past year or so is that it is not an issue of if your NLE including this one is going to crash it is a matter of when. It will crash.. that is a fact.

1: When using multiple video streams in a single time line for credit rolls ect. get the job done, render it and then restart your project and ad it in. sort of compartmentalize your project

2: Set the preview window to the lowest frame rate you can tolerate no matter the source files are.. Source 60fps preview window 30fps. None of the other suggestions and there are many had any effect like setting the the dynamic RAM preview to zero and on and on. Can't tell you how much time I wasted working through all these "Voodoo" fixes. The Guy that has a Youtube channel called "Scrap Yard" or what ever is totally full of crap.

3: start with a clean install on windows 10 and all drivers current. After so may crashes Vegas 17 became corrupted and there is no 100% way to remove it from your computer that I have found. Vegas Gets a total Fail for not having a way to completely and cleanly uninstall their product. If anyone tells you different they are sadly incorrect. Vegas!!! if you see this SHAME on you...No one should have to edit the registry to get you stuff off their system

4: if you are new to the game of editing and have misgivings about the NLE you have... move on.. the longer you use it the harder it is to learn another.

5: when you do ask for help, be thick skinned as most people in forums are defensive and sometimes counter productive spending more time flaming you or just being irrelevant in there comments, good information can be obtained from forum trolls.

Those are the only things that actually helped. I use Build 321 as everything after that so far was very unstable. This only version of vegas I have used that was more stable was version 13 when Sony Still owned it. So this is my opinion after all these months of frustration and research trial and error.