Blackmagic Forum

Posted: **Thu Sep 17, 2020 9:01 pm**

Hello All,

I just upgraded to 16.2.7 and now have an error when opening a project

I receive the following message

The GPU failed to perform image processing because of an error
Error coder 209

The project opens, I can see the timeline, but not image or video.

Attached are the NFO, Dxdiag and logs

HP Z620 / 2x E5-2690 / 64GB RAM - Nvidia GeForce GTX Titan with the latest drivers ( 9/14/2020 )

Thanks

Posted: **Thu Sep 17, 2020 10:05 pm**

OK -

Saw the post from Charles Bennett stating that

With the latest version of Resolve requiring nVidia GPUs to have a minimum Compute Capability of 5 (instead of 3) for CUDA 11, you can check your GPU here.

https://developer.nvidia.com/cuda-gpus

I guess my old Titan is now completely obsolete

Posted: **Thu Sep 17, 2020 10:31 pm**

Install the current NVIDIA 456.38 driver for your Titan GPU.

Posted: **Thu Sep 17, 2020 11:29 pm**

Hello!

The same here: tested a couple of driver versions (with full DDU procedure) - no luck. 16.2.6 works fine. Tested @ working from home environment so forgive the grandpa GTX 780.

: 2020-09-18 02_12_05-Window.png (10.57 KiB) Viewed 59773 times

: 2020-09-18 02_17_12-System Information.png (11.82 KiB) Viewed 59773 times

In the log file there is something like this:

Code: Select all: [size=85][0x0000097c] | DVIP | ERROR | 2020-09-18 02:12:01,571 | DVIP Exception: At position C:/jenkins/workspace/dvip/DaVinciIP/DaVinciIP/Unpacker/Unpacker_kernel.cu:299 - API: CUDA - API Error Code: cudaErrorNoKernelImageForDevice (209) - Call stack: 0: 00007FF71F6D09ED 1: 00007FF71F52361C 2: 00007FF7200CA910 3: 00007FF71FC50A93 4: 00007FF71F851FDC 5: 00007FF71CBF68FF 6: 00007FF71CABD0B1 7: 00007FF71CADA2B8 8: 00007FF71C84DD78 9: 00007FF71C854BC5 10: 00007FF71C851059 11: 00007FFDB01BB70E 12: 00007FFDB5524F7F 13: 00007FFDB5525126 14: 00007FFDCD316FD4 [0x0000097c] | GPUManager | INFO | 2020-09-18 02:12:01,571 | Flushing GPU memory... [0x0000097c] | DVIP | ERROR | 2020-09-18 02:12:01,583 | C:/jenkins/workspace/dvip/DaVinciIP/DaVinciIP/Unpacker/Unpacker_kernel.cu:299: CUDA error cudaErrorNoKernelImageForDevice (209) [0x0000097c] | GPUManager | ERROR | 2020-09-18 02:12:01,586 | Exception caught while running GPU algorithms: [0x0000097c] | DVIP | ERROR | 2020-09-18 02:12:01,586 | DVIP Exception: At position C:/jenkins/workspace/dvip/DaVinciIP/DaVinciIP/Unpacker/Unpacker_kernel.cu:299 - API: CUDA - API Error Code: cudaErrorNoKernelImageForDevice (209) - Call stack: 0: 00007FF71F6D09ED 1: 00007FF71F52361C 2: 00007FF7200CA910 3: 00007FF71FC50A93 4: 00007FF71F851FDC 5: 00007FF71CBF68FF 6: 00007FF71CABD0B1 7: 00007FF71CADA2B8 8: 00007FF71C84DD78 9: 00007FF71C854BC5 10: 00007FF71C851059 11: 00007FFDB01BB70E 12: 00007FFDB5524F7F 13: 00007FFDB5525126 14: 00007FFDCD316FD4 Urgent message: The GPU failed to perform image processing because of an error.||Error Code: 209. [/size]

Posted: **Fri Sep 18, 2020 12:30 am**

I'm having problems too!

Suddenly, it's no longer recognising CUDA on my GTX670 - has been working fine all along up until now!

Already downloaded latest driver, but will only run in OpenCL mode.

What gives?

Posted: **Fri Sep 18, 2020 12:33 am**

The 670 is too old.

Look to pick up a new 3000 series card.

Posted: **Fri Sep 18, 2020 12:56 am**

Dwaine Maggart wrote:Install the current NVIDIA 456.38 driver for your Titan GPU.

Thank you Dwaine,

I did that and still experience the issue.

At this time, as a workaround, I changed the preference for 'Memory and CPU' to use OpenCL instead of AUTO.

Posted: **Fri Sep 18, 2020 6:31 am**

Minimum CUDA Compute Capability for CUDA 11 is 3.5 (not 5.0 as has been stated elsewhere). Your Titan has 3.5, so it would be expected to work.

I'll try to dig up a Titan card tomorrow and see what results I get.

Posted: **Fri Sep 18, 2020 1:59 pm**

Dwaine Maggart wrote:Minimum CUDA Compute Capability for CUDA 11 is 3.5 (not 5.0 as has been stated elsewhere). Your Titan has 3.5, so it would be expected to work.

I'll try to dig up a Titan card tomorrow and see what results I get.

Thank you Dwaine, I really appreciate the clarification and your your efforts

I will not downgrade at this time, just run in OpenCL so Let me know if you need anything else from me.

Thanks again

Posted: **Fri Sep 18, 2020 7:30 pm**

Same here . Worked fine in 16.2.6 but since i installed 16.2.7 I get the 209 error
Black design should come up quickly with an update. This is ridiculous.

Posted: **Fri Sep 18, 2020 8:46 pm**

We are aware of the issue with CUDA Compute Capability 3.5 cards, like Titan and K6000.

It's being looked into. Hopefully a fix will be available soon.

Posted: **Fri Sep 18, 2020 8:56 pm**

Dwaine Maggart wrote:We are aware of the issue with CUDA Compute Capability 3.5 cards, like Titan and K6000.

It's being looked into. Hopefully a fix will be available soon.

Thank you very much for the quick return

Posted: **Fri Sep 18, 2020 9:04 pm**

PierreS wrote:
Dwaine Maggart wrote:We are aware of the issue with CUDA Compute Capability 3.5 cards, like Titan and K6000.

It's being looked into. Hopefully a fix will be available soon.

Thank you very much for the quick return

Posted: **Sat Sep 19, 2020 1:49 am**

The 16.2.7 version you currently have is build 008, as seen in About DaVinci Resolve.

If you download 16.2.7 now, you'll get build 010, which should address the CUDA 209 error issue.

People that have the check for updates turned on should also get an update notification for this new build.

On Windows, you can install the new build 010 version over top of the 008 version. There is no need to uninstall Resolve first, to install this update.

Posted: **Sat Sep 19, 2020 9:37 am**

Still 209 error on Titan with 456.38driver under win7-64bit (16.2.7 sept17).

Posted: **Sat Sep 19, 2020 3:28 pm**

Dwaine Maggart wrote:The 16.2.7 version you currently have is build 008, as seen in About DaVinci Resolve.

If you download 16.2.7 now, you'll get build 010, which should address the CUDA 209 error issue.

WOW !! This is amazingly fast !

Downloaded - installed and tested ! It works for me

Thank you !

( BTW - since I will not need to upgrade my video card now - I will put my $$ in a dongle )

Posted: **Sat Sep 19, 2020 5:05 pm**

PierreS wrote:
Dwaine Maggart wrote:The 16.2.7 version you currently have is build 008, as seen in About DaVinci Resolve.

If you download 16.2.7 now, you'll get build 010, which should address the CUDA 209 error issue.

WOW !! This is amazingly fast !

Downloaded - installed and tested ! It works for me

Thank you !

( BTW - since I will not need to upgrade my video card now - I will put my $$ in a dongle )

Well, I just installed the 16.2.7 Build 010 and I still have the same error and problem. I have a GTX 980. Not fixed at all

Posted: **Sun Sep 20, 2020 1:47 am**

PierreS wrote:OK -

Saw the post from Charles Bennett stating that

With the latest version of Resolve requiring nVidia GPUs to have a minimum Compute Capability of 5 (instead of 3) for CUDA 11, you can check your GPU here.

https://developer.nvidia.com/cuda-gpus

I guess my old Titan is now completely obsolete

The link cited above does not include all cards. My notebook has a GTX 1660 ti. It is not on the list but from other sources it appears that it may have a compute capability of 7.x.

My desktop GTX 1050 ti is also not on the list but the base 1050 is listed at 6.1.

The release notes should always be included in the zip file that can be downloaded for each version, and not just the installation EXE.

It is a real PITA to have to Google multiple places to get the needed information. Those who have older cards need to know IN ADVANCE what is the last Resolve version they should hang with before downloading 1.63 GB files, trying to install, only to find out later that the hardware that was OK with their previous version is no longer.

Posted: **Sun Sep 20, 2020 2:09 am**

The CUDA Wiki generally has those few cards that aren't on the NVIDIA developer site list.

https://en.wikipedia.org/wiki/CUDA

And yes, the 1660 is 7.5 capable.

And the 1050Ti is 6.1 capable.

Posted: **Sun Sep 20, 2020 5:03 am**

Dwaine Maggart wrote:The CUDA Wiki generally has those few cards that aren't on the NVIDIA developer site list.

https://en.wikipedia.org/wiki/CUDA

And yes, the 1660 is 7.5 capable.

And the 1050Ti is 6.1 capable.

Dwaine, that is my point. The list in the link posted for people to check is not complete. I had already pretty much figured out that my hardware was OK. But it is the recurring threads like this, started by people having problems, that illustrate the lack of clear and concise information. What percentage of users (especially newbies) even know the CUDA wiki exists or would think to consult it prior to installing the software or an update?

Posted: **Sun Sep 20, 2020 6:51 am**

Dwaine Maggart wrote:The CUDA Wiki generally has those few cards that aren't on the NVIDIA developer site list.

https://en.wikipedia.org/wiki/CUDA

And yes, the 1660 is 7.5 capable.

And the 1050Ti is 6.1 capable.

Ah thanks for this fix I was having issues with this yesterday with my 1660ti. Will have to finish my current project on 16.2.6 and then upgrade again.

Posted: **Mon Sep 21, 2020 1:09 pm**

Still have this issue,

DaVinci 16.2.7 last update,
GeForce 680 GTX...

What can I do ?

Posted: **Mon Sep 21, 2020 3:30 pm**

X-Raym wrote:Still have this issue,
DaVinci 16.2.7 last update,
GeForce 680 GTX...
What can I do ?

The GTX 680 has a compute capability of 3.0, and will not support CUDA 11.
So you have 3 options:

1. upgrade your video card
2. downgrade to 16.2.6
3. run in OpenCL mode

Posted: **Tue Sep 22, 2020 2:09 am**

But OpenCL will be much slower.

Posted: **Tue Sep 22, 2020 12:07 pm**

Hello, I have a similar problem with an RTX 2060 in my Asus Zenbook Pro Duo. The latest Nvidia driver (456.38) seems to break my installation so I had to roll back to 442.23.

Meanwhile, Resolve Studio 16.2.7 doesn't seem to thing my RTX 2060 supports CUDA anymore. I did download the latest build.

No dice. See below.

Rolling back to Resolve Studio 16.2.6 works fine:

Thanks,
Leonard French
Lawful Masses

Posted: **Tue Sep 22, 2020 4:51 pm**

Resolve 16.2.7 will NOT properly work with that driver. The driver has to be minimum 452.06.

Posted: **Wed Sep 23, 2020 11:59 am**

1. upgrade your video card
2. downgrade to 16.2.6
3. run in OpenCL mode

Many thanks for this,

At least the OpenCL mode allow to check my projects,
for sure better performance would need GPU upgrade (and motherboard, ram, CPU to goes with it, as 680GTX is previous gen). That would be a bit pricey for now...

Posted: **Sat Oct 10, 2020 4:04 pm**

Updated to 16.2.7 I have a GTX670 and got the same error code 209. Updated to latest Nvidia firmware 456.71, I'm now getting a error code 98. Can anyone help

Posted: **Mon Oct 12, 2020 4:13 pm**

The GTX670 does not support CUDA 11, therefore is not a good fit for Resolve 16.2.7 and higher.

None of the GTX600 series cards support the minimum required Compute Capability of 3.5, therefore none of them will work in CUDA mode with 16.2.7 and higher.

They will run in OpenCL mode, but poorly.

Either stay at 16.2.6 or update the GPU.

Posted: **Wed Oct 14, 2020 1:00 pm**

: Error209; 209.png (5.29 KiB) Viewed 56751 times

Same issue for me, updated to latest NVIDIA driver 456.71

GTX 760

Posted: **Wed Oct 14, 2020 6:34 pm**

The GTX760 does not support CUDA 11.

It has Compute Capability 3.0. The GPU needs to support 3.5 or higher for CUDA 11.

Posted: **Fri Oct 16, 2020 12:19 am**

I had the same problem using my Nvidia GTX 1080. I upgraded to the latest Nvidia driver (456.71) but still no luck. I tried OpenCL mode and it works but runs glacially. Do I have no alternative but to downgrade Studio to below 16.2.7?0

If so that is tremendously disappointing. If an update doesn't fix this soon I will have to stop recommending Resolv and start looking for a replacement. I can't imagine being frozen on one specific version forever due to this problem. Surely you have a solution coming? I am NOT going to upgrade my GPU for this software and imagine hardly anyone else will either.

Thanks very much,
Nathan Hoover

Posted: **Fri Oct 16, 2020 1:27 am**

nhoover wrote:I had the same problem using my Nvidia GTX 1080. I upgraded to the latest Nvidia driver (456.71) but still no luck. I tried OpenCL mode and it works but runs glacially. Do I have no alternative but to downgrade Studio to below 16.2.7?0

If so that is tremendously disappointing. If an update doesn't fix this soon I will have to stop recommending Resolv and start looking for a replacement. I can't imagine being frozen on one specific version forever due to this problem. Surely you have a solution coming? I am NOT going to upgrade my GPU for this software and imagine hardly anyone else will either.

Thanks very much,
Nathan Hoover

GTX 1080 is a CUDA 6.x capable so ok in this regard. (3.5 needed) so its likely a driver selection issue.

Posted: **Fri Oct 16, 2020 3:13 am**

In the Resolve Help menu, select "Create Diagnostics Log on Desktop"

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.

Posted: **Fri Oct 16, 2020 6:46 pm**

Thanks - I actually downgraded to 16.2.6 in order to complete my project - it worked fine as before. If I have a chance to try again, I'll definitely follow your steps and post the results.

Posted: **Thu Oct 22, 2020 9:33 am**

I am hitting this problem too, can you advise?
I have a Quadro K4200 GPU and the latest driver form Nvidia: 452.39
Is a fix going to be forthcoming or do I need to downgrade to 16.2.6?
I cannot afford to dump a very good and expensive Quadro card so I hope there will be a fix...?

Posted: **Thu Oct 22, 2020 4:16 pm**

The K4200 has CUDA Compute Capability 3.0. Minimum requirement for CUDA 11 support is 3.5

So your card is not going to work with Resolve 16.2.7 or higher. Unless you run it in OpenCL mode, which will work poorly.

Posted: **Thu Oct 22, 2020 4:41 pm**

Ouch, that wasn't what I wanted to hear. I guess that means I am stuck with 16.2.6 from now on.

Posted: **Mon Nov 09, 2020 4:09 pm**

I have searched the Nvidia site and I cannot find any reference to CUDA Compute Capability or even values such as "CUDA 11". There is plenty about CUDA cores or memory bandwidth but where on earth can I find out which Nvidia GPUs have a specific CUDA level which are now compatible with 16.2.7 or even Resolve 17 which is imminent? There really needs to be a Table of GPU level/performance somewhere. Where can I get this information? Thanks.

Posted: **Mon Nov 09, 2020 11:22 pm**

https://en.wikipedia.org/wiki/CUDA

Your GPU has to have Compute Capability 3.5 or higher, to support CUDA 11.

Posted: **Tue Nov 10, 2020 3:35 am**

Dwaine Maggart wrote:https://en.wikipedia.org/wiki/CUDA

Your GPU has to have Compute Capability 3.5 or higher, to support CUDA 11.

I do appreciate Dwaine's clear statements and the link above.

I had a dual GPU system with one card at 3.0 (Quadro 4200) and one at 3.5 (Quadro K5200). After getting this issue I removed the K4200.

Separately I had an issue of no video on program output in 16.2.7. I had to downgrade to 16.2.6 because of this and the GPU error. However after removing the K4200 I have upgraded to 16.2.7 again and find there is no issue.

I am now running only the Quadro K5200 with driver version 452.57 and so far, so good.

However I am aware that with CUDA compute 3.5 being the minimum, the writing is on the wall and I will need to look at moving up in hardware.

Posted: **Tue Nov 10, 2020 10:14 am**

I can't quite believe I have to plough through a massive Wikipedia post to get this information I need.
It's also hugely disappointing that a K4200 can't be supported any more.
I'll have to stick with 16.2.6.

Posted: **Tue Nov 10, 2020 10:29 am**

Ctrl-f to bring up a find window to easily find your GPU on the CUDA Wiki.

If that's not to your liking, use the NVIDIA site for this info. Be aware it takes more effort than the Wiki, and doesn't always have the odd GPU listed:

https://developer.nvidia.com/cuda-gpus

Posted: **Thu Nov 19, 2020 9:21 pm**

hi Dwaine,

many thanks for your help as usual.

I have a licensed Studio v. 16.2.7.010 on a setup with a Quadro K2000 with computing level 3.0 that should supports up to CUDA 9.2. I could downgrade Resolve to a previous release, but can't find a way to download an old Studio.

Is there anyway for me to enable CUDA processing without buying new hardware?

Thanks.

Posted: **Fri Nov 20, 2020 1:20 am**

Just scroll down on the support page and you'll find older versions reaching far back.

Posted: **Fri Nov 20, 2020 6:50 pm**

As Uli pointed out, go here:

https://www.blackmagicdesign.com/suppor ... and-fusion

All Resolve versions back to 10.1.5 are available.

There is no way to make CUDA work with your GPU in Resolve version 16.2.7 or higher.

Either update the GPU, or use Resolve 16.2.6 or earlier.

Posted: **Sat Nov 21, 2020 1:43 am**

Im getting the same error (But with code 219) in resolve 17.
Pretty simple fusion comp (Just masks and transform nodes with keyframes).

The compute power of GPU is 7.5 (Rtx 2070) and I have updated all the drivers.

Other specs:
i9-9900k
64gb RAM
Windows 10

Posted: **Sun Nov 22, 2020 11:23 am**

Dwaine Maggart wrote:As Uli pointed out, go here:

https://www.blackmagicdesign.com/suppor ... and-fusion

All Resolve versions back to 10.1.5 are available.

There is no way to make CUDA work with your GPU in Resolve version 16.2.7 or higher.

Either update the GPU, or use Resolve 16.2.6 or earlier.

Thanks a lot Dwaine! Superhelpful as usual.

It works a charm now using CUDA v.9.2 and Resolve 16.2.6.
I will stick to v.16.2.6 for the time being. Then at some point I will upgrade the hardware and switch over to v. 17.

Thanks.

Posted: **Thu Nov 26, 2020 3:39 pm**

Dwaine Maggart wrote:In the Resolve Help menu, select "Create Diagnostics Log on Desktop"

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.

I have the same problem with V16.2.7.10 and 17.beta with error 219.
( files of V17 here:
dropbox.com/sh/1n241a5wn8je3bw/AACUGOrWoeApSexT4iu0jZyZa?dl=0)
my config:
mother card Microxtar Z730-A PRO (MS-7B48)
intel I5-8400 CPU @2.8Ghz
NVIDIA GeForce GTX 1050Ti pilote NVIDIA 27.21.14.5638 du 14/9/2020
W10 famille 64bits

How can I solve this issue?
Bernard

Posted: **Thu Dec 03, 2020 8:41 am**

It looks like you are doing something in the project that requires more than the 4GB of GPU VRAM that you have.

Can you send a project export .drp of the Indon??sie commun 2 project, so we can see what's going on in the project?

Blackmagic Forum

GPU Error 209 with Resolve 16.2.7

GPU Error 209 with Resolve 16.2.7

Re: GPU Error with Resolve 16.2.7

Re: GPU Error with Resolve 16.2.7

Re: GPU Error with Resolve 16.2.7

Re: GPU Error with Resolve 16.2.7

Re: GPU Error with Resolve 16.2.7

Re: GPU Error with Resolve 16.2.7

Re: GPU Error with Resolve 16.2.7

Re: GPU Error with Resolve 16.2.7

Re: GPU Error with Resolve 16.2.7

Re: GPU Error 209 with Resolve 16.2.7

Re: GPU Error 209 with Resolve 16.2.7

Re: GPU Error 209 with Resolve 16.2.7

Re: GPU Error 209 with Resolve 16.2.7

Re: GPU Error 209 with Resolve 16.2.7

Re: GPU Error 209 with Resolve 16.2.7

Re: [SOLVED] GPU Error 209 with Resolve 16.2.7

Re: GPU Error with Resolve 16.2.7

Re: [SOLVED] GPU Error 209 with Resolve 16.2.7

Re: [SOLVED] GPU Error 209 with Resolve 16.2.7

Re: [SOLVED] GPU Error 209 with Resolve 16.2.7

Re: [SOLVED] GPU Error 209 with Resolve 16.2.7

Re: [SOLVED] GPU Error 209 with Resolve 16.2.7

Re: [SOLVED] GPU Error 209 with Resolve 16.2.7

Re: [SOLVED] GPU Error 209 with Resolve 16.2.7

Re: [SOLVED] GPU Error 209 with Resolve 16.2.7

Re: [SOLVED] GPU Error 209 with Resolve 16.2.7

Re: [SOLVED] GPU Error 209 with Resolve 16.2.7

Re: [SOLVED] GPU Error 209 with Resolve 16.2.7

Re: [SOLVED] GPU Error 209 with Resolve 16.2.7

Re: [SOLVED] GPU Error 209 with Resolve 16.2.7

Re: [SOLVED] GPU Error 209 with Resolve 16.2.7

Re: [SOLVED] GPU Error 209 with Resolve 16.2.7

Re: [SOLVED] GPU Error 209 with Resolve 16.2.7

Re: [SOLVED] GPU Error 209 with Resolve 16.2.7

Re: [SOLVED] GPU Error 209 with Resolve 16.2.7

Re: [SOLVED] GPU Error 209 with Resolve 16.2.7

Re: [SOLVED] GPU Error 209 with Resolve 16.2.7

Re: [SOLVED] GPU Error 209 with Resolve 16.2.7

Re: [SOLVED] GPU Error 209 with Resolve 16.2.7

Re: [SOLVED] GPU Error 209 with Resolve 16.2.7

Re: [SOLVED] GPU Error 209 with Resolve 16.2.7

Re: [SOLVED] GPU Error 209 with Resolve 16.2.7

Re: [SOLVED] GPU Error 209 with Resolve 16.2.7

Re: [SOLVED] GPU Error 209 with Resolve 16.2.7

Re: [SOLVED] GPU Error 209 with Resolve 16.2.7

Re: [SOLVED] GPU Error 209 with Resolve 16.2.7

Re: [SOLVED] GPU Error 209 with Resolve 16.2.7

Re: [SOLVED] GPU Error 209 with Resolve 16.2.7

Re: [SOLVED] GPU Error 209 with Resolve 16.2.7