Late 2011 Macbook Pro Restarts When Power Connected

I have a late 2011 Macbook Pro, 2.2 GHz with 8GB Ram with  OS X 10.8.2 and a series of unfortunate events.
When I connect the magsafe adapter to the computer, after it has been shut down completely overnight, with the lid closed, the Macbook attempts to restart. The restart fails beause the lid is closed but leaves my Macbook in an unstable state. Unless I do a PRAM reset whenever this happens, I will have at least one random shutdown, usually within the first  half hour of use after the computer restarts itself. I have also reset the SMC controller, checked the hard drive for errors and tested the memory. I have been careful to make sure that the computer shuts all of the way down before closing the lid and disconnecting power. As far as I can tell at this point, starting the computer on battery, and subsequently connecting the magsafe adapter, does not cause any problems.
I never saw this behavior until I installed Mountain Lion.

Run an Apple hardware test and see if that picks up any problems.  If this phenomenon is consistently repeatable, I recommend taking it to a repair facility for a diagnosis.  This clearly is not normal operation.  I hope that you might be still in the warrantee period.
Ciao.

Similar Messages

  • I have a late 2011 macbook pro i want to reinstall os lion 10.7 so when i reboot hold down options key click on recovery hd then in the os x utilities screen it says reinstall mac os x is there any way i can save this download so i can burn to dvd

    i have a late 2011 macbook pro i want to reinstall os lion 10.7 so when i reboot hold down options key click on recovery hd then in the os x utilities screen it says reinstall mac os x is there any way i can save this download so i can burn to dvd

    steve359 wrote:
    Sorry ... I read but was unfortunately distracted from your original post.  You have a system that came with Lion.  The Lion that is on your system is only for your computer and cannot be downloaded from the app store again because you never purchased it officially through the App Store.
    Try this for making an external USB/DVD copy of Recovery on an external disk.  internet is still required for reinstall, though, I believe: http://support.apple.com/kb/HT4848.  But at least you have a separate Recovery Partition if you ever need a fully new and empty internal disk.
    Your assumption is incorrect. Although he may not be able to download it from the App store he can download it directly for the Apple servers using the recovery partition on his original drive.
    All you have to do is start the install routine and then point the install to an external hard drive. Once the download is finished the computer will reboot to start the install. At that reboot disconnect the external drive so the install can not start. Boot the computer back into the OS on the internal hard drive, which is what will happen automatically once the external drive is disconnected. Then connect the external and copy the files from it that were downloaded. Right click on that downloaded package file and select Show contents. In the contents of that package is a file called InstallESD.DMG. Copy that file out of the package and burn it down to a DVD or USB thumb drive and you now have the Full Lion Installer. I have several of them laying around on different hard drives and 2 USB thumb drives which I have used to reinstall Lion on my 15" MBP.
    Sorry OP I should of just typed this out in my first post.

  • I have a late 2011 macbook pro and it wont update the firmware to 2.7, it downloads the update then says its installing it but when i go back to software update it keeps coming up saying it needs to be updated

    I have a late 2011 macbook pro running OSX Lion, and it wont update the firmware to 2.7, it downloads the update then says its installing it but when i go back to software update it keeps coming up saying it needs to be updated. Im wondering what can i do to stop this or get it to update.

    Once it is downloaded you need to restart the computer if it does not restart automatically. When it next starts up you should note a progress bar appearing below the Apple logo. When done the computer will restart once more. The new firmware should now be installed.

  • Having problems connecting a late 2011 Macbook Pro 2.2ghz i7 to a Sony KDL-32L5000 using a display miniport to DVI adapter (DVI to VGA cord). The TV is not detecting the macbook. Anyone have this problem?

    Having problems connecting a late 2011 Macbook Pro 2.2ghz i7 to a Sony KDL-32L5000 using a display miniport to DVI adapter (DVI to VGA cord). The TV is not detecting the macbook. Anyone have this problem?

    You really have to mess with the resoluton, espescially the refresh rate, as it varies from projector to projector, monitor to monitor. Even within the same brand! Because so many manufacturers are trying so many different things to become the next cool kid on the block, and the way the formats are being configured that's now part of the game.
    That's why so many professionally produced corporate shows hire a dedicated projectionist for the video presentations. Too many bugs in the honey.
    Refresh & sesolution are the first things to look at.
    Just so you know that colors in PowerPoint PC, and PowerPoint Mac, don't exactly match... go figure.
    I forgot to mention another thing, sometimes it's the projector that needs to be tweaked.

  • No Power Nap option Late 2011 MacBook Pro

    Here is what the specs for Power Nap say:
    Power Nap
    Supports MacBook Air (Mid 2011 or newer), MacBook Pro with Retina display.
    Does that mean that Power Nap is not supported with my Late 2011 MacBook Pro?

    reveusetoujours wrote:
    I was reading that it is because one of the requirements is flash storage, , so I don't think it will be coming in an update. I have a Feb 12 MBP and probaly won't get the upgrade either.
    I had read that too. Fortunately, I meet that requirement. I have one of those expensive Apple SSD's. So that was not my problem. Sadly, I just don't have the right hardware for this feature.

  • HT204032 Late 2011 MacBook Pro Power Nap

    I have a late 2011 MacBook Pro with a SSD from factory. Is there a way for me to have the power nap feature? I have tried the new firmware for the retina MBP but will not work. Theoretically there is no reason it can't work on the device I have 8gb RAM and a 256GB Solid State Drive.

    Power Nap requires a Mac notebook with built-in flash storage. May require a firmware update.

  • Late 2011 MacBook Pro stuck at spinning wheel of death after a Thunderbolt issue, HD erasing and fresh Lion install from Recovery HD. Please help me!!!

    So, I think the title says it all, but to give you a little more info:
    I connected my late 2011 MacBook Pro to my TV using a Thunderbolt HDMI adapter, and closed the lid. When I opened it, it wouldn't show the login screen, so I restarted using power button. Got stuck at the Apple logo with the spinning wheel. So I booted the Recovery HD and found out it was a HD problem, so I (reluctantly) erased the HD and installed Lion from scratch. When it rebooted (after DOWNLOADING the Lion components) I got some terminal commands (sorry for not being more specific, still a noob when it comes to Mac) and then the screen faded and a message appeared saying I needed to reboot the computer. So I did. 3 effing times. Then I got stuck AGAIN at the spinning wheel, and I'm currently with that on my screen. I'm trying the forums before calling Apple (my computer's still within the 90 days of warranty) because it's not yet 9 A.M. where I live

    can you go back to recovery mode then open disk utility.
    in disk utility, higlight the disk, the one saying the brand and size then click on repair disk under first aid tab
    if it repairs fine, that's okay
    if repair was not successful, go to partition and change current to 1 partition then apply
    install lion again
    hope this helps

  • Late 2011 Macbook Pro with SSD Freezing

    Hello,
    I have a late 2011 macbook pro and about six or so months ago I have it a new lease on live with a Samsung 840 SSD (non pro).
    I haven't really had any problems with that until recently - the machine started locking up on wakeup. This meant that the beachball of doom would start and each program would gradually in turn become unresponsive. Shutdown command wouldn't work and would time out, force quit wouldn't open, and although I could move the mouse around and sometimes switch between programs, they didn't work and the only cure was to hold the power button until it switched off.
    This has also started happening just when the computer has been on for a certain amount of time *without sleeping*. For example, if I watch an episode of a tv show, by the end of it the video is still running but all of the other programs are locked up - clicking out of VLC causes the beachball of doom. This also happens in other programs - it's even happened as I've been writing this, and the only remedy seems to be a hard restart.
    The problem doesn't seem to occur in windows. In OSX I have 'put hard drives to sleep' turned off, and TRIM enabled. I also disables the sudden movement sensor. I have also reset the SMC.
    Does anyone know of a remedy short of a full reinstall of Mountain Lion?
    Oh and I used samsung magician in windows to update the firmware of the drive. It reports that the drive should be fine.
    Thanks very much for any help anyone can give me with this!

    anything is possible - corrupt files - corrupt drivers - it could be anything.
    try doing a nvram/pram reset and see if that sorts it out.
    i have ssd installed in all my Macbook/Macbook Pro and have never had any issues.
    Then again, I don't have windows installed in any of them.
    hopefully the nvram/pram reset sorts it out for you.
    once you've done that reset - go back to system preferences - startup disk and select your ssd as the startup drive again - then restart it again.

  • Late 2011 MacBook Pro (Mountain Lion 10.8.2) backlight keyboard not functioning properly?

         I have a late 2011 MacBook Pro running OS X Mountain Lion 10.8.2 and for some reason, the automatic backlight keyboard will not funtion as it should. When I have the "Adjust keyboard brightness in low light" option enabled in settings, and I turn on the lights, my backlight keyboard stays at full brightness. Then, when I turn off the keyboard, then the lights, the keyboard does not turn on! Correct me if I'm wrong, but I am pretty sure that this was a feature in the MBP lines.

    Try a SMC reset.   Shut down the computer. Plug in the MagSafe power adapter to a power source, connecting it to the Mac if its not already connected. On the built-in keyboard, press the (left side) Shift-Control-Option keys and the power button at the same time. Release all the keys and the power button at the same time. Press the power button to turn on the computer.   Note: The LED on the MagSafe power adapter may change states or temporarily turn off when you reset the SMC.

  • 13-inch, Late 2011 Macbook Pro and Thunderbold Display...

    Hello Dear Users,
    First I wish you have a nice new year with full of health, happiness and wealth, then i am asking my question:
    I am using a 13-inch, Late 2011 MacBook Pro having
    Processor  2,8 GHz Intel Core i7 2 cores+2 HTs
    Memory  16 GB 1333 MHz DDR3
    Graphics  Intel HD Graphics 3000 512 MB
    Software  OS X 10.9.1 (13B42)
    specifications, setup with double Thunderbold Displays.
    I sometimes feel that mac's display performance is marvelous and sometimes I feel like I am looking at an old school, blury screen. Is there anybody feels like I feel. I have doubts about screen performance. Well I searched on internet before to write but I could not express what I feel on google search for example. So, I am writing here what I feel. Sorry for my English if I could not express what I meant.
    Thak you, and have a nice new year.....
    Levent

    I've been having the exact same issue, same monitor and same laptop.  I spoke to a couple Apple techs on the phone and took my mbp to a genius bar last night, thinking it might be a video card issue since the blocks were also showing up on my macbook's screen. It of course failed to replicate at the store, even with a TB display hooked up.
    After this I finally realized it was an issue with the monitor and not the laptop, since it only happened when they were connected (duh... I never checked with them disconnected)
    I was able to make it go away temporarily by pushing the cables on the back of the display firmly in, but a few hours later I noticed a couple blocks popping up again.. however it wasn't as bad as before.  Seems to me it must be some issue with the hardwired power/tb connetor.

  • What external drives work well with a late 2011 MacBook Pro?  I ask because I just found out the hard way that a Samsung EVO 840 does not.  Also should I avail myself of something that works with Thunderbolt or Firewire?

    What external drives work well with a late 2011 MacBook Pro (I7, Lion OS) apart from my Kingston flash and USB drive, and the SD drives that I use in my cameras and recording devices?  I ask because I just found out the hard way that a Samsung EVO 840 does not.  Also, should I avail myself of something that works with the Thunderbolt or Firewire connections?  I'm looking to back up music and video files created and/or processed in Logic Pro and the Adobe Production Premium software suite (Premier Pro, After Effects, Audition, etc).

    Hmm, not sure what problems you had installing this drive. The review here gives it good marks for Mac:
    http://www.amazon.com/Samsung-Electronics-EVO-Series-2-5-Inch-MZ-7TE1T0BW/produc t-reviews/B00E3W16OU
    There does seem to be a lot of prep to make it work:
    "1. Preparation to install your new shiny SSD
    1.a You will need a migration tool (I used the Sabrent kit USB 3.0 to Sata that was suggested in these review) see link http://www.amazon.com/gp/product/B00DQJME7Y/ref=oh_details_o03_s01_i01?ie=UTF8&p sc=1
    1.b You will need to download a trim enabler (mid 2012 macbooks only support native trim with apple brand ssd's) I recommend going to cindori.org and downloading trim enabler version 3.xx. You can do this step before or after the OS migration
    1.c You cannot use the Samsung SSD migration software *don't worry Mac has its own imaging/migration utility*"
    Also in those reviews:
    " Only down side when using this product in a Mac Mini is you will be required to download and install Trim Enabler so that your drive performs optimally on your Mac device. This is an Apple issue, not Samsung, but it is an extra step you will have to take after you install the hard drive, and any time you perform an OS upgrade." He rant's on.
    Personally I only deal with OWC:
    http://eshop.macsales.com/shop/SSD/OWC/
    They are very knowledgable and if there's a problem they will gladly take back the item. (Never happened to me yet - 8 years and counting).
    Just upgraded my 13" MBP 2011 to 120 GB for $79. Adobe CS 6 opens in 3 seconds! Awesome!
    When I was in Chicago I had a pro photographer for a client. She wound up with 4 internal drives in her Pro, 4 external drives and an dual array locked in a steel vault in the basement. All from OWC. OK she was a bit paranoid. Great client though.
    As far as value for price:
    http://eshop.macsales.com/item/OWC/MES3FH7500G/
    500 GB for $130.
    However as far as reliability is concerned:
    http://www.rockpapershotgun.com/2014/01/30/are-ssds-reliable/
    http://www.extremetech.com/computing/173887-ssd-stress-testing-finds-intel-might -be-the-only-reliable-drive-manufacturer
    So sudden power loss is an issue with SSDs.
    Personally I'd go with a moderate sized SSD internally and a conventional external for backup. An array would be the most reliable.

  • Hi i cannot change the brightness on my late 2011 macbook pro.

    Hi i cannot change the brightness on my late 2011 macbook pro. It is stuck on the lowest level in which i can't view the screen without a flash light. Please i need help how to solve this. I was on my computer when i checked the back which it was really dusty, i tried unscrewing the bottom however some screws were too tight so i took it upon myself and got a rod and startedremoving the dust off the vents and i may have clicked something as i closed the lid on the macbook i could hear the sounds still from the film but the lid was closed as i opened it back up the brightness was on low but sounds were still playing. All the buttons work , all of the F keys, apart from the brightnes keys. I can shine a tourch on the screen and see the display but the brightness will not change but i can see when i click the brightness it says it changes. I have connected it to a spare tv i have via hdmi and i really need help as this is my primary computer and i need it for work when going away. Thank you

    Try SMC and PRAM resets:
    http://support.apple.com/kb/ht3964
    http://support.apple.com/kb/ht1379
    Ciao.

  • OS 10.7.5 pinwheels Late 2011 Macbook Pro

    I am using a late 2011 MacBook Pro and I am getting recurrent pinwheels no matter what I do. Even booting into safe mode, I get them but it usually takes a little while of normal use until they happen. At first I thought it was Chrome, but after I started using Safari the behavior continued. In the console, this sometimes happens right before the pinwheels start:
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TC0H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TC1D kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TCAH kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TCBH kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TA0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TH0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TO0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TH1P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TH2P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TH3P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR Th0H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TG0H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TG1H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR Tp1C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR Tp0C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TB3T kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TN0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TN1P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TN0H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM1S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM2S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM3S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM4S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM5S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM6S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM7S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM8S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM9S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TMAS kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TMCS kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TMDS kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TMES kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TMFS kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM1P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM2P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM3P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM4P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM5P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM6P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM7P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM8P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM9P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TMAP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TMBP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TMCP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TMDP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TMEP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TMFP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TS0C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR Tp0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TA0S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TA1S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TA2S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TA3S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TA1P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR Tp1P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR Tp2P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR Tp3P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR Tp4P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR Tp5P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TC0H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TC1D kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TCAH kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TCBH kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TA0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TH0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TO0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TH1P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TH2P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TH3P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR Th0H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TG0H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TG1H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR Tp1C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR Tp0C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TB3T kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TN0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TN1P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TN0H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM1S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM2S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM3S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM4S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM5S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM6S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM7S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM8S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM9S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TMAS kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TMCS kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TMDS kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TMES kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TMFS kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM1P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM2P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM3P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM4P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM5P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM6P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM7P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM8P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TM9P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TMAP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TMBP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TMCP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TMDP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TMEP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TMFP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TS0C kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR Tp0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TA0S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TA1S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TA2S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TA3S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR TA1P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR Tp1P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR Tp2P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR Tp3P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR Tp4P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:37:48.000 PM kernel: SMC::smcReadKeyAction ERROR Tp5P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff800b49e000
    1/10/13 5:38:16.000 PM kernel: IOSurface: buffer allocation size is zero

    I remove the istat widget and the excessive fan speeds ceased. However, the machine will still become unresponsive and begin pinwheeling after a random amount of time, never less than 10 minutes. I have run hardware tests and there does not appear to be anything wrong with the logic board or the RAM. I do have an SSD installed but over one-third of the drive is free space.
    I have had the activity monitor open when this happens, but I cannot tell what process(es) are using the system resources because it becomes unresponsive too. I have tried updating to Mountain Lion, but I can't get it downloaded in full before the machine pinwheels again. I tried doing a Lion Internet Recovery, but I only got 10-15% done before it errored out and told me that it couldn't finish the download. After that, I could attempt to restart the installation, but then it did not see the SSD at all. I no longer have the original HDD to test the unit, but it appears that the SSD is the problem. I am looking for help in any other areas before I install a new piece of hardware.

  • HT201295 Late 2011 Macbook Pro refuses to boot. SMC reset doesn't work

    Late 2011 Macbook Pro refuses to boot. SMC reset does nothing. Have tried bypassing SMC (nothing).
    Magsafe light glows very very faintly (barely visible in a room with lights on).
    Have tried reseating the battery connector. Battery indicator status button illuminates no LEDS (despite it being charged before failing).
    The mac didn't get wet. Was using a non apple USB cable at the time to tether/charge iphone. Computer just dead after working fine.
    Any ideas anyone. Logic board?
    Many thanks and best wishes
    Jamie

    Is it a 15" or 17" MBP? There have been logic board issues with that model.
    https://www.ifixit.com/Device/MacBook_Pro
    For all models.
    If it's a 13" take the bottom off and disconnect the battery:
    https://www.ifixit.com/Guide/MacBook+Pro+13-Inch+Unibody+Late+2011+Battery+Repla cement/7649
    So only do this through step #3!
    Wait 10 seconds. Push the power button for 5 seconds. Wait 10 seconds. Reconnect the battery. Put the bottom back on don't screw it on just yet. Tape it temporarily in place and try to start it
    Even if it's a 15" or 17" try this anyway.  Usually when graphics on the logic board fails there will have been anomalies beforehand.

  • Windows 7 install on late 2011 MacBook Pro without bootcamp (performance issues)

    Hey guys I'm hoping I can get this issue resolved. I have purchased a late 2011 MacBook Pro (radeon 6750m 1gig). I installed a fresh copy of windows 7 without bootcamp. Having real issues with game performance like world of Warcraft. I have done this with an older unibody Mac and it ran great (for any non believer)... But now this time around I'm getting horrible fps in game. I'm thinking it may be driver related it buy I am having trouble finding the right drivers to see if that's then issue. Any help on this would be greatly appreciated.

    Shotgun00 wrote:
    That is completely false. There is no real need to leave OS X on the Mac if you don't want to, especially with Win 7 or 8. That may of been true with Windows XP but not anymore.
    The problem with leaving OS X installed is then you are really limited with what you can do with the drive. You can only have one Windows partition and if you fool with it at all Windows will no longer boot. you can't even change the OS X partition otherwise Windows would boot
    Windows 7 will install all by itself. No need for any Boot loaders or Hack Boot system. Pop the Win 7 DVD in the DVD drive and restart. Windows will be installed all by itself. But you do need the Apple support files.
    In the end if you are going to run Windows on a computer by itself then you really should not buy a Mac. The hardware is the same and as to the OPs perceived better built quality I personally do not see it. And if you actually read some of the posts on this and other Mac forums you will see that perceived build quality is just a bunch of hype, in my opinion.
    To the OP. You aren't missing anything.
    If you had carefully read what I wrote, I merely said that doing the install on a blank drive wasn't a good idea. That's because it can create issues the OP is having. A Mac's hardware is no different than a comparable Windows machine, but the EFI/BIOS/Firmware is. Macs are in something of a no-man's land in this regard, as they have neither an old-school BIOS or modern UEFI of recent Windows-based notebooks. I'm willing to bet that the performance problems the OP is having relates to the fact that a straight EFI install on a modern MBP "enables" (for lack of a better word) automatic graphic switching. The capability manifests, but the functionality is not there. Enterprising individuals have been trying to get graphic switching in Windows to work as it does on the OS X side ever since MacBooks debuted with this abliity but with zero success.
    Using Boot Camp bypasses this, as the discreet GPU is enabled full-time in Windows. Thus, you will realize proper performance.
    As far as perceived build quality, Apple machines are at the high end of the consumer notebook spectrum. They're certainly better than most of the other machines you can pick up at your local Best Buy, but they fall short of business-class machines such as the Dell Latitude/Precision, HP ProBook/EliteBook, and Lenovo ThinkPad.

Maybe you are looking for