constant crashing after upgrading to monterey mac pro

Question

Level 1

5 points

constant crashing after upgrading to monterey mac pro

I've seen daily, sometimes multiple times a day, crashing on my machine since upgrading to Monterey. There seems to be no consistency in the crashes. While browsing safari, sending a message, reading an email, using After Effects, Maya, etc. Just random spontaneous crashes that result in a black screen and a restart.

I don't know what to do. Here's my crash report:

panic(cpu 0 caller 0xfffffff024eeb948): x86 CPU CATERR detected

Debugger message: panic

Memory ID: 0x6

OS release type: User

OS version: 19P5071

macOS version: 21F79

Kernel version: Darwin Kernel Version 21.5.0: Tue Apr 26 20:35:13 PDT 2022; root:xnu-8020.121.3~1/RELEASE_ARM64_T8010

Kernel UUID: 41CCAFE3-249A-32C3-9A09-D08790A306F2

iBoot version: iBoot-7459.121.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: 0x405060400

PCIeUp link state: 0x89271611

Paniclog version: 13

Kernel slide: 0x000000001ce8c000

Kernel text base: 0xfffffff023e90000

mach_absolute_time: 0x1fa593ed7

Epoch Time: sec usec

Boot : 0x62a809d7 0x000d164d

Sleep : 0x62a80a95 0x000d0079

Wake : 0x62a80b3d 0x0008e0f1

Calendar: 0x62a80bdd 0x000b3524

Zone info:

Zone map: 0xffffffe34d3a0000 - 0xffffffe94d3a0000

. VM : 0xffffffe34d3a0000 - 0xffffffe433a04000

. RO : 0xffffffe433a04000 - 0xffffffe4806d0000

. GEN0 : 0xffffffe4806d0000 - 0xffffffe566d34000

. GEN1 : 0xffffffe566d34000 - 0xffffffe64d398000

. GEN2 : 0xffffffe64d398000 - 0xffffffe733a00000

. GEN3 : 0xffffffe733a00000 - 0xffffffe81a068000

. DATA : 0xffffffe81a068000 - 0xffffffe94d3a0000

Metadata: 0xffffffe94d3b0000 - 0xffffffe94ebb0000

Bitmaps : 0xffffffe94ebb0000 - 0xffffffe94ee10000

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

CORE 1: PC=0xfffffff02467a4a0, LR=0xfffffff02467a4a0, FP=0xffffffe00ca53f00

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

Panicked task 0xffffffe733a9c628: 0 pages, 167 threads: pid 0: kernel_task

Panicked thread: 0xffffffe566a830c8, backtrace: 0xffffffe00c8db670, tid: 364

lr: 0xfffffff02464a504 fp: 0xffffffe00c8db6b0

lr: 0xfffffff02464a28c fp: 0xffffffe00c8db720

lr: 0xfffffff024782a40 fp: 0xffffffe00c8db790

lr: 0xfffffff024781aa4 fp: 0xffffffe00c8db840

lr: 0xfffffff024ca55fc fp: 0xffffffe00c8db850

lr: 0xfffffff024649fa8 fp: 0xffffffe00c8dbbe0

lr: 0xfffffff024649fa8 fp: 0xffffffe00c8dbc40

lr: 0xfffffff0256fb340 fp: 0xffffffe00c8dbc60

lr: 0xfffffff024eeb948 fp: 0xffffffe00c8dbc90

lr: 0xfffffff024ed8758 fp: 0xffffffe00c8dbcf0

lr: 0xfffffff024edeb68 fp: 0xffffffe00c8dbd40

lr: 0xfffffff024eda5bc fp: 0xffffffe00c8dbde0

lr: 0xfffffff024ed7e14 fp: 0xffffffe00c8dbe60

lr: 0xfffffff024d868a0 fp: 0xffffffe00c8dbe90

lr: 0xfffffff024bee528 fp: 0xffffffe00c8dbee0

lr: 0xfffffff024bede04 fp: 0xffffffe00c8dbf20

lr: 0xfffffff024cb05a0 fp: 0x0000000000000000

Posted on Jun 15, 2022 7:30 PM

Reply

Answer 1

jimmyburan Author

Level 1

5 points

Jun 16, 2022 7:33 AM in response to Grant Bennet-Alder

Panic code

panic 2

panic 3

Thanks! I have no idea what I'm looking at. They all look consistent, but I don't see what's causing them. It says cause by "Core 0". Not sure what that means. Any additional help would be greatly appreciated. Thanks!

Reply

Answer 2

Jun 16, 2022 6:59 AM in response to jimmyburan

If you have any software that wastes computer resources on a regular basis, such as speeder-uppers, Cleaner-uppers/Removers, Optimizers, Virus Scanners, third-party file Sync-ers such as DropBox, OneDrive, or GoogleDrive, or a VPN that you installed yourself, it will do busywork at previously-impossible speeds. Virus scanners in particular are notorious for causing panics like the one you posted, which appears to be a deliberate 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

————

Take look at your other reports. What you are trying to determine is whether there is a TREND.

Case A) There is a trend: This same panic occurs in each case, with the same extensions present, in the same BSD process. A trend can indicate corrupted software or a Hardware problem that can be tracked down and solved.

Case B) There is a decided NON-Trend. The panics occur "all over the Map" for different panic reasons and in different BSD processes, with different extensions present.

A Non-trend suggests you may have RAM memory problems. MacOS slightly randomizes the load point of key routines on each startup, as a hedge against fixed-address attacks. This causes a marginal memory cell to move into different routines each time your Mac starts up.

If the above is just "word-salad" to you, just ask and Readers can explain a bit more.

Reply

Answer 3

Jun 16, 2022 9:23 AM in response to jimmyburan

Just be warned -- Apple support is happy to REFERENCE anything you posted here, and will read it, but they never believe any conclusions we make here -- they always need to rediscover according to their own procedures, which they consider more rigorous.

Apple specialists have a lot more technical knowledge, but far less patience than the first responders.

Reply