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

I can't even imagine how much money Apple wasted, I replaced my MacBook Pro 16-inch and yesterday same thing happened again (apple support calls it a kernel panic), it's been 2 months and Apple doesn't seem to be bothered at all. By the way Genius Bar didn't even bother to get more information from me about what happened, literally I entered the store and all I said that it has kernel panics and they immediately brought a replacement for me. Good service! Apple really shows that they don't care about their customers, but it's fine.... It won't be a problem for me to switch to a Windows based machines, at least it looks like they care about customers more than shoving their pockets with money.

Same issue here, with a new 16”. It crashes randomly when I leave the laptop unattended, every day or two - I come back and it has shut down, “BAD MAGIC!” error when I restart.

I returned mine, and plan to wait until the issue has been fixed before I buy again. My 2013 MacBook Pro is still a reliable workhorse with a great keyboard. (but I already miss the 16’s speakers, and ability to use an iPad as a second display)

hmmm.

do we maybe have an relation for this issue to MacBooks which are connected to two (or one) external monitors?

How do you have them connected? I connected my two external displays (1x 4k, 1x1080p) via HDMI to USB-C cables.

Cheers and happy new year from Germany!

Man Apple that's so disappointing, I bought a 16" mbp yesterday, It was working all together for 30min and this error. It happens every time within a minute, sometimes doesn't even get past the apple loading screen. Its completely unusable. I did pram and smc resets, nothing. I ll try to reinstall os but reading from this forum 8 don't think it will help. Tomorrow I am returning this 3k eur piece of junk, what a joke.

I see a lot of users here who are victims of this issue. Yet, this company fails to make any comments on this issue... I have completely lost faith in the products. I have spent 15000$ on an imac pro and a macbook pro. There is not a single “pro” feature in terms of product support. I own a small business that relies on video production. All day long, we are buried in this company’s time wasting procedures. Format, reinstall, reset SMC, T2 chip firmware update, replacement units and so on...

Shame on you for putting your share price above user experience. They forgot that the aggregate result of positive user experiences got this brand to where it stands today...

Make an announcement, say you are aware of the issue, say you are working on it, but be honest for God’s sake...

I doubt it's much deferent, I think it's from the same series, as the serials are very similar. Also I don't think they have any clue about this issue - they are a technics store not official apple service. They just had to give me a new one because the machine didn't fully boot after their factory reset and os reinstalI, what else can you do with 1 day dead computer that costs 3k eur?

I checked the T2 version now :

iBridge2,14 J152fAP 4.2

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.

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.

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.

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.

I have reported these problems to Apple support, but i filled in the feedback form now as well. FWIW, the Bad Magic crash only occurred once within the first 24 hours of my MPB 16", but it should not happen at all.