iMac on 10.8.2 hanging

Discussion in 'macOS' started by Astaroth, Feb 24, 2013.

  1. Astaroth macrumors newbie

    Feb 24, 2013
    My 27" i7 couple of years old iMac has in the last week become unstable. Generally it is after a couple of hours of use but beyond that I have seen no pattern but whilst doing light web browsing etc the Dock and Wall paper both disappear to be replaced with a mid grey background and the cursor turns into a beach ball.

    If I leave it in this state for a few minutes eventually the whole screen goes white/ light grey.

    Typically I have always left the iMac to just go to sleep on its own when I've finished using it but now without fail the computer will have crashed within the few hours between use.

    The only way to get the computer working again is with the power button.

    Whilst I have been a mac user for a couple of years now it has always "just worked" and so I am not very good at maintenance on it. I have repaired disk permissions and reset the NVRAM but neither of these have improved the situation at all.

    Can anyone suggest next steps or how I actually diagnose the root cause?
  2. wrldwzrd89 macrumors G5


    Jun 6, 2003
    Solon, OH
    This is the kind of thing that log files will usually reveal the root cause of. Open Console and look for events that occurred around and before one of these situations (simple way to find one - search for BOOT_TIME - that shows up in the log if your computer is forcibly rebooted for any reason). I'll gladly help parse log files - feel free to shoot me a private message in the event that the log is too big to post.
  3. Astaroth thread starter macrumors newbie

    Feb 24, 2013
    Many thanks for the offer, whilst I can load the consol and see the mountain of messages I am not 100% sure what I am ooking for. If using the Diagnostics and Usage Messages then there are only two reoccurring messages:

    1= ReportCrash
    24/02/2013 12:26:00.262 ReportCrash[264]: PhotoStreamAgent UNBUNDLED ||| 2.7 (40.34)

    2= Kernel:
    24/02/2013 12:25:31.000 kernel[0]: FinderLoadBundle Finder noop

    In All Messages there are many more things around the time
  4. wrldwzrd89 macrumors G5


    Jun 6, 2003
    Solon, OH
    Okay. That first message is of concern, the second one isn't. Is there a crash log for PhotoStreamAgent in Console? There may be more than one.
  5. Astaroth thread starter macrumors newbie

    Feb 24, 2013
    There are many, but have turned off iCloud photos (wasnt intending for it to be on) and the every few minute report has gone. Will have to see if it becomes more stable.

    The report is:
    Process: PhotoStreamAgent [499]
    Path: /Applications/
    Identifier: PhotoStreamAgent
    Version: 2.7 (40.34)
    Code Type: X86-64 (Native)
    Parent Process: launchd [134]
    User ID: 501

    Date/Time: 2013-02-24 12:46:38.069 +0000
    OS Version: Mac OS X 10.8.2 (12C60)
    Report Version: 10

    Crashed Thread: 0

    Exception Type: EXC_BREAKPOINT (SIGTRAP)
    Exception Codes: 0x0000000000000002, 0x0000000000000000

    Application Specific Information:
    dyld: launch, loading dependent libraries

    Dyld Error Message:
    Library not loaded: @rpath/CoreMediaStream.framework/Versions/A/CoreMediaStream
    Referenced from: /Applications/
    Reason: no suitable image found. Did find:
    /Applications/ unknown file type, first eight bytes: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00

    Binary Images:
    0x10e50f000 - 0x10e54aff7 (2.7 - 40.34) <AC71D8F3-870D-309D-BD20-F073E341EC80> /Applications/
    0x10e56d000 - 0x10e576ff7 (1.0 - 10.17) <C40F985F-9C0A-389A-9E21-684EB0A5B160> /Applications/
    0x10e5ed000 - 0x10e707fff (1.7.1 - 60.5) <1E1D3528-A309-363F-93AD-D2B5B1115DE6> /Applications/
    0x10e773000 - 0x10e778fff (3.4 - 2.5) <906317D7-09FF-3B77-8F35-01BB74C0109C> /Applications/
    0x7fff6e10f000 - 0x7fff6e14393f dyld (210.2.3) <A40597AA-5529-3337-8C09-D8A014EB1578> /usr/lib/dyld
    0x7fff8c225000 - 0x7fff8ce52ff7 (6.8 - 1187.34) <1FF64844-EB62-3F96-AED7-6525B7CCEC23> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
    0x7fff8d085000 - 0x7fff8d0d6ff7 (1.12.2 - 1.12.2) <E095637C-457F-3D8F-AE32-A032F9D5A46C> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration
    0x7fff8d7c9000 - 0x7fff8da49ff7 (1.05 - 151) <A34E8584-797C-318F-9E25-937A710C68AB> /System/Library/PrivateFrameworks/AOSKit.framework/Versions/A/AOSKit
    0x7fff8f02d000 - 0x7fff8f038ff7 (3.0 - 3.0) <11E1A5D1-F5E5-3228-8B6F-77EB36B5C248> /System/Library/PrivateFrameworks/ApplePushService.framework/Versions/A/ApplePushService
    0x7fff93309000 - 0x7fff9332bff7 (1.1.2 - 1.1.94) <6D0ECB77-3081-3DC8-9B4F-20E5A1A09554> /System/Library/PrivateFrameworks/AOSAccounts.framework/Versions/A/AOSAccounts
    0x7fff95db3000 - 0x7fff96083fff (7.0 - 55179.1) <639641EF-8156-3190-890C-1053658E044A> /System/Library/Frameworks/Security.framework/Versions/A/Security
    0x7fff97076000 - 0x7fff973d2fff (6.8 - 945.11) <A5D41956-A354-3ACC-9355-BE200072223B> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
  6. wrldwzrd89 macrumors G5


    Jun 6, 2003
    Solon, OH
    Okay, that's NOT good. Looks like the version of iPhoto you migrated is a REALLY old one that your new OS doesn't recognize. Fortunately, fixing this is as easy as installing the update from the Mac App Store, assuming it even recognizes that you have iPhoto. If it doesn't, then... you're going to have to delete the old iPhoto and purchase the right one.
  7. Astaroth thread starter macrumors newbie

    Feb 24, 2013
    The version installed reports as being v9.4.2, it is recognised by the App Store and says it is currently up to date :confused:
  8. Astaroth thread starter macrumors newbie

    Feb 24, 2013
    Not getting on very well :(

    Have now gone as far as formatting the hd and reinstalling 10.8.2

    I "immediately" then updated OS X and installed iPhoto from the App Store and my iMac still hung after a few minutes whilst reindexing iTunes files.

    Looking at the console all the details prior to the crash are below

    As this is basically a clean install does it mean there is a hardware failure?

Share This Page