Ever since the last MacOS update, my MacBook has been overheating very easily, very often. When this happened in the past, I would simply put it in the freezer for a few minutes and then pull it out and get back to work. Now something strange is happening: The MacBook itself will be ice-cold, but unlike before when it would just resume working wonderfully, now it "sort of" works, but not really. For example synching stops and says "It needs to wait until the temperature drops". I installed an app to see what's going on and it's reading the CPU at 190º+ F and the GPU at 200º+. Why? How could anything inside be that hot when the frame itself is ice cold?
leakycap|7 months ago
The way macOS/ firmware handles cooling can be confusing. Have you tried rebooting in single user mode and checked the temps from there? Have you ran the hardware diagnostics from boot?
GWBullshit|7 months ago
Having said that I've had this model for quite a while now and have been doing this since I can remember and never had this issue until the latest macOS update, which from what I've researched seems to be affecting loads of people with all sorts of newer, much fancier processors than what I have.
While I will definitely keep your advice in mind going forward, it seems that this issue sprung up only after this last update, which is strange because I remember reading something about "improved energy management" or some such.
apothegm|7 months ago
GWBullshit|7 months ago
_wire_|7 months ago
GWBullshit|7 months ago
Just not sure how the processor definitely works very smooth, very fast, just like as if I restarted it whenever I take it out of the fridge, but the sensor is somehow reading ~200º.
aurizon|7 months ago
GWBullshit|7 months ago
Regardless, I'm still unsure how it can read these temperatures since the "put in freezer for a while" method seems to work when it does this and everything gets "un-sluggish" right away and starts working as well as if I restart it, no matter how many things are open.
So it's like the processor "works as if it wasn't overheating", but for some reason the temperature readings for things like synching sometimes don't work because it reads the temp as approaching ~200º, and even external apps read it as such (though I realize they may just be repeating an internal OS error).