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

"I am not longer experiencing Bad Magic. I have still experienced a few crashes but now there is a proper error log generating..."

Yeah, but I think this is a little misleading. In 10.15.4 Apple just changed the error messaging in the pop-up window after a crash so that it no longer explicitly says "Bad magic!" I'm pretty sure if you look at the panic log, it will read the same as your previous logs, including the "Bad Magic!" bit. At least that's the case for me.

That said, after two days of pretty non-stop use with my replacement machine, it seems like 10.15.4 is much more stable. I've been using it with an external monitor, and it's handled pretty much everything I've thrown at it so far. It wakes much faster, and I'm not having any screen color or brightness glitches. Only crash was plugging in a bunch of peripherals while it was still sleeping.

In my case that issue started four days ago, after installing the last security update in a MacMini 2018 running macOS 10.14.6. I had a reboot warning popup after each start up of the computer, with no further problems, the computer just worked fine.

A NVRAM reset has solved this problem to me.

I had this issue for the very first time today in the morning when I opened my 2018 MacBook Pro (15-inch, 2018) and plugged in an adapter with an external monitor plugged in using HDMI.

Hopefully this is solved on a future version of Catalina. I'm on 10.15.3 (19D76) right now.

My replacement MBP 16" running 10.15.4 has been really stable since I received it about 6 days ago. I did have one Bad Magic! crash plugging in externals while it was asleep, but that was the only issue I've had with it. I've been using it pretty much all day, everyday. It's constantly plugged into a monitor and other peripherals. I've done word processing, edited photos, watched YouTube, watched videos from external media, and played a game in Windows Bootcamp. I don't know whether the difference in stability is due to the change in hardware or the 10.15.4 software update, since I was running 10.15.3 on the original machine.

I think you're on to something. Mine crashes with bug_type_210 after waking only when plugged in. I also notice that every time I restart, on the home screen, the screen would render in a yellow tint and my brightness it would be in a different setting from 1 brightness up. I'm thinking it might have something to do with the displays and energy saver modes in system preferences. I disabled auto brightness, True Tone, slightly dim display, and power nap mode on both battery and power adapter. I will see if this solves the issue. On another note, when in clamshell while plugged in to power before waking I disconnected the plug and it crashed. So yeah, it might be corrupted system preferences files.

Thank you!

Same here: After I installed the security-update on my 2018-MacMini (running Mojave btw) the computer would panic/reboot with the BAD-MAGIC-error every time I put it to sleep.

VERY annoying.

I did an nvram -reset (CMD-OPT-P-R during boot) and now the computer behaves again as it should.

Yes, i had a ton of Bad Magic till the last update , then this kind of error showed up. More infos but what's the meaning ? someone can decypher ?

Bad magic recipe here : multiscreen via usb-c + sleep mode

I did some research and found that this issue is likely caused by a hardware issue with the T2 Chip. And when plugged into external devices like a monitor it's more likely to happen. I've had it happen over 10 times in the last week or so after plugging my computer into a monitor because I'm working remotely, and don't have my iMac here.

Not a great time for everybody to have their top-of-the-line laptops start melting down due to hardware issues. There are no Apple Stores open, and even if there were, we're staying at home to flatten the curve of the coronavirus outbreak. We're stuck with broken hardware and no way to fix it.

Winning combination seems to be the T2 chip and a recent security update. Maybe the update was a little heavy handed?

https://thehackernews.com/2020/04/hacking-iphone-macbook-camera.html?fbclid=IwAR0gQKmJfZ4lUjYdqicAkheq1NMFMzU47COVkJXkszPdCijBVmwMrdIXfOY

Thats exactly where I am and have been since January. The only good news I can report is that the crashdump includes slightly more info than the singe line it did for the last 3 software revisions. Makes me think someone at least realizes there is a problem.

On a 2017 iMac Pro, my customer did not get this until I removed their LG Ultrafine and replaced it with an LG 27UL800. They needed a second monitor that worked with a 4K HDMI KVM. As soon as I added the 27UL8800, the iMac crashed on reboot and displayed an improper shutdown notice on reboot. It does this every time now, except...

When I installed a new macOS Mojave from recovery mode onto an external HDD, the issue was gone. Until I installed the recent Safari and Security updates. Then the exact issue came back.

Not likely a Bad Magic issue, or related to this.

I’ve had the linked issue since Mojave. Using SoftRAID and macOS with a Thunderbolt RAID5. MacOS keeps sleeping some part, even when set not to. RAID disks drop out and RAID gets corrupted. Have to use Amphetamine app to keep Mac awake. Only happens on some Macs, like low end iMacs.

I used iStat Menus to show the processor activity history and confirmed the Mac was sleeping, despite ALL settings to the contrary.

This has been an issue for SoftRAID for years. OWC and SoftRAID blame Apple.

Hey, I had BAD MAGIC in Kernel Panic yesterday. Had a little seizure because of it. Macbook Pro 15' 2018. Completely dark screen, no response at all. Restarting the password (and lighting up the screen with a phone torch) worked (for an unknown reason) Shift+Option+Command+R. Hope it will help somebody.

I had this start happening five days ago on my Mac mini 2018 running Mojave. Every time I boot up I get a crash report with "BAD MAGIC! (flag set in iBoot panic header), no macOS panic log available" in it. Everything was running fine until I installed the security update 2020-002, which I can only assume was actually meant for Catalina and there's no way of installing it. I've ben hunting around on the net and I found somewhere that said if I upgrade to Catalina it will fix it, but everywhere else I've read says that the problem started with Catalina and now I don't know the best course of action. I think the only way that I will find up is to do the upgrade and if it's no better, reinstall Mojave. Any input would be greatly appreciated.