Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

CATERR Error detected on MacBook Air (2019)

Good evening. Over the Martin Luther King Day holiday break (beginning on January 15, 2023 at about 8 pm), my 2019 Retina MacBook Air (SN: FV****YWV) began experiencing a series of kernel panics, which never occurred on any of my previous Mac computer (a mid-2013 Air which I was forced to dispose in 2019). Here is the kernel panic documentation as was originally posted (on 1/16/2023):


panic(cpu 1 caller 0xfffffff02278cb08): x86 CPU CATERR detected

Debugger message: panic

Memory ID: 0x6

OS release type: User

OS version: 20P2059

macOS version: 22C65

Kernel version: Darwin Kernel Version 22.2.0: Thu Nov 10 20:40:09 PST 2022; root:xnu-8792.61.2~1/RELEASE_ARM64_T8010

KernelCache UUID: D65CBF31465686CEA773B6B3569122DD

Kernel UUID: A9DF127E-F886-35CE-B377-B76E772B3FCA

Boot session UUID: 56DC8642-B3FD-4166-BCAB-994881E47D40

iBoot version: iBoot-8419.60.44

secure boot?: YES

roots installed: 0

x86 EFI Boot State: 0x16

x86 System State: 0x0

x86 Power State: 0x0

x86 Shutdown Cause: 0x5

x86 Previous Power Transitions: 0x405060400

PCIeUp link state: 0x68271614

macOS kernel slide: 0x17a00000

Paniclog version: 14

Kernel slide: 0x000000001c43c000

Kernel text base: 0xfffffff023440000

mach_absolute_time: 0xa0be2b2193

Epoch Time: sec usec

Boot : 0x63c555e5 0x000a55eb

Sleep : 0x63c5c600 0x0002eb8c

Wake : 0x63c5e381 0x00074d74

Calendar: 0x63c5e3bf 0x000b94eb


Zone info:

Zone map: 0xffffffe020c44000 - 0xffffffe620c44000

. VM : 0xffffffe020c44000 - 0xffffffe1072a8000

. RO : 0xffffffe1072a8000 - 0xffffffe153f74000

. GEN0 : 0xffffffe153f74000 - 0xffffffe23a5d8000

. GEN1 : 0xffffffe23a5d8000 - 0xffffffe320c3c000

. GEN2 : 0xffffffe320c3c000 - 0xffffffe4072a4000

. GEN3 : 0xffffffe4072a4000 - 0xffffffe4ed90c000

. DATA : 0xffffffe4ed90c000 - 0xffffffe620c44000

Metadata: 0xffffffe0101dc000 - 0xffffffe0119dc000

Bitmaps : 0xffffffe0119dc000 - 0xffffffe011c34000


TPIDRx_ELy = {1: 0xffffffe23a529088 0: 0x0000000000000001 0ro: 0x0000000000000000 }

CORE 0: PC=0xfffffff02365e824, LR=0xfffffff02365e824, FP=0xffffffee41d17f00

CORE 1 is the one that panicked. Check the full backtrace for details.

Compressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 0 swapfiles and OK swap space

Panicked task 0xffffffe320d01638: 0 pages, 202 threads: pid 0: kernel_task

Panicked thread: 0xffffffe23a529088, backtrace: 0xffffffee41de36c0, tid: 311

lr: 0xfffffff02362d44c fp: 0xffffffee41de3700

lr: 0xfffffff02362d25c fp: 0xffffffee41de3770

lr: 0xfffffff023762f9c fp: 0xffffffee41de37e0

lr: 0xfffffff023761f34 fp: 0xffffffee41de38a0

lr: 0xfffffff0235ed5fc fp: 0xffffffee41de38b0

lr: 0xfffffff02362ccd0 fp: 0xffffffee41de3c60

lr: 0xfffffff023cd6650 fp: 0xffffffee41de3c80

lr: 0xfffffff02278cb08 fp: 0xffffffee41de3cb0

lr: 0xfffffff022774604 fp: 0xffffffee41de3d10

lr: 0xfffffff02277dac8 fp: 0xffffffee41de3d60

lr: 0xfffffff022776b58 fp: 0xffffffee41de3e00

lr: 0xfffffff022773b94 fp: 0xffffffee41de3e70

lr: 0xfffffff022591b40 fp: 0xffffffee41de3ea0

lr: 0xfffffff023c21aec fp: 0xffffffee41de3ee0

lr: 0xfffffff023c21344 fp: 0xffffffee41de3f20

lr: 0xfffffff0235f86c0 fp: 0x0000000000000000


I tried to fix this problem by doing a disk check on January 16 and it repaired the Macintosh HD disk's startup volume. I have exactly 5 days of AppleCare support remaining on my device, which I received in December 2019.


Unfortunately, today, the same kernel panic message repeated again (and I did the CMD-option-P-R trick to reset the NAVRAM). I am going to try to contact Apple Support after doing the reset of the SMC and a reinstall of the current MacOS and see what I can do from there. If not, I will bring it in for repair on Saturday if necessary.


Thanks for the information.


-Joseph


[Personal Information Edited by Moderator]



MacBook Air 13″, macOS 13.1

Posted on Jan 17, 2023 4:58 PM

Reply
Question marked as Best reply

Posted on Feb 7, 2023 6:33 AM

It should not be panicking at all. KP events are not normal.


I cannot speak for Apple but Intel is very clear: CATERR is a serious internal CPU fault.


Software cannot fix broken hardware. The fact you brought your Mac to Apple prior to its AppleCare expiration yet the problem still remains should be reflected in its case history.

Similar questions

23 replies
Question marked as Best reply

Feb 7, 2023 6:33 AM in response to J4lambert

It should not be panicking at all. KP events are not normal.


I cannot speak for Apple but Intel is very clear: CATERR is a serious internal CPU fault.


Software cannot fix broken hardware. The fact you brought your Mac to Apple prior to its AppleCare expiration yet the problem still remains should be reflected in its case history.

Mar 12, 2023 2:38 PM in response to J4lambert

Hi J4lambert - You recently replied to a post where I stated I was having similar CATERR error message/shutdown issues with my 2019 MacBook Pro. You mentioned that the problem was rectified with the cleaning of the logic board and replacement of the USB-C adapter. Regarding the adapter, are you referring to the external adapter AC plug, or the internal USB-C power supply? I am about to send my computer in for repair, so I just wanted to be clear on your repair solution. Thanks for your original reply on this matter - hopefully I will find a similar resolution.

Jan 19, 2023 9:02 AM in response to J4lambert

Hi J4lambert,


From what you described in your original post, we recommend you check out the steps in the link below since your Mac experienced a kernel panic.


If your Mac restarts and a message appears - Apple Support


Next, we’d like to show you how to perform the recommended troubleshooting steps via the link above. Please click to open the link, then read through the steps in the section below.


If the kernel panic is caused by a known problem, the faulty software is identified. To make sure that this software doesn’t continue to cause kernel panics, move it to the Trash.

If the faulty software is not identified and your Mac continues to experience kernel panics, try the following:

*Restart your Mac in safe mode. If it successfully starts up in safe mode, choose Apple menu  > App Store, click Updates, then install any available updates.

*Uninstall any plug-ins or other enhancement software from manufacturers other than Apple. If you recently updated macOS or an app, plug-ins and other software that worked in the past may no longer be compatible. Read the manufacturer’s documentation (including Read Me notes) to be sure the software is compatible with your version of macOS.

*Disconnect all devices except for an Apple keyboard and mouse. Remove hardware upgrades from other manufacturers, such as random-access memory (RAM) and Peripheral Component Interconnect (PCI) cards. Then try restarting your Mac.

If this resolves the issue, reconnect one device at a time, restarting your Mac after reconnecting each one, until you determine which device is causing the problem.

*Use Apple Diagnostics to diagnose problems with your computer’s internal hardware, such as the logic board, memory, and wireless components. See the Apple Support article Use Apple Diagnostics to test your Mac.


We recommend the steps above because they will show you what to do if your Mac experiences a kernel panic.


Please let us know the outcome after giving the above steps a try.


Thanks for using the Apple Support Communities.


Cheers!

Jan 21, 2023 6:51 AM in response to J4lambert

{"roots_installed":0,"caused_by":"macos","macos_version":"Mac OS X 13.1 (22C65)","os_version":"Bridge OS 7.1 (20P2059)","macos_system_state":"running","incident_id":"36F2F02D-08F4-4298-AE83-2C77841FF054","bridgeos_roots_installed":0,"bug_type":"210","timestamp":"2023-01-21 14:00:03.00 +0000"}

{

"build" : "Bridge OS 7.1 (20P2059)",

"product" : "iBridge2,12",

"socId" : "0x00008012",

"kernel" : "Darwin Kernel Version 22.2.0: Thu Nov 10 20:40:09 PST 2022; root:xnu-8792.61.2~1\/RELEASE_ARM64_T8010",

"incident" : "36F2F02D-08F4-4298-AE83-2C77841FF054",

"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",

"date" : "2023-01-21 14:00:03.15 +0000",

"panicString" : "panic(cpu 1 caller 0xfffffff00d020b08): x86 CPU CATERR detected\nDebugger message: panic\nMemory ID: 0x6\nOS release type: User\nOS version: 20P2059\nmacOS version: 22C65\nKernel version: Darwin Kernel Version 22.2.0: Thu Nov 10 20:40:09 PST 2022; root:xnu-8792.61.2~1\/RELEASE_ARM64_T8010\nKernelCache UUID: D65CBF31465686CEA773B6B3569122DD\nKernel UUID: A9DF127E-F886-35CE-B377-B76E772B3FCA\nBoot session UUID: 36F2F02D-08F4-4298-AE83-2C77841FF054\niBoot version: iBoot-8419.60.44\nsecure boot?: YES\nroots installed: 0\nx86 EFI Boot State: 0xd\nx86 System State: 0x0\nx86 Power State: 0x0\nx86 Shutdown Cause: 0x5\nx86 Previous Power Transitions: 0x405060400\nPCIeUp link state: 0x89271614\nmacOS kernel slide: 0\nPaniclog version: 14\nKernel slide: 0x0000000006cd0000\nKernel text base: 0xfffffff00dcd4000\nmach_absolute_time: 0xad631f4c6\nEpoch Time: sec usec\n Boot : 0x63cb3d45 0x000644b3\n Sleep : 0x63cb4c0f 0x000b9557\n Wake : 0x63cbef83 0x0002e826\n Calendar: 0x63cbefc4 0x000de72a\n\nZone info:\n Zone map: 0xffffffe693764000 - 0xffffffec93764000\n . VM : 0xffffffe693764000 - 0xffffffe779dc8000\n . RO : 0xffffffe779dc8000 - 0xffffffe7c6a94000\n . GEN0 : 0xffffffe7c6a94000 - 0xffffffe8ad0f8000\n . GEN1 : 0xffffffe8ad0f8000 - 0xffffffe99375c000\n . GEN2 : 0xffffffe99375c000 - 0xffffffea79dc4000\n . GEN3 : 0xffffffea79dc4000 - 0xffffffeb6042c000\n . DATA : 0xffffffeb6042c000 - 0xffffffec93764000\n Metadata: 0xffffffee33a48000 - 0xffffffee35248000\n Bitmaps : 0xffffffee35248000 - 0xffffffee35494000\n\nTPIDRx_ELy = {1: 0xffffffe8ad1549c0 0: 0x0000000000000001 0ro: 0x0000000000000000 }\nCORE 0: PC=0xfffffff00def2824, LR=0xfffffff00def2824, FP=0xffffffec937aff00\nCORE 1 is the one that panicked. Check the full backtrace for details.\nCompressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 0 swapfiles and OK swap space\nPanicked task 0xffffffea79d11638: 0 pages, 202 threads: pid 0: kernel_task\nPanicked thread: 0xffffffe8ad1549c0, backtrace: 0xffffffee339976c0, tid: 299\n\t\t lr: 0xfffffff00dec144c fp: 0xffffffee33997700\n\t\t lr: 0xfffffff00dec125c fp: 0xffffffee33997770\n\t\t lr: 0xfffffff00dff6f9c fp: 0xffffffee339977e0\n\t\t lr: 0xfffffff00dff5f34 fp: 0xffffffee339978a0\n\t\t lr: 0xfffffff00de815fc fp: 0xffffffee339978b0\n\t\t lr: 0xfffffff00dec0cd0 fp: 0xffffffee33997c60\n\t\t lr: 0xfffffff00e56a650 fp: 0xffffffee33997c80\n\t\t lr: 0xfffffff00d020b08 fp: 0xffffffee33997cb0\n\t\t lr: 0xfffffff00d008604 fp: 0xffffffee33997d10\n\t\t lr: 0xfffffff00d011ac8 fp: 0xffffffee33997d60\n\t\t lr: 0xfffffff00d00ab58 fp: 0xffffffee33997e00\n\t\t lr: 0xfffffff00d007b94 fp: 0xffffffee33997e70\n\t\t lr: 0xfffffff00ce25b40 fp: 0xffffffee33997ea0\n\t\t lr: 0xfffffff00e4b5aec fp: 0xffffffee33997ee0\n\t\t lr: 0xfffffff00e4b5344 fp: 0xffffffee33997f20\n\t\t lr: 0xfffffff00de8c6c0 fp: 0x0000000000000000\n\n",

"panicFlags" : "0x902",

"bug_type" : "210",

"otherString" : "\n** Stackshot Succeeded ** Bytes Traced 38286 (Uncompressed 113760) **\n",

"macOSPanicFlags" : "0x0",

"macOSPanicString" : "BAD MAGIC! (flag set in iBoot panic header), no macOS panic log available"

Jan 22, 2023 8:51 AM in response to John Galt

This MacBook is being decommissioned in the coming weeks as a result of the failure of the CPU. This is not being detected in diagnostics, but the CPU has been degrading since the fall of 2022. The computer is just over 3 years old. Back in late 2021, its display had to be replaced because of cheap USB-C cable usage and the display replacement had partially accelerated the degradation of the CPU. Had cheap USB-C cables not been used the CPU degradation would have taken place in early 2025.


Shutdown cause -63 is related to internal failure of the CPU.

Feb 7, 2023 5:30 AM in response to John Galt

I brought my MacBook to the Genius Bar on January 27 and they sent it out to the repair center for further diagnostics. The extended diagnostics that was run at the repair center found that there was an issue with the firmware and so they updated the firmware to the latest version. When I received the laptop back on February 6 the panics began again, and they are happening mostly when the computer is connected to the USB-C power source using a genuine apple cable. There have also been a few instances where the panics happened while on battery power but they happen less frequently while on battery. My Mac is about 3.1 years old and it should not be panicking that often.

Feb 7, 2023 12:07 PM in response to John Galt

I do believe that this is a problem with both the USB-C power supply (primary) and the logic board (secondary). The applecare I had was recently renewed on January 19 after it expired back in December 2022 following the initial three year extended warranty period. Should I tell apple to replace both the logic board and the usb-c power supply? Or should I wait a few months to upgrade to a silicon mac?

Feb 8, 2023 6:18 AM in response to J4lambert

No; I think you should take it back to Apple and tell them to fix it. They accepted it for repair on January 15 and from what you describe it is exhibiting the same exact problems.


Personally I think nothing less than a logic board replacement will be necessary, but just to reiterate I am not in position to personally inspect the Mac or to propose the actions required to fix it.

Feb 8, 2023 10:01 AM in response to John Galt

They accepted the Mac for repair on January 27 and they found no issues during the kernel panic triage at the repair center. They just updated the firmware to the latest version and they did not bother with servicing the logic board during the previous repair. I am going back to the Genius Bar on Friday.

I sent apple support a series of pictures of the USB-C ports. The ports are slightly discolored.

Feb 8, 2023 5:35 PM in response to J4lambert

I am requesting a thorough physical examination of the computer’s logic board to check if there is any corrosion that could require the logic board to be replaced. The computer was not repaired; they only updated the firmware and did a clean reinstall after all troubleshooting tests were exhausted. An unexpected shutdown happened on Monday when I received the computer back from the repair center.


CATERR Error detected on MacBook Air (2019)

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.