MacBook Pro Sleep issues

Hi
Does anyone have any sleep issues with their macbook pro?
When mine goes to sleep and i can wake it up but if i leave it to go into a deeper sleep i can't wake it up. tried using the keypad, touchpad, power button (even reseting), all that happens is it switches on but the screen doesn't come on and the sleep light flashes. The only way i can get it on is if i remove the magsafe connctor and the battery, then reconnect the magsafe and press the powerbutton, it wakes up and loads up to where i previously left off, then i can reconnect my battery. anyone also experienceing a muffled moo noise from their superdrive (every couple of minutes even when there is no disk inside)?
I have the 2.0ghz version with the faster graphics card, 100gb (7200rpm drive), apples 1gb ram, crucial 1gb ram. I'm going to take it down to my local applestore this weekend but i don't want them to hold on to it for such a long time.

I've had this same problem for a couple weeks now. At the Apple Store, they pulled my Crucial RAM and sent me packing. So, I gave the benefit of the doubt, returned the "bad stick" and got another. Same problem.
To be specific, mine would often restart instead of waking, or do nothing at all, forcing me to pop the battery out, or hold the power button to shut it off, then restart.
On my second trip to the store, today, they tried pulling the new Crucial RAM and replacing it with Apple RAM. That worked! So, they claim third party problems and I can't say they're wrong. However, it makes me wonder about proprietary settings in RAM, if that's even possible. I wonder if two sticks of Crucial RAM would work just fine? It's almost worth the try, as the cost is nearly half that of another 1GB of Apple RAM.
Not sure what I'm going to do as of today, might try another vendor for even less than Crucial to see if I have any luck, though I'm nervous to trust some other brand as though it might fix the sleep issue, it could be less reliable for more important usage.

Similar Messages

MacBook Pro sleeping issues

Here's the scoop:
My MacBook Pro (late-2007) randomly goes into sleep mode. It would go to sleep, wake up, go to sleep, wake up, go to sleep...etc. It would do this for about 4-5 times before it just sleeps and doesn't wake back up.
But there's the twist. This only happens when my MacBook Pro is connected to my external display (a Dell) with the lid is closed AND when the MBP is running off of the battery. The only way to wake up my computer would be to open the lid (as neither my Apple wired keyboard or Bluetooth mouse can wake it back up), but then that would be terribly inefficient and render my external display useless. Everything does run fine when the magsafe is plugged in, or if I'm running off of the batter with the lid open.
I have tried to reset the SMC twice with no success. Actually, after my second reset, I was able to use my MBP connected to my display, lid closed, and without magsafe connected. However when I stepped away from my computer, it went to sleep and wouldn't wake up. It is worth mentioning that I changed my battery a week ago but have tried using my old battery again to eliminate a bad battery issue to no avail.
This post is really just a stab in the dark as I'm trying to find solutions before my Genius appointment on Thursday. I hope someone can help.

Does the problem occur when the AC adaptor is connected? If not open Energy Saver preferences and set them to mimic in Battery mode what they are in Adaptor mode. By default these two modes are quite different. Furthermore, the OS will turn off power or reduce power to external ports to conserve battery power. This would not normally be conducive to having an external monitor, keyboard, and mouse connected.

Magic mouse and Macbook Pro Sleeping issues

Since I upgraded to Lion a few months ago, I've noticed that occasionally my Macbook Pro (early 2010) won't sleep when I close the lid. I think I've narrowed down (at least one of) the cause(s): if I turn off my bluetooth Magic Mouse after the lid is closed, the computer won't sleep. In fact, it will run hotter and hotter with the lid closed and, when I open the computer, it's non responsive, necessitating a hard reboot. I've checked the pmset log and I see the EHC2 (bluetooth mouse) waking the computer immediately after the clamshell sleep. Has anyone else seen this problem (I've seen similar things on the foroum, but not quite the same) and does anyone know what to do about it?

Repair disk permissions. Open this app:
Applications > Utilities > Disk Utility.app
Ensure your current volume is selected in the left hand column. Click 'First Aid' (if its not already selected), then 'Repair Disk Permissions' at the bottom.
Ignore the various warnings that come up in the 'Details' window, so long you get a message at the end saying 'Permissions repair complete'.

A solution for macbook pro sleep issue

I had a very annoying problem with my ~1 year old MBP. When I closed the lid, about 50% of the time the computer would not wake up after reopening the lid. The screen would just stay black and there would be no responsiveness from the keyboard or trackpad. I looked up the problem on google and found that many, many people had the same issue and could not find a single solution that worked for me. I called apple support and there suggestion was to reinstall the OS, which I did not want to do. They also suggested booting off the installation disk, but I didn't want to spend time trying to track down an intermittent problem. The solution that worked for me was as follows:
in the preferences tab under security there is an option 'use secure virtual memory'; if you are using a password, this option is grayed out. you can leave this option checked, but it's important to know whether you are using secure VM or not.
the next step is to go the terminal and type
pmset -g | grep hibernatemode
you will see a number pop up, from 0 to 7. the meaning off the numbers is as follows:
0 - Old style sleep mode, with RAM powered on while sleeping, safe sleep disabled, and super-fast wake.
1 - Hibernation mode, with RAM contents written to disk, system totally shut down while “sleeping,” and slower wake up, due to reading the contents of RAM off the hard drive.
3 - The default mode on machines introduced since about fall 2005. RAM is powered on while sleeping, but RAM contents are also written to disk before sleeping. In the event of total power loss, the system enters hibernation mode automatically.
5 - This is the same as mode 1, but it’s for those using secure virtual memory (in System Preferences -> Security).
7 - This is the same as mode 3, but it’s for those using secure virtual memory.
I had 3 selected and this was causing me all the problems because I should have had it at 7, which is the option compatible with secure VM. to change it, simply type
sudo pmset -a hibernatemode 7
That's it! I tried setting it to 0, but this did not solve my problem. Hopefully, this solution will hold up, but I haven't had any problems thus far.

If you have more than one user account, these instructions must be carried out as an administrator.
Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
Step 1
Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left.
Enter "BOOT_TIME" (without the quotes) in the search box. Note the timestamps of those log messages, which refer to the times when the system was booted. Now clear the search box and scroll back in the log to the last boot time when you had the problem. Post the messages logged before the boot, while the system was unresponsive or was failing to shut down. Please include the BOOT_TIME message at the end of the log extract.
Post the log text, please, not a screenshot. If there are runs of repeated messages, post only one example of each. Don’t post many repetitions of the same message. When posting a log extract, be selective. In most cases, a few dozen lines are more than enough.
Please do not indiscriminately dump thousands of lines from the log into a message.
Important: Some private information, such as your name, may appear in the log. Edit it out by search-and-replace in a text editor before posting.
Step 2
Still in Console, look under System Diagnostic Reports for crash or panic logs, and post the most recent one, if any. In the interest of privacy, I suggest you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if present (it may not be.) Please don’t post shutdownStall, spin, or hang logs — they're very long and not helpful.

MacBook Pro Sleep/Wake from sleep problem

As of today I have been experiencing a strange problem with my MBP. I can't wake my MBP when I open the screen although the machine is running. I also realized that I can't put it to sleep mode when I select it from the menu. Also, strangely, when I close the display to put it in sleep mode, the light stays on, instead of blinking. I already reset the power manager and the parameter RAM. I also have all my software updated. Any help would be appreciated.

I searched for Macbook Pro sleep issues since I am having one with my brand new 2.4 MBP.
I adjusted the sleep mode so it doesn't "safe sleep" because that took far too long for my needs. Before and after doing so, however, after the computer goes to sleep (pulsing light), I have taken it out of its bag and noticed the Apple lit up and it making noise. It wakes when I open the lid again but I am concerned it never slept soundly.
I have Bluetooth wake from sleep OFF so that's not the issue.
Has anyone else had concerns that their MBP is not sleeping soundly? I don't want to damage this computer, but I cart it back and forth to work every day i my backpack, and I need to be comfortable that it's parked and asleep during transit.

Macbook pro shutdown issue

Macbook pro shutdown issue when I push the power button it immediately goes into sleep mode

Hello Marrio22,
Thank you for the question. With OS X Mavericks, the power button has new functionality:
OS X Mavericks updates the power button behavior on Mac computers.
Using the Power Button to Sleep & Wake
Tap the power button in Mavericks to put your Mac to sleep or to wake it up:
Tap the power button once to put your Mac to sleep.
Tap the power button again to wake your Mac.
Press the power button for less than a half a second to sleep or wake your Mac. This duration is similar to pressing the Space bar or Return key to wake your Mac. The power button works this way across all Macs using OS X Mavericks, including both notebook and desktop computers.
Accessing the Shut Down Dialog
Press and hold the power button for 1.5 seconds, to bring up additional options:
Forcing the Mac to Turn Off
Hold down the power button for 5 seconds to force the computer to turn off. Important: You may lose unsaved documents if you force the computer to turn off this way. Use this method of turning off your Mac only if it has become unresponsive for an extended period of time. Normally you should shut down the computer by selecting Shut Down from the Apple menu, or from the shut down dialog pictured above.
OS X Mavericks: Using the power button
http://support.apple.com/kb/HT5869
Thank you for using Apple Support Communities.
Best,
Sheila M.

Macbook Pro Wifi Issue

I incorrectly posted this in the wrong thread this morning.
I'm hopeful you might be able to help me diagnose a problem I'm having. I'll provide as much detail as possible.
I have a first generation MacBook Pro. As of this morning I was running 10.5.6 and up until this week was using a linksys router and a comcast cable modem.
I used to have a great wifi signal throughout the house (always full strength), and around 12-18 months ago noticed the signal would weaken. The best I would get would be minus the top bar on the signal, and usually only if I was directly above or next to the room with the router. There were no new phones or devices added that might adjust the signal. On the other side of the house, I would have no signal at all.
My wife has a nine year old ibook and has no issues connecting through wifi.
When I bring my laptop to her parents' house or to the Apple store, where they use Belkin on N or Airport Extreme, I get a full signal.
I've recently suffered a hard drive failure and had a replacement drive installed. The problem persists despite the software update.
Not knowing if it was a router issue or an airport card issue or a combination thereof, I went to the Genius Bar. The genius recommended I upgrade my router to Airport Extreme, and if that doesn't work to return it and he'd focus on the airport card or antenna. I could get the flat rate repair (no AppleCare at this point) for $320+ to repair the problem if Extreme didn't work.
I installed the Airport Extreme router and got a full signal in the basement, far side of the house, upstairs - everywhere. Until around 10pm. The signal died from the basement. If I walked into the room with the Airport Extreme router, I'd get a full signal. If I left the room, I'd get a partial signal. If I walked any distance (10-12 feet), the signal would die. I restarted both the modem and router with no change. I reinstalled the linksys router and got a depreciated connection. I restarted the Airport Extreme again and got a full signal throughout the night, morning, through restarts, and when I returned home from work.
Last evening after using youtube extensively it died again. Linksys would barely work if I switched back, and no matter how many times I restarted I couldn't get the signal to last outside of the area of the router. I left it in the basement overnight shut down, restarted this morning, and had a full signal.
I'm looking for any potential guesses as to what may be causing the problem. I don't want to replace the card if it's the antenna or sink too much cash into a machine if it's a heat related issue linked to Generation 1 syndrome.
During all of this the ten year old ibook works fine. I know a lot of macbook pros have issues with their wireless and don't want to sink in the cash if it's more complex than that. Any advice is much appreciated!

Hi nashie1002,
If you are having issues connecting to your WPA2 WiFi network after a recent update, you may find the troubleshooting steps and settings in the following articles helpful:
Wi-Fi: How to troubleshoot Wi-Fi connectivity
http://support.apple.com/kb/HT4628
Apple Support: About Wireless Diagnostics
http://support.apple.com/kb/HT5606
iOS and OS X: Recommended settings for Wi-Fi routers and access points
http://support.apple.com/kb/ht4199
It may also be worth doing a search for the specific model number of your router to see if anyone has noted any issues with Mavericks.
Regards,
- Brenden

Can't install windondows 8.1 on my macbook pro - format issue

Can't install windondows 8.1 on my macbook pro - format issue
Running latest version of Mavericks.
Followed the exact bootcamp proceduce.
Have official window 8.1 version on cd.
All goes well until I have to format the 65Gb partition. Disk=0 and partition=4
Can't get over it. Altough I formatted it via a hint found on the internet with "dislpart" in NTFS. Wich also went weel and give the labelname "BOOTCAMP". But still no luck.
I have two questions:
1/ How to start my mac again in normal mavericks mode?
2/ How can I overcome the windows installation issue?
Tried already a lot of hints found on the internet.

First, make a time machine backup. You will need to erase ands reformat your hard drive. I had the same issue. The issue is that you can't install Windows using bootcamp without having the hard drive formatted as Mac OS Extended (Journaled). Do this from disk utility or recovery mode (hold down command and r at startup). Then you have to restore the backup to the hard drive. Then make a usb installer drive with bootcamp and then partition and install. Here's a tip: after you install bootcamp and are in the Windows desktop, go into the installer drive and then go into the bootcamp or support folder, then find a installer that contains the Apple bootcamp drivers. Also, you will need to convert the disk to an iso file. TO MAKE THE USB DRIVE FROM A DISC, USE THIS LINK
Boot Camp: Creating an ISO image from a Windows installation DVD - Apple Support

Having Macbook Pro sleep/fan Issues

SUMMARY: Macbook Pro eventually loses ability to sleep properly, will begin to constantly wake with fans at full speed and then quickly go back to sleep, back and forth every 30 seconds while the lid is closed. Restarting fixes the issue but it always comes back after a day or two. Help?
I only occasionally shut down my Macbook Pro - usually I just close the lid and let it sleep when I'm away. But I've noticed that, after a while from my last shutdown/startup, it has trouble staying in sleep mode when the lid is closed. Initially it will sleep and the light will begin to fade in and out like normal, but after about a minute the light will come back on and the fans will suddenly boost to full speed, then quiets down and the unit sleeps again. This cycle repeats every 30 seconds or so, so I'll come home to find my MBP hot and quickly fading in and out of sleep mode. When I open the lid, the screen comes on immediately, then fades to black. I have to hit a key or something to get it to wake up properly.
Any idea what's happening here? I have a feeling it might be software-related.

Try these first:
Resetting your Mac's PRAM and NVRAM
Intel-based Macs: Resetting the System Management Controller (SMC)
If neither hels then reinstall OS X:
Reinstall OS X without erasing the drive
Do the following:
1. Repair the Hard Drive and Permissions
Boot from your Snow Leopard Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer.
If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
2. Reinstall Snow Leopard
If the drive is OK then quit DU and return to the installer. Proceed with reinstalling OS X. Note that the Snow Leopard installer will not erase your drive or disturb your files. After installing a fresh copy of OS X the installer will move your Home folder, third-party applications, support items, and network preferences into the newly installed system.
Download and install the Combo Updater for the version you prefer from support.apple.com/downloads/.

13' MacBook Pro Sleep/Random Shut Down Issues

I purchased a new 13' MacBook Pro about 7 months ago before my first semester of college. Until last week, everything has run at a squeaky clean pace, with no technical issues. Last week, I noticed that my MBP was going into sleep mode and simply shutting down after a about half an hour of sleeping. I dont recall it ever doing this before. If I leave the screen closed, I can open the computer and hit the power button and I will be restored back to the screen I was originally working on, however, if my MBP falls asleep while open, it shuts down eventually and when I hit the power button, it completely reboots the system with no saved position. I thought this was strange, but my MBP has now formed the habit of shutting down without my promting at various occasions. This shutting down is not occurring at very frequent intervals but it is still a problem.
Any assistance would be appreciated!

Try this:
Reset the PRAM:
http://support.apple.com/kb/HT1379?viewlocale=en_US
It's been recommended you wait for the third chime.
There are also a couple of plists you can try removing. These are in Finder in Macintosh HD:
/Library/Preferences/System Configuration/com.apple.PowerManagement.plist
/Library/Preferences/System Configuration/com.apple.Autowake.plist
Good luck!

Advice appreciated on a MacBook pro HDD issue

Hello,
I've just suffered my first real system problem and even though I have a few ideas for how to fix it I thought I'd post here and ask for some advice to see what you guys think.
First the problem... Basically my MacBook Pro's HDD has an issue and won't boot. I don't think it's a physical problem with the hardware (although I'm open to advice on this too), I think it just needs a reformat and fresh install of the OS. But obviously I need to get my files off of there first and this is the problem, but read on for more details.
So that's the problem in a nutshell, but here's the full detail.
It's a MacBook Pro, late 2011, 17", 750GB HDD, 8GB RAM, bought in Miami September 2011 while I was on holiday there (I live in the UK), came with Snow Leopard installed, was upgraded to Lion a few days after purchase and then upgraded to Mountain Lion about a month ago.
Last week I was using it when it suddenly restarted itself. I let it restart, then began using it again and about five minutes later it restarted again, but this time it didn't boot properly.
It stayed on the grey screen with the apple logo and spinning clock-type wheel. There was a progress bar at the bottom of the screen, it took ages to move, then finally got to about 33% and the machine restarted itself again.
I tried lots of restarts but every time it did the same thing or it never even showed the progress bar, and just had the spinning clockwheel forever.
So I held down alt and booted from Mountain Lion's recovery partition instead. I launched Disk Utility and tried to verify / repair the drive but it came back with errors and said that it couldn't fix them. Apologies, I realise typing this that anyone reading would probably quite like to read the error long but I can't remember it and I'm not currently at home. If needed I'll run it again and post.
Anyway, the basic point is that Disk Utility is giving a message saying to copy all my files off the drive and reformat because it can't fix it. Incidentally the SMART status of the drive is fine / normal. Not showing any problems there, which is why I'm hopeful it's not a hadware issue.
So I need to copy my files off, and this is the real reason I'm posting this thread, because I don't mind doing a reformat / fresh install of Mountain Lion, but my last backup is a couple of months old (I know, naughty me) so while it wouldn't be the end of the world to copy files back from that, I would lose a bit of data so would like to get them off the MBP's HDD now.
At this point, let me list the kit I have at my disposal:
- At home I have the aforementioned patient (MacBook Pro), a 2TB external HDD with USB2 / FireWire 800 and a NAS box that sits on my network. I also have one of those cables that lets you connect an internal HDD via USB (more on this later, as I suspect it's going to be my best hope).
- At work I have a Windows 7 PC which I do not have any admin rights to, A Windows XP PC that I do have admin rights to and an iMac that is running Leopard (10.5.8) and cannot be upgraded due to various boring work reasons I won't go into here.
So the first thing I tried was booting into the recovery partition, launching Disk Utility and trying to clone the HDD over to the external 2TB drive I have. Cloning the drive like-for-like gives an error message (again apologies, I can't remember it) and trying to copy to an image file on the external drive gets all the way to the end (takes ages because Disk Utility keeps going to sleep) but then when I try to mount the image it gives an error and fails, so I don't trust this method.
So booting to recovery and using Disk Utility seems to be no good.
I thought about trying to take the MBP to work and launching it in target disk mode, then copying files, however I read that you can only have one FireWire device (the target computer) connected when doing this and my iMac at work doesn't have enough internal HDD space to copy all my MBP's files off, so I would need to have an external drive connected to the iMac in addition to the MBP, which sounds like it's not a good idea, or not supported by Apple anyway.
I thought about making a bootable Mountain Lion USB stick as I have a 16GB USB stick I could use for this, however I don't know how to make the bootable USB using my iMac as it's on Leopard (can't be upgraded for work reasons) and doesn't even have the Mac App store on it for me to re-download the Mountain Lion install file.
I think I have the Snow Leopard DVD that came with my MBP so could probably boot off this, but does that allow me into Finder or anything that would let me copy docs from my internal HDD properly over to the external drive? Or is it just going to look similar to the Mountain Lion recovery partition, with Disk Utility and a few other options?
I don't know whether the Mountain Lion recovery partition lets me install Mountain Lion onto my external drive? Or a USB? I was a bit scared to start clicking through options to see whether it would ask me which drive I wanted to install to, just in case it doesn't and begins erasing the main HDD as one of the first things it does.
So this leaves the cable that allows me to connect internal drives via USB. This cable has saved my bacon in the past and I suspect it may be my best option once more. Obviously this means I'm going to have to open up the MBP and remove the HDD but I installed the extra RAM myself and I've installed full-size (3.5") HDDs in the past so I should be able to handle that, unless there's anything radically different with 2.5" drives I'm not aware of.
I've heard people mention DiskWarrior in the past but to be honest if I'm going to spend that sort of money I'd prefer to just put it towards an new, larger HDD, probably a 2TB model.
So there we are, thanks for reading this far. If you have any advice about another (or better) way to get my files off the MBP I'm all ears.
I've never actually done a fresh install of Mac OS before either, only upgrades downloaded from the Mac App Store so any advice around that might be handy too, but mainly it's the file copying I want help with as I'll probably just boot from the recovery partition to reformat and reinstall Mountain Lion.
Thanks

Yes, on your profile.. But, did you phone update just before this happened?
I want you to view this image on both your phone and computer: Fiery Sunrise | Flickr - Photo Sharing!
If it looks different, it is not your images, but rather your iPhone....
Benjamin

Retina MacBook Pro sleep problem since 10.9.2

Ever since updating to 10.9.2 earlier in the week my macbook refuses to wake from sleep each morning.
Having looked at the console logs it seems that perhaps the problem is related to it not actually managing to go to sleep properly.
I closed the lid on the computer at about 19:07 as can be seen in the first of these console dumps. I put the laptop in my bag and went home, where the laptop stayed closed in my bag all night. Apparently the computer awoke 70 minutes later. In the morning, back at the office, I left the lid open for a good 5 minutes before deciding to reboot at 9:37, so it seems that the computer was indeed turned off as there was no activity in these minutes.
06/03/2014 19:07:12.574 airportd[84]: _handleLinkEvent: WiFi is not powered. Resetting state variables.
06/03/2014 19:07:12.000 kernel[0]: Thunderbolt Self-Reset Count = 0xedefbe00
06/03/2014 19:07:12.000 kernel[0]: **** [IOBluetoothHostControllerUSBTransport][SuspendDevice] -- Suspend -- suspendDeviceCallResult = 0x0000 (kIOReturnSuccess) -- 0xf400 ****
06/03/2014 19:07:12.000 kernel[0]: AppleThunderboltNHIType2::waitForOk2Go2Sx - retries = 6
06/03/2014 19:07:12.000 kernel[0]: Wake reason: EC.SleepTimer EHC1 (SleepTimer)
06/03/2014 20:17:14.000 kernel[0]: AirPort_Brcm43xx::powerChange: System Wake - Full Wake/ Dark Wake / Maintenance wake
06/03/2014 20:17:14.000 kernel[0]: Previous Sleep Cause: 5
06/03/2014 20:17:14.000 kernel[0]: The USB device HubDevice (Port 1 of Hub at 0x1d000000) may have caused a wake by issuing a remote wakeup (2)
06/03/2014 20:17:14.000 kernel[0]: AppleThunderboltNHI::prePCIWake - power up complete - took 0 us
06/03/2014 20:17:14.000 kernel[0]: AppleThunderboltHAL::earlyWake - complete - took 1 milliseconds
06/03/2014 20:17:14.000 kernel[0]: The USB device HubDevice (Port 8 of Hub at 0x1d100000) may have caused a wake by issuing a remote wakeup (3)
06/03/2014 20:17:14.000 kernel[0]: The USB device BRCM20702 Hub (Port 1 of Hub at 0x1d180000) may have caused a wake by issuing a remote wakeup (3)
06/03/2014 20:17:14.000 kernel[0]: Thunderbolt Self-Reset Count = 0xedefbe00
06/03/2014 20:17:14.000 kernel[0]: IOThunderboltSwitch<0xffffff80278cbc00>(0x0)::listenerCallback - Thunderbolt HPD packet for route = 0x0 port = 11 unplug = 0
06/03/2014 20:18:29.000 kernel[0]: IOPPF: Sent cpu-plimit-notification last value 25 (rounded time weighted average 25)
06/03/2014 20:18:39.000 kernel[0]: process com.apple.WebKit[2556] caught causing excessive wakeups. Observed wakeups rate (per sec): 250; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 48044
06/03/2014 20:18:39.458 ReportCrash[4729]: Invoking spindump for pid=2556 wakeups_rate=250 duration=180 because of excessive wakeups
06/03/2014 20:18:45.145 netbiosd[4725]: findReachableAddress: Using port 139 family = 33
06/03/2014 20:18:45.000 kernel[0]: smb1_smb_negotiate: Support for the server SPEEDPORT.IP has been deprecated (PreXP), disconnecting
06/03/2014 20:19:16.000 kernel[0]: IOPPF: Sent gpu-external-plimit-notification last value 12 (rounded time weighted average 12)
06/03/2014 20:19:16.000 kernel[0]: IOPPF: Sent gpu-internal-plimit-notification last value 14 (rounded time weighted average 14)
06/03/2014 20:19:21.558 netbiosd[4725]: findReachableAddress: Using port 139 family = 33
06/03/2014 20:19:21.000 kernel[0]: smb1_smb_negotiate: Support for the server SPEEDPORT.IP has been deprecated (PreXP), disconnecting
06/03/2014 20:19:22.000 kernel[0]: IOPPF: Sent cpu-plimit-notification last value 26 (rounded time weighted average 26)
06/03/2014 20:19:39.000 kernel[0]: process Sequel Pro[162] caught causing excessive wakeups. Observed wakeups rate (per sec): 172; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 120353
06/03/2014 20:19:40.000 kernel[0]: IOPPF: Sent gpu-external-plimit-notification last value 12 (rounded time weighted average 12)
06/03/2014 20:19:40.000 kernel[0]: IOPPF: Sent gpu-internal-plimit-notification last value 14 (rounded time weighted average 14)
06/03/2014 20:19:54.000 kernel[0]: IOPPF: Sent gpu-external-plimit-notification last value 14 (rounded time weighted average 14)
06/03/2014 20:19:54.000 kernel[0]: IOPPF: Sent gpu-internal-plimit-notification last value 14 (rounded time weighted average 14)
06/03/2014 20:19:59.975 netbiosd[4725]: findReachableAddress: Using port 139 family = 33
06/03/2014 20:19:59.000 kernel[0]: smb1_smb_negotiate: Support for the server SPEEDPORT.IP has been deprecated (PreXP), disconnecting
06/03/2014 20:20:11.000 kernel[0]: process Google Chrome[157] caught causing excessive wakeups. Observed wakeups rate (per sec): 1738; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 901505
06/03/2014 20:20:11.792 ReportCrash[4740]: Invoking spindump for pid=157 wakeups_rate=1738 duration=26 because of excessive wakeups
06/03/2014 20:20:12.000 kernel[0]: IOPPF: Sent gpu-external-plimit-notification last value 15 (rounded time weighted average 15)
06/03/2014 20:20:12.000 kernel[0]: IOPPF: Sent gpu-internal-plimit-notification last value 14 (rounded time weighted average 14)
06/03/2014 20:20:12.000 kernel[0]: process Dropbox[418] caught causing excessive wakeups. Observed wakeups rate (per sec): 162; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 166301
06/03/2014 20:20:12.676 ReportCrash[4740]: Invoking spindump for pid=418 wakeups_rate=162 duration=278 because of excessive wakeups
06/03/2014 20:20:38.370 netbiosd[4725]: findReachableAddress: Using port 139 family = 33
06/03/2014 20:20:38.000 kernel[0]: smb1_smb_negotiate: Support for the server SPEEDPORT.IP has been deprecated (PreXP), disconnecting
06/03/2014 20:22:29.000 kernel[0]: CODE SIGNING: cs_invalid_page(0x1000): p=4752[GoogleSoftwareUp] final status 0x0, allowing (remove VALID) page
07/03/2014 09:37:14.000 bootlog[0]: BOOT_TIME 1394181434 0
07/03/2014 09:37:16.000 syslogd[19]: Configuration Notice:
ASL Module "com.apple.appstore" claims selected messages.
Those messages may not appear in standard system log files or in the ASL database.
07/03/2014 09:37:16.000 syslogd[19]: Configuration Notice:
ASL Module "com.apple.authd" sharing output destination "/var/log/system.log" with ASL Module "com.apple.asl".
Output parameters from ASL Module "com.apple.asl" override any specified in ASL Module "com.apple.authd".
Weird huh? Can anyone tell from these logs why it's going mad in my bag? Why would it try and wake and then crash and power-off?

Similar problem 3 times since upgrading to 10.9.2.   Coworker also having same issue.
Process:         appProtd [459]
Path:            /usr/local/McAfee/AppProtection/bin/appProtd
Identifier:      appProtd
Version:         ???
Code Type:       X86 (Native)
Parent Process: launchd [1]
Responsible:     fmpd [86]
User ID:         0
Date/Time:       2014-03-08 14:33:13.906 -0800
OS Version:      Mac OS X 10.9.2 (13C64)
Report Version: 11
Anonymous UUID: 45DE248F-A51E-AE89-0EC5-C788B17FBE12
Crashed Thread: 6
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
Assertion failed: (!pthread_mutex_unlock(m)), function ~interruption_checker, file /usr/local/boost/include/boost/thread/pthread/thread_data.hpp, line 116.
Thread 0:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib                  0x93608102 setsockopt + 10
1   appProtd                                0x000bc8a1 AppProtection::KextInterface::stopHooking() + 65
2   appProtd                                0x000bc78f AppProtection::KextInterface::~KextInterface() + 111
3   appProtd                                0x0009350b AppProtection::AppProtectionController::~AppProtectionController() + 779
4   appProtd                                0x000931d3 AppProtection::AppProtectionController::~AppProtectionController() + 19
5   appProtd                                0x00093ad9 AppProtection::AppProtectionController::releaseInstance() + 313
6   appProtd                                0x000994a9 AppProtection::AppProtectionController::main(int, char**) + 1737
7   appProtd                                0x0009a3fb main + 11
8   appProtd                                0x00092c25 start + 53
Thread 1:
0   libsystem_kernel.dylib                  0x93607046 __workq_kernreturn + 10
1   libsystem_pthread.dylib                 0x940c3dcf _pthread_wqthread + 372
2   libsystem_pthread.dylib                 0x940c7cce start_wqthread + 30
Thread 2:: Dispatch queue: com.apple.libdispatch-manager
0   libsystem_kernel.dylib                  0x93607992 kevent64 + 10
1   libdispatch.dylib                       0x932ee8ad _dispatch_mgr_invoke + 238
2   libdispatch.dylib                       0x932ee546 _dispatch_mgr_thread + 52
Thread 3:
0   libsystem_kernel.dylib                  0x93607046 __workq_kernreturn + 10
1   libsystem_pthread.dylib                 0x940c3dcf _pthread_wqthread + 372
2   libsystem_pthread.dylib                 0x940c7cce start_wqthread + 30
Thread 4:
0   libsystem_kernel.dylib                  0x936067ca __psynch_cvwait + 10
1   libsystem_pthread.dylib                 0x940c4d1d _pthread_cond_wait + 728
2   libsystem_pthread.dylib                 0x940c6c25 pthread_cond_timedwait$UNIX2003 + 71
3   appProtd                                0x0009f42b bool boost::condition_variable_any::timed_wait<boost::unique_lock<boost::mutex> >(boost::unique_lock<boost::mutex>&, boost::posix_time::ptime const&) + 203
4   appProtd                                0x000941fb AppProtection::AppProtectionController::popFromRequestQueue() + 1243
5   appProtd                                0x00095534 AppProtection::AppProtectionController::processRequests() + 308
6   appProtd                                0x0009dada boost::detail::thread_data<boost::_bi::bind_t<void, boost::_mfi::mf0<void, AppProtection::AppProtectionController>, boost::_bi::list1<boost::reference_wrapper<AppProtection::AppProtectionControll er> > > >::run() + 42
7   libboost_thread.dylib                   0x004f454a thread_proxy + 170
8   libsystem_pthread.dylib                 0x940c25fb _pthread_body + 144
9   libsystem_pthread.dylib                 0x940c2485 _pthread_start + 130
10 libsystem_pthread.dylib                 0x940c7cf2 thread_start + 34
Thread 5:
0   libsystem_kernel.dylib                  0x936067ca __psynch_cvwait + 10
1   libsystem_pthread.dylib                 0x940c4d1d _pthread_cond_wait + 728
2   libsystem_pthread.dylib                 0x940c6c25 pthread_cond_timedwait$UNIX2003 + 71
3   appProtd                                0x0009f42b bool boost::condition_variable_any::timed_wait<boost::unique_lock<boost::mutex> >(boost::unique_lock<boost::mutex>&, boost::posix_time::ptime const&) + 203
4   appProtd                                0x000941fb AppProtection::AppProtectionController::popFromRequestQueue() + 1243
5   appProtd                                0x00095534 AppProtection::AppProtectionController::processRequests() + 308
6   appProtd                                0x0009dada boost::detail::thread_data<boost::_bi::bind_t<void, boost::_mfi::mf0<void, AppProtection::AppProtectionController>, boost::_bi::list1<boost::reference_wrapper<AppProtection::AppProtectionControll er> > > >::run() + 42
7   libboost_thread.dylib                   0x004f454a thread_proxy + 170
8   libsystem_pthread.dylib                 0x940c25fb _pthread_body + 144
9   libsystem_pthread.dylib                 0x940c2485 _pthread_start + 130
10 libsystem_pthread.dylib                 0x940c7cf2 thread_start + 34
Thread 6 Crashed:
0   libsystem_kernel.dylib                  0x93606952 __pthread_kill + 10
1   libsystem_pthread.dylib                 0x940c3167 pthread_kill + 101
2   libsystem_c.dylib                       0x9471329c abort + 155
3   libsystem_c.dylib                       0x946de39a __assert_rtn + 347
4   appProtd                                0x0009ce62 boost::detail::interruption_checker::~interruption_checker() + 242
5   appProtd                                0x0009f438 bool boost::condition_variable_any::timed_wait<boost::unique_lock<boost::mutex> >(boost::unique_lock<boost::mutex>&, boost::posix_time::ptime const&) + 216
6   appProtd                                0x000941fb AppProtection::AppProtectionController::popFromRequestQueue() + 1243
7   appProtd                                0x00095534 AppProtection::AppProtectionController::processRequests() + 308
8   appProtd                                0x0009dada boost::detail::thread_data<boost::_bi::bind_t<void, boost::_mfi::mf0<void, AppProtection::AppProtectionController>, boost::_bi::list1<boost::reference_wrapper<AppProtection::AppProtectionControll er> > > >::run() + 42
9   libboost_thread.dylib                   0x004f454a thread_proxy + 170
10 libsystem_pthread.dylib                 0x940c25fb _pthread_body + 144
11 libsystem_pthread.dylib                 0x940c2485 _pthread_start + 130
12 libsystem_pthread.dylib                 0x940c7cf2 thread_start + 34
Thread 7:
0   libsystem_kernel.dylib                  0x936067ca __psynch_cvwait + 10
1   libsystem_pthread.dylib                 0x940c4d1d _pthread_cond_wait + 728
2   libsystem_pthread.dylib                 0x940c6c25 pthread_cond_timedwait$UNIX2003 + 71
3   appProtd                                0x0009f42b bool boost::condition_variable_any::timed_wait<boost::unique_lock<boost::mutex> >(boost::unique_lock<boost::mutex>&, boost::posix_time::ptime const&) + 203
4   appProtd                                0x000941fb AppProtection::AppProtectionController::popFromRequestQueue() + 1243
5   appProtd                                0x00095534 AppProtection::AppProtectionController::processRequests() + 308
6   appProtd                                0x0009dada boost::detail::thread_data<boost::_bi::bind_t<void, boost::_mfi::mf0<void, AppProtection::AppProtectionController>, boost::_bi::list1<boost::reference_wrapper<AppProtection::AppProtectionControll er> > > >::run() + 42
7   libboost_thread.dylib                   0x004f454a thread_proxy + 170
8   libsystem_pthread.dylib                 0x940c25fb _pthread_body + 144
9   libsystem_pthread.dylib                 0x940c2485 _pthread_start + 130
10 libsystem_pthread.dylib                 0x940c7cf2 thread_start + 34
Thread 8:
0   libsystem_kernel.dylib                  0x936067ca __psynch_cvwait + 10
1   libsystem_pthread.dylib                 0x940c4d1d _pthread_cond_wait + 728
2   libsystem_pthread.dylib                 0x940c6c25 pthread_cond_timedwait$UNIX2003 + 71
3   appProtd                                0x0009f42b bool boost::condition_variable_any::timed_wait<boost::unique_lock<boost::mutex> >(boost::unique_lock<boost::mutex>&, boost::posix_time::ptime const&) + 203
4   appProtd                                0x000941fb AppProtection::AppProtectionController::popFromRequestQueue() + 1243
5   appProtd                                0x00095534 AppProtection::AppProtectionController::processRequests() + 308
6   appProtd                                0x0009dada boost::detail::thread_data<boost::_bi::bind_t<void, boost::_mfi::mf0<void, AppProtection::AppProtectionController>, boost::_bi::list1<boost::reference_wrapper<AppProtection::AppProtectionControll er> > > >::run() + 42
7   libboost_thread.dylib                   0x004f454a thread_proxy + 170
8   libsystem_pthread.dylib                 0x940c25fb _pthread_body + 144
9   libsystem_pthread.dylib                 0x940c2485 _pthread_start + 130
10 libsystem_pthread.dylib                 0x940c7cf2 thread_start + 34
Thread 9:
0   libsystem_kernel.dylib                  0x936067ca __psynch_cvwait + 10
1   libsystem_pthread.dylib                 0x940c4d1d _pthread_cond_wait + 728
2   libsystem_pthread.dylib                 0x940c6c25 pthread_cond_timedwait$UNIX2003 + 71
3   appProtd                                0x0009f42b bool boost::condition_variable_any::timed_wait<boost::unique_lock<boost::mutex> >(boost::unique_lock<boost::mutex>&, boost::posix_time::ptime const&) + 203
4   appProtd                                0x000941fb AppProtection::AppProtectionController::popFromRequestQueue() + 1243
5   appProtd                                0x00095534 AppProtection::AppProtectionController::processRequests() + 308
6   appProtd                                0x0009dada boost::detail::thread_data<boost::_bi::bind_t<void, boost::_mfi::mf0<void, AppProtection::AppProtectionController>, boost::_bi::list1<boost::reference_wrapper<AppProtection::AppProtectionControll er> > > >::run() + 42
7   libboost_thread.dylib                   0x004f454a thread_proxy + 170
8   libsystem_pthread.dylib                 0x940c25fb _pthread_body + 144
9   libsystem_pthread.dylib                 0x940c2485 _pthread_start + 130
10 libsystem_pthread.dylib                 0x940c7cf2 thread_start + 34
Thread 10:
0   libsystem_kernel.dylib                  0x936067ca __psynch_cvwait + 10
1   libsystem_pthread.dylib                 0x940c4d1d _pthread_cond_wait + 728
2   libsystem_pthread.dylib                 0x940c6c25 pthread_cond_timedwait$UNIX2003 + 71
3   appProtd                                0x0009f42b bool boost::condition_variable_any::timed_wait<boost::unique_lock<boost::mutex> >(boost::unique_lock<boost::mutex>&, boost::posix_time::ptime const&) + 203
4   appProtd                                0x00094797 AppProtection::AppProtectionController::popAllFromResponseQueue() + 967
5   appProtd                                0x000bdd4a AppProtection::KextInterface::sendResponseToKext() + 74
6   appProtd                                0x000be8ba boost::detail::thread_data<boost::_bi::bind_t<void, boost::_mfi::mf0<void, AppProtection::KextInterface>, boost::_bi::list1<boost::reference_wrapper<AppProtection::KextInterface> > > >::run() + 42
7   libboost_thread.dylib                   0x004f454a thread_proxy + 170
8   libsystem_pthread.dylib                 0x940c25fb _pthread_body + 144
9   libsystem_pthread.dylib                 0x940c2485 _pthread_start + 130
10 libsystem_pthread.dylib                 0x940c7cf2 thread_start + 34
Thread 11:
0   libsystem_kernel.dylib                  0x93606ace __select + 10
1   appProtd                                0x000bd188 AppProtection::KextInterface::getRequestsFromKext() + 1192
2   appProtd                                0x000be8ba boost::detail::thread_data<boost::_bi::bind_t<void, boost::_mfi::mf0<void, AppProtection::KextInterface>, boost::_bi::list1<boost::reference_wrapper<AppProtection::KextInterface> > > >::run() + 42
3   libboost_thread.dylib                   0x004f454a thread_proxy + 170
4   libsystem_pthread.dylib                 0x940c25fb _pthread_body + 144
5   libsystem_pthread.dylib                 0x940c2485 _pthread_start + 130
6   libsystem_pthread.dylib                 0x940c7cf2 thread_start + 34
Thread 6 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0xa0843cf8 ecx: 0xb04208cc edx: 0x93606952
edi: 0xb0421000 esi: 0x00000006 ebp: 0xb04208e8 esp: 0xb04208cc
   ss: 0x00000023 efl: 0x00000206 eip: 0x93606952   cs: 0x0000000b
   ds: 0x00000023   es: 0x00000023   fs: 0x00000023   gs: 0x0000000f
cr2: 0x0049f000
Logical CPU:     0
Error Code:      0x00080148
Trap Number:     132
Binary Images:
   0x92000 -   0x10fff7 +appProtd (???) <E600A460-30A5-3BCA-948D-FB3D8A071F12> /usr/local/McAfee/AppProtection/bin/appProtd
0x1a9000 -   0x2b7ffb +libenterpriseagent.dylib (0) <267CFD41-269F-30A2-AAD7-0C9E9200E4D3> /usr/local/McAfee/fmp/lib/libenterpriseagent.dylib
0x446000 -   0x450ff7 +libappProtPrefs.dylib (1) <2AA2DB03-E8D1-39BC-9BFA-C39D8AED7527> /usr/local/McAfee/AppProtection/lib/libappProtPrefs.dylib
0x465000 -   0x477ff3 +libboost_filesystem.dylib (0) <7B91B435-1244-3EE8-B0B8-89F273846411> /usr/local/McAfee/fmp/lib/libboost_filesystem.dylib
0x489000 -   0x48cfff +libboost_system.dylib (0) <2C2B17DD-C71C-3F79-B9D9-641413E3A44E> /usr/local/McAfee/fmp/lib/libboost_system.dylib
0x491000 -   0x497ff7 +libfmputils.dylib (0) <AEE94A85-5A65-3D35-A099-DC5FAE6096BE> /usr/local/McAfee/fmp/lib/libfmputils.dylib
0x4a0000 -   0x4a6ff3 +libPreferences.dylib (0) <B9C8A097-060F-383A-B590-0D0762D32A17> /usr/local/McAfee/fmp/lib/libPreferences.dylib
0x4b3000 -   0x4d2ff3 +libfmphelpers.dylib (0) <D437B994-E8EE-3F86-BF6A-E3F0FADD5907> /usr/local/McAfee/fmp/lib/libfmphelpers.dylib
0x4f3000 -   0x500ffb +libboost_thread.dylib (0) <45CFDE5F-22F7-300E-802F-7616409D0766> /usr/local/McAfee/fmp/lib/libboost_thread.dylib
0x517000 -   0x5cdff3 +libboost_regex.dylib (0) <66538A59-5573-32DE-AEF5-CEF9A56E2414> /usr/local/McAfee/fmp/lib/libboost_regex.dylib
0x643000 -   0x66dff7 +libboost_serialization.dylib (0) <6FF80133-A28B-39D5-BF6A-4637847BAA2D> /usr/local/McAfee/fmp/lib/libboost_serialization.dylib
0x6d5000 -   0x6f2ffb +libboost_wserialization.dylib (0) <2079F8BC-750A-3430-B18E-E940A2BE2976> /usr/local/McAfee/fmp/lib/libboost_wserialization.dylib
0x747000 -   0x803fef +libappProfileMgmt.dylib (1) <4647415B-59BD-355A-8A15-6A6F82109846> /usr/local/McAfee/AppProtection/lib/libappProfileMgmt.dylib
0x961000 -   0x965ffb +libboost_date_time.dylib (0) <BE2E474D-CC89-3E5C-A61A-934E916CCD38> /usr/local/McAfee/fmp/lib/libboost_date_time.dylib
0x970000 -   0xa75ff7 +libicuuc.48.dylib (48.1.1) <A4CCFD07-095C-3D8D-BC99-95E61F1F48EC> /usr/local/McAfee/fmp/lib/libicuuc.48.dylib
0xb1d000 -   0xc97ff7 +libicui18n.48.dylib (48.1.1) <03455BB8-8770-3CB0-89DF-FB320423F68B> /usr/local/McAfee/fmp/lib/libicui18n.48.dylib
0xdcc000 - 0x1f39fff +libicudata.48.1.1.dylib (48.1.1) <58656AAF-9EB3-329D-8153-3BF48F90786E> /usr/local/McAfee/fmp/lib/libicudata.48.1.1.dylib
0x8fe6d000 - 0x8fe9f417 dyld (239.4) <2E655535-479B-3E48-ADD3-6278819CA38A> /usr/lib/dyld
0x90008000 - 0x901ceffb libicucore.A.dylib (511.31) <9C25D145-E785-357B-9833-1980A1A738C9> /usr/lib/libicucore.A.dylib
0x92a8f000 - 0x92accff7 libauto.dylib (185.5) <CD008E66-4A0C-35F5-8D72-80D76A716A03> /usr/lib/libauto.dylib
0x92b40000 - 0x92b40fff libkeymgr.dylib (28) <1B097DEA-011E-3B1C-86D5-6C7FAD5C765A> /usr/lib/system/libkeymgr.dylib
0x92cc0000 - 0x92cc4ff7 libmacho.dylib (845) <D8E93E59-1F80-3413-B9CF-78B848F6E873> /usr/lib/system/libmacho.dylib
0x92d69000 - 0x92d7bfff libsystem_asl.dylib (217.1.4) <51EB17C9-9F5B-39F3-B6CD-8EF238B05B89> /usr/lib/system/libsystem_asl.dylib
0x932d7000 - 0x932dcff6 libcompiler_rt.dylib (35) <9924DF2E-D80B-3A21-920D-544A4597203F> /usr/lib/system/libcompiler_rt.dylib
0x932e8000 - 0x932eafff libquarantine.dylib (71) <EE3B510E-1AEC-3171-8A1A-D6A5A42CF35C> /usr/lib/system/libquarantine.dylib
0x932eb000 - 0x93303ffd libdispatch.dylib (339.90.1) <871AC354-D1B6-3475-889E-AF594448CF43> /usr/lib/system/libdispatch.dylib
0x93371000 - 0x93379fff liblaunch.dylib (842.90.1) <B259692D-D60B-3BCE-9E03-32F457CB5046> /usr/lib/system/liblaunch.dylib
0x935ef000 - 0x9360cff4 libsystem_kernel.dylib (2422.90.20) <C823B3BD-F818-3D7A-9FB7-9BDE00E2BEA1> /usr/lib/system/libsystem_kernel.dylib
0x938cc000 - 0x938d5fff libsystem_notify.dylib (121) <623269F5-1518-3035-A916-8AF83C972154> /usr/lib/system/libsystem_notify.dylib
0x93eba000 - 0x93f0aff7 libcorecrypto.dylib (161.1) <135FD99E-2211-3DF4-825C-C9F816107F0C> /usr/lib/system/libcorecrypto.dylib
0x93fa3000 - 0x93fbbff7 libsystem_malloc.dylib (23.10.1) <CB52555E-0F5B-31E3-A42A-FD4F930E2192> /usr/lib/system/libsystem_malloc.dylib
0x940c1000 - 0x940c8ffb libsystem_pthread.dylib (53.1.4) <8B1B7B84-1B5D-32A8-AC0D-1E689E5C8A4C> /usr/lib/system/libsystem_pthread.dylib
0x941b0000 - 0x94201ff1 libstdc++.6.dylib (60) <354F284B-2343-3810-9CA2-E28038824F6E> /usr/lib/libstdc++.6.dylib
0x942f3000 - 0x942f8ff3 libsystem_platform.dylib (24.90.1) <0613F163-9A7A-3908-B30B-AC1627503933> /usr/lib/system/libsystem_platform.dylib
0x946b6000 - 0x94748ff9 libsystem_c.dylib (997.90.3) <80D21D3D-1031-314C-B1F0-0B35B977CEFB> /usr/lib/system/libsystem_c.dylib
0x948c8000 - 0x948c9fff libDiagnosticMessagesClient.dylib (100) <B936B1D4-90BB-395D-8EA9-E1237608E7D0> /usr/lib/libDiagnosticMessagesClient.dylib
0x94e14000 - 0x94e15fff libSystem.B.dylib (1197.1.1) <E06132B8-2FD8-322D-A151-C9474B36B561> /usr/lib/libSystem.B.dylib
0x95541000 - 0x9556cff7 libsystem_network.dylib (241.3) <71EBA489-386D-3608-ADE6-CB50EBD1AB1B> /usr/lib/system/libsystem_network.dylib
0x9556d000 - 0x9556effa libsystem_sandbox.dylib (278.11) <E8BE1DF7-2F3D-3202-B807-A85C99220AB6> /usr/lib/system/libsystem_sandbox.dylib
0x955cc000 - 0x955f0ff3 libc++abi.dylib (49.1) <43A04ACF-97A5-35ED-B454-6B5C0CF0F99D> /usr/lib/libc++abi.dylib
0x95635000 - 0x95636ffd libunc.dylib (28) <22A126A1-DCFB-3BE5-A66B-C973F0A5D839> /usr/lib/system/libunc.dylib
0x957be000 - 0x95813fff libc++.1.dylib (120) <10C0A136-64F9-3CC2-9420-013247032120> /usr/lib/libc++.1.dylib
0x96b0b000 - 0x96b0dfff libsystem_configuration.dylib (596.13) <57095AFE-3FF1-3F42-A43E-ED679409B827> /usr/lib/system/libsystem_configuration.dylib
0x96e5d000 - 0x96e65fff libcopyfile.dylib (103) <1B1484BD-08B6-3BA9-94CA-A7C24B610EB3> /usr/lib/system/libcopyfile.dylib
0x96e66000 - 0x96e74ff7 libz.1.dylib (53) <858B4D9F-D87E-3D81-B07A-DF9632BD185F> /usr/lib/libz.1.dylib
0x97510000 - 0x97516ffb libunwind.dylib (35.3) <099D1A6F-A1F0-3D05-BF1C-0A7BB32D39C2> /usr/lib/system/libunwind.dylib
0x97a35000 - 0x97a40ffb libcommonCrypto.dylib (60049) <F8E60C43-22EE-3E0B-9546-3365056901F1> /usr/lib/system/libcommonCrypto.dylib
0x98ccc000 - 0x98cfdffa libsystem_m.dylib (3047.16) <28E614E8-7802-3E84-960A-AD4721EF10F7> /usr/lib/system/libsystem_m.dylib
0x9a27e000 - 0x9a36aff7 libxml2.2.dylib (26) <32040145-6FD6-3AD2-B98B-39F73BF9AC47> /usr/lib/libxml2.2.dylib
0x9a481000 - 0x9a485ffa libcache.dylib (62) <9730D7F2-D226-3F30-8D26-BF598CB781F6> /usr/lib/system/libcache.dylib
0x9a486000 - 0x9a489ff7 libdyld.dylib (239.4) <F4604F64-945B-3871-8F26-E9C55488BC27> /usr/lib/system/libdyld.dylib
0x9a90c000 - 0x9a914fff libsystem_dnssd.dylib (522.90.2) <A73663C9-CE65-3FF3-B41B-686728BBFB00> /usr/lib/system/libsystem_dnssd.dylib
0x9a91f000 - 0x9a943ff7 libxpc.dylib (300.90.2) <5ACBBE2C-74EB-3E88-BCBF-C573095318A5> /usr/lib/system/libxpc.dylib
0x9a944000 - 0x9aa34ffb libiconv.2.dylib (41) <848FEBA7-2E3E-3ECB-BD59-007F32468787> /usr/lib/libiconv.2.dylib
0x9ab8e000 - 0x9aca0ffc libsqlite3.dylib (158) <B3DB0FED-FE4C-314D-8329-CF7708C8AAF4> /usr/lib/libsqlite3.dylib
0x9ad8d000 - 0x9ad8efff libsystem_blocks.dylib (63) <2AC67D5E-ECD4-3644-A53C-9684F9B7AA33> /usr/lib/system/libsystem_blocks.dylib
0x9b789000 - 0x9b98bfff com.apple.CoreFoundation (6.9 - 855.14) <756998B3-F507-3474-AFB2-769FC9CE5263> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x9ba93000 - 0x9bc3b4af libobjc.A.dylib (551.1) <31CBE178-E972-30D1-ADC6-4B8345CAE326> /usr/lib/libobjc.A.dylib
0x9bd2a000 - 0x9bd52fff libsystem_info.dylib (449.1.3) <BB68E8CC-422F-3121-8C86-D0F766FB696D> /usr/lib/system/libsystem_info.dylib
0x9bd91000 - 0x9bd92fff libremovefile.dylib (33) <ED35EA79-EB06-3B84-A6D4-B1A9D6B8648D> /usr/lib/system/libremovefile.dylib
External Modification Summary:
Calls made by other processes targeting this process:
    task_for_pid: 8
    thread_create: 0
    thread_set_state: 0
Calls made by this process:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0
Calls made by all processes on this machine:
    task_for_pid: 2150
    thread_create: 0
    thread_set_state: 0
VM Region Summary:
ReadOnly portion of Libraries: Total=85.5M resident=28.2M(33%) swapped_out_or_unallocated=57.2M(67%)
Writable regions: Total=87.7M written=856K(1%) resident=1248K(1%) swapped_out=0K(0%) unallocated=86.5M(99%)
REGION TYPE                      VIRTUAL
===========                      =======
Kernel Alloc Once                     4K
MALLOC                             74.2M
MALLOC (admin)                       32K
Stack                              69.2M
VM_ALLOCATE                         612K
__DATA                              944K
__LINKEDIT                         49.8M
__OBJC                               60K
__PAGEZERO                            4K
__TEXT                             35.7M
__UNICODE                           544K
mapped file                       206.3M
shared memory                         4K
===========                      =======
TOTAL                             437.3M
System Profile:
Model: MacBookPro10,1, BootROM MBP101.00EE.B03, 4 processors, Intel Core i7, 2.7 GHz, 16 GB, SMC 2.3f36
Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In, 1024 MB
Graphics: NVIDIA GeForce GT 650M, NVIDIA GeForce GT 650M, PCIe, 1024 MB
Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D5434314753364D465238432D50422020
Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D5434314753364D465238432D50422020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xEF), Broadcom BCM43xx 1.0 (5.106.98.100.22)
Bluetooth: Version 4.2.3f10 13477, 3 services, 15 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
Serial ATA Device: APPLE SSD SM768E, 751.28 GB
USB Device: Hub
USB Device: FaceTime HD Camera (Built-in)
USB Device: Hub
USB Device: Hub
USB Device: Apple Internal Keyboard / Trackpad
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
Thunderbolt Bus: MacBook Pro, Apple Inc., 23.4
Message was edited by: amhest

Macbook Pro -- sleep and wakeup problems

If I fold the screen down when leaving my Macbook pro 8,1 (ML 8.1) and then open it again within a few minutes, it will not "wake up". If I continuously open and close it, the small LED on the front goes bright when I close it and dim when I open it. If I leave it closed for several minutes, it will usually wake up on opening, but not always. This particular Mac did the same thing under 10.7 and 10.6. I've heard of the same problem from others, and I have the same problem on a Macbook 2,1, although it is less frequent on that sysem. This does not happen on my iMac or Mini.
Sleep also did not work properly on a G5 from 2005, and I was told by Apple technicians at the time that Apple "broke" sleep around then, and never got it working properly again.
So I'm not expecting a fix, but has anyone found a reliable workaround, other than leaving the system in "sleep" mode for several minutes?

In regards to the trackpsd, read this Apple support article:
https://support.apple.com/en-us/HT203171
Open up the MBP and inspect the battery. It resides under the trackpad and if it has expanded, it will interfere with the trackpad,, If that is the case, replace the battery.
Also a very thorough cleaning of the trackpad will restore functionality.
In regards to the other issue, I suggest a reinstall of the OSX.
Ciao.

TS1248 When my MacBook Pro sleeps, after it wakes the trackpad movement (mouse) reveals the sign-in screen in little squares.

After my MacBook Pro wakes from sleep, the trackpad movement (mouse) reveals the sign-in screen in little squares.

Hello there, peijinc.
I understand your MacBook Pro seems to be taking longer than expected when coming back from sleep. It sounds like you may be seeing the Mavericks feature called Safe Sleep. The following Knowledge Base article offers up an explanation of how that feature works:
OS X: Saving energy with Sleep
http://support.apple.com/kb/HT5963
If you feel that this period of time is greater than normal, this article offers some practical steps to troubleshoot your Mac:
OS X: When your Mac doesn't sleep or wake
http://support.apple.com/kb/TS5357
Although the entire article offers relevant steps, this section may prove most useful:
If the steps above do not resolve your sleep-related issue, try these additional recommendations.
Reset SMC
Reset NVRAM/PRAM
Test with external devices disconnected
Try Safe Mode
Try another user account
Thanks for reaching out to Apple Support Communities.
Cheers,
Pedro.

Macbook pro fan issue

Hello there, I have a 2009 Macbook Pro, which apart from this issue is still running as strong as ever.
I've had this issue for awhile, but for whatever reason have only sought to finally fix it now...
Whenever I finish using the Macbook, I usually just gently close it, I don't turn it off or swich it to sleep or whatever.
The issue is that when I open it again, if at least a few minutes have passed, 9/10 of the time it ROARS to life for 1 or 2 seconds and the fans run full blast and then shut right off again. Its not a huge problem but that volume and speed they run at for that couple seconds is alarming.
Obviously it hasn't always done this, but it's had this happening for off an on a year probably.
Is this normal with an older macbook? Should I start hitting sleep before closing it? Or possible a issue with the CPU or fans?
Also, I used to use SMC fan control for gaming sometimes but I haven't had it installed for ages, if that helps.
Any help is appreciated, thanks!

"Is this normal with an older macbook? "
No.
"Should I start hitting sleep before closing it? "
Shouldn't be necessary
"Or possible a issue with the CPU or fans?"
See below, first.
"Also, I used to use SMC fan control for gaming sometimes but I haven't had it installed for ages, if that helps."
Reset the SMC:
Resetting the System Management Controller (SMC) - Support - Apple

MacBook Pro Sleep issues

Similar Messages

Maybe you are looking for