Kernel Panics on MacBook 12" (9,1)

[sddawson]

Five months
No. nearly always open and awake (I use Screens Connect and have the setting to prevent sleep)
It is only shut for transport, which is quite frequent.
Yes signed in to iCloud

So I guess I should try sleeping with lid shut to reproduce KPs, will think about it

Yes, pretty sure the KPs only happen with sleep. The gpu doesn't wake properly by the looks of it.

 

[japanime]

Is it always the GPU-related panic, as detailed at the start of this thread? Is your Mac fully up to date?

No, I've had causes other than the GPU-related one (thought that seems to be the most frequent). Mine is an M5, up-to-date, and connected to iCloud. The kernel panics occur not just when waking from sleep, but at other random times when I'm using the machine. Today, for instance, I got a kernel panic when trying to open 1Password. First time that's ever happened.

 

[sddawson]

No, I've had causes other than the GPU-related one (thought that seems to be the most frequent). Mine is an M5, up-to-date, and connected to iCloud. The kernel panics occur not just when waking from sleep, but at other random times when I'm using the machine. Today, for instance, I got a kernel panic when trying to open 1Password. First time that's ever happened.

Sounds like your problems are a little different then. I'd push for a whole new MacBook!

 

[japanime]

Sounds like your problems are a little different then. I'd push for a whole new MacBook!

I have been pushing for a new one. These kernel panics have been going on for about six months now, regular as clockwork. I've done everything the AppleCare reps have asked me to — numerous clean system installs, tests with guest accounts, sending it in for a logic board replacement) — and nothing has resolved the trouble. But Apple Japan stubbornly refuses to replace the machine. I've used Macs for nearly 25 years now, and this is by far the worst experience I've ever had.

 

[sddawson]

I have been pushing for a new one. These kernel panics have been going on for about six months now, regular as clockwork. I've done everything the AppleCare reps have asked me to — numerous clean system installs, tests with guest accounts, sending it in for a logic board replacement) — and nothing has resolved the trouble. But Apple Japan stubbornly refuses to replace the machine. I've used Macs for nearly 25 years now, and this is by far the worst experience I've ever had.

Oh dear - I really feel for you. Do you have any consumer protection routes you can take? In Australia, this would instantly be classed as "not fit for purpose" and a replacement machine, or refund, is a consumer right.

 

[japanime]

Oh dear - I really feel for you. Do you have any consumer protection routes you can take? In Australia, this would instantly be classed as "not fit for purpose" and a replacement machine, or refund, is a consumer right.

None that I'm aware of, but I'll continue to insist they do something about it. I'm hoping that eventually, somebody with real authority will step in and help me out.

 

[sddawson]

None that I'm aware of, but I'll continue to insist they do something about it. I'm hoping that eventually, somebody with real authority will step in and help me out.

I guess you've already asked to talk to someone higher up the chain?

 

[Wandsworth53]

I guess you've already asked to talk to someone higher up the chain?

Suffered for 7 months with total battery drain while sleeping followed by IGPU panics after cold boot, occurring every 10-15 days from new on my 12" Retina MacBook (MacBook9,1). Motherboard replaced by authorised Apple service agent, no more problems. A hardware product quality issue for sure.

 

[japanime]

I've tried to get my issue escalated, but Apple Japan is apparently run by a bunch ... well ...

Last week, I had three kernel panics. That's actually a good week. Most weeks, they happen daily. I've already had two today, so the week is not off to a good start.

 

[squareroot777]

Hey, i ve been experiencing the same kernel panics on a '15 MB 512/8g/1.2ghz and found something that may be helpful by browsing the logs. After reading this thread i've shut my Bluetooth off, and all the other advices. I've shut down the laptop and let it plugged in over the night, in the morning I unplugged the charger started the mb and in 10 seconds another kernel panic. So i've looked through the logs and found something relevant(maybe).


Jul 8 09:23:44 MacBooks-MacBook GoogleSoftwareUpdateAgent[472]: 2017-07-08 09:23:44.334 GoogleSoftwareUpdateAgent[472/0x700005edc000] [lvl=2] -[KSAgentApp performSelfUpdateWithEngine:] Finished self update check.
Jul 8 09:23:44 MacBooks-MacBook GoogleSoftwareUpdateAgent[472]: 2017-07-08 09:23:44.334 GoogleSoftwareUpdateAgent[472/0x700005edc000] [lvl=2] -[KSAgentApp(KeystoneThread) runKeystonesInThreadWithArg:] About to run checks for any other apps.
Jul 8 09:23:44 MacBooks-MacBook GoogleSoftwareUpdateAgent[472]: 2017-07-08 09:23:44.335 GoogleSoftwareUpdateAgent[472/0x700005edc000] [lvl=2] -[KSAgentApp updateProductWithProductID:usingEngine:] Checking for updates for "All Products" using engine <KSUpdateEngine:0x100548bb0
ticketStore=<KSPersistentTicketStore:0x100221b00 store=<KSKeyedPersistentStore:0x1002222a0
path="/Users/MareAdrian/Library/Google/GoogleSoftwareUpdate/TicketStore/Keystone.ticketstore"
lockFile=<KSLockFile:0x100344920
path="/Users/MareAdrian/Library/Google/GoogleSoftwareUpdate/TicketStore/Keystone.ticketstore.lock"
locked=NO
>
>>
processor=<KSActionProcessor:0x10027f320
delegate=<KSUpdateEngine:0x100548bb0>
isProcessing=NO actionsCompleted=0 progress=0.00
errors=0 currentActionErrors=0
events=0 currentActionEvents=0
actionQueue=( )
>
delegate=(null)
serverInfoStore=<KSServerPrivateInfoStore:0x100216ba0 path="/Users/MareAdrian/Library/Google/GoogleSoftwareUpdate/Servers">
errors=0
>
Jul 8 09:23:44 MacBooks-MacBook GoogleSoftwareUpdateAgent[472]: 2017-07-08 09:23:44.350 GoogleSoftwareUpdateAgent[472/0x700005edc000] [lvl=2] -[KSUpdateEngine updateAllExceptProduct:] KSUpdateEngine updating all installed products, except:'com.google.Keystone'.
Jul 8 09:23:44 MacBooks-MacBook lowBatteryWarning[504]: DEPRECATED USE in libdispatch client: Changing the target of a source after it has been activated
Jul 8 09:23:44 MacBooks-MacBook GoogleSoftwareUpdateAgent[472]: 2017-07-08 09:23:44.402 GoogleSoftwareUpdateAgent[472/0x700005edc000] [lvl=2] -[KSCheckAction performAction] KSCheckAction checking 1 ticket(s).
Jul 8 09:23:44 MacBooks-MacBook GoogleSoftwareUpdateAgent[472]: 2017-07-08 09:23:44.442 GoogleSoftwareUpdateAgent[472/0x700005edc000] [lvl=2] -[KSUpdateCheckAction performAction] KSUpdateCheckAction starting update check for ticket(s): {(
<KSTicket:0x100541e90
productID=com.google.Chrome
version=59.0.3071.115
xc=<KSPathExistenceChecker:0x1005a3650 path=/Applications/Google Chrome.app>
serverType=Omaha
url=https://tools.google.com/service/update2
creationDate=2017-07-05 20:13:18
tagPath=/Applications/Google Chrome.app/Contents/Info.plist
tagKey=KSChannelID
brandPath=/Users/MareAdrian/Library/Google/Google Chrome Brand.plist
brandKey=KSBrandID
versionPath=/Applications/Google Chrome.app/Contents/Info.plist
versionKey=KSVersion
cohort=1:1y5:
cohortName=Stable
ticketVersion=1
>
)}
Using server: <KSOmahaServer:0x100283240
engine=<KSUpdateEngine:0x100548bb0>
>
Jul 8 09:23:44 MacBooks-MacBook GoogleSoftwareUpdateAgent[472]: 2017-07-08 09:23:44.464 GoogleSoftwareUpdateAgent[472/0x700005edc000] [lvl=2] +[KSCodeSigningVerification verifyBundle:applicationId:error:] KSCodeSigningVerification verifying code signing for '/Applications/Google Chrome.app' with the requirement 'anchor apple generic and certificate 1[field.1.2.840.113635.100.6.2.6] exists and certificate leaf[field.1.2.840.113635.100.6.1.13] exists and certificate leaf[subject.OU]="EQHXZ8M8AV" and (identifier="com.google.Chrome")'
Jul 8 09:24:34 localhost bootlog[0]: BOOT_TIME 1499495074 0
Jul 8 09:24:37 localhost syslogd[52]: Configuration Notice:
ASL Module "com.apple.cdscheduler" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
Jul 8 09:24:37 localhost syslogd[52]: Configuration Notice:
ASL Module "com.apple.install" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
Jul 8 09:24:37 localhost syslogd[52]: Configuration Notice:
ASL Module "com.apple.family.asl" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
Jul 8 09:24:37 localhost syslogd[52]: Configuration Notice:
ASL Module "com.apple.callhistory.asl.conf" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
Jul 8 09:24:37 localhost syslogd[52]: Configuration Notice:
ASL Module "com.apple.contacts.ContactsUICore" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
Jul 8 09:24:37 localhost syslogd[52]: Configuration Notice:
ASL Module "com.apple.authd" sharing output destination "/var/log/asl" with ASL Module "com.apple.asl".
Output parameters from ASL Module "com.apple.asl" override any specified in ASL Module "com.apple.authd".
Jul 8 09:24:37 localhost syslogd[52]: Configuration Notice


The BOOT TIME line is when I rebooted the laptop right after the KP. If you look right before the mb crashed all those lines are related to google chrome, that googlechromehelper thing.

This would not be a new thing for google, there was a similar case of google chrome causing KP in intel HD 4000 series a few years back. I ve unistalled chrome for now an i'm waiting to see if this is the case. I repeat, I had the EXACT same issues like you, random KP with no apparent reason.

What's your status now? have your problems been resolved?


Have a nice day!

 

[sddawson]

Was your panic GPU-related, as has been the case with others in this thread? I've never had Chrome installed, so if you're having the same panics, I doubt it's Chrome-related.

With the "fix" developed over at https://discussions.apple.com/message/30840770?start=45&tstart=0 I have never had a panic. However, my wife has a newer MacBook and it hasn't had any panics without that fix being installed. It's possible that it has been fixed in later Sierra updates, but I don't really want to back the fix off to see - I like that my MacBook doesn't wake up every 2 hours or at random other times.

 

[squareroot777]

Was your panic GPU-related, as has been the case with others in this thread? I've never had Chrome installed, so if you're having the same panics, I doubt it's Chrome-related.

With the "fix" developed over at https://discussions.apple.com/message/30840770?start=45&tstart=0 I have never had a panic. However, my wife has a newer MacBook and it hasn't had any panics without that fix being installed. It's possible that it has been fixed in later Sierra updates, but I don't really want to back the fix off to see - I like that my MacBook doesn't wake up every 2 hours or at random other times.

I have no idea what my KP is relate to. I didn't experience your sleep problem. I just have random KP's with a relatively high frequency(one every day at least). I installed Sierra, then updated to beta HS, then downgraded to ElCap, all clean installs. Apparently that chrome thing wasn't right because i had another KP. I'm scared it's a faulty CPU because i got all types of KP("IGPU(the one you got)" to "Kernel trap 14=page fault" etc...). The reason I think it's a cpu problem is because the other day after a clean ElCap install i was watching a movie for like a half hour and at one point I started to copy something from one folder to another(about 6 gigs) in the background and continued to watch the movie.After about 10 sec another KP with the description " Kernel trap at 0xffffff7ffddc2010" and below "BSD process name corresponding to current thread: ditto". From my basic computer science knowledge ditto is a function related to copy/paste in unix. After a restart I recopied the files and there were no problems. To me it seems like every time a function is passed by the cpu to a particular register(or registers) the system fails. Is "bad registers" a thing for CPU's?

Do any of you have any idea what to try next??

Thank You

 

[sddawson]

I have no idea what my KP is relate to. I didn't experience your sleep problem. I just have random KP's with a relatively high frequency(one every day at least). I installed Sierra, then updated to beta HS, then downgraded to ElCap, all clean installs. Apparently that chrome thing wasn't right because i had another KP. I'm scared it's a faulty CPU because i got all types of KP("IGPU(the one you got)" to "Kernel trap 14=page fault" etc...). The reason I think it's a cpu problem is because the other day after a clean ElCap install i was watching a movie for like a half hour and at one point I started to copy something from one folder to another(about 6 gigs) in the background and continued to watch the movie.After about 10 sec another KP with the description " Kernel trap at 0xffffff7ffddc2010" and below "BSD process name corresponding to current thread: ditto". From my basic computer science knowledge ditto is a function related to copy/paste in unix. After a restart I recopied the files and there were no problems. To me it seems like every time a function is passed by the cpu to a particular register(or registers) the system fails. Is "bad registers" a thing for CPU's?

Do any of you have any idea what to try next??

Thank You

I think it's safe to say your problem is different to that suffered by others on this thread. I think your best course of action is to contact Apple.

 

[Non-Polar]

I've tried to get my issue escalated, but Apple Japan is apparently run by a bunch ... well ...

Last week, I had three kernel panics. That's actually a good week. Most weeks, they happen daily. I've already had two today, so the week is not off to a good start.

Hey, just an FYI, I've run into the same issue with my 2012 rMBP back in the day. After 5 instances of repair for the same symptoms, I was able to convince them to swap it out for a 2015 model. I paid around $700 to get the best in the class. I've read that you will need 4-5 instances of repairs for the same symptom before you can ask for an upgrade. Good luck.

 

[japanime]

Hey, just an FYI, I've run into the same issue with my 2012 rMBP back in the day. After 5 instances of repair for the same symptoms, I was able to convince them to swap it out for a 2015 model. I paid around $700 to get the best in the class. I've read that you will need 4-5 instances of repairs for the same symptom before you can ask for an upgrade. Good luck.

Thanks for the advice. I just gave up, though, and have learned to live with the kernel panics. Recent OS updates have helped some, but the problem persists. Apple Japan isn't worth the trouble anymore.

 

[Marcopolo53]

Have just completed an Internet Recovery, DU wipe SSD and reinstall 10.12.6 in early 2016 MacBook Retina, 8 GB Ram, 512 SSD. Am Not getting KP but am getting Broadcom 4360 Driver crashes after putting to sleep and waking after 30 to 60 minutes. Have done the NVRAM and SMC reset both before and post reinstallation - no love. Checking the logs showing power stat =0 as first entry in crash report. Any thoughts - off topic I realize but find very few others reporting the same issue elsewhere.

 

[al404]

does the happens only on 2016 Macbook or also on 2017?

 

[Marcopolo53]

Can only speak to Retina MacBook 2016

 

[japanime]

I'm resurrecting this very old thread (in which I was a regular participant) because I have a somewhat-related update that might help others who have MacBooks that are still (barely) under warranty.

The kernel panics mostly stopped once I upgraded to OSX High Sierra, but I continued to experience problems with the keyboard (repeating keys, weird accented characters showing up instead of the keys I pressed, etc.). Those issues are, of course, now well-known, and we all know that Apple has an official free-of-charge service program for the keyboard.

Because I mostly use an external keyboard and display, the machine's own keyboard issues weren't something I wasn't in a hurry to have fixed, especially when it would require several days in the repair shop. But my Magic Keyboard died last week, so I figured it was time to get the Macbook's keyboard replaced, too.

I took my machine to the new Marunouchi Apple Store this past weekend. I showed the "Genius" how they keyboard misbehaved, and he replied, almost gleefully, "Oh, that's because the battery is swelling and pushing up on the keyboard!"

Huh? I certainly couldn't detect any battery "swell." I've treated this MacBook with utmost care in consideration to how fragile it feels. It looks as good today as the day I bought it.

The AppleCare on mine expired about three months ago, unfortunately. And, according to the Genius, the keyboard issues I was experiencing were directly related to the battery, and thus not covered under the official recall.

He then insisted that the battery was swelling and would need to be replaced before Apple would even look at the keyboard. And that would cost me at least 20,000 yen (about $200) PLUS whatever it would cost to fix the keyboard.

I declined his "offer." The System Report for my MacBook lists the condition of the battery as "Normal" and the cycle count is just shy of 70. The third-party Coconut Battery app says the capacity of the battery is around 85%. I don't know how reliable those reports are, but I still get a good three hours out of the battery.

He then told me that there were almost certainly going to be other repairs associated with the swollen battery, including the cost of replacing the case, and said that if it were him, he would just spend the money on a new computer. (The case on my MacBook looks perfect, so his assertion was, in my opinion, nonsense.)

In any case, I'm obviously out of luck when it comes to getting the keyboard replaced. But those of you who still have a few days or weeks on your warranties should get your MacBooks to an Apple Store pronto so those keyboards can be repaired AND some so-called "Genius" can't try to shake you down for a "swelling battery" (which would also be covered by the warranty).

Hope this helps some of you out there