[RESOLVED] "ERROR: Failed to create CUDA contex" - DGDecNV 32bit

[admin]

You could try this hotfix driver, too.

http://nvidia.custhelp.com/app/answers/detail/a_id/4378

According to this, it reverts behavior to the level of the previous 376.33 version, so it may fix your issue (or not).

https://forums.geforce.com/default/topi ... er-378-57/

It's obvious that driver version 378.49 had a lot of issues. The PhysX issue is mentioned too.

[Selur]

tried the hotfix drivers, issue is still present.
So I'll stick to 376.33 and test the next version.

Cu Selur

[admin]

Sounds good, Selur. Thanks for your testing and I'm happy you are back in business.

BTW, you can tell Windows update not to include 3rd-party drivers. I do that and don't automatically upgrade. I upgrade only when I have to: to support a user or to get a feature I can't live without. Ann Landers definitely got it right: "If it ain't broke, don't fix it."

[Selur]

I normally try to keep my drivers up-to-date since in example NVCEncC often only works properly with the latest drivers installed.
Hopefully NVIDIA will fix the issue with their drivers in one of their next updates.

Cu Selur

[idbirch]

I'm getting exactly the same behaviour as Selur, his first post describes exactly the same steps I took trying to get around this including the 64-bit exe working but when combined with the 32-bit DLL, the "CUDA error!" green screen. I'm hitting all the same error messages in all the same scenarios.

My system is a little simpler in that no other GPUs are invovled, my specs:

GTX 980Ti (driver 378.66 released Feb 14th)
Win 10 Pro x64
i7 5820k (so no iGPU)
DGIndexNV 2052

[Selur]

-> downgrade your drivers (last working were 376.33 )

[idbirch]

Hi Selur, yes I saw that workaround but my PC is mainly for gaming so I'm not going to be languishing on old drivers for very long. What are the downsides of avisynth 64-bit? I just want to run some encodes in Hybrid without having to stick to outdated GPU drivers.

[Selur]

a. You can't use Avisynth 64bit in Hybrid
b. Avisynth 64bit is even more unstable than Avisynth MT (which is one of the reason for a.)
c. lots of filters are not available for Avisynth 64bit (which is one of the reason for a.)

[idbirch]

Oh dear I guess I'm at the mercy of Nvidia then

[Aleron Ives]

As are we all. I'm still languishing on 326.80, since they refuse to fix bugs for old cards.

[admin]

Yes, and OpenCL support is deficient for older cards too. Who can blame them, though, it's a CUDA versus OpenCL battle. Meanwhile, Vulkan rises to the fore. Everybody is going to concentrate on the cutting edge.

I just make a stable system that meets my CUDA/CUVID needs and then leave it alone. If you are a gamer that needs latest drivers, etc., well, maybe you can afford two systems. If not, play stupid games, win stupid prizes.

It's not unknown for things to get fixed, so keep the faith. Until then, you can only use drivers that work.

BTW, Avisynth+ 64 works fine for me.

[Selur]

Small follow-up: today I was prompted by GeForce Experience that a 'GeForce Game Ready Driver' was available (version 378.66; release date 2017/02/14) and since I'm always a bit curious I installed it and like I suspected DGDecNV doesn't work with it so back to 376.33, till the next driver release.

[admin]

Thanks, I was just about to try that version.

Just a note for those that haven't read the whole thread: It's not just DGDecNV that fails in this use case with these new drivers; the nVidia sample applications also fail.

I think people should try to upgrade to Pascal GPUs where possible, and leave the past behind. Yes, Maxwell is not that old, but it is what it is.

[Selur]

NVCEnC also fails with that the 378.66 driver version,... (upgrading to Pascal isn't planned here for a while,.. not prepared to shell out the money needed for a GeForce 1080 to replace my 980Ti; especially since my whole system is watercooled which adds another 100+ bucks for the cooler,..)

[admin]

$$$ be damned. Ride the bleeding edge.

[Aleron Ives]

In this case, the bleeding is probably from your bank account. GPUs are expensive.

[Guest]

Yes, but band aids are cheap

[admin]

I don't call $139 expensive. With Volta not due for desktops for at least a year, 1050Ti puts you on the bleeding edge for at least a year. What's not to like? 38 cents a day. C'mon, you blow much more at Starsucks.

I pulled the trigger on a second 1050Ti to upgrade my 980X machine. I took it out of the giant tower case to put it in a smaller case I had left over. I'm saving my big tower for the next machine. I put it in the tower only because the CPU cooler was too tall. So I ordered a low-profile 1366 fan.

Maybe we should have a desktop HW/SW subforum? Sure, why not.

[idbirch]

I've created a thread over on the Nvidia forums about this:

https://forums.geforce.com/default/topi ... in-378-66/

Hopefully someone picks it up.

[admin]

Thanks. I'll try to monitor it but please post again if you hear anything.

[Selur]

Just read the thread over inside the NVIDIA forum, seems like they are aware of the problem and working on it,.. so let's hope it doesn't take them too long to figure out how they broke it and how to repair it.

Cu Selur

[admin]

Thanks for the report, Selur. Can you give a try to hotfix driver 378.72HF?

https://forums.geforce.com/default/topi ... er-378-72/

[Selur]

Downloaded and installed the hotfix driver.
From the looks of it the issue is solved with that driver version.
(starting DGDecNV, loading a source die DGSource and NVEncC all work as they should)

Cu Selur

[admin]

That's great to hear. Thank you so much, Selur.

It's a great day on the DG front.

[Selur]

Happy to help and really happy that all is working again.