Skip navigation

my iMac stops responding... its' literally freezes....

466 Views 12 Replies Latest reply: Jun 20, 2013 9:09 AM by Wooky RSS
Wooky Level 1 Level 1 (0 points)
Currently Being Moderated
Jun 18, 2013 6:25 PM

and can't move a thing... the screen is still on. no kernel panic or anything... even checked the diagnostic logs... shows nothing... last one I had was 3 weeks ago... but I recently experienced this a couple of times.

 

some sites recommend check memory and SMART check for the hard... did all that (using techpro) no issues found... what is wrong with my dear imac? This is the latest imac (late 2012), 27 inch and OS is ML.

 

appreciate any advice.

 

thanks

Y

iMac (27-inch, Late 2012), OS X Mountain Lion (10.8.2)
  • Linc Davis Level 10 Level 10 (107,660 points)
    Currently Being Moderated
    Jun 18, 2013 10:21 PM (in response to Wooky)

    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.

  • Linc Davis Level 10 Level 10 (107,660 points)
    Currently Being Moderated
    Jun 19, 2013 6:35 AM (in response to Wooky)

    Please post only the last 50 or so mesages written to the log before you had to reboot.

  • Linc Davis Level 10 Level 10 (107,660 points)
    Currently Being Moderated
    Jun 19, 2013 6:33 PM (in response to Wooky)

    First, remove the useless "TechTool" according to the developer's instructions. Then run the extended version of the Apple Hardware Test, looking for bad RAM.

     

    Using Apple Hardware Test

  • Linc Davis Level 10 Level 10 (107,660 points)
    Currently Being Moderated
    Jun 20, 2013 7:29 AM (in response to Wooky)

    If the problem is that your mouse isn't working, and it also doesn't work while running the hardware test, then most likely the mouse itself is the problem. If it has batteries, replace them. Otherwise try another pointing device.

  • Linc Davis Level 10 Level 10 (107,660 points)
    Currently Being Moderated
    Jun 20, 2013 7:51 AM (in response to Wooky)

    Can you reproduce the problem? That is, does it always happen under certain conditions?

  • Linc Davis Level 10 Level 10 (107,660 points)
    Currently Being Moderated
    Jun 20, 2013 8:40 AM (in response to Wooky)

    A problem that started without any change in configuration, and that you can't reproduce, is going to be almost impossible to track down.

     

    Since you installed "TechTool," you may also have installed other third-party software that could potentially destabilize the system. If you want to check for that possibility, do as follows.

     

    Please read this whole message before doing anything.
      
    This procedure is a diagnostic test. It won’t solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
       
    Third-party system modifications are a common cause of usability problems. By a “system modification,” I mean software that affects the operation of other software — potentially for the worse. The following procedure will help identify which such modifications you've installed. Don’t be alarmed by the complexity of these instructions — they’re easy to carry out and won’t change anything on your Mac.

     

    These steps are to be taken while booted in “normal” mode, not in safe mode. If you’re now running in safe mode, reboot as usual before continuing.

     

    Below are instructions to enter some UNIX shell commands. The commands are harmless, but they must be entered exactly as given in order to work. If you have doubts about the safety of the procedure suggested here, search this site for other discussions in which it’s been followed without any report of ill effects.

     

    Some of the commands will line-wrap or scroll in your browser, but each one is really just a single line, all of which must be selected. You can accomplish this easily by triple-clicking anywhere in the line. The whole line will highlight, and you can then copy it. The headings “Step 1” and so on are not part of the commands.

     

    Note: If you have more than one user account, Step 2 must be taken as an administrator. Ordinarily that would be the user created automatically when you booted the system for the first time. The other steps should be taken as the user who has the problem, if different. Most personal Macs have only one user, and in that case this paragraph doesn’t apply.

     

    Launch the Terminal 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 Terminal in the icon grid.

     

    When you launch Terminal, a text window will open with a line already in it, ending either in a dollar sign (“$”) or a percent sign (“%”). If you get the percent sign, enter “sh” and press return. You should then get a new line ending in a dollar sign.

     

    Step 1

     

    Triple-click the line of text below to select it:
    kextstat -kl | awk '!/com\.apple/{printf "%s %s\n", $6, $7}' | open -f -a TextEdit
     
    Copy the selected text to the Clipboard by pressing the key combination command-C. Then click anywhere in the Terminal window and paste (command-V). A TextEdit window will open. Post the contents of that window, if any — the text, please, not a screenshot. You can then close the TextEdit window. The title of the window doesn't matter, and you don't need to post that. No typing is involved in this step.
        
    Step 2

     

    Repeat with this line:
    { sudo launchctl list | sed 1d | awk '!/0x|com\.(apple|openssh|vix)|org\.(amav|apac|cups|isc|ntp|postf|x)/{print $3}'; sudo defaults read com.apple.loginwindow LoginHook 2> /dev/null; } | open -f -a TextEdit
     
    This time you'll be prompted for your login password, which you do have to type. Nothing will be displayed when you type it. Type it carefully and then press return. You may get a one-time warning to be careful. Heed that warning, but don't post it. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.

     

    Note: If you don’t have a login password, you’ll need to set one before taking this step. If that’s not possible, skip to the next step.

     

    Step 3
    launchctl list | sed 1d | awk '!/0x|com\.apple|org\.(x|openbsd)/{print $3}' | open -f -a TextEdit
     
    Step 4
    ls -1A /e*/mach* {,/}L*/{Ad,Compon,Ex,Fram,In,Keyb,La,Mail/Bu,P*P,Priv,Qu,Scripti,Servi,Spo,Sta}* L*/Fonts 2> /dev/null | open -f -a TextEdit
      
    Important: If you formerly synchronized with a MobileMe account, your me.com email address may appear in the output of the above command. If so, anonymize it before posting.

     

    Step 5
    osascript -e 'tell application "System Events" to get name of every login item' | open -f -a TextEdit
     
    Remember, steps 1-5 are all copy-and-paste — no typing, except your password. Also remember to post the output.

     

    You can then quit Terminal.

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.