Skip navigation

Crashing often

392 Views 3 Replies Latest reply: May 3, 2013 8:13 AM by brownk13 RSS
brownk13 Calculating status...
Currently Being Moderated
May 2, 2013 3:05 PM

I have been crashing quite a bit the past couple of weeks. 

 

The crash log shows Exception Type:  EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at for each crash. 

 

How can I narrow down what the problem is.  I have tried running a memory test and it passed.

MacBook Pro, OS X Mountain Lion (10.8.3)
  • KarenSelena Level 4 Level 4 (1,905 points)
    Currently Being Moderated
    May 2, 2013 3:10 PM (in response to brownk13)

    First, try this.

     

    REPAIRING DISK - About OS X Recovery - http://support.apple.com/kb/HT4718.

     

    - restart your computer hold down command + R keys on the keyboard to boot you into Lion / Mountain Lion Recovery mode

    - select english as your main language then the continue arrow

    - select "Disk Utility" on the resulting screen then 'Disk Utility' ---

     

    - When prompted to select a disk volume or image, select the 'Macintosh HD' in the left column

    - ensure the the "first aid" tab is highlighted blue in the middle of the screen

    - click the button at the bottom that says 'REPAIR DISK' .......NOT "Repair disk permissions"

    - this process will take a few minutes to run.  It will indicate it's done, by scrolling to the bottom of the "details area" displaying "The Macintosh HD appears OK"

     

    If you get any other message OTHER than "The Macintosh HD appears OK", like "the Macintosh HD was repaired successfully" run the "Disk Repair" again, until it displays  "The Macintosh HD appears OK".

     

    Once done, restart the computer as normal

     

     

     

     

    If you still have the issue, try Running the Apple Hardware Test can help rule out Hardware issues.  If they are intermittent, running the Hardware test in "Loop mode" overnight, can be very helpful. 

     

    10.8 - Apple Hardware Test - http://support.apple.com/kb/PH11342.

     

    Restart your computer, holding down the D key while the computer restarts.

    After your computer restarts, you should see the Apple Hardware Test chooser screen. If you don’t, Apple Hardware Test may not be available on your computer. You may be able to start Apple Hardware Test from the Internet. Reconnect your computer to the network, and then restart your computer while holding down both the Option and D keys.

     

    Many times, running the "quick" test, or the "extended" test, may not give you any error results.  Many intermittent issues, may need to have the hardware test to run in loop mode, before it detects any error, and therefore running the Apple Hardware Test in Loop Mode overnight is an excellent troubleshooting step for finding intermittent hardware problems.

    In continuous Loop Mode, the test will run continuously until a problem is found or is stopped by you, by clicking “Stop Test” or by using the Command-period keyboard shortcut. If a problem is found, the test will cease to loop, indicating the problem it found. If the test fails, be sure to write down the exact message associated with the failure. Looping mode could be helpful in diagnosing a fault that may be heat related or when the fault occurs randomly.-------

    -- The Apple Hardware Test console appears. You can choose what sort of test or tests to perform: basic or select the "Perform extended testing"

    -- press and hold down the option key and the "L" key...then select the extended test.  This will make the test go into Loop mode

    -- look over the test results and make notes of any errors that may be logged

    -- to exit out of the test, press the escape key



  • Linc Davis Level 10 Level 10 (107,465 points)
    Currently Being Moderated
    May 2, 2013 6:01 PM (in response to brownk13)

    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 the name of the crashed application or process in the Filter text field. Select the messages from the time of the last crash, if any. Copy them to the Clipboard (command-C). Paste into a reply to this message (command-V).

     

    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 the Console window, look under User Diagnostic Reports for crash reports related to the process. The report name starts with the name of the crashed process, and ends with ".crash". Select the most recent report and post the entire contents — again, the text, not a screenshot. In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.) Please don’t post shutdownStall, spin, or hang logs — they're very long and not helpful.

Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.