DR 19.1.4 Studio crashes when wifi is enabled - help?

After doing some software updates (Nvidia, bios and networking) DR started crashing on startup. I’d had similar issues when updating to the “latest nvidia driver” in the past so immediately went back to the last known-good driver from Lenovo. Worked for a bit but then DR started crashing on startup again.

That’s when I went through the debug trail that led me to turning off networking and I found that every time I did so, DR stopped crashing on startup.

More digging and I found some recommendations saying to uninstall any plugins. I am on the Boris beta and had beta versions of Continuum and Sapphire installed. Removed those and things seemed better for a bit and then went back to crashing on startup again.

Thing is, this happens before the DR splash screen appears and the DR logs don’t show anything that I can interpret.

I have noticed that when this happens, if I’ve got task manager open, I can see three instances of resolve.exe in the task list. I don’t see more than one in the cases where networking is off.

OS Name Microsoft Windows 11 Pro
Version 10.0.26100 Build 26100
System Manufacturer LENOVO
System Type x64-based PC
System SKU LENOVO_MT_83DN_BU_idea_FM_Yoga Pro 9 16IMH9
Processor Intel(R) Core™ Ultra 9 185H, 2300 Mhz, 16 Core(s), 22 Logical Processor(s)
BIOS Version/Date LENOVO NKCN31WW, 3/4/2025
Installed Physical Memory (RAM) 32.0 GB
Name Intel(R) Arc™ Graphics
Adapter RAM 2.00 GB (2,147,479,552 bytes)
Driver Version 32.0.101.5763
Name NVIDIA GeForce RTX 4050 Laptop GPU
Adapter RAM 6G
Driver Version 32.0.15.7602
michaelh
7h

[time passes. I actually posted this first on the Boris forum thinking this was a plugin issue.]

Rolled back the wifi driver to the previous version. Crashing stopped.

Re-installed Sapphire. Still couldn’t get the crashing to happen.

Updated the driver again and verified that the latest version was being used. Still no crashes.

But after leaving my computer for an hour with DR shut down, it crashed when I tried to start DR.

I’ve cleaned off anything network related that’s not critical (vpn, nmap, wireshark, etc) and I'm still seeing startup crashes that go away completely when I turn off wifi.

I'm now starting to wonder, based on the latest logs, if this is a problem connecting to the project server on another machine. Doing some targeted testing with DR only running local project and will update with whatever I find.

Logs are in https://drive.google.com/drive/folders/ ... sp=sharing

Ok, I was able to start and restart DR at least a dozen times without crashes when I switch to loading local projects with wifi turned on.

After going away from the computer for 45 minutes I came back, woke it up and DR crashed before the splash screen.

I turned off wifi and it still crashed on startup. Twice.

Updated logs through the link above.

[edit...]
I am seeing Faulting application name: Resolve.exe, version: 19.1.4.11, time stamp: 0x00000000
Faulting module name: ucrtbase.dll, version: 10.0.26100.3624, time stamp: 0x45295404
in the windows event logs

Now searching to see if any of the solutions related to that might help

see here: viewtopic.php?f=21&t=90190

"Posting on the forum / Contacting Support for DaVinci Resolve and DaVinci Resolve Studio" etc...

good luck!

Which part of that section are you trying to indicate that I haven't included?

As it stands I've done clean installations of the C runtime libs and a clean (ddu) reinstall of the last known good Nvidia driver. Still crashes on startup (all DR logs through the link at the bottom of the OP)

I've also tried an uninstall and reinstall of DR. No change.

Windows Event logs consistently show:

Faulting application name: Resolve.exe, version: 19.1.4.11, time stamp: 0x00000000
Faulting module name: ucrtbase.dll, version: 10.0.26100.3912, time stamp: 0xbd96a17b
Exception code: 0xc0000409
Fault offset: 0x00000000000a4ace
Faulting process id: 0x7534
Faulting application start time: 0x1DBBDB211DE00F0
Faulting application path: C:\Program Files\Blackmagic Design\DaVinci Resolve\Resolve.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: 237d1519-6816-4575-ae31-47c7e7cf8ee3
Faulting package full name:
Faulting package-relative application ID:

[Dwaine Maggart]

The crash logs sort of indicate that it's hanging at startup, and you are force quitting Resolve. Is that the case, or it's just immediately crashing to the desktop at startup?

Having a System Information .NFO file is always helpful.

Also, please make sure there is not a Resolve.exe process already running when you start Resolve. Do that by opening Task Manager, and selecting the Details area (not the Processes area) and look for a Resolve.exe process. If there is one, kill it before attempting to launch Resolve.

Thanks Dwaine.

It very rarely hangs at startup and in all the cases I was chasing this time, when it crashes it's before the splash screen and I would get the DR crash dialog. 9/10 times I sent in a report.

Because of all this crash chasing, I've habitually run task manager so I can watch DR start up. I haven't seen any cases of lingering resolve.exe instances.

I'll try to remember to include the nfo file next time. I can upload one this time if anyone's likely to want to look at the issue further.

I've got my fingers crossed...

This morning I spent the time to uninstall everything in the system add/remove dialog that had Intel in the name. I know in the past sometimes they don't clean up well when things are upgraded. This included the latest graphics driver.

In the last case I had problems uninstalling the driver. It kept wanting me to find an exe that wasn't on my system.

So I followed up by running DDU on the Intel gfx subsytem and reinstalling the latest whql driver.

So far... I've had no DR startup crashes and I've been alternating between closing DR or leaving it open when I walk away from my machine.

Now that I've put that in writing I expect a crash. Yes, I'm a pessimist. But I'm an optimistic pessimist that hopes for the best.

I'll update this if I've not seen any crashes in the next day or so, or earlier if I do.