iMac 27" occasional freeze-up (newbie needs help)

Discussion in 'Mac Basics and Help' started by branhan, Jul 19, 2013.

  1. macrumors newbie

    Joined:
    Jul 19, 2013
    Location:
    Xenia, OH
    #1
    Hey folks: I'm new to the forum and fairly new to the wonderful world of mac. We have a 27" iMac, late 2009 (2.66 ghz core i5 processor; 12 gb RAM; ATI Raedon HD 4850 512 MB graphics) running OS X 10.8.4. Bought it used last year, and for the most part it works fine.

    But every once in awhile it just freezes up on me. I can still see the cursor moving around when I move the mouse, but can't click anything. Keyboard doesn't do anything. My only choice is to hold the power button down and do a hard reboot. I thought maybe it was a mouse/keyboard connectivity issue, maybe a bluetooth thing, but it doesn't appear so.

    It has happened shortly (i.e. within an hour) after turning the computer on, and after hours of use... at one point I thought it was more prone to occur when I was using Google Chrome (I kind of live in Chrome), so I tried uninstalling Chrome, but it still happened, so there might not be a cause-and-effect relationship here; it may be simply that I'm in Chrome a lot, so it's more likely to happen when I'm in Chrome than any other application - I dunno. I'm not knowledgable enough about macs to know if there's a way to troubleshoot this.

    Any help or suggestions or pointers in some direction would be MUCH appreciated. I will not take offense to any responses; feel free to assume I'm completely ignorant.
     
  2. macrumors 601

    satcomer

    Joined:
    Feb 19, 2008
    Location:
    The Finger Lakes Region
    #2
    Then try to check /Applications/Utilities /Console.app to check your logs after the freeze time. This will tell you the time and possible reason for the freeze. Plus how much room is left on the hard drive?
     
  3. thread starter macrumors newbie

    Joined:
    Jul 19, 2013
    Location:
    Xenia, OH
    #3
    Thanks, satcomer! I appreciate the help. Not sure how the timing lines up, but I went to my console (first time I've done this) and these are the entries around the time it happened yesterday morning:

    7/19/13 9:27:11.000 AM kernel[0]: CODE SIGNING: cs_invalid_page(0x1000): p=9898[GoogleSoftwareUp] clearing CS_VALID
    7/19/13 10:08:17.961 AM com.apple.usbmuxd[27]: _heartbeat_failed heartbeat detected detach for device 0x274-192.168.1.100:0!
    7/19/13 10:17:37.453 AM com.apple.usbmuxd[27]: _heartbeat_failed heartbeat detected detach for device 0x275-192.168.1.100:0!
    7/19/13 10:25:52.000 AM kernel[0]: CODE SIGNING: cs_invalid_page(0x1000): p=9958[GoogleSoftwareUp] clearing CS_VALID
    7/19/13 10:53:20.161 AM com.apple.usbmuxd[27]: _heartbeat_failed heartbeat detected detach for device 0x278-192.168.1.100:0!
    7/19/13 10:55:01.633 AM com.apple.usbmuxd[27]: _heartbeat_failed heartbeat detected detach for device 0x279-192.168.1.100:0!
    7/19/13 10:56:46.692 AM com.apple.time[1195]: Interval maximum value is 946100000 seconds (specified value: 9223372036854775807).
    7/19/13 11:01:25.182 AM com.apple.usbmuxd[27]: _heartbeat_failed heartbeat detected detach for device 0x27c-192.168.1.100:0!
    7/19/13 11:07:19.727 AM com.apple.usbmuxd[27]: _heartbeat_failed heartbeat detected detach for device 0x27d-192.168.1.100:0!
    7/19/13 11:24:38.000 AM kernel[0]: CODE SIGNING: cs_invalid_page(0x1000): p=10021[GoogleSoftwareUp] clearing CS_VALID
    7/19/13 11:32:44.378 AM com.apple.usbmuxd[27]: _heartbeat_failed heartbeat detected detach for device 0x280-192.168.1.100:0!
    7/19/13 11:47:20.261 AM com.apple.usbmuxd[27]: _heartbeat_failed heartbeat detected detach for device 0x281-192.168.1.100:0!
    7/19/13 12:12:32.586 PM com.apple.usbmuxd[27]: _heartbeat_failed heartbeat detected detach for device 0x284-192.168.1.100:0!
    7/19/13 12:18:03.019 PM WindowServer[118]: handle_will_sleep_auth_and_shield_windows: no lock state data
    7/19/13 12:18:03.021 PM WindowServer[118]: Created shield window 0x29a for display 0x003f003d
    7/19/13 12:18:03.021 PM WindowServer[118]: handle_will_sleep_auth_and_shield_windows: no lock state data
    7/19/13 12:18:22.602 PM Finder[1212]: *** WARNING: -[NSImage compositeToPoint: operation:fraction:] is deprecated in MacOSX 10.8 and later. Please use -[NSImage drawAtPoint:fromRect: operation:fraction:] instead.
    7/19/13 12:18:22.603 PM Finder[1212]: *** WARNING: -[NSImage compositeToPoint:fromRect: operation:fraction:] is deprecated in MacOSX 10.8 and later. Please use -[NSImage drawAtPoint:fromRect: operation:fraction:] instead.​

    Does anything in there raise any red flags for you? I'm pretty ignorant as to how to interpret any of this...but I know anything related to "kernel" is significant, and "heartbeat failed" sounds bad! I also did a search for "shutdown" and these entires came up:

    Jul 19 12:38:56 localhost com.apple.launchd[1]: *** Shutdown logging is enabled. ***
    Jul 19 12:39:35 localhost kernel[0]: Previous Shutdown Cause: 3
    Jul 19 12:39:48 Hancock-iMac-i5.local locationd[46]: locationd was started after an unclean shutdown​

    What else should I be looking for?

    re: my HD, it's a 1TB that's about half full. Any further guidance is appreciated!
     
  4. macrumors 601

    satcomer

    Joined:
    Feb 19, 2008
    Location:
    The Finger Lakes Region
    #4
    It looks like a USB connection is acting up. Disconnect any third party USB devices (for a day) and see if you get the same freezes. See if that helps, good luck.

    Plus do a Reset Your PRAM action to see if that helps too.
     

Share This Page