Skip navigation

iMac crashes on wake-up from Sleep after 10.8.3 update.

1355 Views 9 Replies Latest reply: Jun 5, 2013 6:55 AM by stephenfromwembley RSS
Lightning George Level 1 Level 1 (0 points)
Currently Being Moderated
Mar 29, 2013 3:15 PM

After updating to OSX 10.8.3 (from 10.8.2), iMac9,1 (March 2009 vintage) crashes every time I attempt to wake it from Sleep.  Following suggestions in other related threads, I ran Disk Utility Verify Disk (OK) and Repair Permissions (completed successfully). I then shut down and started in Safe Mode.  I then put it to sleep, counted to 10, and woke it up.  As has happened every time I attempt to wake it up, it crashed within seconds of displaying the account password dialog box and went into a forced restart, displaying the "Your computer is restarting due to a problem..." message in several languages.

 

This is a royal pain in various body parts.

 

Should I schlepp my iMac to my local Apple Store and ask them to re-install 10.8.2?

OS X Mountain Lion (10.8.3), Model Identifier: iMac9,1
  • Linc Davis Level 10 Level 10 (107,995 points)

    If you have more than one user account, you must be logged in as an administrator to carry out these instructions.

      

    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.

       

    Select the most recent panic log under the heading System Diagnostic Reports on the left. If you don't see that heading, select  

     

    View ▹ Show Log List

      

    from the menu bar. Post the entire contents of the panic report — the text, please, not a screenshot. In the interest of privacy, I suggest you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header and body of the report, if it’s present (it may not be.) Please don't post shutdownStall, spin, or hang reports.

  • Linc Davis Level 10 Level 10 (107,995 points)

    That panic was not caused by third-party software. If the problem is recurrent, the possibilities are:

    1. A damaged OS X installation
    2. A fault in a peripheral device, if any
    3. Corrupt non-volatile memory (NVRAM)
    4. An internal hardware fault (including incompatible memory)
    5. An obscure bug in OS X

    You can rule out the first two possibilities by reinstalling the OS and testing with non-essential peripherals disconnected and aftermarket expansion cards removed, if applicable. Sometimes a clean reinstallation (after erasing the startup volume) may solve a problem that isn't solved by reinstalling in place, without erasing.

     

    Corrupt NVRAM, which rarely causes panics, can be ruled out by resetting it as directed in this support article.

     

    If your model has user-replaceable memory, and you've upgraded the memory modules, reinstall the original memory and see whether there's any improvement. Be careful not to touch the gold contacts. Clean them with a mild solvent such as rubbing alcohol. Aftermarket memory must exactly match the technical specifications for your model. Memory that is either slower or faster than specified may be incompatible.

     

    The Apple Hardware Test, though generally unreliable, will sometimes detect a fault. A negative test can't be depended on. Run the extended version of the test.

     

    In the category of obscure bugs, reports suggest that FileVault may trigger kernel traps under some unknown conditions. Most, though not all, of these reports seem to involve booting from an aftermarket SSD. If those conditions apply to you, try deactivating FileVault.

     

    If none of the above applies, make a "Genius" appointment at an Apple Store to have the machine tested. You may have to leave it there for several days. There isn't much point in doing this unless you can reproduce the panic, or if you can't, it happens often enough that it's likely to be repeated at the store. Otherwise you may be told that nothing is wrong.

     

    Print the first page of the panic report and bring it with you.

     

    Back up all data on the internal drive(s) before you hand over your computer to anyone. If privacy is a concern, erase the data partition(s) with the option to write zeros* (do this only if you know how to restore, and you have at least  two independent backups.) Don’t erase the recovery partition, if present.

     

    Keeping your confidential data secure during hardware repair

     

    *An SSD doesn't need to be zeroed.

  • Linc Davis Level 10 Level 10 (107,995 points)

    1. By booting from the Recovery partition (command-R at startup.)

    2. The Recovery partition won't be erased.

    3. Yes, as long as you haven't excluded anything you want to keep.

  • stephenfromwembley Level 1 Level 1 (0 points)

    I had the same problem on my Early 2009 iMac when I upgraded from 10.8.2 to 10.8.3 immediately after it was released. My iMac is stock standard with just an external WD Book for timemachine and Super Duper backups. I recovered back to 10.8.2 as the problem made the system unworkable. I have been waiting for 10.8.4 and upgraded today. Same problem, so I'm back to 10.8.2 again.

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.