Resolve Studio 18.5.1-up Intel Quicksync memory crashes

Hi Davinci enjoyers,

I have been using Davinci Resolve Studio very happily since 17 on my windows desktop. Let me be clear, I am very glad to have made the switch from Premiere as I think its the superior program by far. I love Davinci.

However, since 18.5 it has been an absolute disaster for me using the studio version. the 18.5 public beta releases have been working flawless on my system but ever since the public release of 18.5 and 18.5.1 editing has become almost impossible. I have never ever in my life posted on a forum because I have always been able to figure it out myself. Here i am though.

This is the general flow of what is happening:
1. I create a project
2. Create multiple bins for my footage, music, sfx, timelines, fusion clips etc.
3. I chuck in my GoPro, and Mirrorless footage in to the correct bins.
4. Scrolling through the bins with footage the thumbnails start to generate.
5. I see Vram rising to the max allowed in Davinci
6. It starts to spill over to system ram to it's max (Ignoring the limits set in the DaVinci preferences)
7. System becomes unusable, laggy as you can expect when there is no more ram available to use for anything else but Davinci. Davinci crashes.
8. Mind you this is only just scrolling through the bins in ed edit tab in the top left.
9. If i start dragging some clips i.e. about 10 it becomes significantly worse and dropping anything in starts to become impossible let alone scrubbing through the timeline.

What have i done to try and fix it (System specs below):
1. reading online through this forum post seems to be the literal same issue I have:
[https://linustechtips.com/topic/1502427-davinci-resolve-eats-up-all-available-memory-then-crashes/](https://linustechtips.com/topic/1502427 ... n-crashes/ "https://linustechtips.com/topic/1502427-davinci-resolve-eats-up-all-available-memory-then-crashes/")
2. Rolled back countless AMD drivers all the way back to 23.2 (Think i tried around 9 GPU drivers total)
3. Tried 18.5 and 18.5.1
4. Tried different Intel 13600k internal GPU drivers (had thoughts it could be the internal Quick sync encoder losing its mind or something).
5. Updated windows 11 to the latest version with all updates etc.
6. Updated al mobo chipset and USB drivers etc.
7. After all this I started to suspect the windows install itself, so created a dual boot with a clean windows 11 install with nothing installed (apart from the essentials ofc) but Davinci.
8. Same issues persisted so I think its not the windows install.
9. Also tried moving all footage to the OS disk so no external SSD (Thought it could maybe be a bad USB driver), also didn't work
10. Here I absolutely lost it and decided to switch from an AMD RX 6800XT to an Nvidia RTX 3090 because I was reading online on multiple forums that the latest AMD drivers and Latest Davinci resolve studio was an unstable situation. Also after reading the above linked forum post. Wanted to try out Davinci with team green anyway so why not.
11. Initially it seemed to work a lot better but after a while and having a timeline with 20 clips, scrolling through the Bins increases ram beyond what's available and crashes.
12. Some projects just open with insane ram usage of the get go and crash straight after opening them. (15 unedited clips on timeline)

I am aware that all footage I use is encoded in H.265. This is ofc not ideal for timelines smoothness etc but always been willing to accept that since I think its still workable on modern hardware. Editing in 18.1.2 and 18.5 public beta was never an issue with the same raw H.265 files with normal ram usage. Also with bigger timelines with 300+ clips, effects, sfx, colour grades etc. Not even kidding that it sometimes crashes so hard I have the re enter my activation code to start up studio. For the heck of it i decided to generate very low quality proxies for my files which seemed to alleviate the problem a bit but eventually it still had the same behaviour and crashes. It only extends the problem to a later occurrence.

The loading of all the thumbnails of these files in either the bins or the timeline seems to be the culprit. I have attached a crash log dump of one project instance below. I think it still has log data from my previous GPU and the current Nvidia GPU. Hope the issue is somewhere in there for some wizard to find . I really hope either Blackmagic themselves can solve this issue or some other insane wizard out there.

I see no other option then rolling back to 18.1.2 and losing my 18.5 projects because of new library structure and start from scratch or try out 18.5 public beta again but I don't have that install online and cannot find a copy anywhere.

Crash log dump:
https://drive.google.com/file/d/16JZuFC ... sp=sharing

System specs:
First system:
CPU: Intel I5-13600k latest drivers everything
GPU: AMD RX 6800XT latest drivers everything
RAM: 32gb 6000mhz DDR5 ram.
Storage: Internal M.2 1tb Samsung 990pro
External storage (Footage): Samsung T7 2tb USB C connected to Mobo.

Second System after GPU upgrade:
CPU: Intel I5-13600k latest drivers everything
GPU: RTX 3090 FE latest drivers everything.
RAM: 32gb 6000mhz DDR5 ram.
Storage: Internal M.2 1tb Samsung 990pro
External storage (Footage): Samsung T7 2tb USB C connected to Mobo.

Out of date comment

[Dwaine Maggart]

Could you please also provide a Windows System Information .NFO file? Open the Windows System Information app and select its File - Save menu to create the .NFO file.

Logs indicate a 3rd party decoder issue. Can you also provide a project export .drp of the 29_BB_ROADTRIP project, so we can see what type of media it's using?

You should certainly try the current 18.6 release, to see if it behaves better.

As far as older versions, all Resolve versions back to 10.1.5 are available on the BMD site in the Support area for DaVinci Resolve and Fusion:

https://www.blackmagicdesign.com/suppor ... and-fusion

I am aware that all footage I use is encoded in H.265. This is ofc not ideal for timelines smoothness.

Your system shouldn't have any trouble with 265. The one obvious reason that it might (I say might) be slower is the media hanging off the USB port. A slow port and or drive could be an issue. But your HW should handle 265 just fine.

Could you please also provide a Windows System Information .NFO file? Open the Windows System Information app and select its File - Save menu to create the .NFO file.

Logs indicate a 3rd party decoder issue. Can you also provide a project export .drp of the 29_BB_ROADTRIP project, so we can see what type of media it's using?

You should certainly try the current 18.6 release, to see if it behaves better.

As far as older versions, all Resolve versions back to 10.1.5 are available on the BMD site in the Support area for DaVinci Resolve and Fusion:

https://www.blackmagicdesign.com/suppor ... and-fusion

Excuse me for not providing that earlier, should've known. NFO is in the attachments, so is the project .drp.

They are GoPro 8:7 stabalized in Gyroflow : 5312x298830p 4:2:0 subsampled 10 bit H.265
Fujifilm All-Intra 360mbps 4k60p 4:2:2 subsampled 10 bit H2.65.

I mentioned this in another post as well.(viewtopic.php?f=21&t=188240) It must be the Intel iGPU / quicksync encoder. When I deselect the intel encoder in the DR preferences and solely use my RTX 3090 there is no issue with crashing or massive memory usage. Memory usage spikes heavily while loading the thumbnails in the Bins but stabilizes to normal use thereafter. I can use DR normally then.

The weird thing is I have used the intel iGPU successfully before with both footage types in previous DR's. If I roll back myself now it also happens in earlier versions.

Installed a windows 10 instance also and the same problem arises.

I was aware that older Davinci versions are available on the site, but not the public beta's unfortunately. So didn't have the ability to test that.

DR 18.6, the crashes are still there.

Link to DRP and NFO:
https://drive.google.com/file/d/1riCd4m ... sp=sharing

Another test project with same files and works with only Nvidia selected as encoder option:
https://drive.google.com/file/d/1j6XWCo ... sp=sharing

I am aware that all footage I use is encoded in H.265. This is ofc not ideal for timelines smoothness.

Your system shouldn't have any trouble with 265. The one obvious reason that it might (I say might) be slower is the media hanging off the USB port. A slow port and or drive could be an issue. But your HW should handle 265 just fine.

Yeah I also had the same thoughts. This hardware should work well with these footage types, it did before anyway.

I did move this project footage to my internal 990 pro Samsung NVME m.2 and the same problem still persisted, so storage is unfortunately not the solution.

Thanks anyway!

[Dwaine Maggart]

It appears you have an Intel ARC driver installed. But your Intel GPU is a UHD Graphics 770 iGPU.

And the NFO system error log has lots of ARC Control Assist errors. But again, you don't have an ARC GPU.

That seems problematic.

I would suggest you go to the ASUS support site for your Z790M-ITX WiFi mobo and download and install their current Intel VGA driver: ver:31.0.101.3302_Planned

See if that behaves better.

It appears you have an Intel ARC driver installed. But your Intel GPU is a UHD Graphics 770 iGPU.

.

It's the same driver package.

Intel® Arc™ A770 Graphics (16GB)
Intel® Arc™ A770 Graphics (8GB)
Intel® Arc™ A750 Graphics
Intel® Arc™ A380 Graphics
Intel® Arc™ A310 Graphics
Intel® Arc™ A770M Graphics
Intel® Arc™ A730M Graphics
Intel® Arc™ A570M Graphics
Intel® Arc™ A550M Graphics
Intel® Arc™ A530M Graphics
Intel® Arc™ A370M Graphics
Intel® Arc™ A350M Graphics

Intel® Core™ i9-13900 Processor (36M Cache, up to 5.60 GHz)


Intel® Core™ i7-13700 Processor (30M Cache, up to 5.20 GHz)

Intel® Core™ i5-13600K Processor (24M Cache, up to 5.10 GHz)

I edited out many other systems. The list of supported systems is pages long.

BTW on the memory leak some people are seeing there is a comment on the Intel forum that the issue is the Ark software not the driver. Looking at my system the control software is eating a lot of memory. The suggestion on the forum was to use the older driver after DDU . The old package has an older version of the software .

[Dwaine Maggart]

OK, I was just going by what your NFO was showing installed, which is Intel driver 31.0.101.4676.

It appears you have an Intel ARC driver installed. But your Intel GPU is a UHD Graphics 770 iGPU.

.

It's the same driver package.

Intel® Arc™ A770 Graphics (16GB)
Intel® Arc™ A770 Graphics (8GB)
Intel® Arc™ A750 Graphics
Intel® Arc™ A380 Graphics
Intel® Arc™ A310 Graphics
Intel® Arc™ A770M Graphics
Intel® Arc™ A730M Graphics
Intel® Arc™ A570M Graphics
Intel® Arc™ A550M Graphics
Intel® Arc™ A530M Graphics
Intel® Arc™ A370M Graphics
Intel® Arc™ A350M Graphics

Intel® Core™ i9-13900 Processor (36M Cache, up to 5.60 GHz)


Intel® Core™ i7-13700 Processor (30M Cache, up to 5.20 GHz)

Intel® Core™ i5-13600K Processor (24M Cache, up to 5.10 GHz)

I edited out many other systems. The list of supported systems is pages long.

BTW on the memory leak some people are seeing there is a comment on the Intel forum that the issue is the Ark software not the driver. Looking at my system the control software is eating a lot of memory. The suggestion on the forum was to use the older driver after DDU . The old package has an older version of the software .

Thanks for your contribution. I was also about the say that its the same driver package compatible with the i5-13600k. So that should be correct at least.

Is there word out that deinstalling the Ark control software fixes it or rolling back to an older driver fixes it for those folks? Can you link that particular forum post here?

Looks like there are more people out there on this forum including the Intel forums having this issue. Think it's worthwhile for Blackmagic and/or Intel to have a good look at what's going on here.

I'll try out deinstalling the ark control software and rolling back to older driver with DDU tonight and will report.

OK, I was just going by what your NFO was showing installed, which is Intel driver 31.0.101.4676.

Hi, thank you for looking into this problem.

I rolled back Intel driver to 30.0.101.1029 [11/3/2021]. A driver from no Intel ARC GPU era.
I'm still getting the same memory leak problem. With Davinci resolve, Intel iGPU memory usage can not go pass 27.5GB on my 12900H laptop with 64GB of ram. Intel iGPU can use up to maximum 32GB.
What I did notice from version 18.5 is that when it is about to crash due to the Intel iGPU quicksync memory leak. Davinci resolve 18.5 and newer will automaticly save the project before quitting without any warning tabs/notifications.

The current workaround is disabling the thumbnail generation. System with 32GB RAM or less will crash much faster due to smaller iGPU RAM pool.

When enabling hardware Intel quicksync to decode H.265 4:2:2 10bit files, I do not get the same iGPU thumbnail memory overload problem with the latest premiere pro.

OK, I was just going by what your NFO was showing installed, which is Intel driver 31.0.101.4676.

I Deinstalled Ark control panel --> Memory leak / crashing persists
DDU'd Intel driver and installed the one from my Mobo manufacturer. This driver is from 2022 --> Memory leak / crashing persists.

Tried this as well on my clean windows 10 install with the same results. Even reverted back all my Bios settings to stock to also eliminate that

At this point I am almost entirely sure this a DR bug. I hope it is worthwhile for the DR team to look at this. Hope some temporary fix or patch is possible.

Warm regards!

OK, I was just going by what your NFO was showing installed, which is Intel driver 31.0.101.4676.

Since I am not the only one with this thing happening. Is Blackmagic looking into this?

Kind regards!

Is there word out that deinstalling the Ark control software fixes it or rolling back to an older driver fixes it for those folks? Can you link that particular forum post here?
.

https://downloadmirror.intel.com/788789 ... 1.4826.pdf

That's the readme for the last driver update 31.0.101.4826 I've no idea what happens if you just remove the arc software. Is the removal clean? Is a stub left around that's broken? It would seem the "safe" choice would be to not remove it but to update it. If that works then remove it.

INTEL® ARC™ CONTROL FIXED ISSUES:
• Intel® Arc™ Control may consume higher than expected system memory

Is there word out that deinstalling the Ark control software fixes it or rolling back to an older driver fixes it for those folks? Can you link that particular forum post here?
.

https://downloadmirror.intel.com/788789 ... 1.4826.pdf

That's the readme for the last driver update 31.0.101.4826 I've no idea what happens if you just remove the arc software. Is the removal clean? Is a stub left around that's broken? It would seem the "safe" choice would be to not remove it but to update it. If that works then remove it.

INTEL® ARC™ CONTROL FIXED ISSUES:
• Intel® Arc™ Control may consume higher than expected system memory

I can try it that way yes. I only install the driver not the arc software. You can choose that in the installer. So I Doubt this problem has to due with the Arc control software (Not saying there was no problem previously because from what I read there actually was). This seems to be different. When Davinci crashes due to massive ram spikes I can see in task mngr that it's attributed to DR. Thanks for giving me another idea to try out though.

Is there word out that deinstalling the Ark control software fixes it or rolling back to an older driver fixes it for those folks? Can you link that particular forum post here?
.

https://downloadmirror.intel.com/788789 ... 1.4826.pdf

That's the readme for the last driver update 31.0.101.4826 I've no idea what happens if you just remove the arc software. Is the removal clean? Is a stub left around that's broken? It would seem the "safe" choice would be to not remove it but to update it. If that works then remove it.

INTEL® ARC™ CONTROL FIXED ISSUES:
• Intel® Arc™ Control may consume higher than expected system memory

I can try it that way yes. I only install the driver not the arc software. You can choose that in the installer. So I Doubt this problem has to due with the Arc control software (Not saying there was no problem previously because from what I read there actually was). This seems to be different. When Davinci crashes due to massive ram spikes I can see in task mngr that it's attributed to DR. Thanks for giving me another idea to try out though.

Another clean install with Arc control and same issue persists. Intel Quick sync crashes Davinci