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

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 27, 2012 5:42 PM in response to adam1232

it might not be.

i decided to roll back to 10.8.1 using time machine today (because this all started for me when i updated to 10.8.2 last week)

everything went fine, it restored, rebooted and then it suddendly happened again...

i'm very dissapointed to say that now my mac pro will not boot at all.

The glitchy fragmented pixels now show up at startup and i cannot even CMD+R, CMD+T or even Eject to do a fresh install of Snow Leopard...

my Mac Pro was working fine till i upgraded to Mountain Lion this month and the whole system has crashed and burned since i updated to 10.8.2.

this has destroyed me since i live in Greece and there isnt an Official Apple Store in this country.

I am probably looking at a couple of hundred euros Just to get it looked at and probably forced to buy new parts

for a mac that was working in tip top condition untill i upgrade to MT.

There are only Authorised Resellers here and all they care about is selling new macs and not helping people get their machine working without bleeding them dry.

And i dont want to get started on how behind i am on my work schedule because of the constant glitches and crashes i've had this month with Mountain Lion.

This is unacceptable and i need help.

this whole affair with MT has put my job and career at risk.

adam1232

Level 1

2 points

Sep 27, 2012 5:41 PM in response to theWoodenKing

What year is your Mac? And also I could have told you that this issue happens in 10.8.1 as well.

Sep 27, 2012 5:46 PM in response to adam1232

its an 2 x 2.8 GHz quad core Mac Pro late 2008.

i saw that other people had problems with 10.8.1 but mine only appeared with 10.8.2

plus my current OSX was a Fresh install i did this month straight from 10.8.1 so i couldnt go any further back without reinstall manually SL.

adam1232

Level 1

2 points

Sep 27, 2012 6:06 PM in response to theWoodenKing

Hm. The earliest Mac Pro that can run Mountain Lion is the early 2008 so you should be fine. I am very sorry thaty you are having these problems. What are the differences between our computer that are having these freezes with Mountian Lion and the other people's computers that aren't having this issue???

Sep 27, 2012 6:15 PM in response to adam1232

Thanks 🙂

i have no clue what the differences are.

in any other case i would have though it was a Hard Drive problem but i just got a new 1TB drive a couple of months back. I paid a lot of money for this mac 4 years ago (3500 euro without the upgrade i've done along the way) and i tend to keep it clean and fresh when i can so that these kind of things wouldnt happen.

But I never would have thought that a software upgrade would cause so much damage.

i will see tomorrow what the service over here has to say and post any new updates about the matter.

i hope for the best and fear the worst.

thanks again.

Sep 28, 2012 6:34 AM in response to adam1232

Well problem solved.

After contacting the Apple phone service here in Greece and having a long chat with the operator and we came to the conclusion that the installation of Mountain Lion pushed my Nvidia 8800 GT 512MB over the hill and rendered it useless.

Thank God i have great friends and we managed to find and borrow a ATI Radeon HD XT 2600 256MB to replace my old graphics card and now everything works fine again, it started up and booted into MT without a problem.

So the conclusion is that Mountain Lion seems to be burning out graphic cards

and because of that i now have to hunt down and buy a new card that fits my 2008 Mac Pro.

PLUS i will be unistalling MT for the time being and going back to good old stable Snow Leopard, where i know everything is safe.

Still a very disapointing experience, Apple should look into this hard. Mountain Lion is breaking hardware and that is not cool.

thanks again for all the help.

Luobote

Level 1

0 points

Sep 28, 2012 5:56 PM in response to sdaza

since ive started to be more cautious on having the Mail.app running, I haven't had a single freeze in a month or so. I make sure Mail.app is never running. Also I have started to use Firefox instead of Chrome.

Now, I did update to 10.8.2 as soon as it was released, but still do not open Mail and Chrome so I don't know if the update fixed it for me.

No Mail.app and no Chrome, that's what works for me

adam1232

Level 1

2 points

Sep 28, 2012 7:59 PM in response to Luobote

That makes sense. If I had to choose any applications I think cause the freeze it would definitely be Mail.app and Google Chrome.

Sep 30, 2012 12:31 AM in response to adam1232

i don't use chrome: i use safari, and i just got the screen freeze (mouse pointer moves but clicks do nothing; after reboot, console shows "kernel[0]: **** Debug info for *possible* hang in MAIN graphics engine ****" many times in the system log at the time of the screen freeze).

this is maybe the second time it's happened. i'm running mountain lion 10.8.2 on a 13" macbook air i5 (2012).

dayweed

Level 1

0 points

Sep 30, 2012 4:36 AM in response to bunnyhero

This have not been solved in 10.8.2. THIS HAS NOT BEEN SOLVED!

I'm so frustrated by this issue. Was listen to some music in Spotify and had Safari up and running and a bunch of others apps. Boom, the computer freeze and the music kept on playing and I could move the mouse but not anything else.

In the console I got the message Sep 30 13:29:47 aeromoon kernel[0]: **** Debug info for *possible* hang in MAIN graphics engine ****

same as before on 10.8.1. What is this anyway? Is the graphic card failing on the macbook pros retina or what?

adam1232

Level 1

2 points

Sep 30, 2012 8:51 AM in response to dayweed

Yup, same error messages in console. Maybe it has to do with the graphics card but I think everyone here has different ones. I have an Intel HD 3000 512m card.

dayweed

Level 1

0 points

Sep 30, 2012 9:03 AM in response to adam1232

Yeah, that's right. I also think it has something to do with the graphics card. I'm using Intel HD Graphics 4000 512 MB and NVIDIA GeForce GT 650M 1 GB on my Retina macbook pro.

adam1232

Level 1

2 points

Sep 30, 2012 9:05 AM in response to dayweed

Well we need to find out what's causing this and get Apple to realize what's happening. What bothers me is that there are people out there who are running Mountain Lion and are not having this issue at all. By the way, I haven't had the issue yet since I installed 10.8.2 YET.

Wemyss4

Level 1

0 points

Sep 30, 2012 10:40 AM in response to dayweed

My retina MBP was doing this under Lion, about every two or three days. I took it to an Apple Store on August 17, and they kept it for five days (including a weekend) to run a hardware diagnostic on it. When I got it back, they said that they hadn't found anything wrong, said it was probably due to an issue with migrating from my old MB, and recommended a clean system install (which I didn't do). Oddly enough, it hasn't had a freeze since then. I upgraded directly to 10.8.2 about a week ago, and it hasn't returned.

Sep 30, 2012 11:07 AM in response to Wemyss4

I have been having the same problem ever since I installed Mountain Lion - Snow Leopard was rock solid on my 2011 Macbook Pro with 4GB and HD3000 graphics. I performed a clean install and wiped the disk (Samsung 830 256GB SSD with the latest firmware) before upgrading.

At first I thought it was an issue with Safari, but it seems the system can lock up at any time for no particular reason. It has done it it Firefox too. It will typically hang for about 30 seconds with the beachball going - the dock still works but I can't select anything. The top bar does not work at all. Then everything seems to catch up and all works again until the next time. It seems totally random.

I have reset the permissions, verified the disk, but nothing helps. Really disappointed in Apple.

Mountain Lion Screen Freeze