Looking for control surfaces crash

When I start Davinci Resolve 15 b1 beta the loading screen appears and stops at "Looking for control surfaces" a few seconds later it crashes. I looked at every forum reference to this I could find, updated all of my drivers, still same result. I was using Davinci Resolve 14b3 beta without any problems.

Here is my system specs:
AMD A10-7870 4C
Geforce 1060 3gb
32gb system mem
Windows 10 pro

[Peter Chamberlain]

Can you try beta 2

Can you try beta 2

Just downloaded it and it does the same thing, going to uninstall and try again.

This is my SYSTEM PARAMETERS xml

<?xml version="1.0" encoding="UTF-8"?>
<SystemParameters>
<SystemParameter module="MT_SYSTEM" index="0" parameter="RECORD_DEPTH" value="0"/>
<SystemParameter module="MT_SYSTEM" index="0" parameter="RECORD_HANDLES" value="0"/>
<SystemParameter module="MT_SYSTEM" index="0" parameter="MONITOR_STYLE" value="1"/>
<SystemParameter module="MT_TCS" index="0" parameter="CLOCK_SYNC_SOURCE" value="0"/>
<SystemParameter module="MT_TCS" index="0" parameter="PULL_RATIO" value="0"/>
<SystemParameter module="MT_TCS" index="0" parameter="JUMP_FRAMES" value="1"/>
<SystemParameter module="MT_TCS" index="0" parameter="SX20_WCLK_OUT" value="0"/>
<SystemParameter module="MT_TCS" index="0" parameter="JOG_DIM_LINK" value="0"/>
<SystemParameter module="MT_SYSTEM" index="0" parameter="SOLO_FOLLOWS_SELECT" value="0"/>
<SystemParameter module="MT_SYSTEM" index="0" parameter="ALT_MONITOR_STYLE" value="0"/>
<SystemParameter module="MT_TCS" index="0" parameter="LOOP_JOG_WIDTH" value="80"/>
<SystemParameter module="MT_TCS" index="0" parameter="LOOP_JOG_ALIGNMENT" value="0"/>
<SystemParameter module="MT_TCS" index="0" parameter="ZOOM_JOG_SCALE" value="1"/>
<SystemParameter module="MT_SYSTEM" index="0" parameter="RANGE_AUTO_CLEAR" value="0"/>
<SystemParameter module="MT_TCS" index="0" parameter="LOOP_USE_PREPOST_ROLL" value="0"/>
<SystemParameter module="MT_TCS" index="0" parameter="SX_WCLK_IN_TERM" value="1"/>
<SystemParameter module="MT_SYSTEM" index="0" parameter="MIDI_CONTROLLER_PROTOCOL" value="0"/>
<SystemParameter module="MT_SYSTEM" index="0" parameter="MIDI_CONTROLLER_INPUT" value="0"/>
<SystemParameter module="MT_SYSTEM" index="0" parameter="MIDI_CONTROLLER_OUTPUT" value="0"/>
<SystemParameter module="MT_SYSTEM" index="0" parameter="MIDI_CONTROLLER_ENABLED" value="0"/>
</SystemParameters>

been having the same issue tried reinstalling several times.
using acer predator g9-593
intel i7-6700
16 gb ram
nvidia 1070 gtx with 8 gb ram
running on windows 10 pro ver.1803
nvidia driver ver 397.31

Hello everyone,

I too, have had this problem with beta 2. I did some digging and found a similar issue was afflicting users with version 14 last August.

Here's the thread: viewtopic.php?f=31&t=63507

Assuming my audio driver or audio interface was causing the issue, I uninstalled all 3rd party audio drivers from my machine. I have managed to open Resolve successfully several times in succession afterward. Resolve starts fine with my audio interface plugged into my machine as well.

I have been having the exact same problems as others have reported. The free version of Resolve 15b2 crashes at the startup screen. This did not happen with the free release version 14.3.

However, I managed to get it working and the way I got it working leads me to believe the issue is related to OpenGL. First my system specs:

OS: Windows 10 Home 1709 64-bit
CPU: Intel 2600K
Memory: 32GB
Display GPU: Nvidia GTX 970
GPU 2: Nvidia Titan X Pascal
GPU 3: Nvidia Titan Xp
Nvidia drivers: 388.59

My global Nvidia settings have the GTX 970 set as the OpenGL GPU and the two Titan X cards are set to run CUDA. Like I said, this setup runs all my 3D apps and Resolve 14.3 just fine. However, when starting Resolve 15b2 it crashes.

What I found was that if you right click on the Resolve 15 desktop icon you'll see a menu that includes "Run OpenGL on". If I select one of the Titan X cards instead of the GTX 970 then Resolve 15 starts normally.

The same problem, but I fixed it. Problem hides in Windows firewall (or Antivirus firewall). All files from Blackmagic need full permissions. Sorry for my English. Good luck.

Does it crash because you are frantically clicking on the title? Haha.... Because I get the 'searching for control surface' too..... But it eventually boots after ten minutes.

So it does boot... But it's not ideal in my case.

Also tried the latest beta version as well and it still boots. But after a painful ten minutes. Not bad if you need to go into in the morning, but very painful if it crashes when trying to back up projects.

viewtopic.php?f=32&t=72366

I also tried disabling my firewall and still the long boot too. Gonna try again in the morning, just to be sure.

The log files are in C:\ProgramData\Blackmagic Design\DaVinci Resolve\Support\logs

For me, it sits on 'socket failed to connect to server, error: 10061' for ten minutes.

what worked for me was going to my NVIDIA settings, go to manage 3D settings, program settings, choosing black magic design, select: use high performance NVIDIA processor and change CUDA GPU to NVIDIA GTX processor. I also updated the drivers for my built in intel graphics processor and the INTEL GPU(using the geforce experience tool) before doing this. These steps worked for me.

Im resolve on an old NVIDIA 660m GPU on a 3rd gen i7 laptop

I solved the problem by pulling out my USB camera

In C:\ProgramData\Blackmagic Design\DaVinci Resolve\Support there is a file named setupfirewall.bat

Running this batch file (as administrator) resolved this crash for me.

I have the same problem on a Mac.

Adding to this thread - our machines were crashing at that stage because the PostgreSQL server ran out of connections ("FATAL: sorry, too many clients already") and needed to be rebooted.

Looks like the causes of this behavior are as diverse as a Windows95 "out of memory" error.

I wish Resolve wouldn't just pop up a message to send an error report to BMD... and actually share the error report with the user. That'd be more useful.

I had this too...

It was my USB dongle to my USB headset that was the issue.

So now I have to remove my usb dongle every time I start Resolve... Super annoying...