Crashing Constantly, DR 19.1 Studio

Sorry if this is a redundant thread, but I I am getting constant crashes in Resolve Studio Version 19.1 Build 12, Windows 10, i5-13600K, 96GB DDR4 RAM, RTX 2060 Super 8GB VRAM, Driver Version 566.14

Is it ok to revert back to version 19 Resolve Studio??? Is there a painless way to do that?

Admittedly, I am trying to do a few speed ramps and a few magic masks with 4K UHD h.264 / h.265 footage on only 8GB of VRAM, but I hope someone could look through the logs and say yes or no whether it is the lack of VRAM that is causing the problems, and if there are alternatives to just throwing money at an expensive GPU

Here is a link to the Diagnostic Logs Folder after the most recent crash:
https://www.dropbox.com/scl/fo/6tqy34mw ... j2ohz&dl=0

Here is the latest crash_archive.txt. I removed everything before DR Studio 19.1 for brevity's sake.

Code: Select all

----------------------------------------------------------------------

----------------------------------------------------------------------
#TIME Sun Aug 18 22:01:19 2024 - Uptime 02:16:44 (hh:mm:ss)
#PROGRAM_NAME DaVinci Resolve Studio v18.6.6.0007 (Windows/MSVC x86_64)
#BMD_ARCHITECTURE x86_64
#BMD_BUILD_UUID 38bc271b-9970-455d-9b0c-dbd7706f3c71
#BMD_GIT_COMMIT 3f827ef0d730e66d9a676870f5237d1a0008c1ec
#BMD_UTIL_VERSION 18.6.6.0007
#OS Windows


----------------------------------------------------------------------
#TIME Tue Sep 17 15:07:20 2024 - Uptime 01:22:43 (hh:mm:ss)
#PROGRAM_NAME DaVinci Resolve Studio v19.0.1.0006 (Windows/MSVC x86_64)
#BMD_ARCHITECTURE x86_64
#BMD_BUILD_UUID a0aad6e6-4887-478e-a37e-b63f08750dd1
#BMD_GIT_COMMIT 4d411512f6e86a6ec85f1b804dfd553884f2e761
#BMD_UTIL_VERSION 19.0.1.0006
#OS Windows


----------------------------------------------------------------------
#TIME Mon Nov 11 18:10:31 2024 - Uptime 05:50:03 (hh:mm:ss)
#PROGRAM_NAME DaVinci Resolve Studio v19.0.3.0005 (Windows/MSVC x86_64)
#BMD_ARCHITECTURE x86_64
#BMD_BUILD_UUID 81e000d4-84f7-4d2b-aee9-cdc15eacf829
#BMD_GIT_COMMIT 67f92ed0dbc9aa2b4da3ccfaba0b32405cef11ac
#BMD_UTIL_VERSION 19.0.3.0005
#OS Windows


----------------------------------------------------------------------
#TIME Tue Nov 12 14:03:36 2024 - Uptime 04:21:32 (hh:mm:ss)
#PROGRAM_NAME DaVinci Resolve Studio v19.0.3.0005 (Windows/MSVC x86_64)
#BMD_ARCHITECTURE x86_64
#BMD_BUILD_UUID 81e000d4-84f7-4d2b-aee9-cdc15eacf829
#BMD_GIT_COMMIT 67f92ed0dbc9aa2b4da3ccfaba0b32405cef11ac
#BMD_UTIL_VERSION 19.0.3.0005
#OS Windows


----------------------------------------------------------------------
#TIME Mon Nov 18 18:23:54 2024 - Uptime 01:15:54 (hh:mm:ss)
#PROGRAM_NAME DaVinci Resolve Studio v19.1.0.0012 (Windows/MSVC x86_64)
#BMD_ARCHITECTURE x86_64
#BMD_BUILD_UUID da8edb93-f21f-4cc2-83ce-30b6bf2ce650
#BMD_GIT_COMMIT 6def76c8ecd41d97024d3515d2ab5dd1214b4b05
#BMD_UTIL_VERSION 19.1.0.0012
#OS Windows


----------------------------------------------------------------------
#TIME Thu Nov 21 14:31:40 2024 - Uptime 00:13:54 (hh:mm:ss)
#PROGRAM_NAME DaVinci Resolve Studio v19.1.0.0012 (Windows/MSVC x86_64)
#BMD_ARCHITECTURE x86_64
#BMD_BUILD_UUID da8edb93-f21f-4cc2-83ce-30b6bf2ce650
#BMD_GIT_COMMIT 6def76c8ecd41d97024d3515d2ab5dd1214b4b05
#BMD_UTIL_VERSION 19.1.0.0012
#OS Windows


----------------------------------------------------------------------
#TIME Thu Nov 21 14:38:10 2024 - Uptime 00:05:58 (hh:mm:ss)
#PROGRAM_NAME DaVinci Resolve Studio v19.1.0.0012 (Windows/MSVC x86_64)
#BMD_ARCHITECTURE x86_64
#BMD_BUILD_UUID da8edb93-f21f-4cc2-83ce-30b6bf2ce650
#BMD_GIT_COMMIT 6def76c8ecd41d97024d3515d2ab5dd1214b4b05
#BMD_UTIL_VERSION 19.1.0.0012
#OS Windows


----------------------------------------------------------------------
#TIME Sat Nov 23 18:30:54 2024 - Uptime 00:03:58 (hh:mm:ss)
#PROGRAM_NAME DaVinci Resolve Studio v19.1.0.0012 (Windows/MSVC x86_64)
#BMD_ARCHITECTURE x86_64
#BMD_BUILD_UUID da8edb93-f21f-4cc2-83ce-30b6bf2ce650
#BMD_GIT_COMMIT 6def76c8ecd41d97024d3515d2ab5dd1214b4b05
#BMD_UTIL_VERSION 19.1.0.0012
#OS Windows


----------------------------------------------------------------------
#TIME Sat Nov 23 18:34:38 2024 - Uptime 00:03:01 (hh:mm:ss)
#PROGRAM_NAME DaVinci Resolve Studio v19.1.0.0012 (Windows/MSVC x86_64)
#BMD_ARCHITECTURE x86_64
#BMD_BUILD_UUID da8edb93-f21f-4cc2-83ce-30b6bf2ce650
#BMD_GIT_COMMIT 6def76c8ecd41d97024d3515d2ab5dd1214b4b05
#BMD_UTIL_VERSION 19.1.0.0012
#OS Windows


----------------------------------------------------------------------
#TIME Sat Nov 23 18:38:49 2024 - Uptime 00:03:39 (hh:mm:ss)
#PROGRAM_NAME DaVinci Resolve Studio v19.1.0.0012 (Windows/MSVC x86_64)
#BMD_ARCHITECTURE x86_64
#BMD_BUILD_UUID da8edb93-f21f-4cc2-83ce-30b6bf2ce650
#BMD_GIT_COMMIT 6def76c8ecd41d97024d3515d2ab5dd1214b4b05
#BMD_UTIL_VERSION 19.1.0.0012
#OS Windows


----------------------------------------------------------------------
#TIME Sat Nov 23 18:46:14 2024 - Uptime 00:07:03 (hh:mm:ss)
#PROGRAM_NAME DaVinci Resolve Studio v19.1.0.0012 (Windows/MSVC x86_64)
#BMD_ARCHITECTURE x86_64
#BMD_BUILD_UUID da8edb93-f21f-4cc2-83ce-30b6bf2ce650
#BMD_GIT_COMMIT 6def76c8ecd41d97024d3515d2ab5dd1214b4b05
#BMD_UTIL_VERSION 19.1.0.0012
#OS Windows


----------------------------------------------------------------------
#TIME Sat Nov 23 18:53:59 2024 - Uptime 00:02:54 (hh:mm:ss)
#PROGRAM_NAME DaVinci Resolve Studio v19.1.0.0012 (Windows/MSVC x86_64)
#BMD_ARCHITECTURE x86_64
#BMD_BUILD_UUID da8edb93-f21f-4cc2-83ce-30b6bf2ce650
#BMD_GIT_COMMIT 6def76c8ecd41d97024d3515d2ab5dd1214b4b05
#BMD_UTIL_VERSION 19.1.0.0012
#OS Windows


----------------------------------------------------------------------
#TIME Sat Nov 23 19:44:07 2024 - Uptime 00:30:56 (hh:mm:ss)
#PROGRAM_NAME DaVinci Resolve Studio v19.1.0.0012 (Windows/MSVC x86_64)
#BMD_ARCHITECTURE x86_64
#BMD_BUILD_UUID da8edb93-f21f-4cc2-83ce-30b6bf2ce650
#BMD_GIT_COMMIT 6def76c8ecd41d97024d3515d2ab5dd1214b4b05
#BMD_UTIL_VERSION 19.1.0.0012
#OS Windows


----------------------------------------------------------------------
#TIME Sat Nov 23 19:52:47 2024 - Uptime 00:05:27 (hh:mm:ss)
#PROGRAM_NAME DaVinci Resolve Studio v19.1.0.0012 (Windows/MSVC x86_64)
#BMD_ARCHITECTURE x86_64
#BMD_BUILD_UUID da8edb93-f21f-4cc2-83ce-30b6bf2ce650
#BMD_GIT_COMMIT 6def76c8ecd41d97024d3515d2ab5dd1214b4b05
#BMD_UTIL_VERSION 19.1.0.0012
#OS Windows


----------------------------------------------------------------------
#TIME Sat Nov 23 20:02:05 2024 - Uptime 00:04:09 (hh:mm:ss)
#PROGRAM_NAME DaVinci Resolve Studio v19.1.0.0012 (Windows/MSVC x86_64)
#BMD_ARCHITECTURE x86_64
#BMD_BUILD_UUID da8edb93-f21f-4cc2-83ce-30b6bf2ce650
#BMD_GIT_COMMIT 6def76c8ecd41d97024d3515d2ab5dd1214b4b05
#BMD_UTIL_VERSION 19.1.0.0012
#OS Windows


----------------------------------------------------------------------
#TIME Sat Nov 23 20:06:39 2024 - Uptime 00:04:04 (hh:mm:ss)
#PROGRAM_NAME DaVinci Resolve Studio v19.1.0.0012 (Windows/MSVC x86_64)
#BMD_ARCHITECTURE x86_64
#BMD_BUILD_UUID da8edb93-f21f-4cc2-83ce-30b6bf2ce650
#BMD_GIT_COMMIT 6def76c8ecd41d97024d3515d2ab5dd1214b4b05
#BMD_UTIL_VERSION 19.1.0.0012
#OS Windows


----------------------------------------------------------------------
#TIME Sun Nov 24 22:35:03 2024 - Uptime 00:00:56 (hh:mm:ss)
#PROGRAM_NAME DaVinci Resolve Studio v19.1.0.0012 (Windows/MSVC x86_64)
#BMD_ARCHITECTURE x86_64
#BMD_BUILD_UUID da8edb93-f21f-4cc2-83ce-30b6bf2ce650
#BMD_GIT_COMMIT 6def76c8ecd41d97024d3515d2ab5dd1214b4b05
#BMD_UTIL_VERSION 19.1.0.0012
#OS Windows


----------------------------------------------------------------------
#TIME Sun Nov 24 23:38:22 2024 - Uptime 01:03:06 (hh:mm:ss)
#PROGRAM_NAME DaVinci Resolve Studio v19.1.0.0012 (Windows/MSVC x86_64)
#BMD_ARCHITECTURE x86_64
#BMD_BUILD_UUID da8edb93-f21f-4cc2-83ce-30b6bf2ce650
#BMD_GIT_COMMIT 6def76c8ecd41d97024d3515d2ab5dd1214b4b05
#BMD_UTIL_VERSION 19.1.0.0012
#OS Windows

00007FF79867C62C
000002453F633310
00007FFD39D5B86B
00000000000A0006
000000000000000F
000000CACB5FCDD0
00007FF79867C580
00007FFD3520E6E0

----------------------------------------------------------------------
#TIME Sun Nov 24 23:55:19 2024 - Uptime 00:03:15 (hh:mm:ss)
#PROGRAM_NAME DaVinci Resolve Studio v19.1.0.0012 (Windows/MSVC x86_64)
#BMD_ARCHITECTURE x86_64
#BMD_BUILD_UUID da8edb93-f21f-4cc2-83ce-30b6bf2ce650
#BMD_GIT_COMMIT 6def76c8ecd41d97024d3515d2ab5dd1214b4b05
#BMD_UTIL_VERSION 19.1.0.0012
#OS Windows


----------------------------------------------------------------------
#TIME Mon Nov 25 09:33:40 2024 - Uptime 00:11:31 (hh:mm:ss)
#PROGRAM_NAME DaVinci Resolve Studio v19.1.0.0012 (Windows/MSVC x86_64)
#BMD_ARCHITECTURE x86_64
#BMD_BUILD_UUID da8edb93-f21f-4cc2-83ce-30b6bf2ce650
#BMD_GIT_COMMIT 6def76c8ecd41d97024d3515d2ab5dd1214b4b05
#BMD_UTIL_VERSION 19.1.0.0012
#OS Windows




P.S. Thanks to Uli and Jim Simon for help they have provided in another thread.

Here are my three latest crashes from this afternoon:

Code: Select all

----------------------------------------------------------------------
#TIME Mon Nov 25 14:20:20 2024 - Uptime 00:10:11 (hh:mm:ss)
#PROGRAM_NAME DaVinci Resolve Studio v19.1.0.0012 (Windows/MSVC x86_64)
#BMD_ARCHITECTURE x86_64
#BMD_BUILD_UUID da8edb93-f21f-4cc2-83ce-30b6bf2ce650
#BMD_GIT_COMMIT 6def76c8ecd41d97024d3515d2ab5dd1214b4b05
#BMD_UTIL_VERSION 19.1.0.0012
#OS Windows


----------------------------------------------------------------------
#TIME Mon Nov 25 14:34:28 2024 - Uptime 00:04:26 (hh:mm:ss)
#PROGRAM_NAME DaVinci Resolve Studio v19.1.0.0012 (Windows/MSVC x86_64)
#BMD_ARCHITECTURE x86_64
#BMD_BUILD_UUID da8edb93-f21f-4cc2-83ce-30b6bf2ce650
#BMD_GIT_COMMIT 6def76c8ecd41d97024d3515d2ab5dd1214b4b05
#BMD_UTIL_VERSION 19.1.0.0012
#OS Windows

00007FF684C5C62C
000000755210C890
00007FF8E5A7B86B
0000000000030007
000000000000004D
000000755210CA10
00007FF684C5C580
00007FF8E16EE6E0

----------------------------------------------------------------------
#TIME Mon Nov 25 14:45:55 2024 - Uptime 00:02:30 (hh:mm:ss)
#PROGRAM_NAME DaVinci Resolve Studio v19.1.0.0012 (Windows/MSVC x86_64)
#BMD_ARCHITECTURE x86_64
#BMD_BUILD_UUID da8edb93-f21f-4cc2-83ce-30b6bf2ce650
#BMD_GIT_COMMIT 6def76c8ecd41d97024d3515d2ab5dd1214b4b05
#BMD_UTIL_VERSION 19.1.0.0012
#OS Windows

[Dwaine Maggart]

Yes, it's OK to revert to an earlier 19 version. But your 19 projects aren't readable in earlier versions, like 18.

Edit: Didn't see your logs link. Thought you'd only posted the inline log snippets.

Yes, it's OK to revert to an earlier 19 version. But your 19 projects aren't readable in earlier versions, like 18.

Edit: Didn't see your logs link. Thought you'd only posted the inline log snippets.

Thank you for the reply. Yes, hope the link has the correct files and the System NFO file should be in that folder too.

Thanks again.

Also, it seems like the one project that crashes has a few graphics-heavy effects (mostly speed ramp and zoom transition). I have been able to open and render some other projects that didn't have those effects.

Another also: I did create an earlier thread on Friday about crashing on render so you can ignore that one for now. Sorry for double posting.

[Dwaine Maggart]

Hard to tell what's going on, because only 1 of 5 expected crash logs is in the diagnostics log package.

Every time Resolve crashes, we generate a C log. We keep the last 5 C logs and the last 5 good logs in the

C:\Users\Lenovo PC\AppData\Roaming\Blackmagic Design\DaVinci Resolve\Support\logs\LogArchive folder.

We also keep 5 rolling logs in the

C:\Users\Lenovo PC\AppData\Roaming\Blackmagic Design\DaVinci Resolve\Support\logs folder.

There is only 1 C log (C2) and no rolling logs. As your crash_archive.txt file shows, Resolve has crashed several times. Meaning there should be 5 C logs. And there should be rolling logs.

Are those being deleted somehow, by you or some file cleanup process? That lack of all that log data makes diagnosis difficult.

The C2 log shows it crashed at 23:55:19 on 11-24, with project "70 Broadmoor 4K". Do you recall what you may have been doing in that project when that crash happened?

Having a project export of the "70 Broadmoor 4K" project could be helpful, if that's the project most of the crashing is happening in.

Finally, I only see one Resolve crash in the Windows NFO Windows Error Reporting area. On 11-21. But I see LOTS of this error:

Faulting application name: IAStorDataMgrSvc.exe, version: 16.8.3.1003, time stamp: 0x5d2c38da
Faulting module name: unknown

Maybe/probably not related to the Resolve issues, but being storage related, seems kinda scary to me.

Hard to tell what's going on, because only 1 of 5 expected crash logs is in the diagnostics log package.

Every time Resolve crashes, we generate a C log. We keep the last 5 C logs and the last 5 good logs in the

C:\Users\Lenovo PC\AppData\Roaming\Blackmagic Design\DaVinci Resolve\Support\logs\LogArchive folder.

We also keep 5 rolling logs in the

C:\Users\Lenovo PC\AppData\Roaming\Blackmagic Design\DaVinci Resolve\Support\logs folder.

There is only 1 C log (C2) and no rolling logs. As your crash_archive.txt file shows, Resolve has crashed several times. Meaning there should be 5 C logs. And there should be rolling logs.

Are those being deleted somehow, by you or some file cleanup process? That lack of all that log data makes diagnosis difficult.

The C2 log shows it crashed at 23:55:19 on 11-24, with project "70 Broadmoor 4K". Do you recall what you may have been doing in that project when that crash happened?

Having a project export of the "70 Broadmoor 4K" project could be helpful, if that's the project most of the crashing is happening in.

Finally, I only see one Resolve crash in the Windows NFO Windows Error Reporting area. On 11-21. But I see LOTS of this error:

Faulting application name: IAStorDataMgrSvc.exe, version: 16.8.3.1003, time stamp: 0x5d2c38da
Faulting module name: unknown

Maybe/probably not related to the Resolve issues, but being storage related, seems kinda scary to me.

Thanks for the follow up. Here is an UPDATED link. I believe I have followed the instructions correctly (the system nfo file is in the logs archive folder, too). But if I understand correctly, then with these updated logs it seems like two crash reports have vanished.

https://www.dropbox.com/scl/fo/jf7m8fl5 ... f3742&dl=0

1) No, I am not deleting any files automatically nor by hand, as far as I can tell. (Please note I have downgraded to Resolve Studio 19.03 now and am still experiencing the crashes.)

2) I will export the 70 Broadmoor Project shortly, as that is the only one that seems to be problematic.

3) The crashes happen when scrubbing, and when exporting that particular project.

4) Regarding Disk errors, is this because I have both the source footage and the proxies on a spinning 7200 RPM hard drive instead of an SSD drive?

5) I noticed in the performance tab of the task manager that when the rendering gets to a speed ramp, the Video Encode of the GPU spikes to 100%, despite my using intel quick sync as the render Type. I guess Resolve MUST use my RTX 2060 Super for rendering certain effects then?

Having a project export of the "70 Broadmoor 4K" project could be helpful, if that's the project most of the crashing is happening in.

Here is a link to the drp file:

https://www.dropbox.com/scl/fi/0kh5nmbk ... ji606&dl=0

Sorry if this is a noob question, but do you need me to upload the 138GB of source footage as well??? My upload speeds are pretty slow

[Dwaine Maggart]

We generally don't require project media. We hope the drp will give us enough clues. If it comes to needing some or all the media to investigate an issue, we'll request it.

On clip 99, on the Edit page Inspector, in the Retime and Scaling area, if you change Retime Process and Motion Estimation from Optical Flow and Speed Warp Better to Project Settings, does that help things?

We generally don't require project media. We hope the drp will give us enough clues. If it comes to needing some or all the media to investigate an issue, we'll request it.

On clip 99, on the Edit page Inspector, in the Retime and Scaling area, if you change Retime Process and Motion Estimation from Optical Flow and Speed Warp Better to Project Settings, does that help things?

Thanks again for taking a look at this.

I was able to get the project to render ONCE by doing the following:

1) As yoiu mentioned, changed clip 99 from optical flow to project settings for retime

2) Delete both clips 14 and 15 (and left a blank space on the timeline) as clip 15 had the speed ramp, and while Clip 14 technically didn't have any retiming, it did show the retime icon (the little black ramp icon) on the clip.

I was able to render it once, but when i tried rendering it again a couple more times, it crashed around 42% complete both times.

Now, the crazy thing about this is, about two weeks ago, I was able to render this project out perfectly fine. I rendered it out completely at least three times. It didn't crash at all, if I recall correctly.

I might have been on Resolve Studio 19.0.3 two weeks ago when I rendered it out fine, and I was on a previous version of the NVidia driver (sorry not sure which version), and it was just before the latest update of Windows 10 that came out about a week ago or so.

Another kind of a weird thing: When rendering now, as the play head moves about halfway through clip 32 (the clip with the starting timecode of 05:40:06;29 ) the fans on my computer begin spinning up louder and louder throught the render (until it crashes). I can honestly say that I have never heard the fans spin up that loud when rendering before.

I am going to double check that I have correctly updted the bios on my motherboard since it's a Gen 13 Intel chip and I remember those were the ones having the voltage problems.

Hi Mark, try to add some tool to monitoring temperature and voltage, seems there is some problems. Resolve use mainly gpu and fan of computer usually up be cause you have temperature problem on cpu.


Inviato dal mio iPhone utilizzando Tapatalk

I can see the effects you're using being a problem for a card with only 8GB of VRAM.

I consider 12 GB of VRAM as a bare minimum for success with Resolve.

I can see the effects you're using being a problem for a card with only 8GB of VRAM.

I consider 12 GB of VRAM as a bare minimum for success with Resolve.

Thank you, Jim.

I guess I am used to before, where Resolve WOULDN'T crash, but instead stopped and gave me the Low VRAM Message. I did experience that in the past whenI had too many nodes.

But this is the first time for a lot of constant crashes.

Off Topic Rant: Now seems to be a particularly bad time to buy a new video card. I guess there are new ones that will be announced. And the current mid-range GPUs with 16GB VRAM tend to suck (like the a770 or the 4060 TI 16GB)

One of those Mac minis looks more and more tempting everyday (although I know they will have a ton of issues themselves).

Hi Mark, try to add some tool to monitoring temperature and voltage, seems there is some problems. Resolve use mainly gpu and fan of computer usually up be cause you have temperature problem on cpu.


Inviato dal mio iPhone utilizzando Tapatalk

Thank you.

Can you suggest a toool for monitoring temperature and voltage?

A few things to update about the situation:

1) Render ALWAYS crashes when trying to use the Vimeo 2160 preset, AND it always seems to crash when the playhead has reached (more-or-less) the same spont on the timeline: right where clips 14 and 15 USED to be on the playhead.

Note that I have REMOVED clips 14 and 15 from the timeline so now there is just a gap in the video track there. So I don't know why it would still crash at that spot.

2) I have been able to render successfully using either the Custom render tab, or the h.264 master tab, and even using the YouTube 2160 presets and Intel Quick Sync for encoding, but the file sizes are pretty big compared (around 1GB h.264 file for a project just under five-minutes). Previously, when I was able to export the project with the Vimeo 2160 profile, the exported h.264 .mov file was only about 140MB. Any suggestions for keeping the file size down when exporting from Custom or h264 Master or even Youtube 2160 preset are appreciated.

3) Resolve crash log Creator does NOT create a new ResolveDebug file when Resolve crashes during a render. I believe it only creates a new ResolveDebug file on my system if it crashes on something like the Edit page or Color Page, but not when it has crashed during rendering.

4) I dont want to jump to conclusions just yet, but I do strongly suspect that my RTX 2060 Super 8GB is hitting its max voltage limit (nominally 175 watts) when rendering. I am using HWMonitor and it says that the volltages are reaching about 180+ Watts 98% GPU utilization, and a power limit level of 1. Oddly enough, it says that it is only using 5142MB of the available 8GB dedicated (VRAM?) Memory.

This particular RTX 2060 Super is a single-fan card that came originally bundled with an AlienWare (i.e., Dell) gaming pc. So it is not the most robust card (and I think that most aftermarket, dual-fan cards have a nominal max wattage rating of 225 watts).