Skip navigation

Mountain Lion Screen Freeze

43519 Views 183 Replies Latest reply: Nov 26, 2013 10:33 PM by Smudge RSS Branched to a new discussion.
  • Chuck Gould Level 1 Level 1 (75 points)
    Currently Being Moderated
    Feb 21, 2013 1:19 PM (in response to seanfromminato-ku)

    I don't think it's FCP X itself, it's just something to do with how its using the GPU driver(s). And, since it's repeatable, it's a good place to start for debugging the code.

  • Chuck Gould Level 1 Level 1 (75 points)
    Currently Being Moderated
    Feb 21, 2013 1:55 PM (in response to sdaza)

    I just did a bit more testing. On quitting FCP X (recreating the hang), if any graphic element is moved (i.e. causes a redraw), it will hang. It always comes back to life after < 10 sec, fortunately. For instance, quitting to the desktop, and moving the arrow cursor will be fine. But, try dragging an icon and it will hang - provided you do it within 10 sec or so of quitting FCP X. There's no doubt it's some cleaning up that's done when FCP quits that will hang if any graphic element needs redrawing.

  • unsu Level 1 Level 1 (10 points)
    Currently Being Moderated
    Feb 22, 2013 9:34 AM (in response to Chuck Gould)

    I had the same problem: https://discussions.apple.com/message/21322029#21322029

     

    Here is a temporary fix:

    Disable the automatic switching of the graphic cards in System Preferences -> Energy Saver -> uncheck the automatic graphics switching

     

    To fix it: bring your macbook to your local apple store and ask them to fix the freezing issue. If it is related to graphics, they will replace your logic board for free (of course).

    They fixed the freezings on my macbook by replacing the logic board. These are the manufacturer's hardware defects and must be fixed.

  • andres.luna Calculating status...
    Currently Being Moderated
    Mar 4, 2013 8:07 PM (in response to sdaza)

    Hey People!!...Do not spend time describing about your problem.  The original post says "Mountain Lion Screen Freeze", then all of us understand what is happening.  I think the best way in order to guide the Apple Developers to help you to solve this issue, is showing your LOG FILE when freeze occurrs.  I did a couple of time this several months ago, and the new releases came to the light.  I waited a couple of month but finally the v10.8.2 solved the same problem you're describing.  So, posting Log Files help better than describing what you believe or think when using Apps.  Think about this...

  • seanfromminato-ku Level 1 Level 1 (0 points)
    Currently Being Moderated
    Mar 4, 2013 8:17 PM (in response to andres.luna)

    While the title of the discussion is "screen freeze", the original post talks about the screen itself not being completely frozen (the cursor etc. can be moved around) but rather the computer is completely unresponsive to mouse and keyboard operations. It quickly got of track from that original post to problems such as with GPU on macbooks. Many of us, myself included, see this problem on non laptops, where the GPU switching is not even available. The problem with logs etc. is that the only way I have to recover this is to force power off, and when I power on there is no crash report, and no information going to apple. Looking in console after the restart I can so far see no common denominators immediately before the Bootlog, so I have no meaningful information I can send. In any case, if I do get reports, how can I send these cnosole lists, logs etc. to Apple. I'd like to do so as I think otherwise they are completey unaware of this since, as I mentioned, my system is sending no information about it to apple.

  • intosh9 Calculating status...
    Currently Being Moderated
    Mar 5, 2013 7:02 AM (in response to unsu)

    The way I reproduced this annoying bug with my HD3000 on 10.7.4:

    Finder: navigate to a few JPEG images or folders, switch to a different app with

    Cmd+Tab. Then switch back again, and so on. It very often hangs with the switcher stuck on screen.

     

    Its not a complete hang; user interface appears stuck but the machine can be sshed into and tasks can be performed, e.g. "sudo reboot"

     

    As was suggested by our friendly intelligent hackintosh community, I did some testing.

    Modified the AISNBFB table with just one connector in the table. Since I only need LVDS (laptop screen) and can do without HDMI, for the time being, its OK as a workaround. Will post back if I experience any more hangs.

  • Monkeynuts1972 Level 1 Level 1 (0 points)
    Currently Being Moderated
    Mar 7, 2013 5:04 AM (in response to Monkeynuts1972)

    Well, after months of putting up with the constant freezing and trying all sorts of fixes and remedies (refer to my previous posts) I have given up and decided that it is not worth having Mountain Lion on my machine any longer. The most frustrating thing is that there is nothing in the system logs to indicate a problem - it just freezes for 30-60 seconds.

     

    Anyway, I wiped the whole mess and installed Snow Leopard a few days ago. Now running it with all the updates to 10.6.8 and so far not a freeze in sight. In fact, I forgot how good Snow Leopard is - it just works! Quick and reliable as an OS should be.

     

    I really hope that Apple will sort this out sooner rather than later. I should not be forced to take this action just to be able to use my very expensive Macbook Pro on a daily basis.

  • seanfromminato-ku Level 1 Level 1 (0 points)
    Currently Being Moderated
    Mar 10, 2013 7:34 PM (in response to andres.luna)

    I did a bit of more serious detective work and thought I had found two rogue processes from years back that I had no idea were still in my system (the drawbacks to alays migrating when rebuilding systems), and indeed I went 4 days without a freeze (a miracle), but had it happen again today. This time, however, I seemed to get a potentially meaningful crash log (a CpuResource spin report for iCloud helper). So what I want to know is, as I have read that the apple technical people don't access these groups, and as it doen't appear that any of the crash logs after these weird screen freeze forced restarts are getting sent to apple, is there an official method for getting these logs to apple so they can hopefully use the information to fix whatever it is that is annoying the beejaysus out of us all?

  • ToneDaBass Level 1 Level 1 (0 points)
    Currently Being Moderated
    Mar 14, 2013 2:45 PM (in response to seanfromminato-ku)

    Hallelujah!!! The latest Apple update seems to have fixed this problem on my rMBP. Thank you Apple!!!

  • dburr Calculating status...
    Currently Being Moderated
    Mar 18, 2013 3:18 PM (in response to sdaza)

    This just happened to me for the first time today. 2012 Mac mini, i7 2.6 GHz, 16 GB RAM, Intel HD 4000 graphics running OS X 10.8.3.  I was playing Minecraft and all of a sudden the game froze on me.  At first I thought it was just the game (I run a lot of mods and thought maybe it was some kind of mod conflict) but then noticed that al+tab, mission control, etc. didn't work, etc.

     

    I was still able to log in to the machine over ssh from one of my other machines, and when I checked the console log, I saw the messages "stampWait: Overflowed checking for stamp 0x9b4cefa on MAIN ring" and "gpu hang trying restart gpu main ring is not waiting on an event"

     

    Funny thing is, this is the first time this has happened to me, out of all the time I've owned this machine, which I normally work pretty hard (FCPX, video encoding, playing lots of 1080p content, etc.)

  • NatWitts Calculating status...
    Currently Being Moderated
    Mar 23, 2013 8:05 PM (in response to dburr)

    Had my first (and now at least 12x) screen freezes today.  iMac 27" / 3.4ghz / 8gb / Geforce GTC 680MX 2048 / 10.8.3 Mountain Lion up-to-date

     

    In addition to the entire screen freezing (mouse still moves, cycling between pointer, beachball and mickeymouse glove) There is a screen tearing phenomenom. Glitchy text. Pixelation flickering.

     

    Its most noticable on the grey log-in screen, where reveals of a pixel grid are visible.

     

    Screenshots:

    http://imgur.com/a/30xv9

     

    Please help! Screen has frozen 3x just trying to post this!!!

  • PauloVasconcelos Level 1 Level 1 (0 points)
    Currently Being Moderated
    Mar 29, 2013 4:00 AM (in response to Chuck Gould)

    This solved my problem

     

    Go to Finder "Go" menu hold the option key and choose Library. Then go to Preferences folder and trash these files:

    com.apple.finder.plist

    com.apple.sidebarlists.plist

    Restart with hold shift key

    restart again

  • bellicose100xp Calculating status...
    Currently Being Moderated
    Apr 12, 2013 8:17 AM (in response to sdaza)

    My screen has been freezing too,

     

    Early 2011 MacBook Pro 2.3 GHz Inter Core i5, 16 GB RAM, SSD 512 GB, External Monitor Connected. I use chrome all the time.

     

    below is the log, I filtered it down,

     

    Apr 12 07:30:10 Buggy kernel[0]: stampWait: Overflowed checking for stamp 0x0 on MAIN ring: called from

    Apr 12 07:30:10 Buggy kernel[0]: timestamp = 0x8f523974

    Apr 12 07:30:10 Buggy kernel[0]: ****  Debug info for *possible* hang in MAIN graphics engine  ****

    Apr 12 07:30:10 Buggy kernel[0]: ring head    = 0x36e06988, wrap count = 439

    Apr 12 07:30:10 Buggy kernel[0]: ring tail    = 0x00006988

    Apr 12 07:30:10 Buggy kernel[0]: ring control = 0x0000f001   enabled, auto report disabled, not waiting, semaphore not waiting, length = 0x010 4KB pages

    Apr 12 07:30:10 Buggy kernel[0]: timestamps = 0x8f523974

    Apr 12 07:30:10 Buggy kernel[0]: Semaphore register values:

    Apr 12 07:30:10 Buggy kernel[0]: VRSYNC: (0x12044) = 0x8f523974

    Apr 12 07:30:10 Buggy kernel[0]: BRSYNC: (0x22040) = 0x0

    Apr 12 07:30:10 Buggy kernel[0]: RVSYNC: (0x 2040) = 0x0

    Apr 12 07:30:10 Buggy kernel[0]: BVSYNC: (0x22044) = 0x0

    Apr 12 07:30:10 Buggy kernel[0]: RBSYNC: (0x 2044) = 0x0

    Apr 12 07:30:10 Buggy kernel[0]: VBSYNC: (0x12040) = 0x0

    Apr 12 07:30:15 Buggy kernel[0]: stampWait: Overflowed checking for stamp 0x207d on MAIN ring: called from

    Apr 12 07:30:15 Buggy kernel[0]: timestamp = 0x8f5239fd

    Apr 12 07:30:15 Buggy kernel[0]: ****  Debug info for *possible* hang in MAIN graphics engine  ****

    Apr 12 07:30:15 Buggy kernel[0]: ring head    = 0x36e0a1d0, wrap count = 439

    Apr 12 07:30:15 Buggy kernel[0]: ring tail    = 0x0000a1d0

    Apr 12 07:30:15 Buggy kernel[0]: ring control = 0x0000f001   enabled, auto report disabled, not waiting, semaphore not waiting, length = 0x010 4KB pages

    Apr 12 07:30:15 Buggy kernel[0]: timestamps = 0x8f5239fd

    Apr 12 07:30:15 Buggy kernel[0]: Semaphore register values:

    Apr 12 07:30:15 Buggy kernel[0]: VRSYNC: (0x12044) = 0x8f5239fd

    Apr 12 07:30:15 Buggy kernel[0]: BRSYNC: (0x22040) = 0x0

    Apr 12 07:30:15 Buggy kernel[0]: RVSYNC: (0x 2040) = 0x0

    Apr 12 07:30:15 Buggy kernel[0]: BVSYNC: (0x22044) = 0x0

    Apr 12 07:30:15 Buggy kernel[0]: RBSYNC: (0x 2044) = 0x0

    Apr 12 07:30:15 Buggy kernel[0]: VBSYNC: (0x12040) = 0x0

    Apr 12 07:30:21 Buggy kernel[0]: stampWait: Overflowed checking for stamp 0x0 on MAIN ring: called from

    Apr 12 07:30:21 Buggy kernel[0]: timestamp = 0x8f523a43

    Apr 12 07:30:21 Buggy kernel[0]: ****  Debug info for *possible* hang in MAIN graphics engine  ****

    Apr 12 07:30:21 Buggy kernel[0]: ring head    = 0x36e0bcd0, wrap count = 439

    Apr 12 07:30:21 Buggy kernel[0]: ring tail    = 0x0000bcd0

    Apr 12 07:30:21 Buggy kernel[0]: ring control = 0x0000f001   enabled, auto report disabled, not waiting, semaphore not waiting, length = 0x010 4KB pages

    Apr 12 07:30:21 Buggy kernel[0]: timestamps = 0x8f523a43

    Apr 12 07:30:21 Buggy kernel[0]: Semaphore register values:

    Apr 12 07:30:21 Buggy kernel[0]: VRSYNC: (0x12044) = 0x8f523a43

    Apr 12 07:30:21 Buggy kernel[0]: BRSYNC: (0x22040) = 0x0

    Apr 12 07:30:21 Buggy kernel[0]: RVSYNC: (0x 2040) = 0x0

    Apr 12 07:30:21 Buggy kernel[0]: BVSYNC: (0x22044) = 0x0

    Apr 12 07:30:21 Buggy kernel[0]: RBSYNC: (0x 2044) = 0x0

    Apr 12 07:30:21 Buggy kernel[0]: VBSYNC: (0x12040) = 0x0

    Apr 12 07:30:26 Buggy kernel[0]: stampWait: Overflowed checking for stamp 0x0 on MAIN ring: called from

    Apr 12 07:30:26 Buggy kernel[0]: timestamp = 0x8f523a43

    Apr 12 07:30:26 Buggy kernel[0]: ****  Debug info for *possible* hang in MAIN graphics engine  ****

    Apr 12 07:30:26 Buggy kernel[0]: ring head    = 0x36e0bcd0, wrap count = 439

    Apr 12 07:30:26 Buggy kernel[0]: ring tail    = 0x0000bcd0

    Apr 12 07:30:26 Buggy kernel[0]: ring control = 0x0000f001   enabled, auto report disabled, not waiting, semaphore not waiting, length = 0x010 4KB pages

    Apr 12 07:30:26 Buggy kernel[0]: timestamps = 0x8f523a43

    Apr 12 07:30:26 Buggy kernel[0]: Semaphore register values:

    Apr 12 07:30:26 Buggy kernel[0]: VRSYNC: (0x12044) = 0x8f523a43

    Apr 12 07:30:26 Buggy kernel[0]: BRSYNC: (0x22040) = 0x0

    Apr 12 07:30:26 Buggy kernel[0]: RVSYNC: (0x 2040) = 0x0

    Apr 12 07:30:26 Buggy kernel[0]: BVSYNC: (0x22044) = 0x0

    Apr 12 07:30:26 Buggy kernel[0]: RBSYNC: (0x 2044) = 0x0

    Apr 12 07:30:26 Buggy kernel[0]: VBSYNC: (0x12040) = 0x0

    Apr 12 07:30:31 Buggy kernel[0]: stampWait: Overflowed checking for stamp 0x0 on MAIN ring: called from

    Apr 12 07:30:31 Buggy kernel[0]: timestamp = 0x8f523a43

    Apr 12 07:30:31 Buggy kernel[0]: ****  Debug info for *possible* hang in MAIN graphics engine  ****

    Apr 12 07:30:31 Buggy kernel[0]: ring head    = 0x36e0bcd0, wrap count = 439

    Apr 12 07:30:31 Buggy kernel[0]: ring tail    = 0x0000bcd0

    Apr 12 07:30:31 Buggy kernel[0]: ring control = 0x0000f001   enabled, auto report disabled, not waiting, semaphore not waiting, length = 0x010 4KB pages

    Apr 12 07:30:31 Buggy kernel[0]: timestamps = 0x8f523a43

    Apr 12 07:30:31 Buggy kernel[0]: Semaphore register values:

    Apr 12 07:30:31 Buggy kernel[0]: VRSYNC: (0x12044) = 0x8f523a43

    Apr 12 07:30:31 Buggy kernel[0]: BRSYNC: (0x22040) = 0x0

    Apr 12 07:30:31 Buggy kernel[0]: RVSYNC: (0x 2040) = 0x0

    Apr 12 07:30:31 Buggy kernel[0]: BVSYNC: (0x22044) = 0x0

    Apr 12 07:30:31 Buggy kernel[0]: RBSYNC: (0x 2044) = 0x0

    Apr 12 07:30:31 Buggy kernel[0]: VBSYNC: (0x12040) = 0x0

    Apr 12 07:30:35 Buggy kernel[0]: stampWait: Overflowed checking for stamp 0x0 on MAIN ring: called from

    Apr 12 07:30:35 Buggy kernel[0]: timestamp = 0x8f523a43

    Apr 12 07:30:35 Buggy kernel[0]: ****  Debug info for *possible* hang in MAIN graphics engine  ****

    Apr 12 07:30:35 Buggy kernel[0]: ring head    = 0x36e0bcd0, wrap count = 439

    Apr 12 07:30:35 Buggy kernel[0]: ring tail    = 0x0000bcd0

    Apr 12 07:30:35 Buggy kernel[0]: ring control = 0x0000f001   enabled, auto report disabled, not waiting, semaphore not waiting, length = 0x010 4KB pages

    Apr 12 07:30:35 Buggy kernel[0]: timestamps = 0x8f523a43

    Apr 12 07:30:35 Buggy kernel[0]: Semaphore register values:

    Apr 12 07:30:35 Buggy kernel[0]: VRSYNC: (0x12044) = 0x8f523a43

    Apr 12 07:30:35 Buggy kernel[0]: BRSYNC: (0x22040) = 0x0

    Apr 12 07:30:35 Buggy kernel[0]: RVSYNC: (0x 2040) = 0x0

    Apr 12 07:30:35 Buggy kernel[0]: BVSYNC: (0x22044) = 0x0

    Apr 12 07:30:35 Buggy kernel[0]: RBSYNC: (0x 2044) = 0x0

    Apr 12 07:30:35 Buggy kernel[0]: VBSYNC: (0x12040) = 0x0

    Apr 12 07:30:40 Buggy kernel[0]: stampWait: Overflowed checking for stamp 0x716e31c on MAIN ring: called from

    Apr 12 07:30:40 Buggy kernel[0]: timestamp = 0x8f523a6b

    Apr 12 07:30:40 Buggy kernel[0]: ****  Debug info for *possible* hang in MAIN graphics engine  ****

    Apr 12 07:30:40 Buggy kernel[0]: ring head    = 0x36e0c9d0, wrap count = 439

    Apr 12 07:30:40 Buggy kernel[0]: ring tail    = 0x0000c9d0

    Apr 12 07:30:40 Buggy kernel[0]: ring control = 0x0000f001   enabled, auto report disabled, not waiting, semaphore not waiting, length = 0x010 4KB pages

    Apr 12 07:30:40 Buggy kernel[0]: timestamps = 0x8f523a6b

    Apr 12 07:30:40 Buggy kernel[0]: Semaphore register values:

    Apr 12 07:30:40 Buggy kernel[0]: VRSYNC: (0x12044) = 0x8f523a6b

    Apr 12 07:30:40 Buggy kernel[0]: BRSYNC: (0x22040) = 0x0

    Apr 12 07:30:40 Buggy kernel[0]: RVSYNC: (0x 2040) = 0x0

    Apr 12 07:30:40 Buggy kernel[0]: BVSYNC: (0x22044) = 0x0

    Apr 12 07:30:40 Buggy kernel[0]: RBSYNC: (0x 2044) = 0x0

    Apr 12 07:30:40 Buggy kernel[0]: VBSYNC: (0x12040) = 0x0

    Apr 12 07:30:46 Buggy kernel[0]: stampWait: Overflowed checking for stamp 0x55cb on MAIN ring: called from

    Apr 12 07:30:46 Buggy kernel[0]: timestamp = 0x8f523ac8

    Apr 12 07:30:46 Buggy kernel[0]: ****  Debug info for *possible* hang in MAIN graphics engine  ****

    Apr 12 07:30:46 Buggy kernel[0]: ring head    = 0x36e0e5c8, wrap count = 439

    Apr 12 07:30:46 Buggy kernel[0]: ring tail    = 0x0000e5c8

    Apr 12 07:30:46 Buggy kernel[0]: ring control = 0x0000f001   enabled, auto report disabled, not waiting, semaphore not waiting, length = 0x010 4KB pages

    Apr 12 07:30:46 Buggy kernel[0]: timestamps = 0x8f523ac8

    Apr 12 07:30:46 Buggy kernel[0]: Semaphore register values:

    Apr 12 07:30:46 Buggy kernel[0]: VRSYNC: (0x12044) = 0x8f523ac8

    Apr 12 07:30:46 Buggy kernel[0]: BRSYNC: (0x22040) = 0x0

    Apr 12 07:30:46 Buggy kernel[0]: RVSYNC: (0x 2040) = 0x0

    Apr 12 07:30:46 Buggy kernel[0]: BVSYNC: (0x22044) = 0x0

    Apr 12 07:30:46 Buggy kernel[0]: RBSYNC: (0x 2044) = 0x0

    Apr 12 07:30:46 Buggy kernel[0]: VBSYNC: (0x12040) = 0x0

  • tbertran Level 1 Level 1 (10 points)
    Currently Being Moderated
    May 1, 2013 11:51 AM (in response to PauloVasconcelos)

    rm ~/Library/Preferences/com.apple.finder.*

    rm ~/Library/Preferences/com.apple.sidebarlists.*

    killall Finder

     

    Inspired by a prior post, this seems to have fixed it for me. I didn't have to restart.

  • tbertran Level 1 Level 1 (10 points)
    Currently Being Moderated
    May 2, 2013 2:41 PM (in response to tbertran)

    Update: no go. Still getting the issue.

    I was thinking it was a hardware issue (faulty RAM maybe) so I ran a complete Apple Hardware Test (restart mac while pressing D) and everything came back clean...

Actions

More Like This

  • Retrieving data ...

Bookmarked By (15)

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.