This issue happens across the board from----- the SanDisk ‘Marvell based’ SSD is found in the 128GB SSD in the Air,….
to the Samsung 256GB NGFF PCIe SSD in the Air,…..
to the 512GB Samsung SSD in the Air,
….and all RAM configs.
There are no genuine “hardware blackouts” in this thread; it’s a sleep/hibernation conflict,.... and a secondary causation from CHROME.
There is no hardware malfunction here as meant a: “screen blackout from power fault/battery, broken contact, damaged HD/ CPU etc.”
Two issues causing this independent of each other, are Google Chrome, and a sleep fault.
Before that however, REGARDLESS of what anyone in this thread has posted, this is in no way a “widespread” issue by any means, not even remotely close to it, …however anyone with this issue, that’s no consolation or help, of course. 😊
Sleep Cause: 5 posted here in this thread:
31/07/2013 09:57:57.000 kernel[0] Previous Sleep Cause: 5
diff user report:
Aug 2 12:01:32 macair kernel[0]: Previous Sleep Cause: 5
diff user report:
7/30/13 10:14:58.000 PM kernel[0]: Previous Sleep Cause: 5
diff user report:
7/16/13 7:59:49.000 PM kernel[0]: Previous Sleep Cause: 5
The sleep cause:5 means the computer went to sleep after idle time expired.
SLEEP CAUSE LIST:
0 = restart (user initiated)
3 = hard shutdown (power button held down for 4+ seconds)
5 = shutdown (user initiated thru system, ie, shutdown from apple menu or shell)
Your Air is going into auto power down sleep before loading the hibernate file before becoming active again. When opening again, it blacks out due to continuing to try to load hibernation.
See also on same:
http://www.laszlopusztai.net/2012/11/09/hibernate-file-issue-with-macbook-2012-u pdate/
What is happening here is the system's power manager (called the Power Management Unit or "PMU" on PowerPC machines, and the System Management Controller or "SMC" on Intel machines) is receiving a signal to perform an emergency shutdown of the system, and cuts power to the system in ways that serve to prevent surges and other harmful electrical events.
The power manager can receive the signal for a variety of reasons including user-initiated events. The system will receive the signal; the power manager will store the event as a number code, and then will shut the system down.When the system starts back up, the kernel will poll the power manager for any events to output to the system log, and if there was an unexpected shutdown it will output the event to the log. Unfortunately there is little information on the exact meaning of the number codes used for these events, but when they happen they are because of a hardware-level failure that is resulting in the system crashing.
***As to the 2013 Air, this is most certainly a conflict between the power management & Haswell processor; also conflict in the battery output which starts / causes initiation towards the Sleep Cause: 5
*Good news, of course, simple firmware/ software fix.
*As for the “2 effects seen”
1. Flickering
2. Screen goes to sleep (have to login again)
There is no “issue #1”, tomtappers issue is utterly unrelated, and has to do with his reed switch, which to mention does NOT have to be near a magnet to be at fault, mere movement CAN set off a reed switch if faulty.
This video which many of you keep referring to, has nothing to do with this specific issue, as meant this video:
http://www.youtube.com/watch?v=BRB0fkrVIF8&feature=youtu.be
*Chrome related causation:
http://qnundrum.com/answer.php?q=29953
http://apple.stackexchange.com/questions/19574/why-does-my-macbook-pro-take-so-l ong-to-go-to-sleep
ALSO SEE: Google Chrome and Kernel Panics
https://discussions.apple.com/thread/4042029?start=0&tstart=0
http://gizmodo.com/5921609/new-macbook-air-crashing-blame-google-chrome-probably
FIXES
Fix #1
Disable sleep login: System Prefs > Security > General > Require password checkbox? CHECK NO
Fix #2
Uncheck the "Put hard drive asleep when possible" AND uncheck “enable power nap” on both battery and power.
Fix #3
Install Caffeine for Mac, unless you’re adamantly inclined not to. ITS FREE
http://caffeine.en.softonic.com/mac
Fix #4
Create an error log for Chrome to fix THEIR end of the problem, or simply use Firefox or Safari
Fix #5
Wait for software fix for this very limited number of Air machines that experience this fault. Simple software here, no hardware at fault.