Previous 1 2 Next 19 Replies Latest reply: Dec 26, 2013 4:32 PM by Konrad Cichocki Go to original post
  • Linc Davis Level 10 Level 10 (177,965 points)

    To stop the kernel log messages, quit iStat.


    Please read this whole message before doing anything.


    This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.


    The purpose of this exercise is to determine whether the problem is caused by third-party system modifications that load automatically at startup or login. Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards. Boot in safe mode* and log in to the account with the problem. The instructions provided by Apple are as follows:


    1. Be sure your Mac is shut down.
    2. Press the power button.
    3. Immediately after you hear the startup tone, hold the Shift key. The Shift key should be held as soon as possible after the startup tone, but not before the tone.
    4. Release the Shift key when you see the gray Apple icon and the progress indicator (looks like a spinning gear).


    *Note: If FileVault is enabled under Mac OS X 10.7 or later, you can’t boot in safe mode.


    Safe mode is much slower to boot and run than normal, and some things won’t work at all, including wireless networking on certain Macs.


    The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.


    Test while in safe mode. Same problem(s)?


    After testing, reboot as usual (i.e., not in safe mode) and verify that you still have the problem. Post the results of the test.

  • Kappy Level 10 Level 10 (262,905 points)



    Safe mode boot was already suggested in one of my earlier posts. It would appear the OP has not fully gone through recommended actions.


    Perhaps you might make sense of the posted crash reports as they are Greek to me. From what the OP has posted it would appear the computer is running a tad hot but there is no reason for it to do so normally, yet nothing appears locked up in Activity Monitor.

  • Linc Davis Level 10 Level 10 (177,965 points)

    The crash log for storeagent is unrevealing. The other one shows that a couple of third-party QuickTime components were loaded, but I can't say whether they contributed to the crash.


    I missed the fact that you had suggested a safe boot. I think it's the next logical step.

  • Kappy Level 10 Level 10 (262,905 points)

    I concur. I actually thought it should have been the next step after resetting the SMC did nothing to help.

  • Konrad Cichocki Level 1 Level 1 (10 points)

    For me it was a tiny CPU monitoring program called CPULed 1.3 that cause the system log to generate messages like this...


    kernel[0]: SMC::smcReadKeyAction ERROR TC0D kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8072eb2000

Previous 1 2 Next