<![CDATA[iFixit - Answers With Device "MacBook Pro 14""]]> https://tr.ifixit.com/Answers/Device/MacBook_Pro_14%22/All?rss=yes en-US Mon, 03 Aug 2026 03:53:24 -0700 <![CDATA[MacBook Pro 14" 2021: MacBook Pro 14" A2442 flat battery]]> Went out on vacation last week and don't remember if I shutdown my MBP 14". When we came back on Friday and tried to power on the laptop, initially it was not powering on, so we tried connecting the MagSafe 3 for us to know whether it was going to take the initial charge. As these newer models work with the internal chip reconizing power before it enters to the mainboard, the laptop cannot take any power if the battery is 0%.

After realizing that MagSafe was not working, I tried my wife's iPhone's USB-C to USB-C and connected it to the MBP power brick. When doing that I saw the battery in red which indicates that the battery is fully drained. This had happened twice and connecting the USB-C from the iPhone helped charging the laptop for 10 minutes and then MagSafe worked perfectly - but this time it didn't work at all.

Tried out DFU "revive" with no luck as I tried connecting both laptops using the same iPhone USB-C cable and no power connected to any of them.

Need to know whether I get a USB-C 3.0 will help for me to start the process of DFU (as it didn't work with the iPhone cable).

Will this resolve my battery issue, should it be better to leave the laptop charging with the MagSafe or USB-C overnight?

⟐ Commented Temmuz 29, 2026 at 17:13 GMT-7

]]> https://tr.ifixit.com/Answers/View/965659/MacBook+Pro+14%22+A2442+flat+battery https://tr.ifixit.com/Answers/View/965659 Wed, 29 Jul 2026 17:13:31 -0700 <![CDATA[MacBook Pro 14" Late 2023 (M3 Pro and M3 Max): Screen having constant glitch of lines/ghost-images across the screen]]> I was using my Macbook and it suddenly happened. The screen definitely didn't get accidentally opened too far or too hard, but it looks a bit like something isn't plugged all the way, if that makes sense. Like the lines that form the display are disorganized and moving/flashing around. I'll include a couple pics but it's a bit hard to see. Look at the lower half of the image where you can see the folder icon leaving this weird "gradient" or "trail":

Resim
Resim

It seems subtle on the image, but in real life when its moving and flashing around it is pretty distracting...

⟐ Commented Temmuz 19, 2026 at 2:09 GMT-7

]]> https://tr.ifixit.com/Answers/View/875400/Screen+having+constant+glitch+of+lines-ghost-images+across+the+screen https://tr.ifixit.com/Answers/View/875400 Sun, 19 Jul 2026 02:09:24 -0700 <![CDATA[MacBook Pro 14" 2021: Why does my MacBook hard crash after opening lid?]]> I have a M1 Macbook Pro 14" (2021) that I have been using for 4 years. For a long time, I simply used the OS it came out of the box with (macOS 12.1). It never gave any issues and I was too lazy to update it. One day I simply opened the lid of my macbook and tried to use Touch ID to open lock screen. After several attempts of trying to use Touch ID (it has a tendency to not work first time), I realized my mac froze and then a hard crash occurred (apple logo flashed).

I tried to force restart which led me to the black screen with exclamation mark. There was no trackpad haptic, power button was unresponsive, MagSafe LED did not work. Since I didn't have a secondary mac for a DFU restore, I simply kept my mac in isolation for a while and didn't touch it. 2 days later I plugged my mac in using Magsafe and the LED lit up.

After a full charge, I opened my macbook which showed how it restarted due to a problem. The logs said it was a kernel panic. After digging, i decided to update my OS to the latest version (macOS Tahoe 26.5.2). I thought it would fix every problem. However a few days later, the same thing happened. I opened the lid, spammed Touch ID for it to register, and then it simply hard crashed and I had to wait another 2 days for it to boot up again (same symptoms). This time there was no kernel log reports and my mac thinks absolutely nothing went wrong (I checked console and there was no crash logs or anything)

The only thing I found using the command
pmset -g log | grep -E "Failure|Sleep|Wake"

was:
2026-07-15 13:38:56 +0600 Assertions          PID 1914(AddressBookSourceSync) Released PreventUserIdleSystemSleep "Address Book Source Sync" 00:00:30  id:0x0x10000856f [System: No Assertions]

2026-07-15 13:52:11 +0600 Assertions          PID 348(powerd) Created InternalPreventSleep "Holding in darkwake for up to 20 seconds to query model for inactivity prediction" 00:00:00  id:0x0xd00008591 [System: SRPrevSleep kCPU]

2026-07-15 13:52:11 +0600 Assertions          PID 348(powerd) Released InternalPreventSleep "Holding in darkwake for up to 20 seconds to query model for inactivity prediction" 00:00:00  id:0x0xd00008591 [System: No Assertions]

2026-07-15 14:37:35 +0600 Assertions          PID 1967(AddressBookSourceSync) Released PreventUserIdleSystemSleep "Address Book Source Sync" 00:00:30  id:0x0x1000085d7 [System: No Assertions]

2026-07-15 14:52:11 +0600 Assertions          PID 348(powerd) Created InternalPreventSleep "Holding in darkwake for up to 20 seconds to query model for inactivity prediction" 00:00:00  id:0x0xd000085f8 [System: SRPrevSleep kCPU]

2026-07-15 14:52:11 +0600 Assertions          PID 348(powerd) Released InternalPreventSleep "Holding in darkwake for up to 20 seconds to query model for inactivity prediction" 00:00:00  id:0x0xd000085f8 [System: No Assertions]

2026-07-15 15:37:26 +0600 Assertions          PID 1993(AddressBookSourceSync) Released PreventUserIdleSystemSleep "Address Book Source Sync" 00:00:30  id:0x0x100008645 [System: No Assertions]

2026-07-15 15:52:11 +0600 Assertions          PID 348(powerd) Created InternalPreventSleep "Holding in darkwake for up to 20 seconds to query model for inactivity prediction" 00:00:00  id:0x0xd00008668 [System: SRPrevSleep kCPU]

2026-07-15 15:52:11 +0600 Assertions          PID 348(powerd) Released InternalPreventSleep "Holding in darkwake for up to 20 seconds to query model for inactivity prediction" 00:00:00  id:0x0xd00008668 [System: No Assertions]

2026-07-15 16:37:26 +0600 Assertions          PID 2020(AddressBookSourceSync) Released PreventUserIdleSystemSleep "Address Book Source Sync" 00:00:30  id:0x0x1000086bf [System: No Assertions]

2026-07-15 16:52:11 +0600 Assertions          PID 348(powerd) Created InternalPreventSleep "Holding in darkwake for up to 20 seconds to query model for inactivity prediction" 00:00:00  id:0x0xd000086e0 [System: SRPrevSleep kCPU]

2026-07-15 16:52:11 +0600 Assertions          PID 348(powerd) Released InternalPreventSleep "Holding in darkwake for up to 20 seconds to query model for inactivity prediction" 00:00:00  id:0x0xd000086e0 [System: No Assertions]

2026-07-15 17:39:26 +0600 Assertions          PID 2074(AddressBookSourceSync) Released PreventUserIdleSystemSleep "Address Book Source Sync" 00:00:30  id:0x0x10000872a [System: No Assertions]

2026-07-15 17:52:11 +0600 Assertions          PID 348(powerd) Created InternalPreventSleep "Holding in darkwake for up to 20 seconds to query model for inactivity prediction" 00:00:00  id:0x0xd00008753 [System: SRPrevSleep kCPU]

2026-07-15 17:52:11 +0600 Assertions          PID 348(powerd) Released InternalPreventSleep "Holding in darkwake for up to 20 seconds to query model for inactivity prediction" 00:00:00  id:0x0xd00008753 [System: No Assertions]

2026-07-15 18:38:20 +0600 Assertions          PID 2136(AddressBookSourceSync) Summary PreventUserIdleSystemSleep "Address Book Source Sync" 00:00:24  id:0x0x10000879f [System: PrevIdle]

2026-07-15 18:38:26 +0600 Assertions          PID 2136(AddressBookSourceSync) Released PreventUserIdleSystemSleep "Address Book Source Sync" 00:00:30  id:0x0x10000879f [System: No Assertions]

2026-07-15 18:28:41 +0600 Assertions          PID 359(powerd) Created InternalPreventSleep "com.apple.powermanagement.wakeschedule" 00:00:00  id:0x0xd00008002 [System: PrevIdle SRPrevSleep kCPU]

2026-07-15 18:28:41 +0600 Assertions          PID 359(powerd) Created InternalPreventSleep "Holding in darkwake for up to 20 seconds to query model for inactivity prediction" 00:00:00  id:0x0xd00008003 [System: PrevIdle SRPrevSleep kCPU]

2026-07-15 18:28:41 +0600 Assertions          PID 359(powerd) Released InternalPreventSleep "Holding in darkwake for up to 20 seconds to query model for inactivity prediction" 00:00:00  id:0x0xd00008003 [System: PrevIdle SRPrevSleep kCPU]

Sleep/Wakes since boot at 2026-07-15 10:06:39 +0600 :0   Dark Wake Count in this sleep cycle:1

2026-07-15 18:28:41 +0600 Assertions          PID 359(powerd) Created UserIsActive "com.apple.powerd.ws.initialize" 00:00:00  id:0x0x900008007 [System: PrevIdle DeclUser SRPrevSleep kCPU kDisp]

2026-07-15 18:28:42 +0600 Assertions          Summary- [System: PrevIdle DeclUser SRPrevSleep kCPU kDisp] Using AC(Charge: 100)

2026-07-15 18:28:44 +0600 Assertions          PID 419(WindowServer) Created UserIsActive "com.apple.iohideventsystem.queue.tickle.nxevent service:IOHIDSystem pid:660 process:Dock" 00:00:00  id:0x0x900008038 [System: PrevIdle DeclUser SRPrevSleep kCPU kDisp]

2026-07-15 18:28:46 +0600 Assertions          PID 359(powerd) TimedOut InternalPreventSleep "com.apple.powermanagement.wakeschedule" 00:00:05  id:0x0xd00008002 [System: PrevIdle DeclUser SRPrevSleep kCPU kDisp]

What is wrong with my macbook? Is it a Touch ID issue or some other hardware/ software related problem?

Things to keep in mind:

1. I installed battery toolkit and used it in this month. I never had any issues with battery but decided to use it since my capacity was 85%. Cycle count is at 483. Condition is normal

2. I did not perform a full wipe when updating my OS from 12.1 to 26.5.2

3. After my macbook booted up, there were no other problems and it worked as intended.

4. Apple diagnostics says there is nothing wrong with any of my hardware (including Touch ID and Battery)

Update 1: Did a workaround by disabling lock screen entirely and removing touch ID as they were usually the causes of hard crash. After leaving my mac overnight with lid closed (not shutdown), it was simply dead right off the bat. I digged up some logs using the same command as before:

2026-07-18 10:11:47 +0600 com.apple.sleepservices.sessionTerminated SleepService: window has terminated.

2026-07-18 10:11:47 +0600 Sleep               Entering Sleep state due to 'Sleep Service Back to Sleep':TCPKeepAlive=active Using Batt (Charge:75%)

2026-07-18 10:11:50 +0600 Wake Requests       [*process=dasd request=SleepService deltaSecs=995 wakeAt=2026-07-18 10:28:25 info="com.apple.dasd:501:com.apple.chronod.nextScheduledTimelineRefresh"] [process=mDNSResponder request=Maintenance deltaSecs=7200 wakeAt=2026-07-18 12:11:50 info="upkeep wake"] [process=powerd request=TCPKATurnOff deltaSecs=312730 wakeAt=2026-07-22 01:04:00] [process=powerd request=CSPNEvaluation deltaSecs=3125 wakeAt=2026-07-18 11:03:55] [process=powerd request=UserWake deltaSecs=10775 wakeAt=2026-07-18 13:11:26 info="com.apple.alarm.user-invisible-com.apple.calaccessd.travelEngine.periodicRefreshTimer,617"]

2026-07-18 10:11:50 +0600 PM Client Acks      Delays to Sleep notifications: [com.apple.bluetooth.sleep is slow(1543 ms)] [mDNSResponder is slow(2877 ms)]

Sleep/Wakes since boot at 2026-07-17 20:45:23 +0600 :65   Dark Wake Count in this sleep cycle:4

2026-07-18 13:25:42 +0600 Assertions          PID 359(powerd) Created InternalPreventSleep "com.apple.powermanagement.darkwakelinger" 00:00:00  id:0x0xd0000817c [System: PrevIdle DeclUser SysAct SRPrevSleep kCPU kDisp]

Sleep/Wakes since boot at 2026-07-18 13:25:14 +0600 :0   Dark Wake Count in this sleep cycle:4

2026-07-18 13:25:42 +0600 Assertions          PID 359(powerd) Released PreventUserIdleSystemSleep "Powerd - Prevent sleep while display is on" 00:00:26  id:0x0x100008008 [System: PrevIdle DeclUser SysAct SRPrevSleep kCPU kDisp]

2026-07-18 13:25:42 +0600 Assertions          PID 426(runningboardd) Summary PreventUserIdleSystemSleep "osservice<com.apple.itunescloudd(501)>426-739-303:com.apple.CFNetwork.StorageDB" 00:00:01  id:0x0x100008177 [System: PrevIdle DeclUser SysAct SRPrevSleep kCPU kDisp]

2026-07-18 13:25:42 +0600 Assertions          PID 359(powerd) Summary UserIsActive "com.apple.powerd.ws.initialize" 00:00:26  id:0x0x900008009 [System: PrevIdle DeclUser SysAct SRPrevSleep kCPU kDisp]

2026-07-18 13:25:42 +0600 Assertions          PID 418(WindowServer) Summary UserIsActive "com.apple.iohideventsystem.queue.tickle serviceID:100000ab6 service:AppleMultitouchDevice product:Apple Internal Keyboard / Trackpad eventType:11" 00:00:02  id:0x0x900008033 [System: PrevIdle DeclUser SysAct SRPrevSleep kCPU kDisp]

2026-07-18 13:25:42 +0600 Assertions          PID 556(mds_stores) Summary BackgroundTask "com.apple.metadata.mds_stores.power" 00:00:19  id:0x0xb00008105 [System: PrevIdle DeclUser SysAct SRPrevSleep kCPU kDisp]

2026-07-18 13:25:42 +0600 Assertions          PID 374(mds) Summary BackgroundTask "com.apple.metadata.mds.power" 00:00:23  id:0x0xb0000803f [System: PrevIdle DeclUser SysAct SRPrevSleep kCPU kDisp]

2026-07-18 13:25:42 +0600 Assertions          PID 647(cloudd) Summary SystemIsActive "NSURLSessionTask B5FB9788-3BCE-44C8-9D99-D492F0F20E72" 00:00:03  id:0x0xc00008172 [System: PrevIdle DeclUser SysAct SRPrevSleep kCPU kDisp]

2026-07-18 13:25:42 +0600 Assertions          PID 647(cloudd) Summary SystemIsActive "NSURLSessionTask A7F6768B-E0B3-4E2B-8783-17F66C8421B0" 00:00:02  id:0x0xc00008173 [System: PrevIdle DeclUser SysAct SRPrevSleep kCPU kDisp]

2026-07-18 13:25:42 +0600 Assertions          PID 647(cloudd) Summary SystemIsActive "NSURLSessionTask BBF3B16C-FA61-4E7F-8A82-B1CFD051E55D" 00:00:02  id:0x0xc00008175 [System: PrevIdle DeclUser SysAct SRPrevSleep kCPU kDisp]

2026-07-18 13:25:42 +0600 Assertions          PID 647(cloudd) Summary SystemIsActive "NSURLSessionTask A94CE808-2F83-4140-AE56-1C3AA62BB4A7" 00:00:01  id:0x0xc00008176 [System: PrevIdle DeclUser SysAct SRPrevSleep kCPU kDisp]

2026-07-18 13:25:42 +0600 Assertions          PID 647(cloudd) Summary SystemIsActive "NSURLSessionTask 0441BFAA-CDB2-4F65-8FC6-9DC89EBAF7A9" 00:00:01  id:0x0xc0000817b [System: PrevIdle DeclUser SysAct SRPrevSleep kCPU kDisp]

2026-07-18 13:25:42 +0600 Assertions          PID 359(powerd) Summary InternalPreventSleep "com.apple.powermanagement.darkwakelinger" 00:00:00  id:0x0xd0000817c [System: PrevIdle DeclUser SysAct SRPrevSleep kCPU kDisp]

2026-07-18 13:25:42 +0600 Assertions          PID 647(cloudd) Released SystemIsActive "NSURLSessionTask B5FB9788-3BCE-44C8-9D99-D492F0F20E72" 00:00:03  id:0x0xc00008172 [System: PrevIdle DeclUser SysAct SRPrevSleep kCPU kDisp]

2026-07-18 13:25:42 +0600 Assertions          PID 418(WindowServer) TurnedOn UserIsActive "com.apple.iohideventsystem.queue.tickle serviceID:1000002e0 service:AppleM68Buttons product:(null) eventType:3" 00:00:00  id:0x0x900008033 [System: PrevIdle DeclUser SysAct SRPrevSleep kCPU kDisp]

2026-07-18 13:25:42 +0600 Assertions          PID 359(powerd) Created UserIsActive "com.apple.powermanagement.lidopen" 00:00:00  id:0x0x900008184 [System: PrevIdle DeclUser SysAct SRPrevSleep kCPU kDisp]

2026-07-18 13:25:43 +0600 Assertions          PID 647(cloudd) Released SystemIsActive "NSURLSessionTask A7F6768B-E0B3-4E2B-8783-17F66C8421B0" 00:00:03  id:0x0xc00008173 [System: PrevIdle DeclUser SysAct SRPrevSleep kCPU kDisp]

2026-07-18 13:25:43 +0600 Assertions          Summary- [System: PrevIdle DeclUser SysAct SRPrevSleep kCPU kDisp] Using Batt(Charge: 69)

Somehow, my battery went from 75% in sleep state, hard crashed into a dead mode, and then suddenly became 69%

Update 2: Decided to shutdown mac and hopefully boot into diagnostics mode. Turns out mac simply restarted before i could even do anything and it said my mac restarted due to a problem. Logs are below:

panic(cpu 1 caller 0xfffffe003e8b4418): SEP Panic: :sars/sars: 0x100010858 0x000584bc 0x00050434 0x10000f880 0x100002388 0x10000be34 0x10000c568 0x10000d070 0x10000b014 0x100006180 0x00052870 0x10000ef0c 0x100005fe4 0x100008d20 0x100000d74 0x100000bc8 0x1000009f0 [hggghgolo]

Panic app vers: 3151.120.3

Panic app UUID: 68A9CDAF-552F-3BB1-B20A-76DA1F603737

Shared cache vers: 3151.120.3

Shared cache UUID: 3726CD1B-A290-308A-9AD8-69417B8D59B2

Root task tag: (root@cm8qz.p1l.plx.sd.apple.com)

Root task build time: Jun 1 2026 20:50:54

Root task vers: AppleSEPOS-3151.120.3

Root task UUID: ECFAE211-028E-35A0-B492-D6BB5A16CADF

Diagnostics: 584c0100e934093989bd7c6a86a7da3f703d52f2332e065d39caf3f38874b447f0b42bf2efeb644800000000000000000000000000000000000000000000000000000000a2953b28c10ac912c87cda8ad9b66eb1555b8ea7f3c9501033c7ca6ba6448acd9dd63ca700000000000000000000000000000000000000000000000000000000000005

SEPO/BOOT

SEPO/EXCP 0xa684/0xab04/0x0000000000000013 er/EXCP

SEPD/SEPD 0x4c63c/0x4cdb4/0x1817181718171817 er/SEPD

SEPD/TIME 0x4c63c/0x4cb10/0x1417181314171813 er/TIME

SEPD/XPRT 0x4c63c/0x4cdb4/0x1817181718171817 er/XPRT

SEPD/PMGR 0x4c63c/0x4cdb4/0x1817181718171817 er/PMGR

SEPD/TRNG 0x4c63c/0x4cb10/0x1314101314131413 er/TRNG

SEPD/KEY 0x4c63c/0x4cb10/0x1718171817181013 er/KEY

SEPD/MONI 0x4c63c/0x4cdb4/0x1516171810151617 er/MONI

SEPD/AKF 0x4c63c/0x4cb10/0x1406101314061013 er/AKF

SEPD/EP0D 0x4c63c/0x4cb10/0x1813141314131413 er/EP0D

SEPD/AESH 0x4c63c/0x4cdb4/0x1516171810151617 er/AESH

SEPD/shnd 0x4c63c/0x4cdb4/0x1817181718171817 er/shnd

SEPD/ep0 0x4c63c/0x4cb10/0x1413141314131413 er/ep0

AESS/DAES 0x4c63c/0x4cdb4/0x1817181718171817 er/DAES

AESS/AESS 0x4c63c/0x4cdb4/0x1516171810151617 er/AESS

AESS/PKA 0x4c63c/0x4cdb4/0x1516171810151617 er/PKA

AESS/AEST 0x4c63c/0x4cdb4/0x1516171810151617 er/AEST

dxio/dxio 0x4c63c/0x4d0fc/0x1410131410131410 r/----

enti/enti 0x4c63c/0x4cdb4/0x1817181718171817 er/enti

enti/vers 0x4c63c/0x4cdb4/0x0000000000131417 er/vers

skg /skg 0x4c63c/0x4cdb4/0x1817181718171817 er/skg

skg /skgs 0x4c63c/0x4cdb4/0x1817181718171817 er/skgs

skg /crow 0x4c63c/0x4cb10/0x0000000000000013 er/crow

skg /cro2 0x4c63c/0x4cb10/0x0000000000000013 er/cro2

sars/sars 0x4c63c/0x4c368/0x1112111211121112 ert/BOOT

ARTM/ARTM 0x4c63c/0x4cb10/0x0000000000000013 er/ARTM

xART/xART 0x4c63c/0x4c368/0x1314171817181718 ert/sars

hibe/hibe 0x4c63c/0x4cb10/0x0000000000131413 er/hibe

scrd/scrd 0x4c63c/0x4c368/0x1718171813141314 ec/xART

pass/pass 0x4c63c/0x4cb10/0x1013141013141013 er/pass

sks /sks 0x4c63c/0x4c368/0x1314131413141314 ert/xART

sks /sksa 0x4c63c/0x4cb10/0x0000000013141013 er/sksa

hdcp/hdcp 0x4c63c/0x4cb10/0x1413141314131413 er/hdcp

stac/stac 0x4c63c/0x4cdb4/0x1417181718171817 er/stac

sbio/sbio 0x4c63c/0x4cb10/0x1413141314131413 er/sbio

sbio/blcx 0x4c63c/0x4d2a0/0x0000000000000f11 wn/----

sbio/---- 0x4c63c/0x4d2a0/0x0000000000000f11 wn/----

sse /sse 0x4c63c/0x4cb10/0x1413141314131413 er/sse

boop/boop 0x4c63c/0x4cb10/0x1413141314131413 er/boop

skdl/skdl 0x4c63c/0x4cb10/0x1413141314131413 er/skdl

Firmware type: UNKNOWN SEPOS

SEP state: 8

PM state: 2

Boot state: 32

Mailbox status:

IDLE_STATUS: 0x00000028

INBOX0_CTRL: 0x00026601

OUTBOX0_CTRL: 0x00029901

Mailbox entries:

Unavailable

Mailbox queue pointers: 28/28 -1/-1 -1/-1 -1/-1 -1/-1 -1/-1 -1/-1 -1/-1 23/23 -1/-1 15/15 -1/-1 2/2 -1/-1 11/11 -1/-1 0/0 -1/-1 26/26 9/9 0/0 24/24 -1/-1 5/5 2/2 -1/-1 -1/-1 -1/-1 -1/-1 -1/-1 -1/-1 -1/-1

TZ0 explicitly set 1 size 0x1c08000

TZ1 explicitly set 0 size 0x8000

Debugger message: panic

Memory ID: 0x1

OS release type: User

OS version: 25F84

Kernel version: Darwin Kernel Version 25.5.0: Tue Jun 9 22:18:58 PDT 2026; root:xnu-12377.121.10~1/RELEASE_ARM64_T6000

Fileset Kernelcache UUID: 32F4D28271521AC511D4722B289D8363

Kernel UUID: E977B940-FDD2-35CD-81B3-EC65AAB8BF5C

Boot session UUID: 7B3BB323-7201-44C9-B421-5D407834F08F

iBoot version: mBoot-18000.121.3

iBoot Stage 2 version: mBoot-18000.121.3

secure boot?: YES

roots installed: 0

Paniclog version: 15

Debug Header address: 0xfffffe001bfdd000

Debug Header entry count: 3

TXM load address: 0xfffffe002bf38000

TXM UUID: F0C1A57F-CE44-3DF4-9E86-0CFF02D7C00D

Debug Header kernelcache load address: 0xfffffe003bf38000

Debug Header kernelcache UUID: 32F4D282-7152-1AC5-11D4-722B289D8363

SPTM load address: 0xfffffe001bf38000

SPTM UUID: D249E718-9C0B-36F5-9F6B-24D58BED4606

KernelCache slide: 0x0000000034f34000

KernelCache base: 0xfffffe003bf38000

Kernel slide: 0x0000000034f3c000

Kernel text base: 0xfffffe003bf40000

Kernel text exec slide: 0x0000000039608000

Kernel text exec base: 0xfffffe004060c000

mach_absolute_time: 0x135ef1b987

Epoch Time: sec usec

Boot : 0x6a5b2a3d 0x0007708e

Sleep : 0x00000000 0x00000000

Wake : 0x00000000 0x00000000

Calendar: 0x6a5b37c1 0x0009de5d

Zone info:

Zone map: 0xfffffe121a000000 - 0xfffffe381a000000

. VM : 0xfffffe121a000000 - 0xfffffe17e6000000

. RO : 0xfffffe17e6000000 - 0xfffffe1a80000000

. GEN0 : 0xfffffe1a80000000 - 0xfffffe204c000000

. GEN1 : 0xfffffe204c000000 - 0xfffffe2618000000

. GEN2 : 0xfffffe2618000000 - 0xfffffe2be4000000

. GEN3 : 0xfffffe2be4000000 - 0xfffffe31b0000000

. DATA : 0xfffffe31b0000000 - 0xfffffe381a000000

Metadata: 0xfffffe1008010000 - 0xfffffe1011810000

Bitmaps : 0xfffffe1011810000 - 0xfffffe1014520000

Extra : 0 - 0

TPIDRx_ELy = {1: 0xfffffe2be6b2aba0 0: 0x0001000000000001 0ro: 0x0000000000000000 }

CORE 0: PC=0xfffffe00406a51b8, LR=0xfffffe00406a51b8, FP=0xfffffe950f00bee0

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

CORE 2: PC=0xfffffe00406a51b8, LR=0xfffffe00406a51b8, FP=0xfffffe950f0ebee0

CORE 3: PC=0xfffffe00406a51b8, LR=0xfffffe00406a51b8, FP=0xfffffe950ecebee0

CORE 4: PC=0xfffffe00406a51b8, LR=0xfffffe00406a51b8, FP=0xfffffe950f5bbee0

CORE 5: PC=0xfffffe00406a51b8, LR=0xfffffe00406a51b8, FP=0xfffffe950f56bee0

CORE 6: PC=0xfffffe00406a51b8, LR=0xfffffe00406a51b8, FP=0xfffffe950e91bee0

CORE 7: PC=0xfffffe00406a51b8, LR=0xfffffe00406a51b8, FP=0xfffffe950e9bbee0

CORE 8: PC=0xfffffe00406a51b8, LR=0xfffffe00406a51b8, FP=0xfffffe950ebbbee0

CORE 9: PC=0xfffffe00406a51b8, LR=0xfffffe00406a51b8, FP=0xfffffe950eafbee0

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

Panicked task 0xfffffe2517f8eb58: 0 pages, 595 threads: pid 0: kernel_task

Panicked thread: 0xfffffe2be6b2aba0, backtrace: 0xfffffe950edeb610, tid: 2176

lr: 0xfffffe004066457c fp: 0xfffffe950edeb6b0

lr: 0xfffffe00407e84ec fp: 0xfffffe950edeb720

lr: 0xfffffe00407e6464 fp: 0xfffffe950edeb7e0

lr: 0xfffffe0040611c40 fp: 0xfffffe950edeb7f0

lr: 0xfffffe0040664888 fp: 0xfffffe950edebd10

lr: 0xfffffe0040f68a78 fp: 0xfffffe950edebd30

lr: 0xfffffe003e8b4418 fp: 0xfffffe950edebd60

lr: 0xfffffe003e896af0 fp: 0xfffffe950edebd80

Note that I never even touched the Touch ID this time. I simply shut it down and before I even got the chance to do anything, it started right back up.

⟐ Commented Temmuz 18, 2026 at 7:05 GMT-7

]]> https://tr.ifixit.com/Answers/View/964244/Why+does+my+MacBook+hard+crash+after+opening+lid https://tr.ifixit.com/Answers/View/964244 Sat, 18 Jul 2026 07:05:07 -0700 <![CDATA[MacBook Pro 14" 2024 (M4 Pro and M4 Max): A heads up regarding the display... again!]]> Hi Folks

My 18 month old, MBP M4 Pro screen died. Took it to the ""Genius Bar"" to be told I had a faulty display!! Apparently this is quite a common fault with this model, my "genius" telling me he alone repairs at least four a day!!!!! If you're using this as intended and on a live event or important gig it may be worth having a spare USB C display to get you out of trouble (Command +F1 to switch).

The really annoying thing about the repair was that they wouldn't work on it unless it used the latest iteration of Mac OS, and threatened to wipe my hard drive before basically undoing some nuts and bolts and cables to replace the screen. I had to upgrade there and then to save the hassle of a later install from Time Machine.

This would've cost £623 to fix (I had AppleCare) BUT as I'm in the UK this was considered a 'Consumer Law Repair' which is up to 6 years in this country and also free.

⟐ Commented Temmuz 13, 2026 at 11:14 GMT-7

]]> https://tr.ifixit.com/Answers/View/963771/A+heads+up+regarding+the+display...+again! https://tr.ifixit.com/Answers/View/963771 Mon, 13 Jul 2026 11:14:00 -0700 <![CDATA[MacBook Pro 14" Late 2023 (M3): How to change Display Cable on MB P 14" late 2023]]> Resim

I have a 2" vertical strip on the left side of my screen that all of a sudden turned darker than the rest of my screen. It's tinted darker. I can still see the screen, but it flickers some, and at certain times I can vaguely see the browser's bookmark bar in the tinted section at the top. I can mirror the screen onto my TV, and the tinted strip isn't there. I did some research and think it may be the display cable. Does anyone have a repair guide for something like this?

⟐ Edited by author Temmuz 12, 2026 at 17:16 GMT-7

]]> https://tr.ifixit.com/Answers/View/963637/How+to+change+Display+Cable+on+MB+P+14%22+late+2023 https://tr.ifixit.com/Answers/View/963637 Sun, 12 Jul 2026 17:16:40 -0700 <![CDATA[MacBook Pro 14" 2021: Will swapping the battery show a 'service required' message?]]> Im planning on swapping the original battery on my 14" MacBook Pro as it's performance has degraded over the years, but I don't know if performing this will show the 'service required' message even after replacing it, similarly as is does when swapping out a display.

⟐ Answered Temmuz 02, 2026 at 14:53 GMT-7

]]> https://tr.ifixit.com/Answers/View/962251/Will+swapping+the+battery+show+a+'service+required'+message https://tr.ifixit.com/Answers/View/962251 Thu, 02 Jul 2026 14:53:07 -0700 <![CDATA[MacBook Pro 14" 2024 (M4 Pro and M4 Max): The hinge tight problem in my MacBook Pro]]> recently purchased a MacBook Pro m4, on the first day I was able to open my laptop lid using one finger. from second day onwards I was not able to open the lid with one finger. the hinges become tight when I used to open with one finger the base also come along with the lid. the one finger supremacy has gone. what will be the solution.

⟐ Answer edited Haziran 26, 2026 at 18:05 GMT-7

]]> https://tr.ifixit.com/Answers/View/961285/The+hinge+tight+problem+in+my+MacBook+Pro https://tr.ifixit.com/Answers/View/961285 Fri, 26 Jun 2026 18:05:42 -0700 <![CDATA[MacBook Pro 14" 2021: MacBook Pro 14” 2021 (A2442, M1 Pro) — Adding thermal pads on heatsink]]> Hi everyone,

I have a MacBook Pro 14-inch 2021 (A2442, M1 Pro) and I want to improve cooling with the easiest/safest method possible.

I don’t want to do a full logic board removal right now if I can avoid it. I’m planning the “add thermal pads” mod — placing high-conductivity thermal pads on top of the metal heatsink/radiator so heat transfers better to the aluminum bottom case (turning the whole bottom into an extra passive heatsink).

I’ve watched some of Your videos and others but there is not a video for my question (what i want).

My questions:

1.  For the easier bottom-case-only version, is 1.5mm or 2mm thick high W/mK pads (Thermalright / Gelid / Arctic style) the best choice? What size sheet should I get and where exactly on the heatsink should I place the pieces?

2.  I will leave Apple’s original grey paste on the main SoC and the black thermal gel (TCRS Carbon Black) on the RAM chips completely alone. I dont wanna touch them i want to add more too cool it down.

4.  What kind of real-world gains have people seen on the 14” M1 Pro specifically (temps, fan noise, sustained performance)?

5.  If the pad mod isn’t enough later, is the full heat sink replacement guide the right next step, and do you recommend Noctua NT-H2 or Arctic MX-6?

I will make pictures when i do this and share it with you here so people to know excactly what to do.

Update (06/25/26)

I want to share my exp. With the chat bot i think i have all answers to my questions i have what i need but you people can read as well and maybe my questions can help.

This is a conversation with AI asking question of how to apply thermal pads with Pics. And extra questions.

Venelin Valkanov

https://fixbot.ifixit.com/chat/f9a4e89e-...

Update (06/25/26)

Resim

Any ideas?

⟐ Answered Haziran 25, 2026 at 6:30 GMT-7

]]> https://tr.ifixit.com/Answers/View/961127/MacBook+Pro+14%E2%80%9D+2021+(A2442,+M1+Pro)+%E2%80%94+Adding+thermal+pads+on+heatsink https://tr.ifixit.com/Answers/View/961127 Thu, 25 Jun 2026 06:30:52 -0700 <![CDATA[MacBook Pro 14" 2025 (M5): Corrosion on right connector. Next to HDMI]]> There seems to be some water damage on the right side usb-c connector. Is it possible to have it changed? Is it removable or does the logic board have to be completely changed. The corrosion is just on the connector pins on the outside.

⟐ Answered Haziran 09, 2026 at 16:25 GMT-7

]]> https://tr.ifixit.com/Answers/View/958934/Corrosion+on+right+connector.+Next+to+HDMI https://tr.ifixit.com/Answers/View/958934 Tue, 09 Jun 2026 16:25:57 -0700 <![CDATA[MacBook Pro 14" Late 2024 M4: Screen Replaced, But Wifi and Bluetooth stopped working]]> Hi

I have MacBook Pro M4 A3112.(Nov'24). this is my first Macbook.

Initially display screen had some damage, so got the screen replaced and i notice both Wifi and Bluetooth has stopped working.

I took back to the repair guy who helped to replace the screen, but he has no clue why Wifi and Bluetooth are not working.

please find the attached the screenshots and photos I took as part of initial diagnosis I could do.

Please advise, what could be the issue and how to resolve this ?

Thanks

RB

Resim
Resim
Resim

Update (01/24/26)

Hi @danj

I did reformat whole Macbook and reinstalled OS. Seems issue still persists.

I connected the MacBook to my router using Rj45 cable with the help of connector so I can access wired network connection to internet.

However I tried to do offline diagnostic and I got the error CNW001 . Have attached screenshot.

Power charger wasn't connected to macbook when I ran the diagnostic so the error PPP020 can be ignored in the image here, as I see the MacBook is working fine when charger is connected.

Let me know what option i have to resolve this CNW001 error.

I am using wired connection for Internet for now, not a substantial solution.

Thanks

Resim

RB

Update (01/21/26)

Resim
Resim

I used an Ethernet cable and was able to connect to internet.

The pic was taken with ethernet cable on !

⟐ Commented Haziran 08, 2026 at 5:06 GMT-7

]]> https://tr.ifixit.com/Answers/View/936952/Screen+Replaced,+But+Wifi+and+Bluetooth+stopped+working https://tr.ifixit.com/Answers/View/936952 Mon, 08 Jun 2026 05:06:19 -0700 <![CDATA[MacBook Pro 14" 2021: Can I replace or fix the microphone?]]> The microphone on my M1 Macbook Pro is very muffled.

After some investigation, I'm fairly sure the problem is a blocked grille. But it's hard to identify which (if any) of the hundreds of dimples on the left-hand side are actual holes and therefore need cleaning. Is there any information on this?

⟐ Commented Haziran 06, 2026 at 9:59 GMT-7

]]> https://tr.ifixit.com/Answers/View/946416/Can+I+replace+or+fix+the+microphone https://tr.ifixit.com/Answers/View/946416 Sat, 06 Jun 2026 09:59:42 -0700 <![CDATA[Macbook Pro 14" 2023: Boot without Battery:Do new MacBooks boot with only the power supply?]]> Hi!

Unfortunately, I couldn't find any information about the new MacBooks; it seems the older models can boot up even without a battery.

Does anyone know for sure if the new MacBooks can also boot up without a battery, using a USB-C power adapter? I'm in the middle of a repair and want to check if the device is still alive.

Thanks a lot!!

⟐ Answered Haziran 03, 2026 at 17:44 GMT-7

]]> https://tr.ifixit.com/Answers/View/958084/Boot+without+Battery:Do+new+MacBooks+boot+with+only+the+power+supply https://tr.ifixit.com/Answers/View/958084 Wed, 03 Jun 2026 17:44:40 -0700 <![CDATA[MacBook Pro 14" 2021: 14-inch MacBook Pro display: Staingate issue]]> Hi everyone,

I am noticing an issue with the display on my 14-inch MacBook Pro (Model A2442). There is a subtle but noticeable color shift happening across the screen. When viewing a pure white background, the affected areas look off-white/grayish. On dark backgrounds, there are permanent "smudge" marks that do not wipe away with a microfiber cloth.

It looks like the anti-reflective coating is failing or peeling (Staingate)?

Has anyone successfully stripped the coating on this specific 14-inch model without damaging the Mini-LED backlight or glass?

Any insights or advice would be greatly appreciated!

Resim
Resim

⟐ Commented Mayıs 27, 2026 at 14:51 GMT-7

]]> https://tr.ifixit.com/Answers/View/956946/14-inch+MacBook+Pro+display:+Staingate+issue https://tr.ifixit.com/Answers/View/956946 Wed, 27 May 2026 14:51:04 -0700 <![CDATA[MacBook Pro 14" 2025 (M5): How can I add more RAM?]]> I only have 16 GB of RAM in my computer, but since I want to run AI's I want to have more ram is there a way I can take it apart and add more RAM or replace the ram that is in there with more.

⟐ Commented Mayıs 23, 2026 at 8:25 GMT-7

]]> https://tr.ifixit.com/Answers/View/952555/How+can+I+add+more+RAM https://tr.ifixit.com/Answers/View/952555 Sat, 23 May 2026 08:25:01 -0700 <![CDATA[MacBook Pro 14" Late 2024 M4: MacBook Pro M4 forcing sleep mode due to false thermal sensor]]> Hi everyone,

I’m facing a frustrating issue with my MacBook Pro M4 (purchased Feb 2025, AppleCare expired) and wanted to see if anyone has encountered this or found a workaround.

Whenever I open the lid—especially after it has been idle—the system behaves as if it’s under extreme thermal stress. It forces itself into sleep mode repeatedly (around 3 to 7 times in a row) before finally stabilizing and going back to normal.

There is no actual overheating, no high CPU usage, and no excessive fan noise.

After digging into the diagnostics, I managed to isolate the root cause. A specific thermal sensor, TDv (appearing as TD23 in the SMC logs), is stuck giving a false, static reading of 81 degree celsius. This erroneous spike is clearly causing the system to panic and force immediate sleep states to protect the hardware.

A factory reset did not change anything, as the issue is driven by this faulty sensor reading. I've attached my powermetrics logs and the diagnostic dump below.

Has anyone dealt with a single rogue sensor failing like this on an Apple Silicon Mac? Is there any known software method or tool to ignore/override a specific sensor input before I resort to a hardware repair?

Any insight would be highly appreciated.

Thermal Pressure Logs (sudo powermetrics)

Plaintext

**** Thermal pressure ****
Current pressure level: Moderate

**** Thermal pressure ****
Current pressure level: Sleeping

**** Thermal pressure ****
Current pressure level: Moderate

**** Thermal pressure ****
Current pressure level: Sleeping

**** Thermal pressure ****
Current pressure level: Nominal

**** Thermal pressure ****
Current pressure level: Heavy

**** Thermal pressure ****
Current pressure level: Sleeping

SMC Diagnose Extract (Rogue Sensor Evidence)

TD23 , 81.000961
TDVx , 81.000961
ftlx , 81.000252

⟐ Commented Mayıs 16, 2026 at 9:11 GMT-7

]]> https://tr.ifixit.com/Answers/View/955307/MacBook+Pro+M4+forcing+sleep+mode+due+to+false+thermal+sensor https://tr.ifixit.com/Answers/View/955307 Sat, 16 May 2026 09:11:00 -0700 <![CDATA[MacBook Pro 14" Late 2024 M4: How to remove iPhone notifications from MacBook?]]> I keep getting notifications that are meant for my Iphone, on my macbook. How do I disable my macbook from receiving the notifications mean for my Iphone?

⟐ Answer accepted Mayıs 11, 2026 at 14:47 GMT-7

]]> https://tr.ifixit.com/Answers/View/954494/How+to+remove+iPhone+notifications+from+MacBook https://tr.ifixit.com/Answers/View/954494 Mon, 11 May 2026 14:47:46 -0700 <![CDATA[MacBook Pro 14" Late 2023 (M3 Pro and M3 Max): No Sound, Keyboard/ trackpad not responding but keyboard lights up]]> Hi, I have this Macbook that won't respond with Keyboard / Trackpad inputs. Keyboard lights up and power button works.

Im not getting any sound from the speakers either but if I connect and bluetooth accessories it works straight away. The fans are also always on high speed.

Please help any solution is highly appreciated.

⟐ Commented Mayıs 04, 2026 at 14:46 GMT-7

]]> https://tr.ifixit.com/Answers/View/953138/No+Sound,+Keyboard-+trackpad+not+responding+but+keyboard+lights+up https://tr.ifixit.com/Answers/View/953138 Mon, 04 May 2026 14:46:57 -0700 <![CDATA[Macbook Pro 14" 2023: MacBook completely dead after battery discharge]]> Hi. I have an A2779 MacBook which was in good working order until the battery discharged. Now, the laptop will not boot despite being charged for several hours

I’ve tried entering DFU mode and it did not work.

There is no sound, and the display does not turn on at all. I had exactly the same issue with a slightly older MacBook, it really seems like this is a systematic issue. Does anyone have an idea if this is true and a possible fix?

]]> https://tr.ifixit.com/Answers/View/953226/MacBook+completely+dead+after+battery+discharge https://tr.ifixit.com/Answers/View/953226 Sun, 03 May 2026 01:47:30 -0700 <![CDATA[MacBook Pro 14": Disabling Haptics on trackpad]]> Hi, has anyone found a way to physically disable the Haptic actuator on the trackpad of the Macbook Pro M4? I am thinking about returning it unless I can find a way. The trackpad experience is awful because the haptics make the whole case rattle and feel tinny, even on the lightest setting.

⟐ Commented Nisan 17, 2026 at 16:02 GMT-7

]]> https://tr.ifixit.com/Answers/View/919290/Disabling+Haptics+on+trackpad https://tr.ifixit.com/Answers/View/919290 Fri, 17 Apr 2026 16:02:41 -0700 <![CDATA[MacBook Pro 14" 2021: macOS 26.4 charge limiter not working, possibly due to replacement bat]]> ]Not sure if this has been reported on or if I just have a weird bug but for the life of me I cannot get the battery charge limiter to work. I thought it would be nice since I rarely use it for more than a few hours at a time and figured it could save me the hassle of replacing the battery again, or at least offset it. Admittedly I do not know if it is due to the battery being aftermarket or if it is just modern macOS doing modern macOS things, so I am just seeing if anyone has similar issues.Edit:

Resim

⟐ Commented Nisan 07, 2026 at 19:53 GMT-7

]]> https://tr.ifixit.com/Answers/View/949174/macOS+26.4+charge+limiter+not+working,+possibly+due+to+replacement+bat https://tr.ifixit.com/Answers/View/949174 Tue, 07 Apr 2026 19:53:50 -0700