Resolve not fully closing after Crash

Hi,

we are experiencing some problems with Resolve crashing and looking for some ideas, hints, possible solutions or things to try.

We're on a Supermicro computer running Windows 11 with a Decklink 8K Pro. There's occasions when Resolve freezes and you have to shut it down with the Task Manager. The reasons for that are diverse, but that's not the big thing. This can happen every once in a while.

However, what is problematic is that once closed, we can still see Resolve in the Task Manager, occupying a few gigs of RAM, unable to close this instance. We can open a new instance of Resolve, however, since the old one is still there, it blocks the Video I/O and we can't get signal on the monitor.

What we tried so far (unsuccessful):
- close the second instance with Task Manager (as Admin of course)
- close it with Process Explorer
- sign out of the computer and sign in

The only thing that worked so far, was restarting the PC. However this just takes too much time, if it happens every few hours. There has to be an easier solution.

I'm looking forward to what you are coming up with. Maybe someone has had similar issues before? Again, the main problem is, that we are unable to close this old instance of Resolve. Even with Admin rights, it's still telling us "Access Denied"

As I see it there's two questions here:
1) Why does Davinci crash?
Fix that and every problem is solved.

2) Who started Davinci?
It sounds like the user starting Davinci has more permissions than the user attempting to close.
I like System Informer https://systeminformer.sourceforge.io/downloads.php as it shows who did what.
To really deep dive, you can use https://learn.microsoft.com/en-us/sysin ... ds/procmon to see exactly what error messages windows gives (can be vastly more detailed than what a normal GUI shows).

but that's not the big thing.

I'm kinda thinking it is. Resolve shouldn't be crashing like that. Solving that issue would be where I focus my efforts.

There is millions of reasons why Resolve can crash. And fixing one reason now would not help in the future.
Don't get me wrong, we're obviously looking into that as well.
I've been using Resolve for years, and I have never had the situation where it is blocking me from closing it. This is the new part and the thing that is causing the most trouble. Which is why I am looking for experience here on the forum.

From the symptoms, it sounds like Resolve is creating a separate process to handle some task (like talking to an I/O device). When Resolve crashes, the process is not getting the message that the game is over and everyone has gone home, so it hangs around patiently.

You mentioned the process resists being killed. I wonder if you could send it a Terminate or Hangup signal to make it leave.
/disclaimer: Not a Windows system guy

[Dwaine Maggart]

When Resolve crashes on Windows, it can leave a Resolve.exe process running. Launching Resolve again, without stopping the existing Resolve.exe process will lead to additional issues.

And to note, even on a clean exit of Resolve, on Windows, the Resolve.exe process can remain running for several seconds. And if you launch Resolve while an existing Resolve.exe process is running, that will create issues.

This shouldn't happen and hopefully we'll fix it someday, but until that day, I would STRONGLY advise that if Resolve crashes, or you want to exit and immediately relaunch Resolve, that you first open Windows Task Manager and select the Details area (NOT the Processes area), and verify there is not a Resolve.exe process running. If there is, right click it and select End task.

When Resolve crashes on Windows, it can leave a Resolve.exe process running. Launching Resolve again, without stopping the existing Resolve.exe process will lead to additional issues.

And to note, even on a clean exit of Resolve, on Windows, the Resolve.exe process can remain running for several seconds. And if you launch Resolve while an existing Resolve.exe process is running, that will create issues.

This shouldn't happen and hopefully we'll fix it someday, but until that day, I would STRONGLY advise that if Resolve crashes, or you want to exit and immediately relaunch Resolve, that you first open Windows Task Manager and select the Details area (NOT the Processes area), and verify there is not a Resolve.exe process running. If there is, right click it and select End task.

Thanks Dwaine for stepping in.

See that's the problem. Resolve does not allow me to close it via the Task Manager. Not in the process area, not in the details area. Even as Admin. We get a popup saying "Access Denied". This is the part where it is sketchy.

We're giving the computer some time before we restart Resolve, but it just doesn't disappear from the task manager, no matter how long we wait.

So far we helped ourselves with changing the Decklink card to a 4K instead of the 8K. We're not experiencing any crashes so far. But it doesn't satisfy, not knowing why Resolve blocks us from closing it. Any idea?

[Dwaine Maggart]

Is it possible you are not an Admin level user on the system? I've never had an issue of closing the Resolve.exe app in Task Manager - Details. But I always run as an Admin level user.

Is it possible you are not an Admin level user on the system? I've never had an issue of closing the Resolve.exe app in Task Manager - Details. But I always run as an Admin level user.

Tried both. Running task manager as admin.
Logging in as admin in the first place.
Nothing worked.

[Dwaine Maggart]

I've never seen a scenario where the Resolve.exe process could not be killed.

I've certainly had crashes where the Resolve.exe app does not go away. And it's never been a problem to kill the process in Task Manager - Details.

I've verified that non-Admin level users can also "End task" the Resolve.exe process from the Task Manager Details area.

Perhaps if you provide a Resolve diagnostics log (you can generate that from the Resolve Help menu) and a Windows System Information .NFO file, that might provide a clue.