Davinci resolve ошибка gpu

DaVinci Resolve 18 is a powerful video editing software, loved by professionals and beginners alike. It is well known for its advanced features and tools that enable users to edit and color correct their videos with ease. However, sometimes users face issues like the «Unable to Initialize GPU» error, which can be quite frustrating. This article will explore some simple and effective solutions to fix this problem and get you back to creating stunning videos in no time.

Windows Graphics Settings

Close DaVinci Resolve and open up your Windows settings. In your system settings, click on Display. From here, scroll down and select Graphics. Alternatively, you can search for Graphics Settings to get here.

Windows Settings > System > Display > Graphics

Find DaVinci Resolve Install Location

Configure which apps you allow your graphics card to support while running. Click on Browse, which will open up your File Explorer.

Graphics Settings > Browse

The default install location for DaVinci Resolve is in your main drive under Program Files > Blackmagic Design > DaVinci Resolve. Scroll down until you can find the Resolve.exe application.

Program Files > Blackmagic Design > DaVinci Resolve

If DaVinci Resolve is not installed in this location, search for DaVinci and select Open File Location for the app. In most cases, this will be the location of the DaVinci Resolve shortcut. Right-click the shortcut and select Open File Location again to get to the final install location for this app.

DaVinci Resolve > Open File Location

Change DaVinci Resolve 18 Graphics Preference

After adding the application to this list, click Options to change its Graphics preference to High performance. This will allow DaVinci Resolve to utilize your graphics card and fix the “unable to initialize GPU” error you are getting.

High Performance Graphics Preference

  • This error is usually caused by outdated or incompatible GPU drivers, incorrect graphics card settings, or insufficient graphics card memory.

  • If none of the solutions work, you may need to upgrade your graphics card to a more powerful and compatible one. Additionally, you can seek help from the official DaVinci Resolve community forums or contact their customer support for further assistance.

Most users get some sort of GPU issue or the other while working on DaVinci Resolve.

Sometimes you might face GPU (graphics card) related issues when…

You update Resolve to the latest version.

Or…

When you update the Nvidia drivers. Or it could be due to other reasons as well.

Today we’ll see how to fix these GPU related issues in DaVinci Resolve.

Without wasting time, let’s get started.


Is DaVinci Resolve GPU Intensive?

DaVinci Resolve is GPU intensive in the sense that the GPU does all the image processing heavy-lifting as per BlackMagic Design. Whereas other video editors rely heavily on CPU.

So DaVinci Resolve will naturally demand a good discrete GPU with a minimum of 2 GB onboard memory (4 GB and above is preferable).


Related Article:

How to Make DaVinci Resolve Use GPU (Helpful Tips!)


Most Commonly Used GPUs in DaVinci Resolve

Both Nvidia (CUDA) and AMD Radeon (OpenCL) are good. But the most commonly used GPUs come under Nvidia, for example:

  • GeForce GTX Series like 970, 1080, 1650 Ti. etc, – for Consumers
  • Quadro series – for Professionals
  • Tesla series – Data Center

Because of a lot of graphics card variants in Nvidia and Radeon, there arises a need to properly update your computer with the right version of drivers (to run the hardware).


Why does DaVinci Resolve Throw GPU Errors?

DaVinci Resolve usually throws GPU errors whenever there are any compatibility issues with the graphics card, video driver and the version of DaVinci Resolve.

Hence it is very important for you to check whether your graphics card is supported, whether you have the latest or reliable version of video driver (like Nvidia Studio driver) and the latest or stable Resolve.

Though you don’t have control over the DaVinci Resolve software, you can make sure you have the right GPU with the correct video driver installed.


Some of the most common GPU issues faced in DaVinci Resolve are:

  • GPU Configuration Warning
  • Unsupported GPU processing mode
  • GPU Error – like “Davinci resolve gpu failed to perform image processing error 702”
  • GPU Memory Full

Related Article:

GPU & DaVinci Resolve (9 Things Most Beginners Don’t Know)


GPU Configuration Warning, Unsupported GPU Processing Mode & GPU Failed to Perform Image Processing Error

The GPU configuration warning will say “DaVinci Resolve is using OpenCL for image processing because the installed Nvidia driver does not support CUDA 11.0…“.

Starting from DaVinci Resolve version 16.2.7 and afterwards (including version 17), BlackMagic has come up with a minimum requirement for hardware GPU types and Nvidia drivers (Mac, Windows and Linux).

OS GPU Hardware Type Minimum Nvidia Driver Version
MacOS 10.14.6 Mojave Metal or OpenCL 1.2
Windows 10 Creators Update CUDA 11.0 or OpenCL 1.2 451.82
Linux CentOS 7.3 CUDA 11.0 or OpenCL 1.2 450.51.06

The table clearly tells that for Windows, your Nvidia GPU (graphics card like GeForce GTX 1650) should support CUDA 11.0.

In other words…

Your Nvidia GPU should have a minimum compute capability of 3.5 and a minimum Nvidia driver version of 451.82.

(If you think it is too technical, just hang on. Just have your GPU name ready for the next step).

How to Check your Nvidia GPU Card is Supported by DaVinci Resolve?

  • Navigate to Wikipedia GPU CUDA Support List.
  • Search for your GPU card by pressing “Ctrl + F”.
  • After locating your card, check the first column “Compute Capability (version)“.
  • The Compute capability version should be equal to or greater than 3.5.
  • If it is less than 3.5, Resolve won’t support your GPU card for versions after 16.2.7 (including version 17).

You can also check the compute capability from Nvidia website as well.

If the “compute capability” for your card is greater than 3.5, there is nothing for you to do.

But if it is less than 3.5, then you won’t be able to use CUDA in Resolve.

Instead you’ll have to go to the menu “DaVinci Resolve” -> “Preferences” -> “System” -> “Memory and GPU” -> “GPU Configuration” -> against “GPU Processing Mode” uncheck “Auto” and select “OpenCL” instead of CUDA.

If “OpenCL” doesn’t improve the performance, then keep the option as CUDA.

Go to Nvidia Driver Downloads, and select your graphics card from the list, search and download the appropriate driver and install it.

See if this improves your situation.

If you still have issues, then probably you might need to upgrade your graphics card (whose compute capability is more than 3.5).

Or roll back to previous versions of DaVinci Resolve (like 16.2.6) to check your existing card is getting supported in Resolve or not.


My GPU card is Eligible But Still Resolve Says It Is Un-Supported

If your graphics card has a compute capability of over 3.5, and Resolve says it’s unsupported, then you need to update your Nvidia driver version to a newer one.

For Windows, the minimum driver version is 451.82.

For Linux CentOS, the minimum driver version is 450.51.06.

Go to the Nvidia Driver Downloads, select your graphics card from the list, search and download the appropriate driver and install it.

DaVinci Resolve GPU Memory Full

When you work on high resolution footage like 4K UHD in a 4K timeline and do a lot of image processing like color grading, OFX plugins, Fusion effects, etc, Resolve might throw “GPU Memory is Full” error.

I get this error when I click on Fusion tab (after applying effects, transitions to the clips).

There is so much image processing happening that your Nvidia GPU might not have sufficient memory to handle them all.

Or…

When the GPU Processing Mode is set to “Auto” (which results in “OpenCL” being selected instead of “CUDA”).

Here’s how to fix the DaVinci Resolve GPU Memory Full issue in DaVinci Resolve 17:

  • Go to the menu “DaVinci Resolve” -> “Preferences” -> “System” -> “Memory and GPU” -> “GPU Configuration” -> against “GPU Processing Mode” uncheck “Auto” and select “CUDA” instead of “OpenCL”.
  • Against “GPU Selection”, uncheck “Auto” and manually select the available Nvidia card in your system.
  • Restart DaVinci Resolve.

This should get rid of the error.

If the above fix doesn’t work, then try this work-around:

  • Try to reduce the timeline resolution to 1920 x 1080p (if you were using 4K UHD = 3840 x 2160), by clicking on the “Project Settings” (bottom right hand corner cog wheel).
  • Click on “Master Settings” -> “Timeline Resolution” -> “1920 x 1080 HD” or “1280 x 1080 HD”. (Before delivering, you have the option to render in 4K UHD).

If after doing all the above, if you still have issues with your GPU, then either update Resolve to the latest version or roll back to the previous version.

Most probably the latest version should have bug fixes and could support your GPU without any issues.


Still facing issues?

Then click on this link to generate log files and share it in the BlackMagic forum (scroll to this section “The Last Step – Getting Help from BlackMagic Design Support Staff”)


You may be also interested in the below posts:

  • Set up DaVinci Resolve 18 the Right Way (& Fix Issues)
  • (How to Troubleshoot): DaVinci Resolve Keeps Crashing!
  • Tips to Save Your Precious Work in DaVinci Resolve (IMPORTANT!)
  • 6 Ways to Fix DaVinci Resolve Media Offline Issue [NEW]
  • 14 Ways to Fix DaVinci Resolve Not Opening Issue

Source:

BlackMagic Forum

Открываю проект в DaVinci Resolve 16.2.8, он открывается, но появляется окошко с сообщением об ошибке:

The GPU failed to perform image processing because of an error.
Error Code: 209.

Накануне я обновил DaVinci Resolve. Скорее всего из неё обрали поддержку CUDA (в моём случае минимум Compute Capability of 3.0).
Посмотрел логи:
«C:UsersDenisAppDataRoamingBlackmagic DesignDaVinci ResolveSupportlogsResolveDebug.txt»
Там была такая запись:

[0x0000323c] | GPUManager           | INFO  | 2021-02-04 13:33:04,843 | Flushing GPU memory...
[0x0000323c] | DVIP                 | ERROR | 2021-02-04 13:33:04,845 | C:/jenkins/workspace/dvip/DaVinciIP/DaVinciIP/Unpacker/Unpacker_kernel.cu:226: CUDA error cudaErrorNoKernelImageForDevice (209)
[0x0000323c] | GPUManager           | ERROR | 2021-02-04 13:33:04,851 | Exception caught while running GPU algorithms:
[0x0000323c] | DVIP                 | ERROR | 2021-02-04 13:33:04,851 | 
DVIP Exception: At position C:/jenkins/workspace/dvip/DaVinciIP/DaVinciIP/Unpacker/Unpacker_kernel.cu:226
 - API: CUDA
 - API Error Code: cudaErrorNoKernelImageForDevice (209)

Как всегда для решения подобной проблемы у пользователя аж 3 варианта:
1. Купить видео-карту помощнее
2. Установить старую версию DaVinci (16.2.6)
3. Переключить режим работы программы на OpenCL:
▶ ▶
GPU Processing Mode = OpenCL

Придётся воспользоваться вторым вариантом, т.к. вариант (3) почему-то замедляет производительность программы (судя по некоторым отзывам, хотя по идее не должен), а тратить деньги на новую видюху я не хочу. К тому же сейчас из-за ажиотажа вокруг майнинга криптовалют, видео-карты стоят нереальных денег.
Текущий драйвер NVIDIA GeForce: 461.40.
Попробовал драйверы:
461.09 — проблема не решилась
460.89 — аналогично
460.79 — та же ошибка при открытии проекта
457.61 — увы
457.30 — не сработало
457.09 — ошибка осталась
456.71 — нет
456.55 — тоже нет
456.38 — и этот драйвер не сработал.

Таким образом рекомендация с форума, в которой предлагалось попробовать старый драйвер, мне не помогла.

Зато проблема решилась установкой DaVinci Resolve версии 16.2.6.005

  • Об авторе
  • Недавние публикации

DenTNT

  • Message

PierreS

  • Posts: 25
  • Joined: Mon Sep 14, 2020 9:16 pm
  • Location: Chicagoland
  • Real Name: Pierre STEYGERS

PostThu 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 :)

Attachments
Z620.zip
Log + NFO + DxDiag
(263.43 KiB) Downloaded 567 times

Last edited by PierreS on Sat Sep 19, 2020 3:28 pm, edited 2 times in total.

Resolve Studio 17.2.1 — Win 10 — 2x E5-2690@2.9Ghz — 96GB — RTX2060S — Driver 471.11 Studio

PierreS

  • Posts: 25
  • Joined: Mon Sep 14, 2020 9:16 pm
  • Location: Chicagoland
  • Real Name: Pierre STEYGERS

PostThu 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 :(

Resolve Studio 17.2.1 — Win 10 — 2x E5-2690@2.9Ghz — 96GB — RTX2060S — Driver 471.11 Studio

User avatar

Dwaine Maggart

Blackmagic Design

  • Posts: 9948
  • Joined: Wed Aug 22, 2012 2:53 pm

PostThu Sep 17, 2020 10:31 pm

Install the current NVIDIA 456.38 driver for your Titan GPU.

Dwaine Maggart
Blackmagic Design DaVinci Support

p.sudakovs

  • Posts: 5
  • Joined: Tue May 01, 2018 1:53 pm
  • Real Name: Peteris Sudakovs

PostThu 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
2020-09-18 02_12_05-Window.png (10.57 KiB) Viewed 50111 times
2020-09-18 02_17_12-System Information.png
2020-09-18 02_17_12-System Information.png (11.82 KiB) Viewed 50111 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]

Attachments
logs.zip
(34.24 KiB) Downloaded 278 times

User avatar

iannicholson

  • Website
  • Posts: 34
  • Joined: Thu Feb 15, 2018 1:26 am
  • Location: Sydney, Australia.
  • Real Name: Ian Nicholson

PostFri 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?

Jim Simon

  • Posts: 23952
  • Joined: Fri Dec 23, 2016 1:47 am

PostFri Sep 18, 2020 12:33 am

The 670 is too old.

Look to pick up a new 3000 series card.

PierreS

  • Posts: 25
  • Joined: Mon Sep 14, 2020 9:16 pm
  • Location: Chicagoland
  • Real Name: Pierre STEYGERS

PostFri 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.

Resolve Studio 17.2.1 — Win 10 — 2x E5-2690@2.9Ghz — 96GB — RTX2060S — Driver 471.11 Studio

User avatar

Dwaine Maggart

Blackmagic Design

  • Posts: 9948
  • Joined: Wed Aug 22, 2012 2:53 pm

PostFri 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.

Dwaine Maggart
Blackmagic Design DaVinci Support

PierreS

  • Posts: 25
  • Joined: Mon Sep 14, 2020 9:16 pm
  • Location: Chicagoland
  • Real Name: Pierre STEYGERS

PostFri 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

Resolve Studio 17.2.1 — Win 10 — 2x E5-2690@2.9Ghz — 96GB — RTX2060S — Driver 471.11 Studio

harryvanlamoen

  • Posts: 23
  • Joined: Tue Oct 08, 2019 6:03 pm
  • Real Name: Harry van Lamoen

PostFri 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.

User avatar

Dwaine Maggart

Blackmagic Design

  • Posts: 9948
  • Joined: Wed Aug 22, 2012 2:53 pm

PostFri 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.

Dwaine Maggart
Blackmagic Design DaVinci Support

PierreS

  • Posts: 25
  • Joined: Mon Sep 14, 2020 9:16 pm
  • Location: Chicagoland
  • Real Name: Pierre STEYGERS

PostFri 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 :)

Resolve Studio 17.2.1 — Win 10 — 2x E5-2690@2.9Ghz — 96GB — RTX2060S — Driver 471.11 Studio

harryvanlamoen

  • Posts: 23
  • Joined: Tue Oct 08, 2019 6:03 pm
  • Real Name: Harry van Lamoen

PostFri 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 :)

User avatar

Dwaine Maggart

Blackmagic Design

  • Posts: 9948
  • Joined: Wed Aug 22, 2012 2:53 pm

PostSat 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.

Dwaine Maggart
Blackmagic Design DaVinci Support

mastergoo

  • Posts: 1
  • Joined: Sat Sep 19, 2020 9:34 am
  • Real Name: Evgeniy Chesnokov

PostSat Sep 19, 2020 9:37 am

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

PierreS

  • Posts: 25
  • Joined: Mon Sep 14, 2020 9:16 pm
  • Location: Chicagoland
  • Real Name: Pierre STEYGERS

PostSat 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 )

Resolve Studio 17.2.1 — Win 10 — 2x E5-2690@2.9Ghz — 96GB — RTX2060S — Driver 471.11 Studio

maumoreno2001

  • Posts: 1
  • Joined: Sat Sep 19, 2020 5:02 pm
  • Real Name: Mauro Moreno

PostSat 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

User avatar

gtempleman

  • Posts: 191
  • Joined: Sat Jul 27, 2019 3:07 pm
  • Real Name: Gary Templeman

PostSun 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.

Microsoft Windows 10 Home x64
Version 22H2 build 19045.2546
Lenovo Legion Y545
32GB RAM
GTX 1660Ti
Driver version 528.24
Resolve (Studio) 18.1.2 build 6

User avatar

Dwaine Maggart

Blackmagic Design

  • Posts: 9948
  • Joined: Wed Aug 22, 2012 2:53 pm

PostSun 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.

Dwaine Maggart
Blackmagic Design DaVinci Support

User avatar

gtempleman

  • Posts: 191
  • Joined: Sat Jul 27, 2019 3:07 pm
  • Real Name: Gary Templeman

PostSun 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?

Microsoft Windows 10 Home x64
Version 22H2 build 19045.2546
Lenovo Legion Y545
32GB RAM
GTX 1660Ti
Driver version 528.24
Resolve (Studio) 18.1.2 build 6

georgegg

  • Posts: 4
  • Joined: Sun May 05, 2019 12:59 pm
  • Real Name: George Ganitis

PostSun 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.

User avatar

X-Raym

  • Website
  • Posts: 125
  • Joined: Thu Apr 18, 2013 4:05 pm
  • Location: France
  • Real Name: Raymond Radet

PostMon Sep 21, 2020 1:09 pm

Still have this issue,

DaVinci 16.2.7 last update,
GeForce 680 GTX…

What can I do ?

My DaVinci Resolve Scripts: https://github.com/X-Raym/DaVinci-Resolve-Scripts
Donation: https://paypal.me/extremraym

PierreS

  • Posts: 25
  • Joined: Mon Sep 14, 2020 9:16 pm
  • Location: Chicagoland
  • Real Name: Pierre STEYGERS

PostMon 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

Resolve Studio 17.2.1 — Win 10 — 2x E5-2690@2.9Ghz — 96GB — RTX2060S — Driver 471.11 Studio

Uli Plank

  • Posts: 16601
  • Joined: Fri Feb 08, 2013 2:48 am
  • Location: Germany and Indonesia

PostTue Sep 22, 2020 2:09 am

But OpenCL will be much slower.

Don’t approach DR with your preconceptions from another NLE.
Many features are better, some worse, most are different.

Resolve Studio 18.1.2, MacOS 12.6.2
MacBook M1 Pro, 16 GPU cores, 32 GB RAM
and
iMac 2017, Radeon 580, 32 GB RAM
Speed Editor

ljfrench

  • Posts: 5
  • Joined: Wed Dec 19, 2018 3:19 pm
  • Real Name: Leonard French

PostTue 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.

Image
Image
Image

Rolling back to Resolve Studio 16.2.6 works fine:

Image

Thanks,
Leonard French
Lawful Masses

User avatar

Dwaine Maggart

Blackmagic Design

  • Posts: 9948
  • Joined: Wed Aug 22, 2012 2:53 pm

PostTue 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.

Dwaine Maggart
Blackmagic Design DaVinci Support

User avatar

X-Raym

  • Website
  • Posts: 125
  • Joined: Thu Apr 18, 2013 4:05 pm
  • Location: France
  • Real Name: Raymond Radet

PostWed 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…

My DaVinci Resolve Scripts: https://github.com/X-Raym/DaVinci-Resolve-Scripts
Donation: https://paypal.me/extremraym

Chris A

  • Posts: 1
  • Joined: Sat Oct 10, 2020 3:39 pm
  • Real Name: chris Aspinall

PostSat 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

User avatar

Dwaine Maggart

Blackmagic Design

  • Posts: 9948
  • Joined: Wed Aug 22, 2012 2:53 pm

PostMon 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.

Dwaine Maggart
Blackmagic Design DaVinci Support

Barnsy

  • Posts: 1
  • Joined: Wed Oct 14, 2020 12:56 pm
  • Real Name: Adam Barns

PostWed Oct 14, 2020 1:00 pm

209.png
Error209
209.png (5.29 KiB) Viewed 47089 times

Same issue for me, updated to latest NVIDIA driver 456.71

GTX 760

User avatar

Dwaine Maggart

Blackmagic Design

  • Posts: 9948
  • Joined: Wed Aug 22, 2012 2:53 pm

PostWed 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.

Dwaine Maggart
Blackmagic Design DaVinci Support

nhoover

  • Posts: 4
  • Joined: Sat Jul 07, 2018 5:48 pm
  • Real Name: Nathan Hoover

PostFri 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

PostFri 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.

DaVinci Resolve Product Manager

User avatar

Dwaine Maggart

Blackmagic Design

  • Posts: 9948
  • Joined: Wed Aug 22, 2012 2:53 pm

PostFri 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.

Dwaine Maggart
Blackmagic Design DaVinci Support

nhoover

  • Posts: 4
  • Joined: Sat Jul 07, 2018 5:48 pm
  • Real Name: Nathan Hoover

PostFri 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.

SimonBrown

  • Website
  • Posts: 4
  • Joined: Tue Aug 25, 2020 6:42 pm
  • Location: Worcestershire, UK
  • Real Name: Simon Brown

PostThu 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…?

User avatar

Dwaine Maggart

Blackmagic Design

  • Posts: 9948
  • Joined: Wed Aug 22, 2012 2:53 pm

PostThu 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.

Dwaine Maggart
Blackmagic Design DaVinci Support

SimonBrown

  • Website
  • Posts: 4
  • Joined: Tue Aug 25, 2020 6:42 pm
  • Location: Worcestershire, UK
  • Real Name: Simon Brown

PostThu 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. :(

SimonBrown

  • Website
  • Posts: 4
  • Joined: Tue Aug 25, 2020 6:42 pm
  • Location: Worcestershire, UK
  • Real Name: Simon Brown

PostMon 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.

User avatar

Dwaine Maggart

Blackmagic Design

  • Posts: 9948
  • Joined: Wed Aug 22, 2012 2:53 pm

PostMon 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.

Dwaine Maggart
Blackmagic Design DaVinci Support

roadrunner

  • Posts: 33
  • Joined: Wed Jul 29, 2020 1:48 am
  • Real Name: Nathan Tyler

PostTue 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. ;)

System 1: Dell Precision 7810, Dual Xeon 2620, 72GB RAM, GeForce 1080ti 11GB, Win10 pro, Resolve Studio 17.4.
System 2: Custom build Intel i7-12700K, 64GB RAM, GeForce 1080ti 11GB, Ubuntu 22.04, Resolve Studio 17.4.

SimonBrown

  • Website
  • Posts: 4
  • Joined: Tue Aug 25, 2020 6:42 pm
  • Location: Worcestershire, UK
  • Real Name: Simon Brown

PostTue 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.

User avatar

Dwaine Maggart

Blackmagic Design

  • Posts: 9948
  • Joined: Wed Aug 22, 2012 2:53 pm

PostTue 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

Dwaine Maggart
Blackmagic Design DaVinci Support

User avatar

pascar1973

  • LinkedIn
  • Posts: 20
  • Joined: Fri Jan 03, 2020 11:33 am
  • Location: Italy
  • Real Name: Paolo Scaramuzzino

PostThu 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.

Uli Plank

  • Posts: 16601
  • Joined: Fri Feb 08, 2013 2:48 am
  • Location: Germany and Indonesia

PostFri Nov 20, 2020 1:20 am

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

Don’t approach DR with your preconceptions from another NLE.
Many features are better, some worse, most are different.

Resolve Studio 18.1.2, MacOS 12.6.2
MacBook M1 Pro, 16 GPU cores, 32 GB RAM
and
iMac 2017, Radeon 580, 32 GB RAM
Speed Editor

User avatar

Dwaine Maggart

Blackmagic Design

  • Posts: 9948
  • Joined: Wed Aug 22, 2012 2:53 pm

PostFri 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.

Dwaine Maggart
Blackmagic Design DaVinci Support

Conner John

  • Posts: 4
  • Joined: Sat Nov 21, 2020 1:39 am
  • Real Name: Conner Peterson

PostSat 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

User avatar

pascar1973

  • LinkedIn
  • Posts: 20
  • Joined: Fri Jan 03, 2020 11:33 am
  • Location: Italy
  • Real Name: Paolo Scaramuzzino

PostSun 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.

Bernard74

  • Posts: 3
  • Joined: Fri Apr 17, 2020 7:46 pm
  • Real Name: Bernard Ravier

PostThu 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

User avatar

Dwaine Maggart

Blackmagic Design

  • Posts: 9948
  • Joined: Wed Aug 22, 2012 2:53 pm

PostThu 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?

Dwaine Maggart
Blackmagic Design DaVinci Support

DaVinci Resolve от Blackmagic Design — популярный бесплатный видеоредактор, доступный на нескольких платформах. Однако некоторые пользователи сообщают, что DaVinci Resolve продолжает падать при редактировании видео.

В отличие от Adobe Premier Pro, популярный видеоредактор DaVinci Resolve лучше работает с системой с выделенным графическим процессором. Отсутствие которых может привести к случайным сбоям.

В этой статье мы рассмотрим несколько шагов по устранению неполадок, которые помогут вам навсегда решить проблемы сбоев DaVinci Resolve.

1. Изменить приоритет процесса

Решение DaVinci продолжает падать

  1. Убедитесь, что DaVinci Resolve запущен.
  2. Щелкните правой кнопкой мыши на панели задач и выберите «Диспетчер задач».
  3. Откройте детали
  4. Прокрутите вниз и щелкните правой кнопкой мыши Разрешить. исполняемый файл
  5. Перейдите в «Установить приоритет» и выберите «Высокий».

Вот и все. Попробуйте поработать над любым из ваших проектов и проверьте, решена ли проблема. Обратите внимание, что при каждом перезапуске DaVinci Resolve вам, возможно, придется устанавливать высокий приоритет.

2. Установите драйвер Nvidia Studio

Решение DaVinci продолжает падать

  1. Запустите опыт Nvidia GeForce.
  2. Нажмите на значок меню (три точки в правом верхнем углу).
  3. Выберите Студийный драйвер.
  4. GeForce Experience загрузит и установит драйвер Nvidia Studio.

Если у вас уже установлены драйверы Studio, попробуйте выполнить чистую установку.

Решение DaVinci продолжает падать

  1. Загрузите и установите программу удаления драйвера дисплея.
  2. Запустите инструмент и выберите графическую карту,
  3. Нажмите «Очистить» и перезапустите.
  4. После удаления загрузите последнюю версию драйвера NVIDA Studio.
  5. Запустите установщик и установите необходимые пакеты через выборочную установку.
  6. Перезагрузите компьютер и перезапустите DaVinci Resolve.

Драйвер Nvidia Studio также может вызывать сбои DaVinci Resolve. Попробуйте выполнить чистую установку драйверов, чтобы устранить проблемы.

Если вам нужно правильно установить этот драйвер Nvidia, не вызывая серьезных проблем, лучше попробуйте специальный инструмент обновления драйверов и эффективно установите или обновите любые драйверы на вашем ПК.

3. Какая версия DaVinci Resolve лучше всего подходит для предотвращения сбоев?

Начнем с наиболее распространенной причины сбоев DaVinci Resolve. DaVinci Resolve 15 был пронизан несколькими сбоями и ошибками, которые приводили к частым сбоям.

Эти сбои также происходили в системе, в которой было достаточно оборудования для запуска видеоредактора. Тем не менее, установка последней версии DaVinci Resolve 16, похоже, устранила многие проблемы с программным обеспечением.

Обновить DaVinci Resolve

Решение DaVinci продолжает падать при запуске

  1. Запустите приложение Разрешение.
  2. Щелкните DaVinci Resolve.
  3. Выберите Проверить наличие обновлений.
  4. Загрузите и установите все ожидающие обновления.

После установки перезапустите приложение и проверьте, решена ли проблема сбоя. Если нет, возможно, вам придется удалить, а затем переустановить последнюю версию, чтобы устранить проблему. Вот как это сделать.

Решение DaVinci продолжает падать при запуске

  1. Нажмите клавишу Windows + R.
  2. Введите appwiz. cpl и нажмите OK.
  3. В Панели управления выберите DaVinci Resolve.
  4. Нажмите «Удалить», а затем подтвердите действие.
  5. После удаления загрузите последнюю версию DaVinci Resolve отсюда.
  6. Запустите установщик и проверьте наличие улучшений.

4. Включите мультимониторинг IGPU

Davinci Resolve зависает

  1. Выключите компьютер.
  2. Нажмите кнопку питания, чтобы перезагрузить компьютер. При перезапуске начните нажимать клавишу настройки (F2) на клавиатуре, чтобы войти в BIOS.
    Примечание. Клавиша настройки обычно отображается на начальном экране. Обратитесь к руководству пользователя для вашего ноутбука или материнской платы (в случае настольного компьютера), чтобы найти ключ настройки.
  3. В меню BIOS откройте вкладку Advanced.
  4. Найдите IGPU Multi-Monitoring и убедитесь, что он включен.
  5. Сохраните изменения и выйдите.

5. Проверьте совместимость графического процессора

Отключить встроенный графический процессор

Davinci Resolve зависает

  1. Нажмите клавишу Windows + R.
  2. Введите devmgmt.msc и нажмите OK.
  3. В диспетчере устройств разверните раздел «Адаптер дисплея».
  4. Щелкните правой кнопкой мыши встроенный графический процессор Intel.
  5. Выберите Отключить устройство.
  6. Откройте DaVinci Resolve и проверьте, не возникают ли сбои по-прежнему.

Обновление графического процессора

Как обсуждалось ранее, DaVinci Resolve — это приложение, интенсивно использующее GPU. Для стабильной работы рекомендуется установить достойную дискретную видеокарту. Если у вас есть только интегрированный графический процессор Intel, самое время подумать о переходе на выделенный графический процессор.

Решение DaVinci продолжает давать сбой. Обычно это происходит из-за несовместимости драйвера графического процессора или ошибки в самом программном обеспечении. Выполните шаги один за другим, чтобы диагностировать и устранить проблемы, вызывающие сбои.


  • Login
  • Register
  • FAQ
  • Search
  • It is currently Wed Jun 21, 2023 7:12 pm
  • Print view

Unsupported GPU Processing Mode with 17.4.6

  • Message

Grilli.P

  • Posts: 6
  • Joined: Sat Apr 02, 2022 8:05 pm
  • Real Name: Grilli Paolo

PostSat Apr 02, 2022 8:08 pm

j’ve installed the latest version 17.4.6 but it doesn’t work, it tells me «Unsopported GPU Processing Mode», until the previous version everything was fine . Windows 11 os , da vinci resolve free
thanks

Jim Simon

  • Posts: 25879
  • Joined: Fri Dec 23, 2016 1:47 am

PostSun Apr 03, 2022 3:40 pm

Set the following manually.

Preferences>System>Memory and GPU>GPU Configuration

My Biases:

You NEED training.
You NEED a desktop.
You NEED a calibrated (non-computer) display.

fynflood

  • Posts: 9
  • Joined: Wed Mar 10, 2021 11:44 pm
  • Real Name: Adam Elkins

PostSun Apr 03, 2022 3:55 pm

Jim Simon wrote:Set the following manually.

Preferences>System>Memory and GPU>GPU Configuration

I’m suffering from this one too — unfortunately Davinci isn’t able to use my GPU at all anymore, I have nothing to select in the configuration.

Code: Select all
[0x000007e0] | GPUDetect            | INFO  | 2022-04-02 17:14:18,766 | Starting GPUDetect 1.2_1-a9
[0x000007e0] | GPUDetect            | WARN  | 2022-04-02 17:14:19,227 | Ignoring unmatched DirectX GPU "AMD Radeon RX 6700 XT".
[0x000007e0] | GPUDetect            | ERROR | 2022-04-02 17:14:19,227 | No matched GPUs found.
[0x000007e0] | Main.GPUConfig       | INFO  | 2022-04-02 17:14:19,228 | Compute API set to automatic, defaulting to Unknown.
[0x000007e0] | Main.GPUConfig       | INFO  | 2022-04-02 17:14:19,228 | Unsupported API Unknown, defaulting to Unknown.
[0x000007e0] | Main.GPUConfig       | ERROR | 2022-04-02 17:14:19,228 | Failed to select a valid compute API.
[0x000007e0] | Main.GPUConfig       | INFO  | 2022-04-02 17:14:19,228 | Automatic GPU Selection:
[0x000007e0] | Main.GPUConfig       | ERROR | 2022-04-02 17:14:19,228 |   No GPUs selected!
Attachments
DaVinci-Resolve-logs-20220402_171759.zip
(418.42 KiB) Downloaded 212 times

GarethM

  • Posts: 1
  • Joined: Sun Apr 03, 2022 8:11 pm
  • Real Name: Gareth Maudsley

PostSun Apr 03, 2022 8:19 pm

I have just come back to edit some footage (yay! motivation) and had the same issue.
I did try a re-install as well but got the same issue.

My laptop has an apu (ryzen 5 radeon) and it lists in the selection bar but claims to be A) unknown (though it lists the chip set exactly) and B) that it is unsupported now.
I hope there is a work around for this, so joined to see if help is on it’s way.

Grilli.P

  • Posts: 6
  • Joined: Sat Apr 02, 2022 8:05 pm
  • Real Name: Grilli Paolo

PostTue Apr 05, 2022 3:08 pm

thanks for your reply

from Preferences>System>Memory and GPU>GPU Configuration GPU voices are disabled
with drs 17.4.5 work wery well

from DaVinci-Resolve-logs 17.4.6

Code: Select all
[0x000007fc] | Main                 | INFO  | 2022-03-07 16:55:35,782 | Running DaVinci Resolve v17.4.4.0007 (Windows/MSVC x86_64)
[0x000007fc] | Main                 | INFO  | 2022-03-07 16:55:35,782 | BMD_BUILD_UUID 48cbf344-2fb7-4e76-b0b3-d8cebdbfffed
[0x000007fc] | Main                 | INFO  | 2022-03-07 16:55:35,782 | BMD_GIT_COMMIT 00b0f21d19732b5e6bda07860bae535982fd8715
[0x000007fc] | GPUDetect            | INFO  | 2022-03-07 16:55:35,782 | Starting GPUDetect 1.2-a3
[0x000007fc] | GPUDetect            | INFO  | 2022-03-07 16:55:36,743 | Done in 952 ms.
[0x000007fc] | GPUDetect            | INFO  | 2022-03-07 16:55:36,743 | Detected System:
[0x000007fc] | GPUDetect            | INFO  | 2022-03-07 16:55:36,743 |   - OS: Windows 10 Home (Build 22000)
[0x000007fc] | GPUDetect            | INFO  | 2022-03-07 16:55:36,743 |   - Model: ASUSTeK N75SF
[0x000007fc] | GPUDetect            | INFO  | 2022-03-07 16:55:36,743 |   - System ID: e355f268-73d2-414e-b056-e26a9f314145
[0x000007fc] | GPUDetect            | INFO  | 2022-03-07 16:55:36,743 |   - CPU: Intel Core i7-2670QM, 8 threads, x86-64
[0x000007fc] | GPUDetect            | INFO  | 2022-03-07 16:55:36,743 |   - RAM: 5.2 GiB used of 15.9 GiB
[0x000007fc] | GPUDetect            | INFO  | 2022-03-07 16:55:36,743 |   - NVIDIA GPU Driver: 391.35, supports CUDA 9.1
[0x000007fc] | GPUDetect            | INFO  | 2022-03-07 16:55:36,743 | Detected 2 GPUs:
[0x000007fc] | GPUDetect            | INFO  | 2022-03-07 16:55:36,743 |   - "NVIDIA GeForce GT 555M" (gpu:637c5781.5150080d)
[0x000007fc] | GPUDetect            | INFO  | 2022-03-07 16:55:36,743 |     Discrete, 0 B used of 1.9 GiB VRAM, PCI:1:0 (x16)
[0x000007fc] | GPUDetect            | INFO  | 2022-03-07 16:55:36,743 |     Matches: CUDA, DirectX, NVAPI, OpenCL, Win32
[0x000007fc] | GPUDetect            | INFO  | 2022-03-07 16:55:36,743 |   - "Intel HD Graphics 3000" (gpu:19815edb.5f6737f1) <- Main Display GPU
[0x000007fc] | GPUDetect            | INFO  | 2022-03-07 16:55:36,743 |     Discrete, 2 GiB VRAM, PCI:0:2.0
[0x000007fc] | GPUDetect            | INFO  | 2022-03-07 16:55:36,743 |     Matches: DirectX, OpenCL, Win32
[0x000007fc] | GPUDetect            | INFO  | 2022-03-07 16:55:36,743 | Detected 1 monitors:
[0x000007fc] | GPUDetect            | INFO  | 2022-03-07 16:55:36,743 |   - "Generic PnP Monitor" <- Main Monitor
[0x000007fc] | GPUDetect            | INFO  | 2022-03-07 16:55:36,743 |     1920x1080, connected to "Intel HD Graphics 3000" (gpu:19815edb.5f6737f1)
[0x000007fc] | Main.GPUConfig       | INFO  | 2022-03-07 16:55:36,743 | Selected compute API: OpenCL
[0x000007fc] | Main.GPUConfig       | INFO  | 2022-03-07 16:55:36,743 | Manual GPU Selection:
[0x000007fc] | Main.GPUConfig       | INFO  | 2022-03-07 16:55:36,743 |   - "NVIDIA GeForce GT 555M" (gpu:637c5781.5150080d)
[0x000007fc] | IO                   | INFO  | 2022-03-07 16:55:36,743 | RED InitializeSdk with library path at C:ProgramDataBlackmagic DesignDaVinci ResolveSupportLibraries
[0x000007fc] | IO                   | INFO  | 2022-03-07 16:55:36,790 | R3DAPI 8.1.1-51614 (20211117 Wx64S) R3DSDK 8.1.1-51614 (20211117 Wx64D C1B3) RED OPENCL 8.1.1-51623 (20211117) [C:ProgramDataBlackmagic DesignDaVinci Resolve

from DaVinci-Resolve-logs 17.4.5

Code: Select all
[0x000007fc] | Main                 | INFO  | 2022-03-07 16:55:35,782 | Running DaVinci Resolve v17.4.4.0007 (Windows/MSVC x86_64)
[0x000007fc] | Main                 | INFO  | 2022-03-07 16:55:35,782 | BMD_BUILD_UUID 48cbf344-2fb7-4e76-b0b3-d8cebdbfffed
[0x000007fc] | Main                 | INFO  | 2022-03-07 16:55:35,782 | BMD_GIT_COMMIT 00b0f21d19732b5e6bda07860bae535982fd8715
[0x000007fc] | GPUDetect            | INFO  | 2022-03-07 16:55:35,782 | Starting GPUDetect 1.2-a3
[0x000007fc] | GPUDetect            | INFO  | 2022-03-07 16:55:36,743 | Done in 952 ms.
[0x000007fc] | GPUDetect            | INFO  | 2022-03-07 16:55:36,743 | Detected System:
[0x000007fc] | GPUDetect            | INFO  | 2022-03-07 16:55:36,743 |   - OS: Windows 10 Home (Build 22000)
[0x000007fc] | GPUDetect            | INFO  | 2022-03-07 16:55:36,743 |   - Model: ASUSTeK N75SF
[0x000007fc] | GPUDetect            | INFO  | 2022-03-07 16:55:36,743 |   - System ID: e355f268-73d2-414e-b056-e26a9f314145
[0x000007fc] | GPUDetect            | INFO  | 2022-03-07 16:55:36,743 |   - CPU: Intel Core i7-2670QM, 8 threads, x86-64
[0x000007fc] | GPUDetect            | INFO  | 2022-03-07 16:55:36,743 |   - RAM: 5.2 GiB used of 15.9 GiB
[0x000007fc] | GPUDetect            | INFO  | 2022-03-07 16:55:36,743 |   - NVIDIA GPU Driver: 391.35, supports CUDA 9.1
[0x000007fc] | GPUDetect            | INFO  | 2022-03-07 16:55:36,743 | Detected 2 GPUs:
[0x000007fc] | GPUDetect            | INFO  | 2022-03-07 16:55:36,743 |   - "NVIDIA GeForce GT 555M" (gpu:637c5781.5150080d)
[0x000007fc] | GPUDetect            | INFO  | 2022-03-07 16:55:36,743 |     Discrete, 0 B used of 1.9 GiB VRAM, PCI:1:0 (x16)
[0x000007fc] | GPUDetect            | INFO  | 2022-03-07 16:55:36,743 |     Matches: CUDA, DirectX, NVAPI, OpenCL, Win32
[0x000007fc] | GPUDetect            | INFO  | 2022-03-07 16:55:36,743 |   - "Intel HD Graphics 3000" (gpu:19815edb.5f6737f1) <- Main Display GPU
[0x000007fc] | GPUDetect            | INFO  | 2022-03-07 16:55:36,743 |     Discrete, 2 GiB VRAM, PCI:0:2.0
[0x000007fc] | GPUDetect            | INFO  | 2022-03-07 16:55:36,743 |     Matches: DirectX, OpenCL, Win32
[0x000007fc] | GPUDetect            | INFO  | 2022-03-07 16:55:36,743 | Detected 1 monitors:
[0x000007fc] | GPUDetect            | INFO  | 2022-03-07 16:55:36,743 |   - "Generic PnP Monitor" <- Main Monitor
[0x000007fc] | GPUDetect            | INFO  | 2022-03-07 16:55:36,743 |     1920x1080, connected to "Intel HD Graphics 3000" (gpu:19815edb.5f6737f1)
[0x000007fc] | Main.GPUConfig       | INFO  | 2022-03-07 16:55:36,743 | Selected compute API: OpenCL
[0x000007fc] | Main.GPUConfig       | INFO  | 2022-03-07 16:55:36,743 | Manual GPU Selection:
[0x000007fc] | Main.GPUConfig       | INFO  | 2022-03-07 16:55:36,743 |   - "NVIDIA GeForce GT 555M" (gpu:637c5781.5150080d)
[0x000007fc] | IO                   | INFO  | 2022-03-07 16:55:36,743 | RED InitializeSdk with library path at C:ProgramDataBlackmagic DesignDaVinci ResolveSupportLibraries
[0x000007fc] | IO                   | INFO  | 2022-03-07 16:55:36,790 | R3DAPI 8.1.1-51614 (20211117 Wx64S) R3DSDK 8.1.1-51614 (20211117 Wx64D C1B3) RED OPENCL 8.1.1-51623 (20211117) [C:ProgramDataBlackmagic DesignDaVinci Resolve

fynflood

  • Posts: 9
  • Joined: Wed Mar 10, 2021 11:44 pm
  • Real Name: Adam Elkins

PostWed Apr 06, 2022 8:04 pm

GarethM wrote:I have just come back to edit some footage (yay! motivation) and had the same issue.
I did try a re-install as well but got the same issue.

My laptop has an apu (ryzen 5 radeon) and it lists in the selection bar but claims to be A) unknown (though it lists the chip set exactly) and B) that it is unsupported now.
I hope there is a work around for this, so joined to see if help is on it’s way.

I was able to resolve this by re-installing the latest Radeon drivers and making sure the «factory reset» box is checked.

Mac McIver

  • Posts: 8
  • Joined: Fri Jan 20, 2017 7:32 am

PostWed Apr 06, 2022 9:35 pm

In 17.4.5 I got a popup on launch saying unsupported GPU was disabled. howeverI could continue to use Resolve to edit.
17.4.6 launches but will not run until I change configuration settings (which happened automaticaly in 17.4.5) but does not allow me to change them, so I cannot run the program.
I’ve had to re-install the older version.

Grilli.P

  • Posts: 6
  • Joined: Sat Apr 02, 2022 8:05 pm
  • Real Name: Grilli Paolo

PostSun Apr 10, 2022 9:59 am

all GPU (Intel HD Graphics 3000 and NVDIA GeForce GT 555M) are updated to the latest software version but I can’t select either of them

PostMon Apr 11, 2022 2:20 am

Grilli.P wrote:all GPU (Intel HD Graphics 3000 and NVDIA GeForce GT 555M) are updated to the latest software version but I can’t select either of them

How old is the computer?
The GT555M is particularly old and i don’t recall the HD Graphics 3000 but it could be they just don’t support OpenCL 1.2 as they are too old. That OpenCL version is a requirement.

DaVinci Resolve Product Manager

Grilli.P

  • Posts: 6
  • Joined: Sat Apr 02, 2022 8:05 pm
  • Real Name: Grilli Paolo

PostMon Apr 11, 2022 4:38 pm

with drs 17.4.5 OpenCL is installed but not with drs 17.4.6
my computer is 10 yeras old

Noerde

  • Posts: 108
  • Joined: Tue Mar 30, 2021 12:37 pm
  • Real Name: Panu Artimo

PostMon Apr 11, 2022 4:56 pm

Grilli.P wrote:with drs 17.4.5 OpenCL is installed but not with drs 17.4.6
my computer is 10 yeras old

Then I think it’s better to stay with 17.4.5 or older right?

User avatar

Dwaine Maggart

Blackmagic Design

  • Posts: 10421
  • Joined: Wed Aug 22, 2012 2:53 pm

PostMon Apr 11, 2022 5:38 pm

Intel 3000 and 4000 series iGPU’s don’t work for Resolve 17.x.

The NVIDIA GT 555M supports CUDA Compute 2.1. Minimum support for Resolve 17 is 3.5.

The GT 555M might sort of work in OpenCL mode, but it will work poorly and likely won’t work properly for some things.

If anything works at all in 17.4.5 but stops in 17.4.6, the only surprising thing would be that it works at all in 17.4.5.

Your computer GPU resources are simply not adequate for Resolve 17.

Dwaine Maggart
Blackmagic Design DaVinci Support

Grilli.P

  • Posts: 6
  • Joined: Sat Apr 02, 2022 8:05 pm
  • Real Name: Grilli Paolo

PostWed Apr 27, 2022 4:59 pm

now drs 17.4.5 no longer starts, there is the messagge of unsopported gpu
j’ve installed drs 16 but when import Local Database.resolve.diskdb (from drs 17.4.5) there is the message of incompatible version
my job is lost ?

PostWed Apr 27, 2022 9:00 pm

If you didn’t follow the instruction to back up your database before upgrading it, then yes you have lost your project as databases between major upgrades are not backwards compatible.

Attachments
Database Management.JPG
Database Management.JPG (28.14 KiB) Viewed 16512 times

Resolve Studio 18.5b4 Build 31
Dell XPS 8700 i7-4790 4 core, 24GB RAM, 2 x Samsung Evo SSDs, GTX1060/6GB (535.98 Studio driver), Win10 Home (22H2), Speed Editor, Faderport mk1, Eizo ColorEdge CS230 + BenQ GW2270, Canon C100mk2, Atomos Ninja 2, Zoom H2n.

RolfBirlenbach

  • Posts: 10
  • Joined: Sat Jan 23, 2021 11:37 am
  • Real Name: Rolf Birlenbach

PostTue Jun 28, 2022 6:53 am

Hello,

I have a newer system with
Intel(R) Core(TM) i7-9700KF CPU @ 3.60GHz
128 GB
and a 8GB AMD graphics card (AMD Radeon Pro W5500 PCI 4)

I get the same error.

The windows system has installed the default system driver with windows update and after updating to the last AMD update the Resolve 17 was not more able to find the AMD Card.

Then I removed all the drivers and make a factory reset for the installation of the AMD software.

After reinstallation the problem was solved and the system was woking fine, also with the new Resolve 18 (BUBLIC BETA)

Best regards

Rolf

Grilli.P

  • Posts: 6
  • Joined: Sat Apr 02, 2022 8:05 pm
  • Real Name: Grilli Paolo

PostThu Jul 28, 2022 3:41 pm

RolfBirlenbach wrote:Hello,

I have a newer system with
Intel(R) Core(TM) i7-9700KF CPU @ 3.60GHz
128 GB
and a 8GB AMD graphics card (AMD Radeon Pro W5500 PCI 4)

I get the same error.

The windows system has installed the default system driver with windows update and after updating to the last AMD update the Resolve 17 was not more able to find the AMD Card.

Then I removed all the drivers and make a factory reset for the installation of the AMD software.

After reinstallation the problem was solved and the system was woking fine, also with the new Resolve 18 (BUBLIC BETA)

Best regards

Rolf

you are very lucky but be careful
i have always used only drs 17 and now i can only use drs 16
maybe gpudetect.dll is not working so well

RolfBirlenbach

  • Posts: 10
  • Joined: Sat Jan 23, 2021 11:37 am
  • Real Name: Rolf Birlenbach

PostMon Sep 05, 2022 2:15 pm

We found that Mircosoft is replacing the org. Driver from AMD Cards.

Than you get an error opening the AMD Toolbox.

AMD Link https://www.amd.com/en/support/kb/faq/pa-300

After replaceing the driver to the newest AMD Driver without restoring factory defalts you get the error of an unsuported GPU!

1st: Disable «Device Installation Settings» by «NO» in the system setting. (AMD KB)

2nd: Only when you uninstall the AMD driver completly and then reboot.
Then install the AMD Driver with factory defalts and don not keep user data follows by a second reboot.
Install all the NEW AMD Drivers

3rd: Clean Install DaVinci new by uninstalling old version and install the new version after reboot.

This can fix the problems and worked for me.

Best regards

Rolf

jorisdeman

  • Posts: 3
  • Joined: Mon Sep 26, 2022 6:32 am
  • Real Name: Joris de Man

PostMon Sep 26, 2022 6:39 am

Hi,

when I wanted to start up resolve today I got this message for the first time. In the GPU configuration menu in the settings my GPU is greyed out and I can’t select it. I’m guessing this is because of a new version of davinci that has been installed? I haven’t personally updated the program but maybe it did automatically. I want to reinstall the program to an older version but I’m not sure what would happen to the projects I was working on. Is there a way I can download those projects without being able to open the program? Or will they still be there if I reinstall the program?

thanks,
Joris

User avatar

Dwaine Maggart

Blackmagic Design

  • Posts: 10421
  • Joined: Wed Aug 22, 2012 2:53 pm

PostMon Sep 26, 2022 5:49 pm

Not enough info to answer your question.

Mac or Windows?

What version does the splash screen show when you launch Resolve?

Dwaine Maggart
Blackmagic Design DaVinci Support

jorisdeman

  • Posts: 3
  • Joined: Mon Sep 26, 2022 6:32 am
  • Real Name: Joris de Man

PostTue Sep 27, 2022 5:45 am

I’m on windows 10. When I launch drs it says 17, but I don’t know what version exactly

User avatar

Dwaine Maggart

Blackmagic Design

  • Posts: 10421
  • Joined: Wed Aug 22, 2012 2:53 pm

PostWed Sep 28, 2022 6:56 am

In a File Explorer window, go to:

C:Program FilesBlackmagic DesignDaVinci 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.

Dwaine Maggart
Blackmagic Design DaVinci Support

jorisdeman

  • Posts: 3
  • Joined: Mon Sep 26, 2022 6:32 am
  • Real Name: Joris de Man

PostWed Sep 28, 2022 6:07 pm

I’m not sure which file I have to select when doing the file save, sorry for my lack of computer knowledge haha :P

Romain Dgv

  • Posts: 10
  • Joined: Sat Oct 15, 2022 12:59 pm
  • Real Name: Romain Degrave

PostSat Oct 15, 2022 2:15 pm

Hey,

I have an issue with Resolve. For a week, every time I try to launch the app it displays the message «unsupported gpu processing mode». I tried different things to fix it, like reinstalling other versions of Resolve, changing gpu drivers versions … but without success. I got a gtx1070 by the way. This problem started teh 10 october, just after I deleted the «bink2w64.dll» from the System32 to fix another issue with the app «Overwatch 2» (putting the dll back didn’t fixed the problem with Resolve, so this may be not linked). I would be super gratefull if someone could help me to fix it. Thank you in advance !

Romain.

User avatar

Dwaine Maggart

Blackmagic Design

  • Posts: 10421
  • Joined: Wed Aug 22, 2012 2:53 pm

PostMon Oct 17, 2022 8:15 pm

In a File Explorer window, go to:

C:Program FilesBlackmagic DesignDaVinci 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.

Dwaine Maggart
Blackmagic Design DaVinci Support

Romain Dgv

  • Posts: 10
  • Joined: Sat Oct 15, 2022 12:59 pm
  • Real Name: Romain Degrave

PostSun Oct 23, 2022 5:01 pm

Hey, There are the Resolves logs and the msinfo files you asked for !

https://1drv.ms/u/s!AgAZlbOwv4cXii3RR8K … 2?e=kuMDSE

The problem seems to be linked to OpenCL and CUDA but I do not know how to enable again theses options.
Thank you in advance for your help !

Romain.

User avatar

Dwaine Maggart

Blackmagic Design

  • Posts: 10421
  • Joined: Wed Aug 22, 2012 2:53 pm

PostThu Oct 27, 2022 8:07 am

The problem is that when Resolve does a GPU detect, your GPU reports:

NVIDIA GPU Driver: 522.30, supports CUDA -1.-1

Which is a no good response. That’s the current driver, so it seems like it should work. But maybe the current driver has an issue.

So go the the NVIDIA driver download site, select Beta and Older drivers, enter your GPU and OS info, select a DCH Windows Driver type, and download and install the 512.15 Studio Driver. And when you run the installer, select the custom and Clean install options.

If it still doesn’t work, send another Resolve log and NFO file.

Dwaine Maggart
Blackmagic Design DaVinci Support

Romain Dgv

  • Posts: 10
  • Joined: Sat Oct 15, 2022 12:59 pm
  • Real Name: Romain Degrave

PostSun Oct 30, 2022 7:47 pm

Hi,

I have installed the DCH driver following the way you described, but unfortunately it still doesnt work.

Thus, I link you new Resolve logs and NFO.

https://1drv.ms/u/s!AgAZlbOwv4cXii3RR8K … 2?e=MfL6cS

Thank you in advance, Romain.

User avatar

Dwaine Maggart

Blackmagic Design

  • Posts: 10421
  • Joined: Wed Aug 22, 2012 2:53 pm

PostTue Nov 01, 2022 5:40 pm

OK, that verifies it’s not a driver related issue.

We know that the NVIDIA Nsight stuff can cause GPU detect issues. But your system Environment Variables don’t have the typical definitions that cause issues, which are these 2 below:

CUDA_INJECTION32_PATH=C:Program Files (x86)NVIDIA CorporationNsight
Visual Studio Edition
2019.2MonitorCommonInjection32Nvda.Cuda.Injection.dll
CUDA_INJECTION64_PATH=C:Program Files (x86)NVIDIA CorporationNsight
Visual Studio Edition

However, I see in the Program Groups area that you have several NVIDIA Nsight packages installed, as well as a couple of CUDA Toolkit packages. I’m guessing one of those is causing the issue.

Your system environment variables do have the following defined:

NVTOOLSEXT_PATH C:Program FilesNVIDIA CorporationNvToolsExt <SYSTEM>
CUDA_PATH C:Program FilesNVIDIA GPU Computing ToolkitCUDAv11.8 <SYSTEM>
CUDA_PATH_V11_8 C:Program FilesNVIDIA GPU Computing ToolkitCUDAv11.8 <SYSTEM>

I would suggest removing those 3 environment variables and seeing if that solves the issue.

Dwaine Maggart
Blackmagic Design DaVinci Support

Warmonger

  • Posts: 3
  • Joined: Wed Nov 02, 2022 9:02 am
  • Real Name: Tomasz Zielinski

PostWed Nov 02, 2022 9:07 am

Hello, I’m having the issue with RTX 3050 now. Suprisingly, it certainly worked back in March and I already rendered two videos with it.

I already tried to install NVidia drivers (from Experience and manual download) as well as DaVinci Resolve Studio itself, upgrading to version 18. Nothing has changed and I can’t use the software.

Attachments
Resolve RTX 3050.png
Resolve RTX 3050.png (18.78 KiB) Viewed 7781 times

User avatar

Dwaine Maggart

Blackmagic Design

  • Posts: 10421
  • Joined: Wed Aug 22, 2012 2:53 pm

PostWed Nov 02, 2022 4:39 pm

In a File Explorer window, go to:

C:Program FilesBlackmagic DesignDaVinci 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.

Dwaine Maggart
Blackmagic Design DaVinci Support

Romain Dgv

  • Posts: 10
  • Joined: Sat Oct 15, 2022 12:59 pm
  • Real Name: Romain Degrave

PostWed Nov 02, 2022 5:38 pm

Hi,

I removed the two environment variables that you showed (the third one was in the same folder than the second one), but unfortunately it didnt fixed the issue.

Likewise, given that the problem with Resolve started after the»bink2w64.dll» was removed from my System32, this may be linked to that (I have no clue, but this could be a useful intel to you).

Thank you in advance for your help, Romain.

User avatar

Dwaine Maggart

Blackmagic Design

  • Posts: 10421
  • Joined: Wed Aug 22, 2012 2:53 pm

PostWed Nov 02, 2022 6:18 pm

I don’t think the bink2w64.dll file should have any effect on Resolve. I don’t see that on any of my Windows systems.

I guess my last suggestion would be to remove the NVIDIA driver with DDU and then reinstall it.

Here is a link on how to use DDU. Follow the details in the thread, and just choose the NVIDIA GPU instead of Intel:

viewtopic.php?f=21&t=119852&hilit=+ddu#p659861

After you’ve uninstalled it, hopefully you still have the 512.15 Studio Driver installer. Run that to reinstall the 512.15 driver and then see what Resolve does.

Dwaine Maggart
Blackmagic Design DaVinci Support

rogerharding

  • Posts: 1
  • Joined: Sat Jan 04, 2020 3:23 pm
  • Real Name: Roger Harding

PostWed Nov 02, 2022 9:28 pm

It seems pretty clear that a lot of users are experiencing this problem.

Will there be a bug fix ?

Warmonger

  • Posts: 3
  • Joined: Wed Nov 02, 2022 9:02 am
  • Real Name: Tomasz Zielinski

PostFri Nov 04, 2022 8:13 am

Dwaine Maggart wrote:In a File Explorer window, go to:

C:Program FilesBlackmagic DesignDaVinci 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.

Hee you are:

https://drive.google.com/file/d/1HncCJH … share_link

https://drive.google.com/file/d/1PHqrON … share_link

Romain Dgv

  • Posts: 10
  • Joined: Sat Oct 15, 2022 12:59 pm
  • Real Name: Romain Degrave

PostFri Nov 04, 2022 5:05 pm

Hey,

I reinstalled the driver using DDU by following the steps you described in the other thread, but unfortunately it still doesnt work.

Thank you in advance for your help, Romain.

User avatar

Dwaine Maggart

Blackmagic Design

  • Posts: 10421
  • Joined: Wed Aug 22, 2012 2:53 pm

PostFri Nov 04, 2022 10:09 pm

@Tomasz: Congratulations, you have the exact same issue as Romain.

What’s common in your 2 systems? The fact that you have a bunch of NVIDIA Insight and CUDA Toolkit and Tools Extension stuff installed.

I’m pretty sure at this point that something in all that NVIDIA stuff is causing the issue.

Since a complete removal and install of the NVIDIA driver didn’t help Romain, I’m going to suggest to you both that you start uninstalling all that extra NVIDIA stuff. Are you both developers and that’s why you have all that stuff installed? If not, why do you have that stuff installed? Do you need it? It not, uninstall it all.

If you have the time and you want to be more scientific about it, you could uninstall one thing at a time and see what specific thing is causing the issue.

I think I’d suggest the Nsight stuff first, then the Tools Extension and then the CUDA Toolkits.

Dwaine Maggart
Blackmagic Design DaVinci Support

Romain Dgv

  • Posts: 10
  • Joined: Sat Oct 15, 2022 12:59 pm
  • Real Name: Romain Degrave

PostSat Nov 05, 2022 12:49 pm

Hey,

I am not a developper, even though I am curious and tried to dev some little things, I dont know why I do have that stuff installed. Thus, I dont need it.

Where can I find theses folders to delete them ?

Thank you for your help ! Romain.

Warmonger

  • Posts: 3
  • Joined: Wed Nov 02, 2022 9:02 am
  • Real Name: Tomasz Zielinski

PostSat Nov 05, 2022 8:06 pm

Here:

CUDA_VISIBLE_DEVICES.png
CUDA_VISIBLE_DEVICES.png (9.79 KiB) Viewed 7454 times

Was 1, while default is 0. This variable allows to set custom GPU used for computation, or in my case — disable it altogether.

However, I didn’t change it over last year, while I got RTX 3050 in February.

Setting this variable back to 0 solved the issue. I use Rapid Environment Editor, if anyone asks.

User avatar

Dwaine Maggart

Blackmagic Design

  • Posts: 10421
  • Joined: Wed Aug 22, 2012 2:53 pm

PostMon Nov 07, 2022 5:50 pm

Check in Windows Settings — Apps & features, and see if any of that is in the installed program list. If it is, select it in the list and it should have an Uninstall button.

Dwaine Maggart
Blackmagic Design DaVinci Support

Romain Dgv

  • Posts: 10
  • Joined: Sat Oct 15, 2022 12:59 pm
  • Real Name: Romain Degrave

PostThu Nov 10, 2022 5:03 pm

Hey,

I deleted the apps that you described but I still cannot launch Resolve.

Also, I tried to find the CUDA_VISIBLE_DEVICES using Rapid Environment Editor, but unfortunately I cannot find it (I linked a screen of it).

Thank you in advance for your help, Romain.

Attachments
uservariables.jpg
uservariables.jpg (313.45 KiB) Viewed 7239 times

User avatar

Dwaine Maggart

Blackmagic Design

  • Posts: 10421
  • Joined: Wed Aug 22, 2012 2:53 pm

PostThu Nov 10, 2022 9:44 pm

@Tomasz: Thanks for the info on Rapid Environment Editor. That looks like a useful tool and I was not aware of it.

@Romain: In the System Variables list of Rapid Environment Editor, do you see these variables:

NVTOOLSEXT_PATH C:Program FilesNVIDIA CorporationNvToolsExt <SYSTEM>
CUDA_PATH C:Program FilesNVIDIA GPU Computing ToolkitCUDAv11.8 <SYSTEM>
CUDA_PATH_V11_8 C:Program FilesNVIDIA GPU Computing ToolkitCUDAv11.8 <SYSTEM>

If so, try removing them and see if that helps. You’ll need to reboot the system after removing them.

Dwaine Maggart
Blackmagic Design DaVinci Support

Romain Dgv

  • Posts: 10
  • Joined: Sat Oct 15, 2022 12:59 pm
  • Real Name: Romain Degrave

PostFri Nov 11, 2022 4:30 pm

Hey,

Unfortunately I did not found any of theses variables in the System Variables list of Rapid Environment Editor.

Thanks you in advance, Romain.

Attachments
systemvariables.jpg
systemvariables.jpg (282.23 KiB) Viewed 7163 times

User avatar

Dwaine Maggart

Blackmagic Design

  • Posts: 10421
  • Joined: Wed Aug 22, 2012 2:53 pm

PostFri Nov 11, 2022 10:08 pm

Please save and send a current NFO file. I want to see if those variables are no longer in that.

Dwaine Maggart
Blackmagic Design DaVinci Support

Romain Dgv

  • Posts: 10
  • Joined: Sat Oct 15, 2022 12:59 pm
  • Real Name: Romain Degrave

PostSat Nov 19, 2022 4:42 pm

Hey,

There is a new NFO file:

https://1drv.ms/u/s!AgAZlbOwv4cXii3RR8K … 2?e=0A81YF

Thank you for your help, Romain.

User avatar

Dwaine Maggart

Blackmagic Design

  • Posts: 10421
  • Joined: Wed Aug 22, 2012 2:53 pm

PostTue Nov 22, 2022 7:32 am

Yep, it’s all gone.

Pretty weird if the issue persists.

One more time, now that that stuff is gone, use DDU to remove the NVIDIA driver, then reinstall it, and when you run the installer, select the Custom Install option then select the Clean Install option.

If it still fails to work, send an updated Resolve log and a current NFO file.

Dwaine Maggart
Blackmagic Design DaVinci Support

Romain Dgv

  • Posts: 10
  • Joined: Sat Oct 15, 2022 12:59 pm
  • Real Name: Romain Degrave

PostMon Dec 19, 2022 5:17 pm

Hey, I did a DDU again but it still dont work. I then send you new Resolve Logs and NFO filles.

https://1drv.ms/u/s!AgAZlbOwv4cXii3RR8K … 2?e=cqPFef

Thanks for your help, Romain.

User avatar

Dwaine Maggart

Blackmagic Design

  • Posts: 10421
  • Joined: Wed Aug 22, 2012 2:53 pm

PostTue Dec 20, 2022 4:23 am

Yeah, I don’t know. Resolve is seeing the GTX 1070 but doesn’t think it has CUDA support, for some reason.

I’m basically out of suggestions, except for a clean Windows install.

Dwaine Maggart
Blackmagic Design DaVinci Support

DanMann

  • Posts: 19
  • Joined: Tue Aug 10, 2021 2:15 pm
  • Real Name: Dan Mann

PostFri May 19, 2023 9:42 am

Oh wow! What advice. Reinstall your whole computer because your software is so unstable. Yes, this is cynicism in my voice, as I am spending dozens of hours trying to troubleshoot this garbage software that completely cripples my ability to work. Why should I have to reinstall Windows if other editing software work fine?

PostFri May 19, 2023 10:19 am

DanMann wrote:Oh wow! What advice. Reinstall your whole computer because your software is so unstable. Yes, this is cynicism in my voice, as I am spending dozens of hours trying to troubleshoot this garbage software that completely cripples my ability to work. Why should I have to reinstall Windows if other editing software work fine?

And yet this is your first post in this thread. A rant, classy

Alex Silva

  • Posts: 374
  • Joined: Thu Jul 10, 2014 8:12 am

PostSun May 21, 2023 10:50 am

Not only that, he did not even specified what hardware he does have and how he is using it with Resolve.


Return to DaVinci Resolve

Who is online

Users browsing this forum: Daniel Batinic, Google [Bot], Harold Tomlinson, indigogo, kenjohanson, mpetech and 90 guests

Открываю проект в DaVinci Resolve 16.2.8, он открывается, но появляется окошко с сообщением об ошибке:

The GPU failed to perform image processing because of an error.
Error Code: 209.

Накануне я обновил DaVinci Resolve. Скорее всего из неё обрали поддержку CUDA (в моём случае минимум Compute Capability of 3.0).
Посмотрел логи:
«C:UsersDenisAppDataRoamingBlackmagic DesignDaVinci ResolveSupportlogsResolveDebug.txt»
Там была такая запись:

[0x0000323c] | GPUManager           | INFO  | 2021-02-04 13:33:04,843 | Flushing GPU memory...
[0x0000323c] | DVIP                 | ERROR | 2021-02-04 13:33:04,845 | C:/jenkins/workspace/dvip/DaVinciIP/DaVinciIP/Unpacker/Unpacker_kernel.cu:226: CUDA error cudaErrorNoKernelImageForDevice (209)
[0x0000323c] | GPUManager           | ERROR | 2021-02-04 13:33:04,851 | Exception caught while running GPU algorithms:
[0x0000323c] | DVIP                 | ERROR | 2021-02-04 13:33:04,851 | 
DVIP Exception: At position C:/jenkins/workspace/dvip/DaVinciIP/DaVinciIP/Unpacker/Unpacker_kernel.cu:226
 - API: CUDA
 - API Error Code: cudaErrorNoKernelImageForDevice (209)

Как всегда для решения подобной проблемы у пользователя аж 3 варианта:
1. Купить видео-карту помощнее
2. Установить старую версию DaVinci (16.2.6)
3. Переключить режим работы программы на OpenCL:
▶ ▶
GPU Processing Mode = OpenCL

Придётся воспользоваться вторым вариантом, т.к. вариант (3) почему-то замедляет производительность программы (судя по некоторым отзывам, хотя по идее не должен), а тратить деньги на новую видюху я не хочу. К тому же сейчас из-за ажиотажа вокруг майнинга криптовалют, видео-карты стоят нереальных денег.
Текущий драйвер NVIDIA GeForce: 461.40.
Попробовал драйверы:
461.09 — проблема не решилась
460.89 — аналогично
460.79 — та же ошибка при открытии проекта
457.61 — увы
457.30 — не сработало
457.09 — ошибка осталась
456.71 — нет
456.55 — тоже нет
456.38 — и этот драйвер не сработал.

Таким образом рекомендация с форума, в которой предлагалось попробовать старый драйвер, мне не помогла.

Зато проблема решилась установкой DaVinci Resolve версии 16.2.6.005

  • Об авторе
  • Недавние публикации

DenTNT

  • Davinci resolve ошибка cuda
  • Davinci resolve ошибка 702
  • Davinci resolve ошибка 209
  • David beckham is a name where is known all over the world исправить ошибку
  • Dauntless произошла ошибка при подключении к игровым серверам