Suddenly getting endless crashing Win 11

Hi all, newbie poster please be gentle with me!

I've been using Studio for several months very happily. It's been rock solid stable. However after a gap of a few weeks, now it is crashing every 10-15 mins, seemingly at random. Nothing obvious sets it off.

Now I know the basics here - what has changed on my system? Answer - nothing as far as I can tell. No hardware changes, no software changes save a few audio plugin updates. However, Windows has had its last feature update. I've just updated Studio from 19.1.3 to 19.1.4, and after a search here I've uninstalled Davinci Resolve Control Panels, all to no avail.

I've created a zip log, but as a new user I can't seem to link it here. System basics: Win 11 Pro; GeForce 1050i, RME Babyface.

Thanks for any and all help!

[Peter Chamberlain]

Start by reinstalling the GPU driver

Thanks very much Peter, just updated the GeForce driver from 560.94 to 572.83. So far so good but only done a cursory test, I'll report back once I've used it in anger for a while.

It just crashed, but as I switched to the Render tab. It's never crashed for me doing that at any time before, all the recent crashes have been on the main edit page, so it could be unrelated I guess.

You can post links by adding spaces between the parts so the forum software does not recognize it as a link.

You can post links by adding spaces between the parts so the forum software does not recognize it as a link.

Thank you! I'll try this: A space before the first // and another after .com.

https: //www.dropbox.com /scl/fi/7vbxjew0unt713pu9qgux/DaVinci-Resolve-logs-20250322-075022.zip?rlkey=zsdklnagn0zuw1ctv82o90hf8&st=ehjtq0kq&dl=0

For future forum searchers...

I have a working theory. I put the cache on an external NVMe with some rushes several weeks ago as it was maxing out disk space on my main internal media drive. Initially no problems, but I have a feeling it's related. It's not been an obvious correlation, but this morning the whole drive glitched, it took Da Vinci with it and then Windows couldn't read any data until a full PC reboot. But since then I've been working with it all day and it's been good as gold.

It just makes me suspicious. Have ordered a new 4TB internal drive, will report back when it has all transferred over. (hey aren't NVMes cheap these days?)

[Dwaine Maggart]

The Windows crash .dmp file points the finger at this, whatever this is:

Oxford SuprEsser.vst3

The Windows crash .dmp file points the finger at this, whatever this is:

Oxford SuprEsser.vst3

Ah, that's a very fine Sony audio plug-in.

The Windows crash .dmp file points the finger at this, whatever this is:

Oxford SuprEsser.vst3

Ah, that's a very fine Sony audio plug-in.

Maybe it was Sony before, now its Sonnox
https://sonnox.com/products/oxford-supresser

The Windows crash .dmp file points the finger at this, whatever this is:

Oxford SuprEsser.vst3

Wow, that's extraordinary thank you. It is indeed a (very fine) Sonnox de-esser. I'll switch the plugin out for an alternate de-esser if I still get crashes. Thank you!

Oh, sadly it's not that. Crashing like crazy again with the Sonnox de-esser plugin removed from the mixer.

Oh, sadly it's not that.

Try uninstalling it from the system.

[Dwaine Maggart]

Send an updated Resolve log file.

I have just had Resolve repeatedly crash on me whenever it was started. I traced the problem down to the beta OFX plug-in from Topaz. As soon as that was removed Resolve worked fine.

Send an updated Resolve log file.

Thanks - new log here (and I can now post a clean URL!):

https://www.dropbox.com/scl/fi/vnxxf1e1 ... ef4fx&dl=0

It's a nightmare so very grateful for all help. Resolve just crashed in the background in the time it took for me to move the crashlog file from the desktop and move it to dropbox. I've now disabled Oxford Supressor in preferences, and have bought a new internal NVMe drive. I've moved the render cache to this new NVMe, and all footage has migrated too. Having had a good morning, it's now crashing more than ever.

Same here:

19.1.3 Studio was solid, I changed NOTHING and suddenly very slow and crashes.

I had the same part of the timeline cached in 1min, now the same part without any changes takes 6min.

Then later at night, it is OK again, although I changed NOTHING.

Send an updated Resolve log file.

Thanks - new log here (and I can now post a clean URL!):

https://www.dropbox.com/scl/fi/vnxxf1e1 ... ef4fx&dl=0

It's a nightmare so very grateful for all help. Resolve just crashed in the background in the time it took for me to move the crashlog file from the desktop and move it to dropbox. I've now disabled Oxford Supressor in preferences, and have bought a new internal NVMe drive. I've moved the render cache to this new NVMe, and all footage has migrated too. Having had a good morning, it's now crashing more than ever.

In the log files I have seen that you have some MotionVFX templates installed - it is possible that those are causing the crash issues - I remember users on this forum reporting that. They had success by contacting MotionVFX support and getting updated templates.

Then there are FXHOME.HitFilm OFXs - that company cheased to exist several years ago - so plugins could also be problematic with newer Resolve versions.

And you have 2 GPUs:
discrete "NVIDIA GeForce GTX 1050 Ti" with only 4GB - NVIDIA GPU Driver: 572.83
integrated "AMD Radeon Graphics" from your CPU - AMD GPU Crimson Driver: 24.10.27.02

So there are some points to have a closer look.

[Dwaine Maggart]

The Windows .dmp file shows that this is causing a crash:

Oxford Dynamics Native.vst3

Maybe try avoiding anything from Oxford ?

The Windows .dmp file shows that this is causing a crash:

Oxford Dynamics Native.vst3

Maybe try avoiding anything from Oxford ?

Thanks for the suggestion - I've disabled every Oxford plugin from the system now, and just had a crash (as I went into the grading tab).

I'm going to go through all the other suggestions above one by one, very grateful for everyone's help.

[Dwaine Maggart]

When you've eliminated each obvious crash suspect, if you provide a Resolve diagnostics log file after each new crash, that could be helpful.

When you've eliminated each obvious crash suspect, if you provide a Resolve diagnostics log file after each new crash, that could be helpful.

Thanks Dwaine. Now I hesitate to say it, but I'm on the third day without a crash!

I disabled the hitfilm plugins which didn't seem to help. Then I disabled the AMD video card from Windows Device Manager and... no crashes. At all.

It's very odd to me. The card wasn't enabled in Resolve, and additionally I'd not changed anything between my happy early months and the more recent crash-fest. So I'd say this isn't yet definitive, but at the moment it seems solid and well.

If the crashes return I'll send another file and a note of any changes made - thanks!

Send an updated Resolve log file.

Thanks - new log here (and I can now post a clean URL!):

https://www.dropbox.com/scl/fi/vnxxf1e1 ... ef4fx&dl=0

It's a nightmare so very grateful for all help. Resolve just crashed in the background in the time it took for me to move the crashlog file from the desktop and move it to dropbox. I've now disabled Oxford Supressor in preferences, and have bought a new internal NVMe drive. I've moved the render cache to this new NVMe, and all footage has migrated too. Having had a good morning, it's now crashing more than ever.

My advise to you, uninstall Resolve and any third party plugin in your PC, including audio plugins. Do a fresh install of Resolve 19.1.3. Test it throughly with your projects to make sure Resolve dose not crash. If it works fine, then install your plugins but one at a time to fully test it and make sure it is not the cause of the crash. Keep doing that until you know which plugin is causing the problem.