Mac Mini crashing on sleep

Update: it appears that even when the computer does not sleep, it panics/crashes if I have "put hard drives to sleep" checked.

(also updated one of the other similar threads and sent a note to the Macrumors guys)

Definitely on to something here with Safari. I admittedly hadn't been good at tracking updates and when things went bad. That being said, I stopped using Safari yesterday and am using MS Edge (Chromium) now. Have not started it at all since the last reboot and Sleep for the last 24 hours seems to be better.

I uninstalled Bitdefender 2020 in thoughts that was the issue. Going to try this for another 24 hours. If things seem to stabilize, I'll reinstall Bitdefender and see how that goes.

There's only one "Solved" result on the discussions of this problem.

It is here; https://discussions.apple.com/thread/251168481

And Apple replaced his motherboard. It's clear they know what caused it, and that it would be a very expensive fix for them to replace ALL of the damaged motherboards. Perhaps they hope that AppleCare will run out for many of the Macs that were damaged by the security update - or that over time they may find a T-2 chip firmware fix to undo the previous buggy firmware update. Time will tell.

POSTSCRIPT: I've been using Apple computers since the Apple ][ and I've received a number of invitations to join various class action lawsuits over that time. If they don't address this issue SOON, I expect I'll be invited to join another.

So far, my machine have run without any issue for 5days.

MagicQs-MacMini:~ MagicQ$ uptime

10:27 up 5 days, 1 hr, 4 users, load averages: 1.70 1.79 1.79

What I had done:

1. Apple replaced my motherboard, and that issue occurred once after restore all data from timeMachine.

{"caused_by":"bridgeos","macos_version":"Mac OS X 10.14.6 (18G103)","os_version":"Bridge OS 4.5 (17P5290)","macos_system_state":"sleep","incident_id":"0D2F7D05-3AE4-4653-9B88-EA3EB8068580","timestamp":"2020-05-28 18:11:28.00 +0000","bug_type":"210"}

Note, the T2-Chip's firmware version is 17P5290, that's being said, replace motherboard is not useful for me, and the issue might caused by software itself.

2 Install security update 2020-003, sounds good now.

Someone had posted that update 2020-003 doesn't make sense, so i doubt security 2020-002 made some hard hurt on the machine, mostly the T2-Chip.

Let me report on the condition of my machine,

1. Whether using Safari does not mean whether the machine will crash

2. After replacing the motherboard, does the frequency appear to be reduced, but the problem still exists

3. The frequency is reduced again after installing the latest security update 2020-003 after crashing for 1 day after replacing the motherboard, but crashing again after 6 days of operation

I have sent the latest crash report to Apple and the error message is still -20.

{"caused_by":"bridgeos","macos_version":"Mac OS X 10.14.6 (18G5033)","os_version":"Bridge OS 4.5 (17P5290)","macos_system_state":"sleep","incident_id":"099DCEB1-7CD7-4271-B651-880C172C4757","timestamp":"2020-06-04 11:48:38.00 +0000","bug_type":"210"}

"panicString" : "panic(cpu 0 caller 0xfffffff0122a41e4): SEP Panic: :SEPD\/MDMA: 0x000147df 0x000094ff 0x0000ed79 0x0001273d 0x0001301d 0x000138eb 0x00013ac3 0x00000000 [hkntv]\n\nPanic app vers: 1267.120.4\nPanic app UUID: 71A98C38-886E-37FD-8017-CBD4D067CCA7\nRoot task tag: AppleSEPOS-1267.120.4\nRoot task vers: AppleSEPOS-1267.120.4\nRoot task UUID: 6D0D6C62-D79A-3326-9F47-807CCDF72F76\n\nFirmware type: UNKNOWN SEPOS\nSEP state: 9\nPM state: 2\nBoot state: 32\nMailbox status:\nIDLE_STATUS: 0x00000068\nMAILBOX_SET: 0x00000110\nMAILBOX_CLR: 0x00000110\nINBOX_CTRL: 0x0002bb01\nOUTBOX_CTRL: 0x00028801\n\nMailbox entries:\nUnavailable\nMailbox queue pointers: 6\/6 0\/0 -1\/-1 -1\/-1 -1\/-1 -1\/-1 -1\/-1 -1\/-1 -1\/-1 -1\/-1 8\/8 -1\/-1 0\/0 -1\/-1 -1\/-1 -1\/-1 3\/3 -1\/-1 22\/22 3\/3 -1\/-1 -1\/-1 -1\/-1 -1\/-1 -1\/-1 -1\/-1 -1\/-1 -1\/-1 -1\/-1 -1\/-1 -1\/-1 -1\/-1\nDebugger message: panic\nMemory ID: 0xff\nOS version: 17P5290\nmacOS version: 18G5033\nKernel version: Darwin Kernel Version 19.5.0: Thu Apr 30 23:53:45 PDT 2020; root:xnu-6153.120.31~33\/RELEASE_ARM64_T8010\nKernel UUID: 1CB01607-F239-3FE9-833E-F72D62835EF6\niBoot version: iBoot-5540.125.4\nsecure boot?: YES\nx86 EFI Boot State: 0xe\nx86 System State: 0x1\nx86 Power State: 0x2\nx86 Shutdown Cause: 0x5\nx86 Previous Power Transitions: 0x200020002\nPCIeUp link state: not available\nPaniclog version: 13\nKernel slide: 0x000000000a13c000\nKernel text base: 0xfffffff011140000\nmach_absolute_time: 0x69139d9a95f\nEpoch Time: sec usec\n Boot : 0x5ecffec0 0x000a1501\n Sleep : 0x5ed83577 0x000a3b38\n Wake : 0x5ed8357f 0x000923e4\n Calendar: 0x5ed8df82 0x000e969b\n\nPanicked task 0xffffffe0007f7600: 2447 pages, 162 threads: pid 0: kernel_task\nPanicked thread: 0xffffffe00124d520, backtrace: 0xffffffe011763600, tid: 93765\n\t\t lr: 0xfffffff011990878 fp: 0xffffffe011763640\n\t\t lr: 0xfffffff0119906d4 fp: 0xffffffe0117636b0\n\t\t lr: 0xfffffff011aab350 fp: 0xffffffe011763760\n\t\t lr: 0xfffffff011f5962c fp: 0xffffffe011763770\n\t\t lr: 0xfffffff01199003c fp: 0xffffffe011763ae0\n\t\t lr: 0xfffffff011990394 fp: 0xffffffe011763b30\n\t\t lr: 0xfffffff0126da8f8 fp: 0xffffffe011763b50\n\t\t lr: 0xfffffff0122a41e4 fp: 0xffffffe011763b80\n\t\t lr: 0xfffffff012299660 fp: 0xffffffe011763ba0\n\t\t lr: 0xfffffff011ecd0a8 fp: 0xffffffe011763bd0\n\t\t lr: 0xfffffff0119d3964 fp: 0xffffffe011763bf0\n\t\t lr: 0xfffffff0119d356c fp: 0xffffffe011763c90\n\t\t lr: 0xfffffff011f64514 fp: 0x0000000000000000\n\n",

I see a very important piece of information in the first words of the Problem Report; "caused_by":"bridgeos"

From a Cult of Mac article;

"The reference to Bridge OS would seem to indicate that the problem lies somewhere in the Apple T2 chip. This co-processor does so many jobs it has its own operating system separate from macOS. This is called (you guessed it) Bridge OS.

The T2 with Bridge OS is the disk controller for the hard drive, it adds intelligence to the FaceTime Camera, includes a secure enclave, and even oversees the macOS boot up process."

Have you tried that? Create a Catalina boot drive somewhere (which I assume updates the Mac Mini T2 chip in the process) and then go back to using the normal Mojave boot drive.

I certainly have some spare external HDDs around to try that.

[I shut down every night and the MM is scheduled to restart every morning. I can hear the startup chime. The crash at restart notice comes up each time but I swear I have never heard a second startup chime. Not sure what exactly is "restarting".]

@mavots

From various threads around this topic I know of at least 2 users who upgraded their Mac mini to Catalina to no avail.

(They also had the hope that the upgraded T2 firmware, aka BridgeOS, would finally solve their problems).

Another point: as BridgeOS for Catalina has a different build number than the Mojave build, I wouldn’t necessarily assume that they would perfectly work together. (But I admit that this is a personal assumption, I do not have enough knowledge about how close the relation between macOS and BridgeOS is).

If you look at the timestamp from you Kernel Panic Log files, you will most likely see that the BridgeOS crash happens at the moment when you shut down the Mac (or send it to sleep).

At least, that is what I’m observing here (where I have the exact same issues: BridgeOS crash on shut down and sleep {when Safari was launched beforehand}, macOS crashes when disconnecting the eGPU via top menu bar command).

Another point: did you run some hack to reactivate the Mac's startup chime? (As usually all newer Macs boot up in silence).

Yes, you're right.

From what I've fetched during the last couple of weeks, the Security Update 2020-002 updated the BootROM for some older Macs. It seems that some of these machines now come up with similar troubles than the T2 minis and iMac Pros.

I supected a relation to SMC in general because most problems seem somewhat related to power management. But as I'm getting macOS crashes since then when I disconnect the eGPU by the top bar menu command, there might also be some troubles introduced with 2020-002 by the changes for the USB/Thunderbolt Busses.

I filed this bug August 5, and updated it a number crashes with a new sysdiagnose.  Still: "Recent Similar Reports:None"

The sysdiagnose however is quite a large file, 140M, I'm getting a bit fe(e)d up with it without any feedback (ha!) from Apple..

Give it a go, make yourselves heard, file a bug at https://feedbackassistant.apple.com/.

And add a reference to this discussion? https://discussions.apple.com/thread/251226783

Try a clean install on an external disk.

Seems your MBP doesn't have T2-Chip, maybe the crash was caused by Safari itself. Have you upgrade Safari to 13.1.1 ?

Try to install security 2020-003 on your MINI , seems it works on my side.

It update the software, the old one was something like Boot ROM Version: 1037.120.87.0.0 (iBridge: 17.16.15290.0.0,0)

I let mine install Catalina, which it wanted to do for a while, and now it stopped crashing.

I know people don’t want to do that because of apps they like, but it didn’t matter to me.