Crash on Mac SOS

I've been waiting for tech support to return a call since 8A on Friday when I sent my logs. Support ticket #XYM-424-39057.

DR is crashing on startup with a meaty project, crashing 1-5 minutes after running. All projects crash, so I don't think it's a corrupt project.

I'm on a Mac Pro (late 2013), Processor is 2.7 GHz 12-core Intel Xeon E6, Memory: 64GB 1866MHz DDR3, Graphics: AMD FirePro D700 6GB

Events leading to crashes:
I was working on DR version 17.3 with Mojave Mac OS.
My computer crashed while working in another app with DR running in the BG.
Restarted my computer went into DR and the crashes began.
Update computer to Monterey 12.6
Updated DR to 18.03
Crashes continue.
Properly uninstalled DR, reinstalled 18.3, crashes continue.

Is there anyone here that can help?

[Peter Chamberlain]

Did you backup your v17.3 database before upgrading to v18?

Can you launch resolve and from the help menu generate diagnostic logs.
Then post a link here to them

Thank you Peter.
I did not back up the v17.3 database through DR but did do a time machine back up on the mac so I could revert.

Here's a link to the logs. https://drive.google.com/drive/folders/ ... sp=sharing

Thanks so much.

Im afraid that other app damaged some of your file structure when crashing. Are you using HFS+ or APFS for the system drive? If it's HFS+ you could try to fix it with Disk Warrior. If APFS, try a fresh install of the system without deleting the data area.

Im afraid that other app damaged some of your file structure when crashing. Are you using HFS+ or APFS for the system drive? If it's HFS+ you could try to fix it with Disk Warrior. If APFS, try a fresh install of the system without deleting the data area.

HFS+ is no longer possible as systemdevice since mojave (macOS 10.14).
APFS is therefore a must for newer systems :- (

No, I think HFS+ could have been a choice at installation time, for example if your OS was still HFS+ when you installed Mojave meaning you may have kept Mojave on HFS+). APFS+ obligation came on subsequent OS versions...
Anyway this is no longer your worries, obviously. Personally I'd install a fresh OS on an external disk and boot on it for tests purposes...

No, I think HFS+ could have been a choice at installation time, for example if your OS was still HFS+ when you installed Mojave meaning you may have kept Mojave on HFS+). APFS+ obligation came on subsequent OS versions...
Anyway this is no longer your worries, obviously. Personally I'd install a fresh OS on an external disk and boot on it for tests purposes...

when installing or updating to mojave, HFS+ is automatically converted to APFS.
which is the worst method, because the FSroot tree is damaged, which even the apple disk utility
can not repair (not even in recovery mode).
with mojave you could keep the HFS+ format by restoring a clone, but after that no updates worked.

since catalina this does not work anymore.

has unfortunately nothing to do with the problem of the TS, because with his configuration
the startupdevice is on APFS anyway.

I would in his place once the eltrecheck software check whether a conflict with extensions is present.

when installing or updating to mojave, HFS+ is automatically converted to APFS.

Ok, didn't notice that because either I manage some old friends' old macs up to say high Sierra, or I'm into Big Sur or Monterey
My strategy would be to investigate for a potential HW issue by booting on a known rock solid OS with Resolve on it, then push further...

Second that. Put a clean system on an external storage, add only DR and see if it works.
Being a relatively old computer, it can be a hardware issue. Are you sure about the cooling?
There may be dust collected or a bad fan. TG Pro can show you thermal issues, it's free for a few days.