-
All replies
-
Helpful answers
-
Jul 25, 2013 10:14 AM in response to gtownblastby snuffybear,Yeah, the problem didn't appear until I migrated, but that might just have been lucky for the first few days.
-
Jul 25, 2013 10:24 AM in response to jportnoyby djeucalyptus,I figured I'd add my input since this has been driving me crazy.
New MBA 13"/1.7 i7/8gb/128gb purchased the last week of June.
No migration, no nothing - I started fresh with this one. I've been experiencing the same symptoms discussed in this thread: random cutout to black and a quick keystroke brings the log-in screen back up.
No significant delay or lag here, it's just annoying, especially when I'm using my laptop to show images to others. It's happened while using a variety of programs, including mission control and a standard finder window.
It was happening at a frequency of roughtly 5 to 10 times a day. Then I installed the os update (fixing the photoshop display issue) and I didn't have the cut-to-black issue for 4 days. I thought maybe it had been solved but then it came back. twice yesterday, and twice so far today.
I don't really want to send it back only to get another that has the same issue...
Is this only happening on 8gb 13" Airs? It seems to be one of the underlying themes... and possibly with Chrome installed (although mine has done it without chrome running).
-
Jul 25, 2013 11:58 AM in response to jportnoyby dsjackson,Macbook air 11 inch, 8gb. Same problem as reported here. Happens when plugged in and on battery; happens with chrome, word, excel, and probably others as well. All software currently up to date. I find that it happens most often after just waking up from sleep--the computer just pops back into a blank screen. Single key stroke brings me to login and I'm then good to go.
Apple: get to the bottom of this.
-
Jul 25, 2013 12:32 PM in response to jportnoyby surajb,I've been having the #2 problem as well. Seems like a hardware issue than a software issue though.
I have an appointment with Genius bar later today to get this figured out, its been really annoying!
I have the 2013 13 inch Macbook Air with an 256/8gb/i7 configuration.
It happens to me only on battery power and it started out slow but now it happens every 15 minutes after I take out the plug even though the battery meter says 100%.
-
Jul 25, 2013 6:31 PM in response to jportnoyby kilani818,Hey everyone,
I just watched this video http://www.youtube.com/watch?v=BRB0fkrVIF8 regarding this issue, and someone suggested in the comments below that it might be due to magnets near the macbook air.
This seems intresting perhaps someone can try hovering an iphone or a magnet around the macbook screen and base and see if that triggers the screen to blackout. And report back to us.
Hoping to find an end to this.
-
Jul 25, 2013 7:23 PM in response to jportnoyby gtownblast,Here's a log from my recent screen blackout... note that it did not prompt me to login with password for unlocking from sleep.
7/25/13 10:20:22.406 PM WindowServer[77]: CGXSetWindowBackgroundBlurRadius: Invalid window 0xffffffff
7/25/13 10:20:22.000 PM kernel[0]: PM notification timeout (pid 194, Jettison)
7/25/13 10:20:22.000 PM kernel[0]: PM notification timeout (pid 203, Google Chrome)
7/25/13 10:20:22.000 PM kernel[0]: PM notification timeout (pid 268, Google Chrome He)
7/25/13 10:20:22.000 PM kernel[0]: PM notification timeout (pid 270, Google Chrome He)
7/25/13 10:20:22.000 PM kernel[0]: PM notification timeout (pid 272, Google Chrome He)
7/25/13 10:20:22.000 PM kernel[0]: PM notification timeout (pid 273, Google Chrome He)
7/25/13 10:20:22.000 PM kernel[0]: PM notification timeout (pid 274, Google Chrome He)
7/25/13 10:20:22.000 PM kernel[0]: PM notification timeout (pid 275, Google Chrome He)
7/25/13 10:20:22.000 PM kernel[0]: PM notification timeout (pid 345, Google Chrome He)
7/25/13 10:20:22.000 PM kernel[0]: PM notification timeout (pid 399, Google Chrome He)
7/25/13 10:20:22.407 PM loginwindow[57]: find_shared_window: WID -1
7/25/13 10:20:22.407 PM loginwindow[57]: CGSGetWindowTags: Invalid window 0xffffffff
7/25/13 10:20:22.407 PM loginwindow[57]: find_shared_window: WID -1
7/25/13 10:20:22.407 PM loginwindow[57]: CGSSetWindowTags: Invalid window 0xffffffff
7/25/13 10:20:22.419 PM loginwindow[57]: ERROR | -[LWBuiltInScreenLockAuthLion preLoad] | guestEnabled is true, but guest mode is not set to a usable value
7/25/13 10:20:22.547 PM WindowServer[77]: Created shield window 0x16a for display 0x04273c00
7/25/13 10:20:22.549 PM WindowServer[77]: device_generate_desktop_screenshot: authw 0x7f971c149b30(2000), shield 0x7f971c149580(2001)
7/25/13 10:20:22.562 PM com.apple.time[11]: Next maintenance wake [Backup Interval]: <date: 0x7f9d53209ac0> Thu Jul 25 22:40:49 2013 EDT (approx)
7/25/13 10:20:22.562 PM com.apple.time[11]: Requesting maintenance wake [Backup Interval]: <date: 0x7f9d53209ac0> Thu Jul 25 22:40:49 2013 EDT (approx)
7/25/13 10:20:22.565 PM WindowServer[77]: device_generate_lock_screen_screenshot: authw 0x7f971c149b30(2000), shield 0x7f971c149580(2001)
7/25/13 10:20:23.000 PM kernel[0]: 2376.861084: AirPort_Brcm43xx::powerChange: System Sleep
7/25/13 10:20:23.000 PM kernel[0]: AppleCamIn::powerStateWillChangeTo - root-domain power state = 0x00000002 (flags=0x00000004)
7/25/13 10:20:24.000 PM kernel[0]: en0: BSSID changed to 58:6d:8f:73:4f:af
7/25/13 10:20:24.000 PM kernel[0]: LE is supported - Disable LE meta event
7/25/13 10:20:24.000 PM kernel[0]: wlEvent: en0 en0 Link DOWN virtIf = 0
7/25/13 10:20:24.000 PM kernel[0]: AirPort: Link Down on en0. Reason 8 (Disassociated because station leaving).
7/25/13 10:20:24.000 PM kernel[0]: en0::IO80211Interface::postMessage bssid changed
7/25/13 10:20:24.000 PM kernel[0]: IOThunderboltSwitch<0xffffff8030941400>(0x0)::listenerCallback - Thunderbolt HPD packet for route = 0x0 port = 11 unplug = 0
7/25/13 10:20:26.273 PM hidd[61]: MultitouchHID: device bootloaded
7/25/13 10:20:26.000 PM kernel[0]: AppleThunderboltNHIType2::waitForOk2Go2Sx - retries = 2
7/25/13 10:20:26.000 PM kernel[0]: Wake reason: SPIT (User)
7/25/13 10:20:26.000 PM kernel[0]: 2379.290302: AirPort_Brcm43xx::powerChange: System Wake - Full Wake/ Dark Wake / Maintenance wake
7/25/13 10:20:26.000 PM kernel[0]: AppleCamIn::powerStateWillChangeTo - root-domain power state = 0x00000003 (flags=0x00000002)
7/25/13 10:20:26.000 PM kernel[0]: AppleCamIn::wakeEventHandlerThread
7/25/13 10:20:26.000 PM kernel[0]: Previous Sleep Cause: 5
7/25/13 10:20:26.000 PM kernel[0]: AppleHSSPIController::HandleMessage Device Wake by Button
7/25/13 10:20:26.000 PM kernel[0]: IOThunderboltSwitch<0xffffff8030941400>(0x0)::listenerCallback - Thunderbolt HPD packet for route = 0x0 port = 11 unplug = 0
7/25/13 10:20:26.000 PM kernel[0]: IOThunderboltSwitch<0xffffff8030941400>(0x0)::listenerCallback - Thunderbolt HPD packet for route = 0x0 port = 12 unplug = 0
7/25/13 10:20:26.000 PM kernel[0]: TBT W (2): 0x0100 [x]
7/25/13 10:20:26.000 PM kernel[0]: en0: 802.11d country code set to 'X0'.
7/25/13 10:20:26.000 PM kernel[0]: en0: Supported channels 1 2 3 4 5 6 7 8 9 10 11 12 13 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 144 149 153 157 161 165
7/25/13 10:20:26.692 PM Spotify[211]: Reachability Flag Status: -R tc----- networkStatusForFlags
7/25/13 10:20:26.696 PM WindowServer[77]: handle_will_sleep_auth_and_shield_windows: NULL auth_window
7/25/13 10:20:26.699 PM configd[17]: network changed: v4(en0-:192.168.1.112) DNS- Proxy SMB
7/25/13 10:20:26.713 PM Spotify[211]: Reachability Flag Status: -- ------- networkStatusForFlags
7/25/13 10:20:26.722 PM WindowServer[77]: Created shield window 0x16b for display 0x003f003d
7/25/13 10:20:26.722 PM WindowServer[77]: handle_will_sleep_auth_and_shield_windows: NULL auth_window
7/25/13 10:20:26.725 PM WindowServer[77]: Created shield window 0x16c for display 0x003f003e
7/25/13 10:20:26.725 PM WindowServer[77]: handle_will_sleep_auth_and_shield_windows: NULL auth_window
7/25/13 10:20:26.825 PM Spotify[211]: Reachability Flag Status: -- ------- networkStatusForFlags
7/25/13 10:20:28.000 PM kernel[0]: en0: 802.11d country code set to 'US'.
7/25/13 10:20:28.000 PM kernel[0]: en0: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 144 149 153 157 161 165
7/25/13 10:20:28.000 PM kernel[0]: AppleCamIn::handleWakeEvent_gated
7/25/13 10:20:28.000 PM kernel[0]: AppleCamIn::acpiControlS2ChipPower - powerState=0, status = 0x0, result_value = 0x0
7/25/13 10:20:30.000 PM kernel[0]: 2383.850682: MacAuthEvent en0 Auth result for: 58:6d:8f:73:4f:af MAC AUTH succeeded
7/25/13 10:20:30.000 PM kernel[0]: wlEvent: en0 en0 Link UP virtIf = 0
7/25/13 10:20:30.000 PM kernel[0]: AirPort: Link Up on en0
7/25/13 10:20:30.000 PM kernel[0]: en0: BSSID changed to 58:6d:8f:73:4f:af
7/25/13 10:20:30.000 PM kernel[0]: en0::IO80211Interface::postMessage bssid changed
7/25/13 10:20:30.000 PM kernel[0]: AirPort: RSN handshake complete on en0
7/25/13 10:20:30.864 PM airportd[408]: _doAutoJoin: Already associated to “sigal5ghz”. Bailing on auto-join.
7/25/13 10:20:30.893 PM airportd[408]: _doAutoJoin: Already associated to “sigal5ghz”. Bailing on auto-join.
7/25/13 10:20:30.929 PM airportd[408]: _doAutoJoin: Already associated to “sigal5ghz”. Bailing on auto-join.
7/25/13 10:20:31.638 PM Spotify[211]: Reachability Flag Status: -R tc----- networkStatusForFlags
7/25/13 10:20:31.644 PM configd[17]: network changed: v4(en0+:192.168.1.112) DNS+ Proxy SMB
7/25/13 10:20:31.662 PM UserEventAgent[11]: Captive: en0: Not probing 'sigal5ghz' (protected network)
7/25/13 10:20:31.669 PM configd[17]: network changed: v4(en0!:192.168.1.112) DNS Proxy SMB
7/25/13 10:20:31.670 PM Spotify[211]: Reachability Flag Status: -- ------- networkStatusForFlags
7/25/13 10:20:32.708 PM Spotify[211]: Reachability Flag Status: -R ------- networkStatusForFlags
7/25/13 10:20:35.019 PM System Preferences[419]: Cannot call setInetDServiceEnabled:enabled without first being authenticated
7/25/13 10:20:35.054 PM ntpd[73]: ntpd exiting on signal 15
7/25/13 10:20:35.167 PM ntpd[426]: proto: precision = 1.000 usec
7/25/13 10:20:35.175 PM com.apple.time[134]: Interval maximum value is 946100000 seconds (specified value: 9223372036854775807).
7/25/13 10:20:56.770 PM com.apple.backupd-helper[410]: Not starting Time Machine backup after wake - failed to resolve alias to backup volume.
-
Jul 26, 2013 1:49 AM in response to jportnoyby Herbert_Lima,Ok, My problem was solved, took 3 days in the assistance and they changed the following:
1. LCD display CLAM SHELL
2. MLB, 1.8GHZ, DC, IVB, 4GB. 13 MBA-UVS
On the first day I took the macbook they told me that the change of the display would solve the problem. But after 3 days they called me and told that it didnt... so they changed the second piece (the "Logic Bord" I think) and the problem was solved...
I think people are having different problems, but if your screen is fleackering, that should solve it. (hope it stays like this for the next 4 year at least)
Hope it helped.
-
Jul 27, 2013 1:30 AM in response to jportnoyby iterva,Just to chime in on this discussion -
I have the same/similar issue, but it does not happen that frequently. ~2-3 times a week.
It always happens when MBA has been woken from sleep.
Wake from sleep -> Login -> Continue browsing/scrolling (Safari) or/and watching movie (iTunes, VLC) or/and Mail etc -> Goes to sleep (within 5-10s) -> Press keyboard to wake -> Login.
And all good until next time, never happens 2 times in a row.
2013 - 13"/i7/8/256.
- Not using Chrome.
- Installed fresh (No migration etc)
- SW update 1.0 installed
- No magnets anywhere near the MBA
- Occurs with AC and battery use
- SMC/NVRAM reset done
- Happens regardless of time MBA has been in sleep (few minutes to several hours)
- No hot corners active
-
Jul 27, 2013 4:54 AM in response to jportnoyby alcibiadesjr,Yes i also have this problem. I move the mouse around then suddly screen goes black (like it went to sleep) then i move it around or tap on some keys to bring the screen back up then i have to log in again.
I really hope they fix this
-
Jul 27, 2013 7:39 AM in response to jportnoyby TroyKirin,I too am havning this problem, while I'm actively using my mac, maybe browing on chrome. The screen will just go black on me but the mouse still works. For a short period of time pressing or clicking anything will wake it up. I just have to wait it out for maybe 10 sec or close the lid and let it sleep. Very frustrating and am not pleased with my first mac experience.
-
Jul 27, 2013 11:51 AM in response to jportnoyby tnk479,I just experienced exactly this issue. I also have a build to order MacBook Air with 512 SSD, 8 GB RAM, and core i7 CPU. I was on battery when it occurred. The computer is 2 weeks old and this was the first time.
-
Jul 27, 2013 7:40 PM in response to tnk479by Saeid,Can anyone that has 10.8.5 Beta or 10.9 Mavericks on their MacBook Air 2013" confirm that the issue has been resolved?
-
Jul 27, 2013 10:18 PM in response to Saeidby babowa,Unfortunately, anyone who might know won't be able to answer or he'd be violating their NDA. And, discussing features of a not yet publicly released OS are not allowed here.
-
Jul 28, 2013 1:12 AM in response to jportnoyby kimgood,Oh well,
I'm experiencing the same issue with my 2013 11" 8GB/128GB
Now I just want to know whether this has to do with HW or SW, as I have to return till next week if it's HW but I really don't want to do that, thiking about all the hassle I have to endure.
-
Jul 28, 2013 6:57 AM in response to jportnoyby minalee,I too am having this problem with my customized 11" 8 Gig MacBook Air. I had this problem once, so I took the laptop back to Apple where I requested a new one since it was less than two weeks old. They customized me a new one and shipped it, and now I still have the same problem. Screen goes black randomly and won't come back for 3-4 seconds no matter what I do. Mouse doesn't work, keys don't work, nothing. I use Chrome for almost everything I do, but I can't say for sure that's the only thing I'm doing when it happens. I'm not wearing any jewelry that would interact with the magnet near the track pad, as was suggested by an Apple employee. I'm frustrated and not willing to return this one only to wait for another one to be shipped from China, so I'm hoping Apple will come up with an update that fixes this problem.