Suddenly ALL renders freeze/crash

I have opened a support ticket (still have not heard back from BM Support from last week's Critical Error Saving ticket) but now all of a sudden starting yesterday the feature that I am trying to render out just freezes during the render and not at the same points. And last night as I tried another render overnight I woke up to see no Resolve even open so it crashed and vanished. I have made the Capture Logs, info, etc. Not sure what has changed as the Nvidia GPU is current. Anyone else having this issue? We are trying to get to Picture Lock.

AMD Ryzen 9 3900x 12-Core 24 logical processors
64 GB RAM
GeForce RTX 2080 Super

This is my issue rendering STOP...how to resolve

The only renders I recall failing in any version of 17 were HDR projects using a too old GTX 960. Those same renders came out fine on a slightly newer 1070.

[Peter Chamberlain]

Post ur logs and nfo as per FAQs.
You can also describe source and render codec which might help someone guide you.
Also try reducing render speed in render file settings

Thank you Peter. I did reduce my render speed to 50. What part of the Capture Log do I post here? I'm not sure which part is useful. And I was rendering to an .mp4 which I had been doing with the work prints until yesterday. I feel like a setting was changed somehow or something stupid like that for it to suddenly not work. And thanks again man. We greatly appreciate any and all help here.

Also try reducing render speed in render file settings

That advice confuses me, Peter. I thought the purpose of that feature was to limit disk access bandwidth in a network environment so that one user doesn't hog it all, allowing other users to access the network disks as well.

It seems to me that it should have no effect whatsoever on whether or not a render fails. Renders should always take as much time as they need to properly process a frame.

So to my thinking, if reducing render speed solves a failed render, there is a bug in Resolve that needs fixing.

Where's my error?

Attached is the Capture Log after the last render crash attempt. I have been trying isolate what files(s) might be causing this as I have rendered several workprints until a few days ago. I do have 2 image files in the new part where it seems to just freeze and I see that those are .psd transparent images. The only other components of the 30 second section that seems to be the problem area are 3 .mp4 files and 2 Resolve Text files.

Now after trying to remove the potential problem clip(s) so I can troubleshoot each one to see which one(s) could be triggering this I am getting that Critical Error Saving project loop again followed by a new and bizarre Error Message that I have never seen before and as when this started last week before the render crashes/freezes you have to End Task to get DR to even close.

nfo

OS Name Microsoft Windows 10 Home
Version 10.0.18363 Build 18363
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name DESKTOP-H8JKG1D
System Manufacturer To Be Filled By O.E.M.
System Model To Be Filled By O.E.M.
System Type x64-based PC
System SKU To Be Filled By O.E.M.
Processor AMD Ryzen 9 3900X 12-Core Processor, 3800 Mhz, 12 Core(s), 24 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. P2.60, 4/8/2020
SMBIOS Version 3.2
Embedded Controller Version 255.255
BIOS Mode UEFI
BaseBoard Manufacturer ASRock
BaseBoard Product X570 Phantom Gaming 4
BaseBoard Version
Platform Role Desktop
Secure Boot State Off
PCR7 Configuration Binding Not Possible
Windows Directory C:\windows
System Directory C:\windows\system32
Boot Device \Device\HarddiskVolume2
Locale United States
Hardware Abstraction Layer Version = "10.0.18362.752"
User Name DESKTOP-H8JKG1D\bryan
Time Zone Eastern Daylight Time
Installed Physical Memory (RAM) 64.0 GB
Total Physical Memory 63.9 GB
Available Physical Memory 18.4 GB
Total Virtual Memory 73.4 GB
Available Virtual Memory 20.7 GB
Page File Space 9.50 GB
Page File C:\pagefile.sys
Kernel DMA Protection Off
Virtualization-based security Not enabled
Device Encryption Support Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and device is not Modern Standby, Un-allowed DMA capable bus/device(s) detected, TPM is not usable
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware Yes
Hyper-V - Data Execution Protection Yes

[Peter Chamberlain]

Post a link to the full logs generated by resolve and the nfo. Put them on Dropbox if u need.

[Peter Chamberlain]

Also try reducing render speed in render file settings

That advice confuses me, Peter. I thought the purpose of that feature was to limit disk access bandwidth in a network environment so that one user doesn't hog it all, allowing other users to access the network disks as well.

It seems to me that it should have no effect whatsoever on whether or not a render fails. Renders should always take as much time as they need to properly process a frame.

So to my thinking, if reducing render speed solves a failed render, there is a bug in Resolve that needs fixing.

Where's my error?

Let’s assume fir a moment that the file system or GPU decoder provides data it thinks is good but it’s not, but it didn’t report that to Resolve so we couldn’t slow to edit for it, all we received was bad data masquerading as good. Sometimes slowing the render helps.
I’ve heard this is particularly the case with over clocked systems but we haven’t tried to repo that as we just don’t recommend over clocking

Edited for clarification

Post a link to the full logs generated by resolve and the nfo. Put them on Dropbox if u need.

Hey Peter. Thank you for replying.
Here are the full Log and nfo links. I hope I linked these right

https://www.dropbox.com/s/thmqvb0sjexc1jr/DaVinci-Resolve-logs-20210426-085437.zip?dl=0

https://www.dropbox.com/s/phrv4ugcslc9nmh/BW%20System%20Info.nfo?dl=0

it ran out of time to process correctly

That's the part that confuses me. Render should always take all the time it needs. Why is Resolve artificially limiting that time allowed?

I don't recall ever using another program that did that, so that's why I'm not understanding.

Post a link to the full logs generated by resolve and the nfo. Put them on Dropbox if u need.

Latest Capture Log taken after I tried to delete what I think might be the offending clip/image:

https://www.dropbox.com/s/82g4x455f0ryrh8/DaVinci-Resolve-logs-20210426_%2092019.zip?dl=0

Tried to render from a copy of the Timeline with what I thought what might have been the offending clip(s) removed and this time it has frozen during the render at the 55% mark which is not even close to where it was consistently freezing/crashing (76% most of the time). It still says Rendering in Progress but nothing is happening and you can't even Stop the render.

I have experienced render freezing on 17.1.1, never had an issue with any other 17 betas.

Yesterday I have experienced the same so I selected everything inside the timeline I wanted to render out and pasted it in a different project on a timeline that I had recently rendered out.

It worked, rendered no problem. Somehow the project file must have got corrupted during the freezing/quitting of resolve.

[Peter Chamberlain]

it ran out of time to process correctly

That's the part that confuses me. Render should always take all the time it needs. Why is Resolve artificially limiting that time allowed?

I don't recall ever using another program that did that, so that's why I'm not understanding.

Resolve is not driving it faster, nor limiting the time, let me rephrase, what I mean is the process says it’s completed to Resolve but it’s not, or it’s bad data that’s given.

I have experienced render freezing on 17.1.1, never had an issue with any other 17 betas.

Yesterday I have experienced the same so I selected everything inside the timeline I wanted to render out and pasted it in a different project on a timeline that I had recently rendered out.

It worked, rendered no problem. Somehow the project file must have got corrupted during the freezing/quitting of resolve.

This is interesting as I did that to temporarily get out of that Critical Error Saving Project loop. When you say a different Project how did you copy/paste to a new Project altogether?

Thankfully Dmitry from BM is on my case looking into everything for me.

I have experienced render freezing on 17.1.1, never had an issue with any other 17 betas.

Yesterday I have experienced the same so I selected everything inside the timeline I wanted to render out and pasted it in a different project on a timeline that I had recently rendered out.

It worked, rendered no problem. Somehow the project file must have got corrupted during the freezing/quitting of resolve.

This is interesting as I did that to temporarily get out of that Critical Error Saving Project loop. When you say a different Project how did you copy/paste to a new Project altogether?

I just seleceted everything in a timeline and copy then open a new project and timeline and pasted everything. I dont even think you need messing with importing media it just works like that. The two projects were open at the same time, not sure if that makes a difference but you can activate having multiple projects open at the same time right clicking into where your projects are listed and click on "Dynamic Project Switching' (

)

the process says it’s completed to Resolve but it’s not

OK, that I can understand. Thanks.

But...that sounds like a bug to me. The process shouldn't be reporting completion until it's actually complete. No?

I mean, I'm not a programmer and maybe that will prevent a full understanding here, but...again I don't recall ever seeing such behavior in any other software that renders video.

I have experienced render freezing on 17.1.1, never had an issue with any other 17 betas.

Yesterday I have experienced the same so I selected everything inside the timeline I wanted to render out and pasted it in a different project on a timeline that I had recently rendered out.

It worked, rendered no problem. Somehow the project file must have got corrupted during the freezing/quitting of resolve.

This is interesting as I did that to temporarily get out of that Critical Error Saving Project loop. When you say a different Project how did you copy/paste to a new Project altogether?

I just seleceted everything in a timeline and copy then open a new project and timeline and pasted everything. I dont even think you need messing with importing media it just works like that. The two projects were open at the same time, not sure if that makes a difference but you can activate having multiple projects open at the same time right clicking into where your projects are listed and click on "Dynamic Project Switching' (

)

Hey Mario! Thank you for the tip and video. I've learned a lot from that guy. I did try this and sadly when I went to render it still Froze/Crashed again. Makes no sense as literally everything on the TL has been rendered fine until last week. I did notice when I copied/pasted the couple of Fusion comps the work I did in them did not show up like the simple Paint and Wire-Removal I did. Weirdest part is it is now seemingly getting frozen on DR's own Title Horizon Line Reveal Text clip. I just need whatever has suddenly happened after several successful renders to be sorted as our deliverables deadline is looming.

So I replaced DR's own Text file with a different one and I was able to render past that new problem point but it still Froze and then Crashed at the 76% mark and the clip that is right there is a clip that was rendered IN DR! I'm at a loss here. It shouldn't be this difficult.

Latest Capture Log from the most recent Render Freeze/Crash at the 76% mark. Really need help here.

https://www.dropbox.com/s/jxkh4m2on9mabl2/DaVinci-Resolve-logs-20210427_195520.zip?dl=0

Try checking each clip with a fusion composition, it could be there is an error in there. It happened to me once I had a photos slideshow, I forgot to enter text for a caption in the fusion composition that animate one of the photos. If there is something missing in the fusion composition once you go back in you should see visually as it's highlighted in red.

Thanks Mario. I'll do that and see if anything jumps out. I appreciate your input very much.

I just selected everything in a timeline and copy then open a new project and timeline and pasted everything. I don't even think you need messing with importing media it just works like that. The two projects were open at the same time, not sure if that makes a difference...

Yes, it does make a difference. The more projects you have open at the same time, the more RAM will be used and the more system resources will be used.

I've learned a lot from that guy. I did try this and sadly when I went to render it still Froze/Crashed again. Makes no sense as literally everything on the TL has been rendered fine until last week. I did notice when I copied/pasted the couple of Fusion comps the work I did in them did not show up like the simple Paint and Wire-Removal I did.

My workaround would be: render the Fusion composition in a virtually-lossless format like DNxHR and then drop it into the timeline and color correct it for final delivery. Don't try to render a Fusion composition with a color-corrected timeline unless you have an extremely powerful system.

I don't have a problem with automatically cutting down on the render speed just as standard procedure. I'm generally not in so much of a hurry that I can't limit the speed to 25fps or even 10fps. I know there's not going to be any problems if I do that.

Hey Marc!
Thank you for the suggestion. I still have not received any answers or suggestions from BM tech Support so I took your advice on the "Render In Place" on the clip (not a Fusion comp but a clip that was rendered from resolve on a different project) that seemed to be for some unknown reason freezing and crashing during rendering. I then changed the Render output directory to my C drive since i had not tried that yet and voila it rendered overnight. I am now sifting through the rendered file and making notes on the things that DR "moved/scrambled" on the timeline when the Critical Error loop happened and my restored TL had several clips all moved around like a grenade went off on the TL. I'll keep everyone posted and again I truly appreciate the help and advice from fellow BM'ers.

I also wanted to wrap this up by giving a shoutout to Dmitry from BM Tech Support as he emailed me just now a lengthy and very detailed breakdown of what I can do for this project now and helpful settings tips.

I am now sifting through the rendered file and making notes on the things that DR "moved/scrambled" on the timeline when the Critical Error loop happened and my restored TL had several clips all moved around like a grenade went off on the TL.

Wow, that is bad. If the project has become "slightly" corrupted, I can see where that might happen. My suggestion would be to Export the project to a new one, then open the new one and fix the timelines as best you can. Sometimes exporting from a corrupted DRP can create a workable file with no problems. Make sure you back it up. It should not scramble anything in the timeline, but I have had cases where links got broken, render cache files went stupid, Gallery stills went missing, and so on.

Hi all

Just wanted to say I'm seeing this also. Nothing renders and just seems to crash at "Rendering in Progress". Have also tried exporting project, moving to different clean install of Resolve and re-importing/linking media ... same thing. (OSX BigSur Release 11.2.3 & Beta 11.4 )

I also wanted to wrap this up by giving a shoutout to Dmitry from BM Tech Support as he emailed me just now a lengthy and very detailed breakdown of what I can do for this project now and helpful settings tips.

Anything useful to us that you can share?

Have found a workaround mentioned elsewhere ... the issue, for me at least, is with Fusion bundled Titles. Prerender these and everything works again ..