"BAD MAGIC! (flag set in iBoot panic header)" — Catalina freezing all the time!

I have same here, 16 inch MBP 32 8gb gpu one time bad magic when I tried to connect a hub. I used the hub several times since without issues.

Chip version is:

iBridge2,14  J152fAP  4.2 (17P2551/17.16.12551.0.0,0) -

which is the same as @susanfromwinthrop above.

Same problem here (random restart after 5-10 minutes when nothing or only the charger is attached). It is working fine when I have a second display attached.

My chip:

iBridge2,14  J152fAP  4.2 (17P2551/17.16.12551.0.0,0)

I did a complete fresh reinstall with Catalina 10.15.2, but it is still crashing.

Hi, My 16" is  iBridge2,14  J152fAP  4.2 (17P2551/17.16.12551.0.0,0).

I got this unit on Nov 16 from the Apple Store as a replacement for a unit received on Nov 15 direct from Apple that could not be updated to the10.15.1 supplement.

This unit was stable for almost 3 weeks until yesterday when the BAD_MAGIC returned.

To add one thing, I have been having issues with my iMac Pro since High Sierra ( it was restarting with fans on giving bridge OS kernel panic and with Catalina just the name got changed to "BAD MAGIC")

Other than that, very nice summary of the topic you got there.

Tech news media, or the influencers are not picking up this topic... Apple is completely silent on this one.

We need to do something to form an active group. My money is tied to these useless computers.

(Also I have confirmed with my friend in Google Lab Germany that they have this issue on iMac Pro's.

And in my case I have in on iMac Pro and 15" MacBook Pro.)

This is effecting my brand new Mac Pro so I doubt it is a Touch Bar related issue or uniquely hardware issue for that matter. I have four mac's in my studio the only one running into this particular issue is the brand new Mac Pro which coincidentally is the only one running Catalina at the moment. For me it seems to happen when the machine sleeps. I have yet to have it crash when I am actively working. But once rebooted I get the exact same Bad Magic! error captured and discussed in this thread.

I took my machine to the store. They replaced the keyboard, touchbar and touchpad (apparently, it's all one piece) with brand new pieces. Excited at the possibility that the crash would be gone.

Lo and behold, the crashed happened again today. This discards the possibility that it's a touchbar-related issue.

The fellow who worked on my Mac told me he did some research regarding the Bad Magic crash. He believes it's a Catalina issue and that Apple could resolve it with a patch. Fingers crossed.

yeah, I’ve noticed that I had more of those panics when I was on 10.15, and on 10.15.2 it happened just once and didn’t happen at all during any heavy work. There is also Catalina 10.15.3 beta available for developers maybe it would get fixed there.

With Sprattnedia confirming crash in the new mac pro, I can now say T2 crashes have plagued all systems. (touch bar is also supervised by this chip) I would debate that they cannot solve the issue because it’s been there since High Sierra (Name was Bridge OS crash, now with Catalina it’s Bad Magic)

I have some corrupt files which trigger the kernel panic every time , My 2015 macbook pro handles the files just fine saying they are corrupt.

When I do the test with Imac pro and the 2018 macbook pro, they pop the rainbow wheel, then fans kick in, they shut the system down. I power the machines on, Voila, bad magic report is on the screen. ( Catalina 10.15.2)

I would speculate that the issue is with T2 hardware, they are trying to solve a hardware problem by software since High Sierra and they are unable to do so. This explains why they are avoiding any acknowledgement of the issue, I would argue that they fear the mass recall and its consequences.

I found these files by trial and error, I am a very methodical person, have done a lot of tests. Now I can replicate the issue...

I was transferring some mp4 files to FCPX. Then I connected the HDD to my old macbook and ran terminal and copied the files using rsync command. Then I located these files.

Now anytime I try to copy these corrupt files system crashes but it is not supposed to do so, obviously. Because in my old macbook, system basically says tgey are corrupt. This is the expected behavior.

As far as I know in any OS, files can become corrupt. But after the introduction of T2 chip, which meddles with almost every process, this issue surfaced. T2 chip is basically an iphone A12 processor(might be A11) in charge of so much supervision.

T2 seems the logic culprit when you crunch all the cases in this thread. I read that it's flashable and that you can disable in part some security functions on it, does someone has tested this lead ?

If this bug is old and changed name i fear it's bad news for them and us. Historically Apple doesn't aknowledge or recall easily, a bad-buzz (T2 gate?) or class action seems to be the way. Let's open the conversation with influencers and the press.

After 4 days without having any crash today I has 2 already, so the SMC and PRAM reset fix didn't last for too long.

This time it wasn't a bad magic error but the Sleep wake failure.

Sleep Wake failure in EFI

Failure code:: 0xffffffff 0x0000001f

Please IGNORE the below stackshot

================================================================

Date/Time: 2020-01-04 18:01:24 +0100

OS Version: ??? ??? (Build ???)

Architecture: x86_64

Report Version: 29

Data Source: Stackshots

Shared Cache: 0x6e53000 CF1837CB-9E43-3B29-BC95-9F8BCB1A8D20

Event: Sleep Wake Failure

Duration: 0.00s

Steps: 1

Boot args: chunklist-security-epoch=0 -chunklist-no-rev2-dev

Time Awake Since Boot: 15s

Process: swd [298]

Architecture: x86_64

Footprint: 588 KB

Start time: 2020-01-04 18:01:24 +0100

End time: 2020-01-04 18:01:24 +0100

Num samples: 1 (1)

Thread 0xb55 1 sample (1) priority 4 (base 4)

<thread QoS background (requested background), thread darwinbg, process darwinbg, IO tier 2>

1 start + 1 (libdyld.dylib + 108541) [0x7fff69ed17fd] 1

1 ??? [0x100903454] 1

1 ??? [0x1009031dd] 1

1 __stack_snapshot_with_config + 10 (libsystem_kernel.dylib + 136138) [0x7fff6a0323ca] 1

*1 ??? [0xffffff80002e3206] 1

*1 ??? [0xffffff800099acba] 1

*1 ??? [0xffffff80008b3bc1] 1

*1 ??? [0xffffff8000306467] (running) 1

Binary Images:

0x7fff69eb7000 - 0x7fff69eecfff libdyld.dylib (733.8) <8E2D3DED-0756-37A0-9D55-B9264CA020B4> /usr/lib/system/libdyld.dylib

0x7fff6a011000 - 0x7fff6a03dfff libsystem_kernel.dylib (6153.61.1) <90F8650F-D3A9-38B3-BB8C-B5D3686393BC> /usr/lib/system/libsystem_kernel.dylib

Model: MacBookPro16,1, BootROM 1037.60.58.0.0 (iBridge: 17.16.12551.0.0,0), 8 processors, 8-Core Intel Core i9, 2,3 GHz, 32 GB, SMC

Graphics: kHW_IntelUHDGraphics630Item, Intel UHD Graphics 630, spdisplays_builtin

Graphics: kHW_AMDRadeonPro5500MItem, AMD Radeon Pro 5500M, spdisplays_pcie_device, 8 GB

Memory Module: BANK 0/ChannelA-DIMM0, 16 GB, DDR4, 2667 MHz, SK Hynix, -

Memory Module: BANK 2/ChannelB-DIMM0, 16 GB, DDR4, 2667 MHz, SK Hynix, -

AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x7BF), wl0: Oct 26 2019 10:24:57 version 9.112.2.0.32.5.40 FWID 01-95c65950

Bluetooth: Version 7.0.2f4, 3 services, 27 devices, 1 incoming serial ports

Network Service: Wi-Fi, AirPort, en0

USB Device: USB 3.1 Bus

USB Device: Apple T2 Bus

USB Device: Composite Device

USB Device: Touch Bar Backlight

USB Device: Touch Bar Display

USB Device: Apple Internal Keyboard / Trackpad

USB Device: Headset

USB Device: Ambient Light Sensor

USB Device: FaceTime HD Camera (Built-in)

USB Device: Apple T2 Controller

Thunderbolt Bus: MacBook Pro, Apple Inc., 51.7

Thunderbolt Bus: MacBook Pro, Apple Inc., 51.7

Very disappointed with Apple which doesn't has the decency to answer anything in this post.

It always comes back ? Also when you disabled safe boot and energy saving features? I have done all these precautions swell on the new machine, all good for now, haven't stressed it much yet, I am planning a slow adaptation, from my early 2015 to 16'', which is crazy for the price tag, and just the fact at it supposed to be a computer for professionals.

I am almost just waiting that it crashes once within next 12 days, that would finally push me to go for a refund.

Get a refund while you can. I could not do it at the time because I needed to keep the machines for my profession. However, I lost customers during the replacement process which took 9 months for imac pro. And the process for the macbook pro is still ongoing (somewhat stagnant process actually)

IMPORTANT NOTE FOR THOSE WHO WANT TO KEEP THEIR DEVICES:

Call the Apple Support line make them give you a case number, have it documented in the system. This way no matter how long it takes they cannot reject your warranty claims on this T2 chip - Bad Magic kernel panic error.

A total of 8 senior reps ghosted me on this subject saying “we will help you don`t worry”. No callbacks whatsoever...

Yes, I too have a Mac mini that has experienced the “Bad Magic” failure on two different machines.

I just received my third replacement in the mail yesterday.

I have two Thunderbolt screens and my plan is to run the machine on just one screen for a week and then connect the second screen to see if this triggers the failure.

Great summary of the issue and matches my experience.

Add in the "Sleep Wake failure in EFI" crash which some of us are experiencing prior to the "Bad Magic" crashes.

As a test that it may have to do with either the Sleep/Energy Saver functions or having multiple LG UltraFine 4k directly connected monitors, I started by disabling Display options to "never sleep" and turned off "automatic graphics switching". I then connected directly one monitor and left the laptop open with the screen as the second monitor. No crashes after 2 days, so then connected directly the second monitor while still keeping the laptop open. No crashes after 1 day. Yesterday I closed the laptop and now running both monitors. No crashes yet. So perhaps the sleep/wake settings are key?