EMac blue screen on waking From sleep

When my eMac goes to sleep it wakes up to a locked compressed ble screen and needs a resart to clear. Any Ideas how to fix

Thanks, I have tried suggestion still problem. I have looked in the console But I don't really understand what I am looking for. The computer sleep and wakes up fine if it is just for a couple of minutes but if left any lenght of time wakes up to a blue/black screen. here are the consule results after reboot:
Dec 14 13:31:07 Allies-eMac mDNSResponder[17]: Note: Frequent transitions for interface en0 (192.168.1.64); network traffic reduction measures in effect
Dec 14 13:44:41 localhost kernel[0]: Darwin Kernel Version 9.8.0: Wed Jul 15 16:57:01 PDT 2009; root:xnu-1228.15.4~1/RELEASE_PPC
Dec 14 13:44:34 localhost com.apple.launchctl.System[2]: fsck_hfs: Volume is journaled.  No checking performed.
Dec 14 13:44:34 localhost com.apple.launchctl.System[2]: fsck_hfs: Use the -f option to force checking.
Dec 14 13:44:35 localhost com.apple.launchctl.System[2]: BootCacheControl: could not open /var/db/BootCache.playlist: No such file or directory
Dec 14 13:44:35 localhost com.apple.launchctl.System[2]: BootCacheControl: could not unlink playlist /var/db/BootCache.playlist: Unknown error: -1
Dec 14 13:44:37 localhost com.apple.launchctl.System[2]: launchctl: Please convert the following to launchd: /etc/mach_init.d/dashboardadvisoryd.plist
Dec 14 13:44:37 localhost com.apple.launchd[1] (com.apple.ODSAgent): Unknown key: SHAuthorizationRight
Dec 14 13:44:37 localhost com.apple.launchd[1] (com.apple.RemoteDesktop.PrivilegeProxy): Unknown key for boolean: EnableTransactions
Dec 14 13:44:37 localhost com.apple.launchd[1] (com.apple.usbmuxd): Unknown key for boolean: EnableTransactions
Dec 14 13:44:37 localhost com.apple.launchd[1] (org.cups.cups-lpd): Unknown key: SHAuthorizationRight
Dec 14 13:44:37 localhost com.apple.launchd[1] (org.cups.cupsd): Unknown key: SHAuthorizationRight
Dec 14 13:44:37 localhost com.apple.launchd[1] (org.ntp.ntpd): Unknown key: SHAuthorizationRight
Dec 14 13:44:37 localhost com.apple.launchd[1] (org.x.privileged_startx): Unknown key for boolean: EnableTransactions
Dec 14 13:44:39 localhost DirectoryService[11]: Launched version 5.8.1 (v514.28)
Dec 14 13:44:42 localhost kernel[0]: standard timeslicing quantum is 10000 us
Dec 14 13:44:40 localhost DirectoryService[11]: Improper shutdown detected
Dec 14 13:44:42 localhost kernel[0]: vm_page_bootstrap: 254066 free pages and 8078 wired pages
Dec 14 13:44:41 localhost kextd[10]: 426 cached, 0 uncached personalities to catalog
Dec 14 13:44:42 localhost kernel[0]: mig_table_max_displ = 79
Dec 14 13:44:42 localhost kernel[0]: 77 prelinked modules
Dec 14 13:44:42 localhost kernel[0]: Loading security extension com.apple.security.TMSafetyNet
Dec 14 13:44:43 localhost kernel[0]: calling mpo_policy_init for TMSafetyNet
Dec 14 13:44:43 localhost kernel[0]: Security policy loaded: Safety net for Time Machine (TMSafetyNet)
Dec 14 13:44:43 localhost kernel[0]: Loading security extension com.apple.nke.applicationfirewall
Dec 14 13:44:43 localhost kernel[0]: Loading security extension com.apple.security.seatbelt
Dec 14 13:44:43 localhost kernel[0]: calling mpo_policy_init for mb
Dec 14 13:44:43 localhost kernel[0]: Seatbelt MACF policy initialized
Dec 14 13:44:43 localhost kernel[0]: Security policy loaded: Seatbelt Policy (mb)
Dec 14 13:44:43 localhost kernel[0]: Copyright (c) 1982, 1986, 1989, 1991, 1993
Dec 14 13:44:43 localhost kernel[0]: The Regents of the University of California. All rights reserved.
Dec 14 13:44:43 localhost kernel[0]: MAC Framework successfully initialized
Dec 14 13:44:43 localhost kernel[0]: using 5242 buffer headers and 4096 cluster IO buffer headers
Dec 14 13:44:43 localhost kernel[0]: FireWire (OHCI) Lucent ID 5811 built-in now active, GUID 000a95fffe852a54; max speed s400.
Dec 14 13:44:43 localhost kernel[0]: mbinit: done
Dec 14 13:44:43 localhost kernel[0]: Security auditing service present
Dec 14 13:44:43 localhost kernel[0]: BSM auditing present
Dec 14 13:44:43 localhost kernel[0]: rooting via boot-uuid from /chosen: 18ED512C-1C63-3D84-ADFE-61708D80F903
Dec 14 13:44:43 localhost kernel[0]: Waiting on <dict ID="0"><key>IOProviderClass</key><string ID="1">IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict>
Dec 14 13:44:43 localhost kernel[0]: Got boot device = IOService:/MacRISC2PE/pci@f2000000/AppleMacRiscPCI/mac-io@17/AppleKeyLargo/ata- 4@1f000/KeyLargoATA/ATADeviceNub@0/AppleATADiskDriver/IOATABlockStorageDevice/IO BlockStorageDriver/IBM-IC35L060AVV207-0 IBM-IC35L060AVV207-0/IOApplePartitionScheme/Apple_HFS_Untitled_2@10
Dec 14 13:44:43 localhost kernel[0]: BSD root: disk0s10, major 14, minor 2
Dec 14 13:44:43 localhost kernel[0]: jnl: unknown-dev: replay_journal: from: 3786240 to: 5192704 (joffset 0x648000)
Dec 14 13:44:43 localhost kernel[0]: jnl: unknown-dev: journal replay done.
Dec 14 13:44:43 localhost kernel[0]: Jettisoning kernel linker.
Dec 14 13:44:43 localhost kernel[0]: Resetting IOCatalogue.
Dec 14 13:44:43 localhost kernel[0]: Matching service count = 0
Dec 14 13:44:43 localhost kernel[0]: Matching service count = 1
Dec 14 13:44:43: --- last message repeated 4 times ---
Dec 14 13:44:43 localhost kernel[0]: Matching service count = 4
Dec 14 13:44:43 localhost kernel[0]: PowerMac4,4: stalling for module
Dec 14 13:44:43 localhost kernel[0]: Matching service count = 1
Dec 14 13:44:46 localhost kernel[0]: UniNEnet: Ethernet address 00:0a:95:85:2a:54
Dec 14 13:44:52 localhost mDNSResponder mDNSResponder-176.3 (Jun 17 2009 18:57:52)[17]: starting
Dec 14 13:44:52 localhost kextd[10]: writing kernel link data to /var/run/mach.sym
Dec 14 13:44:55 localhost kernel[0]: UniNEnet::monitorLinkStatus - Link is up at 100 Mbps - Full Duplex (PHY regs 5,6:0x41e1,0x0007)
Dec 14 13:44:55 localhost configd[14]: AppleTalk startup
Dec 14 13:44:55 Allies-eMac configd[14]: setting hostname to "Allies-eMac.local"
Dec 14 13:44:57 Allies-eMac bootlog[50]: BOOT_TIME: 1355492671 0
Dec 14 13:44:58 Allies-eMac rpc.statd[33]: statd.notify - no notifications needed
Dec 14 13:44:58 Allies-eMac fseventsd[43]: event logs in /.fseventsd out of sync with volume.  destroying old logs. (383 27 1214)
Dec 14 13:45:00 Allies-eMac fseventsd[43]: log dir: /.fseventsd getting new uuid: F232774E-DCFC-48F5-93C6-8992824B9F39
Dec 14 13:45:01 Allies-eMac com.apple.usbmuxd[30]: usbmuxd-268.5 on Apr  5 2012 at 15:33:47, running 32 bit
Dec 14 13:45:03 Allies-eMac /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow[38]: Login Window Application Started -- Threaded auth
Dec 14 13:45:03 Allies-eMac kernel[0]: ALF ALERT: sockwall_cntl_updaterules ctl_enqueuedata rts err 55
Dec 14 13:45:06: --- last message repeated 10 times ---
Dec 14 13:45:06 Allies-eMac configd[14]: AppleTalk startup complete
Dec 14 13:45:08 Allies-eMac kernel[0]: ALF ALERT: sockwall_cntl_updaterules ctl_enqueuedata rts err 55
Dec 14 13:45:08 Allies-eMac /usr/sbin/ocspd[62]: starting
Dec 14 13:45:09 Allies-eMac kernel[0]: ALF ALERT: sockwall_cntl_updaterules ctl_enqueuedata rts err 55
Dec 14 13:45:29 Allies-eMac configd[14]: setting hostname to "Allies-eMac.home"
Dec 14 13:45:40 Allies-eMac loginwindow[38]: Login Window Started Security Agent
Dec 14 13:45:43 Allies-eMac authorizationhost[82]: MechanismInvoke 0x11e430 retainCount 2
Dec 14 13:45:43 Allies-eMac SecurityAgent[83]: MechanismInvoke 0x101620 retainCount 1
Dec 14 13:45:44 Allies-eMac loginwindow[38]: Login Window - Returned from Security Agent
Dec 14 13:45:44 Allies-eMac authorizationhost[82]: MechanismDestroy 0x11e430 retainCount 2
Dec 14 13:45:44 Allies-eMac SecurityAgent[83]: MechanismDestroy 0x101620 retainCount 1
Dec 14 13:45:44 Allies-eMac loginwindow[38]: USER_PROCESS: 38 console
Dec 14 13:45:45 Allies-eMac com.apple.launchd[1] (com.apple.UserEventAgent-LoginWindow[76]): Exited: Terminated
Dec 14 13:45:45 Allies-eMac com.apple.launchd[1] (com.apple.ScreenSharing.server[75]): Exited: Terminated
Dec 14 13:45:45 Allies-eMac com.apple.launchd[84] (com.apple.AirPortBaseStationAgent): Unknown key for boolean: EnableTransactions
Dec 14 13:45:45 Allies-eMac com.apple.launchd[84] (org.x.startx): Unknown key for boolean: EnableTransactions
Dec 14 13:45:47 Allies-eMac kernel[0]: CODE SIGNING: cs_invalid_page(0x1000): p=89[GoogleSoftwareUp] clearing CS_VALID
Dec 14 13:45:59 Allies-eMac /System/Library/CoreServices/coreservicesd[58]: SFLSharePointsEntry::CreateDSRecord: dsCreateRecordAndOpen(andy's Public Folder) returned -14135
Dec 14 13:46:00 Allies-eMac /System/Library/CoreServices/coreservicesd[58]: SFLSharePointsEntry::CreateDSRecord: dsCreateRecordAndOpen(Josie's Public Folder) returned -14135
Dec 14 13:46:00 Allies-eMac /System/Library/CoreServices/coreservicesd[58]: SFLSharePointsEntry::CreateDSRecord: dsCreateRecordAndOpen(HANDBAG) returned -14135
Dec 14 13:46:00 Allies-eMac /System/Library/CoreServices/coreservicesd[58]: SFLSharePointsEntry::CreateDSRecord: dsCreateRecordAndOpen(Ali's Public Folder) returned -14135
Dec 14 13:46:13 Allies-eMac Finder[103]: [QL ERROR] Generator database update takes too long... we will use what we currently have

Similar Messages

  • IMac has empty blue screen on waking from sleep

    My iMac goes to a blue empty screen when waking from sleep. No login. No desktop shows up. Any ideas or explanations? I am working on clearing off hard drive space - currently about 100GB available on 1TB system. But I do not know if that could be a cause.
    Thanks for any help you can give.

    tritzer wrote:
    As far as resetting the SMT, my only option was to hold the power button down and force the system off anyway, since I couldn't see anything.
    I did reset the PRAM, which ended up being disastrous! Instead of encountering the problem each time the system went to sleep like what had been happening, after I reset the PRAM, it started doing it immediately during startup. I couldn't even get to the desktop. The computer was completely unusable!
    If I hadn't had a spare monitor around, I wouldn't have been able to do anything with my computer! Interestingly, the problem doesn't occur with my old Apple Studio Display, just my new Apple Cinema Display.
    You better revert to 10.5.4 and stay with it until this is resolved.

  • T60 Type 2623 Blue Screen on Resume from Sleep Mode problem solved - XP Pro

    I hope that this post ends some frustrations for some people.
    I hope that IBM deals with this issue by getting ATI to fix the video driver issue.
    After three months of tracking down blue screens when resuming from Sleep Mode and some lockups while working, I have identified the problem on my T60 Type 2623 running Windows XP-Pro and all service packs and updates.  The Sleep Mode resume issues were intermittant and it would be fine for a day or two and then reboot on Resume or reboot every time I used Resume for a while.  For months the Blue Screen would reboot and attempt to send the message to Microsoft using the logs, but the logs were always corrupted.  I disabled every driver that I could and the problem continued for months.
    The problem solution came about when I decided to try my Rhapsody Music account after many months of not using it.  I kept getting a message about DRM (Digital Right Management) being disabled and Rhapsody software could not self-fix this.  So I finally called Rhapsody and they spent over an hour with me trying to get Rhapsody to work.  The support person asked me about my computer and I noted that it was an IBM T60.  He then asked about my Video Card and I responded that it was an ATI Mobility Radeon X1300.  After a few minutes on hold he asked about my driver version which was 8.442.3-080103a1-057754C the set from January 31, 2008.  He noted that there is a known problem wit the 8.4 driver and it interferes with DRM.  He had me go to control panel Settings and Hardware and then roll-back the driver to the prior version.
    After a reboot, the DRM issue was solved and I soon discovered that my resume from Sleep mode no longer crashed.  In fact it has been fine and crash free for over a month now.  I have noted that the older driver can sometimes resize my screen to something like 600 X 800 if I close the lid under certain circumstances, but that is just a function key reset to get my normal desktop resolution back.  At least it is not a blue screen reboot with a corrupted log file.
    Message Edited by retro74 on 07-05-2008 08:50 AM
    Solved!
    Go to Solution.

    Unfortunately I could not fix the problem so I wiped my system and loaded all new drivers before I found this posting.
    Is there a way to get the old ATI driver that works? The only one available on the ATI and Lenovo website is the latest one with the problem. I agree with you David, Lenovo should have fixed this problem already with ATI.
    John

  • A Few seconds of blue screen on wake from sleep

    I have kind of a weird glitch. When waking from sleep my iMac always goes to blue screen first for a few seconds before totally waking up to desktop. This is on a machine without any problems at all. I do not have this behavior on an iMac G5 with the ambient light.
    I also have Leopard running on an external hard drive with no problems. It will wake directly to desktop without any blue screen before hand. As I say on the Intel iMac it goes to blue screen for like 2 seconds first.
    Anyone else experienced this?
    Cheers
    mrjazz

    I think this has been mentioned before.
    Yours does it. Mine does it. Maybe they all do it. No glitch.
    Not too abnormal for the Mac to wake up the video first and then wait for the HD to spin up in order to present a coherent desktop.
    M

  • "Washed out" screen after waking from sleep?

    Over the past couple of months, when either waking from sleep or coming off the screen saver, the display has a washed out look to it. The colors can be restored by either reinitializing the screen saver or putting the computer to sleep and waking it back up again. I tried the PRAM and PMU resets with no success. The problem seems to be getting worse. (more frequent) Any ideas, suggestions would be appreciated.

    hey, just adding my story to yours cause it seems to be a similar issue.
    Every now and the when My MBP wakes from sleep or screensaver, the screen seems to lose its calibration, it gets all blueish. When I go to Display preferences to see what's there, the computer sort of recovers from the flaw and loads proper colors. I can almost her it say Oh yeah, color calibration!..

  • Black screen after waking from sleep mode - Compaq Presario CQ5110F

    My mother's computer has been having the problem listed in the subject -- after waking from sleep mode, the monitor just stays black, and won't come back. After trying everything I could find online, I eventually found the bios update which claims to fix the exact issue. The problem is that I guess my mother had opted to upgrade to Windows 7, while the bios update seems to only work for Windows Vista, as I get the following error message: "Your system does not meet the minimum requirements for this update. Update has been canceleld. (9998)." I've tried running the update in Vista compatibility mode, with no luck. I've tried using a different monitor, I've updated all the drivers, Windows Updates are all current, I've cleared CMOS. Any idea on how to fix this? It's very recent; only for about the past 2 weeks has this been happening, while we've had the computer for over 3 years. It's quite a waste of energy to keep it on all day.

    Hello liltwix,
    When taking your computer out of safe mode the screen just remains black, is that correct? I will try to help you with this issue.
    I understand you upgraded from Vista to 7, was that when the issue started or has the computer had windows 7 installed for some time before this problem started?
    Please respond back at your earliest convenience.
    Thanks
    Clicking the White Kudos star on the left is a way to say Thanks!
    Clicking the 'Accept as Solution' button is a way to let others know which steps helped solve the problem!

  • White screen after waking from sleep when external display is attache

    Waking from sleep mode to lock screen when a secondary monitor is connected with an HDMI cable presents a blank white screen with user icon but no other elements, including the box where one enters their password.  The remaining UI elements appear only after disconnecting the HDMI cable.
    Configuration:
    MacBook Pro (Retina, 15-inch, Mid 2014) with nVidia GPU

    Send Apple feedback. They won't answer, but at least will know there is a problem. If enough people send feedback, it may get the problem solved sooner.
    Feedback
    Mail/Provide Mail Feedback
    Or you can use your Apple ID to register with this site and go the Apple BugReporter. Supposedly you will get an answer if you submit feedback.
    Feedback via Apple Developer

  • Black screen upon waking from sleep

    Hello,
    I have an intermittent problem with waking my entry-level MBP from sleep; on some occasions, the screen remains black instead of the system waking up and displaying the Finder.
    Recently, upon waking from sleep, the authentication dialog displayed, I typed my password and pressed return, the dialog dismissed, the screen remained black, and the wait cursor displayed without spinning.
    To recover, I needed to force power down and cold reboot.
    system.log (in Console) contained the following entry at the time of the crash.
    Aug 14 07:39:51 BF-H-MBP kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0xd = GR: SW Notify ErrorAug 14 07:39:51 BF-H-MBP kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0xd = GR: SW Notify Error
    The entries surrounding the one above were as follows (the next to last one evidently was the final entry before the forced power down).
    Aug 14 07:39:47 BF-H-MBP kernel[0]: IOBluetoothHCIController::restartShutdownWL this is a wake from sleep
    Aug 14 07:39:47 BF-H-MBP kernel[0]: System Wake
    Aug 14 07:39:47 BF-H-MBP kernel[0]: IOUSBWorkLoop::closeGate - interrupt Thread being held off
    Aug 14 07:39:51 BF-H-MBP kernel[0]: NVChannel(GL): Graphics channel exception! status = 0xffff info32 = 0xd = GR: SW Notify Error
    Aug 14 07:39:51 BF-H-MBP BatteryUpdater[3590]: Battery does not need the BatteryUpdate v 1.2 (0x2)
    Aug 14 07:39:51 BF-H-MBP lookupd[3588]: lookupd (version 369.6) starting - Tue Aug 14 07:39:51 2007
    Aug 14 07:50:08 localhost kernel[0]: hi mem tramps at 0xffe00000
    Can someone diagnose the problem based upon the above Console entries?
    Thanks in advance!

    Hi,
    Thanks for taking time to post.
    My question is different than the one your posting answers.
    My question is, what is the diagnosis of the problem based upon the Console log entries that I've posted (rather than "How do I recover from the black screen?")?
    Cheers!

  • White stairs on screen after waking from sleep (lid closed)

    recently my Mid 2012 MBP has started to show large jagged white stairs on screen after awaking from sleep. Anybody have any ideas? I will try to attach a picture when it happens again. (new phone)
    last one had what looked like blown pixels. goes away after reboot

    Mid 2012 you are still under warrenty. I would not hesitate to call their help desk or take it in for elvaluation.
    Genius reservation http://www.apple.com/retail/geniusbar/
    check warranty https://selfsolve.apple.com/agreementWarrantyDynamic.do

  • 13.3" macbook pro flickering screen when waking from sleep

    I have a Mid 2012 13.3" MacBook Pro (non-Retina) laptop that has been working well, until the last few days.  The laptop has had no physical damage and no liquid damage.  I have put the laptop to sleep by closing the lid.  When the laptop lid is raised and the laptop turns on this last week I have noticed that the screen flickers and then appears to be on, but the screen is a grey color.  I have been able to press the power button to put the computer back to sleep.  Usually when pressing the power button to wake it from sleep the screen issues have cleared up. 
    Is there a known issue that may cause the issue with the flickering/grey screen or could there be a short in the wiring that powers the screen?

    Hey there Oregan Mac User,
    It sounds like you are getting screen flickers when trying to wake your device from sleep. I recommend the troubleshooting form the article named:
    Apple computers: Troubleshooting issues with video on internal or external displays
    http://support.apple.com/kb/ht1573
    Reset the system
    You can reset the Mac's parameter RAM and SMC.
    Reset the resolution
    Start by resetting the Mac's parameter RAM. If the display does not come up, was previously set to an unsupported resolution, and still results in no video:
    Start up in Safe Mode.
    From the Apple () menu, choose System Preferences.
    Choose Displays from the View menu to open the preferences pane.
    Select any resolution and refresh rate that your display supports.
    Restart your computer.
    Thank you for using Apple Support Communities.
    All the best,
    Sterling

  • MBP 17" garbled screen after waking from sleep

    Occasionally, when the computer wakes from sleep, the screen is garbled like on the picture at http://www.geocities.com/chv74/IMG_6416.JPG. It makes no difference wheather the computer was put into sleep by closing the lid or any other method. I can type in my password and continue, but the screen is still garbled, the desktop is shown, but also garbled. The only method to correct the situation is to close the lid, let is sleep again and then wake the computer again. Ot, restart the whole thing by turning it off (5 seconds power-button). Sometimes it will not occur for a few weeks. It occurred throughout the updates 10.4.6 up to and including 10.4.10.
    I just want to know if others have experienced the same or not.

    So, I took my MBP to my Apple store where I bought it and showed the picture. They said it is not supposed to happen and I should reset the NVRAM, but that didn't help. So, now they replaced the motherboard and the problem is fixed, but my bluetooth doesn't work anymore, so my laptop is still in the shop. So, I can't say that it is completely over.
    Another thing. I took it back first to have my screen fixed. It looked like there was dust behind the screen! I've seen someone post something about that also. At first it was just at one place, but in one week it turned up throughout the entire screen. So, I had the screen replaced. Now, there is one dead pixel right in the middle. Very irritating. What's up with these screens? Can they not give you a pixel-perfect screen in such an expensive notebook?! My last screen had three dead pixels (not at annoying places though)!
    So, perhaps, y'all should take a picture too and show it to a tech guy at your Apple store.
    Later, Parsec

  • Strange shadow on bottom of screen after waking from sleep

    I just go the Macbook Pro 15" Penryn and when the screen wakes from sleep it has about 6-7 dark black shadowy marks on the bottom. They look like 1/2" thick parallel lines that go up about 1" from the bottom. I don't know exactly how to explain it but I thought that they would disappear after the screen warms up but they only go away when I turn the display completely dark and then bright again or if restart the computer. Any thoughts? Does anyone else have this problem?

    You've most likely got a bad inverter board. It sits at the very bottom of the LCD display and controls the backlighting. I would take your notebook to the Apple store, demonstrate the problem, and request an exchange.
    A good way to test this is to make the problem appear, then take a full screenshot using Grab (the application) and post it online. Then go look at it with a different computer. If the problem doesn't show up in the screenshot, it's definitely a hardware failure.

  • Blank screen after waking from sleep (OSX 10.6)

    Same as question here:
    https://discussions.apple.com/thread/2672662?threadID=2672662
    ... which is archived, so can't add this to that thread.
    This occurs on a 13" MacBook Pro, and the problem has been largely persistent during the 16 months I've been using this Mac. I generally perform updates as soon as they're available (to within a few days), so whatever the current release is - that's where this problem is happening.
    What happens:
    If the machine is put to sleep by unplugging the display adapter and power plug, then when it's wakened again with an external monitor as the main display, the screen is empty -- not black, but blank. This also sometimes, but not always, happens when just waking the machine by opening the lid.
    What's really happening:
    The login field is being displayed in an area that's not on the current screen.
    How I know that / one workaround:
    If I wait until the machine is clearly awake (i.e., the screen is still blank but plainly displaying black instead of just being dead -- alternately, when I can see the mouse pointer), and then just type the password and hit the ENTER key, the machine will typically start.

    A little update:
    I reset the SMC but that made no difference. I restarted in Safe Mode and the problem seemed to vanish. So I restarted in normal mode again. I was hoping that the clearing of caches, etc that is done in Safe Mode might have solved the problem. Sadly it didn't.
    However, I have now quit several items that run on startup and I think the problem may have gone. I will reintroduce them one by one in a bid to discover the culprit. Currently under suspicion is Dropbox, Audiogalaxy, LastFM and Xmarks. Possibly it's none of the above. I'll keep you posted.
    Dave

  • Distorted Log In screen after waking from sleep

    Every time i wake my MacBook Pro (15" Early 2011), it's a black screen with the spinning rainbow for about 20-30 seconds and then i get a distorted screen at the log in. I am able to enter my password, and i can see it being typed, but i am worried about why the screen is distorted. Do note that i have had my logic board changed about 4-5 times this year. Anyone else facing this issue? I'm adding a photo to show you what it looks like.

    Well, hae you tried "quirks"?
    Maybe manpage of pm-suspend could help. There are severel "quirks" that solve these graphics-based problem when resuming from suspend.

  • Black screen after waking from sleep, but mouse pointer visible

    I'm not sure if this is the same as the many other posts on problems connecting the Mac Mini to an external monitor. In my case, after it wakes, there is no login menu - but the mouse pointer is visible and I can move it around the screen no problem.
    At present, I have to power the Mac Mini down and back up again, which is unacceptable.
    What's causing this and how can I fix it?

    Yes, I have this problem too. I reported to Apple about 3 or 4 weeks ago. They said no one else ever reported it and said they would escalate it but they have never got back too me. It is a pain because my mini is a media center pc and hard to get to when this happens.
    For now the work around I use is to unplug the mini dvi connecter and plug it back in; this fixes the issue until the next time it happens.
    +My mini (2009 version) is connected using the mini-dvi connector to a Denon receiver (with a DVI->hdmi connector) which is then connected to a sony 1080p TV. This replaced an older mini (intel duo) which did not have this problem using the same setup.+
    Message was edited by: rsonnens

Maybe you are looking for