A suggestion please - constant crashes with GPU

adimatis wrote on 3/29/2019, 4:49 AM

Hello Friends,

This is my first post here, so I want to say HI to you all and all my best wishes!

Please advice, I am using VP16 b361 and I have serious difficulties in using GPU with Vegas.

It must be all in relation with GPU acceleration, as without it, the program runs smoothly and stabile.

But with GPU, Vegas behaves funny, either with Intel UHD 630 or with dedicated 1050ti. With Intel less so, but I still have occassional freesez. With 1050ti, EACH time when I quit the programme, even if it doesn't crash while editing, the crash window comes up and tells me the nVidia driver caused an unexpected error. Then, sometimes, during the editing, the programme hangs and that's it. But not always, it was the case that I could edit for hours and no problem (atually I thought b361 fixed the issue) but eventually I get to the same situation.

Of course the Live Safe is on, so I don't loose work, but it is indeed frustrating to suffer these hangs, many of them within 1 minute after opening the program. But like I said, these are not reproductible, as far as I observed.

Of course I have red many posts here about what to do and I tried many solutions I found over internet. Really, nothing worked except for turning the GPU acceleration off, which defeats the purpose... I bought a new laptop just to be able to use GPU and to increase the work efficiency. My system: ASUS GL703GE - WIN 10, CPU 8750h, 16 Mb RAM, 512 SSD as C drive, NVidia 1050TI.

Now, my question is (actually two questions):

1. Would WIN7 work better? I could go back to it, but I am not sure this would solve much... Maybe you ave some experience with this...?

2. Is there any way AT ALL that GPU works properly, or should I make peace with myself and wait for a undefinite future when new drivers or new build will solve the problem? :)

Thank you very much and all the best!

Adi

Comments

j-v wrote on 3/29/2019, 5:46 AM

Answer to 1: No

Answer to 2: Yes

My laptop from signature has a little weaker processor than yours but for the rest it is almost the same and it works for me very good.
My advice for you is

1. Download the latest Driverversions for both GPU's,
for Nvidia that is the 419.67-notebook-win10-64bit-international-crd-whql.exe
for Intel that is the dch_win64_25.20.100.6577.exe

2. Through the Configurationsscreen/All programs
- uninstall all you can find of Nvidia and install the newest drivers only you downloaded before and don't let Windows restart before and after
- uninstall all you find of Intell and install also that downloaded newest one.

3. Restart Windows now

4. Rightclick the startpic of Vegas on your desktop and let that program start with the integrated (Intel) GPU

5. Set for GPU acceleration in Vegas Options/Preferences/Video your NVidia as used GPU.

With me these precise settings give a very smooth and fast working Vegas Pro 16 361.

!!! Don't let your laptop restart before and after installing the newest drivers otherwise Windows sets its own drivers that cause that nasty error popup after you closed the program. ( Windows than installs also AMD drivers at C:\Windows\System32\DriverStore\FileRepository\nvami.inf_amd64_xxxxxxxx, you cannot delete)

Good luck!

adimatis wrote on 3/29/2019, 6:30 AM

Well, thanks a ton. :) I will try these. I will report back.

adimatis wrote on 3/29/2019, 2:31 PM

So, I tried to follow the procedure, but after uninstall the old drivers, it wouldn't let me install the new ones without a restart first. Doing so, I ended up with the newest drivers - the ones you mentioned - but I am afraid I failed in preventing Windows to add whatever it adds to it...

As I still got the error message when exiting Vegas:

Problem Description
Application Name: VEGAS Pro
Application Version: Version 16.0 (Build 361)
Problem: Unmanaged Exception (0xc0000005)
Fault Module: C:\Windows\System32\DriverStore\FileRepository\nvamci.inf_amd64_5a7a47ad0f59234f\nvoglv64.dll
Fault Address: 0x000000006D6E7BF9
Fault Offset: 0x0000000000AF7BF9

Fault Process Details
Process Path: C:\Program Files\VEGAS\VEGAS Pro 16.0\vegas160.exe
Process Version: Version 16.0 (Build 361)
Process Description: VEGAS Pro
Process Image Date: 2019-01-07 (Mon Jan 07) 16:54:52

But I plan to go through the procedure again and see what I end up with, eventually! ;)

Thanks again, I will post again my findings!

Adi

adimatis wrote on 3/29/2019, 3:34 PM

I tried again.

After uninstalling "original" nVidia driver - 399.24, the folder nvam.inf_amd64_9b1341e92276ee7c is gone.

So, without restarting, I want to install driver 419.67. It is getting to "checking system compatibility" when guess what? Folder nvam.inf_amd64_9b1341e92276ee7c is showing up again in the FileRepository and nVidia Control Panel shows me that driver 399.24 was installed again. Then, it tells me I have to restart if I wanted 419.67 to continue installing.

It seems Windows does not allow me to install directly the latest nVidia, but rather goes through the "default" driver, which seems to be embedded somehow and only after that would allow advancing to the newest driver.

Boomer.

I wonder how did you do the install of the latest nVidia? And are you saying you managed to install the driver without having the C:\Windows\System32\DriverStore\FileRepository\nvami.inf_amd64_xxxxxxxx installing as well?

Thanks!

j-v wrote on 3/29/2019, 5:18 PM

Do you installing this Nvidia driver?

And after restart of Windows did you through rightclick set which GPU the program starts? It must be the Intel, because I can trigger that error by starting it with the Nvidia.
The Nvidia is the one you have to set in Vegas at Options/Preferences/Video.

This is the way you can set which one the program starts

adimatis wrote on 3/30/2019, 1:34 AM

Jan, thank you for trying to help!

Yes, it is indeed the Creator Ready driver.

I do start Vegas with Intel and I do choose 1050ti in the GPU acceleration in video window of the menu.

Except for not being able to install the newest nVidia driver without a restart, as I explain in the previous post, I followed the steps closely. But like I said, I find curious that 419 will not install directly without going through 399 first...

Another funny thing:

The previous

C:\Windows\System32\DriverStore\FileRepository\nvami.inf_amd64_ xxxxxx

became

C:\Windows\System32\DriverStore\FileRepository\nvamci.inf_amd64_xxxxxx

and it still produce the error at quiting Vegas.

Thanks again for being ready to help. I will need to continue the quest for a solution! ;)

j-v wrote on 3/30/2019, 3:23 AM

Because I can trigger it by switching to the other starting GPU (in my case to the NVidia) maybe that switch is causing it and can you try out swiching a few times and in between control the behaviour of that error.
1 minute ago I did it again and the AMD dll is stil present at my Windows installation, but with me Vegas has no troubles when starting with the Intel.

Here is my screenshot of the last triggered error.

adimatis wrote on 3/30/2019, 4:36 AM

:) Go figure...

I decided to give up on fighting with the nVidia driver update. So, I clean everything, using Display Driver Uninstaller and I decided to just let it do it's thing.

So, Windows reverted by itself (like I said, I think this is the "default" driver in Windows 10 now) to 399.24.

I had updated the Intel driver yesterday, so that one is at latest version.

I open Vegas and I enabled 1050ti in the GPU acceleration.

I started editing and... all is good. Of course it is still too soon to be completely sure, but I had no freezes neither glitches in the last two hours, and when I quit Vegas no error message anymore. And this is after several restarts, so I am hopeful.

To me, it seems there was some sort of error between the old 399 and new 419 driver installation, even though I use "clean install" each time. Or maybe that was the problem... Anyway, fingers crossed and heart up!

If all goes well this time, I plan on NOT updating nVidia driver EVER - well, unless I need to. I will report back here, as some others might have had the same problem. And I hope the future updates, either Magix or Microsoft or Intel or nVidia will rather help things not mess them up worse. ;)

Jan, thanks again a million. You're a good guy! I appreciate the help!

Adi

j-v wrote on 3/30/2019, 5:01 AM

👍 Good to know you find for you the best way to work.
The only difference I saw between 399 and 419 driver is a litle difference in rendertime for the Magix HEVC with NVenc .In the older one the QSV option renders the fastest and in the newer one the NVenc option renders faster than the QSV and also pretty faster than in the older one.
And because I do now all the renders for myself in HEVC I made my choice for the newer one.
Have a good time and happy editing with Vegas!

karma17 wrote on 3/30/2019, 5:11 AM

Awesome job j-v and welcome to the forum adimatis, This is how things should work!. You have a problem and politely state what it is, someone is nice enough to help you, and however, the issue is resolved. I have always had the opinion that for every problem you hear about on this forum, there are a 100 people not having that problem, but unfortunately, if people aren't having a problem, they don't post about it. Any way, welcome!!!

Dexcon wrote on 3/30/2019, 5:48 AM

@karma17

Your comment is a well-considered, respectful, polite and professional comment - as they always have been on this forum.

At times on this forum, posts from owners/managers of production companies (as well as others), their 'hostile/aggressive' posts demonstrate a lack of tolerance and professionalism that borders on the incredible in a business environment. I sometimes think about what it would be like to be an employee at one of these businesses where the 'boss' evidently lacks such a level of self-control when dealing with a supplier. What are they like when dealing with their employees and/or clients?

Many people are managers/team leaders/etc but, in my experience, not all that many are good managers.

adimatis wrote on 3/30/2019, 5:54 AM

Thank you guys, and I appreciate your support! Yes, absolutely, a good forum is a positive and constructive arena and we are all here to help each other, as we can. Some more than others... ;) After all, we are all in the same area of interest and why not create a nice meeting place, for everyone's benefit!

Unfortunately, I am afraid I was too quick to tag a solution, sorry. Even though I do not get the error message anymore, when closing Vegas, the unexpected freezes seems to still be here. :( No error message, simply a freeze. Random, no way to determine what caused it.

Well, I will be continuing to try some other solutions, maybe... But what is for sure is that LIVE SAVE is a tremendous feature and an (almost) acceptable trade, I would say! Kudos for that one! ;)

Thanks again!

Best wishes,

Adi

NickHope wrote on 3/30/2019, 9:17 PM

...Then, sometimes, during the editing, the programme hangs and that's it. But not always, it was the case that I could edit for hours and no problem (atually I thought b361 fixed the issue) but eventually I get to the same situation...

...Unfortunately, I am afraid I was too quick to tag a solution, sorry. Even though I do not get the error message anymore, when closing Vegas, the unexpected freezes seems to still be here. :( No error message, simply a freeze. Random, no way to determine what caused it.

What type of footage are you editing and how was it created?

Part 2 of this post shows how to know which decoder is being used. If so4compoundplug is decoding your footage, try disabling it. My Vegas Pro 15 (build 416) and 16 (build 361) have been hanging quite frequently when cutting Panasonic GH4 AVC footage, and this seems to have helped, although it's too early to be sure.

AVsupport wrote on 3/31/2019, 7:07 AM

I have turned my iGPU off (Bios). This helped me stabilize my system

adimatis wrote on 3/31/2019, 12:40 PM

Thank you Nick for your advice, indeed I have a Panasonic G85 camera and while I also edited recently some Canon C100 footage, most of the work I do is Lumix... So, I will pay attention if that's the problem! Thank you for your suggestion! :) Appreciate it!

AVsupport, thank you, but I am afraid my Asus' BIOS is rather simple and does not offer many options... I cannot disable GPU, neither of them, I have thought of doing that.

Thanks guys!

Adi

adimatis wrote on 4/3/2019, 4:54 AM

I just wanted to drop another short message saying thank you, as it seems now I have much less freezes, actually none so far in the last... 10 hours of editing, over two or three separate days of work. That should be a good sign.:)

So, just to conclude this discussion - it seems the reason why I got the error message on exiting Vegas was because of the driver conflict. The solution was to revert from the latest driver to driver 399.24 for nVidia 1050ti and to update the Intel driver to the latest. No errors anymore.

The random freezes during the editing seems to have something to do with the so4compoundplug, which I deactivated and so far so good. Not to say this will solve all the freezes, of course that would be way too soon and too much to say - but I am happy for now. :)

Thank you all again for your support and happy editing!

Adi

joost-berk wrote on 4/8/2019, 3:41 AM

I was just looking for this solution. Because I have the same issue with the new editing laptop! I will try this solution right away! Cheers!

adimatis wrote on 4/9/2019, 1:10 AM

For me, these two fixes work great.

Had only have one freeze in the last 20h editing, but that was for some other reason.

So, it works. :) Thank you again guys!

Adi