Ashadur

Q: 27' iMac (2011) Screen turns off

This has been going on for me for the past few months on and off, it just randomly switches the screen off but everything else works perfectly, for example if im watching a video on hulu i can still hear the sound, if im doing work on word the documents are still there, iv finally gotten video footage of it.

 

Screen turning off:

http://youtu.be/l6DfD7o_fXs

 

Screenshot of my settings

http://i.imgur.com/pPvUH.jpg

 

To turn it back on i press "ctrl + shift + eject" and then move the mouse.

 

Any help will do, i have contacted Apple support on the phone they did say bring it in, just need to make an appointment. If anyone else has this problem and knows a better solution than having to keep pressing buttons to turn the screen back on please share.

 

Thank you in advance

- Ashadur

iPhone 4S, iOS 5

Posted on Jun 27, 2012 3:39 PM

Close

Q: 27' iMac (2011) Screen turns off

  • All replies
  • Helpful answers

first Previous Page 8 of 16 last Next
  • by Mirkin23,

    Mirkin23 Mirkin23 Jul 20, 2013 10:38 AM in response to nedandcj
    Level 1 (0 points)
    Jul 20, 2013 10:38 AM in response to nedandcj

    Thanks for the brightness tip, mine was turning off every 2 minutes and now it's just a flicker now and again. Not ideal, there should definately be a product recall but your tip really helped.

  • by Olilux,

    Olilux Olilux Jul 21, 2013 10:26 AM in response to Ashadur
    Level 1 (0 points)
    Jul 21, 2013 10:26 AM in response to Ashadur

    Welcome to the club I could say to myself...

    I have a 27" iMAC from Mid 2010 with the same problem.

    I have read all the posts and so much for my patient. It is in a relatively cool office, it still runs Lion 10.7.5 and has never been upgraded to 10.8. I hardly believe it has to do with power supply because the problem seems to come from all over the place. i.e. USA with 110V/60Hz and Europe with 220V/50Hz.

    My black screen is so bad now that the iMAC stays on for hardly longer than a few minutes after startup. I put the brightness down to minimum and this works but the problem is still there. Interrestingly does the Safe Mode not change anything.

    I would like to reinstall the OS with Bootcamp and using windows7. Wonder if that changes anything.

    I am still convinced that this is a software problem because the Screen works fine... if it works.

     

    N.B: I just saw the video on Youtube. My iMAC does not seem to have the problem with backlit. It goes pitchblack as if the monitor is turned off. It does not come cack either. I tried the "Shift+CTRL+Eject" and the screen comes back for a few seconds. The only way to get it back is "REBOOT".

  • by MarkusWinter,

    MarkusWinter MarkusWinter Aug 4, 2013 12:14 PM in response to Olilux
    Level 1 (4 points)
    Aug 4, 2013 12:14 PM in response to Olilux

    Hi,

     

    I have a late 2009 27in iMac. Apple did the Samsung 1 TB harddisk replacement, but since then I have the problem that the monitor keeps going to sleep. It can be every 2 minutes, or it can be 3 days till it happens, but happen it will.

     

    The Mac is running, I can see the desktop dimly when I shine a light on it, and by making the bottom right corner activate the screen saver I can get it back to working by moving the mouse to the bottom right corner and out again, thereby activating and deactivating the screen saver.

     

    The problem doesn't seem to be temperature related. After reading

     

    http://blog.macsales.com/16878-imac-hard-drive-upgradeability-expanded/comment-p age-1#comment-63865

     

    I wonder if Apple put a "not completely compatible" drive in …

  • by HenkRoodt,

    HenkRoodt HenkRoodt Aug 4, 2013 4:28 PM in response to Ashadur
    Level 1 (0 points)
    Aug 4, 2013 4:28 PM in response to Ashadur

    Mid 2011 iMac 27" with extra display memory, etc, same problem with screen going blank. 

    Work-around was to set a screen save hot corner bottom right.  This worked well enough so I could get work done.  I have Apple care, but not sure all the replacements will sort it out.  So phoned Apple support and after a good technical and friendly discussion I was asked to reset PRAM according to this link:

    support.apple.com/kb/ht1379

    This has solved it for me for now.

     

    Henk

  • by SteveMcQueen1971,

    SteveMcQueen1971 SteveMcQueen1971 Aug 7, 2013 1:09 PM in response to HenkRoodt
    Level 1 (0 points)
    Aug 7, 2013 1:09 PM in response to HenkRoodt

    I applied resetting the NVRAM as suggested in http://support.apple.com/kb/ht1379 two days ago.

    I decided then to re-set the brightness to a normal level as I was using the only trick that have worked so far which is to set the brightness to the max level.

    As a consequence, I just got a blank screen again this evening.

     

    So I conclude resetting the NVRAM does not solve the problem and does not even improve the situation.

     

    Back to a very bright screen...

    I need some sunscreen and sun glasses! (^^,)

     

    Pascal

  • by HenkRoodt,

    HenkRoodt HenkRoodt Aug 7, 2013 1:20 PM in response to SteveMcQueen1971
    Level 1 (0 points)
    Aug 7, 2013 1:20 PM in response to SteveMcQueen1971

    Thanks for that feedback Pascal.  Will go check my machine when I'm back at office to see if brightness setting changes induce the problem for me. 

    Just a note: It took me two tries to actually reset the PRAM using my wireless keyboard.  On the first try It did not work and I checked procedure carefully before getting it right using a USB  keyboard. 

    Henk

  • by HenkRoodt,

    HenkRoodt HenkRoodt Aug 7, 2013 1:23 PM in response to HenkRoodt
    Level 1 (0 points)
    Aug 7, 2013 1:23 PM in response to HenkRoodt

    Note:  make sure you actually reset PRAM.  You know it worked when you are asked to set some core system parameters after the procedure. 

    It is possible with wireless keyboard from Apple, but try and use a USB one for this exercise.

    Keen to hear if this works for someone, or if my one was a once-off.

    Henk

  • by SteveMcQueen1971,

    SteveMcQueen1971 SteveMcQueen1971 Aug 7, 2013 2:02 PM in response to HenkRoodt
    Level 1 (0 points)
    Aug 7, 2013 2:02 PM in response to HenkRoodt

    Henk,

     

    I only have a Bluetooth keyboard but I can to borrow one...

    When I held [Command (⌘)] + [Option] + [P] + [R] while cold booting the PC, the behavior was as described in step 5.

    The computer restarted once again and I heard the startup sound for the second time.

    Then I was not asked to reset parameters such as speaker volume, screen resolution, startup disk selection, and time zone information as described in the procedure.

    I double checked those just in case and I actually had to reset the time zone that was changed from Central Europe (I live near Paris) to one of the American ones.

    My speaker volume, screen resolution were set to the max values anyway and I only have on disk.

    So I thought it all worked. Maybe not...

     

    I'll try it again with a USB keyboard and I'll get back to you.

     

    On your side how long has it been working since you did reset NVRAM/PRAM?

     

    Pascal

  • by goombamd,

    goombamd goombamd Aug 7, 2013 3:04 PM in response to HenkRoodt
    Level 1 (0 points)
    Aug 7, 2013 3:04 PM in response to HenkRoodt

    Add me to the list. Mid-2010 iMac 27" still under AppleCare.

    I have had 32gb of Crucial RAM in it since I purchased it. (Upgraded immediately)

     

    I've had nothing but problems with this iMac.  Ever since Lion, I had WiFi dropping issues that never really got resolved.  They are better in Mountain Lion, and much more tolerable... but not perfect like my other apple products.

     

    The screen blackout is happening more and more over past month.  Now I feel like I've spent more time trouble shooting this machine than it's worth... which is frustrating when you buy a top of the line machine at the time of purchase.

     

    Anyway, hope this info helps someone:

     

    HACK FIX (Not ideal, but makes it more manageable):

    After 3 calls with Applecare and a trip to Apple Store genius bar, still not fixed.  I actually "RE-ENABLED" hot corner to make it a little bit more tolerable.  (I previously deactivated hot corner to see if that was the issue)

     

    When the display blacks out, which it does several times a day... usually 3-8 times in a row in a short period of time... I just drag my mouse to the corner and out of the corner and then the display wakes up.  I also changed the setting so I didn't have to re-enter my password immediately on display wake up.

     

     

    Here's what I've tried, with no success:

    -Reset SMC (numerous times)

    -Reset PRAM (numerous times)

    -Adjusted Energy Saver settings

    -Turned on Caffeine (screen blackout still occurs)

    -Turned off FileVault -- allowed hard drive to decrypt

    -Re-installed OSX Mountain Lion

    -Ran Apple Hardware Test that came on DVD.  (The first time, the screen would black out and not wake up.  Waited for hours.  The next day, I tried it again and everything passed).

    -Avoided different programs.. but nothing consistently turns the screen off.  e.g. at first I thought it was Chrome, so I switched to Safari.. same issues.

    -Found reproducible logs on Console (see below).  These also probably show that I'm waking up the screen with a hot corner.

     

     

    Of note, the screen blackout is not true sleep mode:

    -I can still "Share Screen" from my macbook to my iMac.  If I am already sharing screen.. the macbook doesn't change at all.. but I can't wake up the screen on my iMac without the hot corner or SHIFT-CONTROL-MEDIA-EJECT (unresponsive to mouse, keyboard)

    -If music is playing, it does not stop

    -Pressing the power button in back puts the iMac into true sleep mode, then pushing it again in a few seconds wakes it up (including the screen)

     

     

    Of course, the problem did not happen during my ~1 hour at Apple Store.  Since decryption was going to take >1 day, I decided to take my iMac back hoping that decrypting and reinstalling would fix the issue.  It didn't (I still haven't re-encrypted).

     

     

    re: Heat -- I thought that was the issue too.  Heat may or may not exacerbate it, but it definitely happens when the machine is cold or recently waken from a long sleep as well.

     

    re: Logic board -- I've read lots of posts pointing to a problem with logic board.

     

    re: Screen - I've also read lots of posts saying that replacing the screen can help, but doesn't always.

     

    Here are some good links describing similar problems:

    https://discussions.apple.com/thread/5118135?start=105&tstart=0

    http://forums.macrumors.com/showthread.php?t=1234778

     

     

    Console Logs that seem pretty reproducible:

     

    8/7/13 4:50:17.109 PM WindowServer[89]: CGXSetWindowBackgroundBlurRadius: Invalid window 0xffffffff

    8/7/13 4:50:17.109 PM loginwindow[41]: find_shared_window: WID -1

    8/7/13 4:50:17.110 PM loginwindow[41]: CGSGetWindowTags: Invalid window 0xffffffff

    8/7/13 4:50:17.110 PM loginwindow[41]: find_shared_window: WID -1

    8/7/13 4:50:17.110 PM loginwindow[41]: CGSSetWindowTags: Invalid window 0xffffffff

    8/7/13 4:50:17.276 PM WindowServer[89]: Created shield window 0x3a6 for display 0x042735c0

    8/7/13 4:50:17.280 PM WindowServer[89]: device_generate_desktop_screenshot: authw 0x7f82b96471b0(2000), shield 0x7f82b8637990(2001)

    8/7/13 4:50:17.360 PM WindowServer[89]: device_generate_lock_screen_screenshot: authw 0x7f82b96471b0(2000), shield 0x7f82b8637990(2001)

    8/7/13 4:50:18.245 PM WindowServer[89]: handle_will_sleep_auth_and_shield_windows: releasing authw 0x7f82b96471b0(2000), shield 0x7f82b8637990(2001), lock state 2

    8/7/13 4:50:18.246 PM WindowServer[89]: handle_will_sleep_auth_and_shield_windows: errs 0x0, 0x0, 0x0

    8/7/13 4:50:18.248 PM WindowServer[89]: Created shield window 0x3a7 for display 0x003f003d

    8/7/13 4:50:18.248 PM WindowServer[89]: handle_will_sleep_auth_and_shield_windows: releasing authw 0x7f82b96471b0(2000), shield 0x7f82b8637990(2001), lock state 2

    8/7/13 4:50:18.249 PM WindowServer[89]: handle_will_sleep_auth_and_shield_windows: errs 0x0, 0x0, 0x0

  • by HenkRoodt,

    HenkRoodt HenkRoodt Aug 7, 2013 4:48 PM in response to Ashadur
    Level 1 (0 points)
    Aug 7, 2013 4:48 PM in response to Ashadur

    Pascal, my system is now working for about two weeks.  I am in New Zealand on 220V supply via a UPS.  I have extra screen RAM.  I bought the high-end display card at the time and I am driving a second display via Thunderbolt.  That display stays on even when the iMac blinked. 

    I checked temperature, workload running several Apple approved packages, worked wit a clean install of ML, and only the PRAM reset recently changed anything.  I do see the screen doing a slight flicker every so often, but it does not go black.  Checked working temperature, room is at 18°C all the time via aircon.  It is not a heat issue as far as I can tell.

    I wonder how many people here have that specific expanded display card with the extra RAM.  Also had my HDD recalled and replaced. 

    One thing is clear, if this happens again I will ask for a replacement machine under NZ law.  The machine is not working as intended, and given that I have Apple Care I have done my bit.  It is not my job to fix or trouble shoot a product that was sold to me.

    Will keep you posted

    Henk

  • by goombamd,

    goombamd goombamd Aug 8, 2013 11:59 AM in response to HenkRoodt
    Level 1 (0 points)
    Aug 8, 2013 11:59 AM in response to HenkRoodt

    So, I did a time machine backup and then completely reinstalled a fresh copy of osx (deleted everything)... it is still blacking out.  no temperature warnings... does not feel hot at all.  I'm managing to catch it on video so hopefully that works at genius bar if it cant be reproduced there....

     

    Not a software issue if a complete reinstall doesnt take care of it.

  • by SteveMcQueen1971,

    SteveMcQueen1971 SteveMcQueen1971 Aug 13, 2013 3:38 PM in response to HenkRoodt
    Level 1 (0 points)
    Aug 13, 2013 3:38 PM in response to HenkRoodt

    Henk,

     

    I borrowed a USB keyboard yesterday and re-applied the procedure twice to make sure I did it right.

    I didn't had to reset/restaure the settings but the computer behaved as described in the procedure (again).

    I did this yesterday and guess what tonight, so less than 24hours after I've reset the PRAM/NVRAM and dimmed the screen, ...

    ...got a black one again!

    It used to take much longer before and this time I barely used the computer between the time I reset it yesterday evening and the second time I used afterward tonight. I was myself surprised it happened again so quickly.

    So I am back in "Sunlamp" mode... (^^,)

    Thanks anyway for the trick. It might have worked for me too...

     

    So far the only "trick" that worked for sure (for me) is to set the brightness to the max.

    It is still better than a totally black screen. (^^,)

    Pascal

  • by ChristopherES,

    ChristopherES ChristopherES Aug 16, 2013 10:41 PM in response to SteveMcQueen1971
    Level 1 (0 points)
    Aug 16, 2013 10:41 PM in response to SteveMcQueen1971

    Is this the solution, finally?

    http://9to5mac.com/2013/08/16/apple-opens-graphics-card-replacement-program-for- some-mid-2011-imacs/

    9to5Mac is reporting that graphics cards of MY2011 iMacs will be replaced free - Apple is finally admitting there's a problem.

    My iMac (same problem as all of yours) was fixed by Apple free a while ago, but not without a fight. Hopefully this will solve quite a few more problems for people.

    Good luck!

  • by mebyard,

    mebyard mebyard Aug 17, 2013 5:31 AM in response to ChristopherES
    Level 1 (0 points)
    Aug 17, 2013 5:31 AM in response to ChristopherES

    Thanks ChristopherES:  It certainly won't be the solution for all; my machine does not qualify.  It doesn't meet their serial number range.  BUT... let's hope this does lead to Apple finally "discovering" that a significant screen blackout problem does exist in many of their mid-2011 iMacs.

     

    I have not reported in for a while; I've been performing a long-term experiment.  But now I want to give out this FINDING to those following this thread.  Last February I had to cough up the cash and purchase a new iMac.  I use mine professionally and could not tolerate the screen blackout issue.  This "freed up" the problem machine and allowed me to do some experimentation that I could not otherwise (as I sat in my very dark room, attempting to see the image with minimum screen brightness and internal fans clocked out)!   I did try the "max screen brightness" that some have used as a work-around, but it didn't work for me.

     

    Since the problem started only AFTER I upgraded to Mt. Lion (some had the problem start with their Lion upgrade), I thought I would try to re-image the machine with it's native OS, Snow Leopard, Mac OS 10.6.  I dug out my install discs, re-partitioned the drive, and installed a pristine Snow Leopard image.  I did all the Apple updates for that OS (through Software Update) and then gave the machine to a friend to use, and use as hard as she could.  I explained the issue and she has been using it a lot, at varied screen brightnesses.

     

    To date she has had only two screen blackouts... of sort... after almost 6 months of use.  But these blackouts have not acted like our common problem because she was able to JUST TOUCH the power button and the screen instantly popped back on.  In other words, she did not have to invoke genuine "sleep" and then wake the machine OR reboot the machine.  It was as if the video display went into normal display sleep, but she was using the machine actively each time this happened and I had her check to make sure that she didn't have a "sleep hot corner" set up.

     

    The bottom line is this: with the native Mac OS 10.6 running, the problem seems to have disappeared!  NOW... IF WE ASSUME THAT THE PROBLEM IS REALLY WITH THE LCD BACKLIGHT PANEL (which seems to be the sensitve componentry) then we can PERHAPS conclude that some code in the later OS upgrades—perhaps graphics cards driver code (???)—is causing the hardware failures.  Obviously something in the new OS code is precipitating this issue.

     

    Thanks for all who have contributed to this thread.  Obviously this IS an Apple issue, but for those of us who forgot/or didn't purchase the AppleCare extended warranty, it has become our problem, at least for the present.

     

    Regards to the Thread,

     

    Mark Byard

    Ponca City, OK USA

    <Email Edited by Host>

  • by goombamd,

    goombamd goombamd Aug 21, 2013 9:57 PM in response to goombamd
    Level 1 (0 points)
    Aug 21, 2013 9:57 PM in response to goombamd

    As an update:

     

    Apple store kept my iMac for over 1 week and states they could not replicate the issue.  They would not test it with my RAM because they said 32GB is not supported in the mid-2010 released iMac.

     

    They concluded it must be my RAM even though it was functioning properly for the past 2.5 years and passed all memory tests.  I was told I would have to put in Apple Certified RAM and replicate the issue for them to take another look.

     

    I asked Apple what type of testing they did and they claimed they tested it with different sleep settings and could not replicate the screen black out issue.  They also claimed that they did not have the CGXSetWindowBackgroundBlurRadius: Invalid window 0xffffffff error come up at all in the console when I called to check.  They did not clear the console and this error in fact showed up 4 times during their testing.  The sleep settings were set to NEVER for both display and computer sleep... making me believe they did not in fact test with "normal" sleep settings.  The problem is so random that you actually have to sit down and use the computer for typing text documents, e-mails, watching youtube, etc for the problem to start happening.  Then it happens a few times in a row... sometimes once or twice, sometims 5-10 times.

     

    Earlier this evening, I put in 4GB of Apple original Samsung RAM.

     

    With less than 2 hours of total use (probably less than 1) with the 4GB of RAM, the iMac screen has gone black twice.  This is still a fresh install of Mountain Lion as I did not want to restore from TimeMachine only to have the problem recur.  I am trying to capture it on video again with the 4GB.

     

     

    To make matters more confusing, the console did not have the CGXSetWindowBackgroundBlurRadius: Invalid window 0xffffffff error the last 2 times it blacked out.

     

    I'm beginning to wonder if

    device_generate_desktop_screenshot: authw 0x0(0), shield 0x0(0)

    OR

    device_generate_lock_screen_screenshot: authw 0x0(0), shield

    is the culprit.

     

     

    CONSOLE LOG containing 2 blackouts at 12:15AM and 12:20AM

     

     

    8/22/13 12:15:23.193 AM coreaudiod[113]: Disabled automatic stack shots because audio IO is active

    8/22/13 12:15:56.931 AM WindowServer[88]: Created shield window 0x95 for display 0x042735c0

    8/22/13 12:15:56.936 AM WindowServer[88]: device_generate_desktop_screenshot: authw 0x0(0), shield 0x0(0)

    8/22/13 12:15:56.957 AM WindowServer[88]: device_generate_lock_screen_screenshot: authw 0x0(0), shield 0x0(0)

    8/22/13 12:16:16.007 AM coreaudiod[113]: Enabled automatic stack shots because audio IO is inactive

    8/22/13 12:16:16.000 AM kernel[0]: Wake reason: PWRB (User)

    8/22/13 12:16:16.000 AM kernel[0]: Previous Sleep Cause: 5

    8/22/13 12:16:16.000 AM kernel[0]: 9042.897044: setDISASSOC from ATH_INTERFACE_CLASS disconnectVap

    8/22/13 12:16:16.000 AM kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).

    8/22/13 12:16:16.000 AM kernel[0]: en1::IO80211Interface::postMessage bssid changed

    8/22/13 12:16:16.000 AM kernel[0]: 9042.933439: setDISASSOCIATE ****STA SYNC DISASSOC SUCCESS 

    8/22/13 12:16:16.227 AM WindowServer[88]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1

    8/22/13 12:16:16.244 AM WindowServer[88]: Created shield window 0x96 for display 0x003f003d

    8/22/13 12:16:16.244 AM WindowServer[88]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1

    8/22/13 12:16:17.051 AM configd[17]: network changed: v4(en1-:10.0.1.16) DNS- Proxy- SMB

    8/22/13 12:16:17.000 AM kernel[0]: en1: BSSID changed to 00:1e:52:78:01:d5

    8/22/13 12:16:17.000 AM kernel[0]: en1::IO80211Interface::postMessage bssid changed

    8/22/13 12:16:17.000 AM kernel[0]: AirPort: Link Up on en1

    8/22/13 12:16:17.000 AM kernel[0]: 9044.202272: apple80211Request[10310] Unsupported ioctl 181

    8/22/13 12:16:17.000 AM kernel[0]: en1: BSSID changed to 00:1e:52:78:01:d5

    8/22/13 12:16:17.000 AM kernel[0]: en1::IO80211Interface::postMessage bssid changed

    8/22/13 12:16:17.000 AM kernel[0]: AirPort: RSN handshake complete on en1

    8/22/13 12:16:17.480 AM hidd[54]: MultitouchHID: device bootloaded

    8/22/13 12:16:18.288 AM coreaudiod[113]: Disabled automatic stack shots because audio IO is active

    8/22/13 12:16:19.847 AM coreaudiod[113]: Enabled automatic stack shots because audio IO is inactive

    8/22/13 12:16:28.763 AM configd[17]: network changed: v4(en1+:10.0.1.16) DNS+ Proxy+ SMB

    8/22/13 12:16:28.771 AM mDNSResponder[46]:  24: Could not write data to clientPID[-1]()  because of error - aborting connection

    8/22/13 12:16:28.775 AM mDNSResponder[46]:  24: DNSServiceGetAddrInfo      v4v6 9-courier.sandbox.push.apple.com. PID[-1]()

    8/22/13 12:16:28.775 AM mDNSResponder[46]:  28: Could not write data to clientPID[-1]()  because of error - aborting connection

    8/22/13 12:16:28.777 AM UserEventAgent[11]: Captive: en1: Not probing 'Apple 1516' (protected network)

    8/22/13 12:16:28.779 AM mDNSResponder[46]:  28: DNSServiceGetAddrInfo      v4v6 14-courier.push.apple.com. PID[-1]()

    8/22/13 12:16:28.780 AM configd[17]: network changed: v4(en1!:10.0.1.16) DNS Proxy SMB

    8/22/13 12:16:28.000 AM kernel[0]: en1: BSSID changed to 00:1e:52:78:01:d5

    8/22/13 12:16:29.460 AM airportd[825]: _doAutoJoin: Already associated to “Apple 1516”. Bailing on auto-join.

    8/22/13 12:16:29.472 AM airportd[825]: _doAutoJoin: Already associated to “Apple 1516”. Bailing on auto-join.

    8/22/13 12:19:06.338 AM coreaudiod[113]: Disabled automatic stack shots because audio IO is active

    8/22/13 12:19:06.872 AM coreaudiod[113]: Enabled automatic stack shots because audio IO is inactive

    8/22/13 12:20:07.530 AM WindowServer[88]: Created shield window 0xa4 for display 0x042735c0

    8/22/13 12:20:07.530 AM WindowServer[88]: device_generate_desktop_screenshot: authw 0x0(0), shield 0x0(0)

    8/22/13 12:20:07.540 AM WindowServer[88]: device_generate_lock_screen_screenshot: authw 0x0(0), shield 0x0(0)

    8/22/13 12:20:24.000 AM kernel[0]: Wake reason: PWRB (User)

    8/22/13 12:20:24.000 AM kernel[0]: Previous Sleep Cause: 5

    8/22/13 12:20:24.000 AM kernel[0]: 9278.160443: setDISASSOC from ATH_INTERFACE_CLASS disconnectVap

    8/22/13 12:20:24.000 AM kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).

    8/22/13 12:20:24.000 AM kernel[0]: en1::IO80211Interface::postMessage bssid changed

    8/22/13 12:20:24.000 AM kernel[0]: 9278.199077: setDISASSOCIATE ****STA SYNC DISASSOC SUCCESS 

    8/22/13 12:20:24.226 AM WindowServer[88]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1

    8/22/13 12:20:24.228 AM WindowServer[88]: Created shield window 0xa5 for display 0x003f003d

    8/22/13 12:20:24.228 AM WindowServer[88]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1

    8/22/13 12:20:25.051 AM configd[17]: network changed: v4(en1-:10.0.1.16) DNS- Proxy- SMB

    8/22/13 12:20:25.000 AM kernel[0]: en1: BSSID changed to 00:1e:52:78:01:d5

    8/22/13 12:20:25.000 AM kernel[0]: en1::IO80211Interface::postMessage bssid changed

    8/22/13 12:20:25.000 AM kernel[0]: AirPort: Link Up on en1

    8/22/13 12:20:25.000 AM kernel[0]: 9279.468678: apple80211Request[10310] Unsupported ioctl 181

    8/22/13 12:20:25.000 AM kernel[0]: en1: BSSID changed to 00:1e:52:78:01:d5

    8/22/13 12:20:25.000 AM kernel[0]: en1::IO80211Interface::postMessage bssid changed

    8/22/13 12:20:25.000 AM kernel[0]: AirPort: RSN handshake complete on en1

    8/22/13 12:20:25.449 AM hidd[54]: MultitouchHID: device bootloaded

    8/22/13 12:20:36.377 AM configd[17]: network changed: v4(en1+:10.0.1.16) DNS+ Proxy+ SMB

    8/22/13 12:20:36.385 AM mDNSResponder[46]:  28: Could not write data to clientPID[-1]()  because of error - aborting connection

    8/22/13 12:20:36.389 AM mDNSResponder[46]:  28: DNSServiceGetAddrInfo      v4v6 45-courier.push.apple.com. PID[-1]()

    8/22/13 12:20:36.389 AM UserEventAgent[11]: Captive: en1: Not probing 'Apple 1516' (protected network)

    8/22/13 12:20:36.000 AM kernel[0]: en1: BSSID changed to 00:1e:52:78:01:d5

    8/22/13 12:20:36.403 AM configd[17]: network changed: v4(en1!:10.0.1.16) DNS Proxy SMB

    8/22/13 12:20:36.646 AM airportd[843]: _doAutoJoin: Already associated to “Apple 1516”. Bailing on auto-join.

    8/22/13 12:20:36.657 AM airportd[843]: _doAutoJoin: Already associated to “Apple 1516”. Bailing on auto-join.

    8/22/13 12:20:36.667 AM airportd[843]: _doAutoJoin: Already associated to “Apple 1516”. Bailing on auto-join.

    8/22/13 12:21:13.984 AM coreaudiod[113]: Disabled automatic stack shots because audio IO is active

    8/22/13 12:21:14.518 AM coreaudiod[113]: Enabled automatic stack shots because audio IO is inactive

    8/22/13 12:21:40.789 AM coreaudiod[113]: Disabled automatic stack shots because audio IO is active

    8/22/13 12:21:41.324 AM coreaudiod[113]: Enabled automatic stack shots because audio IO is inactive

     

     

     

    _______

     

    I'm also not sure if the WiFi issues are back but to a lesser degree.  When I wake from sleep, I have to wait about 20 seconds sometimes for the iMac to reconnect to WiFi.  At least I don't have to turn off WiFi and reconnect it at random times.  I haven't tried to remote access yet since getting this back.

first Previous Page 8 of 16 last Next