Mid-2013 Macbook Air screen goes black?

same blackouts here, brand new air 13

is there a ticket or some kind of tracker for this issue (or any other issue in general)?

I've got an 11" that I just got a few days after launch and I have had the exact same issue since day one. The frustrating thing is this was a replacement for a previous gen that had to be serviced multiple times. Hopefully they come out with a fix soon.

Brand new 13-inch MBA, 8-gigs, i7, doing the same thing. I notice that it also seems to reset the launcher -- I lose wireless connection and my Dropbox sync goes offline. It is only dark for a few seconds, but a nuisance nontheless.

I think it's pretty safe to say it's a very widespread OS issue. Although there's a few on this thread experiencing serious problems, a few who are making a big thing out of it, it is a relatively minor inconvenience for most and an intermitent one at that.

It's not happened to me now for days, but has happened to my wife on her Macbook Pro twice. Under normal circumstances she wouldn't have mentioned it but for the fact that I'd been complaining about it on my Air. I suspect her behaviour is relatively standard where for most people it'll happen a couple of times, they'll bash the keyboard, computer will wake, they'll shrug their shoulders and then carry on with what they were doing.

Just got the new mid-2013 i7, 256gb 8gb version for 2 weeks, and noticed the same problem. Randomly blacks out and goes to sleep mode and comes back to login screen. i'm started to worry it might be a hardware issue. Should I be swapping those out?

I and 2 others in my office are having the same problem with brand new MacBook Air 13". Apple please fix. This is a major problem and is now occuring daily.

Bought a 13" MBA last month, my first Apple product since the iPhone 3g (first Apple computer in almost a decade). i7, 256GB, 8GB. Having the same problem with black screens upon waking, and have had at least 4 complete lockups where I had to hold down the power button during a black screen and get it to reboot.

Needless to say, it doesn't "just work".

Should I be making an appointment to get it looked at/possibly swapped? Or is that not helping anyone?

Quick update.

I recently turned off the "Put hard drive asleep when possible" option within battery and power adapter mode. attached screen shots for my settings. I haven't had the problem for the last two days since I have updated this setting. I will continue to report any issues on this but I am 75% sure this has something to do with it.

After another day I still haven't had the problem after switching that option off. I've been running mostly off the battery too, using Chrome, etc. More later. Stay tuned...

Thanks for the update. I had this happen during a business presentation yesterday which is not acceptable. Apple had better be looking at this as a priority.

Sorry to tell you i disabled both as well and it's happened 10 times in the last hour.

doesn't this somewhat impact the battery life ??

Maybe to a miniscule amount because the Macbook Air has a solid state drive in it instead of a traditional hard drive. So no moving parts, no motors, etc. It would be the equivalent of leaving a flash drive in your USB port all the time.

Don't bother.

I replaced with a brand new one, but it took only a couple of hour just to realize that this doesn't help at all.

I wasted time and energy just to get this replaced and all in vain... setting up and backing up a computer cost a lot of your mojo.

I hope my case was just like that of this thread starter, but maybe I'm not good at a lottery.

How about others who recently got a new one, I'm quite at a loss with what to do next.

FYI: Another day running off battery after disabling hard drive sleeping in Energy Saver prefs - still no flickers.

This might be unrelated, but it could be a hardware issue so this may point to the root of the problem we're having here.

In Chrome, on the New Tab page the screenshot thumbnails' colors are inverted. This could be a problem specific to Chrome, but on this thread over at MacRumors, everyone having this problem in Chrome is using... *drumroll* ...a mid 2013 Macbook Air.

If it is a bad graphics card, that'd be real unfortunate news. Maybe it's a bad driver causing everything?

I'm just spitballing at this point.