Mountain Lion freezing

if you do a clean install, from a cd and don't migrate, you should have a defaulted system with everything on the state of your install cd.

after loading all the updates, still without migrating your account you sould have an actual defaulted system, without any modification.

Now, you can use safari to produce heavy cpu and gpu loads simultaniusly viewing hi res videos on youtube.

or you can install your software step by step using it, and looking for the error before you install the next part of your software.

If you migrate with timemachine a lot software would be changed on an newly installed system. It's hard to point the error out if it relays in software.

What if you don't have a CD. Like with Mountain Lion what if I used a usb? By the way, I love your username. It's very similar to my username on a lot of other websites.

Yeah, I'm taking it to an Apple Genius Bar very soon I think. If it happens again in like 1 day or 2, I'm going there on Friday or on the weekend.

The only REAL Apple Genius Bar we have here in Sweden is a bit far away but if they can fix it I'm goin

Knock on wood, the computer has been running smoothly for the past day and 8 hours. No freezing yet..

I have the same problem and crash log entries...

on a MBP (late 2008) with the GeForce 9400M, 9600M GT cards.

It only occured after the update to 10.8.2, on 10.8.1 my machine was running completely fine

... and the 10.8.2 supplemental update didn't solve the problem 😟

@fgwinner, sounds like you and I are in the same boat. My install of ML was fresh onto a brand new drive... and I was able to wake from sleep without lockup until 10.8.2.

Right now, all I can do for a workaround is remember to religiously shut down instead of simply closing the lid anytime I want to quiesce my MBP and cart it around.

I still suspect a problem somewhere that correlates to Keychain activity.

Wait, so you think it's a problem with keychain access?

Maybe. Maybe not. I think the Keychain is definitely affected... but I have no way to know if it's at the root of the problem, or simply impacted like everything else.

In one wake-from-sleep scene, I noticed that my MBP would deny the password I was typing in. I wasn't mis-typing it or using the wrong one. It's just that OS X could not seemingly validate it.

So, like always now in 10.8.2, I had to perform a hard-restart and then - like everything else - signon worked correctly.

The thing is, Keychain is down in the guts of how a lot of things work and so I think it might be a helpful clue - if Keychain is blocked somehow, what would block it upon wake-from-sleep and in particular if that is a necessary step along the chain of events that eventually lockup the whole system?

There's no opportunity for the OS to send an error report back to Apple that I've witnessed. Eventually the beach ball takes over all open apps and the only resolution is a hard restart. So I hope Apple is culling this discussion for these kinds of clues.

I don't think Keychain is the problem or even related. I haven't had any problems with keychain access.

So far I didn't notice any problems with keychain (or at least logging on) either. Just judging from the strange 'static' that I get whenever my MBP freezes up and the systemlog entries about NVIDIA that Canadianpj described as well, I think it's related to the graphics card drivers or something...

hmmm... so far, I cannot see any involvement from graphics h/w... no mention of NVIDIA in my console messages. (I have a late 2008 MBP w/ Nvidia GeForce 9400M).

I do see messages like:

- kernel: disk0s2: media is not present

- jnl: unknown-dev: write_journal_header: error writing the journal header!

whatever is causing this blocking condition is serious business.

I just updated the firmware on my SSD. Repeated sleep and wakes and so far, no beach balls.

Keeping my fingers crossed.

My Mountain Lion Server is un-usable due to all the freezing... I can move the mouse around but I cannot click anything. Then it might do something for 30 secondes and then it freezes again. really anoying. I am running the 10.8.2

24 hours later, sleep-and-wake'd a couple dozen times, including 12 hours overnight -- and no freezing beach balls.

So, apparently my issue was outdated SSD firmware that hiccupped with the update to OS X 10.8.2. Since my SSD did not ship with my MBP back in late 2008, I can understand that.

In case it matters to anyone else, mine is an OCZ Agility 4 (SATA-III) solid-state drive. And it's now running firmware 1.5.2.

I definitely have the same problem as you, Canadianpj.... At first I only got the graphics artefacts/hangups upon wake-from-sleep, but by now it's getting more frequent and at seemingly random points in time. And as you reported, all the crashes show logs like this one:

Oct 11 16:52:12 turmeric kernel[0]: NVDA(OpenGL): Channel exception! exception type = 0xd = GR: SW Notify Error

Oct 11 16:52:12 turmeric kernel[0]: IOVendorGLContext::ReportGPURestart

Oct 11 16:52:12 turmeric kernel[0]: 0000006e

Oct 11 16:52:12 turmeric kernel[0]: 00200000 00008397 00000474 00000040

Oct 11 16:52:12 turmeric kernel[0]: 0000047e 00000ff8 00560000 0000000f

Oct 11 16:52:12 turmeric kernel[0]: 00000000 00000000 00000002

Oct 11 16:52:12 turmeric kernel[0]: 00000040 00000000

Did it work out for you to use the build-in graphics only? I'm really starting to get desperate, since those hangups make it almost impossible to work properly.

And in case it did help you, can you give me a pointer on how to make your MBP use build-in graphics only?

Thanks in advance!

I have to ask again. When you download the operating system how do you know it completed successfully? Is there a MD5 hash or equivalent that tells you have a valid download?