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

Grazie wrote on 8/28/2019, 10:31 PM

@joseph-desaavedra - I really have to applaud your tenacity. My reading between the lines here, it appears it’s no longer about a refund, it’s more about you wishing to at least get the same responsiveness as you pleasurably experienced with VP14. I also bet that MAGIX when reading this thread is also frustrated, they’d have to be. JD, I truly feel for yah.

joseph-desaavedra wrote on 8/28/2019, 10:59 PM

Man! thanks I care nothing for the refund. I just want it to work, it is an easy platform to make my Youtube videos, I make two to three a week as a hobby, I have been using this for the majority of the videos and just do not want to have to learn another program. My sister uses Davinci for her channel and I have been looking at it and it is stable as a rock on my machine, I just am so used to Vegas I do not want to interrupt production. I did a food video tonight, I used three cameras and it crashed 6 times before I was done making a 5 minute video. My Channel name is Joe is hungry if you want to see the editing..Yeah I do not let the subtle flaming bother me, I have been very through trouble shooting and have extensive experience with computers dating back to 1997. But I am not perfect and miss things and perhaps someone will say hey did you try this and then the light bulb might go on in my head. I think it is an issue with NVIDIA drivers and VP and they are not admitting it.. No matter, I got a good AMD GPU coming to see if it will work. The GPU will cost me way more than the cost of VP.. thanks. nice to hear kind words.

j-v wrote on 8/29/2019, 7:14 AM

@Howard-Vigorita

To eliminate the Intel gpu as a suspect, you might want to go into your motherboard bios and see if you can disable the Intel internal gpu and see if that makes a difference..

Is it not easier and with the same result to deactivate that one in the Configuration screen?

fifonik wrote on 8/29/2019, 3:48 PM

OP does not have Intel iGPU as he has AMD + NVidia, so only one GPU is in the system

joseph-desaavedra wrote on 8/29/2019, 9:07 PM

My laptop is similar to your system with an Nvidia 1050 Ti and an Intel uhd630, albeit with an Intel cpu. I've noticed there's quite a bit of interplay between the gpu's at the driver level so Vegas' gpu settings may not be totally controlling. For one thing, the Nvidia Control panel apparently controls which gpu is presented to applications as the default gpu... you might want to check with it and switch whatever its set to and see if that changes anything in Vegas. Also, you don't mention which gpu you set Vegas to in settings/video... I get awful results if I set that to Intel... suggest you keep it set to Nvidia. Also in the settings/io, setting that to Intel might make a difference with the error you are getting. There's also a couple of checkboxes in settings/general that pertain to gpu usage as well as another one in settings/deprecated you might want to play with. If you're crashing on playback rather than rendering, also try looking at the gpu checkbox in settings/preview.

Regarding the Intel drivers. I've noticed that some of the latest versions, particularly ones the come directly from Intel or Windowsupdate instead of your motherboard maker, tend to step on the openCL interface shared with Nvidia as well as AMD boards I have in other systems. If you've gotten a driver from Intel, suggest you revert back to the one from your motherboard maker. That'll also protect you from WIndowsupdate overwriting the driver with an Intel-sourced one. To eliminate the Intel gpu as a suspect, you might want to go into your motherboard bios and see if you can disable the Intel internal gpu and see if that makes a difference... it should simplify things for Vegas and the Nvidia driver by making the Intel gpu invisible to them. Also, Win10 build you mention may be an older 1809 version. At least make sure it's up to 17763.720. I'm using 1903 18362.295 on all my systems. Also make sure that all your .NET stuff is up to date as applications like Vegas use that extensively.

joseph-desaavedra wrote on 8/29/2019, 9:19 PM

1: I have set the NVIDIA control panel to point at the 1060 TI.

2: I do not have an intel GPU or any other integrated GPU to disable and it does not show as an option in VP,not sure why people keep thinking I have an integrated GPU

3: My OS is current as of today, it just rebooted to the new version. Plus when I did a clean install of OS last week on another partition is was up to date and behaved just as bad. It was a clean install with minimal apps installed in an effort to isolate the problem.

4: there is one GPU to choose from in VP, as I only have one

5: I am going to put a AMD based GPU in the system to see if anything changes I will do this tomorrow and see what what. Gigabyte Radeon Computer Graphics Cards (GV-RXVEGA64GAMING OC-8GD) to be exact, I think it will have a little more kick that the 1660 TI as least from the Vegas bench marking I saw. I can return it if it does not pan out, I am at a point where I need to rule out the GPU as the issue. Hopefully AMD talks better to VP than NVIDIA. I have never really got an answer about that. I am just throwing thing at the wall and see if it sticks.

6: I had experimented as suggested with the VP IO check boxes little to no change

Joe d

joseph-desaavedra wrote on 8/29/2019, 10:06 PM

ah was wondering..hope the new card makes everything better although it will take a while to know as I do not have a video to do right now. I just released one to you tube today.

joseph-desaavedra wrote on 8/29/2019, 10:07 PM

I will you know try to crash it as soon as I get it in. 😬

joseph-desaavedra wrote on 8/30/2019, 7:46 PM

well Got the AMD Vega 64 video card installed, took drivers out with DDU in safe mode, wish me luck.. will let you all know what happens, won't be making a youtube video till next week as I have a day job I make a living with, Thanks you all for helping me.

joseph-desaavedra wrote on 8/30/2019, 7:48 PM

does 17 load .veg files a lot slower than 16 when loading a project?

Vegas_Sebastian wrote on 9/2/2019, 1:50 AM

does 17 load .veg files a lot slower than 16 when loading a project?

It is a known bug. Will be fixed in next update.

joseph-desaavedra wrote on 9/3/2019, 1:56 PM

sebastianS wrote on 9/2/2019, 2:50 AM

thanks.. it also helped going to the File I&O section and switching hardware decoder to NVIDIA NVDEC away from intel and turning thumbnails off. Don't use Thumbnails anyway. Am going to shoot weekly video today will let you know how it goes, will do NVIDIA vs AMD card too if continue crashing during edit and let you know. do you know if they are going to include hardware encoding support for the vega card in next update and any idea what the time table is for the update?

joseph-desaavedra wrote on 9/3/2019, 10:43 PM

preliminary update

17 crashed tree times with 1660 TI on this edit, changed to the AMD Vega Card (previously listed) and crashing has stopped for now..still editing..

joseph-desaavedra wrote on 9/3/2019, 10:53 PM

well from my trouble shooting over the last few weeks, my preliminary conclusion, defect in my 1660 TI or unresolved issues between VP17 and NVIDIA (I vote for the later) I hope they fix it because I would rather use NVIDIA..

joseph-desaavedra wrote on 9/3/2019, 11:16 PM

well jinxed myself by jumping to early conclusions. crashed with AMD install, oh well back to the drawing board, it does not like to do multicam. Buggy software will be the end of me.

fr0sty wrote on 9/4/2019, 1:20 AM

What source media are you using? Forgive me if already posted, I looked and didn't see it, but can you download mediainfo and post the report it gives on each different type of media used in your project (i.e., if you have more than one type of camera, a mediainfo report for each type's file).

Also, what are your project settings?

It's more complex than "it doesn't like to do multicam". I recently edited a 2.5 hour long 5 cam 4k multicam project with no issues (aside from the thumbnail bug we've already gone over how to fix, that's how I discovered it existed).

joseph-desaavedra wrote on 9/4/2019, 2:15 AM

Thanks Frosty, I will see about getting it together and try to be more systematic on working through this. at least I know it is not the video card (AMD vs NVIDIA) at present. What I want to do for myself is go back through the windows crash reports again and see what else is running. I suspect I have another very old program (jpeg viewer) possibly interfering but need to look. the cameras are two Canon G7X mk2s and a Cannon SL2 Rebel But you asked for the media type which I will get. I have to limp through the rest of this 5 minute video and get it posted first :)

Yeah I just turned the thumbnails off..

Sylk wrote on 9/4/2019, 2:36 AM

on each different type of media used in your project (i.e., if you have more than one type of camera, a mediainfo report for each type's file).

Hi @joseph-desaavedra

Perhaps an other way to target the wrong thing;

- save a copy of project
- open it
- delete one media from this project copy
- save it
- close it
- reopen project copy
- delete the next media
- save
- close
- reopen
- ... continue like that for each media, until you don't get crash
-> this could target the problematic media

joseph-desaavedra wrote on 9/4/2019, 2:49 AM

will give it a shot. So you are on the thought process that is one of the media's?

joseph-desaavedra wrote on 9/4/2019, 2:51 AM

for my music sound track does it matter whether I use mp3 or a wav file?

joseph-desaavedra wrote on 9/4/2019, 2:53 AM

I will get my video posted in the morning and try to isolate that way then with the project file

joseph-desaavedra wrote on 9/4/2019, 3:12 AM

did the open save thing, when I removed all video it finally did not crash. removing just anyone of them it always crashed..its late here I will continue tomorrow any video added it goes red screen and crashes every time.

Sylk wrote on 9/4/2019, 5:17 AM

any video added it goes red screen and crashes every time.

Added in Timeline or just in the Project Media list?

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

timeline

1 2 3 4 … 11

of 11