MBA 13 Mid 2013 crash Black screen

Thank you, yoganinja for sharing all your diligent work on the BSOD secondary to sleep!!!

My 11" Macbook Air Mid 2013 always reproduced the Black Screen of Death with Energy Savings set to default while running on the battery or power adapter following your steps:

shortened version: Immediately after screen turns black, tap any key or keys; keyboard lights stay on but device will not wake. Must perform hard boot to restart.

SMC P-RAM, EFI and SMC firmware updates produced "no joy".

Called Apple Support today and started a case number. The engineers got a Capture_Data.dmg file of the failure.

Dec 7th the tech called me and said the engineers want me to set up a disk partition to test my device to see if it is hardware or "software" (perhaps he meant "firmware"?) related. I said I really didn't want to do that and spend another hour on the phone. The tech said he will tell the engineers I "refused" and I said "whoa.....that's a little harsh, isn't it? Why can't they test this on their mid 2013 MacBook Airs? I've spent enough time on this--we showed them the problem and how to reproduce it." The tech said he would relay that info and for me to make sure auto updates are "on".

Meanwhile using the suggested "bandaid" and it seems to work:

apple/system preferences/energy saver/battery: 15 min and deselect box "put hard disks to sleep when possible/power adapter 25 min and deselect box "put hard disks to sleep when possible"

If others wish to create a case here is the URL: http://expresslane.apple.com

Now it sounds like I wait and see. At least they didn't deny a problem!

Case No. 538481151

MacBook Air 11" mid 2013, i5 processer/4gb RAM/256gb Storage

Noticed problem occurred after upgrade to Mavericks.

I called AppleCare for this 'sleep - immediate wakeup - crash' issue and was told to bring it in for a hardware repair, so I made an appointment at the Genius Bar.

Last weekend at the Genius Bar, I mentioned yoganinja's case number 524999600 and demonstrated the issue, and also demonstrated it both in Recovery Mode and on their known good network booted Mavericks. Their diagnostics software could not find any hardware error. I also was able to reproduce the issue on 3 out of 7 MacBook Airs on display in the Apple Store, although it was harder to do than on my MBA.

The Lead Genius at the Genius Bar told me that it's being worked on by the engineers. According to him, there was no point in replacing any hardware at this time. I was told to look out for firmware updates, but no time frame could be given.

Not all Mid-2013 MacBook Airs have this 'sleep - immediate wakeup - crash' issue. In my office, there are 3 MBAs. All have the same specs: 13" / Mid-2013 / i7 / 8GB / 512 GB / 10.9 / all updates installed. One of these three cannot be crashed, no matter how hard we tried! Intriguing!

I tried to find the difference between the good one and the two bad ones, and found a single difference: the two bad MBAs have memory made by Hynix, and the good one has Elpida memory!

I would like to ask all of the Mid-2013 MacBook Air users that are having this issue to check the memory manufacturer of your MBA's memory and report it here.

Here's how you can find it:

1. click the Apple icon
2. click About this Mac
3. click More Info...
4. click System Report...
5. click Memory

There you will see a field named 'Manufacturer' with a value of 0x80AD (Hynix) or 0x02FE (Elpida).

I have the same setup i7 8GB en 512Gb WITH the Elpida chips

I DO have the problem. I have another thread on this issue. It startede after the move to mavericks. No issue with ML.

Pascal

Yeah i also have Elpida memory, so don't think thats the issue. as i have the same screen going blank issue.

Thanks Pascal Heijnen and MohammedaliH.

No relationship to the memory manufacturer then, it's not so easy after all.

Back to the drawing board...

I have had the same problem as recently as Saturday 12/07 for 90 minutes. My MBA (mid 2013) has 2 x 2MB of Elpida memory. Hmm!

Yeah in my experience bad memory would not cause such a specific and easily reproducible bug.

It's good news they don't all do it.

The issue first appeared on 2011 machines.

My first 2012 MBA did it with ML.

It'll probably turn out to be a combination of tolerances they didn't test for or a supplier who isn't meeting a tolerance. If it's a combination of components it could take a while to find.

My macbook air has the 'sleep - immediate wakeup - crash' issue. Here is the manufacturer code:

0x802C

I'm also on Elpida. Too bad there was no correlation there.

MDN64 wrote:

My first 2012 MBA did it with ML.

Was it ever resolved with your 2012 MBA?

shyannlindy wrote:

My macbook air has the 'sleep - immediate wakeup - crash' issue. Here is the manufacturer code:

0x802C

For the record, 0x802C is Micron.

How about SSDs? I've moved on now and ordered a Thinkpad, but both of my defective Macbooks had Sandisk SSDs. Somebody noted that the problem seemingly went away if a power management setting to do with disks sleeping (which would surely be meaningless with SSDs) was unchecked.

http://macgateway.com/help-and-support/find-out-if-your-macbook-air-ssd-is-a-sam sung-or-toshiba/
SD = SanDisk.

I don't think anybody every really fixed it by disabling disk sleep. If you have an Mid-2013 MBA with this issue, you can only work around it by not waking it up just after the screen goes black. So you have to train yourself or disable sleep altogether.