Kernel panic over and over and over

I have experienced numerous kernel panics on my MacBook Pro 16-inch. It wasn´t that often in the beginning but has increased over time so I went to an Apple Certified Engineer to fix the problem. The solution, as they told me, was to replace the mothercard and keyboard. Unfortunately the warranty had expired so the repairs costed me $1600, almost two thirds as much as a new MacBookPro.

After getting the MacBookPro back I have been having the same, exact issues with kernel panics several times a day. I went back to the engineer but they say that everything is OK. They have done, what they call a stress test which did not show anything. So I had do pay $60 for them performing that stress test that didn´t show anything.

I took the computer back home and it took about 1 hour until another kernel panic, and then serveral every day. It´s impossible to work in that situation. So I went back to the Apple Certified Engineer one more time, but got the same explanation. There is nothing wrong with the computer.

So I went back again, and the same result. We have performed a stress test and there is nothing wrong with your computer. Went home again, this time it crasched immediatly when starting. And then again after about one hour.


I can add that I have reinstalled MacOS twice, wiping the hard drive both times, there is no peripherals and no other software installed unless Apple software that came with MacOS.


This time I have been saving the crash reports and hope that someone can figure out what´s wrong.


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

Debugger message: panic

Memory ID: 0x6

OS release type: User

OS version: 19P6066

macOS version: 21G83

Kernel version: Darwin Kernel Version 21.6.0: Wed Aug 10 14:04:32 PDT 2022; root:xnu-8020.141.5~1/RELEASE_ARM64_T8010

Kernel UUID: ED0C23DC-B156-3B2D-A95D-022856D12AD5

iBoot version: iBoot-7459.141.1

secure boot?: YES

x86 EFI Boot State: 0x16

x86 System State: 0x0

x86 Power State: 0x0

x86 Shutdown Cause: 0xec

x86 Previous Power Transitions: 0x70604000100

PCIeUp link state: 0x89473611

Paniclog version: 13

Kernel slide:   0x000000000dc3c000

Kernel text base: 0xfffffff014c40000

mach_absolute_time: 0x168f53b6c

Epoch Time:    sec    usec

 Boot  : 0x630603af 0x0002f312

 Sleep  : 0x6306045e 0x0007dab8

 Wake  : 0x63060952 0x0004998f

 Calendar: 0x6306099b 0x00063886


Zone info:

 Zone map: 0xffffffe02ddec000 - 0xffffffe62ddec000

 . VM  : 0xffffffe02ddec000 - 0xffffffe114450000

 . RO  : 0xffffffe114450000 - 0xffffffe16111c000

 . GEN0 : 0xffffffe16111c000 - 0xffffffe247780000

 . GEN1 : 0xffffffe247780000 - 0xffffffe32dde4000

 . GEN2 : 0xffffffe32dde4000 - 0xffffffe41444c000

 . GEN3 : 0xffffffe41444c000 - 0xffffffe4faab4000

 . DATA : 0xffffffe4faab4000 - 0xffffffe62ddec000

 Metadata: 0xffffffee579e4000 - 0xffffffee591e4000

 Bitmaps : 0xffffffee591e4000 - 0xffffffee59434000


CORE 0: PC=0xfffffff01547e924, LR=0xfffffff01547e924, FP=0xffffffee594c3f00

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 0xffffffe4143f8628: 0 pages, 228 threads: pid 0: kernel_task

Panicked thread: 0xffffffe413f294e8, backtrace: 0xffffffe62ea33670, tid: 439

 lr: 0xfffffff01544e64c fp: 0xffffffe62ea336b0

 lr: 0xfffffff01544e3d4 fp: 0xffffffe62ea33720

 lr: 0xfffffff015587e48 fp: 0xffffffe62ea33790

 lr: 0xfffffff015586dec fp: 0xffffffe62ea33840

 lr: 0xfffffff015aad5fc fp: 0xffffffe62ea33850

 lr: 0xfffffff01544e0f0 fp: 0xffffffe62ea33be0

 lr: 0xfffffff01544e0f0 fp: 0xffffffe62ea33c40

 lr: 0xfffffff0165d33e8 fp: 0xffffffe62ea33c60

 lr: 0xfffffff015cf5550 fp: 0xffffffe62ea33c90

 lr: 0xfffffff015ce2360 fp: 0xffffffe62ea33cf0

 lr: 0xfffffff015ce8770 fp: 0xffffffe62ea33d40

 lr: 0xfffffff015ce41c4 fp: 0xffffffe62ea33de0

 lr: 0xfffffff015ce1a1c fp: 0xffffffe62ea33e60

 lr: 0xfffffff015b903d8 fp: 0xffffffe62ea33e90

 lr: 0xfffffff0159f4394 fp: 0xffffffe62ea33ee0

 lr: 0xfffffff0159f3c70 fp: 0xffffffe62ea33f20

 lr: 0xfffffff015ab85a0 fp: 0x0000000000000000



MacBook Pro

Posted on Aug 24, 2022 8:36 AM

Reply
Question marked as Top-ranking reply

Posted on Aug 25, 2022 1:19 PM

x86 CPU CATERR detected

This is a CPU CATastrophic ERRor.


If there are no external devices connected and a clean install has been performed with no third party apps or restoration from a backup, then this is most definitely a hardware issue. Keep in mind a lot of Apple techs have no clue how to read a Kernel Panic report as Apple does not provide any training on things like this to their techs. Unfortunately many Apple techs just blindly follow Apple's very basic training.


I think it is time to speak with the manager of the store or repair shop to get this straightened out. Keep in mind you have a 90 part/repair warranty depending on how the laptop was serviced so it is best to have them deal with this during that 90 day period. You may need to contact Apple support directly here to see if they can assist by clicking the "Get Support" link at the top right of this page. Or you may even need to contact Apple corporate if neither of these methods get the repair shop to deal with the problem.

Similar questions

4 replies
Question marked as Top-ranking reply

Aug 25, 2022 1:19 PM in response to madeleine224

x86 CPU CATERR detected

This is a CPU CATastrophic ERRor.


If there are no external devices connected and a clean install has been performed with no third party apps or restoration from a backup, then this is most definitely a hardware issue. Keep in mind a lot of Apple techs have no clue how to read a Kernel Panic report as Apple does not provide any training on things like this to their techs. Unfortunately many Apple techs just blindly follow Apple's very basic training.


I think it is time to speak with the manager of the store or repair shop to get this straightened out. Keep in mind you have a 90 part/repair warranty depending on how the laptop was serviced so it is best to have them deal with this during that 90 day period. You may need to contact Apple support directly here to see if they can assist by clicking the "Get Support" link at the top right of this page. Or you may even need to contact Apple corporate if neither of these methods get the repair shop to deal with the problem.

Aug 25, 2022 11:11 AM in response to madeleine224

Hi madeleine224,


Thank you for using the Apple Support Communities! You have done great steps so far. We would also suggest any additional steps such as checking for RAM and third-party hardware as listed in the following article:


If your Mac restarted because of a problem


After reviewing the article, if the issue remains, we recommend that you reach out to Apple Support directly to take a further look. Please reach out here:


Get Support


Hope this helps!

Have a great day.


Sep 19, 2022 5:49 AM in response to toddfromla

toddfromla wrote:

I followed Mac's instructions for problematic reboots and the issue--of constant rebooting Darwin Kernel Panic Monterey--continues.

Each person's issues will be unique for these symptoms. Please start your own thread so you have the best chance of receiving advice most suited to your exact situation and to prevent confusion as we provide assistance to the original poster of this thread. Provide as much detail as possible including the exact model of the Mac and version of macOS being used. Plus what you were doing on the Mac the first time you encountered the issue including whether you had made any recent changes to the software (including a macOS update), hardware (internal or external), etc. Also include the steps you have already performed to try to resolve the situation so we don't' offer advice for things you have already tried. If possible run EtreCheck and post the report in your own thread using the "Additional Text" icon which looks like a piece of paper.


To look for possible hardware issues run the Apple Diagnostics.


Also disconnect all external devices in case one of them is causing a problem.


If you cannot boot macOS normally, then try booting into Safe Mode.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Kernel panic over and over and over

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