I just installed the free Resolve 14 (had 12.5 before, worked great) and am experiencing major problems.The program will start just fine until I get to the window where I have to select whether I want to create a new project or if I want to open a old one. It does not matter what I choose to do, as soon as I click "create" (new project) or "open" on an old project Resolve 14 just closes. No crash report or anything, it acts like a regular closure (it also just disappears in the task manager).

I'm on a Windows 10 HP machine, i7-2600, 16GB of RAM and an old GTX 550 Ti.

Is it my graphics card? The start up system check of Resolve told me it'd be fine for simple editing, which is my goal.

I already de- and re-installed the program twice, restarted the computer and updated the graphics driver.

I have the same issue. First I updated the previous version of the Davinci Resolve (12.5) to DR 14 on Win 7 Pro and I could not start the project. It's the same as Alex Schubert wrote. Then I installed Win 10 Pro (fresh install) and nothing has changed.

I am having the same problemI am on Mac Pro 5,1 Sierra. Studio version 12.5 works and 14 beta also worked but as I had 'missing LUT' I reverted back to 12.5. Resolve 14 closes as soon as I try to make new project or open previous project.My graphics card is GTX570

Thank you for that link, although it doesn't exactly help in this matter as we are not able to access the help menu (as Miriana pointed out).I exported the CaptureLog manually as described in viewtopic.php?f=21&t=41211The resulting zip and a NFO of my system can be found on my google drive: okay, the forum tells me I can't post URLs... Maybe I can send you a PM, Dwaine Maggart?

R14.0.0078 splash screen shows up, project manager starts, but it crashes as soon as I try to open an old project or try to start a new project. Most of the time the resolve.exe process is still visible in the task manager.

I've tried different Nvidia drivers and a new database (file), did a fresh installation of R14, I removed the VST-plugin directories, changed the standard sound device etc.

If my graphics card isn't supported... How come I was able to access the program and use all it's features, create content, render it, and have a finished video yesterday, but for some reason it won't work today?

As Peter already mentioned to you in another thread, the Quadro M1000 GPU you have will not work with Resolve 14. It would work with Resolve 12.5. See my comments above about CUDA Compute 3.0 or above being required with Resolve 14 and NVIDIA cards.

@Dwaine: Apparently my GTX580 is only 2.0 however I think the right behaviour from the software would be not to use an incompatible card and fall back to software mode instead. Is there a way to force this in the config file?

Hi all. I have some similar situation with a brand new Asus Rog notebook. Theres a big problem in DR 14 with dual monitor and resolutions. To start a proyect I change the resolution from 1920 to 1650 or 1280, start the proyect and then change again to 1920. Works, but its temporal. Cant be this way every time. need a quick patch.See yaDario

I have the same or a similar problem. Resolve 14 closes when opening a project or starting a new project.It worked fine with Davinci 12.5.It worked some days with 14.Maybe there was a windows 10 update.Maybe Davinci got confused in the past when I tried to install it again using a different user during the Davinci 14 beta. But later it worked with Davinci 14.The "fix" which was described in the last post didn't help: Setting CUDA oder OpenCL didn't help.

I have a GEFORCE 750 Ti and newest driver.The details should be available in the dropbox link. (which I can no post currently because somehow it's not allowed for me to post URLs)

Can anybody help, please? Maybe it's easy to see for an expert if he looks in the log file.

Hi. A bit of help needed here. I'm trying to locate this config.dat but cannot find it. I made all hidden and system files visible. I installed the SW to another older and very slow computer, that has never had Resolve installed on it. Installation ok, Resolve works with some warning during installation about video card a bit too slow, but works anyway. Also here I do not find any config.dat file... (just wanted to test if my installation on PC-1 had been corrupted or something). On PC-1 Resolve does not work, just "dies" after trying to open or create a new project. Windows 10 on both PC:s. Resolve 12.x worked fine, but after trying v.14 I cannot get either to work anymore... Video card too slow, I know (CUDA 2.1) but the fix from Bela and confirmation from Richard kind of gave me some hope... I only find a file called config6 (with no extension) in the Resolve folder. That is probably not the one we are talking about, right...? Is this config.dat a file that should be generated during installation and is unique to each PC, or is it a general file I can copy-paste from another PC that has it, or what can be done here?

As it seems resolve 12.5 is no longer offered on the web site, and being keen to have some means of editing, I managed to restore 12.5 and it seems to be operating OK. But I wonder if the logs available now will be of any use to you in investigating this problem?

Please forgive my unfamiliarity with this topic! I'm having the same problem, but I don't think my graphics card is at fault: I'm running Windows 10, i7 7700, 16gb RAM, and a GTX 1050. Am I right in thinking that this ought to meet the CUDA requirements?

@Dwaine: The Project Manager window opens without issue, but once I select a project or create a new one, the window closes and nothing happens. Resolve still appears to be open and I can see it running in the task manager, but there's no actual window.

This started while I was running Beta 3, and I updated in the hope of fixing it, but the problem has remained.

Note that if you DO use OpenCL on NVIDIA cards that don't have CUDA Compute 3.0 capability, (which we don't recommend) it will probably sort of work. But if you try to use a LUT, your image will probably go away. Other GPU intensive things like Temporal NR and OFX effects will likely also not work well.