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

Feb 9, 2023 11:20 AM in response to John Galt

I have turned off some performance settings on my Mac and changed the charging port to the right side port, which seems to have partially resolved the issue with the kernel panics and unexpected shutdowns at least for now. However the logic board might still have to be physically inspected and the adapter will need to be changed.

Feb 20, 2023 8:51 AM in response to J4lambert

UPDATE: The problem has been officially fixed.


The cause of this problem was that there were several issues with the USB-C adapter's internal components, which resulted in the adapter being replaced. The logic board was also cleaned.


Thanks to everyone who had helped me with this problem over the past few weeks. The computer is still good for at least another 18-24 months. I am intending on upgrading to an Apple silicon computer in the second half of next year as macOS 14 might be the last version to support intel T2 macs.

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.