Blackmagic Forum

Posted: **Mon Sep 16, 2024 4:59 pm**

Great find!
IMHO this tough to find problem should be fixed by Resolve checking to see if it’s running in Rosetta and if so, pointing the user to a help file that explains what’s going wrong and how to fix it.

Posted: **Mon Sep 16, 2024 7:37 pm**

pajamas55 wrote:@Dwaine What do you reccommend to resolve this situation? I need to work and I've not being able to for almost a week.
Should I do a clean install? I can't think of an alternative, other than revert to Resove 18.

Any suggestions @Dwaine?

Posted: **Mon Sep 16, 2024 8:12 pm**

pajamas55 wrote:
SkierEvans wrote:Checked latest download on all my machines and they all seem to play fine in CUT, edit and colour pages. However I noticed that there was a very slight delay in lip sync on clip 4. Happened on all machines. To recap my email PC an old 3770K 1080Ti with the free version of Resolve 19 then the two in my signature. Both PC's show failed to load USD.plugin at launch.

I do not normally use proxies so checked what the project has set. It is set to prefer proxies so I reset to originals and the lip sync is now correct, instant playback. Happens on all three machines. These files are also not the originals but exports from Resolve so we may not be seeing the effect of the original files.

If I reset to Camera Originals I'm back in slow motion and audio out of sync. Really don't know what to try next. Perhaps a full unistall of Resolve and GPU drivers, then reinstall?

Just updated Nvidia RTX 3060 Driver to version 32.0.15.6109. Still no difference, the issue persists.

Posted: **Mon Sep 16, 2024 8:40 pm**

pajamas55 wrote:
pajamas55 wrote:
If I reset to Camera Originals I'm back in slow motion and audio out of sync. Really don't know what to try next. Perhaps a full unistall of Resolve and GPU drivers, then reinstall?

Just updated Nvidia RTX 3060 Driver to version 32.0.15.6109. Still no difference, the issue persists.

Hmmm! If I select the clips and 'Render in Place' it all plays back normally. Perhaps this is a workaround? Never had to do this previously.

Posted: **Mon Sep 16, 2024 8:53 pm**

pajamas55 wrote:
pajamas55 wrote:
pajamas55 wrote:
If I reset to Camera Originals I'm back in slow motion and audio out of sync. Really don't know what to try next. Perhaps a full unistall of Resolve and GPU drivers, then reinstall?

Just updated Nvidia RTX 3060 Driver to version 32.0.15.6109. Still no difference, the issue persists.

Hmmm! If I select the clips and 'Render in Place' it all plays back normally. Perhaps this is a workaround? Never had to do this previously.

However with consecutive clips there's a stutter when it transitions into the next clip, argh!

Posted: **Mon Sep 16, 2024 9:41 pm**

"transition to the next clip" you mean a transition effect? Because that would be normal for me for some more complex effects - Resolve should automatically cache that after the first pass.

Posted: **Mon Sep 16, 2024 9:52 pm**

The fact that "Render in Place" makes the issue better points to either an issue decoding the H.264 files, or a storage speed issue.

It appears your files are on drive F: which appears to be an NVMe drive, so it doesn't seem like it would be a storage issue.

My clip 4 playback slowdown issue on Friday is down to the GPU file decoding. As mentioned, I have a GTX1050Ti on a heavily loaded desktop system and the GPU file decoding, along with the color grade on clip 4 along with being a UHD timeline, was maxing out the GPU performance. Turning off the GPU file decoding made that issue go away.

I have an old 8 core Xeon 3.2GHz CPU. Your 8 core 11th gen CPU is much better than mine, and you likely don't have all the crap running on your system that I do. So it's baffling why your system would be struggling with the YT_1A project you provided.

If you disable Resolve Preferences - System - Decode Options: "Decode H.264/H.265 using hardware acceleration", and then restart Resolve, does that make the problem go away?

If you select the "Bypass Color Grades and Fusion Effects" icon, does that affect the issue?

If none of the above helps, send a screen shot of the Windows Task Manager Processes tab, showing all the Apps that are running. Make sure it's wide enough to show all the columns. Grab the screenshot while Windows is playing the timeline and the playback is not real time.

Posted: **Mon Sep 16, 2024 10:22 pm**

Dwaine Maggart wrote:
If you disable Resolve Preferences - System - Decode Options: "Decode H.264/H.265 using hardware acceleration", and then restart Resolve, does that make the problem go away?

If you select the "Bypass Color Grades and Fusion Effects" icon, does that affect the issue?

If none of the above helps, send a screen shot of the Windows Task Manager Processes tab, showing all the Apps that are running. Make sure it's wide enough to show all the columns. Grab the screenshot while Windows is playing the timeline and the playback is not real time.

Thanks Dwaine,
Task manager screenshot attached. Both of those options are disabled , so no the issue doesn't go away.

Posted: **Mon Sep 16, 2024 10:26 pm**

Try Uninstalling Avria. Windows Security is all you really need these days.

Posted: **Mon Sep 16, 2024 10:27 pm**

Jim Simon wrote:Try Uninstalling Avria. Windows Security is all you really need these days.

Thanks, I will. Although I've always had it there whilst using Resolve 18 with no issues.

Posted: **Mon Sep 16, 2024 10:34 pm**

pajamas55 wrote:
Jim Simon wrote:Try Uninstalling Avria. Windows Security is all you really need these days.

Thanks, I will. Although I've always had it there whilst using Resolve 18 with no issues.

I've just tried it with Avira disabled and there is some improvement. I'll try it more extensively in the morning. Thanks

Posted: **Mon Sep 16, 2024 10:37 pm**

Anyone having success with the latest DaVinci Resolve on the general release of macOS Sequoia 15.0 released today?

Posted: **Mon Sep 16, 2024 11:01 pm**

@Philip: Your screen shot shows it's playing back at locked 25 FPS. Was that varying while it was playing?

With the timeline playing (and hopefully the playback rate not at locked play speed) also send a screen shot of the Task Manager Performance tab showing the GPU activity.

I'm skeptical that Avira would make any difference, unless Jim has experience with that causing issues.

@Rick: This Windows issue focused thread seems like an odd place to ask about Sequoia?

Posted: **Mon Sep 16, 2024 11:09 pm**

pajamas55 wrote:Both of those options are disabled , so no the issue doesn't go away.

If "Bypass All Grades" was selected, it would look like the yellow square in this graphic. It was not selected in your screen cap, IOW grades were still on. It is vital to determine if this is a decoding issue or an effects issue. Bypassing All Grades is a good way to start.

Posted: **Tue Sep 17, 2024 12:41 am**

If "Bypass All Grades" was selected, it would look like the yellow square in this graphic. It was not selected in your screen cap, IOW grades were still on. It is vital to determine if this is a decoding issue or an effects issue. Bypassing All Grades is a good way to start.[/quote]

Many thanks for the tip! For me that worked. I installed DR 19 yesterday. Mainly to start using the Replay Editor (which requires DR19). It all worked fine until I did some grading in Color. It was on a project imported from 18.6 - working fine there and never had any issue with any component in DR. So, after hitting some grading buttons that whole page became slow as well as the viewer. Rendering did work but overall it did not feel good. Restarting the laptop did not help, neither using a proxy. Others have suggested upgrading the Nvidia GPU driver. My Nvidia seemed up to date (using an HP Fury G9, 32GB and RTX A4500 with 16GB...never an issue in previous versions).

By the way, just disabled the grading-bypass (so grading is on again) and DR still worked. This is no proof of course and I should test much more but hopefully this is an indicator for BMD in solving the underlying issue (It happens on many systems globally from what I read).

Posted: **Tue Sep 17, 2024 1:40 am**

Just finished my second of two features done on Resolve 19 on Mac OSX Sonoma 14.5. I had 2 crashes on the first feature (which was 8 solid days), but one of them was due to the internal cache drive suddenly unmounting itself; I could blame that on the OS or hardware. The other was a momentary slowdown/freeze; when I restarted, all was well.

The second feature (5 solid days), I had zero crashes, no issues, no problems with Resolve 19.0.1.

I'm about to make a bunch of plug-in changes (new DCTLs, new add-ons, updating Neat Video, updating Dehancer), so we'll see if anything changes tomorrow.

Posted: **Tue Sep 17, 2024 3:42 am**

Going out on a limb here, but try the following.

While in Resolve, open the task manager and manually end all "runtime broker" processes - keep the task manager open in the background and see if makes any difference.

And yeah, I know it sounds strange - I still don't really understand why it worked, when I had to troubleshoot a system a while ago that had a similar problem, but it somehow worked as a band aid.

Posted: **Tue Sep 17, 2024 6:58 am**

joema4 wrote:
Starfilm wrote:...This project just contains end-to-end rushes filmed with A7SIII. I tried unchecking the H.264/265 decoding option with hardware acceleration. After restarting the software, the playback worked perfectly for 10 seconds and then after "pausing" and restarting the playback everything went back to the way it was before...

I spent lots of time studying your case and trying to reproduce the problem. I finally determined your version of Resolve Studio 19.01 is somehow being forced to run under x86 Rosetta emulation. That will definitely cause performance problems.

The Resolve executable is a universal binary that contains both arm64 and x86_64 executables. On an Apple Silicon Mac, it always runs the arm64 version -- unless something forces it to run the x86 version under Rosetta emulation. For some reason, that has apparently happened on your machine.

This can be determined by examining the first line of the first debug file. It should say this:
Running DaVinci Resolve Studio v19.0.1.0006 (macOS/Clang arm64)

However on your machine it says this:
Running DaVinci Resolve Studio v19.0.1.0006 (macOS/Clang x86_64)

IMO you should NEVER run Resolve under Rosetta emulation on an Apple Silicon Mac.. Sometimes this happens because a plugin manufacturer (after four years!!) still has not made an Apple Silicon version of their plugin. They sometimes tell customers to just run Resolve under Rosetta, which enables it to use the prior x86 version of the plugin.

You can determine if this was done by using Finder's "Get Info" on DaVinci Resolve.app, and inspecting of the checkbox is set for "Open using Rosetta".

This can cause problems that later materialize, as this situation makes all too clear. Lots of time can be expended troubleshooting those, but the original person who made the Rosetta recommendation never faces the consequences of what they set in motion.

Do you have any idea why you were running Resolve Studio 19.01 on your M1 Max under Rosetta emulation?

I just disabled the opening with rosetta and miracle everything is back to normal. The playback is still jerky for the A7SIII shots in H.264 but for those in MXF everything works perfectly. On my other projects, I found complete fluidity! Starting Davinci and loading sequences is also much faster. I haven't tried exporting yet but I'm sure it will work as before.

I have absolutely no idea why Davinci started opening under Rosetta.

Joema thank you very much for your help it had economic consequences on my business!

Posted: **Tue Sep 17, 2024 8:45 am**

Frank Glencairn wrote:Going out on a limb here, but try the following.

While in Resolve, open the task manager and manually end all "runtime broker" processes - keep the task manager open in the background and see if makes any difference.

And yeah, I know it sounds strange - I still don't really understand why it worked, when I had to troubleshoot a system a while ago that had a similar problem, but it somehow worked as a band aid.

Thank you for your feedback but the problem seems to be solved. Are you talking about the finder task manager?

Posted: **Tue Sep 17, 2024 8:47 am**

Frank Glencairn wrote:Going out on a limb here, but try the following.

While in Resolve, open the task manager and manually end all "runtime broker" processes - keep the task manager open in the background and see if makes any difference.

And yeah, I know it sounds strange - I still don't really understand why it worked, when I had to troubleshoot a system a while ago that had a similar problem, but it somehow worked as a band aid.

Not sure about that

'Unfortunately, because RuntimeBroker.exe is highly important, it will automatically restart even if you terminate it. And even though it cannot be disabled permanently, you should refrain from even trying so since it is highly important for proper functioning of your Windows computer.'

Posted: **Tue Sep 17, 2024 11:34 am**

I'm also experiencing the unusable situation on my 2020 Intel i7 MacBook Pro with 32gb ram. Not the most modern machine, but my Davinci issues come up as soon as I load some clips in to a timeline. Monitoring the CPU and RAM usage isn't showing any lack of resources (both at around 10% all the time) even though my timeline completely freezes up and inputs hardly get registered and the UI updates only once every 8 to 10 seconds. I'm planning on using the system for instant replay, but this obviously requires a responsive setup. And by the sound of it, upgrading to a new Mac doesn't seem to be the solution since other people with M1's or M2's are having the same issues. I added my logs

Posted: **Tue Sep 17, 2024 1:14 pm**

Peter Robbemond wrote:I'm also experiencing the unusable situation on my 2020 Intel i7 MacBook Pro with 32gb ram....by the sound of it, upgrading to a new Mac doesn't seem to be the solution since other people with M1's or M2's are having the same issues. I added my logs

You have a 2020 13-inch 32GB MacBook Pro with a 10th-generation, 4-core i7-1068NG7 CPU.
It has no discrete GPU but only Intel Iris Plus Graphics, with 1.5 GB of VRAM.

I don't know if that meets the minimum equipment spec for Resolve 19. Maybe some BMD people could clarify?

Your logs are full of various errors. I suggest creating a new project, import a few clips, put them on a simple timeline and see if it can play those.

In troubleshooting cases like this, it's important to use a minimal config. If you're using a Decklink or any outboard audio hardware, temporarily disconnect that. Likewise, if you're using an external monitor, Bluetooth wireless audio, etc, temporarily discontinue that.

I have several M1 and M2 machines, and so far I've not seen any major problems unique to Resolve Studio 19. Some of the "Resolve 19" problems reported on Apple Silicon machines have clearly been unrelated, such as forcing Resolve to run under Rosetta emulation.

Posted: **Tue Sep 17, 2024 1:57 pm**

joema4 wrote:
Peter Robbemond wrote:I'm also experiencing the unusable situation on my 2020 Intel i7 MacBook Pro with 32gb ram....by the sound of it, upgrading to a new Mac doesn't seem to be the solution since other people with M1's or M2's are having the same issues. I added my logs

You have a 2020 13-inch 32GB MacBook Pro with a 10th-generation, 4-core i7-1068NG7 CPU.
It has no discrete GPU but only Intel Iris Plus Graphics, with 1.5 GB of VRAM.

I don't know if that meets the minimum equipment spec for Resolve 19. Maybe some BMD people could clarify?

Your logs are full of various errors. I suggest creating a new project, import a few clips, put them on a simple timeline and see if it can play those.

Yes, I'm aware. I've been meaning to update/upgrade my Macbook to an M-series chip. But it sounds even people with these chips are experiencing some issues. I'm testing out Davinci's new instant replay feature, and I'm testing it with a very minimal, barebones setup (just 1 camera feed). But this requires the Ultrastudio 4K mini to be connected. A friend of mine has a M1 Max MacBook Pro, which I hope to be able to test the same setup with.

Posted: **Tue Sep 17, 2024 2:00 pm**

Dwaine Maggart wrote:@Philip: Your screen shot shows it's playing back at locked 25 FPS. Was that varying while it was playing?

With the timeline playing (and hopefully the playback rate not at locked play speed) also send a screen shot of the Task Manager Performance tab showing the GPU activity.

I'm skeptical that Avira would make any difference, unless Jim has experience with that causing issues.

@Dwaine I took the decision to revert back to Resolve 18.6 and everything is playing as normal and using the Full camera clip versions.
So clearly it's not the Hardware. I'll maybe have to wait for a few updates to 19 before trying the upgrade again. Disappointing, but at least I can get on with the project.
Thanks for your help.

Posted: **Tue Sep 17, 2024 2:01 pm**

Ow, and by the way; for good measure I also purchased a Davinci Studio license to benefit from some hardware accelerated encoding, but I'm having the same issues in the paid version.

Posted: **Tue Sep 17, 2024 6:09 pm**

Peter Robbemond wrote:Ow, and by the way; for good measure I also purchased a Davinci Studio license to benefit from some hardware accelerated encoding, but I'm having the same issues in the paid version.

In general that's a good step -- regardless of whether it improves the current problem.

Was your workflow OK on Resolve 18.6x, but then became unusable on Resolve 19? Or are you trying something on Resolve 19 that you never used before?

Obviously, we want all the new features of Resolve 19 to work, but for purposes of troubleshooting, it helps to define what feature, codecs, interfaces, etc. the problem seems associated with. What was your experience on Resolve 18.6x, before upgrading to Resolve 19? Did you have performance or reliability problems then?

Did you ever run your same workload (no more, no less) from Resolve 18.6x on Resolve 19? What was your experience with that, before adding any new Resolve 19 features?

Your logs show you experienced many crashes of Resolve from 8-26-24 to 9-17-24. These were initially on Resolve 19.0.0.0069 but since Sept 10 on v19.0.1.0006.

Many of those stack traces involve various audio functions and Fairlight. Are you using any third-party audio plugins? If so, were those updated when you upgraded to Resolve 19? It's common for older plugins to cause problems when the OS or application is updated.

Posted: **Tue Sep 17, 2024 8:47 pm**

I never used Davinci before, because the replay functionality was introduced in v19, and I will primarily be using Davinci for this purpose. The replay functionality finally made me move away from FCPX (which always worked fine for me), so all is very new to me. In terms of codecs, I'm using whatever filetypes are created by the ATEM SDI Extreme ISO switcher. So, no plugins, no external tools, just a stock barebones install of Davinci 19. And yes, it has crashed many many times already, so, confidence wise, I'm very eager to see if a solution arises.

Posted: **Tue Sep 17, 2024 8:57 pm**

joema4 wrote:Many of those stack traces involve various audio functions and Fairlight.

Here's something very weird: I've been using Resolve 19 with no problems until today. I made a small adjustment in volume to a clip that uses Resolve's built-in reverb (I am using it only on this one short clip so didn't put the reverb on a bus; I added the effect directly to the clip), and after I adjusted the clip volume I started seeing some of the same weirdness described above: playback would slow to a crawl and then suddenly speed up to double or triple speed. I shut down Resolve and restarted, shut down my computer (M2 Mac) and restarted, to no avail.

And then I went back to that clip and adjusted the volume back to where it was and now everything is back to normal, playback is perfectly smooth.

Posted: **Wed Sep 18, 2024 5:28 pm**

tons of playback glitches on Davinci Resolve where it'll hang in one spot and the only solution is to reboot DR (it doesn't close or crash, but the audio continues but the video gets stuck and the color scopes also get stuck), and mostly will have issues when color grading. I don't have big files, 1080p stuff and the project settings match the source clip and all.

I'm on a macbook pro m2 16gb, but I'm upgrading to a M2 Max 32gb.

I also don't know if I have a lemon of a laptop (which is why I'm returning and chose to upgrade at the same time) but Premiere Pro never had issues with the projects I've worked on which aren't complex by any means, 1080p footage h.264 footage on my previous Macbook Pro M2 16gb but this current one I have has had issues that are similar related to playback glitches in both PP & DR. Hoping the new laptop (refurbished M2 Max 32gb) will not have issues in either.

I've also tried proxies and use ProRes codecs, no difference.

If my issues in DR continue, I will have to stay with PP. Was considering buying a license for DR but seems some folks still have issues on 19.0, 19.0.1 with M chips too

Posted: **Thu Sep 19, 2024 5:16 pm**

BimblingAbout wrote:Since upgrading to Davinci Resolve 19.01 I am experiencing the following:

3) Rendering ready for upload to YouTube now runs a 2 frames a second, resulting in an estimated 17hr render for a 24 minute 4K project.

Are you using any side chains in Fairlight?

Posted: **Mon Sep 23, 2024 5:36 pm**

BimblingAbout wrote:Since upgrading to Davinci Resolve 19.01 I am experiencing the following:

1) constant memory leaks until the application crashes, the system monitor shows the memory usage growing from 5GB to 76GB, even after generating proxies.

2) Media offline messages (the project is stored on a Samsung T7 SSD)

3) Rendering ready for upload to YouTube now runs a 2 frames a second, resulting in an estimated 17hr render for a 24 minute 4K project.

My system is a M2 MacBook Pro, 16gb ram, macOS Sonoma 14.6.1

Any suggestions before I throw in the towel and revert back to 18.06

Following this, I think it might be Sonoma 14.6.1, I had tons of issues on my m2 macbook pro 16gb after upgrading to Sonoma 14.6.1 on Premiere Pro, I installed DR and tested it out only after upgrading the OS and I had similar playback glitches so I feel the OS wasn't optimizing something properly

Posted: **Tue Sep 24, 2024 10:53 am**

Interesting, I'm also on 14.6.1...

Apparently, 14.7 is also out. I wasn't aware, so I'll update and see if that improves anything.

Posted: **Sat Sep 28, 2024 12:39 pm**

Upgrading to 14.7 made me lose control of my Ultrastudio 4k Mini and my Ultrastudio Mini Recorder 3G (in Desktop Video). Tried downgrading, but no luck. Upgraded tot MacOS 15.0 but still nothing. It works fine on a friends M1 Max MacBook Pro weirdly enough.

As for Davinci, even on the M1 Max it’s still sluggish sometimes, and occasionally hangs/freezes when doing the instant replay stuff, although it did run a little better than on my intel macbook (but not by much).

I’m doing a boxing match today with the instant replay features so I hope it won’t crash or hang today :cry:

Posted: **Tue Nov 12, 2024 3:26 am**

I am having this issue as well, PC user, updated to 19.1 and now I can't accomplish anything without a crash.

I'm new to the forum, and trying to figure out how to share the necessary info to get help-

I've got the logs here https://drive.google.com/file/d/1PAz-d0 ... drive_link

But when I try to accomplish this step "Open Windows System Information, and from the menubar, select File > Save (Not a File Export) to generate a .NFO file and save it to your desktop." -I cannot find any menubar and can't complete the task. I'm using the start menu, and going into Settings. If there's some other way to "Open Windows System Information", I'm not seeing it.
This is a screenshot of my System Info https://drive.google.com/file/d/1B1Yo9l ... drive_link

Anyone who can help, I'd greatly appreciate the guidance

Posted: **Tue Nov 12, 2024 11:37 pm**

This System Information:

: windows_system_information.png (36.55 KiB) Viewed 2440 times

Posted: **Tue Nov 12, 2024 11:59 pm**

Minimum supported NVIDIA GPU driver is 550.58. You currently have 536.23 installed.

Download and install the current 566.14 Game Ready driver for your GTX960 GPU.

For those who expected me to suggest the Studio driver, there are no Studio drivers for GTX9xx GPUs.

When you run the driver installer, select the Custom install option, then the Clean Install option.

Posted: **Thu Nov 14, 2024 8:41 pm**

Thanks Dwaine!

I installed the new drivers, but still ran into the same crash issue.

Using your help I got the NFO file
https://drive.google.com/file/d/1PBZ5dE ... sp=sharing

Let me know what you think I should try next!

Posted: **Thu Nov 14, 2024 10:27 pm**

Another major issue in the logs is that you have the default cache/stills path set to drive F:

Your NFO doesn't show a drive F:.

And this is causing lots of issues trying to write things to the missing drive F:

Are you able to run Resolve at all? If Resolve starts and gets the Project Manager window, do a <CTRL><,> (that's a comma) which opens the Resolve Preferences window. It will be sitting on the Media Storage area, and the F: path will be at the top of the list. Use the Remove button to remove it and add a path that actually exists on your system. The normal default would be (for your system):

C:\Users\Sean Youngman\Videos

Since you have almost 4TB free on the C: drive, that's the path I would recommend you use.

Let me know if Resolve won't open that far and I'll provide a different suggestion.

If you are able to do the above, but still have issues with Resolve running properly, send another Resolve diagnostics log.

Posted: **Thu Nov 14, 2024 11:51 pm**

Okay I fixed the cache to the C drive, still crashing though, here's the logs

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

Posted: **Fri Nov 15, 2024 6:49 pm**

Please send a project export .drp of this project: "Untitled Project 2024-11-14_183031"

Open the Project Manager window, right click that project and select Export Project

Also send a current Windows System Information .NFO file.

Posted: **Fri Nov 15, 2024 10:08 pm**

the system info
https://drive.google.com/file/d/1Emt7np ... sp=sharing

& the project info
https://drive.google.com/file/d/1paqmid ... sp=sharing

Posted: **Sat Nov 16, 2024 6:18 am**

Hmmm. There is nothing going on in that project.

The NFO shows the Resolve crash was NVIDIA driver related. Maybe the current driver sucks on 900 series GPUs.

Try the 560.70 driver and see if that makes any difference.

Posted: **Tue Nov 19, 2024 4:34 am**

Ah man no luck.

Here's my newest info and reports. I tried redoing the project because I thought maybe using the old projects would be problematic, but it crashes no matter what as soon as i hit Render.

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

system info
https://drive.google.com/file/d/1bHNJaX ... sp=sharing

Posted: **Tue Nov 19, 2024 9:12 am**

Your NFO still shows the NVIDIA driver is the issue.

So, use the DDU app to uninstall the NVIDIA driver. Then re-run the NVIDIA driver installer of your choice. Might as well try the current driver again, after running DDU.

This is a forum thread where I describe how to get and use the DDU app. This thread was for uninstalling an Intel driver. Same process, just select NVIDIA instead of Intel:

viewtopic.php?f=21&t=119852&hilit=%2Bddu#p659861

Posted: **Tue Nov 19, 2024 6:37 pm**

ahhh no luck again, did the DDU, installed the newest Nvidia (this time i didn't bother with GEForce because I'm not using this PC for gaming) and still the same crash when I hit Render

system info
https://drive.google.com/file/d/1Qp2uCN ... sp=sharing

project file
https://drive.google.com/file/d/1LXr2TD ... drive_link

Posted: **Tue Nov 19, 2024 7:01 pm**

Please send a Resolve diagnostics log as well.

Posted: **Tue Nov 19, 2024 7:08 pm**

Here!
https://drive.google.com/file/d/17AkNZd ... sp=sharing

Posted: **Tue Nov 19, 2024 7:12 pm**

Also, something you can try, if you haven't already:

Since rendering is causing the crash, and you are rendering H.264, on the Deliver page, put the Encoder setting to Native. That will render H.264 using the CPU instead of the GPU. Perhaps the GTX960 GPU isn't liking doing the H.264 encoding for some reason.

Posted: **Wed Nov 20, 2024 2:00 am**

Try to update to 14.7.1, delete DR and make a fresh install of 19.1. Any better?

What Dwaine suggests should help, that's a pretty old GPU. You could also export a master file in ProRes 422 and do the final encoding in HandBrake.

Posted: **Wed Nov 20, 2024 5:20 am**

I tried Native, it seemed to try for a few seconds longer than usual but still crashed
https://drive.google.com/file/d/1vJRUV_ ... drive_link

Uli, what program are you suggesting I update to 14.7.1?

Blackmagic Forum

Resolve 19.01 Unusable

Re: Resolve 19.01 Unusable

Re: Resolve 19.01 Unusable

Re: Resolve 19.01 Unusable

Re: Resolve 19.01 Unusable

Re: Resolve 19.01 Unusable

Re: Resolve 19.01 Unusable

Re: Resolve 19.01 Unusable

Re: Resolve 19.01 Unusable

Re: Resolve 19.01 Unusable

Re: Resolve 19.01 Unusable

Re: Resolve 19.01 Unusable

Resolve 19.01 Unusable

Re: Resolve 19.01 Unusable

Re: Resolve 19.01 Unusable

Re: Resolve 19.01 Unusable

Re: Resolve 19.01 Unusable

Re: Resolve 19.01 Unusable

Re: Resolve 19.01 Unusable

Re: Resolve 19.01 Unusable

Re: Resolve 19.01 Unusable

Re: Resolve 19.01 Unusable

Re: Resolve 19.01 Unusable

Re: Resolve 19.01 Unusable

Re: Resolve 19.01 Unusable

Re: Resolve 19.01 Unusable

Re: Resolve 19.01 Unusable

Re: Resolve 19.01 Unusable

Re: Resolve 19.01 Unusable

Re: Resolve 19.01 Unusable

Re: Resolve 19.01 Unusable

Re: Resolve 19.01 Unusable

Re: Resolve 19.01 Unusable

Re: Resolve 19.01 Unusable

Re: Resolve 19.01 Unusable

Re: Resolve 19.01 Unusable

Re: Resolve 19.01 Unusable

Re: Resolve 19.01 Unusable

Re: Resolve 19.01 Unusable

Re: Resolve 19.01 Unusable

Re: Resolve 19.01 Unusable

Re: Resolve 19.01 Unusable

Re: Resolve 19.01 Unusable

Re: Resolve 19.01 Unusable

Re: Resolve 19.01 Unusable

Re: Resolve 19.01 Unusable

Re: Resolve 19.01 Unusable

Re: Resolve 19.01 Unusable

Re: Resolve 19.01 Unusable

Re: Resolve 19.01 Unusable

Re: Resolve 19.01 Unusable