Mac mini freezing start up loop

[AlanMacInnes]

I bought a factory-sealed 2018 Mac Mini, and after a week, it started freezing. The monitor would display tiny red or green lines all over the screen, and if there was video playing, it would loop. The computer would restart on its own, sometimes with a dialogue box saying there was a problem and a report option, then crash again after a minute or two, sometimes longer. Other World Computing, where I bought the computer, said they couldn't find anything as it ran fine. The report** is below if anyone can decipher it. If the computer doesn't restart on its own, I'll push the power button; the light comes on, I hear a whoosh sound from the exhaust vent in the back, and then the light goes out. This will happen continuously. So it seems like it's trying to start up but can't. I also noticed that the computer gets warm. I've been using it now for about an hour, and it's cold. I've been using it today for about 3 hours. I'm expecting it to crash any minute, but oddly, the other day it ran for at least 5 hours without a problem. They suggested it could be other factors, not the computer, that are causing the problem, but what could that be? There's just the monitor and the speakers; it can't be a peripheral, could it? Does anybody know what the problem is? Can I have it repaired? Thank you for your consideration. Al

Spoiler: Crash log

* Macmini
Processor: 3.2 GHz 6-Core Intel Core i7
Graphics: Intel UHD Graphics 630 1536 MB
Memory 64 GB 2667 MHz DDR4
Serial number
macOS Ventura 13.3.1 (a)

**REPORT
panic(EFI): Exception 3 occurred: Breakpoint

B779-4383-93E9-0C7F9416A6DA
#[PEI|D] 012 2FAC2694-400C-480C-844F-4EC474DD3A2B #[PEI|D] 013 3FB1A55F-DDEF-42D9-8FAF-891039769F8D #[PEI|D] 014 A1F39391-B841-4C3E-A458-71E312DD6CB9 #[PEI|D] 015 EEEE611D-F78F-4FB9-B868-55907F169280 #[BTPU]
#[RS3M] P 65500000 180000 FF7000000
#[PEI|D] 016 A8499E65-A6F6-48B0-96DB-45C266030D83 #[0x80] 0x0000dd00
#[0x80] 0x0000dd1b
#[0x80] 0x0000dd1c
#[0x80] 0x0000dd1e
#[0x80] 0x0000dd21
#[0x80] 0x0000dd22
#[0x80] 0x0000dd23
#[0x80] 0x0000dd24
#[0x80] 0x0000dd27
#[0x80] 0x0000dd5e
#[0x80] 0x0000dd43
#[0x80] 0x0000dd26
#[0x80] 0x0000dd71
#[0x80] 0x0000dd72
#[0x80] 0x0000dd5c
#[0x80] 0x0000dd61
#[0x80] 0x0000dd60
#[0x80] 0x0000dd5d
#[0x80] 0x000000d5

Exception 3 occurred: Breakpoint ================================================================== ====
CS = 0x0010 EIP = 0xffe97c88 EC = 0x00000000
EFL = 0x00000046 id vip vif ac vm rf nt o d i t s Z a P c
EAX = 0x00000001 DR0 = 0x00000000 CR0 = 0x00000013 DS = 0x0018
EBX = 0xff7f7813 DR1 = 0x00000000 CR1 = 0x00000000 ES = 0x0018
ECX = 0x00000001 DR2 = 0x00000000 CR2 = 0x00000000 FS = 0x0018
EDX = 0x00000001 DR3 = 0x00000080 CR3 = 0x00000000 GS = 0x0018
ESI = 0x000000d5 DR6 = 0xfffe0ff0 CR4 = 0x00040608 SS = 0x0018
EDI = 0x00000000 DR7 = 0x200004c0
EBP = 0xff7f7820
ESP = 0xff7f7808
IDT = 0xff7ffdfb/0x010f
GDT = 0xffffd598/0x003f

011 649760C0-

================================================================== ====
0xff7f7820: 0xffe97c88 9ad98eb1-68ef-3f32-a983-6e9f55c19aab

EEEE611D-F78F-4FB9-B868-55907F169280 0xffe91000+0xe00006c88 0xff7fddb0: 0xffeb6c05 73602d9a-0e03-39ee-b619-5be2876edeac
A8499E65-A6F6-48B0-96DB-45C266030D83 0xffea4000+0xe00012c05 0xff7fddf0: 0xffe65c41 66efddf7-633c-31d9-86ca-9391e39c4181
52C05B14-0B98-496c-BC3B-04B50211D680 0xffe65000+0xe00000c41 0xff7fde30: 0xffe65ee4 66efddf7-633c-31d9-86ca-9391e39c4181
52C05B14-0B98-496c-BC3B-04B50211D680 0xffe65000+0xe00000ee4 0xff7fde40: 0xffe65f09 66efddf7-633c-31d9-86ca-9391e39c4181
52C05B14-0B98-496c-BC3B-04B50211D680 0xffe65000+0xe00000f09 0xff7fdee0: 0xffea5c50 73602d9a-0e03-39ee-b619-5be2876edeac
A8499E65-A6F6-48B0-96DB-45C266030D83 0xffea4000+0xe00001c50 0xff7fdf20: 0xffe65c41 66efddf7-633c-31d9-86ca-9391e39c4181
52C05B14-0B98-496c-BC3B-04B50211D680 0xffe65000+0xe00000c41 0xff7fdf50: 0xffe65f3a 66efddf7-633c-31d9-86ca-9391e39c4181
52C05B14-0B98-496c-BC3B-04B50211D680 0xffe65000+0xe00000f3a 0xff7fe2f0: 0xffe66e50 66efddf7-633c-31d9-86ca-9391e39c4181
52C05B14-0B98-496c-BC3B-04B50211D680 0xffe65000+0xe00001e50 0xff7fe310: 0xffe6a7bb 66efddf7-633c-31d9-86ca-9391e39c4181
52C05B14-0B98-496c-BC3B-04B50211D680 0xffe65000+0xe000057bb 0xff7fe330: 0xffe7210f 66efddf7-633c-31d9-86ca-9391e39c4181
52C05B14-0B98-496c-BC3B-04B50211D680 0xffe65000+0xe0000d10f 0xff7fff60: 0xffe7105b 66efddf7-633c-31d9-86ca-9391e39c4181
52C05B14-0B98-496c-BC3B-04B50211D680 0xffe65000+0xe0000c05b 0xff7fff80: 0xffe7213d 66efddf7-633c-31d9-86ca-9391e39c4181

52C05B14-0B98-496c-BC3B-04B50211D680 0xffe6============================================= DebugFeatureFlags: 0x0
DebugControl: 0x3

LogLevel: 0x80000000 ================================================================== ====
Trigger bridgeOS panic...
]5000+0xe0000d13d
0xff7fffd0: 0xffffd876 2a0d2a13-7dd1-3441-a9e2-83e6d4e521c4

1BA0062E-C779-4582-8566-336AE8F78F09 0xffffcdd8+0xe00000a9e ================================================================== ====
Apple ROM Version

BIOS ID: MM81.88Z.F000.B00.2303040335 Model: MM81
EFI Version: 1968.100.17.0.0
Built by: root@m4rld

Date: Sat Mar 4 03:35:46 2023

Revision: 1968.100.17 (B&I)
ROM Version: F000_B00
Build Type: Official Build, RELEASE
Compiler: clang-1403.0.22.11
UUID: 66EFDDF7-633C-31D9-86CA-9391E39C4181 UUID: 29CAAA43-487B-3043-9071-66E993407C55

 

[rm5]

Hey! Have you tried reviving or restoring the Mac? That might help, although I can't make any guarantees. Do you wanna try that first? Although given OWC's less-than-good reputation when it comes to reliable machines, um, it's entirely possible you have a faulty machine. But I'd try restoring first, because that basically wipes the hard drive and the T2 chip and replaces it with new, up-to-date firmware and software.

 

[stradify]

I'd also recommend the Revive and Restore process.

From the Log it shows that you're experiencing a bridgeOS panic:
Trigger bridgeOS panic...
]5000+0xe0000d13d
0xff7fffd0: 0xffffd876 2a0d2a13-7dd1-3441-a9e2-83e6d4e521c4

1BA0062E-C779-4582-8566-336AE8F78F09 0xffffcdd8+0xe00000a9e

From Wikipedia: bridgeOS is an embedded operating system created and developed by Apple Inc. for use exclusively with its hardware. bridgeOS runs on the T series Apple silicon processors[1] and operates the OLED touchscreenstrip called the "Touch Bar"[2] as well as multiple other functions, including managing the encrypted data in their Secure Enclave and acting as a gatekeeper and video codec to the device's cameras. bridgeOS is a heavily modified version of Apple's watchOS.

How to Revive a T2 Mac from Apple's website: https://support.apple.com/guide/app...r-restore-an-intel-based-mac-apdebea5be51/mac

How the revive and restore processes work​

The revive and restore processes involve the following steps:

Step 1. Plug the Mac computers together with a supported USB-C cable, locate Apple Configurator in the Applications folder or in Launchpad, then launch Apple Configurator on the first Mac.

Step 2. Restart the second Mac using a special key sequence. The key varies according to the type of Mac you want to revive or restore.

Step 3. Use Apple Configurator to revive the Mac.

Step 4. If a revive is unsuccessful, you can use Apple Configurator to restore the Mac.

 

[AlanMacInnes]

thank you for your reply - I don't have two computers to do this revive and restore process although it sounds like a solution

 

[Fishrrman]

How much memory is in it?

Did OWC add any RAM?

 

[AlanMacInnes]

Yes it has 64 gigs of RAM and they upgraded it from 8 so they did open up the computer to do the upgrade.

 

[Fishrrman]

"Yes it has 64 gigs of RAM and they upgraded it from 8 so they did open up the computer to do the upgrade."

That's what I'd be checking first.
Take the added memory out, return it to factory configuration, run like that 4-5 days.
Any difference?

 

[carylee2002]

I would try to run the computer and monitor on different power outlets. You may be maxing out 15amps or if your on a power strip that maybe the cause. Just make sure the two outlets is not controlled on the same power line to your breaker box. Ie. I have one line that is controlled on my kitchen breaker and the other outlet is controlled by my dining room breaker.

 

[Boyd01]

Although given OWC's less-than-good reputation when it comes to reliable machines, um, it's entirely possible you have a faulty machine.

I got a 2012 Quad Mini from them that has been running fine for the past 7 years or so, but maybe I was just lucky? The main reason I bought from OWC was the warranty however, so assuming that you're still within the warranty period, why not just return to OWC?

 

[Fishrrman]

The OP noted that OWC "upped the RAM".
The only "bad RAM" I ever recall dealing with came from OWC.
It wasn't "bad" at first... the problem developed over time.
That's why I mentioned it.

 

[TechnoMonk]

I had issues OWC RAM and disks upgraded in Mac Mini years ago. I would check the RAM first. Do they have multiple slots/chips for 64 GB? I would start popping out the upgraded chips and find if there is a faulty RAM.

 

[Boyd01]

It takes a significant effort to get at the memory in the 2018 Mini and there's always a risk of damaging something. That's why I say to just return it to OWC if still within warranty, let them replace it or just get your money back.

 

[carylee2002]

As I recall, the memory is not plug and play on a 2018 mini but must be soddered onto the main board. I too have a 32gb 2018 Mini from OWC and so far no problems. There is a program called memtest86 that is freeware that you can run to find out if your memory is bad. If it passes then it maybe one of your drivers.

 

[Boyd01]

As I recall, the memory is not plug and play on a 2018 mini but must be soddered onto the main board.

No, the memory is upgradeable, but designed to be upgraded by Apple service providers and not users because it involves disassembly. Nevertheless, many people have sucessfully done this themselves and there are videos and kits with the tools needed.

OWC (aka MacSales) is a well-known company here in the US, they sell memory, disks, ssd's and other computer parts. They also sell used Macs (with a warranty) that they have upgraded with more memory and larger SSD's using their own products.