You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

sdaza Author

Level 1

19 points

Mountain Lion Screen Freeze

Hello,

the cursor freezes sometimes, but even when it moves I cannot make anything happen with it except Shut Down, the track pad is unresponsive, and the screen is frozen, and sometimes there are some problems with graphics:

This is what happens repeatly before the boot time:

8/9/12 6:19:29.000 PM kernel[0]: stampWait: Overflowed checking for stamp 0x9b4cefa on MAIN ring: called from

8/9/12 6:19:29.000 PM kernel[0]: timestamp = 0x9b4cef8

8/9/12 6:19:29.000 PM kernel[0]: **** Debug info for *possible* hang in MAIN graphics engine ****

8/9/12 6:19:29.000 PM kernel[0]: ring control = 0x0000f401 enabled, auto report disabled, not waiting, semaphore is waiting, length = 0x010 4KB pages

8/9/12 6:19:29.000 PM kernel[0]: timestamps = 0x9b4cef8

8/9/12 6:19:29.000 PM kernel[0]: VRSYNC: (0x12044) = 0x9b4cef8

8/9/12 6:19:29.000 PM kernel[0]: BRSYNC: (0x22040) = 0x0

8/9/12 6:19:29.000 PM kernel[0]: BVSYNC: (0x22044) = 0x0

8/9/12 6:19:29.000 PM kernel[0]: RBSYNC: (0x 2044) = 0x0

8/9/12 6:19:29.000 PM kernel[0]: VBSYNC: (0x12040) = 0x0

8/9/12 6:19:29.000 PM kernel[0]: stampWait: Overflowed checking for stamp 0x9b4cf0d on MAIN ring: called from

8/9/12 6:19:29.000 PM kernel[0]: timestamp = 0x9b4cef9

8/9/12 6:19:29.000 PM kernel[0]: **** Debug info for *possible* hang in MAIN graphics engine ****

8/9/12 6:19:29.000 PM kernel[0]: ring control = 0x0000f401 enabled, auto report disabled, not waiting, semaphore is waiting, length = 0x010 4KB pages

8/9/12 6:19:29.000 PM kernel[0]: timestamps = 0x9b4cef9

8/9/12 6:19:29.000 PM kernel[0]: VRSYNC: (0x12044) = 0x9b4cef9

8/9/12 6:19:29.000 PM kernel[0]: BRSYNC: (0x22040) = 0x1

8/9/12 6:19:29.000 PM kernel[0]: BVSYNC: (0x22044) = 0x0

8/9/12 6:19:29.000 PM kernel[0]: RBSYNC: (0x 2044) = 0x0

8/9/12 6:19:29.000 PM kernel[0]: VBSYNC: (0x12040) = 0x0

8/9/12 6:19:34.000 PM kernel[0]: stampWait: Overflowed checking for stamp 0x9b4cf45 on MAIN ring: called from

8/9/12 6:19:34.000 PM kernel[0]: timestamp = 0x9b4cf25

8/9/12 6:19:34.000 PM kernel[0]: **** Debug info for *possible* hang in MAIN graphics engine ****

8/9/12 6:19:34.000 PM kernel[0]: ring control = 0x0000f401 enabled, auto report disabled, not waiting, semaphore is waiting, length = 0x010 4KB pages

8/9/12 6:19:34.000 PM kernel[0]: timestamps = 0x9b4cf25

8/9/12 6:19:34.000 PM kernel[0]: VRSYNC: (0x12044) = 0x9b4cf25

8/9/12 6:19:34.000 PM kernel[0]: BRSYNC: (0x22040) = 0x1

8/9/12 6:19:34.000 PM kernel[0]: BVSYNC: (0x22044) = 0x0

8/9/12 6:19:34.000 PM kernel[0]: RBSYNC: (0x 2044) = 0x0

8/9/12 6:19:34.000 PM kernel[0]: VBSYNC: (0x12040) = 0x0

8/9/12 6:19:34.000 PM kernel[0]: stampWait: Overflowed checking for stamp 0x9b4cf59 on MAIN ring: called from

8/9/12 6:19:34.000 PM kernel[0]: timestamp = 0x9b4cf27

This is what I found just before the boot time:

8/9/12 6:24:20.000 PM kernel[0]: stampWait: Overflowed checking for stamp 0x9b4cfe7 on MAIN ring: called from

8/9/12 6:24:20.000 PM kernel[0]: timestamp = 0x9b4cf9a

8/9/12 6:24:20.000 PM kernel[0]: **** Debug info for *possible* hang in MAIN graphics engine ****

8/9/12 6:24:20.000 PM kernel[0]: ring head = 0x86a077a4, wrap count = 1077

8/9/12 6:24:20.000 PM kernel[0]: ring tail = 0x0000b910

8/9/12 6:24:20.000 PM kernel[0]: ring control = 0x0000f401 enabled, auto report disabled, not waiting, semaphore is waiting, length = 0x010 4KB pages

8/9/12 6:24:20.000 PM kernel[0]: timestamps = 0x9b4cf9a

8/9/12 6:24:20.000 PM kernel[0]: Semaphore register values:

8/9/12 6:24:20.000 PM kernel[0]: VRSYNC: (0x12044) = 0x9b4cf9a

8/9/12 6:24:20.000 PM kernel[0]: BRSYNC: (0x22040) = 0x1

8/9/12 6:24:20.000 PM kernel[0]: RVSYNC: (0x 2040) = 0x0

8/9/12 6:24:20.000 PM kernel[0]: BVSYNC: (0x22044) = 0x0

8/9/12 6:24:20.000 PM kernel[0]: RBSYNC: (0x 2044) = 0x0

8/9/12 6:24:20.000 PM kernel[0]: VBSYNC: (0x12040) = 0x0

8/9/12 6:24:20.000 PM kernel[0]: trying to clear semaphore wait on MAIN ring

8/9/12 6:24:20.000 PM kernel[0]: After attempt to clear semaphore wait = 0x0000f001 no longer waiting

8/9/12 6:24:24.997 PM coreservicesd[31]: SendFlattenedData, got error #268435460 (ipc/send) timed out from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=207

8/9/12 6:24:24.997 PM coreservicesd[31]: SendFlattenedData, got error #268435460 (ipc/send) timed out from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=214

8/9/12 6:24:24.000 PM kernel[0]: stampWait: Overflowed checking for stamp 0x9b4cfdf on MAIN ring: called from

8/9/12 6:24:24.000 PM kernel[0]: timestamp = 0x9b4cf9c

8/9/12 6:24:24.000 PM kernel[0]: **** Debug info for *possible* hang in MAIN graphics engine ****

8/9/12 6:24:24.000 PM kernel[0]: ring head = 0x86a07864, wrap count = 1077

8/9/12 6:24:24.000 PM kernel[0]: ring tail = 0x0000ba48

8/9/12 6:24:24.000 PM kernel[0]: ring control = 0x0000f401 enabled, auto report disabled, not waiting, semaphore is waiting, length = 0x010 4KB pages

8/9/12 6:24:24.000 PM kernel[0]: timestamps = 0x9b4cf9c

8/9/12 6:24:24.000 PM kernel[0]: Semaphore register values:

8/9/12 6:24:24.000 PM kernel[0]: VRSYNC: (0x12044) = 0x9b4cf9c

8/9/12 6:24:24.000 PM kernel[0]: BRSYNC: (0x22040) = 0x1

8/9/12 6:24:24.000 PM kernel[0]: RVSYNC: (0x 2040) = 0x0

8/9/12 6:24:24.000 PM kernel[0]: BVSYNC: (0x22044) = 0x0

8/9/12 6:24:24.000 PM kernel[0]: RBSYNC: (0x 2044) = 0x0

8/9/12 6:24:24.000 PM kernel[0]: VBSYNC: (0x12040) = 0x0

8/9/12 6:24:24.000 PM kernel[0]: trying to clear semaphore wait on MAIN ring

8/9/12 6:24:24.000 PM kernel[0]: After attempt to clear semaphore wait = 0x0000f001 no longer waiting

8/9/12 6:24:52.000 PM bootlog[0]: BOOT_TIME 1344554692 0

Thank you in adavnace

Sebastian

MacBook Air, OS X Mountain Lion

Posted on Aug 9, 2012 5:20 PM

185 replies

Sep 30, 2012 1:14 PM in response to dayweed

Hi everyone!!

All I can say at this moment is OS X v10.8.2 improved notably my proceses on my MBP 13" (Dec 2011), and since 1 week ago I have not had more freezes (working full at the same time with Firefox/GNS3/SecureCRT/Adobe/Parallels/iTunes/All MS Office/RealVNC/MSN/iSoftphone/ACAD/so on). I think each one have a different "freeze" case, so it will be better if you could check your system.log and paste what happen here, in order to Apple Technicians (or any delegate) could check your specific problem...someone here (including me) we did it, and in some cases the problem was solved.

I will not doubt, if anything wrong happen in the next days (a new freeze), to post again what my syslog shows.

Oct 2, 2012 11:53 PM in response to Jerry@Apple

It's been 6 days since I did my manual upgrade. There is no single freeze up and I am pretty happy with my iMac. The only thing I did afterwards was to remove Google Chrome.

Can't tell which one works now, would say the 10.8.2 combo update makes more sense.

adam1232

Level 1

2 points

Oct 3, 2012 4:10 AM in response to Jerry@Apple

Is there a difference between OS X 10.8.2 and 10.8.2 combo? Also, it is highly likely the freezes are caused by google chrome because I am always getting 2-3 logs that repeat in my console about google chrome.

Humps_s

Level 1

0 points

Oct 3, 2012 4:13 AM in response to adam1232

Not targeting you specifically, just everyone who is going down the chrome route.

THIS CANNOT BE CAUSES BY CHROME, I dont use chrome and seem to be experiencing worse symptoms than most described here...

Please apple sort this, this is my business I run from this mbp!

Humps_s

Level 1

0 points

Oct 3, 2012 4:13 AM in response to Humps_s

Caused*

Oct 3, 2012 4:23 AM in response to adam1232

i'm not sure anymore.

After changing graphic card everything works smoothly again

i havent managed to install Snow Leopard again because i have to format the HDD

but right now i am running 10.8.1 and using Chrome all the time and nothing happens

"Knock on Wood!"

i still believe that it has something to do with ML and overloading Graphic Cards.

adam1232

Level 1

2 points

Oct 3, 2012 4:23 AM in response to Humps_s

Oh ok. Well this is very frustrating for many reasons. 1. Not EVERYONE is having this problem. 2. We don't even know what's causing this yet! 3. Has apple even realized this issue?

I'm worried and angry about this and I haven't even had a freeze since the 10.8.2 upgrade. But, I do realize other people are still having the hard freezes in this new update as well.

adam1232

Level 1

2 points

Oct 3, 2012 4:25 AM in response to theWoodenKing

Well it does mention the graphics card in the logs in the console. But why would apple make a Mac's graphics card not compatible with Mountain Lion???

Oct 3, 2012 4:41 AM in response to adam1232

i have no idea, Apple should be taking this very seriously.

All i know is that i had an A-OK working Mac Pro and suddenly after installing Mountain Lion my graphic card burnt out.

The phone service mentioned it being a coincidence but a lot of people are having related problems

and i now have to buy a 250$ card just to fix the problem.

mikebrew

Level 1

0 points

Oct 4, 2012 11:16 AM in response to sdaza

I had the same issue and thought it was Google Chrome as well. It actually ended up being a file in my "/Library/Contextual Manu Items" directory which was left over from Google Drive that did not have the correct write permissions and somehow stalled my wifi connection. Once I removed the *.plist file I have not had any issues since.

keliutZu

Level 1

4 points

Oct 5, 2012 2:52 AM in response to Jerry@Apple

How did you install the 1.8.2 Combo?

I get a message that (roughly translated) "This volume does not meet the requirements for this update"

Did any of you got a strange message while updating to 1.8.2 in the first place?

My very recent Retina MBP used to run great (It came with ML preinstalled)

I updated to 1.8.2, and after the dowload, restart, update i got a message that the update was NOT correctly installed. It was just a message window with an OK button.

However, even if it was "not correctly installed" I couldn't reapply the update.

From that update everything went to ****.

If i Plug In or Out the external monitor while the computer is running, it will freeze (with graphic glitches) and need a hard reboot.

If I open for example Google Earth ( OpenGL render ) it will crash.

Only Safari works ok, every other browser has random garbled graphics ( Firefox, Chrome, Opera )

+ Other random crashes when opening PgAdmin or Photoshop.

Oct 12, 2012 10:38 AM in response to sdaza

Hey guys,

Looks like I'm not alone here. My MacBook Pro (late 2011) already froze twice after installing Mountain Lion 10.8.2. I have also updated to the cumullative patch of last week.. and this still happens. First time I was shutting down the laptop when it froze.

Now it froze right at the login screen upon a cold boot.. so I think definitely this is not due to any running browsers... this is just some weird stuff going on

Here's the video proof

If someone thinks this link earns a new thread, just let me know and I'll create one but it seems like it's the same issue people are complaining about in here..

http://www.youtube.com/watch?v=-5ef-kDiWRI

Oct 12, 2012 11:20 AM in response to sdaza

Hey all,

Just posting an update on my issue here... I'm running Mt. Lion 10.8.2. I'm on a brand new MacBook Pro (Retina) with 2.6 GHz Intel Core i7, 8GB 1600 MHz DDR3.

Many of you are posting about older mac versions and upgrading to Mt. Lion and that being the issue... I'm assuming with this machine right out of the box — the graphics card should handle it just fine.

This is not a Google Chrome issue as they've resolved their browser leak. Not to mention I get freezes when Chrome is nowhere near being open.

Here's what I do know... I had a few files in my download directory, when I would pull up that directory, I had a lot of freezes occuring (requireing a full power off and reboot — totally locked up). I narrowed the freezes down to a single file I had in that directory. I deleted this file via the Terminal. I thought the problem was resolved.

Nope.

This is my second attempt to post here, the first time I was writing this message and the freeze occured again. I'm really hoping that there's a fix to this soon. Likely, I'll be taking a trip to the Apple store soon.

Best,

Russel

iChrisbe

Level 1

0 points

Nov 2, 2012 4:48 AM in response to rslvnpryr

And now... Is it good for you ?

Not for me and my macbook white...

Thanks Apple to help your customer !

Nov 4, 2012 1:48 AM in response to Monkeynuts1972

A little update on my posting above - I have now upgraded my memory from 4GB to 8GB and it seems to have stopped the freezing so far, fingers crossed.

My experience with Mountain Lion suggests it needs more than 4GB to operate reliably or perhaps the Apple supplied memory was not of the best quality? It was generic unbranded memory.

Mountain Lion Screen Freeze