You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Latest Sierra update crashed my MPB

Hi,


This is the second time i get in trouble after updating my OSX!

I make clean installs now and then so my MBP is very clean and i don't have much on it, basically use it for surfing nowadays.

Any how yesterday when i updated from App Store it rebooted my computer and all i saw what this sign:

https://dl.dropboxusercontent.com/u/33591942/OSX%20Sierra%20crash/2017-02-15%202 2.10.31.jpg


After more digging i got to see these errors in the background:

https://dl.dropboxusercontent.com/u/33591942/OSX%20Sierra%20crash/2017-02-15%202 2.11.05.jpg


ERROR!!! prelinked kernel corrupted

ERROR!!! Load prelinked kernel with status 0x800000000000001b

Error loading kernel cache (0x1b)


What is this all about!?!? i tried to repair using disk utility and macOS Recovery where it did not allow me to continue and install again.

Got some other error:

https://dl.dropboxusercontent.com/u/33591942/OSX%20Sierra%20crash/2017-02-15%202 2.45.08.jpg


It was only when i used my USB stick i had created with previous OSX version and run the disk utility and repair that i could finally get back into the computer. No idea what the **** it was all about but honestly i'm scared doing more OSX updated now. They seem to mess up to many times. Last time i also could not get into the OSX, don't remember how i fixed that but it was also scary.


Did anyone else encounter this problem?

Also should i do some check to see if something is broken? if so how do i do that? Don't want to reboot later and get into the same mess.


Personally i get a feeling that the quality has been worse with every software Apple releases these days. From iOS updates to OSX updates. Maybe i'm wrong but thats just my guts feeling.

macOS Sierra (10.12.3)

Posted on Feb 16, 2017 8:06 AM

Reply
18 replies

Feb 19, 2017 7:21 PM in response to shadow

It is very likely that a hardware fault is the cause of your problems; specifically, that Mac's hard disk drive. Disk Utility is of limited use for such diagnoses, leaving only anecdotal methods. The problems you describe strongly support that hypothesis. For example, you wrote that you attempted to use Disk Utility to "repair" it, and attempting to reinstall macOS did not allow you to continue. You also wrote that you experienced similar problems in the past. Lastly, its age is reason to question the hard disk drive's integrity.


Since Sierra introduced a completely new logging system, I do not know of a reliable way to diagnose potential hard disk problems. Disk Utility will not suffice. Until I come across a disk in a state of failure yet operational enough to test I can't provide a means of extracting any applicable log entries that could definitively show those failures. A definitive conclusion could be drawn by installing Sierra on an external hard disk drive, booting from it, and determining if the symptoms are alleviated while running Sierra from that startup disk. To do that read How to set up and use an external Mac startup disk - Apple Support. If the external hard disk installation of Sierra works properly while the internal one does not, that is all the justification you need to replace the internal drive.


Hard disk drives are wear items that should be replaced when they become unreliable. Fortunately they are inexpensive and easy to replace on a MPB. Unfortunately, it has become abundantly clear that Apple is no longer interested in using them in any of their products, and that support for them is likely to diminish if it has not already disappeared altogether.

Feb 19, 2017 2:52 PM in response to dialabrain

ehmmm ok how do you come to that conclusion? Just because its 7 years old does not automatically mean its HW problem. Where did you draw the line. Seriously i want to get help from someone who knows more about the errors i provided and solution to them.


And if it was HW problem it would not magically solve itself when i run firstaid from an old start disk.

So no i dont believe its HW problem sorry.


ps. I ran the Hw test without finding problem also.

Feb 20, 2017 12:44 PM in response to John Galt

@John Galt

Thanks for the detailed explanation. I should have said that i use a Samsung 950 Pro SSD. So that is one reason i did not consider the wear and tear but sure it can be the SSD as well. They do break.

Just not sure else i can test it properly and determine if its in good condition.

Any good program to recommend?


@dialabrain:

I appreciate your help but being a computer nerd myself i like to know more about people analysis. I should have said the SSD i made a few year back but please dont take it in a wrong way. I do appreciate the help but i like to understand why people come to a conclusion.

Feb 20, 2017 1:25 PM in response to shadow

Using an external startup disk, one that is known to be operational, will be instructive. If it works, swap it with the internal one. If the problem follows the SSD, you found the culprit.


I do not know of any utility that would be particularly useful to diagnose a problem with it. I have seen such things report failures with perfectly good drives, as well declare broken ones perfectly OK.


Samsung SSDs do not enjoy a particularly good reputation among Mac users. If it requires a firmware update, which is possible, you need a Windows PC (as far as I know).

Feb 20, 2017 1:26 PM in response to shadow

shadow wrote:


@dialabrain:

I appreciate your help but being a computer nerd myself i like to know more about people analysis. I should have said the SSD i made a few year back but please dont take it in a wrong way. I do appreciate the help but i like to understand why people come to a conclusion.

FWIW, I came to the "conclusion" because I believed you when you said you had made clean installs and were still having a problem. You stated what errors you were getting and that often points to a hardware issue as John explained. Simple as that.

Feb 20, 2017 4:34 PM in response to dialabrain

I think we misunderstood each other.

I have never had any problem after install or anything. I encounter this specific crash once and another crash that was different from this. Both times (maybe there was one more but not sure) it happened right after making appstore update to the OSX.

Like now i dont see the problem so changing the drive dont do anything really. I could boot from external drive and do HD or rather SSD testing if i knew any good software. Will google for it.

Still the errors are a mystery. I read about them of other forums but no one explain exactly what cause it and why.

Feb 20, 2017 8:44 PM in response to shadow

Try running this program in your normal account, then copy and paste the output in a reply. The program was created by etresoft, a frequent contributor. Please use copy and paste as screen shots can be hard to read. On the screen with Options, please open Options and check the bottom 2 boxes before running. Click “Share Report” button in the toolbar, select “Copy Report” and then paste into a reply. This will show what is running on your computer. No personal information is shown.

Etrecheck – System Information

Feb 23, 2017 2:38 AM in response to shadow

And here is the report made by the tool (and with the 2 checkboxes checked):

--------------

EtreCheck version: 3.1.5 (343)

Report generated 2017-02-23 11:34:50

Download EtreCheck from https://etrecheck.com

Runtime 1:47

Performance: Excellent


Click the [Support] links for help with non-Apple products.

Click the [Details] links for more information about that line.


Problem: Other problem


Hardware Information: ⓘ

MacBook Pro (15-inch, Mid 2010)

[Technical Specifications] - [User Guide] - [Warranty & Service]

MacBook Pro - model: MacBookPro6,2

1 2,66 GHz Intel Core i7 (i7) CPU: 2-core

8 GB RAM Upgradeable - [Instructions]

BANK 0/DIMM0

4 GB DDR3 1067 MHz ok

BANK 1/DIMM0

4 GB DDR3 1067 MHz ok

Bluetooth: Old - Handoff/Airdrop2 not supported

Wireless: en1: 802.11 a/b/g/n

Battery: Health = Normal - Cycle count = 560


Video Information: ⓘ

Intel HD Graphics

NVIDIA GeForce GT 330M - VRAM: 512 MB

Color LCD 1680 x 1050


System Software: ⓘ

macOS Sierra 10.12.3 (16D32) - Time since boot: about 7 days


Disk Information: ⓘ

Samsung SSD 840 PRO Series disk0 : (256,06 GB) (Solid State - TRIM: No)

[Show SMART report]

EFI (disk0s1) <not mounted> : 210 MB

Recovery HD (disk0s3) <not mounted> [Recovery]: 650 MB

Macintosh HD (disk1) / [Startup]: 254.85 GB (130.35 GB free)

Core Storage: disk0s2 255.20 GB Online


MATSHITADVD-R UJ-898 ()


USB Information: ⓘ

Apple Card Reader

Apple Inc. Apple Internal Keyboard / Trackpad

Apple Inc. BRCM2070 Hub

Apple Inc. Bluetooth USB Host Controller

Apple Computer, Inc. IR Receiver

Apple Inc. Built-in iSight


Gatekeeper: ⓘ

Mac App Store and identified developers


Kernel Extensions: ⓘ

/Library/Extensions

[loaded] com.getdropbox.dropbox.kext (1.8.6 - SDK 10.11 - 2017-02-16) [Support]


System Launch Agents: ⓘ

[not loaded] 8 Apple tasks

[loaded] 169 Apple tasks

[running] 103 Apple tasks


System Launch Daemons: ⓘ

[not loaded] 42 Apple tasks

[loaded] 166 Apple tasks

[running] 103 Apple tasks


Launch Daemons: ⓘ

[loaded] com.adobe.fpsaud.plist (2017-01-30) [Support]

[loaded] com.microsoft.office.licensingV2.helper.plist (2015-09-11) [Support]


User Launch Agents: ⓘ

[loaded] com.dropbox.DropboxMacUpdate.agent.plist (2017-02-22) [Support]


User Login Items: ⓘ

iTunesHelper Application (2017-01-29)

(/Applications/iTunes.app/Contents/MacOS/iTunesHelper.app)

Dropbox Application

(/Applications/Dropbox.app)

CopyLess Application

(/Applications/CopyLess.app)


Internet Plug-ins: ⓘ

Silverlight: 5.1.41212.0 - SDK 10.6 (2016-01-26) [Support]

FlashPlayer-10.6: 24.0.0.221 - SDK 10.9 (2017-02-19) [Support]

QuickTime Plugin: 7.7.3 (2016-12-15)

Flash Player: 24.0.0.221 - SDK 10.9 (2017-02-19) [Support]


Safari Extensions: ⓘ

Adblock Plus - Eyeo GmbH - https://adblockplus.org/ (2016-12-23)


3rd Party Preference Panes: ⓘ

Flash Player (2017-01-30) [Support]


Time Machine: ⓘ

Time Machine not configured!


Top Processes by CPU: ⓘ

14% firefox

6% WindowServer

3% fontd

2% kernel_task

1% com.apple.AmbientDisplayAgent


Top Processes by Memory: ⓘ

2.26 GB firefox

669 MB kernel_task

197 MB Dropbox

197 MB mdworker(10)

172 MB WindowServer


Virtual Memory Information: ⓘ

2.30 GB Available RAM

44 MB Free RAM

5.70 GB Used RAM

2.26 GB Cached files

344 MB Swap Used


Diagnostics Information: ⓘ

Feb 22, 2017, 10:19:55 AM /Library/Logs/DiagnosticReports/firefox_2017-02-22-101955_[redacted].cpu_resour ce.diag [Details]

/Applications/Firefox.app/Contents/MacOS/firefox


--------------


As usual Firefox is a huge memory drain 😀

Feb 23, 2017 4:40 AM in response to shadow

shadow wrote:


... I should have said that i use a Samsung 950 Pro SSD.


That report states:


Samsung SSD 840 PRO Series disk0 : (256,06 GB) (Solid State - TRIM: No)


So which is it?


As you are aware Samsung SSDs do not enjoy a very good reputation among Mac users. You will not advance troubleshooting until you take steps to isolate it as the cause of your Mac's poor performance.

Feb 28, 2017 1:14 AM in response to John Galt

Hi,

Samsung SSD 840 PRO is correct. I mixed it with my PC which has the 950 Pro.


Still wonder about my first question which is what the errors actually mean and how to fix them. I have worked as a developer and these messages seem to me to be a software error:

ERROR!!! prelinked kernel corrupted

ERROR!!! Load prelinked kernel with status 0x800000000000001b

Error loading kernel cache (0x1b)


What causes a "prelinked kernel corrupted" ?


Also my MBP has worked without a issue since i somehow got it working. I'm on the other hand worried that it will pop up next time Apple does a update and like to understand why these error occur and how to fix them.

If you google it there are many people with the same problem but there is no confirmation that any of the ideas work for sure or what causes the problem:

http://apple.stackexchange.com/questions/253906/mid-2010-macbook-pro-wont-boot-a fter-trying-to-install-macos-sierra


http://www.insanelymac.com/forum/topic/308384-how-to-rebuild-my-prelinked-kernel -after-updating-to-el-capitan/


https://www.reddit.com/r/hackintosh/comments/3ehu34/unable_to_boot_after_rebuild ing_kernel_cachei/



Regards

Reza

Feb 28, 2017 2:14 PM in response to shadow

I'm on the other hand worried that it will pop up next time Apple does a update and like to understand why these error occur and how to fix them.


That is entirely likely and your concerns are justified. That is the risk you take when modifying a Mac's hardware, and is the reason Apple does not approve of such modifications.


You will not be able to fix the problem since Apple retains sole control over macOS and the hardware on which it is designed to be installed. They are utterly disinterested in anything else. They wouldn't even dignify a complaint such as yours with a response.


The only SSDs that I have used and can personally recommend are manufactured by OWC / MacSales, specifically their Mercury Extreme Pro SSDs. Failures are almost unheard of, whereas Samsung's failures are common. If an OWC SSD requires a firmware update to cope with future macOS releases, OWC provides it. Other manufacturers are just as unlikely to care about that as Apple.

Mar 1, 2017 1:47 PM in response to John Galt

Sorry as a engineer i can just laugh at your comment. Are you seriously claiming Apple HW is failsafe? All HW fail sooner or later. I have used this SSD for some years now so if it was incompatible i would not see it after some years. Also a simple google shows how wrong you are about the Mercury SSD:

https://www.google.se/search?q=failure+Mercury+Extreme+Pro&ie=utf-8&oe=utf-8&cli ent=firefox-b-ab&gfe_rd=cr&ei=Qz63WIPaKIKA8Qeo05agDw


Samsung SSD is among the best (did allot of research before i selected this and read lots of reviews at the time).


Any way i still wait for someone with knowledge about my errors and hopefully some explanation that is based on facts.

Latest Sierra update crashed my MPB

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