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

Sylk wrote on 9/26/2019, 5:32 PM

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

Except when it makes your Vegas unusable...

joseph-desaavedra wrote on 9/26/2019, 6:25 PM

Yes! and it does with me right now. no question. Thanks! whydat

joseph-desaavedra wrote on 9/27/2019, 5:58 AM

1: I like the dynamic RAM previewing feature, BUT, it does destabilize vp17 when enabled by increasing the dynamic RAM allowed above zero. I have 32 gigs of RAM so I do not think I am running out of memory. when enabled I get blank and red screens in playback. When I say destabilize I mean I am actually not using the feature, it is just enabled and the VP tends to crash more frequently. So I leave it at zero as changing the number one way or the other has no effect on quality of editing just makes VP crash more.

2: I am learning a lot of about VP17. Pre-rendering seems a little on a the useless side as you might as well just render the video and watch it. If you pre render and then start editing it you loose the pre-render (being smooth in preview, correct me if I am wrong. And I AM reading the manual before anyone says anything, unless I just can't read (which is possible). So unless someone can enlighten me, I don't get the pre render thing, makes no sense to use it where the Dynamic RAM preview does as it only take a few seconds to smooth it out, if it DID NOT make VP17 unusable. Now if I could pre render all my source file before I start a edit and I gained the the smoothness in playback and (god forbid) stabilize VP17 I am all for it.

Just some observations as I struggle with making VP usable and am between getting time sensitive videos out. And reading the directions (something I think any good software should not need)

Joe d

Kinvermark wrote on 9/27/2019, 11:48 AM

Agreed. Thre previewing tools in Vegas need some improvement. Dynamic RAM previews are completely temporary and do cause some users to have stability problems. I have found them unreliable for composited video (titles, etc), so tend to avoid them. The selective pre-render is similar to caching in other NLE's except that it is not automated, and is too twitchy - one change and you need to re-render the whole timeline.

joseph-desaavedra wrote on 9/27/2019, 12:42 PM

as I learned yesterday. Might as well leave the dynamic ram limit to zero.

Kinvermark wrote on 9/27/2019, 12:48 PM

How is timeline playback performance now that you have a 2080ti installed?

joseph-desaavedra wrote on 9/27/2019, 1:07 PM

a little better, but I was expecting more, if you got a lot going on it will still drop the frame rate, speeding up video takes the most toll. For the amount of money it is probably was not worth it for the gain from the 1660 TI. If I had to give it a number, I would say I gained about 20%. Still got the same crashing issues though that has plagued me from the beginning. Clean windows 10 install improved things some, but still slogging through tech support. They have gone unresponsive for days now.

Sylk wrote on 9/27/2019, 2:31 PM

@joseph-desaavedra

Any new about screencap of your work until crash?

SuperG wrote on 9/27/2019, 2:34 PM

a little better, but I was expecting more, if you got a lot going on it will still drop the frame rate, speeding up video takes the most toll. For the amount of money it is probably was not worth it for the gain from the 1660 TI. If I had to give it a number, I would say I gained about 20%. Still got the same crashing issues though that has plagued me from the beginning. Clean windows 10 install improved things some, but still slogging through tech support. They have gone unresponsive for days now.

Interesting. I was just recently looking for a boost in GPU performance over my old (OEM) GTX 745. I researched the latest Nvidia cards and selected a 1660 Ti as giving the most "bang" for the buck. It's working pretty well, nice "boost" for me.

joseph-desaavedra wrote on 9/27/2019, 2:53 PM

I liked the card.. I was pursuing this crash issue and it seemed a good excuse to buy a faster cards. What I read was playback was better and it is. But not all that much. Hopefully as they develope VP it will get better. I wanted to rule that card out For the cause of crashing. 1160 is great for the money. It will find its way to another machine

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

@joseph-desaavedra

Any new about screencap of your work until crash?

I did not run it last night. I run one my video next week. I did get the screen grab program setup last night

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

still crashing.. tech support as far as I am concerned does not exist..To say that VP has tech support is a gross misrepresentation..they have been zero help.. and I mean zero.. am reduced to trying vodo tricks like going into the developer menu and disabling so4. Who in the world really knows what that does. When the only help comes from crap yard films it is a dark day. This is depressing.

Sylk wrote on 10/3/2019, 4:03 PM

Still not screencapture? What email do you use to contact support?

j-v wrote on 10/3/2019, 4:13 PM

still crashing.. tech support as far as I am concerned does not exist..To say that VP has tech support is a gross misrepresentation..they have been zero help.. and I mean zero.. am reduced to trying vodo tricks like going into the developer menu and disabling so4. Who in the world really knows what that does. When the only help comes from crap yard films it is a dark day. This is depressing.

Are you ready now complaining about a good program, but propable not for you as YT-er, like many others, who know nothing or too little what real editing needs. 😬😿

joseph-desaavedra wrote on 10/3/2019, 4:33 PM

Still not screencapture? What email do you use to contact support?\

support@magix.net, they sometimes answer me by asking for more info and then that's the last I hear from them, I made a new ticket out this morning. I have not done a screen grab yet, the last crash was while using velocity envelopes. its pretty random. Just frustrated.

joseph-desaavedra wrote on 10/3/2019, 4:35 PM

still crashing.. tech support as far as I am concerned does not exist..To say that VP has tech support is a gross misrepresentation..they have been zero help.. and I mean zero.. am reduced to trying vodo tricks like going into the developer menu and disabling so4. Who in the world really knows what that does. When the only help comes from crap yard films it is a dark day. This is depressing.

Are you ready now complaining about a good program, but propable not for you as YT-er, like many others, who know nothing or too little what real editing needs. 😬😿

If you were more coherent, I guess that is an insult? why are people in this group so defensive but offer little substance.

joseph-desaavedra wrote on 10/3/2019, 5:23 PM

But you can rest assured I love this editor or I would not fuss so much.. Like a hot chick that just won't act right.

Sylk wrote on 10/3/2019, 5:34 PM

Are you ready now complaining about a good program, but propable not for you as YT-er, like many others, who know nothing or too little what real editing needs. 😬😿

So, explain him "what real editing needs" to make its Vegas workable.🙂 I'm pretty sure he will stop complaining when you'll solve its problem with this good program he paid but he can't use 😉

Kinvermark wrote on 10/3/2019, 5:42 PM

@joseph-desaavedra

Hi again Joe,

Isn't Vegas 16 stable for you? IIRC, you said it was, so I am surprised to see you struggling with V17. Is there something particular you need from V17 to complete your YT videos?

joseph-desaavedra wrote on 10/3/2019, 6:09 PM

@joseph-desaavedra

Hi again Joe,

Isn't Vegas 16 stable for you? IIRC, you said it was, so I am surprised to see you struggling with V17. Is there something particular you need from V17 to complete your YT videos?

when I did a clean install it seemed to stabilize some but will still crash. Then the next build came out and I was trying to work with it and perhaps get it working good all the time. I would get occasional crashes in 16 maybe one every second or third video. I see what you are saying. why do I just not revert to 16? actually nothing special for YT, I really don't do anything fancy no color grading or even image stabilization. If I need stabilization I just throw it in resolve render and finish in VP. I just like the work flow in VP. What kept me in 17 is that the behavior improved when I clean installed my OS making me think perhaps I was missing something on my end. I thought starting fresh with tech support on a clean system, they might have some help for me, but as you see they totally go incommunicado with me when ever we get down to the meat and potatoes of this. We never get past me sending the error report and detailed system information.. after that they go dead stick on me. Makes me feel like tech support has not a clue.

Kinvermark wrote on 10/3/2019, 6:31 PM

Because your issue is unusual, the only way to move forward is to figure out how to replicate the crash (or crashes). If support cannot replicate the issue, then it becomes a dead end. Hopefully, at some point some bit of evidence will come to the fore that will allow someone to reproduce the problem. I tried your test media on V16 and didn't see an issue.

Besides going back to V16, all I can suggest is to take careful note of what you were doing when crashes occur.

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

yeah, I understand that, though perhaps they could correlate crash with the system information but it would be nice if they would communicate with me, but I do not even get that respect.

Sometimes it is during cut and paste other times it is just making a cut, others is just during playback, and seems worse with mutiple video tracks. I can find no common thread, I thought I was on to something with the dynamic RAM rendering, but it seems does not matter if it is off or on. They are less frequent since doing a clean OS install with network unplugged to keep win10 from installing drivers. I was not able to use 17 at all before this.

Sylk wrote on 10/3/2019, 7:50 PM

Windows 10 WinUpdate is the Evil ; it does upgrade or downgrade GPU drivers without our consent... In two words, a GPU rape. Block it for one month and reblock it every month.

With a screencapture, you and we could try to reproduce exact op you do, and see if it's really random.

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

Windows 10 WinUpdate is the Evil ; it does upgrade or downgrade GPU drivers without our consent... In two words, a GPU rape. Block it for one month and redo it every month.

With a screencapture, you and we could try to reproduce exact op you do, and see if it's really random.

will do, I got to make a shop video tomorrow will see about getting the screen grab thing working

1 … 6 7 8 … 11

of 11