820-00875 CPU overheats with battery connected

[tcampbell34]

I got an 820-00875 that is not liquid damaged but it overheats and shuts down randomly. I can boot the computer into the OS and it will works ok as long as I don't do anything that uses a lot of CPU power. Once the CPU gets up to like 30% or more, the CPU temps start going up and the computer will eventually reboot itself, or kernel panic. I figured out it only happens when the battery is connected though. If I unplug the battery, it works normally and does not overheat. I attached 2 screen shots from the CPU stress test app. One shows the test with the battery connected, and then other is the same test without the battery. You can see the CPU gets to over 90 Celsius after just a minute of the test, and it is only set to use 50% of the CPU. Without the battery, all temperatures stay low. I have tested the board in another case with a good battery, and same issue. The board is spotless so I am not sure where to look at what would be causing this.

 

[2informaticos]

Did PRAM reset?
Try another macOS installation, eventually USB one.

 

[tcampbell34]

Yes I did a PRAM reset but it did not help. I have also tried another internal SSD and booted from and external drive and it still does the same thing.

 

[piernov]

Nothing wrong with 90°C. If CPU stays at 100°C or above with fan at full speed under load, then you have a problem. If it stays below 100°C then everything is fine with cooling system.
You can use Intel Power Gadget to monitor CPU temp, usage and frequency to see the boosting behaviour on battery and when AC adapter is connected.

 

[2informaticos]

I saw you get two 128 temps, even without battery.
Compare these values with a good working board.

 

[Askaleto]

It is very interesting to see that at 90 °C, fan is still below 2000 rpm. Is this normal on Macbook pro? Doesn't seem like it is.

 

[piernov]

The fan profiles are always very conservative on MacBooks so the fan only runs at full speed if it gets close to throttling.

 

[tcampbell34]

The two temps that are at 128 Celsius are normal for this board model. The fans do start to spin faster after 2 or 3 minutes, but it never gets up to full speed or even above 3000 rpm. I don't think the issue is with the cooling system, but there is definitely some issue with the battery connected that causes the CPU to get hotter then usual. I tried to install Big Sur with the battery connected and the CPU gets really really hot, to where I will burn my finger if I keep my finger there even for a second. The computer will also reboot constantly during the install or sometimes kernel panic, and then it starts again back at 29 minutes remaining. I have only made it to like 22 minutes remaining with the battery connected before it reboots itself. Without the battery connected, the install runs fine and the CPU does not really get that hot. I can hold my finger on the heatsink for multiple seconds without burning my finger. Shouldn't the CPU basically be the same temp with or without the battery installed?

 

[2informaticos]

CPU clock should be different.
It probably run faster with both charger and battery connected.
However, the mentioned behaviour is not normal.
Machine shouldn't restart in that way.
Try known good BIOS, clean ME.

 

[piernov]

When the battery is disconnected inside a MacBook, in general the CPU cannot use Turbo Boost. Even worse, it may be throttled below the base frequency. Intel Power Gadget should make it clear if boost is working or not.

If the machine crashes only when hitting boost clock, there's probably a power delivery issue to the CPU (for example one phase not working properly or too much ripple) or the CPU is dying.

 

[tcampbell34]

I have tried a good BIOS with Clean ME but its still the same. I cannot install the OS with the battery connected. It just reboots and restarts the install. The computer will run from my external SSD and everything seems fine, but it does randomly still reboot or kernel panic only when the battery is connected. Maybe the issue is not actually the CPU overheating, but something is not right with this board. The CPU gets to 90c and then the fans kick in a little harder and it cools it down to about 80c. Here is the report I got from the last kernel panic.

panic(cpu 1 caller 0xffffff80065ed0e6): Kernel trap at 0xffffff8006b8fa85, type 14=page fault, registers:
CR0: 0x0000000080010033, CR2: 0xffffff7f8a133014, CR3: 0x000000045c6be016, CR4: 0x00000000003626e0
RAX: 0x0000000000000000, RBX: 0xffffffa024269000, RCX: 0xffffffb0ad46b868, RDX: 0x00000000e1000000
RSP: 0xffffffb0ad46b850, RBP: 0xffffffb0ad46b8b0, RSI: 0xffffff7f8a134000, RDI: 0xffffff8023ffdf00
R8: 0xffffff7f8a134000, R9: 0x0000000008000000, R10: 0x0000000000024000, R11: 0x0000000000000001
R12: 0xffffffb0ad46b958, R13: 0x0000000000000000, R14: 0xffffff7f8a133000, R15: 0x0000000003322000
RFL: 0x0000000000010246, RIP: 0xffffff8006b8fa85, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0xffffff7f8a133014, Error code: 0x0000000000000000, Fault CPU: 0x1, PL: 0, VF: 10

Backtrace (CPU 1), Frame : Return Address
0xffffffb0ad46b270 : 0xffffff80064b9aed
0xffffffb0ad46b2c0 : 0xffffff80065fc6e3
0xffffffb0ad46b300 : 0xffffff80065ecd1a
0xffffffb0ad46b350 : 0xffffff800645ea2f
0xffffffb0ad46b370 : 0xffffff80064b938d
0xffffffb0ad46b490 : 0xffffff80064b9678
0xffffffb0ad46b500 : 0xffffff8006cbe3ca
0xffffffb0ad46b570 : 0xffffff80065ed0e6
0xffffffb0ad46b6f0 : 0xffffff80065ecdcd
0xffffffb0ad46b740 : 0xffffff800645ea2f
0xffffffb0ad46b760 : 0xffffff8006b8fa85
0xffffffb0ad46b8b0 : 0xffffff8006b8ebd5
0xffffffb0ad46b930 : 0xffffff8006b8ed5b
0xffffffb0ad46b9c0 : 0xffffff8006b9cb3c
0xffffffb0ad46bbe0 : 0xffffff8006b9c304
0xffffffb0ad46bc40 : 0xffffff8006b9a848
0xffffffb0ad46bcc0 : 0xffffff8006bad88b
0xffffffb0ad46bd40 : 0xffffff800651ec1b
0xffffffb0ad46bd90 : 0xffffff80064bf0e7
0xffffffb0ad46be00 : 0xffffff8006495905
0xffffffb0ad46be60 : 0xffffff80064ad012
0xffffffb0ad46bef0 : 0xffffff80065d0ec3
0xffffffb0ad46bfa0 : 0xffffff800645f216

Process name corresponding to current thread: kernelmanagerd

Mac OS version:
20C69

Kernel version:
Darwin Kernel Version 20.2.0: Wed Dec 2 20:39:59 PST 2020; root:xnu-7195.60.75~1/RELEASE_X86_64
Kernel UUID: 82E2050C-5936-3D24-AD3B-EC4EC5C09E11
KernelCache slide: 0x0000000006200000
KernelCache base: 0xffffff8006400000
Kernel slide: 0x0000000006210000
Kernel text base: 0xffffff8006410000
__HIB text base: 0xffffff8006300000
System model name: MacBookPro13,1 (Mac-473D31EABEB93F9B)
System shutdown begun: NO
Panic diags file available: NO (0xe00002bc)
Hibernation exit count: 0

System uptime in nanoseconds: 15267279395
Last Sleep: absolute base_tsc base_nano
Uptime : 0x000000038e003687
Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000
Wake : 0x0000000000000000 0x0000001f5ac94810 0x0000000000000000
last started kext at 1458452931: |SCSITaskUserClient 436.40.6 (addr 0xffffff8008eca000, size 20480)
loaded kexts:
|SCSITaskUserClient 436.40.6
>!ATopCaseHIDEventDriver 4020.6
@filesystems.apfs 1677.60.23
>!AFileSystemDriver 3.0.1
@filesystems.tmpfs 1
@filesystems.hfs.kext 556.60.1
@BootCache 40
@!AFSCompression.!AFSCompressionTypeZlib 1.0.0
@!AFSCompression.!AFSCompressionTypeDataless 1.0.0d1
>AirPort.BrcmNIC 1400.1.1
@private.KextAudit 1.0
>!ASmartBatteryManager 161.0.0
>!AACPIButtons 6.1
>!ARTC 2.0
>!ASMBIOS 2.1
>!AACPIEC 6.1
>!AAPIC 1.7
@!ASystemPolicy 2.0.0
@nke.applicationfirewall 310
|IOKitRegistryCompatibility 1
|EndpointSecurity 1
>usb.cdc 5.0.0
>usb.networking 5.0.0
>usb.!UHostCompositeDevice 1.2
>!AActuatorDriver 4400.28
>!AHIDKeyboard 222
>!AMultitouchDriver 4400.28
>!AInputDeviceSupport 4400.35
>!AHS!BDriver 4020.6
>IO!BHIDDriver 8.0.2f9
>!AHSSPIHIDDriver 61
>!AThunderboltDPInAdapter 8.1.4
>!AThunderboltDPAdapter!F 8.1.4
>!AThunderboltPCIDownAdapter 4.1.1
>!AHPM 3.4.4
>!A!ILpssI2C!C 3.0.60
>!AXsanScheme 3
>!ABSDKextStarter 3
|IOSurface 289.3
@filesystems.hfs.encodings.kext 1
>!AHSSPISupport 61
>!AThunderboltNHI 7.2.8
|IOThunderbolt!F 9.3.2
>!A!ILpssSpi!C 3.0.60
>!A!ILpssDmac 3.0.60
|IO80211!F 1200.12.2b1
|IOSkywalk!F 1
>mDNSOffloadUserClient 1.0.1b8
>corecapture 1.0.4
|IONVMe!F 2.1.0
>usb.!UHostPacketFilter 1.0
|IOUSB!F 900.4.2
>!A!ILpssI2C 3.0.60
>!A!ILpssGspi 3.0.60
>usb.!UXHCIPCI 1.2
>usb.!UXHCI 1.2
>!AEFINVRAM 2.1
>!AEFIRuntime 2.1
|IOSMBus!F 1.1
|IOHID!F 2.0.0
$!AImage4 3.0.0
|IOTimeSync!F 900.11
|IONetworking!F 3.4
>DiskImages 493.0.0
|IO!B!F 8.0.2f9
|IOReport!F 47
|IO!BPacketLogger 8.0.2f9
$quarantine 4
$sandbox 300.0
@kext.!AMatch 1.0.0d1
|CoreAnalytics!F 1
>!ASSE 1.0
>!AKeyStore 2
>!UTDM 511.60.2
|IOUSBMass!SDriver 184.40.6
|IOSCSIBlockCommandsDevice 436.40.6
|IO!S!F 2.1
|IOSCSIArchitectureModel!F 436.40.6
>!AMobileFileIntegrity 1.0.5
@kext.CoreTrust 1
>!AFDEKeyStore 28.30
>!AEffaceable!S 1.0
>!ACredentialManager 1.0
>KernelRelayHost 1
|IOUSBHost!F 1.2
>!UHostMergeProperties 1.2
>usb.!UCommon 1.0
>!ABusPower!C 1.0
>!ASEPManager 1.0.1
>IOSlaveProcessor 1
>!AACPIPlatform 6.1
>!ASMC 3.1.9
|IOPCI!F 2.9
|IOACPI!F 1.4
>watchdog 1
@kec.pthread 1
@kec.corecrypto 11.1
@kec.Libm 1

 

[2informaticos]

Probably bad CPU.
The shutdown point is calculated from all sensors combined and depends also by CPU frequency at that time.

 

[tcampbell34]

Update on this one. I tested it for a few days and found the issue seems to be with the SSD and not with the computer overheating. Every time it would kernel panic, the report would say the same thing, nvme: "Fatal error occurred". I downloaded the program Disk Speed Test and tried to run a test, and it would freeze and kernel panic every time. I swapped the SSD and now everything seems to be working fine. Thanks for the assistance

 

[2informaticos]

Thanks for feedback.
Really strange issue, can help other members in the future.

 

[Askaleto]

Tcampbell, can you please specify in which report you read nvme: Fatal error? I cannot see this in the kernel panic report posted earlier.

 

[tcampbell34]

Take a look at this https://forums.macrumors.com/threads/persistent-nvme-kernel-panics-on-macbook-pro-13-2017.2251610/

I found this while looking into the error. The kernel panic I posted earlier was also one that I got, but that is not the same kernel panic which stated the nvme error, and I only got that once or twice. Majority of the time the KP looks just like the one in that post with the nvme: "Fatal error occurred" in the first line.