- Message
Mokiflip
- Posts: 3
- Joined: Thu Jan 07, 2021 9:44 pm
- Real Name: Nicolo Valsasina
Thu Jan 07, 2021 9:58 pm
Hello,
I’ve been using Davinci Resolve 16 for about a year now. Apart from the occasional crash, always worked great.
PC Specs:
— i7-9700k
— 2080ti
— 32gb @3200mhz
— 2x500gb ssd (sata, raid)
— 2TB hard drive
— Windows 10
Today, Davinci has suddenly stopped working. When I open a project and try to play any media, it will only play a few frames per second, and eventually fail completely and give me the error message (GPU has failed to perform because of an error — code 702). Strangely enough, this seems to happen differently on different projects. Most of my projects are with clips recorded in 2560×1440 60fps .mp4 format, with the exception of one project at 1080p30fps. For some reason, that project I can still play without too much staggering. The other ones, best case scenario I get 5-10 seconds of media before it starts failing.
The only things I did today:
— Installed new Nvidia game ready driver from the Geforce Experience. I tried reinstalling it from said Geforce Experience, but that didn’t fix the issue.
— I was messing around with rendering settings, trying Quicktime movie format with the DNxHR HQ settings and was trying to see what the best quality was. This is only in the Delivery tab, and my timeline and project settings havent changed, so I don’t see how that would be the problem.
— I upgraded to Davinci Resolve 17 thinking that might fix it somehow. No luck. Using Davinci 17 atm and still have the exact same issue.
— I also tried a fix I found mentioning going in the Memory and GPU Preferences and change the GPU Processing mode. I tried both with CUDA (the Auto one) and OpenCL but no luck.
I really think it may have to do with the Nvidia driver somehow, because I seem to remember it just happening just after I installed it.
Happy to provide any more information.
Thank you all in advance for the help.
Fri Jan 08, 2021 12:32 am
What GPU driver version are you using? The current recommended minimum Nvidia driver version for Resolve 17.0b6 is 451.82.
Resolve Studio 18.1.2 Build 6
Dell XPS 8700 i7-4790 4 core, 24GB RAM, 2 x Samsung Evo SSDs, GTX1060/6GB (528.02 Studio driver), Win10 Home (22H2), Speed Editor, Faderport 1, Eizo ColorEdge CS230 + BenQ GW2270, Canon C100mk2, Atomos Ninja 2.
SirCat
- Posts: 2
- Joined: Fri Jan 08, 2021 12:54 am
- Real Name: Erik Ivanowski
Fri Jan 08, 2021 12:55 am
Same Problem !
SirCat
- Posts: 2
- Joined: Fri Jan 08, 2021 12:54 am
- Real Name: Erik Ivanowski
Fri Jan 08, 2021 12:58 am
I have found a Solution
Had the same problem, same driver update
you must install the nvidia Studio drivers
worked for me
scapino
- Posts: 11
- Joined: Sat Nov 21, 2020 2:11 am
- Real Name: Kurt Herman
Fri Jan 08, 2021 1:45 am
I have the same problem. DR 17 b6 , todays 1/7/2021 Nvidia drivers Game Ready 461.09.
Same error code crash, 702. I do believe its the drivers, had no problem before today with 17b6.
Re installed both the drivers and 17b6, still the same problem.
Am running an ROG 2080.
I’m going to see if I can find and install the last version prior of NVidias drivers to see if that helps.
Kurt
Win 11 Pro, 64 gigs ram, ROG Nvidia 2080 with 8 gigs. 5 tb hard drive. 500gb SSD System drive. Intel 8 core pros.
scapino
- Posts: 11
- Joined: Sat Nov 21, 2020 2:11 am
- Real Name: Kurt Herman
Fri Jan 08, 2021 4:58 am
Just an update. I installed the NVidia Studio drivers, which are dated 12/15/20, which seem to be a version back, and my crashing with 702 is gone. Works fine now.
Kurt
Win 11 Pro, 64 gigs ram, ROG Nvidia 2080 with 8 gigs. 5 tb hard drive. 500gb SSD System drive. Intel 8 core pros.
Mokiflip
- Posts: 3
- Joined: Thu Jan 07, 2021 9:44 pm
- Real Name: Nicolo Valsasina
Fri Jan 08, 2021 12:45 pm
Thanks for all the replies!
Glad to hear it’s driver related, I suspected as much 
One question from an ignorant person like myself: can I have both Game Ready driver and Studio Drivers installed (and it would use the correct one depending on what I’m doing?), or would I have to keep re-downloading drivers depending on wether im gaming or editing? (I do both about 50-50 so this would be pretty inconvenient).
Thanks again!
Sheizen
- Posts: 3
- Joined: Fri Jan 08, 2021 1:40 pm
- Real Name: Jesús Gutiérrez
Fri Jan 08, 2021 8:09 pm
You can just have one activated (as far as I know). I’m suffering the same issue and gaming with the Studio drivers and for now It has been fine.
Can’t wait for an update tho (I don’t feel confident with this issue. My DR has been doing weird things even with Studio drivers).
djcutnpaste
- Posts: 2
- Joined: Sat Jan 09, 2021 3:59 am
- Real Name: Sean Thakoor
Sat Jan 09, 2021 4:46 am
Same issue here after getting the NVIDIA game ready drivers released on Jan 7 2021. Installed the Studio drivers which are from Dec 2020 and that fixed the issue right up. Shout out to the person that suggested that further up this thread!!!!
prd0000
- Posts: 1
- Joined: Sat Jan 09, 2021 3:28 pm
- Real Name: Rudy Dajoh
Sat Jan 09, 2021 3:32 pm
Hi.. I also had the same problem.
You can fix it by downgrading to 457.51 driver. Did not encounter any problem since.
stryftek
- Posts: 1
- Joined: Sun Jan 10, 2021 3:17 am
- Real Name: Ryan Bullock
Sun Jan 10, 2021 3:19 am
Just wanted to chime in that 461.09 game ready broke me too. Been 100% working without issue until now.
Hopefully something can be resolved. As a content creator who needs to be on the latest drivers to ensure games are running correctly — swapping back and forth to a studio one would be painful.
jajaboss
- Posts: 6
- Joined: Sun Jan 10, 2021 8:55 am
- Real Name: Atsadawut Jungwat
Sun Jan 10, 2021 8:56 am
I too have this problems both Resolve 16 and 17
inktomi
- Posts: 2
- Joined: Sun Oct 25, 2020 5:52 pm
- Real Name: Matt Runo
Sun Jan 10, 2021 5:30 pm
This thread saved me. Thank you! Rolling back to the previous driver version solves this issue.
Arppegio
- Posts: 2
- Joined: Sun Jan 10, 2021 9:07 pm
- Real Name: Glenn Aquino
Sun Jan 10, 2021 9:11 pm
Jus posting that I’m experiencing the same thing within the same time frame. The only thing of note I did when it first started was update my nvidia drivers in Geforce experience. I downloaded the studio drivers and installed them but it’s not helping either. I’m using a 1080 sc.
ferocious_cat
- Posts: 3
- Joined: Fri Jan 08, 2021 4:02 am
- Real Name: Devin Mora
Mon Jan 11, 2021 2:39 am
scapino wrote:Just an update. I installed the NVidia Studio drivers, which are dated 12/15/20, which seem to be a version back, and my crashing with 702 is gone. Works fine now.
Kurt
Thanks Kurt, I confirm that this fix works. I just down loaded and installed the NVidia Studio Drivers and no 702 error. Thank you so much for this because I didn’t want to have to use that Vegas Pro crap.
luwibi
- Posts: 1
- Joined: Mon Jan 11, 2021 3:46 am
- Real Name: Lucky Wibisono
Mon Jan 11, 2021 3:48 am
Hi,
I got the same problem. To whom do you thing we should push this issue forward? NVIDIA or Blackmagic? I’ve reported this problem to Nvidia from Geforce experience software but with no response.
Mardy Dep
- Posts: 34
- Joined: Tue Sep 12, 2017 12:27 am
Mon Jan 11, 2021 6:51 am
Same here and I am glad it wasn’t just me. I just built a new PC so having resolve do this really made me troubleshoot like a mad man, because i thought it was something with my build. Hoping this gets fixed in future game ready drivers — i would rather be on game ready drivers than creative ones since i game as well.
kikohv
- Website
- Posts: 4
- Joined: Sun Jun 30, 2013 9:56 am
- Location: Cape Town, South Africa
Mon Jan 11, 2021 11:44 am
Just had the error 702 pop up and have just updated my NVIDIA gaming driver.. I am downloading the Studio driver now and will see if this resolves the issue.
…yup the issue was resolved with the studio driver
Thanks all.
Kiko
Mardy Dep
- Posts: 34
- Joined: Tue Sep 12, 2017 12:27 am
Mon Jan 11, 2021 4:10 pm
Peter and company — I think this will be very worth escalating to Nvidia. I can see this becoming a big problem for folks as a lot of people are on the latest game drivers and more will be as time goes on. Whatever is in the latest update completely breaks resolve (16 and version 17). There are also ton of folks who don’t even know studio drivers are a thing.
Mokiflip
- Posts: 3
- Joined: Thu Jan 07, 2021 9:44 pm
- Real Name: Nicolo Valsasina
Tue Jan 12, 2021 9:31 am
I can confirm:
— the latest Nvidia game driver crashes Resolve (16&17)
— the Nvidia Studio driver works perfectly fine and can be installed instead. For those concerned in terms of performance difference, from what I’ve been to find on the internet the different between running games with Game Ready and with Studio is insignificant (we’re talking about + — 1 fps or less) so don’t worry about that and go ahead and install the Studio driver. I also haven’t noticed any difference at all even when running high end games that the Game Ready driver is supposedly «optimised» for.
— you can also revert back to the previous version of the Game Ready driver and that has been confirmed to work
That being said, would be nice if it got fixed.
Thank you all for the help!
Fassbrause
- Posts: 42
- Joined: Sun Jan 06, 2019 1:23 pm
- Real Name: Robin Fassbrause
Tue Jan 12, 2021 10:18 am
Just want to mention, that I encounter the exact same problem. This needs to be fixed by Nvidia or BM Design, I hope theyre watching this thread. 
Will try the suggestions above now. Thank you guys!
Fassbrause
- Posts: 42
- Joined: Sun Jan 06, 2019 1:23 pm
- Real Name: Robin Fassbrause
Tue Jan 12, 2021 10:31 am
Installed the studio drivers. Works fine now. Thanks again folks! 
Logan Whiteman
- Posts: 11
- Joined: Sun Sep 06, 2020 5:37 am
- Real Name: Logan K Whiteman
Tue Jan 12, 2021 5:56 pm
I also would like to add, I had the same thing happen. I installed studio drivers and it seems to work fine. Does this mean it is NVIDIA’s problem to fix?
redscapes
- Posts: 1
- Joined: Tue Jan 12, 2021 6:13 pm
- Real Name: Dan Curtis
Tue Jan 12, 2021 6:15 pm
Want to bump this as well. Trying to play a clip will work up to halfway of the clip (no matter on length) before freezing, waiting for a second and working again. Can press buttons and alter the clip but actual playback does not work
Waendi
- Posts: 11
- Joined: Wed Jan 13, 2021 10:20 am
- Real Name: Andreas Wandfluh
Wed Jan 13, 2021 10:27 am
HELP NEEDED
Hi everybody
I have still the same issue despite the fact that I installed today the Studio Driver!! I’m in the middle of a video project and now stucked…
Thanks for any support
Waendi
Waendi
- Posts: 11
- Joined: Wed Jan 13, 2021 10:20 am
- Real Name: Andreas Wandfluh
Wed Jan 13, 2021 3:32 pm
Re my post earlier today with the header «HELP NEEDED»
Hi everybody,
I was able to fix the problem as follows:
— uninstalling Davinci Resolve 16
— uninstalling the Nvidia Studio Driver
— reinstalling th Nvidia Studio Driver
— reinstalling Da Vinci Resolve 16
(I was lucky that I did not delete the zip-file so it was a matter of seconds)
Hope this may help to other people.
Waendi
heathbah21
- Posts: 1
- Joined: Thu Jan 14, 2021 6:48 am
- Real Name: Heath Searles
Thu Jan 14, 2021 6:51 am
Same happened to me! Lorb help me with getting used to Streamlabs and then to have my Resolve keep crashing! Downloaded the latest studio driver for Nvidia, worked like a charm!! Big kudos to this thread for the help!!
UKstu99
- Posts: 1
- Joined: Thu Jan 14, 2021 11:53 am
- Real Name: Stuart Henderson
Thu Jan 14, 2021 11:58 am
Huge thank you for the fix, I have just built a new PC installed DR17 and started getting this error immediately.. installed the studio driver from Nvidia and all great again.
Ryzen 9 5900x
2080 Super
32gb Ram
1 + 2 tb m.2s
YamaMX
- Posts: 3
- Joined: Fri Apr 26, 2019 7:52 pm
- Real Name: George Melita
Tue Jan 19, 2021 9:39 am
Uninstalled DR16 for DR17, went back to the latest 16, then back to the current 17 beta and kept getting the same error until I eventually found this post. As a gamer first and then creator, this is a tough one. Is there any word of a fix? Should we expect it from BM or should we escalate this to Nvidia? This is a huge pain, can’t swap drivers frequently nor have I had issues prior with Game Ready.
coffesanger
- Posts: 1
- Joined: Tue Jan 19, 2021 10:07 am
- Real Name: han kalin
Tue Jan 19, 2021 10:08 am
same here!
Mardy Dep
- Posts: 34
- Joined: Tue Sep 12, 2017 12:27 am
Wed Jan 20, 2021 5:06 am
we need to just keep bumping this post so blackmagic can read and send to nvidia — i am in the same boat with you and i do NOT want to be on the studio drivers and the game ready drivers have never given me issue until now. This is a crippling bug as it completely locks down your computer unless you have the studio drivers.
RikshaDriver
- Website
- Posts: 584
- Joined: Sun Aug 12, 2018 10:08 am
- Location: Melbourne
- Real Name: Asim Siddiqui
Wed Jan 20, 2021 12:10 pm
Just roll back to the previous driver release until NVIDIA comes out with an update.
Unless you have some obscure bug on a game that you play frequently which absolutely requires the latest gaming driver, it’s not the end of the world.
—
Zumerzetbike
- Posts: 3
- Joined: Wed Jan 20, 2021 3:48 pm
- Real Name: michael pearce
Wed Jan 20, 2021 3:59 pm
I’m having the same issues and there is no Studio Driver For my G.P.U According to the Nvidia Site my GPU IS A Ge Force GT1030 So looks like I’m stuck till its sorted with a Update . Tried to Roll back but that option is greyed out .
RikshaDriver
- Website
- Posts: 584
- Joined: Sun Aug 12, 2018 10:08 am
- Location: Melbourne
- Real Name: Asim Siddiqui
Wed Jan 20, 2021 11:17 pm
Download the previous version of NVIDIA drivers
Uninstall the current NVIDIA drivers
Reboot for safe measure
Install the downloaded NVIDIA drivers
There’s no need to do weird stuff like uninstalling Resolve then reinstalling it.
—
scapino
- Posts: 11
- Joined: Sat Nov 21, 2020 2:11 am
- Real Name: Kurt Herman
Thu Jan 21, 2021 4:31 pm
Also to note…
Todays release of the NVidia drivers has a bunch of fixes for GPU processor errors in Premier, and I assume Resolve.
The studio drivers are still working for me, so I will stick with them for the time being.
Kurt
Win 11 Pro, 64 gigs ram, ROG Nvidia 2080 with 8 gigs. 5 tb hard drive. 500gb SSD System drive. Intel 8 core pros.
RGcrocodile
- Posts: 1
- Joined: Sun Jan 24, 2021 7:33 pm
- Real Name: Duncan McDonald
Sun Jan 24, 2021 7:35 pm
its the new nvidia drivers… not anything you can do until they release another or put out a hot fix. maybe the program will put out an update but thats unlikely
YamaMX
- Posts: 3
- Joined: Fri Apr 26, 2019 7:52 pm
- Real Name: George Melita
Mon Jan 25, 2021 7:52 am
Anyone have any luck on Game Ready drivers since? Hoping the next update helps.
GoMati
- Posts: 7
- Joined: Thu Jan 28, 2021 10:20 am
- Real Name: Mati Urban
Thu Jan 28, 2021 12:32 pm
There are new game ready drivers as of today. Going to try them today/tomorrow
Fri Jan 29, 2021 9:17 pm
Just landed on this thread via google because of 702 errors on my setup and good news, the latest version of Nvidia driver (461.40) fixes the issue!
paulhannon
- Posts: 1
- Joined: Thu Feb 25, 2021 10:19 pm
- Real Name: Paul Hannon
Thu Feb 25, 2021 10:22 pm
I have found the studio drivers RUIN my stream when playing F1 2020. It will cause the game to drop to 4fps and just complete cap out. Game drivers completely fix the issue, but then I cant use Resolve. ?
Do I have to keep uninstalling and reinstalling the relevant drivers everyday, now?
Sheizen
- Posts: 3
- Joined: Fri Jan 08, 2021 1:40 pm
- Real Name: Jesús Gutiérrez
Fri Feb 26, 2021 8:16 am
paulhannon wrote:I have found the studio drivers RUIN my stream when playing F1 2020. It will cause the game to drop to 4fps and just complete cap out. Game drivers completely fix the issue, but then I cant use Resolve. ?
Do I have to keep uninstalling and reinstalling the relevant drivers everyday, now?
I’m guessing you are using the latest drivers for both options, right?
Teddy Dem
- Posts: 2
- Joined: Fri Feb 26, 2021 2:37 pm
- Real Name: Chuks Ude
Mon Mar 22, 2021 6:37 pm
I’m currently now having this problem non-stop, making it impossible to get any work done. I have always used the Nvidia studio drivers. This started when I updated to Resolve 17.1. I’ve tried re-installing the Nvidia studio driver to the most current driver and even downgrading Resolve to the version right before 17.1, and I’m still having the issue. Any ideas? Thanks.
LMcCart
- Posts: 12
- Joined: Thu Jun 11, 2020 6:51 pm
- Real Name: Les McCarter
Sun Apr 11, 2021 11:30 pm
I just installed 7.1 and got this 702 error.
My solution was NOT to downgrade, but just do a reinstall of my Studio driver (it was the latest). I made sure to do the custom install and elect to do a fresh install, which included the automatic uninstall and then reinstall.
Rebooted and my 702 error went away.
Mon Sep 26, 2022 5:26 pm
I started to get this today after a fresh install of windows 10 pro. I use the latest studio versions. Im thinking Davinci 18 no longer works with the old gtx 1080Ti. Will get a 3090 or 4090 but who knows if that will help. I thought 18.0.3 should be solid by now.
Resolve Studio 18.0.3 Build 5, Studio driver 517.40
Supermicro 2 Intel Xeon E5-2687W 3.10GHz processors. 64GB ram. GTX 1080Ti GPU Samsung PM893 SSD for system, Intel ssd for cache. Windows 10 pro. Qnap gnap TS-1685 for media. 925MB/s & 1062MB/s
Mon Sep 26, 2022 6:36 pm
Resolve will work fine with your 1080. It works fine with my 1060. Have you checked on nvidia.com for the latest driver? Though not the very latest, I’m running 516.94 Studio. As you have re-installed Windows other settings may have changed.
Might I suggest you post logs and see if Dwaine picks up on them.
- Attachments
-
- Log and NFO Information.JPG (46.64 KiB) Viewed 1458 times
Resolve Studio 18.1.2 Build 6
Dell XPS 8700 i7-4790 4 core, 24GB RAM, 2 x Samsung Evo SSDs, GTX1060/6GB (528.02 Studio driver), Win10 Home (22H2), Speed Editor, Faderport 1, Eizo ColorEdge CS230 + BenQ GW2270, Canon C100mk2, Atomos Ninja 2.
Mon Sep 26, 2022 6:53 pm
Good points there Charles, I should get the log for Dwaine. Also I need to look into putting the system info as a foot note as you have. I have tried the three latest studio drivers I belive. And right now is the latest installed. Next time I get it working solid again I refuse to upgrade this workstation =).
It was a while since I collected a log. Should you start to run the «capturelogs» it prior to the crash/error message, or run it right after? By the name it sound like before.
Resolve Studio 18.0.3 Build 5, Studio driver 517.40
Supermicro 2 Intel Xeon E5-2687W 3.10GHz processors. 64GB ram. GTX 1080Ti GPU Samsung PM893 SSD for system, Intel ssd for cache. Windows 10 pro. Qnap gnap TS-1685 for media. 925MB/s & 1062MB/s
Mon Sep 26, 2022 8:06 pm
Yes, I would just do a Capture log and an NFO file, unless Resolve is crashing when you should do the Capture log afterwards.
Resolve Studio 18.1.2 Build 6
Dell XPS 8700 i7-4790 4 core, 24GB RAM, 2 x Samsung Evo SSDs, GTX1060/6GB (528.02 Studio driver), Win10 Home (22H2), Speed Editor, Faderport 1, Eizo ColorEdge CS230 + BenQ GW2270, Canon C100mk2, Atomos Ninja 2.
Dwaine Maggart
Blackmagic Design
- Posts: 9904
- Joined: Wed Aug 22, 2012 2:53 pm
Mon Sep 26, 2022 9:35 pm
A log and an NFO and yes, GTX 1080Ti is fine. Anything that has CUDA Compute 3.5 support or higher is fine.
https://en.wikipedia.org/wiki/CUDA
Dwaine Maggart
Blackmagic Design DaVinci Support
Alignment Films
- Posts: 1
- Joined: Fri Dec 30, 2022 7:36 am
- Real Name: Russ Cootey
Fri Dec 30, 2022 7:44 am
Hello,
I am having the same issue with DR 18. I have tried every configuration in preferences. It’s set to CUDA. I’ve rolled back my gpu driver, I’ve installed new driver. It is the studio driver.
MSI motheroard — DD5
intel i9 cpu
Nvidia Geforce RTX 3060 ti
I am stumped and frustrated. I hope someone can help.
Thank you
Dwaine Maggart
Blackmagic Design
- Posts: 9904
- Joined: Wed Aug 22, 2012 2:53 pm
Fri Dec 30, 2022 5:07 pm
If Resolve launches and you can start a project, in the Resolve Help menu, select the «Create Diagnostics Log on Desktop» menu to generate a Resolve log file. Put that file, along with a Windows System Information .NFO file on a file sharing site and provide a link to the files here.
If Resolve won’t launch far enough to open a project then follow this:
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
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 от Blackmagic Design — популярный бесплатный видеоредактор, доступный на нескольких платформах. Однако некоторые пользователи сообщают, что DaVinci Resolve продолжает падать при редактировании видео.
В отличие от Adobe Premier Pro, популярный видеоредактор DaVinci Resolve лучше работает с системой с выделенным графическим процессором. Отсутствие которых может привести к случайным сбоям.
В этой статье мы рассмотрим несколько шагов по устранению неполадок, которые помогут вам навсегда решить проблемы сбоев DaVinci Resolve.
Как исправить сбой DaVinci Resolve при запуске?
1. Изменить приоритет процесса
- Убедитесь, что DaVinci Resolve запущен.
- Щелкните правой кнопкой мыши на панели задач и выберите «Диспетчер задач».
- Откройте детали
- Прокрутите вниз и щелкните правой кнопкой мыши Разрешить. исполняемый файл
- Перейдите в «Установить приоритет» и выберите «Высокий».
Вот и все. Попробуйте поработать над любым из ваших проектов и проверьте, решена ли проблема. Обратите внимание, что при каждом перезапуске DaVinci Resolve вам, возможно, придется устанавливать высокий приоритет.
2. Установите драйвер Nvidia Studio
- Запустите опыт Nvidia GeForce.
- Нажмите на значок меню (три точки в правом верхнем углу).
- Выберите Студийный драйвер.
- GeForce Experience загрузит и установит драйвер Nvidia Studio.
Если у вас уже установлены драйверы Studio, попробуйте выполнить чистую установку.
- Загрузите и установите программу удаления драйвера дисплея.
- Запустите инструмент и выберите графическую карту,
- Нажмите «Очистить» и перезапустите.
- После удаления загрузите последнюю версию драйвера NVIDA Studio.
- Запустите установщик и установите необходимые пакеты через выборочную установку.
- Перезагрузите компьютер и перезапустите DaVinci Resolve.
Драйвер Nvidia Studio также может вызывать сбои DaVinci Resolve. Попробуйте выполнить чистую установку драйверов, чтобы устранить проблемы.
Если вам нужно правильно установить этот драйвер Nvidia, не вызывая серьезных проблем, лучше попробуйте специальный инструмент обновления драйверов и эффективно установите или обновите любые драйверы на вашем ПК.
3. Какая версия DaVinci Resolve лучше всего подходит для предотвращения сбоев?
Начнем с наиболее распространенной причины сбоев DaVinci Resolve. DaVinci Resolve 15 был пронизан несколькими сбоями и ошибками, которые приводили к частым сбоям.
Эти сбои также происходили в системе, в которой было достаточно оборудования для запуска видеоредактора. Тем не менее, установка последней версии DaVinci Resolve 16, похоже, устранила многие проблемы с программным обеспечением.
Обновить DaVinci Resolve
- Запустите приложение Разрешение.
- Щелкните DaVinci Resolve.
- Выберите Проверить наличие обновлений.
- Загрузите и установите все ожидающие обновления.
После установки перезапустите приложение и проверьте, решена ли проблема сбоя. Если нет, возможно, вам придется удалить, а затем переустановить последнюю версию, чтобы устранить проблему. Вот как это сделать.
- Нажмите клавишу Windows + R.
- Введите appwiz. cpl и нажмите OK.
- В Панели управления выберите DaVinci Resolve.
- Нажмите «Удалить», а затем подтвердите действие.
- После удаления загрузите последнюю версию DaVinci Resolve отсюда.
- Запустите установщик и проверьте наличие улучшений.
4. Включите мультимониторинг IGPU
- Выключите компьютер.
- Нажмите кнопку питания, чтобы перезагрузить компьютер. При перезапуске начните нажимать клавишу настройки (F2) на клавиатуре, чтобы войти в BIOS.
Примечание. Клавиша настройки обычно отображается на начальном экране. Обратитесь к руководству пользователя для вашего ноутбука или материнской платы (в случае настольного компьютера), чтобы найти ключ настройки. - В меню BIOS откройте вкладку Advanced.
- Найдите IGPU Multi-Monitoring и убедитесь, что он включен.
- Сохраните изменения и выйдите.
5. Проверьте совместимость графического процессора
Отключить встроенный графический процессор
- Нажмите клавишу Windows + R.
- Введите devmgmt.msc и нажмите OK.
- В диспетчере устройств разверните раздел «Адаптер дисплея».
- Щелкните правой кнопкой мыши встроенный графический процессор Intel.
- Выберите Отключить устройство.
- Откройте DaVinci Resolve и проверьте, не возникают ли сбои по-прежнему.
Обновление графического процессора
Как обсуждалось ранее, DaVinci Resolve — это приложение, интенсивно использующее GPU. Для стабильной работы рекомендуется установить достойную дискретную видеокарту. Если у вас есть только интегрированный графический процессор Intel, самое время подумать о переходе на выделенный графический процессор.
Решение DaVinci продолжает давать сбой. Обычно это происходит из-за несовместимости драйвера графического процессора или ошибки в самом программном обеспечении. Выполните шаги один за другим, чтобы диагностировать и устранить проблемы, вызывающие сбои.
Открываю проект в 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
- Об авторе
- Недавние публикации
