Resolve won't open after being closed.

System: Ryzen Threadripper 2920X 12 core CPU
64 gb RAM Windows 10 Home 64-bit
GPU-- Geforce RTX 2060, 6gb

A weird, minor but annoying thing. I open Davinci Resolve, use it, then exit by clicking on 'Quit Davinci Resolve' in the dropdown menu.

When I decide to start Davinci again a bit later to resume work on a project, I click on the Davinci Resolve icon either on the desktop OR in the Program menu (makes no apparent difference). The mouse pointer shows the little activity icon for a few seconds, and then nothing happens and Davinci does not open, nor will it with consecutive attempts.

HOWEVER, if I hit Ctrl-Alt-Del and go into the task manager, I will find the Resolve icon sitting in there, pretty as you please, active but using 0% of the CPU. If I hit 'end task' on Resolve, then close the task manager and go once again to click on the DVR icon in the program menu or desktop shortcut, THEN Davinci Resolve will start and run properly.

This has been pretty consistent for me, particularly since I updated to 16.1.1.005

FYI.

I saw that in my system as well, the previous instance of resolve never closed.

It started to do that with v16.1.

I saw that in my system as well, the previous instance of resolve never closed.

It started to do that with v16.1.

I get that behaviour as well. I find that, on my Windows system, I have to pull up the Task Manager and kill the still-running DaVinci Resolve there. Then it starts normally.

I have seen that a few people have this problem, but have never had it myself. When trying to answer questions on the forum I often open Resolve multiple times. It must like something about my system.

Had this problem. Updated to the latest drivers from Nvidia studio solved it for me.

Windows 10, resolve 16.1 studio, intel i7-7800x, ram 128gb, 1080GTX.

Had this problem. Updated to the latest drivers from Nvidia studio solved it for me.

Windows 10, resolve 16.1 studio, intel i7-7800x, ram 128gb, 1080GTX.

which drivers version exactly?

If you're using Blackmagic RAW footage, recommend you continue to use the NVIDIA driver identified in your signature. See viewtopic.php?f=21&t=102152

I experienced the reluctant restart of DR several times during the few hours I tried out 16.1. Haven't had it happen with 16.1.1

Ditto with the issue and task manager work around. Not using raw or doing anything else fancy. Issue is not consistent.

If you update from DR 15.x to 16.x, your database will be restructured and you will not be able to reverse your decision unless you've made a backup of your database first and restore it.

Why are you still using 15.2 instead of 15.3.1? I've heard that sometimes a major Windows update will cause some settings to change, so maybe installing 15.3.1 will fix things. Then later on depending on where your projects are you can think about upgrading to 16.x, right now it would be 16.1.1.

Ditto with the issue and task manager work around. Not using raw or doing anything else fancy. Issue is not consistent.

Same here, but sometimes even killing Resolve by task manager is not possible.

I have exactly this problem too.

As has been mentioned, DR doesn't always shut itself down properly and leaves open processes.

I note the comment that there's no CPU activity, but there is a tiny bit (<0.01%) which only shows up on SysInternals process explorer . It also holds on to a lot of system RAM (12 Gbytes when I just encountered it).

If I shut DR down after doing only a small amount of work, it doesn't seem to leave a process running - so I'm trying to isolate what it is that causes it to happen.

Ditto with the issue and task manager work around. Not using raw or doing anything else fancy. Issue is not consistent.

Same here, but sometimes even killing Resolve by task manager is not possible.

Hi Ingolf,
same here, I experienced several crashes out of different situations. Sometimes Resolves hangs in Backgroundprocesses (Hintergrundprozesse), after killing each of them, you should be able to restart Resolve.

PS:
I am back on Version 16.1.b03 which is build 033 because on any higher version I had crashes over crashes during rendering H264 and huge problems (stuttering) on playback and preview H264 footage

Even weirder … straight after a reboot just now, I ran Resolve (studio 16.1.1) and the cursor showed that there was activity. Then nothing.

I looked at Task Manager, and there was the usual DaVinci Resolve entry running at 0%.

I didn't bother killing it, and went on to do a few other things. About 4 minutes later, Resolve burst into life and started its boot up (which always takes about 45 seconds).

Not sure if that info is a help or a hindrance, but I felt it worth reporting.

Same issue here..... I'd like to know which NVIDIA drivers were the culprit?

Recent NVIDIA drivers have been identified as causing problems with BRAW, if they're a source of other problems that's not clear. viewtopic.php?f=21&t=102152

I have the same issue, tried reinstalling, going to do a fresh windows install, try again, then will post reports

I didn't have this issue for a few days, but today it is back. Resolve didn't shutdown properly.
In the attached screenshot you can see which tasks are still alive minutes after shutting down Resolve.

DVR_16.1.1_doesnt_shutdown.JPG (333.52 KiB) Viewed 28227 times

Hi Ingolf,
those where the same ones which I have seen too. I asume you are working with h264 footage as I do.
All versions above 16.1b03 have issues with h264 and h265 footage which concerns playback and rendering.
That's the reason I went back to 16.1b03 and this kind of problem doesn't appear again.

Still waiting on the next version which hopefully will fix this and other issues.

Hi Andy,

you are right. Source is h265, destination (delivery) is h264.

Best regards to OF

I experienced the reluctant restart of DR several times during the few hours I tried out 16.1. Haven't had it happen with 16.1.1

I experienced the reluctant restart of DR several times during the few hours I tried out 16.1. Haven't had it happen with 16.1.1

Which kind of footage do you use?

Today I've had this happen a couple of times with 16.1.1. Still playing with it, once I found a Project Manager task way down on the list and was able to kill it. But that might have happened on a restart, as I said I'm still playing with it.

As soon as I installed the release version 15.0.0.86 I could not launch Resolve anymore. It would show up in the Task Manager but nothing else.

Tried uninstalling and reinstalling multiple versions. (V14 and all v15 betas worked for me)

I experienced the reluctant restart of DR several times during the few hours I tried out 16.1. Haven't had it happen with 16.1.1

Which kind of footage do you use?

i have it happen frequently, but not every time, and have not been able to see a pattern

my source footage is mainly ArriRAW, RED and ArriProrez, some DJI, but that's been transcoded to ProRez before it got to me

so i'm not seeing any h264 sources

but i am rendering screeners to h264, so i'll look for a commonality between the issue with haveing to kill it in taskmangler, and rendering h264

I experienced the reluctant restart of DR several times during the few hours I tried out 16.1. Haven't had it happen with 16.1.1

Which kind of footage do you use?

i have it happen frequently, but not every time, and have not been able to see a pattern

my source footage is mainly ArriRAW, RED and ArriProrez, some DJI, but that's been transcoded to ProRez before it got to me

so i'm not seeing any h264 sources

but i am rendering screeners to h264, so i'll look for a commonality between the issue with haveing to kill it in taskmangler, and rendering h264

I almost never use H264 and I still get it (on winzoz)

I almost never use H264 and I still get it (on winzoz)

The hanging processes are also DPDecoder.exe?

I almost never use H264 and I still get it (on winzoz)

The hanging processes are also DPDecoder.exe?

I need to check that, not sure.

BUG: Many times I have to stop the process(Resolve) manually in the Win10 task manager!

Win10 Pro 64bit version:1809, build: 17763.805 (on inner SSD)
Dell Inspiron 15-7577
32 GB Ram
4 GB VRam GeForce 1050 Ti (430.86 driver)
Intel HD630: 26.20.100.7323
Resolve Cache, Files on a 512GB SSD connected with USB-C
Resolve Version: 16.1.1.005

BUG: Many times I have to stop the process(Resolve) manually in the Win10 task manager!

Win10 Pro 64bit version:1809, build: 17763.805 (on inner SSD)
Dell Inspiron 15-7577
32 GB Ram
4 GB VRam GeForce 1050 Ti (430.86 driver)
Intel HD630: 26.20.100.7323
Resolve Cache, Files on a 512GB SSD connected with USB-C
Resolve Version: 16.1.1.005

I am having the same issues. First I changed back to studio drivers 431.86 and that seemed to work. But some time later it came back. I turned of "dynamic project switching" and everything is working normal again. Can you check if this works for you?

Windows 10, resolve 16.1 studio, intel i7-7800x, ram 128gb, 1080GTX.

I didn't experience any effect of dynamic switching related to rs remaining in memory incorrectly after exit. If I remember well, I couldn't use version 431 Nvidia driver, the program even didn't start.

Thanks: Bela

Right now, I have a project that won't let me render out a video. Resolve just crashes. It just dies outright with no error logging option that sometimes pops up. I ran the Arorus Engine monitor that shows GPU clock, Memory clock, and GPU voltage. When Resolve is running, the GPU clock goes up. After it crashes, the GPU clock keeps running. When I kill the Resolve process with Task Manager, the GPU clock drops to what I assume is it's idle level.

Right now, my confidence in using Resolve is very low. I had to complete my last project without color correction using Hitfilm Express. I have tried the earlier nVidia driver (as recommended in this discussion) to no avail.

I'm hoping some future upgrade fixes this. It's disappointing that something that I've done many times before is failing so much, now.

Hi all,

I've been using DR 16 for about a month now and this morning I edited a bunch of images in my timeline and I started getting "media offline" problems. This gradually worsened until the program was unable to save. Finally I forced the program closed, restarted the computer, and I haven't been able to launch DR since. I see it pop up in the task manager for a second before it shows "suspended". I tried generating a log but it won't even allow me to do that. I tried reinstalling several times but it still won't open. I notice during the install the CMD.exe shows an error with Windows Defender but otherwise says the install worked.

Any thoughts?

Kevin

I have this issue on my Windows installations, too using NVIDIA cards.
Closing DPDecoder.exe and Resolve does the trick.

No such issue on my Linux installations though.

Incredible annoying, all the time you have to kill the Resolve in Tasks list, amateur

people are discouraged from work by not simply restarting the program
all the time, all the time!!!

Same issue here.

16.1.2 doesn't exit properly remain in tasks list!!! Unacceptable!!!

Win10 Pro 64bit version:1809, build: 17763.914 (on inner SSD)
Dell Inspiron 15-7577
32 GB Ram
4 GB VRam GeForce 1050 Ti (430.86 driver)
Intel HD630: 26.20.100.7323
Resolve Cache, Files on a 512GB SSD connected with USB-C
Resolve Version: 16.1.2.026

How did this not get fixed for 16.1.2? Absolute nonsense.

It's consistently happening to me and I'm on the latest version of Resolve.

At least in one occasion, it looked to me as if the main gui closed correctly, but the gui scope window was hanging a bit longer than what it should.

Then killing the process fixed....

Not sure 100%... I could not find a reliable replication method user.

As I posted before, I have never had this problem. I always render to h264 as well. This is what I see in Task Manager with Resolve running and stopped. For Resolve to not shut down sounds like a related background process not releasing it.

I experienced the problem exactly now again that is still exist

Win10 Pro 64bit version:1809, build: 17763.973 (on inner SSD)
Dell Inspiron 15-7577
32 GB Ram
4 GB VRam GeForce 1050 Ti (430.86 driver)
Intel HD630: 26.20.100.7323
Resolve Cache, Files on a 512GB SSD connected with USB-C
Resolve Version: 16.1.2.026

A good workaround could be this: a bat fiile run as administrator:
Aim: force kill Resolve process if wasn't closed completely
Content:
-----------------------------------------------------------
taskkill /f /im Resolve.exe
pause
-----------------------------------------------------------


https://docs.microsoft.com/en-us/window ... s/taskkill

/f Specifies that processes be forcefully terminated. This parameter is ignored for remote processes; all remote processes are forcefully terminated.

/im <ImageName> Specifies

yup the same issue for a long time now. Updating the Nvidia drivers has notably helped general stability, but Davinci studio just doesn't quit. For me it is probably around 75% of the time. Would be nice to get Blackmagic to look into it.

Confirm this problem. And it been before (15, 14, 12.5 versions)

HP Z820, 2xXeon E5-2687w, 64 Gb RAM, AMD FirePRO W8000

I alwayse have all updates for system and drivers

+1

I have the same problem.

I too have this issue.
I’m currently on 16.2 Studio. Been experiencing this intermittently since v14.
Many of the times Resolve is hanging onto Ram.

+1 and I have an AMD 580...no nVidia card here....