I bring my MBP  out of sleep I get:  X300 SE 128MB BIOS P/N 113-A33 406-100

My MBP had to be reset to come out of sleep mode, and when it did, there was the blue screen of death.
It was reset again and seemed to be working fine.
Then, when I brought the MBP while boot camp Vista out of sleep mode this afternoon, there was nothing on the screen but a string of characters (X300 SE 128MB BIOS P/N 113-A33 406-100).
I've tried to restart the machine several times and keep getting this same screen. Any thoughts as to what might be going on?

Boot from your DVD for Vista; do a Safe Boot; run sfc /scannow and force it to do a disk check for errors on next startup.

Similar Messages

  • CD Eject sound when MBP comes out of sleep

    Perhaps this is typical - I'm a new convert from the PC world. But the only thing that I don't like about my new MBP is that the CD drive (when empty) makes the CD eject noise every time the machine comes out of sleep. Is this typical? What's it trying to accomplish? Is there any way to disable this behavior?
    Any insight would be welcomed.
    thanks,
    Pete

    Yes it's normal. It is the behaviour of the Matshita (Panasonic) drives as they are powered, which is what happens when you boot and wake from sleep. Unfortunately there's nothing you can do about it.

  • HP LaserJet P3005x will not come out of sleep mode

    Printer will not come out of sleep mode (after being in sleep mode for an extended period of time (over 24 hrs)).  When this happens, I can not ping the printer and pressing any of the buttons on the printer will not bring it out of sleep mode.  I'm testing now to see if I can recreate this with the printer attached to my PC via USB.

    Hi arosecarter,
    I understand your monitor is not coming out of sleep mode. Take a look at the following support document, Resolving Problems with Sleep and Hibernate Modes (Windows 7). Step 3 might be of particular interest to you, as you mentioned your keyboard and mouse are not really working for you either. Perhaps it is another connected device that is causing the issue? Anyway, hopefully this document will be of help to you. Best of luck. Have a wonderful day.
    Ryan1216
    I work on behalf of HP
    The advice and opinions given here are my own and not those of HP

  • Wireless Network Does Not Work After Coming Out of Sleep

    I have a WEP connection that does not broadcast. My Airport connects to it fine. When the MacBook comes out of sleep mode, sometimes it cannot connect and does not show the network in the list of available networks (because it doesn't broadcast, but the network is setup so it should show). If I turn off Airport and then immediately turn it back on, it connects right away.
    Has anyone else had this problem? Does anyone know of a fix?

    Thanks for the reply. I don't think I need to delete and recreate the connection because just bouncing the Airport on the MacBook brings the connection back online... so I don't think there is anything wrong with the connection per se. It doesn't happen every time I come backup from sleep, just often enough that it's something I'd like to see them fix in an update if it's a problem that other people are having too.
    As for switching from WEP, I have a many wireless clients in my house including laptops, desktops, printers, console systems, and iPhones/Smart-Phones. They all support WEP, but they don't all support WPA. I'd rather try to keep from buying new network cards or new printers.

  • How to stop ManagedClient from crashing my MBP when in sleep mode?

    Since upgrading my Early 2011 MBP to Mavericks (now 10.9.1) it has a tendency to crash while in sleep mode.
    By "crash" I mean very loud fan activity - disturbing especially during night time. 
    Sometimes the crash is so serious that when I click the trackpad to re-activate the screen, all I get is a grey screen with a mouse pointer. All I can do is a hard restart using the power buttion.
    At other times it lets me log-in again, and Activity Monitors shows multiple instances of a process called ManagedClient, around five of them, each of them using high amounts of CPU. Killing the ManagedClient processes brings the MBP back to normal operation.
    I guess that "ManagedClient" has a function in company networks or in conjunction with a Mac server. In my network is neither a server nor other MBPs, so I don't understand what the use of ManagedClient would be for me.
    I already used Disc Utility to repair permissions, repair disc, and repair partition map - no change.
    Furthermore I did a complete re-install of Mavericks over the internet using the Recovery Mode, problem persists.
    When I search Console for "ManagedClient" after a soft crash (a crash where I can still log-in an kill the ManagedClient instances), I get a lot of entries like this:
    19.12.13 23:14:40,339 ManagedClient[788]: CGSGetNextEventRecord (Inline) connection 0x9503, 32768 bytes
    19.12.13 23:14:40,339 ManagedClient[788]: shutdown_server_connections: Detaching application from window server
    19.12.13 23:14:50,419 ManagedClient[788]: CGSLookupServerRootPort: Failed to look up the port for "com.apple.windowserver" (268435459)
    19.12.13 23:14:50,739 ManagedClient[798]: CGSGetNextEventRecord (Inline) connection 0x9503, 32768 bytes
    19.12.13 23:14:50,739 ManagedClient[798]: shutdown_server_connections: Detaching application from window server
    19.12.13 23:15:00,817 ManagedClient[798]: CGSLookupServerRootPort: Failed to look up the port for "com.apple.windowserver" (268435459)
    19.12.13 23:15:01,143 ManagedClient[808]: CGError CGSGetDisplaySystemState(uint64_t, CGSDisplaySystemState **): MIG error 0x10000003: (ipc/send) invalid destination port
    19.12.13 23:15:01,143 ManagedClient[808]: CGError CGSGetDisplaySystemState(uint64_t, CGSDisplaySystemState **): MIG error 0x10000003: (ipc/send) invalid destination port
    19.12.13 23:15:01,143 ManagedClient[808]: CGSGetNextEventRecord (Inline) connection 0x9603, 32768 bytes
    19.12.13 23:15:01,143 ManagedClient[808]: CGError CGSGetDisplaySystemState(uint64_t, CGSDisplaySystemState **): MIG error 0x10000003: (ipc/send) invalid destination port
    19.12.13 23:15:01,143 ManagedClient[808]: shutdown_server_connections: Detaching application from window server
    19.12.13 23:15:11,572 ManagedClient[818]: CGSGetNextEventRecord (Inline) connection 0x9503, 32768 bytes
    19.12.13 23:15:11,572 ManagedClient[818]: shutdown_server_connections: Detaching application from window server
    19.12.13 23:15:21,654 ManagedClient[818]: CGSLookupServerRootPort: Failed to look up the port for "com.apple.windowserver" (268435459)
    19.12.13 23:15:32,086 ManagedClient[828]: CGError CGSGetDisplaySystemState(uint64_t, CGSDisplaySystemState **): MIG error 0x10000003: (ipc/send) invalid destination port
    19.12.13 23:15:32,086 ManagedClient[828]: CGError CGSGetDisplaySystemState(uint64_t, CGSDisplaySystemState **): MIG error 0x10000003: (ipc/send) invalid destination port

    My macbook air is having the same problem and killing my battery in under an hour.  Console shows the following:
    May  7 18:26:30 myMacAir.local ManagedClient[649]: CGError CGSGetDisplaySystemState(uint64_t, CGSDisplaySystemState **): MIG error 0xfffffecc: (ipc/mig) server died
    May  7 18:26:30 myMacAir.local ManagedClient[649]: CGError CGSGetDisplaySystemState(uint64_t, CGSDisplaySystemState **): MIG error 0x10000003: (ipc/send) invalid destination port
    May  7 18:26:30 myMacAir.local ManagedClient[649]: CGSGetOnScreenWindowCount
    May  7 18:26:30 myMacAir.local ManagedClient[649]: CGSGetNextEventRecord (Inline) connection 0x8a03, 32768 bytes
    May  7 18:26:30 myMacAir.local ManagedClient[649]: shutdown_server_connections: Detaching application from window server
    May  7 18:26:30 myMacAir.local ManagedClient[649]: *** -[NSMachPort handlePortMessage:]: dropping incoming DO message because the connection is invalid
    May  7 18:26:30 myMacAir.local ManagedClient[649]: HIToolbox: received notification of WindowServer event port death.
    May  7 18:26:30 myMacAir.local ManagedClient[649]: port matched the WindowServer port created in BindCGSToRunLoop
    May  7 18:26:40 myMacAir.local ManagedClient[649]: CGSLookupServerRootPort: Failed to look up the port for "com.apple.windowserver" (268435459)
    May  7 18:26:40 myMacAir.local ManagedClient[659]: MCX.createConnection bootstrap_register failed = 1100
    May  7 18:26:40 myMacAir.local ManagedClient[659]: CGError CGSGetDisplaySystemState(uint64_t, CGSDisplaySystemState **): MIG error 0xfffffecc: (ipc/mig) server died
    May  7 18:26:40 myMacAir.local ManagedClient[659]: CGError CGSGetDisplaySystemState(uint64_t, CGSDisplaySystemState **): MIG error 0x10000003: (ipc/send) invalid destination port
    May  7 18:26:40 myMacAir.local ManagedClient[659]: CGSGetOnScreenWindowCount
    May  7 18:26:40 myMacAir.local ManagedClient[659]: CGSGetNextEventRecord (Inline) connection 0x8b03, 32768 bytes
    May  7 18:26:40 myMacAir.local ManagedClient[659]: shutdown_server_connections: Detaching application from window server
    May  7 18:26:40 myMacAir.local ManagedClient[659]: *** -[NSMachPort handlePortMessage:]: dropping incoming DO message because the connection is invalid
    May  7 18:26:40 myMacAir.local ManagedClient[659]: HIToolbox: received notification of WindowServer event port death.
    May  7 18:26:40 myMacAir.local ManagedClient[659]: port matched the WindowServer port created in BindCGSToRunLoop
    May  7 18:26:50 myMacAir.local ManagedClient[659]: CGSLookupServerRootPort: Failed to look up the port for "com.apple.windowserver" (268435459)
    May  7 18:26:50 myMacAir.local ManagedClient[669]: MCX.createConnection bootstrap_register failed = 1100
    May  7 18:26:50 myMacAir.local ManagedClient[669]: *** -[NSMachPort handlePortMessage:]: dropping incoming DO message because the connection is invalid
    May  7 18:26:50 myMacAir.local ManagedClient[669]: HIToolbox: received notification of WindowServer event port death.
    May  7 18:26:50 myMacAir.local ManagedClient[669]: CGSGetNextEventRecord (Inline) connection 0x8b03, 32768 bytes
    May  7 18:26:50 myMacAir.local ManagedClient[669]: shutdown_server_connections: Detaching application from window server
    May  7 18:26:50 myMacAir.local ManagedClient[669]: port matched the WindowServer port created in BindCGSToRunLoop
    May  7 18:27:00 myMacAir.local ManagedClient[669]: CGSLookupServerRootPort: Failed to look up the port for "com.apple.windowserver" (268435459)
    May  7 18:27:00 myMacAir.local ManagedClient[679]: MCX.createConnection bootstrap_register failed = 1100
    May  7 18:27:00 myMacAir.local ManagedClient[679]: CGError CGSGetDisplaySystemState(uint64_t, CGSDisplaySystemState **): MIG error 0xfffffecc: (ipc/mig) server died
    May  7 18:27:00 myMacAir.local ManagedClient[679]: CGError CGSGetDisplaySystemState(uint64_t, CGSDisplaySystemState **): MIG error 0x10000003: (ipc/send) invalid destination port
    May  7 18:27:00 myMacAir.local ManagedClient[679]: CGSGetOnScreenWindowCount
    May  7 18:27:00 myMacAir.local ManagedClient[679]: CGSGetNextEventRecord (Inline) connection 0x8a03, 32768 bytes
    May  7 18:27:00 myMacAir.local ManagedClient[679]: shutdown_server_connections: Detaching application from window server
    May  7 18:27:00 myMacAir.local ManagedClient[679]: *** -[NSMachPort handlePortMessage:]: dropping incoming DO message because the connection is invalid
    May  7 18:27:00 myMacAir.local ManagedClient[679]: HIToolbox: received notification of WindowServer event port death.
    May  7 18:27:00 myMacAir.local ManagedClient[679]: port matched the WindowServer port created in BindCGSToRunLoop
    May  7 18:27:10 myMacAir.local ManagedClient[679]: CGSLookupServerRootPort: Failed to look up the port for "com.apple.windowserver" (268435459)
    May  7 18:27:10 myMacAir.local ManagedClient[689]: MCX.createConnection bootstrap_register failed = 1100
    May  7 18:27:11 myMacAir.local ManagedClient[689]: CGError CGSGetDisplaySystemState(uint64_t, CGSDisplaySystemState **): MIG error 0xfffffecc: (ipc/mig) server died
    May  7 18:27:11 myMacAir.local ManagedClient[689]: CGError CGSGetDisplaySystemState(uint64_t, CGSDisplaySystemState **): MIG error 0x10000003: (ipc/send) invalid destination port
    May  7 18:27:11 myMacAir.local ManagedClient[689]: CGSGetOnScreenWindowCount
    May  7 18:27:11 myMacAir.local ManagedClient[689]: CGSGetNextEventRecord (Inline) connection 0x8b03, 32768 bytes
    May  7 18:27:11 myMacAir.local ManagedClient[689]: shutdown_server_connections: Detaching application from window server
    May  7 18:27:11 myMacAir.local ManagedClient[689]: *** -[NSMachPort handlePortMessage:]: dropping incoming DO message because the connection is invalid
    May  7 18:27:11 myMacAir.local ManagedClient[689]: HIToolbox: received notification of WindowServer event port death.
    May  7 18:27:11 myMacAir.local ManagedClient[689]: port matched the WindowServer port created in BindCGSToRunLoop
    May  7 18:27:21 myMacAir.local ManagedClient[689]: CGSLookupServerRootPort: Failed to look up the port for "com.apple.windowserver" (268435459)
    May  7 18:27:21 myMacAir.local ManagedClient[699]: MCX.createConnection bootstrap_register failed = 1100
    May  7 18:27:21 myMacAir.local ManagedClient[699]: CGError CGSGetDisplaySystemState(uint64_t, CGSDisplaySystemState **): MIG error 0x10000003: (ipc/send) invalid destination port
    May  7 18:27:21 myMacAir.local ManagedClient[699]: CGError CGSGetDisplaySystemState(uint64_t, CGSDisplaySystemState **): MIG error 0x10000003: (ipc/send) invalid destination port
    May  7 18:27:21 myMacAir.local ManagedClient[699]: CGSGetOnScreenWindowCount
    May  7 18:27:21 myMacAir.local ManagedClient[699]: CGSGetNextEventRecord (Inline) connection 0x8a03, 32768 bytes
    May  7 18:27:21 myMacAir.local ManagedClient[699]: shutdown_server_connections: Detaching application from window server
    May  7 18:27:21 myMacAir.local ManagedClient[699]: *** -[NSMachPort handlePortMessage:]: dropping incoming DO message because the connection is invalid
    May  7 18:27:21 myMacAir.local ManagedClient[699]: HIToolbox: received notification of WindowServer event port death.
    May  7 18:27:21 myMacAir.local ManagedClient[699]: port matched the WindowServer port created in BindCGSToRunLoop
    May  7 18:27:31 myMacAir.local ManagedClient[699]: CGSLookupServerRootPort: Failed to look up the port for "com.apple.windowserver" (268435459)
    May  7 18:27:31 myMacAir.local ManagedClient[709]: MCX.createConnection bootstrap_register failed = 1100
    May  7 18:27:31 myMacAir.local ManagedClient[709]: CGSGetNextEventRecord (Inline) connection 0x8c03, 32768 bytes
    May  7 18:27:31 myMacAir.local ManagedClient[709]: shutdown_server_connections: Detaching application from window server
    May  7 18:27:31 myMacAir.local ManagedClient[709]: *** -[NSMachPort handlePortMessage:]: dropping incoming DO message because the connection is invalid
    May  7 18:27:31 myMacAir.local ManagedClient[709]: HIToolbox: received notification of WindowServer event port death.
    May  7 18:27:31 myMacAir.local ManagedClient[709]: port matched the WindowServer port created in BindCGSToRunLoop
    May  7 19:27:38 myMacAir.local ManagedClient[709]: CGSLookupServerRootPort: Failed to look up the port for "com.apple.windowserver" (268435459)
    May  7 19:27:38 myMacAir.local ManagedClient[723]: MCX.createConnection bootstrap_register failed = 1100
    May  7 19:27:38 myMacAir.local ManagedClient[723]: CGError CGSGetDisplaySystemState(uint64_t, CGSDisplaySystemState **): MIG error 0xfffffecc: (ipc/mig) server died
    May  7 19:27:38 myMacAir.local ManagedClient[723]: CGError CGSGetDisplaySystemState(uint64_t, CGSDisplaySystemState **): MIG error 0x10000003: (ipc/send) invalid destination port
    May  7 19:27:48 lan177.wibblers.org ManagedClient[734]: MCX.createConnection bootstrap_register failed = 1100
    May  7 20:27:55 myMacAir.local ManagedClient[734]: CGError CGSGetDisplaySystemState(uint64_t, CGSDisplaySystemState **): MIG error 0x10000003: (ipc/send) invalid destination port
    May  7 20:27:55 myMacAir.local ManagedClient[734]: CGError CGSGetDisplaySystemState(uint64_t, CGSDisplaySystemState **): MIG error 0x10000003: (ipc/send) invalid destination port
    May  7 20:27:55 myMacAir.local ManagedClient[734]: CGSGetOnScreenWindowCount
    May  7 20:27:55 myMacAir.local ManagedClient[734]: CGSGetNextEventRecord (Inline) connection 0x8a03, 32768 bytes
    May  7 20:27:55 myMacAir.local ManagedClient[734]: shutdown_server_connections: Detaching application from window server
    May  7 20:27:55 myMacAir.local ManagedClient[734]: CGSLookupServerRootPort: Failed to look up the port for "com.apple.windowserver" (268435459)
    May  7 20:27:55 myMacAir.local ManagedClient[734]: *** -[NSMachPort handlePortMessage:]: dropping incoming DO message because the connection is invalid
    May  7 20:27:55 myMacAir.local ManagedClient[734]: HIToolbox: received notification of WindowServer event port death.
    May  7 20:27:55 myMacAir.local ManagedClient[734]: port matched the WindowServer port created in BindCGSToRunLoop
    May  7 20:27:55 myMacAir.local ManagedClient[749]: MCX.createConnection bootstrap_register failed = 1100
    May  7 20:28:06 myMacAir.local ManagedClient[771]: MCX.createConnection bootstrap_register failed = 1100
    May  7 20:28:06 myMacAir.local ManagedClient[771]: *** -[NSMachPort handlePortMessage:]: dropping incoming DO message because the connection is invalid
    May  7 20:28:06 myMacAir.local ManagedClient[771]: CGSGetNextEventRecord (Inline) connection 0x8b03, 32768 bytes
    May  7 20:28:06 myMacAir.local ManagedClient[771]: shutdown_server_connections: Detaching application from window server
    May  7 20:28:06 myMacAir.local ManagedClient[771]: HIToolbox: received notification of WindowServer event port death.
    May  7 20:28:06 myMacAir.local ManagedClient[771]: port matched the WindowServer port created in BindCGSToRunLoop
    May  7 20:28:16 myMacAir.local ManagedClient[771]: CGSLookupServerRootPort: Failed to look up the port for "com.apple.windowserver" (268435459)
    May  7 20:28:16 myMacAir.local ManagedClient[781]: MCX.createConnection bootstrap_register failed = 1100
    May  7 20:28:16 myMacAir.local ManagedClient[781]: CGSGetNextEventRecord (Inline) connection 0x8d03, 32768 bytes
    May  7 20:28:16 myMacAir.local ManagedClient[781]: shutdown_server_connections: Detaching application from window server
    May  7 20:28:16 myMacAir.local ManagedClient[781]: *** -[NSMachPort handlePortMessage:]: dropping incoming DO message because the connection is invalid
    May  7 20:28:16 myMacAir.local ManagedClient[781]: HIToolbox: received notification of WindowServer event port death.
    May  7 20:28:16 myMacAir.local ManagedClient[781]: port matched the WindowServer port created in BindCGSToRunLoop
    May  7 20:58:20 myMacAir.local ManagedClient[781]: CGSLookupServerRootPort: Failed to look up the port for "com.apple.windowserver" (268435459)
    May  7 20:58:20 myMacAir.local ManagedClient[787]: MCX.createConnection bootstrap_register failed = 1100

  • Apple app windows disappear after coming out of sleep

    In Yosemite, after coming out of sleep, some Apple apps are still active but the windows have disappeared. I have noticed this with the Activity Monitor and with the Calculator. I played around with Hide/Show Windows, etc and was finally able to make the Activity Monitor window show up. I was unable to get the window to show up in the Calculator. Killing and restarting the app resolved the issue.
    I have not had any problems with non-Apple apps, and Finder and Safari seem to be OK.

    Further correction: Even when initially launched, after a restart Activity Monitor and Settings will both launch with no windows. There is a window name shown when right clicking on the icon in the Dock and in the application menu, but clicking on the window does not bring it up for display. With no Activity Monitor, you have to use command line, ps command and kill to clear the processes, following which they can be relaunched with all windows displayed.

  • Screen freezing/blanking when coming out of sleep

    Hi,
    Wonder if someone can help.
    I have a iMac (20-inch Mid 2007), that's been running fine up till about a year ago.
    Now sometimes when you take it out of sleep, one of the following will happen:
    - Screen will come on, then just go blank.
    or
    - Screen will come on, screen freezes but the cursor will still move around, but nothing will be selectable.
    With both you can hear the hard drive and fans still spinning. The only way to bring it back is to completely power it off, and on.  But sometimes after doing this, after signing in again, it my freeze or blank out again.
    When the iMac is on, its normally ok, but if after bringing out of sleep you try and open things, it can then go blank or freeze as above.  But when Its been on for 5 minutes  its fine and runs fine for hours or even days if you leave it on.
    It doesn't always happen, many times when you turn it on, its fine, just getting more and more...
    I have upgraded to latest OS and recently upgraded the 250gb internal hard drive to 1TB drive, I cleaned the fans out while doing this, but again issues remain.
    Can anyone suggest what could be causing this?  I would be fixing it myself, as its out of warranty and more than capable of doing a full strip down.
    Thanks
    ShaiboyUK

    anyone help?

  • Mac makes "waking out of sleep" noise without screen turning on.

    I always put my Mac to sleep. For a while now, I would notice the Mac would make the noise randomly (middle of the night lets say) as if it were coming out of sleep mode yet the screen wouldn't turn on. Only when I physically bring it out of sleep mode the monitor obviously turns on. Any reason for this? Thanks!

    It seems I've seen a few posts about the Logitech drivers causing KPs recently. Try doing a search on "Logitech" for recent posts. I would do this for you, but the forums are running slow right now.

  • Optical drive tries to find a disk at startup and when getting out of sleep

    I don't think it's a macbook only problem. I had tried to install photoshop but at a certain point, the computer freezes and I had to shutdown. When I startup, it freezes after five seconds when loading up everything everytime, but the mouse still moves. I finally found out about the safe mode so I solved my inability to work with my macbook.
    The problem I have now is that everytime I startup the computer, it wants to find a disk in the optical drive. It only does it once but it does it everytime I startup and also coming out of sleep, any suggestions?

    Is the system process to look the optical drive that bad, I mean like sound wise, was it horrible, and what about the time consuming when it look for something in the drive, was it a couple second or it took forever with the beachball rolling. And was it like that since you have it or it just happen after you installed photoshop and freeze.
    If it just like couple second, I assume it just default setting from PRAM that instruct optical drive everytime you start up or wake up from sleep to check is there something inside the optical drive that need to be read or spit it out or it could be the lens adjusted/calibrated itself, but I could be wrong on this.
    But if it to annoying and you suspect a mal-production, better bring that to apple store and show them and consult with them, probably you will get a better one that is not a mal-production.
    Hope this help.
    Mike

  • My laptop won't come out of sleep

    I have the Macbook Pro w/ retina display and whenever I go to open it, my laptop won't come out of sleep and I have to hold the power button to turn it off then back on again. I have to do the same thing if I walk away from it for to long and the laptop goes to sleep except this time when I bring it out of slepp it just shows the enter password for user screen but it is frozen. I got my laptop on the 8th of June 2013 so it is practicly brand new. Does anyone know how to fix this problem.

    Brand new out of the box this shouldn't happen. Bring it to an Apple store or AASP.

  • Hi fan speed when coming out of sleep

    Hello Everyone,
    I've had my iMAC Core Duo for a week now and I've noticed that when I power up the iMAC from shutdown the fans are almost completely silent. After I put the iMAC to sleep for a while 1 hour or so and wake it up the fans kick into high speed and don't slow down at all (lots of noise). I've tried reseting the SMU (unplug the mac, wait 30 seconds and plug it back in while holding down the power button.), no luck. I also tried reseting the NVRAM and deleting the powermanagement.plist. No luck. Anyone else having the same issue? If so have you found a fix or work around?
    Thanks,
    Rem

    Looks like I've been able to narrow this down. I have a second monitor attached to the iMAC in extended desktop mode. If I remove the mini DVI connector to the second monitor and put the iMAC to sleep and wake it up a while later the fans start up go fast and within a few seconds slow right down to an level barely audible. Put the Mini DVI back in put it to sleep bring it out of sleep and the fans kick in full and stay on. Anyone else having this issue?

  • MBP won't sleep since Lion upgrade

    Late 2008 MacBook pro, since upgrading to lion will not go to sleep. Screen goes dark, but fan continues to run, and power light stays solid without flashing. I've tries sleeping the computer with the keyboard shortcut, with the apple remote, and with the apple menu. Sleep mode works normally when the magsafe plug is disconnected, but not when it's connected. I've tried resetting PRAM and SMC, and quitting processes in the activity monitor.

    I've been having a similar problem. I haven't found a permanent solution but I have found a work around. If you have TextExpander or Alfred this will work much faster.
    I was able to use the 'pmset -g log' terminal command to find out that mDNSResponder was the reason my MBP wouldn't fall alseep. So it has something to do with Bonjour.
    I then found a pair of command codes to shut off and turn on Bonjour. After using them, my MBP goes to sleep without issue.
    Turn Off Bonjour: sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.mDNSResponder.plist
    Turn On Bonjour: sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.mDNSResponder.plist
    You'll notice that when you turn off Bonjour that you won't be able to use the Internet. That is the only down side to this work-around.
    Using Textexpander you can use 'ssleep' and 'wwake' for the two command codes and alfred can give you quick access to the terminal.
    I hope that helps somewhat.

  • MBP Won't Sleep automatically. Sleep light on. Not pulsing. Drive spinning.

    I can get my new MBP SR to sleep when I tell it to but it won't sleep when it's supposed to according to my Energy Saver preferences.
    Instead of sleeping, the screen goes dark and the sleep light stays on at medium - no pulsing. I can hear the hard drive still spinning. I tried changing my screen saver to one of the original Apple settings (Computer Name) but that didn't help. I'm going to try throwing away my Energy Saver prefs.
    Any suggestions?
    BTW - I took a closer look and I was a bit surprised at how many posts there are for the MacBook Pro on the Apple.com discussions. The most posts per day of any model by far. I know its a very popular Mac but this model seems to have more problems than we are able to solve. That worries me. Anybody else noticing this?
    -Todd

    I had exactly the same issue and needed three hours to find out the reason. It was the Bluetooth Mighty Mouse. I had to disselect the *third option* in the *bluetooth preferences*. I have a German-language OS X so I don't know the exactly expression but it affects the ability for bluetooth devices to weak up the system.
    If you have EyeTV 2: This application must not be running. If you have scheduled recordings that doesn't matter it will record anyway: It will wake up the Mac - record the thing - go to sleep again.
    I have several devices connected to the MBP: Three external enclosures with harddisk drives (2xFW800, 1xUSB without sleep function), EyeTV 610, speakers - all those things did not prevent the system for going to sleep. All those devices can be left attached - up and running. The FW harddisks will go to sleep the USB not.

  • MBP: Failure to sleep, leads to forced hard boot and sometimes overheating

    I am new to the Mac world, but it appears as though these are both common issues. I am thinking that my problem is more about failure to sleep properly than the overheating (it wouldn't overheat if it were asleep properly!).
    Situation:
    1. I have a bunch or a few programs running.
    2. I close the lid.
    3. It looks like the display shuts down.
    4. I put the machine in my bag, which has a furry inside to prevent scratches.
    5. I live my life for a while.
    6. Later, I find that my MBP is burning up, opening the lid doesn't get the machine to "wake up", the batteries have been drained, and I need to hard reboot to get the machine back.
    Anyway, I have read on some groups that the failure to properly sleep is a hardware problem, others opt for an OS upgrade, and one promising lead that suggested I pull the power before closing the lid.
    It seems that several of the conversations I've read are old, and my MBP is only 2 months old, so I think I have the latest OS builds. Pulling the power cord seems to not matter. This leaves me with the possibility of a hardware issue... My best guess is that my machine a) can't figure out if it is plugged in or not; b) can't figure out if it is asleep or awake; or c) restarts, even with the lid closed, and without displaying the display.
    I suspect that when it gets running again, it heats up, burns the battery down to zero, and forces the OS to crash when the batteries run dry or nearly so.
    So, I thought I'd post my dilemma here, and maybe someone who is "current" on this issue on MBP's could suggest a good course of action. I have AppleCare, so it is certainly an option to get the hardware replaced, however, is that going to actually help?
    Is this as common a problem as it seems like to me (100% of my Apple MBPs have this issue, even though my sample size is small at 1)?
    Are 10% of MBPs afflicted like this or more like 90%?
    Will Apple take care of me or will it be a battle?
    I really appreciate anyone who can help me out with suggestions on what course of action to take next.
    Kevin

    Eve, I think you are having the same problem I had. Basically, sleep seems to not be very resilient, and in my case I think it was partially because the machine kept running and then entered a semi-failure state when the battery finally drained out. I think the machine just can't handle running out of power, which is somewhat reasonable. I'd like to see Apple make the machine recognize that it is sleeping, and running out of power, and then automatically deep sleep itself to protect your session...
    You can test to see if we had the same problem by doing this when the machine "won't wake back up":
    - make sure the power cable is in
    - depress the power button for a long time, like 10 seconds to force a hard reboot (it seems weird, because the machine looks like it is off already)
    - you may "feel" the machine shut down (I don't know how else to describe it, but you can "tell" that it shut down).
    - release the power button
    - then, press the power again, as if to turn on
    - I think you will find that your MBP has now started back up
    So, if you see this problem when your MBP has been sleeping for a while, I think you have the same problem I did. Now, if you deep sleep it (using the widget referred to above) every time you put it away, and wake it up with the power button, I think you will have very few problems.
    The only problems I've had since starting this process was that a couple of times, the MBP didn't realize it was quite awake and feel back into deep sleep. This wasn't so bad as you just had to hit the power button to wake it up again. I'm also not 100% sure that there wasn't user error (me!) that caused that problem...
    Anyway, give this widget a try and see if your problem goes away. I think you will find that it does.

  • MBP wakes from sleep as soon as ac adapter is plugged in

    My MBP recently wakes from sleep after this series of events:
    1. Use MBP on battery power
    2. Close lid
    3. Sleeps (light pulses so apparently sleeping)
    4. Plug in AC adapter (while the lid is still closed)
    5. Wakes at that moment the adapter is plugged in (while the lid is still closed)
    6. Sometimes the MBP recognizes the lid is indeed closed and then goes to sleep itself; other times, the MBP goes to sleep, then immediately wakes, then goes to sleep, then wakes, etc., repeatedly (this happens all while the lid is closed as if it's demented), until I open the lid, wake the system and then close the lid again. Then it will finally sleep.
    "Wake on AC change" is set to No (see below). I was wondering if anyone knew how to set it to Yes. Maybe I just need to switch the setting back and forth once.
    I can recreate the problem, so I can just take it to the Apple Store and let them figure it out (Applecare is still in effect), but I was just wanted to give it a shot here first.
    Battery Information:
    Model Information:
    Serial Number: Sony-ASMB012-3926-1554
    Manufacturer: Sony
    Device name: ASMB012
    Pack Lot Code: 0001
    PCB Lot Code: 0000
    Firmware Version: 0110
    Hardware Revision: 0500
    Cell Revision: 0303
    Charge Information:
    Charge remaining (mAh): 4811
    Fully charged: No
    Charging: Yes
    Full charge capacity (mAh): 5202
    Health Information:
    Cycle count: 91
    Condition: Good
    Battery Installed: Yes
    Amperage (mA): 1342
    Voltage (mV): 12530
    System Power Settings:
    AC Power:
    System Sleep Timer (Minutes): 20
    Disk Sleep Timer (Minutes): 10
    Display Sleep Timer (Minutes): 20
    Automatic Restart On Power Loss: No
    Wake On AC Change: No
    Wake On Clamshell Open: Yes
    Wake On LAN: No
    Display Sleep Uses Dim: Yes
    Battery Power:
    System Sleep Timer (Minutes): 5
    Disk Sleep Timer (Minutes): 10
    Display Sleep Timer (Minutes): 3
    Wake On AC Change: No
    Wake On Clamshell Open: Yes
    Display Sleep Uses Dim: Yes
    Reduce Brightness: Yes
    Hardware Configuration:
    UPS Installed: No
    AC Charger Information:
    Connected: Yes
    Charging: Yes

    tsenga88 wrote:
    i have the same problem as well...but in my case water spilled on my macbook i let dry it for a day and when i switched it on it went on  butwent off after about an hour..and ever since then every time i connect the charger it turnsoff and some times it just doesnt charge at all...please help
    You don't have the same problem, you have the 'I damaged my Mac by spilling water on it' problem.
    it will probably fail.
    Take it to an Apple Store.

Maybe you are looking for