Macbook acting up just in time for college to start

Discussion in 'MacBook Pro' started by Redsox2, Sep 3, 2014.

  1. Redsox2 macrumors newbie

    Joined:
    Sep 3, 2014
    #1
    I have a Mid 2010 MacbookPro 13"
    Version: 10.9.4
    Processor: 2.4 GHz Intel Core 2 Duo

    A week ago my Mac died/ran out of battery for the first time in months. I threw it on the charger for the night and the next day when i went to turn it on and i would hear it starting to boot for a second and then it would shut back down. And it would keep repeating this process about every 10 seconds until i pressed the power button again. A few hours later i tried it again and it turned on no problem and worked fine for the next few days.

    However, now its been randomly shutting down on me and it seems like its happening more and more. I know there are many threads about this and ive done my research on it but it seems like theres often a couple different things that could be causing this, and im looking to you guys to help distinguish that. College just started up this week and i wouldnt be able to live without my mac :)

    When i look at the system logs after it randomly shuts off, i usually see something like this.

    3:13:12 PM kernel: Previous Shutdown Cause: 0

    and around that are some

    kernel: SMC:: smcReadKeyAction ERROR: smcReadData8 failed for key LsNM (kSMCKeyNotFound)

    If you need me to i can post the full logs.

    Thanks so much for help. Its greatly appreciated
     
  2. Hustler1337 macrumors 68000

    Hustler1337

    Joined:
    Dec 23, 2010
    Location:
    London, UK
    #2
    I think your battery might be going dead and may need replacing. In the meantime, have you tried resetting the SMC?

    I had a similar issue with mines, but it was due to large amount of dust build up inside the machine.
     
  3. Redsox2 thread starter macrumors newbie

    Joined:
    Sep 3, 2014
    #3
    Yeah ive reset the SMC, PRAM, and also started it up in safe boot. My battery is on cycle count 808 so it is getting up there, but it also says the battery condition is normal. Is there a way i can be sure that its my battery before i go out and buy a new one? Also it will shut down with the charger plugged in as well. Not sure if that changes things or not.

    Thanks
     
  4. Redsox2 thread starter macrumors newbie

    Joined:
    Sep 3, 2014
    #4
    So i removed my battery and im just powering my mac from the adapter and the problem is still happening, only not as often.

    I did a diagnostic test through terminal and this is what the output was. If someone could help me interpret this, it would be great. Thanks!

    Start time: 12:45:20 09/25/14


    Model Identifier: MacBookPro7,1
    System Version: OS X 10.9.5 (13F34)
    Kernel Version: Darwin 13.4.0
    Time since boot: 29 minutes


    SATA


    TOSHIBA MK2555GSXF


    Diagnostic reports


    2014-09-16 SecureDownloadManager crash
    2014-09-17 App Store hang
    2014-09-17 Microsoft Excel hang
    2014-09-17 UserEventAgent crash
    2014-09-18 UserEventAgent crash x2
    2014-09-19 UserEventAgent crash
    2014-09-20 UserEventAgent crash
    2014-09-22 UserEventAgent crash
    2014-09-23 UserEventAgent crash
    2014-09-24 UserEventAgent crash x2


    Log


    Sep 23 18:50:37 AppleLMUController::smcWriteKey received error 0x84 when reading key 'LKSB'.
    Sep 23 18:50:37 AppleLMUController received the SMC error of 0xbc when trying to set keyboard brightness
    Sep 23 18:50:37 AppleLMUController::smcWriteKey received error 0x84 when reading key 'LKSB'.
    Sep 23 18:50:37 AppleLMUController received the SMC error of 0xbc when trying to set keyboard brightness
    Sep 23 18:50:37 AppleLMUController::smcWriteKey received error 0x84 when reading key 'LKSB'.
    Sep 23 18:50:37 AppleLMUController received the SMC error of 0xbc when trying to set keyboard brightness
    Sep 23 18:50:37 AppleLMUController::smcWriteKey received error 0x84 when reading key 'LKSB'.
    Sep 23 18:50:37 AppleLMUController received the SMC error of 0xbc when trying to set keyboard brightness
    Sep 23 18:50:37 AppleLMUController::smcWriteKey received error 0x84 when reading key 'LKSB'.
    Sep 23 18:50:37 AppleLMUController received the SMC error of 0xbc when trying to set keyboard brightness
    Sep 23 18:50:37 AppleLMUController::smcWriteKey received error 0x84 when reading key 'LKSB'.
    Sep 23 18:50:37 AppleLMUController received the SMC error of 0xbc when trying to set keyboard brightness
    Sep 23 18:50:37 AppleLMUController::smcWriteKey received error 0x84 when reading key 'LKSB'.
    Sep 23 18:50:37 AppleLMUController received the SMC error of 0xbc when trying to set keyboard brightness
    Sep 23 18:52:32 process rpcsvchost[85] thread 713 caught burning CPU! It used more than 50% CPU (Actual recent usage: 62%) over 180 seconds. thread lifetime cpu usage 90.014288 seconds, (71.326986 user, 18.687302 system) ledger info: balance: 90006257421 credit: 90006257421 debit: 0 limit: 90000000000 (50%) period: 180000000000 time since last refill (ns): 143621496469
    Sep 23 18:58:24 process WindowServer[84] caught causing excessive wakeups. Observed wakeups rate (per sec): 229; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 88914
    Sep 24 10:46:11 jnl: b(1, 2): replay_journal: from: 1809920 to: 6660096 (joffset 0x743000)
    Sep 24 10:46:11 jnl: b(1, 2): journal replay done.
    Sep 24 10:50:18 process WindowServer[88] caught causing excessive wakeups. Observed wakeups rate (per sec): 200; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 45005
    Sep 25 12:12:52 Sleep failure code 0x00000000 0x1f006700
    Sep 25 12:12:52 jnl: b(1, 2): replay_journal: from: 1412096 to: 9821696 (joffset 0x743000)
    Sep 25 12:12:52 jnl: b(1, 2): journal replay done.
    Sep 25 12:16:25 jnl: b(1, 2): replay_journal: from: 11311616 to: 24649216 (joffset 0x743000)
    Sep 25 12:16:25 jnl: b(1, 2): journal replay done.
    Sep 25 12:21:32 process WindowServer[88] caught causing excessive wakeups. EXC_RESOURCE supressed due to audio playback


    Activity


    CPU: user 18%, system 12%


    CPU per process: Google Chrome He (UID 501) is using 42.6 %


    Daemons


    com.microsoft.office.licensing.helper
    com.adobe.fpsaud


    Agents


    com.spotify.webhelper
    com.google.keystone.user.agent


    launchd


    /Library/LaunchDaemons/com.adobe.fpsaud.plist
    - com.adobe.fpsaud
    /Library/LaunchDaemons/com.microsoft.office.licensing.helper.plist
    - com.microsoft.office.licensing.helper
    Library/LaunchAgents/com.google.keystone.agent.plist
    - com.google.keystone.user.agent
    Library/LaunchAgents/com.spotify.webhelper.plist
    - com.spotify.webhelper


    Bundles


    /Library/Internet Plug-Ins/SharePointBrowserPlugin.plugin
    - com.microsoft.sharepoint.browserplugin
    /Library/Internet Plug-Ins/SharePointWebKitPlugin.webplugin
    - com.microsoft.sharepoint.webkitplugin
    /Library/PreferencePanes/Flash Player.prefPane
    - com.adobe.flashplayerpreferences


    Font issues: 21


    User login items


    iTunesHelper
    - /Applications/iTunes.app/Contents/MacOS/iTunesHelper.app
    Spotify
    - /Applications/Spotify.app
    BitTorrent Sync
    - /Applications/BitTorrent Sync.app
    Google Chrome
    - /Applications/Google Chrome.app
    BitTorrent
    - /Applications/BitTorrent.app


    Restricted files: 54


    Elapsed time (s): 268
     
  5. Redsox2 thread starter macrumors newbie

    Joined:
    Sep 3, 2014
    #5
    I also was looking around in the console logs and found displaypolicyd.log in the diagnostic messages in my var/log

    Each of these times is when my mac went to sleep or shutdown. What would this mean?



    u>24557333 /usr/libexec/displaypolicyd: Version: V1.0 starting [0]
    u>24835246 /usr/libexec/displaypolicyd: Started at Wed Sep 24 10:46:14 2014
    u>61282881 ERROR: AGDC suppport not present in system
    u>61282976 ERROR: Policy engine instance init failed
    u>39623471 /usr/libexec/displaypolicyd: Version: V1.0 starting [0]
    u>39662741 /usr/libexec/displaypolicyd: Started at Thu Sep 25 12:12:51 2014
    u>75766891 ERROR: AGDC suppport not present in system
    u>75766918 ERROR: Policy engine instance init failed
    u>33359365 /usr/libexec/displaypolicyd: Version: V1.0 starting [0]
    u>33376349 /usr/libexec/displaypolicyd: Started at Thu Sep 25 12:16:25 2014
    u>69721544 ERROR: AGDC suppport not present in system
    u>69721616 ERROR: Policy engine instance init failed
    u>25525596 /usr/libexec/displaypolicyd: Version: V1.0 starting [0]
    u>25827372 /usr/libexec/displaypolicyd: Started at Thu Sep 25 19:25:07 2014
    u>61847040 ERROR: AGDC suppport not present in system
    u>61847116 ERROR: Policy engine instance init failed
    u>40190786 /usr/libexec/displaypolicyd: Version: V1.0 starting [0]
    u>40534629 /usr/libexec/displaypolicyd: Started at Thu Sep 25 19:34:33 2014
    u>77561270 ERROR: AGDC suppport not present in system
    u>77561330 ERROR: Policy engine instance init failed
     
  6. Samuelsan2001 macrumors 603

    Joined:
    Oct 24, 2013
    #6
    Post this info to apple support

    To be honest this is just a rumours website.

    Some of the posters here may be able to help but your best bet for a quick answer to what your issue logs are telling you is to post on apples support pages.
     
  7. Weaselboy Moderator

    Weaselboy

    Staff Member

    Joined:
    Jan 23, 2005
    Location:
    California
    #7
    Try running the Apple Hardware Test.
     
  8. poiihy macrumors 68020

    poiihy

    Joined:
    Aug 22, 2014
    #8
    Nonsense!
    Macrumors helps a lot.
    They fixed my MacBook Pro :D

    If you ask at the official apple forums they'd probably say to take it into an AASP or something like that ¬_¬

    And this is a community-made forum so you can be friendly and humorous etc., without die Gestapo halting you.

    ----------

    Yes do this.

    It might be RAM, or it might be a bad chip. It looks like the SMC is trying to read and write to PRAM but cannot do it. PRAM is soldered directly to the logic board, right? If it is bad PRAM then you'd have to replace the logic board. (AFAIK)

    Whatever it is, AHT should be able to detect something like this.
     
  9. Redsox2 thread starter macrumors newbie

    Joined:
    Sep 3, 2014
    #9
    Thanks for the reply, but I dont have the disc for the hardware test, but i did take it into an apple service provider and they ran a bunch of diagnostics on it the last few days and they said there were no errors detected and they gave it back to me. Now i have no idea what to do because it is still randomly shutting down.
    I was thinking it was the logic board, but the guy said the test said there was no error and usually when it is the logic board the problem worsens. This has been happening for about 2 months and it hasn't gotten worse
     

Share This Page