Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

dsim87

macrumors member
Original poster
Feb 7, 2008
38
0
Early 2011 MBP running High Sierra 10.13.6. SSD. 16GB RAM (max) Security Update 2020-002 applied on 5/10/20 and MBP has been unusable ever since. It took 40 minutes just to boot up and get to the Apple Support pages before I decided to borrow another laptop to post this message.



kernel_task is at 3.4% when it is usable and 48.1% when frozen as I type this message. It is currently using 1.1GB of Memory



I have performed the following:

Restart

Reset SMC

Reset PRAM/NVRAM

Booted into Safe Mode and had same issue

Repair Disk without any issues found

Ran full Apple Hardware test with no issues found

Ran Onyx to clean up MBP

Deleted System Cache folder

Uninstalled Flash Player

Time Machine does not have a local snapshot prior to the 2020-02 update

Booted into recovery mode to reinstall macOS and I get a "Request Timed Out" error



Able to perform tasks for appx 10 seconds before I recieve the Spinning Wheel and MBP freezes for 2-3 minutes. Sometimes when MBP is frozen I can move the mouse icon without an issue.



Any solutions other than waiting for the next Update or buying a new hard drive to try a fresh install?
 
Last edited:

Analias

macrumors regular
May 13, 2019
134
47
Sounds like a sensor error. The usual suspects for this sort of behaviour in a 2011 is webcam, battery or sata cable. Running ASD would narrow it down, AHT is next to useless. Webcam would be my number 1 suspect though, try disconnecting it and see what happens.
 

Audit13

macrumors 604
Apr 19, 2017
6,897
1,840
Toronto, Ontario, Canada
Is it possible that the sata hard drive cable is bad?

It's a lot of work but replace the SSD with a mechanical drive but a cable can work fine with a spinning drive.
 

justashooter

macrumors 6502
Apr 8, 2020
335
194
To check your SATA cable you could take the boot drive out, put it in an external usb enclosure, boot from it. If it works I would say your SATA cable is bad. It would be quite a coincidence happening at the same time as the update, but it is possible. My 2012 MBP 13 acted like that when the sata cable went bad.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.