Davinci Resolve 15.1 crash on startup

Title says it. Recently installed 15.1 and program hangs on the splashcreen when it gets to "Looking for Control Surface" until windows offers to close it. I've had previous versions of 15 installed including the Beta and not had this issue.

I've scoured the forums and tried every solution people have had with this issue previously but nothing has worked. If someone at Blackmagic is reading this please help!!!

I have the log file and system info but this forum won't let me paste the links to them and the upload attachments button wont work . Please let me know if there is another way I can upload.

Thanks!!!!

Me too!

Me three!

It's reported in multiple other threads. I reported it here: viewtopic.php?f=21&t=79296

In this thread you will find the link of what to report and upload: viewtopic.php?f=21&t=71894

Have a look at Properties/details of the extracted install file. 15.1.24.0 should have a patch to fix this issue, but that didn't solve my problem.

Black Magic; are you aware that it's not solved yet?

Went back and installed the older version 15.01 instead and it loads up just fine.
I'll have to use that for now since I have projects I'm working on.

There obviously is some bug in the newer 15.1 that hasn't been resolved yet. (no pun intended)

Same problem here. Just crashes on startup (splash screen).

Using Windows 10 x64 Spring Creators / April 2018 Update (1803)
on AMD Phenom II X6 1075T / NVIDIA GeForce GT 710 / 16 GB SAMSUNG DDR3 RAM

Previous versions are working correctly (15.0 Beta, 15.0, 15.0.1).

[Dwaine Maggart]

Logs?

[Rohit Singhal]

Could you all please try the latest build on the website - 15.1.0.025

Same here, it crashes after around 10-15 seconds, using 15.1.0.025 on MacOS Mojave. Going back to 15.0.1 all fine.

[Dwaine Maggart]

Logs?

https://drive.google.com/file/d/1hKG10Q ... sp=sharing

[Dwaine Maggart]

@Rick: what's your issue? Your system is not crashing on startup, which is the focus of this thread.

uhm well yeah it is, i can see why it's a little confusing since im posting about other issues as well.

To paint the picture, my pc at home is crashing at the typical ''looking for control surface'' screen, but the pc at my office is working properly, apart from some 'minor' issues.

i noticed there's a new version of resolve, i will check if that works tonight.


edit: i think i posted the wrong log file, the one from my office. dang thats stupid by bad..

Who else here is running AMD and/or Phenom CPU?

Greetings,

I was using one of the 15 betas (b8, I believe) without issue, but today upgraded to 15.1.1005. In summary, Windows 10 and AMD, and Resolve crashes immediately after the 'loading control surfaces" screen. NFO and zip files attached. It just stops with no windows crash handler, so it's like a silent shutdown.

Let me know if I can help debug/test.

Thanks!
Ken

[Dwaine Maggart]

@Ken: You have the AMD Phenom II CPU that Resolve 15.1 doesn't work with.

Phenom users: Last working version for phenoms is 15.0.1, please use it until...
@Dwaine: As you can see, there are several people waiting for some update on this.
Please, could you provide some feedback? Is anything else we can do to help get all the needed info?
If this is final and we stuck on old Resolve, please provide some message for non-SSE4 CPU users on new builds. Link to last working version would be good also.

[Dwaine Maggart]

It's being looked into.

All Resolve releases back to 10.1.5 are available for download in the Support - DaVinci Resolve area of the web site.

It's being looked into.

All Resolve releases back to 10.1.5 are available for download in the Support - DaVinci Resolve area of the web site.

Thanks!
If you need some additional tests on phenom CPU, just let me know.
I can also provide you with remote desktop access.
Also please don't forget about linux users

[Dwaine Maggart]

We have Linux users?

We have Linux users?

Affected by this issue? Yes
In fact, the suspect on SSE4 requirement to run the last Resolve builds raised from linux version first, as it's easier to debug.
Here you can find my findings

I too am suffering from the won't start crash issue and have posted numerous times about it as well as requested help from technical support.

Here are my logs:

https://drive.google.com/open?id=1ogpug ... OCB7MBi4aP

We have Linux users?

Let me just "vote" for Linux. I'm only using W10 because 14 had limited-codec support on CentOS, and I haven't had time yet to read if that improved with 15.x. But I do run Linux on my same Phenom box, so will be able (anxious, actually) to test it once I hear the Phenom issue is fixed. As for user demand, my 13yo daughter also runs a Phenom box and has been learning Resolve - and asks me when she can upgrade past b8 (to fix some stability issues b8 seems to have)

Btw thanks for clue about trying 15.0.1 - I download that...

PS Dwaine!! I remember meeting you back circa '94 when Unitel was using the DCC in the telecine bay we transferred Trek TNG in!! You prob don't remember me, but maybe my colleague Cliff?

Installed 15.0.1 on my machine (w10 + Phenom, details above) -- and the splash screen takes over 5 minutes to get through all the status panels and display the project list. Once passed that and it starts running, it seems to be normal speed. Wow. Is there a fix?

If this is a known issue then I second the idea to make release notes part of the installer, or even an option/preference to have the splash screen poll a internet server to display know and newly discovered issues (so it could explain this, and we wouldn't have to ask or search)

Installed 15.0.1 on my machine (w10 + Phenom, details above) -- and the splash screen takes over 5 minutes to get through all the status panels and display the project list. Once passed that and it starts running, it seems to be normal speed. Wow. Is there a fix?

If this is a known issue then I second the idea to make release notes part of the installer, or even an option/preference to have the splash screen poll a internet server to display know and newly discovered issues (so it could explain this, and we wouldn't have to ask or search)

15.0.1 works fine for me, and cold start doesn't take so long.
Try reinstalling, watch for disk i/o, cpu load, etc during the boot.
Maybe you have lots of projects? Or some network problems in case projects are stored on NFS or something...

p/s loved the idea about pulling news/issues during splash!

We have Linux users?

Affected by this issue? Yes
In fact, the suspect on SSE4 requirement to run the last Resolve builds raised from linux version first, as it's easier to debug.

Now I know why Resolve didn't start on my Ubuntu setup previously. I thought it was unsupported version of distribution but seems like the problem was in the other place

I have the same issue,
when I change the program compatibility to "Windows 8"
the program starts...
quite a mess at the moment

I have the same issue,
when I change the program compatibility to "Windows 8"
the program starts...
quite a mess at the moment

Do you have Phenom CPU and with this trick new Resolve builds work?

Update:
15.2 fixed Phenom issues on windows.

On Linux you'll still get:
Nov 14 22:15:27 resolver kernel: [ 1075.542832] traps: resolve[6204] trap invalid opcode ip:7f9ad6d8f518 sp:7ffff8f44670 error:0 in fusionscript.so[7f9ad6ba9000+3a5000]

Is 15.2 expected to work on Phenom procs on W10? And also is the situation any better with RH/CentOS?

A quick update to my last post, about slow startup: it was caused by having a webdav (http) server mapped as a drive; and the webdav server was offline. I discovered this by watching activity in procmon. I'm not sure why Resolve would need to poll all attached drives on startup, but it seem like it could contribute to slow or erratic behavior, especially when some drive letters are not used for post work or with drives mapped over Internet paths (SMB/CIFS is notoriously slow with even modest round trip times)

[Dwaine Maggart]

It's expected to work with Phenom II procs on Win10.

On phenom CPUs
It's working on windows 10 (all but Fusion functionality) starting with 15.2
It's not working on Linux
How we can help BMD to fix this?

[Dwaine Maggart]

I suspect fixing this in Linux will be a very low priority. The dev team is aware.

Very low...

I suspect fixing this in Linux will be a very low priority. The dev team is aware.

Very low...

Sure, thanks anyway Dwaine