Перейти к основному содержанию

2010 MacBook Pro shutdown during boot (OS is good)

It is the 2.66 GHz Core i7 model. I say it is not the OS because it crashes with two different OSX boot disks and during OSX recovery mode. Have tried the following:

  • Sent it to a shop to have the bad capacitor on the logic board replaced. I previously had the capacitor overheat issue but the symptom was different: under GPU load the laptop _rebooted_. The current symptom is a complete power down: it never powers back up to show a panic screen.
  • Booting with each of the RAM sticks one at a time
  • NVRAM clear and SMC reset startups
  • Single user mode (runs for 30s or so before shutting down)
  • Verbose mode: shuts down during a different log message each time
  • Safe mode: typically gets to login screen then shuts down shortly after
  • Recovery mode: shuts down a few seconds into the recovery
  • Replaced the hard drive with another OSX drive: same symptoms
  • Replaced the hard drive with Windows bootable drive (boot menu then BSOD)
  • Target disk mode: stays up as long as I want it to be up
  • Searched for panic files while in target disk mode: found recent startup logs but no panic logs
  • Ran Apple Hardware Test: quick test and long test passed
  • Froze computer in freezer for one hour: shut down in same amount of time during boot
  • Boot from High Sierra installer USB stick: shutdown during boot

What I have not tried:

  • Repaste the heatsink (ordering paste today). I live in a dry climate which might aggravate heatsink paste drying out?
  • Remove battery

One frustrating thing is that ifixit.com has a procedure for replacing the heatsink paste but does not describe the symptoms that would lead you to execute that difficult procedure. Obviously if you can run the laptop long enough to read temperature sensors you would know it was overheating. Does overheat shutdown occur _before_ the system would record a panic?

FWIW, this question is similar to: MacBook Pro turns on, shows Apple logo or desktop, and cuts out.

Отвечено! Посмотреть ответ У меня та же проблема

Это хороший вопрос?

Оценка 0
2 Комментариев

Granted, the OP didn't accept the answer from the other question. But @originalmachead did answer! And it was reasonable answer!

из

Thanks. (I didn't scroll far enough the first time.) The upshot is a recommendation to repaste the chips under the heatsink.

из

Добавить комментарий

2 Ответов

Выбранное решение

I sent this laptop to a second shop for repair. They told me the logic board was ok but the keyboard was bad. They said the first indication of the keyboard failure was no response to the brightness keys. In the 30-60 seconds that it would run I never noticed a problem with the keys but never tried to adjust the brightness.

After the repair, the laptop works normally: and the cap overheat Nvidia GPU problem is gone, due to the repair from the first shop.

@Dan has been trying to work out a model for the root cause. It seems that as heat (or charges?) built up it triggered the keyboard failure: some short or false button press combo that led to shutdown. It is interesting that target disk mode and AHT were able to keep running. My guess is that either they don’t activate the keyboard the same way or they don’t generate enough heat to trigger the failure.

Был ли этот ответ полезен?

Оценка 0
Добавить комментарий
Наиболее полезный ответ

First Target Disk Mode uses the the Intel Graphics engine Vs the NVIDIA GeForce GT 330M GPU and it still uses the CPU for either, granted its not heavy taxed.

So that is a very powerful diagnostic clue! With the rest of your symptoms it’s clear the NVIDIA GPU is failing.

Here’s a good write up on the issues with the NVIDIA GPU Cures for a panicking mid-2010 MacBook Pro sadly Apple pulled the Tech Note HT203554 which offered more information. There really isn’t anything else you can do other than replace the logic board.

Update (11/14/2020)

Let me re-phrase... If you have already replaced the cap, then you need a new logic board to get the NVIDIA GPU working, otherwise you'll disable it which in this series really limits the graphics performance as the Intel HD graphics engine is not very good.

The 2011 boards have the AMD Radeon HD 6750M or 6770M GPU and Intel HD Graphics 3000, the 2012 model has the NVIDIA GeForce GT 650M and Intel HD Graphics 4000!

The root issue is people push the graphics with newer more powerful apps which this series was not expected to run.

Был ли этот ответ полезен?

Оценка 2

11 Комментариев:

Not sure why you say there is nothing you can do about the panic issue. There are dozens of posts saying that replacing the bad capacitor on the logic board fixes the panics. In my case the capacitor is _supposed_ to have been replaced and there are no panics (prior to this boot problem and prior to the repair I got the panics if I did not use a utility to switch off the Nvidia GPU). The 2011 models have a different GPU issue which, I think, does require a logic board replacement. This one has the Nvidia GT 330M

из

Thanks for the clarification, Dan. Before I spend $300 on a logic board I want to be sure its a clear diagnosis. So AHT and Target disk mode never "touch" the Nvidia GPU while single user mode, which displays nothing but text, somehow "touches" the GPU and causes the system to shut down. The shutdown in single user mode casts some doubt in my mind: I guess there could be a GPU driver process starting up in the background after the prompt appears in single user mode. Also wouldn't AHT test the GPU? That seems like a serious shortcoming in a hardware diagnostic tool.

из

@nmgeek - The issue is one of which driver is loaded. What is held in the firmware or what is loaded from within the system files. Target Disk Mode & Boot Manager, as well as the onboard diagnostics use the firmware Intel graphics driver,

Think of it this way if the system didn't have a drive available what would be used? Only the firmware graphics which only load the Intel graphics engine.

из

@Dan, excellent explanation: Intel graphics uses a "driver" built into firmware but the Nvidia GPU requires an OS kernel driver. I just booted up ASD, a hardware diagnostic that actually tells you which hardware it is testing. With an ASD EFI boot there is no GPU test (since it cannot run the OS driver in this mode). I do find it counter-intuitive that safe mode loads the GPU driver: its not "safe enough" for my purposes. Could you edit the answer text with your "rephrase" correction? Then I will mark it as the accepted answer.

из

Addendum: I thought if I disabled the discrete Nvidia GPU (dGPU) then I could boot OSX to prove it is the dGPU that is bad. I tried booting into Arch Linux as per https://apple.stackexchange.com/a/285896... but I get a black screen. It also will not start the EFI shell. I plan to find a logic board seller who will accept a return if the new logic board does not fix it.

из

Показать 6 больше комментариев

Добавить комментарий

Добавьте свой ответ

Glenn будет вечно благодарен.
Просмотр статистики:

За последние 24часов: 0

За последние 7 дней: 0

За последние 30 дней: 3

За всё время: 251