User profile for user: zirconate
zirconate Author
User level: Level 1
4 points

CPU CATErr Detected, Crashed While Sleeping

My 2020 MacBook Pro (Intel 1.4GHz Quad-Core i5) has been having intermittent issues either with apps crashing or the computer crashing. Along with that the computer has been getting concerningly hot for the last year or so. The heating started with RAM-intensive video games and has been progressing to much simpler apps like Apple Pages or TextEdit. It is operating on Sequoia 15.4.1. Today the computer fully crashed with a CATErr. I had it charging overnight with no peripherals attached and a couple light apps open. I am not super techy so I don't entirely know what all the reports my computer has given me. I pulled this from the crash report:


Machine-check capabilities: 0x0000000000000c0b

family: 6 model: 142 stepping: 10 microcode: 246

signature: 0x806ea

Intel(R) Core(TM) i5-8257U CPU @ 1.40GHz

11 error-reporting banks

Processor 0: IA32_MCG_STATUS: 0x0000000000000005

IA32_MC4_STATUS(0x411): 0xba00000011000402

IA32_MC4_MISC(0x413): 0x0000000000000000

Processor 1: IA32_MCG_STATUS: 0x0000000000000005

IA32_MC4_STATUS(0x411): 0xba00000011000402

IA32_MC4_MISC(0x413): 0x0000000000000000

Processor 2: IA32_MCG_STATUS: 0x0000000000000005

IA32_MC4_STATUS(0x411): 0xba00000011000402

IA32_MC4_MISC(0x413): 0x0000000000000000

Processor 3: IA32_MCG_STATUS: 0x0000000000000005

IA32_MC4_STATUS(0x411): 0xba00000011000402

IA32_MC4_MISC(0x413): 0x0000000000000000

Processor 4: IA32_MCG_STATUS: 0x0000000000000005

IA32_MC4_STATUS(0x411): 0xba00000011000402

IA32_MC4_MISC(0x413): 0x0000000000000000

Processor 5: IA32_MCG_STATUS: 0x0000000000000005

IA32_MC4_STATUS(0x411): 0xba00000011000402

IA32_MC4_MISC(0x413): 0x0000000000000000

Processor 6: IA32_MCG_STATUS: 0x0000000000000005

IA32_MC4_STATUS(0x411): 0xba00000011000402

IA32_MC4_MISC(0x413): 0x0000000000000000

Processor 7: IA32_MCG_STATUS: 0x0000000000000005

IA32_MC4_STATUS(0x411): 0xba00000011000402

IA32_MC4_MISC(0x413): 0x0000000000000000

mp_kdp_enter() timed-out on cpu 1, NMI-ing

mp_kdp_enter() NMI pending on cpus: 0 2 3 4 5 6 7

mp_kdp_enter() timed-out during locked wait after NMI;expected 8 acks but received 1 after 9711705 loops in 695999999 ticks

panic(cpu 1 caller 0xffffff801873db84): Machine Check at 0x00007ff80cf35d52, registers:

CR0: 0x0000000080010033, CR2: 0x0000000107652000, CR3: 0x00000002b480e2c4, CR4: 0x00000000003626e0

RAX: 0x00007ff80d12de40, RBX: 0x00007ff84b9e15e8, RCX: 0x00000000000007c8, RDX: 0x000070000b372888

RSP: 0x000070000b372828, RBP: 0x000070000b372870, RSI: 0x0000000000000001, RDI: 0x0000000000000001

R8: 0x1400001a80000035, R9: 0x3f0ea0aa25c1faa8, R10: 0x00007ff84e910f50, R11: 0x00007ff80e05bfab

R12: 0x00007ff80cad90c0, R13: 0x000070000b372888, R14: 0x0000000000000006, R15: 0x0000000000000000

RFL: 0x0000000000000246, RIP: 0x00007ff80cf35d52, CS: 0x000000000000002b, SS: 0x0000000000000023

Error code: 0x0000000000000000

@trap_native.c:168

Panicked task 0xffffffa04c922988: 42 threads: pid 69611: Music

Backtrace (CPU 1), panicked thread: 0xffffffa5162de598, Frame : Return Address

0xffffffe52d75fac0 : 0xffffff80185da441

0xffffffe52d75fb10 : 0xffffff801874d6c6

0xffffffe52d75fb50 : 0xffffff801873c85c

0xffffffe52d75fc10 : 0xffffff801856f971

0xffffffe52d75fc30 : 0xffffff80185da737

0xffffffe52d75fd30 : 0xffffff80185d9dbb

0xffffffe52d75fda0 : 0xffffff8018dcdd5d

0xffffffe52d75fe90 : 0xffffff801873db84

0xffffffe52d75ff90 : 0xffffff8018dd8029

0xffffffe52d75ffa0 : 0xffffff801856fe4f


Process name corresponding to current thread (0xffffffa5162de598): Music


The panic log shows a catastrophic error in the same CPU (1). When I ran the diagnostic (restart + hold "D") that returned "No issues found". Does anyone know if this is the beginning of the end for my computer or is this something software related that can be fixed?

MacBook Pro 13″, macOS 15.4

Posted on Oct 13, 2025 10:48 AM

Reply
Question marked as Top-ranking reply
User profile for user: John Galt
John Galt
User level: Level 10
154,588 points

Posted on Oct 13, 2025 6:21 PM

CATERR = catastrophic error condition

MCA = machine check architecture


Contact Support, because that Mac is suffering from a hardware fault.


For those with too much time on their hands, https://software.intel.com/content/www/us/en/develop/articles/intel-sdm.html#combined


panic(cpu 1 caller 0xffffff801873db84): Machine Check at 0x00007ff80cf35d52,


An archived version of If your Mac spontaneously restarts or displays "Your computer restarted because of a problem" also contained the following passage:


"Note: If you find the term "machine check" in the "Problem Details and System Configuration" field of this report, it may indicate a hardware-related issue."

View in context
7 replies
Question marked as Top-ranking reply
User profile for user: John Galt
John Galt
User level: Level 10
154,588 points

Oct 13, 2025 6:21 PM in response to zirconate

CATERR = catastrophic error condition

MCA = machine check architecture


Contact Support, because that Mac is suffering from a hardware fault.


For those with too much time on their hands, https://software.intel.com/content/www/us/en/develop/articles/intel-sdm.html#combined


panic(cpu 1 caller 0xffffff801873db84): Machine Check at 0x00007ff80cf35d52,


An archived version of If your Mac spontaneously restarts or displays "Your computer restarted because of a problem" also contained the following passage:


"Note: If you find the term "machine check" in the "Problem Details and System Configuration" field of this report, it may indicate a hardware-related issue."

Reply
User profile for user: HWTech
HWTech
User level: Level 9
67,934 points

Nov 5, 2025 7:50 PM in response to brs973

brs973 wrote:

My Macbook Pro (Intel) running Sequoia crashed during sleep, every time.
Work around fix: open a Terminal session and disable the sleep service with the following syntax: SUDO PMSET DISABLESLEEP1.

The way you have written the command appears to be incorrect. "pmset" does not appear to have a "disablesleep1" option (unless it just happens to be an undocumented option....seems to occur too much with macOS command line utilities). Besides you don't have a space between the option name & its configuration value, which is extremely important when using the command line.


According to the "pmset" man pages, 

man  pmset

     sleep - system sleep timer (value in minutes, or 0 to disable)



the correct option is:

sudo  pmset  sleep  0


FYI, instead of putting the command in all CAPs, if you want to show a Terminal command, you should use the "Code Insertion" tool which has an icon which looks like "</>" on the forum editing toolbar. It will make the command stand out from the rest of the post and it will use a fixed font which makes it easier to differentiate characters & spacings. Notice how the "zero" is shown with a slash to distinguish it from the letter "O" with the command I posted above where I used the forum's "Code Insertion" tool.



Note to Apple: This bug in the OS can be fixed with a patch. Get on it! (please)

Apple is not here on this forum. If you want to get Apple's attention, then file an official bug report (not sure where to go with that), or provide Apple with product feedback here:

Product Feedback - Apple


Unless people report issues to Apple directly, Apple may never know an issue exists, nor how wide spread or concerning the issue may be.


FYI, if you are getting the same CPU CATERR & MachineCheck errors, then you most likely have a hardware failure with your Mac...you just happened to have found a way around having that hardware failure triggered.

Reply
User profile for user: leroydouglas
leroydouglas
Community+ 2025
User level: Level 10
198,024 points

Oct 13, 2025 11:26 AM in response to zirconate

zirconate wrote:

My 2020 MacBook Pro (Intel 1.4GHz Quad-Core i5) has been having intermittent issues either with apps crashing or the computer crashing.

It is operating on Sequoia 15.4.1.





The current stable release of Sequoia including bug fixes, security updates is macOS 15.7.1 - I would start there

Keep your Mac up to date - Apple Support

Keep your Mac up to date - Apple Support


Reply
User profile for user: brs973
brs973
User level: Level 1
8 points

Nov 5, 2025 11:38 AM in response to zirconate

My Macbook Pro (Intel) running Sequoia crashed during sleep, every time.

Work around fix: open a Terminal session and disable the sleep service with the following syntax: SUDO PMSET DISABLESLEEP1.


I power off the Macbook at night and do all my iCloud syncing during the day.


If you upgrade to Tahoe you'll have to reset the sleep service again.


Note to Apple: This bug in the OS can be fixed with a patch. Get on it! (please)

Reply
User profile for user: zirconate
zirconate Author
User level: Level 1
4 points

Oct 13, 2025 10:48 AM in response to zirconate

I also pulled this from the panic log in the console:


"panicString" : "panic(cpu 1 caller 0xfffffff0165b36a0): x86 CPU CATERR detected\nDebugger message: panic\nMemory ID: 0xff\nOS release type: User\nOS version: 22P4248\nmacOS version: 24E263\nKernel version: Darwin Kernel Version 24.4.0: Fri Mar 14 18:21:55 PDT 2025; root:xnu-11417.101.14~1\/RELEASE_ARM64_T8010\nKernelCache UUID: 559F48FC0E53452D134FB3D7C1BB67F4\nKernel UUID: 4ED489B1-A8E5-31AD-9354-6E81AC8B41DD\nBoot session UUID: 9C388318-860D-480D-BB94-80CC96D88E5A\niBoot version: iBoot-11881.101.1\niBoot Stage 2 version: \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: 0x10001000100\nPCIeUp link state: 0x89473614\nmacOS kernel slide: 0x18200000\nPaniclog version: 14\nKernel slide: 0x00000000103a8000\nKernel text base: 0xfffffff0173ac000\nmach_absolute_time: 0x5dd6685f659a\nEpoch Time: sec usec\n Boot : 0x68a759c8 0x00057845\n Sleep : 0x68ed18ec 0x000ea013\n Wake : 0x68ed18ed 0x0004c11a\n Calendar: 0x68ed1925 0x00060ff7\n\nZone info:\n Zone map: 0xffffffdebee84000 - 0xffffffe4bee84000\n . VM : 0xffffffdebee84000 - 0xffffffdfa54e8000\n . RO : 0xffffffdfa54e8000 - 0xffffffdff21bc000\n . GEN0 : 0xffffffdff21bc000 - 0xffffffe0d8820000\n . GEN1 : 0xffffffe0d8820000 - 0xffffffe1bee84000\n . GEN2 : 0xffffffe1bee84000 - 0xffffffe2a54ec000\n . GEN3 : 0xffffffe2a54ec000 - 0xffffffe38bb54000\n . DATA : 0xffffffe38bb54000 - 0xffffffe4bee84000\n Metadata: 0xffffffeffe5ec000 - 0xffffffefffdec000\n Bitmaps : 0xffffffefffdec000 - 0xffffffeffff18000\n Extra : 0 - 0\n\nTPIDRx_ELy = {1: 0xffffffe0d8314940 0: 0x0000000000000001 0ro: 0x0000000000000000 }\nCORE 0: PC=0xfffffff0176f8c30, LR=0xfffffff0176f8c2c, FP=0xffffffe4bf9afe60\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 0xffffffe38baace40: 0 pages, 233 threads: pid 0: kernel_task\nPanicked thread: 0xffffffe0d8314940, backtrace: 0xffffffe4bf7936b0, tid: 31074278\n\t\t lr: 0xfffffff0175bac8c fp: 0xffffffe4bf793720\n\t\t lr: 0xfffffff0176f6bbc fp: 0xffffffe4bf793790\n\t\t lr: 0xfffffff0176f5be4 fp: 0xffffffe4bf793880\n\t\t lr: 0xfffffff0175796c8 fp: 0xffffffe4bf793890\n\t\t lr: 0xfffffff0175ba6bc fp: 0xffffffe4bf793c60\n\t\t lr: 0xfffffff017cb3910 fp: 0xffffffe4bf793c80\n\t\t lr: 0xfffffff0165b36a0 fp: 0xffffffe4bf793cb0\n\t\t lr: 0xfffffff01659c31c fp: 0xffffffe4bf793d10\n\t\t lr: 0xfffffff0165a326c fp: 0xffffffe4bf793d60\n\t\t lr: 0xfffffff01659ce1c fp: 0xffffffe4bf793e00\n\t\t lr: 0xfffffff01659bae4 fp: 0xffffffe4bf793e30\n\t\t lr: 0xfffffff017615b84 fp: 0xffffffe4bf793f20\n\t\t lr: 0xfffffff0175846c4 fp: 0x0000000000000000\n\n",

Reply

CPU CATErr Detected, Crashed While Sleeping

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