15.1.2 will not start, stuck loading fairlight

Running Windows 10 Pro 1803, build 17134.345, DaVinci Resolve Studio 15.1.2. Was working fine some time last week, but I now can't get past Loading Fairlight on the splash page. The issue persists after removing everything from ProgramData/AppData and reinstalling + licensing. Firewall is already off.

[Dwaine Maggart]

Since you've reinstalled everything, we've lost the prior log history to see what might have happened when it stopped working.

Right now, it seems to be stopping after it sees this OFX plugin:

com.timeinpixels.tomsfalsecolor3gpu

So try removing that, and see if that helps.

Removed, still no joy. Updated logs attached. I have the debug archive from before I nuked the installation, but they're too large to attach.

[Dwaine Maggart]

That's what file sharing sites are for.

Try installing the current NVIDIA 416.81 driver, and see what that does.

I'm also confused by why it's showing a DeckLink 4K Extreme 12G card, but no Desktop Video driver version. If there is no Desktop Video driver, it can't see that card. It's basically impossible to have one and not the other. Do you have that card installed, and if so, what Desktop Video driver is currently installed? If you open the Blackmagic Desktop Video Setup app, does it see the card? And if so, what version does it show, under the Help - About Desktop Video Setup menu?

Your point is well taken: https://we.tl/t-gkOASV42Gg

Clean install of the current NVIDIA drivers did not fix it. I have Desktop Video Software 10.11.4 installed, and the Setup app works fine, showing my card, and letting me write new preferences.

[Dwaine Maggart]

In File Explorer, go to:

C:\ProgramData\Blackmagic Design\DaVinci Resolve, and rename the Preferences folder to Preferences.bk

Then copy the Preferences folder out of that last log you linked to, and paste it into C:\ProgramData\Blackmagic Design\DaVinci Resolve

What happens then when you launch Resolve?

It freezes the same way when launching, when using the old preferences.

Some combination of updating my panel firmware and updating to 15.2 has fixed this.