Overheated Macbook pro

Hello,

My 13-inch Macbook Pro, Mid 2010 overheated when incredibly hot watching a movie a few days ago. The screen froze and horizontal lines appeared. I switched off the laptop and left it to cool down. Since then it has gone though a series of stages. Initially the screen would appear with a kernel trap , type 14 with the word "panic" (image attached). Now it is starting up normally, I sent a report to Apple and am writing this post on it. However, it has since frozen again when not especially hot. I am writing to ask for recommendations of what to do next.


I was considering a hardware test to try (this is proving tricky because of the model - holding D and then option-D were unsuccessful at startup) and isolate the problem and replace any damaged parts, as well as cleaning out the fan inside. Or perhaps backing up my laptop (doing this anyway) and restarting OS X (currently running El Capitan 10.11.6) Does the community have any thoughts on this matter? Just looking to prolong the life of a well-loved machine.

MacBook Pro 13", OS X 10.11

Posted on Jul 22, 2019 9:30 AM

Reply
Question marked as Top-ranking reply

Posted on Jul 22, 2019 9:42 AM

That is a kernel panic due to page fault (a references to memory not owned by the task making the reference). It occurred with ethernet and USB mass storage drivers at the "scene of the crime".


--------

There are three quick take-aways from any panic report.


1) The panic-reason,


2) the kernel extensions present at the "scene of the crime", (shown in the " backtrace" which is the stored calling sequence of how you ended up where the panic occurred.)


3) the BSD process in which the problem occurred.


All these report are stored at:


/Library/logs/DiagnosticReports


... the appropriate ones are named with date&time and end in .panic


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.



Similar questions

9 replies
Question marked as Top-ranking reply

Jul 22, 2019 9:42 AM in response to charapita

That is a kernel panic due to page fault (a references to memory not owned by the task making the reference). It occurred with ethernet and USB mass storage drivers at the "scene of the crime".


--------

There are three quick take-aways from any panic report.


1) The panic-reason,


2) the kernel extensions present at the "scene of the crime", (shown in the " backtrace" which is the stored calling sequence of how you ended up where the panic occurred.)


3) the BSD process in which the problem occurred.


All these report are stored at:


/Library/logs/DiagnosticReports


... the appropriate ones are named with date&time and end in .panic


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.



Jul 23, 2019 2:22 PM in response to charapita

Runtime: 7:34 -- Performance: poor


Time Machine backup out-of-date - The last Time Machine backup is over 10 days old.


Failing hard drive - This machine has a hard drive that appears to be failing.


Adware - Adware detected.

Launchd: ~/Library/LaunchAgents/com.spigot.ApplicationManager.plist


Kernel panics - This system has experienced kernel panics. This could be a sign of hardware failure.

Two in last seven days, one is a name error (could be just a random failure) the other is a Page fault (as you reported)


Low disk space - This machine is running low on free hard drive space.


High battery cycle count - Your battery may be losing capacity.

1637 cycles when typical useful life is around 1000 cycles.



Jul 23, 2019 2:36 PM in response to Grant Bennet-Alder

So your old familiar Mac has a failing Hard drive, and a battery well past its prime. it does not look to have a pervasive RAM memory problem.


Regardless of what you decide to do, you need to connect your backup drive and allow Time Machine to complete a backup, so that you can have it up-to-date. You may need that backup very soon.


Time machine runs in the background, automatically, so you can allow it to run anytime. It should not interrupt your important work.


--------

Readers who have installed a 500-ish GB or larger SSD drive instead of a Rotating Magnetic drive report, "It's like getting a whole new computer". Cost is about US$80 and up in the US.


You are not especially short of RAM but you could install up to 16GB. Cost in the US is under US$45 per 8GB DIMM, and you can replace by the each DIMM. Be sure to deal with a Mac-centric vendor and you will get the correct parts and a lifetime warranty.


OWC.net has a replacement battery available for about US$100.

Jul 22, 2019 11:26 AM in response to charapita

Looking in the console for clues to something is a recipe for madness.


All these report are stored at:


/Library/logs/DiagnosticReports


... the appropriate ones are named with date&time and end in .panic


the reports are clear text and can be opened with TextEdit.


Copy and paste the directory-name above into:

Finder > Go menu > go to folder


Another way to get a summary of those and other problems is to run Etrecheck, change preferences to "allow full disk access" and run its report. A summary of these incidents in the last seven days is provided automatically at the end, no digging required.


Using EtreCheck - Apple Community


.

Jul 22, 2019 10:12 AM in response to Grant Bennet-Alder

So when looking on the console the find the reports you mentioned this is what I found from this morning. However, I wasn't able to find much more. It was a little bit of a word salad but I'm trying to figure it out.


Mon Jul 22 06:49:05 2019


*** Panic Report ***

panic(cpu 1 caller 0xffffff80105d0c0b): Kernel trap at 0xffffff80105850e2, type 14=page fault, registers:

CR0: 0x000000008001003b, CR2: 0xffffff80dba07f48, CR3: 0x0000000013be8000, CR4: 0x00000000000026e0

RAX: 0xffffff8010d11ac0, RBX: 0x0000000000000026, RCX: 0xffffff8010d11860, RDX: 0xffffff80dba07f40

RSP: 0xffffff811a573ad0, RBP: 0xffffff811a573ae0, RSI: 0xffffff801ba08f40, RDI: 0x0000000000000026

R8: 0x000000000000005a, R9: 0xffffff801ba07f00, R10: 0x0000000033a064f1, R11: 0x0000000000000035

R12: 0xffffff811a573c30, R13: 0x0000000000000000, R14: 0xffffff801ba055c0, R15: 0x0000000000000000

RFL: 0x0000000000010283, RIP: 0xffffff80105850e2, CS: 0x0000000000000008, SS: 0x0000000000000010

Fault CR2: 0xffffff80dba07f48, Error code: 0x0000000000000002, Fault CPU: 0x1, PL: 2


Backtrace (CPU 1), Frame : Return Address

0xffffff811a573760 : 0xffffff80104dbb52

0xffffff811a5737e0 : 0xffffff80105d0c0b

0xffffff811a5739c0 : 0xffffff80105eca63

0xffffff811a5739e0 : 0xffffff80105850e2

0xffffff811a573ae0 : 0xffffff8010576bb5

0xffffff811a573e60 : 0xffffff80109d87f6

0xffffff811a573e90 : 0xffffff7f9262163b

0xffffff811a573fb0 : 0xffffff80105cb257

Kernel Extensions in backtrace:

com.apple.iokit.IOEthernetAVBController(1.0.3b3)[90B4A715-9DB3-34BA-ADBA-5C5FE9467C0C]@0xffffff7fffde1000->0xffffff80fede7fff

dependency: com.apple.iokit.IONetworkingFamily(3.2)[848B398F-4D96-3024-8092-6CD3534D2CCA]@0xffffff7f917e5000

com.apple.driver.AppleUSBStorageCoexistentDriver((invalid))[D395406E-16A2-3771-8283-FAA62BEE5AC1]@0xffffff7fd2901000->0xffffff8092904fff

kmod dependency scan stopped due to missing dependency page: 0xffffff80260311e0

comnapple.BootCache(38.0)[C1EA21DC-CEC4-34EF-8172-8D217927D3EC]@0xffffff7f9261b000->0xffffff7f92624fff


BSD process name corresponding to current thread: kernel_task

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Overheated Macbook pro

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