Davinci resolve ошибка 702

  • Message

Mokiflip

  • Posts: 3
  • Joined: Thu Jan 07, 2021 9:44 pm
  • Real Name: Nicolo Valsasina

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

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

SirCat

  • Posts: 2
  • Joined: Fri Jan 08, 2021 12:54 am
  • Real Name: Erik Ivanowski

PostFri Jan 08, 2021 12:55 am

Same Problem !

SirCat

  • Posts: 2
  • Joined: Fri Jan 08, 2021 12:54 am
  • Real Name: Erik Ivanowski

PostFri 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

PostFri 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

PostFri 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

PostFri 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

PostFri 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

PostSat 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

PostSat 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

PostSun 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

PostSun 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

PostSun 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

PostSun 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

PostMon 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

PostMon 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

PostMon 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

PostMon 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

PostMon 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

PostTue 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

PostTue 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

PostTue Jan 12, 2021 10:31 am

Installed the studio drivers. Works fine now. Thanks again folks! :D :D :D

Logan Whiteman

  • Posts: 11
  • Joined: Sun Sep 06, 2020 5:37 am
  • Real Name: Logan K Whiteman

PostTue 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

PostTue 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

PostWed 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

PostWed 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

PostThu 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!! :D :D :D

UKstu99

  • Posts: 1
  • Joined: Thu Jan 14, 2021 11:53 am
  • Real Name: Stuart Henderson

PostThu 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

PostTue 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

PostTue Jan 19, 2021 10:08 am

same here!

Mardy Dep

  • Posts: 34
  • Joined: Tue Sep 12, 2017 12:27 am

PostWed 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: 603
  • Joined: Sun Aug 12, 2018 10:08 am
  • Location: Melbourne
  • Real Name: Asim Siddiqui

PostWed 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

PostWed 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: 603
  • Joined: Sun Aug 12, 2018 10:08 am
  • Location: Melbourne
  • Real Name: Asim Siddiqui

PostWed 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

PostThu 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

PostSun 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

PostMon 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

PostThu Jan 28, 2021 12:32 pm

There are new game ready drivers as of today. Going to try them today/tomorrow :)

PostFri 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

PostThu 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

PostFri 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

PostMon 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

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

PostMon 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

PostMon 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
Log and NFO Information.JPG (46.64 KiB) Viewed 2746 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.

PostMon 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

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

User avatar

Dwaine Maggart

Blackmagic Design

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

PostMon 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

PostFri 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

User avatar

Dwaine Maggart

Blackmagic Design

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

PostFri 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

  • Message

Mokiflip

  • Posts: 3
  • Joined: Thu Jan 07, 2021 9:44 pm
  • Real Name: Nicolo Valsasina

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

PostFri 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.3 Build 8
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

PostFri Jan 08, 2021 12:55 am

Same Problem !

SirCat

  • Posts: 2
  • Joined: Fri Jan 08, 2021 12:54 am
  • Real Name: Erik Ivanowski

PostFri 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

PostFri 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

PostFri 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

PostFri 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

PostFri 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

PostSat 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

PostSat 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

PostSun 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

PostSun 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

PostSun 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

PostSun 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

PostMon 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

PostMon 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

PostMon 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

PostMon 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

PostMon 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

PostTue 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

PostTue 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

PostTue Jan 12, 2021 10:31 am

Installed the studio drivers. Works fine now. Thanks again folks! :D :D :D

Logan Whiteman

  • Posts: 11
  • Joined: Sun Sep 06, 2020 5:37 am
  • Real Name: Logan K Whiteman

PostTue 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

PostTue 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

PostWed 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

PostWed 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

PostThu 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!! :D :D :D

UKstu99

  • Posts: 1
  • Joined: Thu Jan 14, 2021 11:53 am
  • Real Name: Stuart Henderson

PostThu 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

PostTue 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

PostTue Jan 19, 2021 10:08 am

same here!

Mardy Dep

  • Posts: 34
  • Joined: Tue Sep 12, 2017 12:27 am

PostWed 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

PostWed 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

PostWed 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

PostWed 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

PostThu 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

PostSun 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

PostMon 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

PostThu Jan 28, 2021 12:32 pm

There are new game ready drivers as of today. Going to try them today/tomorrow :)

PostFri 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

PostThu 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

PostFri 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

PostMon 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

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

PostMon 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

PostMon 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
Log and NFO Information.JPG (46.64 KiB) Viewed 1599 times

Resolve Studio 18.1.3 Build 8
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.

PostMon 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

PostMon 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.3 Build 8
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.

User avatar

Dwaine Maggart

Blackmagic Design

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

PostMon 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

PostFri 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

User avatar

Dwaine Maggart

Blackmagic Design

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

PostFri 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

Содержание

  1. opencl не видит видеокарту nvidia
  2. Davinci resolve не видит видеокарту
  3. DaVinci could not find any CUDA capable GPUs
  4. Most Common DaVinci Resolve GPU Issues (& How to Fix Them)
  5. Is DaVinci Resolve GPU Intensive?
  6. Most Commonly Used GPUs in DaVinci Resolve
  7. Why does DaVinci Resolve Throw GPU Errors?
  8. Most Common GPU Errors in DaVinci Resolve
  9. GPU Configuration Warning, Unsupported GPU Processing Mode & GPU Failed to Perform Image Processing Error
  10. How to Check your Nvidia GPU Card is Supported by DaVinci Resolve?
  11. My GPU card is Eligible But Still Resolve Says It Is Un-Supported
  12. DaVinci Resolve GPU Memory Full
  13. Установить драйверы для встроенного графического процессора Intel в Ubuntu 18.04 для DaVinci Resolve 17?
  14. 3 ответа

opencl не видит видеокарту nvidia

Столкнулся с проблемой при установке daVinci resolve — программа не видит opencl. Точнее, сами библиотеки она видит, но при попытке запуска opencl ругается на «отсутствующую» видеокарту. OpenCl, headers и icd установлены с репозитория, видеокарта nvidia geforce 1050 ti, драйвера nvidia 440xx, cuda тоже с репозитория, в nvidia-smi отображается, ffmpeg-cuda работает без нареканий. Но, тем не менее, opencl упорно вещает, что «number of platforms = 0» и ошибка -1001. Помогите, может, кто сталкивался с подобной проблемой или хотя бы знает, где и что смотреть, а то в интернете максимум что предлагают — переустановить cuda и opencl (что делалось уже неоднократно). Прилагаю выхлоп nvcc –version для сомневающихся:

nvcc: NVIDIA (R) Cuda compiler driver Copyright (c) 2005-2019 NVIDIA Corporation Built on Wed_Oct_23_19:24:38_PDT_2019 Cuda compilation tools, release 10.2, V10.2.89

какой дистрибутив-то? наверное не установлен какой-то пакет вроде nvidia-opencl

сама куда для работы приложений не нужна, рантаймы включены в драйвер

Дистрибутив manjaro linux 19.0.2

extra/opencl-nvidia-440xx 440.82-1 (3.3 MiB 27.8 MiB) (Installed) extra/opencl-headers 2:2.2.20170516-2 (70.5 KiB 777.0 KiB) (Installed) extra/ocl-icd 2.2.12-3 (47.7 KiB 277.0 KiB) (Installed) multilib/lib32-opencl-nvidia-440xx 440.82-1 (24.1 MiB 73.2 MiB) (Installed)

Источник

  • Posts: 3
  • Joined: Tue Jul 03, 2018 7:12 pm
  • Real Name: Luisa Dale Silva

DaVinci could not find any CUDA capable GPUs

Tue Jul 03, 2018 9:19 pm

I’ve searched the topics and found some informations I need to solve my issue. But as I am really new to DaVinci and my computing skills are quite basic level, I thought I’d write here with the exact things that are happening to me.

I’ve recently bought a Macbook Pro 15″ and these are its specifications:

Hardware overview
Model Name: MacBook Pro
Model Identifier: MacBookPro14,3
Processor Name: Intel Core i7
Processor Speed: 2,9 GHz
Number of Processors: 1
Total Number of Cores: 4
L2 Cache (per Core): 256 KB
L3 Cache: 8 MB
Memory: 16 GB
Boot ROM Version: MBP143.0175.B00
SMC Version (system): 2.45f0

Intel HD Graphics 630:

Chipset Model: Intel HD Graphics 630
Type: GPU
Bus: Built-In
VRAM (Dynamic, Max): 1536 MB
Vendor: Intel
Device ID: 0x591b
Revision ID: 0x0004
Automatic Graphics Switching: Supported
gMux Version: 4.0.29 [3.2.8]
Metal: Supported, feature set macOS GPUFamily1 v3

Chipset Model: Radeon Pro 560
Type: GPU
Bus: PCIe
PCIe Lane Width: x8
VRAM (Dynamic, Max): 4096 MB
Vendor: AMD (0x1002)
Device ID: 0x67ef
Revision ID: 0x00c0
ROM Revision: 113-C980AJ-927
VBIOS Version: 113-C9801AU-A02
EFI Driver Version: 01.00.927
Automatic Graphics Switching: Supported
gMux Version: 4.0.29 [3.2.8]
Metal: Supported, feature set macOS GPUFamily1 v3
Displays:
Color LCD:
Display Type: Built-In Retina LCD
Resolution: 2880 x 1800 Retina
Framebuffer Depth: 30-Bit Color (ARGB2101010)
Main Display: Yes
Mirror: Off
Online: Yes
Rotation: Supported
Automatically Adjust Brightness: No

I’ve downloaded first DaVinci Resolve 15 Beta and the following message appeared to me after I launched the program:

«DaVinci Resolve could not find any CUDA capable GPUs. Would you like to review and update your DaVinci Resolve Hardware configuration?
Please ensure that appropriate GPU and CUDA drivers are installed and your DaVinci Resolve Hardware is configures appropriately.»

I then press Update Configuration and change GPU to OpenCL as recommended and then I save configs. I reopen the program and everything happens again, over and over. I have tried with DaVinci 14 and the same problem persists. I’ve read forums, I’ve downloaded the latest CUDA driver 396.64 (deleted it afterwards, as my computer did not detect any GPUs), and so on. Really have no idea where to go now. I’m upset because I bought this computer mainly to start grading my projects.

If there’s any information I missed to help you help me, please tell me. And thank you very much!

Источник

Most Common DaVinci Resolve GPU Issues (& How to Fix Them)

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.

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:

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.

Most Common GPU Errors in DaVinci Resolve

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

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.

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.

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:

Источник

Установить драйверы для встроенного графического процессора Intel в Ubuntu 18.04 для DaVinci Resolve 17?

Мой графический процессор — это

Я установил DaVinci Разрешите 17 на моем компьютере с Ubuntu 18.04, но при запуске решения показывает ошибку неподдерживаемого режима графического процессора.

Затем в конфигурации не отображается графический процессор для выбора.

Я видел эту команду для Nvidia sudo apt install nvidia- драйвер nvidia-opencl-icd libcudal libnvidia-encodel , но он не работает для этого iGPU. Есть ли способ исправить это?

3 ответа

Я вполне уверен (но не могу найти документацию), что Davinci Resolve требует графического процессора Nvidia с проприетарными драйверами. К сожалению, если у вас его нет, вы не сможете его запустить.

Дважды проверьте, какое оборудование у вас на самом деле.

Графика Intel интегрирована. Если у вас нет выделенного графического процессора, это означает, что ваш процессор также является вашим iGPU.

Если вы в настоящее время работаете в среде рабочего стола, то ваши графические драйверы уже установлены и работают.

Если вы этого не сделали. Если у вас есть работающий iGPU или графический процессор, вы не сможете использовать среду рабочего стола.

Более того, если у вас нет графического процессора NVIDIA, вам не нужны драйверы видеокарт NVIDIA. Фактически, если вы принудительно установили несовместимое оборудование, вы вполне можете сломать свою систему.

Я ничего не знаю о вашем приложении, но это наводит на мысль, что вы могли установить неправильные настройки в этом приложении. Если у вас нет выделенного графического процессора и вы должны выбирать между процессором CPU и GPU, вы, вероятно, должны выбрать CPU.

После быстрого поиска в моей любимой поисковой системе с использованием терминов «Минимальные системные требования DaVinci Resolve 17», кажется, предполагается, что для запуска программного обеспечения требуется выделенный графический процессор.

Источник

Hi, 

         There is a couple of easy fixes for this problem. First off, the reason why it is happening is there’s too many nodes and or there is too many heavy VFX on there. Such as noise reduction or film grain etc.

First thing you want to do is update your video card to the newest drives. Then in Resolve, go up to preferences , memory and GPU. It depends on your video card but under GPU processing mode, for Nvidia cards, choose CUDA. If you’re using an AMD card, choose Open CL. You can also choose to have most of your system memory for Resolve and take the system memory for Fusion. This option is just above the said before options. 

Save and then restart. Should fix all your problems. If not, Your computer might not be able to handle your current timeline. 

Have a great day and I hope this helps

Drew

https://www.greengoatproductions.com/home/


Edited March 6, 2021 by Green Goat Productions

Forgot a few things


Go to davinciresolve


r/davinciresolve

r/davinciresolve has decided to stand with the 7,000+ subs who have decided to go dark in protest of Reddit’s API changes. For more information, please visit r/Save3rdPartyApps or r/ModCoord.
You can find us with r/videography over at https://prodpost.com/forum/ or get support from Blackmagic Design directly at https://www.blackmagicdesign.com/support




Members





Online



After maybe 2-5 frames of 2560×1440 60fps playback I get the error code pop up. I installed the newest studio drivers and that didn’t work for me either. I hope someone can help me fix this issue.

Archived post. New comments cannot be posted and votes cannot be cast.

More posts you may like

  • Message

Mokiflip

  • Posts: 3
  • Joined: Thu Jan 07, 2021 9:44 pm
  • Real Name: Nicolo Valsasina

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

PostFri 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

PostFri Jan 08, 2021 12:55 am

Same Problem !

SirCat

  • Posts: 2
  • Joined: Fri Jan 08, 2021 12:54 am
  • Real Name: Erik Ivanowski

PostFri 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

PostFri 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

PostFri 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

PostFri 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

PostFri 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

PostSat 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

PostSat 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

PostSun 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

PostSun 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

PostSun 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

PostSun 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

PostMon 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

PostMon 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

PostMon 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

PostMon 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

PostMon 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

PostTue 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

PostTue 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

PostTue Jan 12, 2021 10:31 am

Installed the studio drivers. Works fine now. Thanks again folks! :D :D :D

Logan Whiteman

  • Posts: 11
  • Joined: Sun Sep 06, 2020 5:37 am
  • Real Name: Logan K Whiteman

PostTue 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

PostTue 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

PostWed 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

PostWed 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

PostThu 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!! :D :D :D

UKstu99

  • Posts: 1
  • Joined: Thu Jan 14, 2021 11:53 am
  • Real Name: Stuart Henderson

PostThu 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

PostTue 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

PostTue Jan 19, 2021 10:08 am

same here!

Mardy Dep

  • Posts: 34
  • Joined: Tue Sep 12, 2017 12:27 am

PostWed 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

PostWed 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

PostWed 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

PostWed 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

PostThu 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

PostSun 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

PostMon 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

PostThu Jan 28, 2021 12:32 pm

There are new game ready drivers as of today. Going to try them today/tomorrow :)

PostFri 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

PostThu 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

PostFri 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

PostMon 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

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

PostMon 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

PostMon 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
Log and NFO Information.JPG (46.64 KiB) Viewed 1481 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.

PostMon 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

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

User avatar

Dwaine Maggart

Blackmagic Design

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

PostMon 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

PostFri 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

User avatar

Dwaine Maggart

Blackmagic Design

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

PostFri 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

  • Форум
  • Другое

Автор

Сообщение

Вставить имя в ответ
Перейти в профиль

ElvisSuperStar

Репутация: 1348

На сайте c 11.06.2009
Сообщений: 65
Екатеринбург / Хуст Трансильвания

06.05.2020 17:50

Error Cuda 702 РЕШЕНО!

Совет для тех кто рендерит на нодах и во время рендеринга на каком то кадре все стопорит и выдает ошибку Cuda error 702

1) Это не связано с Octane, такое встречается и на Vray Rt , RedShift

2) Первая причина виндовс 10 перегружает драйвер . так-как малая задержка ожидания? надо увеличить до 100 TdrDelay TDR (Timeout Detection and Recovery) 

https://docs.nvidia.com/gameworks/content/developertools/desktop/timeout_detection_recovery.htm
 

3) Обновить или откатить видеодрайвер

4) Для 4-6-8 видеокарт нужно много виртуальной памяти , надо файл подкачки увеличить, это поможет!

5) Эта болезнь 702 встречается только на видеокартах на удалённое (сборки типа майнинг фермы )

6) От количества оперативной памяти хоть миллион ничего не поменяется пока не сделать выше описанные пункты

7)Добавил в папку советы нашей группы�https://vk.com/album-17913093_227716161
 

Error Cuda 702 solution!

1) The error is not related to Octane. This is a common mistake Vray. RadShift

2) Update or roll back the video driver

3) Enlarge virtual memory for video cards using the node-based principle of connection

4) TdrDelay set 100 TDR (Timeout Detection and Recovery)�https://docs.nvidia.com/gameworks/conte
  … covery.htm

Lorikkcat

Lorikkcat

654823

1640

583

10.03.2014

RU

СКАЧАТЬ ВИДЕО

Описание видео:

Davinci Resolve зависает, ошибка 702, загрузка GPU на 100% Davinci Resolve error code 702 load GPU 100%
Собираю компьютер MPG Z390 PRO CARBON i7 9700K RTX 2070 Super 🤍🤍youtube.com/watch?v=q-Wupr1iCc0

Тэги из видео

davinci resolve 16 davinci resolve error code 702 davinci resolve 16 gpu error davinci resolve davinci resolve error davinci resolve ошибка 702 davinci resolve зависает davinci resolve error code 702 fix

Комментарии пользователей:

Icon Ex Номер ошибки: Ошибка 702
Название ошибки: Norton Partition Magic Error 702
Описание ошибки: Ошибка 702: Возникла ошибка в приложении PartitionMagic. Приложение будет закрыто. Приносим извинения за неудобства.
Разработчик: PowerQuest Corporation
Программное обеспечение: PartitionMagic
Относится к: Windows XP, Vista, 7, 8, 10, 11

Обзор «Norton Partition Magic Error 702»

«Norton Partition Magic Error 702» также считается ошибкой во время выполнения (ошибкой). Разработчики программного обеспечения, такие как PowerQuest Corporation, обычно принимают PartitionMagic через несколько уровней отладки, чтобы сорвать эти ошибки перед выпуском для общественности. К сожалению, иногда ошибки, такие как ошибка 702, могут быть пропущены во время этого процесса.

Ошибка 702 также отображается как «Norton Partition Magic Error 702». Это распространенная ошибка, которая может возникнуть после установки программного обеспечения. Если происходит «Norton Partition Magic Error 702», разработчикам будет сообщено об этой проблеме, хотя отчеты об ошибках встроены в приложение. PowerQuest Corporation может устранить обнаруженные проблемы, а затем загрузить измененный файл исходного кода, позволяя пользователям обновлять свою версию. Чтобы исправить такие ошибки 702 ошибки, устанавливаемое обновление программного обеспечения будет выпущено от поставщика программного обеспечения.

Сбой во время выполнения PartitionMagic, как правило, когда вы столкнетесь с «Norton Partition Magic Error 702» в качестве ошибки во время выполнения. Следующие три наиболее значимые причины ошибок выполнения ошибки 702 включают в себя:

Ошибка 702 Crash — это типичная ошибка 702 во время выполнения, которая полностью аварийно завершает работу компьютера. Обычно это происходит, когда PartitionMagic не может распознать, что ему дается неправильный ввод, или не знает, что он должен производить.

Утечка памяти «Norton Partition Magic Error 702» — при утечке памяти PartitionMagic это может привести к медленной работе устройства из-за нехватки системных ресурсов. Возможные причины включают сбой PowerQuest Corporation для девыделения памяти в программе или когда плохой код выполняет «бесконечный цикл».

Error 702 Logic Error — Ошибка программной логики возникает, когда, несмотря на точный ввод от пользователя, производится неверный вывод. Это видно, когда исходный код PowerQuest Corporation содержит недостаток в обработке данных.

PowerQuest Corporation проблемы файла Norton Partition Magic Error 702 в большинстве случаев связаны с повреждением, отсутствием или заражением файлов PartitionMagic. Основной способ решить эти проблемы вручную — заменить файл PowerQuest Corporation новой копией. Кроме того, некоторые ошибки Norton Partition Magic Error 702 могут возникать по причине наличия неправильных ссылок на реестр. По этой причине для очистки недействительных записей рекомендуется выполнить сканирование реестра.

Ошибки Norton Partition Magic Error 702

Типичные ошибки Norton Partition Magic Error 702, возникающие в PartitionMagic для Windows:

  • «Ошибка программы Norton Partition Magic Error 702. «
  • «Недопустимый файл Norton Partition Magic Error 702. «
  • «Извините, Norton Partition Magic Error 702 столкнулся с проблемой. «
  • «К сожалению, мы не можем найти Norton Partition Magic Error 702. «
  • «Отсутствует файл Norton Partition Magic Error 702.»
  • «Ошибка запуска программы: Norton Partition Magic Error 702.»
  • «Файл Norton Partition Magic Error 702 не запущен.»
  • «Norton Partition Magic Error 702 выйти. «
  • «Неверный путь к приложению: Norton Partition Magic Error 702.»

Эти сообщения об ошибках PowerQuest Corporation могут появляться во время установки программы, в то время как программа, связанная с Norton Partition Magic Error 702 (например, PartitionMagic) работает, во время запуска или завершения работы Windows, или даже во время установки операционной системы Windows. Запись ошибок Norton Partition Magic Error 702 внутри PartitionMagic имеет решающее значение для обнаружения неисправностей электронной Windows и ретрансляции обратно в PowerQuest Corporation для параметров ремонта.

Истоки проблем Norton Partition Magic Error 702

Проблемы PartitionMagic и Norton Partition Magic Error 702 возникают из отсутствующих или поврежденных файлов, недействительных записей реестра Windows и вредоносных инфекций.

В частности, проблемы с Norton Partition Magic Error 702, вызванные:

  • Поврежденная или недопустимая запись реестра Norton Partition Magic Error 702.
  • Файл Norton Partition Magic Error 702 поврежден от вирусной инфекции.
  • Norton Partition Magic Error 702 ошибочно удален или злонамеренно программным обеспечением, не связанным с приложением PartitionMagic.
  • Другая программа находится в конфликте с PartitionMagic и его общими файлами ссылок.
  • Неполный или поврежденный PartitionMagic (Norton Partition Magic Error 702) из загрузки или установки.

Продукт Solvusoft

Загрузка
WinThruster 2022 — Проверьте свой компьютер на наличие ошибок.

Совместима с Windows 2000, XP, Vista, 7, 8, 10 и 11

Установить необязательные продукты — WinThruster (Solvusoft) | Лицензия | Политика защиты личных сведений | Условия | Удаление

  • Dauntless win64 shipping exe ошибка
  • Dattemkot def котел будерус ошибка
  • Datsun mi do ошибка u0100
  • Date format picture ends before converting entire input string ошибка
  • Darksiders 3 ошибка unreal engine 4 crash reporter как исправить