Resolve Studio 17 just crashes

Hello,

I'm using Resolve Studio 17 on a new Notebook Computer and I'm facing a problem I never had seen before when I was using Resolve for two years. Resolve just crashes, no Error Code, nothing, it just closes.

The Hardware configuration of the Notebook is pretty unique. It's a Xiaomi Mi Notebook Pro 15" 2021.
The best of this Notebook is a 3,5K OLED Screen.

I thought it would work great for resolve with neewer HEVC Footage because it has a i7-11370H CPU with a Intel Xe iGPU that can and does decode even Canon R5 or R6 Footage.

Also it has a dedicated MX450 CPU with 2GB VRAM that is capable of CUDA.

When resolve runs, it's impressively good in performance for such a "low powered" Notebook, but it just runs for 5-10 Minuten and then crashes and closes without any error code.

I assumed that it has to do with the 2GB of VRAM but thats Resolve Hardware Requirement for CUDA GPUs.

Also very interesting is that I can't use the iGPU for Resolve because it wouldn't let me select it.
If I select OpenCL I'm not able to select the Intel Xe GPU.

If I want to use just the Intel Xe GPU I need to deactivate the MX450 in the System Device Manager.

Is there anything that can be done about this?

Here is the Log File: https://drive.google.com/open?id=11OTfj ... UIPS_LgnEY

Here the NFO File: https://drive.google.com/open?id=1FCPgX ... XFX6ECsSvI

For someone to be able to help, they will need to see the log and NFO file.

From the Troubleshooting FAQ:

Logs
DaVinci Resolve has a function to generate diagnostic logs that can be analysed to look for problems. It is important to get the logs from DaVinci Resolve, generated immediately after a crash. OS generated diagnostics and logs are of little use. Please post a link to these logs on the forum - this will often give others a chance to assist you. If you are unable to post a link, put a space in the path so the forum doesn't think its a link, eg. my logsarehere. com

You can grab logs by restarting DaVinci Resolve and choosing “Create Diagnostic Logs on Desktop” from the Help menu.

If you cannot launch DaVinci Resolve after a crash, please follow the steps below:

Windows:
Go to C:/Program Files/Blackmagic Design/DaVinci Resolve/ and run CaptureLogs.bat application

NFO File
In Windows start menu, open Windows System Information. From the File menu, select Save and save this NFO file.

For someone to be able to help, they will need to see the log and NFO file.

From the Troubleshooting FAQ:

Logs
DaVinci Resolve has a function to generate diagnostic logs that can be analysed to look for problems. It is important to get the logs from DaVinci Resolve, generated immediately after a crash. OS generated diagnostics and logs are of little use. Please post a link to these logs on the forum - this will often give others a chance to assist you. If you are unable to post a link, put a space in the path so the forum doesn't think its a link, eg. my logsarehere. com

You can grab logs by restarting DaVinci Resolve and choosing “Create Diagnostic Logs on Desktop” from the Help menu.

If you cannot launch DaVinci Resolve after a crash, please follow the steps below:

Windows:
Go to C:/Program Files/Blackmagic Design/DaVinci Resolve/ and run CaptureLogs.bat application

NFO File
In Windows start menu, open Windows System Information. From the File menu, select Save and save this NFO file.

Thank you very much!

Here is the Log File: https://drive.google.com/open?id=11OTfj ... UIPS_LgnEY

Here the NFO File: https://drive.google.com/open?id=1FCPgX ... XFX6ECsSvI

Unfortunately, I need to add my voice to getting a lot more crashes in 17.2. Whether rendering or using magic mask on the color page. Lots of different things are causing crashes now.

[Peter Chamberlain]

Erik, u have been on the forum and report issues, and crashes, please post nfo and logs.

Thank you Peter. I had the understanding that the log files are only helpful if you export immediately after a crash. Unfortunately, when working and experiencing crashes, the last thing you want to do is export a log file but try to complete the work that is needed on a timely basis.

It would be helpful if the log files contained more of a history I think.

Regardless, I have created a NFO and Log file at the following link. Thanks.

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

Hello,

I'm using Resolve Studio 17 on a new Notebook Computer and I'm facing a problem I never had seen before when I was using Resolve for two years. Resolve just crashes, no Error Code, nothing, it just closes.

The Hardware configuration of the Notebook is pretty unique. It's a Xiaomi Mi Notebook Pro 15" 2021.
The best of this Notebook is a 3,5K OLED Screen.

I thought it would work great for resolve with neewer HEVC Footage because it has a i7-11370H CPU with a Intel Xe iGPU that can and does decode even Canon R5 or R6 Footage.

Also it has a dedicated MX450 CPU with 2GB VRAM that is capable of CUDA.

When resolve runs, it's impressively good in performance for such a "low powered" Notebook, but it just runs for 5-10 Minuten and then crashes and closes without any error code.

I assumed that it has to do with the 2GB of VRAM but thats Resolve Hardware Requirement for CUDA GPUs.

Also very interesting is that I can't use the iGPU for Resolve because it wouldn't let me select it.
If I select OpenCL I'm not able to select the Intel Xe GPU.

If I want to use just the Intel Xe GPU I need to deactivate the MX450 in the System Device Manager.

Is there anything that can be done about this?

Here is the Log File: https://drive.google.com/open?id=11OTfj ... UIPS_LgnEY

Here the NFO File: https://drive.google.com/open?id=1FCPgX ... XFX6ECsSvI

This machine seems very underpowered to run resolve 17, I’m surprised that it runs at all...

This machine seems very underpowered to run resolve 17, I’m surprised that it runs at all...

You can "run" Resolve basically on anything that has a half decent GPU in it. How it runs depends on what you want to do. With Proxies you can use nearly whatever Hardware you want and it will work.

Resolve got Support for Intels Hardware Decoding in Xe iGPUs in 17.1 so this Hardware is basically what Resolve 17.1 and following is made for.

I would even be happy if I can just choose the iGPU for Resolve, because it will run, but unfortunatly I can't.

Is there anything that can be done about this?

When parts become available again, build a proper desktop.

Until then...

https://www.productionhub.com/

This machine seems very underpowered to run resolve 17, I’m surprised that it runs at all...

You can "run" Resolve basically on anything that has a half decent GPU in it. How it runs depends on what you want to do. With Proxies you can use nearly whatever Hardware you want and it will work.

Resolve got Support for Intels Hardware Decoding in Xe iGPUs in 17.1 so this Hardware is basically what Resolve 17.1 and following is made for.

I would even be happy if I can just choose the iGPU for Resolve, because it will run, but unfortunatly I can't.

David, it looks like you have everything under control.

Happy resolve.

Is there anything that can be done about this?

When parts become available again, build a proper desktop.

Until then...

https://www.productionhub.com/

I have a Threadripper 3970X, 128GB RAM and an RTX 3090
but I want it to work on my Notebook too for liitle work I do on the go or on the couch.

[Peter Chamberlain]

Thank you Peter. I had the understanding that the log files are only helpful if you export immediately after a crash. Unfortunately, when working and experiencing crashes, the last thing you want to do is export a log file but try to complete the work that is needed on a timely basis.

It would be helpful if the log files contained more of a history I think.

Regardless, I have created a NFO and Log file at the following link. Thanks.

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

Do you have a constant and fixed render cache path on an internal drive?
Do you have more than one monitor connected, how many and are they the same resolution?
If not, try removing the odd one or two till you see if operation improves.

Thank you Peter.

Do you have a constant and fixed render cache path on an internal drive?
Yes, it is a fixed internal drive.
Do you have more than one monitor connected, how many and are they the same resolution?
I have a 3 monitor setup using a clean feed for video output to 1080p HD.
If not, try removing the odd one or two till you see if operation improves.
"If not"? Did you mean instead "if so"? I kind of need all 3 monitors to edit effectively.

More crash logs from yesterday at the link provided.

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

[Peter Chamberlain]

Do the monitors have the same res?
and do the crashes stop if there is only one monitor?

Hi Peter,

I have started a new and soon-to-be large project. I am not getting any consistent crashes so far but will keep you updated. I did have one crash right at the beginning of the day which is unusual. I have put the log at the link below.

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

Thanks,

Erik

I keep adding more Davinci crash logs but the only response I got was what happens if you turn off a monitor or two. Are these logs of any help to anyone? I will stop sending if they aren't useful.

Erik

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

I finally had time to do some testing with running Davinci Resolve 17.2 on a single monitor. I can not detect any differences in the likelihood of a crash. Most of my crashes are happening at the conclusion of a usually successful render. Sometimes the crashes are at the beginning of a render when I have told DR to replace a clip with same name for the render output.

Sometimes the crashes are more typical, light usage of Fusion. Or more intensive usage of the Color page. In general 17.2 is more crashy for me than 17.0.

I noticed the difference after 17.1 update.

Erik

I now have a repeatable crash from Davinci Resolve 17.2.

I have included the DRP and the Davinci Resolve log file/NFO file at this link.

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

Whenever I render a timeline the program crashes every time at the completion of the render. *I should add that the render is completed successfully.* I have tried turning everything off related to secondary monitors using reset GUI and the result is the same, crash.

Erik

I have added a different project drp file and the Davinci log file at the link below. Same problem with a completely different project. Single monitor or multiple monitors. Render successfully completes but Davinci Resolve 17.2 immediately crashes.

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