Resolve 17 Studio B7 CUDA issues

Hi All,

I use v16 Studio with CUDA acceleration for over a year now and got the new Speed Editor which runs only on v17. After installing, been getting into problems (like the latest, 461.09 for my GTX 960, is not compatible with Beta 7) even after downgrading my NVidia Driver and to Studio Beta 6, which was working fine with CUDA enabled just recently.

Now, with DVR Studio 17b6 and an earlier NVidia Driver, I can't get CUDA working anymore and OpenCL seems to be impotent as when I create my Optimised Media. Now, it literally takes hours instead of my usual minutes! I do know that muy GPU meets the minimum requirements both in CUDA version (11.2 I believe is what I have) and CUDA Compute Capability (Mine's at 5.2).

Any advise is greatly appreciated!

-----------------------UPDATE-----------------------

Since I already made backups of my work. I did a clean DVR Studio 16 install, updated my drivers, made sure I have CUDA working then updated to 17b6 to get my Speed Editor working. Now my renders and Optimized Media runs 8-13x as fast as when I was on 17B7!

------------------------------------------------------

Alienware Alpha R2
i7 6700T
GTX 960 4GB
32GB RAM
1TB SSD
Windows 10 64-bit

nVidia's driver 461.09 isn't compatible with any version of Resolve, and even Premiere Pro is having issues with it.

You should be fine using Beta 7 and driver version 460.89. (I use a 4GB 970 myself.)

nVidia's driver 461.09 isn't compatible with any version of Resolve, and even Premiere Pro is having issues with it.

You should be fine using Beta 7 and driver version 460.89. (I use a 4GB 970 myself.)

Since I already made backups of my work. I did a clean DVR Studio 16 install, updated my drivers, made sure I have CUDA working then updated to 17b6 to get my Speed Editor working. Now my renders and Optimized Media runs 8-13x as fast as when I was on 17B7!

I am on 461.09 with my 17B6 and works flawlessly. But when I tried another attempt at Beta 7, it gave me the same Driver Warning... I'll just stay on Beta 6 until something is resolved. =)

I am on 461.09 with my 17B6 and works flawlessly.

Well, you might be the only person on planet Earth who can say that.

I am on 461.09 with my 17B6 and works flawlessly.

Well, you might be the only person on planet Earth who can say that.

Probably... Still I don't think that's lucky. =)

when I tried to go 17B7 (again) with the downgraded driver, I get this message:

"DaVinci Resolve is using OpenCL for image processing
because the installed NVIDIA driver does not support
CUDA 11.0. Upgrade your NVIDIA driver for optimal
performance. Alternatively you can manually select
OpenCL processing mode to run in the current
configuration."

From there, it now forces OpenCL whenever I open DVR Studio 17. Well, I'm going back to a clean 16 install and to 17B6... =(

The thing is, my 960 GTX supports CUDA 11.2 and I believe I'm in that now.

The only thing that makes sense with that message is that you aren't using the 460.89 driver. I can't think of anything else to explain it.

Running 17.0b7 with driver 457.30 Studio, as I have done with all the 17 betas since November. All have run fine with no problem selecting CUDA.

The only thing that makes sense with that message is that you aren't using the 460.89 driver. I can't think of anything else to explain it.

I'm already back on the 460.89 driver and 17B6 with CUDA enabled. With either drivers (new or old) I still get the message that the installation will revert to OpenCL whenever I install 17B7. So I'm staying on the 17B6 until this is resolved.

[Dwaine Maggart]

The 461.09 driver is so problematic with Resolve that we've blacklisted it in 17b7.

So absolutely positively do NOT use 461.09 with Resolve.

If you have a GPU issue with the 460.89 driver, send us a Resolve log and Windows System Information .NFO file.

Running 17.0b7 with driver 457.30 Studio, as I have done with all the 17 betas since November. All have run fine with no problem selecting CUDA.

Since my Resolve Rig has the GTX 960, I suspect that upgrading my video card (via Alienware Graphics Amplifier) seems to be my only option to move forward. I was planning on the RTX 2070 Super in a couple of months anyways. But here's to hoping that my 17B7 snafu would be resolved.

The 461.09 driver is so problematic with Resolve that we've blacklisted it in 17b7.

So absolutely positively do NOT use 461.09 with Resolve.

If you have a GPU issue with the 460.89 driver, send us a Resolve log and Windows System Information .NFO file.

Thank You.

Any link where I can make these files?

[Dwaine Maggart]

There should be no issue with the GTX960 and installing the 460.89 driver.

If you have 17b7 issues with the 460.89 driver, please send a Resolve log and system info NFO file so we can look into what's going on.

In a File Explorer window, go to:

C:\Program Files\Blackmagic Design\DaVinci Resolve

and run CaptureLogs

This will place a Resolve log file named similar to this on your Windows desktop: DaVinci-Resolve-logs-20181228_140434.zip (You may not see the .zip extension if your system is set to hide known extensions).

Then open Windows System Information and do a File - Save (Not a File Export), which will generate a .NFO file.

Place both those files on a file sharing site and provide links to the files here.

If you are a new Forum user, you may not be allowed to post URLs. If this happens, just put a space near the front of the URL, so the system doesn't think it's a URL.

Hi all! Got it fixed!

I had to do a complete clean install (including AppData and Registry stuff) and REMOVING both the NVidia Experience and Alienware video driver updater components. Because, for some reason, either reverts to the ancient & original 432.00 driver whenever I do a rollback (that version is the base version that came with my unit and a recovery component by Dell/Windows). Manually just installing the 460.89 driver without the included fluff did the trick!

Now on DVR Studio 17B7 with full use of CUDA, thanks all!

Another question though... The wired Speed Editor stops working (even when lights are on) randomly whenever I switch between the CUT and EDIT pages. Not all of the time, but when I do a restart and just work on the CUT page, it works like a dream. Anyone else experience this on the beta?

I updated to DR17 B7, got the msg about drivers, uninstalled & put DR17 B6 back on, and it's working fine, with the 461 drivers, set it to CUDA in DR, and no issues.. rendering a Minecraft video as I write this

[Dwaine Maggart]

viewtopic.php?f=36&t=131254#p717736