3 Replies Latest reply: Aug 26, 2013 10:00 AM by Linc Davis
Joris Riedstra Level 1 Level 1

Since a week or so my MacBook Pro crashes every day. The screen freezes and I can't do anything. I have been looking for crash logs but I haven't found a log which corresponds with the time my computer crashes. I have tried to reset my 'System Management Controller' and I ran a 'Apple Hardware Test', both to no avail.


Here are the specifics of my MacBook Pro:


Model Name:          MacBook Pro

  Model Identifier:          MacBookPro9,1

  Processor Name:          Intel Core i7

  Processor Speed:          2.6 GHz

  Number of Processors:          1

  Total Number of Cores:          4

  L2 Cache (per Core):          256 KB

  L3 Cache:          6 MB

  Memory:          16 GB

  Boot ROM Version:          MBP91.00D3.B08

  SMC Version (system):          2.1f173

  Serial Number (system):          C0*******1G3

  Hardware UUID:          DD678E52-1A55-5319-8D66-71D1F614506F

  Sudden Motion Sensor:

  State:          Enabled


I hope someone can help me solving the crashes or can tell where the problem lies.


<Edited By Host>

MacBook Pro, OS X Mountain Lion (10.8.4)
  • Linc Davis Level 10 Level 10

    If you have more than one user account, these instructions must be carried out as an administrator.

    Launch the Console application in any of the following ways:

    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

    ☞ In the Finder, select Go Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

    ☞ Open LaunchPad. Click Utilities, then Console in the icon grid.

    Step 1

    Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select

    View Show Log List

    from the menu bar.


    Enter "BOOT_TIME" (without the quotes) in the search box. Note the timestamps of those log messages, which refer to the times when the system was booted. Now clear the search box and scroll back in the log to the last boot time after  you had the problem. Select the messages logged before the boot, while the system was unresponsive or was failing to shut down. Copy them to the Clipboard (command-C). Paste into a reply to this message (command-V). Please include the BOOT_TIME message at the end of the log extract.

    If there are runs of repeated messages, post only one example of each. Don’t post many repetitions of the same message.

    When posting a log extract, be selective. In most cases, a few dozen lines are more than enough.

    Please do not indiscriminately dump thousands of lines from the log into this discussion.

    Important: Some private information, such as your name, may appear in the log. Anonymize before posting.

    Step 2

    Still in Console, look under System Diagnostic Reports for crash or panic logs, and post the entire contents of the most recent one, if any. In the interest of privacy, I suggest you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if present (it may not be.) Please don’t post shutdownStall, spin, or hang logs — they're very long and not helpful.

  • Joris Riedstra Level 1 Level 1

    Thanks for your fast response!


    This morning my computer crashes/froze again, so I followed you steps:



    8/26/13 10:55:47.000 AM kernel[0]: NVDA(Private): Channel exception! exception type = 0x20 = PBDMA Error

    8/26/13 10:56:07.000 AM kernel[0]: NVDA(Private): Channel timeout!

    8/26/13 10:56:07.000 AM kernel[0]: NVDA(OpenGL): Channel timeout!

    8/26/13 10:56:28.000 AM bootlog[0]: BOOT_TIME 1377507388 0


    These lines correspond with the time exact time my computer crashed, so I think this has something to do with it.



    The last crash log I could find was from a few days ago and I don't know if it is of any importance. Also the log is very long, so I decided to post only the first lines:


    Code Type:       X86-64 (Native)

    Parent Process:  launchd [1]

    User ID:         0



    Date/Time:       2013-08-20 22:45:51.423 +0200

    OS Version:      Mac OS X 10.8.4 (12E55)

    Report Version:  10



    Crashed Thread:  3  Dispatch queue: com.apple.metadata.spotlightindex



    Exception Type:  EXC_BAD_ACCESS (SIGSEGV)

    Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000bad



    VM Regions Near 0xbad:


        __TEXT                 000000010ce5a000-000000010cf7a000 [ 1152K] r-x/rwx SM=COW  /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadat a.framework/Versions/A/Support/mds



    Application Specific Information:

    [0x110660000]/SourceCache/Spotlight_frameworks/Spotlight-707.11/index/common/sto rage.c:689: failed assertion 'success' /.Spotlight-V100/Store-V2/2383C498-EA36-4BD7-808C-D02B90486547 (hfs, t: 0x11, st: 0x1, f: 0x480d000) 


    [0x110660000](Error) IndexCI in _Bool _storeageSetFreeListHead(storage_t *, int, offset_t):offset(196883) < freeRegion (147712)

    [0x10ec34000](Warning) IndexQuery in virtual bool SISearchCtx_FSI::performSearch(struct PartialQueryResults *):Retried searchfs 4 times

    [0x11066e000](Warning) I




    Also I forgot to tell this: the crashes/freezes also happen on WIndows 8, which is installed on the same MacBook Pro, so I think the problem is not software-related.


    I hope you can do something with these logs

  • Linc Davis Level 10 Level 10

    The logic board is defective. Make a "Genius" appointment at an Apple Store, or go to another authorized service provider.

    Back up all data on the internal drive(s) before you hand over your computer to anyone. There are ways to back up a computer that isn't fully functional — ask if you need guidance.

    If privacy is a concern, erase the data partition(s) with the option to write zeros* (do this only if you have at least two complete, independent backups, and you know how to restore to an empty drive from any of them.) Don’t erase the recovery partition, if present.


    Keeping your confidential data secure during hardware repair

    *An SSD doesn't need to be zeroed.