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

black screen after login, Mountain Lion on Macbook Retina

I've been using Mountain Lion for a while, and regularly I get a black screen, right after the login screen (after entering the password).

Often I have to reboot several times until it boots properly.


It is not clear when or why it happens: it could be some 3rd party code (gfxCardStatus, CUDA 5.0 sdk, steer mouse, Microsoft Intellimouse driver?) or something else.


Does anyone else have a similar issue?

Posted on Jul 26, 2012 9:59 PM

Reply
330 replies

Sep 10, 2012 12:41 PM in response to iseeyou4ever

The guest user login before your login is a solution ...

but it's not a reasonable one, why having a super fast computer to loose time at each start ?

Apple must take care seriously of this, these solutions reminds me other concurrent OS in the past (nowadays there are not so bad).

Imagine a PC ad with PC telling Mac to login to the guest user before using his session with his brand new MBP Retina ...), that's what we experience, not serious !

Sep 10, 2012 12:47 PM in response to Djim's

What I'm beginning to wonder is if there are any MBPr owners w/ ML that have not been affected by this issue, because it seems like, it's in all likelihood an issue that's affecting all MBPr users, and if so, why hasn't Apple made an official statement of some sort or at least inform its tech support guys of this issue?

Sep 10, 2012 12:53 PM in response to jcnyc

What I'm beginning to wonder is if there are any MBPr owners w/ ML that have not been affected by this issue, because it seems like, it's in all likelihood an issue that's affecting all MBPr users, and if so, why hasn't Apple made an official statement of some sort or at least inform its tech support guys of this issue?


One part of your question I can offer a good guess. The other a definite fact...


The reason I suspect not all MBPr owners are having a problem is because they have their display set to the best Retina setting. Unless I am wrong -- and I could very well be -- this problem only occurs when you move the display setting off the "best for retina" setting. I know in my instance, I have only been able to duplicate this problem when my setting is one below the best for retina.


Apple isn't going to make an official announcement because their engineers are still trying to find the cause of the problem and how to fix it.


There are a lot of people here trying to offer fixes, but it's funny that based on a conversation I had with one of their top executives last week, Apple engineers haven't yet been able to fix the problem. If they can't -- I don't see what these temporary workarounds are going to accomplish.


I am just as frustrated as all of you -- even moreso after talking with the Apple team directly and finding out that this problem is far from being fixed.


I am going to give it a few more months. If a fix doesn't come, I'll get a refund on the laptop. Under these circumstances, I am being told Apple should be very reasonable about offering refunds.

Sep 10, 2012 8:47 PM in response to erwincoumans

I have MacBook Pro Retina also. Received it just last week. This is my first Mac so I am at the mercy of all others posting here. From day one I created a User Account that required a login so that everything matched my Windows Network. Things had been working fine except for maybe 1 or 2 instances of the Black Screen after Login. I then added an account on the Mac for my son. After that I continually had problems with Black Screen after Login. I needed to restart every time. I did try the fix recommended by Horatio Salazar on Sept 6 and that seemed to fix the problem, so far. I have shutdown and restarted 4 times now without any hitches. Thanks Horatio for the fix. Again, since I have no history with Macs (28 years with DOS/Windows), I do not have a clue as to what the command does and why it works (so far). I noticed others that mentioned that they had this issue once they created accounts. Just thought I would add my comments so that the Apple Techs that may be troubleshooting this issue have another instance to record.


Thanks again to Horatio. Hope the fix sticks and works for others.

Sep 10, 2012 9:00 PM in response to NJ Ron

I'm sorry, I should have been more clear, but what I'm hoping for and expecting, is for Apple to officially acknowledge the problem via press statement or blog post or something. My frustration lies with the uninformed apple tech support reps who all tell me they've never heard of the issue when I'm pretty sure this is something that afflicts all MBPr's once you change the resolution settings, which I'm sure 99% of people who purchase this notebook will.


I hope you're right about the refund though, being relegated to the Best for Retina resolution on a 15 inch pretty much defeats the purpose of this notebook, for me at least. If I had discovered this within my return window, I would not be discussing this with you guys right now lol.

Sep 10, 2012 10:24 PM in response to erwincoumans

SNumbers: I've had Macs since 1987, and I don't have a clue either as to what that command does. But it seems to work, and that's good enough for me for now. On the whole, I've had good luck with these machines over the decades. So I remain optimistic.


Still, Apple's lack of public acknowledgement is of concern. Perhaps some of us should forward this information to various sites such as MacFixit. I for one will be writing to OSXDaily. Maybe some actual press coverage will kick Apple into getting this fixed NOW.

Sep 11, 2012 8:23 AM in response to LVTim


The "defaults write" command add/updates settings in a parameter file (like windows .ini file or windows registry).


In this case they are setting DBLogging parameter to an array containing 5 items. (Process, Users, OpenDirectory, Autologin, FUS).


To me it would seem they are enabling some extra logging (just by the name of the parameter DBLogging) on these functions, and in doing that may change the software path and or timing such that the particular crash we are seeing is prevented. If it works, then sounds like a work around for now.


You can read your current settings for the loginwindow via:


defaults read /Library/Preferences/com.apple.loginwindow


Steve.

Sep 15, 2012 4:02 PM in response to xpowers

To those who have used the terminal command, have any of you experienced the issue since?


On another note, I just saw this on BGR about 10.8.2:


http://www.bgr.com/2012/09/14/os-x-10-8-2-mountain-lion-update-battery-boost/


"That’s great news for customers, as the drop in battery life from Lion to Mountain Lion is unacceptable."


Nothing in there about the freezing problem.


You know what's unacceptable? A random freezing problem due to the login function that still hasn't been officially acknowledged or repsonded to by Apple. Unacceptable.

Sep 15, 2012 4:25 PM in response to jcnyc

I used the Terminal command on the day it was posted (I think just over a week ago) and have not had the problem since. I've had to restart at least twice a day since that time. I'm using a custom resolution via SwitchRes, and I disabled my guest user account. On the whole, I think I've been doing everything that everyone has tried to attribute as being the source of the problem. But the problem has not returned. Everything is working great.


I sent this thread to a few Mac news sites in the hopes that they would pick up on it; but no luck. Anyone know what the most anti-Mac site is out there? I'm sure they'd love to give it a run. Anything to get Apple's attention, since they're apparently not getting ours.

Sep 15, 2012 8:22 PM in response to erwincoumans

On my iMac, (I am having the same Black Screen issue) I ran the terminal command. When I restarted my computer the computer immediately logged out into a black screen and then came on into the log in window. I logged in again and then it black screened again and then came on into the loin window again. I restarted into another user account, logged into my account and the screen stayed on. After using the computer for a while it black screened again but did not come back on.

I am going to reinstall my operating system tomorrow morning and I would not advise anyone using this command.

Sep 16, 2012 1:27 AM in response to BlueGreen22

I also run the command line and still having black screen after login.

I called Aplle support in Denmark last week and they obviously have not heard about this. I'm not sure but think it is not apple itself is responsible for support and it is some sort of 3 part company. But they would switch the machine, although I tried to explain that this was not the machine but a software problem, I also have to install all my software again and then I surely getting the same problem again. But that is probably what I have to due for now. Or just return the machine and get my money back.


My questen is.


Is this not an officially forum?


Where is apple support ?


Is this how apple is working ?


For many years I had lenovo and also used their forum, and at least you get an anwser of some type. Or the forum admins is going to forward you request or problem to the right people.


HELLO APPLE !!!!!!!!!!! PLEASE HELP !!!!


What a disappointment.


To others stay away from apple for now. No support and ther best PC they ever made is probably going to get broken after some time and that is your own problem, not apple`s.

black screen after login, Mountain Lion on Macbook Retina

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.