Blackmagic Forum

A few days ago I upgraded my work station and updated Davinci Resolve to the latest version (Studio 19). Afterwhich, the program has been crashing CONSTANTLY (Every few minutes).

Drivers are up to date (Nvidia Studio Driver ver. 565.90) And GPU processing is set to CUDA in Davinci system settings.

Specs:

Mobo - Gigabyte GA-B650-AORUS-ELITE-AX AM5
CPU - Ryzen 7 7700x
GPU - Asus Nvidia Geforce RTX 3070
PSU - RM850 — 850 Watt 80 PLUS® Gold Certified
Ram - XPG Lancer Blade 64GB (32GB x2) DDR5-6000MHz CL30
Storage - Samsung 990 EVO 2TB (x1), Mushkin Vortex 2TB (x2)

I have stress tested the hardware (GPU, CPU, RAM and Storage). No errors were detected.

For months and months I had been using a version of Davinci studio 18 (cannot remember which version exactly). When I upgraded my pc and did a fresh install of windows, I decided to update Davinci to the latest version.

When booting the updated Davinci for the first time, I was greeted with a prompt to allow AI GPU optimisation, which I allowed. Figuring this could be the issue, I later disabled it via the preferences menu in Davinci, but this made no difference.

Sometimes Davinci crashes with no error and other times I receive error codes 700 and error codes 1.

I am working on a 1080p timeline. I am simply cutting and moving pieces around. I am working with the same video files I always do, from the same client. Nothing has changed in regards to the footage I am working with. But I can hardly work for 10 minutes at a time without the program crashing.

I have retrieved my crash logs after the crash. I am just not sure how to upload this to the forum or which files in the crash log folder is required for you guys to assist.

I thank anyone who takes the time to help me in advance. Any assistance on this matter would be greatly appreciated, thank you.

Did you update the Nvidia driver?

IIRC, error codes 700 is a GPU that get full, check the video drivers and be sure that in teh preference in your settings CUDA is explicitly selected.

Yes sorry I should have specified. Drivers are up to date (Nvidia Studio Driver ver 565.90) And CUDA is explicitly selected in Davinci system settings.

Try
NVIDIA Driver - Studio driver 550.58

I changed absolutely nothing and things seemed to have stablised for now... thanks.

And we are back to crashing every few minutes... I have once again updated to the latest studio version driver for my GPU, yet the issue continues. Now back to crashing every few SECONDS with error code 700

Sukoshi wrote:And we are back to crashing every few minutes... I have once again updated to the latest studio version driver for my GPU, yet the issue continues. Now back to crashing every few SECONDS with error code 700

Did you try Peter suggestion?

No i didn't, I was currently busy with projects and I was worried it would interfer with things to backdate the drivers.

BUT I figured out the issue!

This may help others who have tried everything and nothing works... my specific issue was my RAM. After I upgraded my pc, I enabled the xmp profile to take my ram from 4800 to 6000 mhz. And this is what caused the issue. So even though Davinci says its error 700 (gpu), it's not. It was my ram running at an unstable speed.

What makes this even weirder is that I ran a stress tester for the ram to see if it could function stable under load. On the test it performed perfectly... but not in davinci.

Once i reverted the RAM back to it's default speeds in the system BIOS, everything was functioning smoothly.

Thank you all for your attempts to solve the situation. Hopefully someone else will benefit from this info.

I have seen a few reports over the years when folks tried overclocking various components.

As a good rule of thumb, don't.

Not on an edit system.

Yes, we learn the hard way haha

Yeah.. OC can do that...

Why is that? I OC my system and everything else runs fine. System is completely stable. Video editing is WHY you'd want to OC.

Okay wait... problem IS NOT solved... Good grief this is exhausting. Davinci is crashing a lot less, but still crashing semi frequently.

I will try the suggestion for using a different driver version and report back.

Peter Chamberlain wrote:Try
NVIDIA Driver - Studio driver 550.58

I can't find this version

This may be useful:

viewtopic.php?p=1099799#p1099799

I am not seeing anywhere in this thread where the crash logs have been provided. Without those for Black Magic to analyze, any other ideas are just speculation. Weird things happen in computers. I once had an issue with the old Internet Explorer, where clicking on a hyperlink before the page fully loaded (slow dial-up days) would crash the entire computer. Turned out to be the mouse driver.

If you're running into crashes, go to the Help Menu and select "Create Diagnostics Log on Desktop." If you're running Windows, create an NFO file by using the MSINFO32 command in the Start menu. Place both files on a download site like Dropbox and post the link here in a forum message.

I OC my system and everything else runs fine.

You are lucky! It all depends on the particular chips in your box and the work load. Computer chips are designed and rated to run at a certain speed. Most of them will run faster. Maybe. For a while. But no guarantees. If a system is unstable, over-clocking is one of the first things to suspect.

If you can I’d suggest turning off the OC and seeing if that fixes it. If it does, can you gradually turn up the OC until it starts crashing again and then back it off?

Joe Shapiro wrote:This may be useful:

viewtopic.php?p=1099799#p1099799

I appreciate it, but I don't use RTSS

Joe Shapiro wrote:If you can I’d suggest turning off the OC and seeing if that fixes it. If it does, can you gradually turn up the OC until it starts crashing again and then back it off?

I had the XMP profile for my RAM originally on and there was crashing, turned it off and there was less crashing (at the start) but now we are back to normal crashing

Here are my crash logs. I cannot read these, maybe someone here can make sense of them:

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

Has anyone been able to decode the mess that is this crash log yet?

What about the process of elimination?

Take out the GPU and use the built-in on the Ryzen 7 7700x.
If that doesn't work, take out one stick of RAM. If that doesn't work, put it back and take out another one. Repeat until you go through them all.

Open your task manager during editing so that at least you can see where the load is. Good luck

luisvalenzuela wrote:What about the process of elimination?

Take out the GPU and use the built-in on the Ryzen 7 7700x.
If that doesn't work, take out one stick of RAM. If that doesn't work, put it back and take out another one. Repeat until you go through them all.

Open your task manager during editing so that at least you can see where the load is. Good luck

So the crash log provides no useful info then?

Try disabling the iGPU .. many times i've seen integrated graphics messing things up

ohimbz wrote:Try disabling the iGPU .. many times i've seen integrated graphics messing things up

You mean in davinci? It is disabled. Only my main GPU is in use and enabled.

Are you using a Render Cache?

ShaheedMalik wrote:Are you using a Render Cache?

Nope, set to "none"

I was asked to upload my crash logs because apparently this is the best way to sus out a problem? Which I did.

So if anyone here is able to read through that and make sense of it, I would greatly appreciate the feedback. Otherwise if there is no luck in finding an answer, then I guess I will have to go through my hardware one at a time to see which part could be causing the issue.

Sukoshi wrote:

luisvalenzuela wrote:What about the process of elimination?

Take out the GPU and use the built-in on the Ryzen 7 7700x.
If that doesn't work, take out one stick of RAM. If that doesn't work, put it back and take out another one. Repeat until you go through them all.

Open your task manager during editing so that at least you can see where the load is. Good luck

So the crash log provides no useful info then?

I'm not support and do not understand the logs. I take the practical approach on what I would do if the software was crashing on my custom system.

One more suggestion is to uninstall Resolve Studio and run the Free version. I remember at least once the Studio version would instantly crash for me, but Free worked just fine.

For reference, Resolve 19.x has been stable on turnkey machines from my experience: MacBooks. The hardware on these devices is uniform across most of them, so I imagine if BM makes Resolve work great on one, it works great on all.

ohimbz wrote:Try disabling the iGPU .. many times i've seen integrated graphics messing things up

Yup, seen it on my system too (with Resolve & a few other apps).. I've just disabled the Internal Graphics (via Bios). I don't know if Resolve or the other packages I've had issues with is because it tries to access the iGPU (not a coder, hardware guy here).

That said, if you do not use your Internal GPU (iGPU), just disable it... Saves ya alot of headaches in the long run.

Regarding the comments to disable the iGPU, this will cause Resolve to not launch due to OpenGL issues. So don't do that. (Disabling it in the BIOS may work, but definitely don't disable it in Windows Device Manager - Display Adapters).

@Kyle: we need a Windows System Information .NFO file. Generate that by opening the Windows System Information app and selecting its File - Save menu.

Would also be helpful to have project export .drps for your "Oval Race Collab" and "Uni coin" projects.

Dwaine Maggart wrote:Regarding the comments to disable the iGPU, this will cause Resolve to not launch due to OpenGL issues. So don't do that. (Disabling it in the BIOS may work, but definitely don't disable it in Windows Device Manager - Display Adapters).

@Kyle: we need a Windows System Information .NFO file. Generate that by opening the Windows System Information app and selecting its File - Save menu.

Would also be helpful to have project export .drps for your "Oval Race Collab" and "Uni coin" projects.

^^^__ Yup... Do not disable iGPU driver from within windows (device manager). If you want to disable it, do it from BIOS (before windows loads - for those who don't know).

That said, I can confirm at on least my system - Resolve loads without the iGPU (disabled in BIOS).

Buttt..

please backup your projects & database before doing anything - have a great weekend everyone

Dwaine Maggart wrote:Regarding the comments to disable the iGPU, this will cause Resolve to not launch due to OpenGL issues. So don't do that. (Disabling it in the BIOS may work, but definitely don't disable it in Windows Device Manager - Display Adapters).

@Kyle: we need a Windows System Information .NFO file. Generate that by opening the Windows System Information app and selecting its File - Save menu.

Would also be helpful to have project export .drps for your "Oval Race Collab" and "Uni coin" projects.

Here are all the files as requested...

https://drive.google.com/drive/folders/ ... sp=sharing

Thank you for taking the time

i also disabled my IGPU as suggested, no difference.

The only thing different is now instead of getting the error code 700, Davinci just crashes to desktop now.

I don't see anything in your projects that should cause a GPU mem error.

However, I do notice this in the logs:

Out-of-memory exception caught, purging memory: Packer OpenGL interop failed.

Googling for that indicates:

Packer is primarily used to create virtual machine images for various cloud providers, often requiring the creation of graphical environments which rely on OpenGL.

Are you doing anything like that?

Dwaine Maggart wrote:I don't see anything in your projects that should cause a GPU mem error.

However, I do notice this in the logs:

Out-of-memory exception caught, purging memory: Packer OpenGL interop failed.

Googling for that indicates:

Packer is primarily used to create virtual machine images for various cloud providers, often requiring the creation of graphical environments which rely on OpenGL.

Are you doing anything like that?

No, and if something like that has been set up or running, it's not because I set it up that way. How do I check if something like this is happening?

No idea. Have never seen that before. It's only in the most recent crash log, with project "Uni coin".

The 2nd most recent crash log, also with GPU mem errors, is using project "Oval Race Collab".

Both logs are also complaining of "3rd Party Decode Err". So the issue seems perhaps related to the specific source files in use with those 2 projects.

Have you installed any 3rd party codec packages on your system?

This would be a file being complained about in the "Uni coin" project:

<C:\Business\1 Clients\Mando\2 - To do\2 - Uni Coin\UNI CAM.mp4>

This would be a file being complained about with the "Oval Race Collab" project:

<C:\Business\1 Clients\Goosiest\To Do\FH5 Oval Race\Rizon POV.mkv>

If you could provide links to those 2 files, I can see if the issue can be repro'd on my system.

In the meantime, since the issue seem related to GPU file decoding, in Resolve Preferences - System - Decode Options, if you uncheck the "Decode H.264/H.265 using hardware acceleration" option, save the prefs and restart Resolve, does that work better?

Dwaine Maggart wrote:No idea. Have never seen that before. It's only in the most recent crash log, with project "Uni coin".

The 2nd most recent crash log, also with GPU mem errors, is using project "Oval Race Collab".

Both logs are also complaining of "3rd Party Decode Err". So the issue seems perhaps related to the specific source files in use with those 2 projects.

Have you installed any 3rd party codec packages on your system?

This would be a file being complained about in the "Uni coin" project:

<C:\Business\1 Clients\Mando\2 - To do\2 - Uni Coin\UNI CAM.mp4>

This would be a file being complained about with the "Oval Race Collab" project:

<C:\Business\1 Clients\Goosiest\To Do\FH5 Oval Race\Rizon POV.mkv>

If you could provide links to those 2 files, I can see if the issue can be repro'd on my system.

In the meantime, since the issue seem related to GPU file decoding, in Resolve Preferences - System - Decode Options, if you uncheck the "Decode H.264/H.265 using hardware acceleration" option, save the prefs and restart Resolve, does that work better?

Apologies for the late response.

Not certain it has anything to do with the specific source files, as mention in my original post, I am working with exactly the same files I have always been working with. So I am not sure why now all of a sudden they would be a problem after upgrading my pc. Maybe I am missing something though?

As far as 3rd party codec packages are concerned, no not to my knowledge. Windows did install hevc codec so that I was able to view the videos I was being sent on my desktop. But again, I have always downloaded this from windows and never had an issue with it.

I have followed your advice to uncheck the decoding option you specified, but that has not changed anything for me sadly. Still crashing.

As for the links to the project files, it is happening on every single project I work with. I have noticed that it happens far more often with unoptimised media, but again... it has never ever crashed on me before because of it. Only now after I have upgraded my system.

My Ryzen system needed a small bump in RAM voltage to be stable with Resolve. Something to try!


Sent from my iPhone using Tapatalk