Level 1

4 points

MacBook Pro 16 inch 2019 with panic error after MacOS Monterey update

Dear Community,

after installing new MacOS Monterey operating system last summer, My MacBook Pro started having a serious recurring issue: it keeps restarting automatically every time I use it, making it impossible to use it.

It all started during the Monterey update, making it impossible to finalize the installation. I spent hours on the phone with Apple trying to revive my laptop and the problem seemed to be fixed back then. Immediately after it kept again restarting and giving me the belo panic error.

I went to an authorized Apple center but they told me to ask Apple directly as they could not fix the issue as it seemed to be a software problem that I would carry anyhow within my Time machine back-up....

Can anyone help here, maybe? What is best to do to save my data and save also my macbook?

thanks a lot!!!

panic(cpu 1 caller 0xfffffff00b5e4550): macOS watchdog detected

Debugger message: panic

Memory ID: 0x6

OS release type: User

OS version: 19P4243

macOS version: 21E258

Kernel version: Darwin Kernel Version 21.4.0: Mon Feb 21 20:11:10 PST 2022; root:xnu-8020.101.4~1/RELEASE_ARM64_T8010

Kernel UUID: E6F1BA8F-E69D-3228-BA00-99812FF9CBEF

iBoot version: iBoot-7459.101.2

secure boot?: YES

x86 EFI Boot State: 0x16

x86 System State: 0x0

x86 Power State: 0x0

x86 Shutdown Cause: 0x5

x86 Previous Power Transitions: 0x10001000100

PCIeUp link state: 0x89473614

Paniclog version: 13

Kernel slide: 0x0000000003530000

Kernel text base: 0xfffffff00a534000

mach_absolute_time: 0x28beca04c0

Epoch Time: sec usec

Boot : 0x635b7f38 0x00076cf6

Sleep : 0x636222f4 0x0000be54

Wake : 0x636229f4 0x0003863e

Calendar: 0x6362391c 0x000296ac

Zone info:

Foreign : 0xfffffff0481b4000 - 0xfffffff0481c4000

Native : 0xffffffe0004bc000 - 0xffffffe6004bc000

Readonly: 0xffffffe0e6b20000 - 0xffffffe1337ec000

Metadata: 0xffffffeb009cc000 - 0xffffffeb04aec000

Bitmaps : 0xffffffeb021cc000 - 0xffffffeb02428000

CORE 0: PC=0xfffffff00ad6b070, LR=0xfffffff00ad6b070, FP=0xffffffeb1080bf00

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

Panicked thread: 0xffffffe133f1f800, backtrace: 0xffffffeb04a0b680, tid: 419

lr: 0xfffffff00ad3ab08 fp: 0xffffffeb04a0b6c0

lr: 0xfffffff00ad3a890 fp: 0xffffffeb04a0b730

lr: 0xfffffff00ae72e64 fp: 0xffffffeb04a0b7a0

lr: 0xfffffff00ae72018 fp: 0xffffffeb04a0b850

lr: 0xfffffff00b39d5fc fp: 0xffffffeb04a0b860

lr: 0xfffffff00ad3a5ac fp: 0xffffffeb04a0bbf0

lr: 0xfffffff00ad3a5ac fp: 0xffffffeb04a0bc50

lr: 0xfffffff00beb74c8 fp: 0xffffffeb04a0bc70

lr: 0xfffffff00b5e4550 fp: 0xffffffeb04a0bca0

lr: 0xfffffff00b5d1380 fp: 0xffffffeb04a0bd00

lr: 0xfffffff00b5d7790 fp: 0xffffffeb04a0bd50

lr: 0xfffffff00b5d31e4 fp: 0xffffffeb04a0bdf0

lr: 0xfffffff00b5d0a3c fp: 0xffffffeb04a0be70

lr: 0xfffffff00b47f578 fp: 0xffffffeb04a0bea0

lr: 0xfffffff00b2e3abc fp: 0xffffffeb04a0bee0

lr: 0xfffffff00b2e339c fp: 0xffffffeb04a0bf20

lr: 0xfffffff00b3a85a0 fp: 0x0000000000000000

MacBook Pro 16″, macOS 12.3

Posted on Nov 4, 2022 12:33 PM

Top-ranking reply

Grant Bennet-Alder

Level 10

140,255 points

Posted on Nov 4, 2022 12:36 PM

That is only the initial portion of the report, and does not have the reason fro the panic.

Kernel Panic Reports are stored at:

/Library/Logs/DiagnosticReports

If you copy and paste that string into:

Finder > Go menu > Go to Folder

it will take you to where those reports are stored.

They are named with Date&Time and start or end in ‘panic’

If you find one, please post the entire report here, by using the “additional text” Icon in the reply footer (looks like a paper with writing).

Please don’t post more about 20 lines of any other types of reports — they are interminable, and any information useful for this purpose is on the first screenful.

There are three quick take-aways from any panic report.

1) The panic-reason,

2) the extensions present at the "scene of the crime", and

3) the BSD process in which the problem occurred.

One more item that is important is the names of any third-party Extensions you have added. They are shown FIRST in the extensions loaded section

View in context

MacBook Pro 16 inch 2019 with panic error after MacOS Monterey update

Similar questions