2011 Macbook Pro tells me to restart it once i USB tether from iphone 3gs

i got a brand new macbook pro yesterday morning, and the first thing i did once i got home is transfer all of my files via the setup screen once you first turn it on. onc everything was on, i downloaded all of the updates for all the apps i had. Today, when i plugged on my iphone 3gs (4.2.1) to tether my 3g so i could use it on the road, and once i plugged it in, the top part of my phone turned blue, saying that it was tehering the internet, then itunes popped up, and then the screen went dark and the message saying i had to restart it showed up. so i unplugged my phone, fearing anything would be deleted from it, then i held down the power button and restarted it. when the white sceen and the apple logo showed, i plugged my phone back in, and on he log in screen, i tried to increase the brightness of the baclight in the keyboard, but all it showed was the lttle thing showing the level of brightess, and the a circle with a cross through it at the bottom. that was also new. then when i logged in, itunes popped up, and then my phone turned blue, showing it that it was tethering, anf the screen telling my to restart it showed up immidiatley after. i dont know what could have caused this, all i know is that it has only happened when i plug in my iphone to tether, but only by USB and not by bluetooth. help is much appreciated!

If it was a gray screen that covered your monitor telling you to shutdown in multiple languages, then you had a kernel panic. This is generally caused by a hardware problem. Since you say it happens when the iPhone is attached then there is something wrong with the iPhone or its cable.
|___________________
Allan

Similar Messages

  • Late 2011 Macbook Pro 13 inch keeps restarting

    Here's the error report.
    It happens whether I'm doing graphics or even if I'm just surfing the web.
    I get a gray screen that tells my my system needs to restart then it does and I need to log back in again.
    This started just a few days ago.
    Anonymous UUID:       F6254CD4-3EB5-D689-DC3D-1072B93D8738
    Sun Feb 16 23:49:09 2014
    panic(cpu 3 caller 0xffffff8023f63c3e): "hfs_swap_HFSPlusBTInternalNode: catalog record #16 keyLength=42 expected=4138\n"@/SourceCache/xnu/xnu-2422.1.72/bsd/hfs/hfs_endian.c:560
    Backtrace (CPU 3), Frame : Return Address
    0xffffff8150bdbd50 : 0xffffff8023c22f69
    0xffffff8150bdbdd0 : 0xffffff8023f63c3e
    0xffffff8150bdbe10 : 0xffffff8023f62c6f
    0xffffff8150bdbe60 : 0xffffff8023f57661
    0xffffff8150bdbea0 : 0xffffff8023e0697e
    0xffffff8150bdbf90 : 0xffffff8023e070ab
    0xffffff8150bdbfb0 : 0xffffff8023cd6aa7
    BSD process name corresponding to current thread: kernel_task
    Mac OS version:
    13B42
    Kernel version:
    Darwin Kernel Version 13.0.0: Thu Sep 19 22:22:27 PDT 2013; root:xnu-2422.1.72~6/RELEASE_X86_64
    Kernel UUID: 1D9369E3-D0A5-31B6-8D16-BFFBBB390393
    Kernel slide:     0x0000000023a00000
    Kernel text base: 0xffffff8023c00000
    System model name: MacBookPro8,1 (Mac-94245B3640C91C81)
    System uptime in nanoseconds: 809671690896
    last loaded kext at 283936356386: com.apple.filesystems.msdosfs          1.9 (addr 0xffffff7fa5bdf000, size 65536)
    last unloaded kext at 345378746042: com.apple.filesystems.msdosfs          1.9 (addr 0xffffff7fa5bdf000, size 57344)
    loaded kexts:
    com.rim.driver.BlackBerryUSBDriverInt          0.0.74
    com.apple.driver.AudioAUUC          1.60
    com.apple.driver.AppleHWSensor          1.9.5d0
    com.apple.driver.AGPM          100.14.11
    com.apple.filesystems.autofs          3.0
    com.apple.driver.AppleMikeyHIDDriver          124
    com.apple.driver.AppleHDA          2.5.3fc1
    com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport          4.2.0f6
    com.apple.driver.SMCMotionSensor          3.0.4d1
    com.apple.driver.AppleSMCPDRC          1.0.0
    com.apple.driver.ApplePolicyControl          3.4.12
    com.apple.driver.AppleUpstreamUserClient          3.5.13
    com.apple.driver.AppleSMCLMU          2.0.4d1
    com.apple.driver.ACPI_SMC_PlatformPlugin          1.0.0
    com.apple.driver.AppleMikeyDriver          2.5.3fc1
    com.apple.driver.AppleLPC          1.7.0
    com.apple.driver.AppleThunderboltIP          1.0.10
    com.apple.driver.AppleBacklight          170.3.5
    com.apple.driver.AppleMCCSControl          1.1.12
    com.apple.driver.AppleIntelHD3000Graphics          8.1.8
    com.apple.driver.AppleIntelSNBGraphicsFB          8.1.8
    com.apple.iokit.IOUserEthernet          1.0.0d1
    com.apple.iokit.IOBluetoothSerialManager          4.2.0f6
    com.apple.Dont_Steal_Mac_OS_X          7.0.0
    com.apple.driver.AppleHWAccess          1
    com.apple.driver.AppleUSBTCButtons          240.2
    com.apple.driver.AppleUSBTCKeyboard          240.2
    com.apple.driver.AppleIRController          325.7
    com.apple.AppleFSCompression.AppleFSCompressionTypeDataless          1.0.0d1
    com.apple.AppleFSCompression.AppleFSCompressionTypeZlib          1.0.0d1
    com.apple.BootCache          35
    com.apple.iokit.SCSITaskUserClient          3.6.0
    com.apple.driver.XsanFilter          404
    com.apple.iokit.IOAHCIBlockStorage          2.4.0
    com.apple.driver.AppleUSBHub          650.4.4
    com.apple.iokit.AppleBCM5701Ethernet          3.6.9b9
    com.apple.driver.AppleSDXC          1.4.0
    com.apple.driver.AppleFWOHCI          4.9.9
    com.apple.driver.AppleAHCIPort          2.9.5
    com.apple.driver.AppleUSBEHCI          650.4.1
    com.apple.driver.AirPort.Brcm4331          700.20.22
    com.apple.driver.AppleRTC          2.0
    com.apple.driver.AppleSmartBatteryManager          161.0.0
    com.apple.driver.AppleACPIButtons          2.0
    com.apple.driver.AppleHPET          1.8
    com.apple.driver.AppleSMBIOS          2.0
    com.apple.driver.AppleACPIEC          2.0
    com.apple.driver.AppleAPIC          1.7
    com.apple.driver.AppleIntelCPUPowerManagementClient          216.0.0
    com.apple.nke.applicationfirewall          153
    com.apple.security.quarantine          3
    com.apple.driver.AppleIntelCPUPowerManagement          216.0.0
    com.apple.AppleGraphicsDeviceControl          3.4.12
    com.apple.kext.triggers          1.0
    com.apple.driver.DspFuncLib          2.5.3fc1
    com.apple.vecLib.kext          1.0.0
    com.apple.iokit.IOAudioFamily          1.9.4fc11
    com.apple.kext.OSvKernDSPLib          1.14
    com.apple.iokit.IOBluetoothHostControllerUSBTransport          4.2.0f6
    com.apple.iokit.IOFireWireIP          2.2.5
    com.apple.driver.IOPlatformPluginLegacy          1.0.0
    com.apple.driver.AppleSMBusPCI          1.0.12d1
    com.apple.driver.IOPlatformPluginFamily          5.5.1d27
    com.apple.driver.AppleHDAController          2.5.3fc1
    com.apple.iokit.IOHDAFamily          2.5.3fc1
    com.apple.driver.AppleGraphicsControl          3.4.12
    com.apple.driver.AppleBacklightExpert          1.0.4
    com.apple.driver.AppleSMBusController          1.0.11d1
    com.apple.iokit.IONDRVSupport          2.3.6
    com.apple.iokit.IOSurface          91
    com.apple.iokit.IOGraphicsFamily          2.3.6
    com.apple.iokit.IOSerialFamily          10.0.7
    com.apple.iokit.IOBluetoothFamily          4.2.0f6
    com.apple.driver.AppleSMC          3.1.6d1
    com.apple.driver.AppleThunderboltDPInAdapter          2.5.0
    com.apple.driver.AppleThunderboltDPAdapterFamily          2.5.0
    com.apple.driver.AppleThunderboltPCIDownAdapter          1.4.0
    com.apple.driver.AppleUSBMultitouch          240.6
    com.apple.iokit.IOUSBHIDDriver          650.4.4
    com.apple.driver.AppleUSBMergeNub          650.4.0
    com.apple.iokit.IOSCSIMultimediaCommandsDevice          3.6.0
    com.apple.iokit.IOBDStorageFamily          1.7
    com.apple.iokit.IODVDStorageFamily          1.7.1
    com.apple.iokit.IOCDStorageFamily          1.7.1
    com.apple.iokit.IOAHCISerialATAPI          2.6.0
    com.apple.iokit.IOUSBUserClient          650.4.4
    com.apple.driver.AppleThunderboltNHI          1.9.2
    com.apple.iokit.IOThunderboltFamily          2.8.5
    com.apple.iokit.IOEthernetAVBController          1.0.3b3
    com.apple.driver.mDNSOffloadUserClient          1.0.1b4
    com.apple.iokit.IOFireWireFamily          4.5.5
    com.apple.iokit.IOAHCIFamily          2.6.0
    com.apple.iokit.IO80211Family          600.34
    com.apple.iokit.IONetworkingFamily          3.2
    com.apple.driver.AppleEFINVRAM          2.0
    com.apple.driver.AppleEFIRuntime          2.0
    com.apple.iokit.IOHIDFamily          2.0.0
    com.apple.iokit.IOSMBusFamily          1.1
    com.apple.security.sandbox          278.10
    com.apple.kext.AppleMatch          1.0.0d1
    com.apple.security.TMSafetyNet          7
    com.apple.driver.AppleKeyStore          2
    com.apple.driver.DiskImages          371.1
    com.apple.iokit.IOReportFamily          21
    com.apple.driver.AppleFDEKeyStore          28.30
    com.apple.iokit.IOUSBMassStorageClass          3.6.0
    com.apple.driver.AppleUSBComposite          650.4.0
    com.apple.iokit.IOSCSIBlockCommandsDevice          3.6.0
    com.apple.iokit.IOStorageFamily          1.9
    com.apple.iokit.IOSCSIArchitectureModelFamily          3.6.0
    com.apple.iokit.IOUSBFamily          650.4.4
    com.apple.driver.AppleACPIPlatform          2.0
    com.apple.iokit.IOPCIFamily          2.8
    com.apple.iokit.IOACPIFamily          1.4
    com.apple.kec.corecrypto          1.0
    com.apple.kec.pthread          1

    If you've upgraded the memory modules, reinstall the original memory and see whether there's any improvement. Be careful not to touch the gold contacts. Clean them with a mild solvent such as rubbing alcohol. Aftermarket memory must exactly match the technical specifications of the machine.

  • 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.

  • Why won't my 2011 MacBook Pro restart after Yosemite installation?

    Why won't my 2011 MacBook Pro restart after Yosemite installation?

    What symptoms are you seeing?
    At what point does it get stuck? 
    Is it failing to Restart, or failing once it restart?
    what exactly is on the screen, if anything?
    Do you get the chime? the gray Apple? The spinner? black screen? gray screen? prohibitory sign?

  • I installed the 829mb Apple software update on my 2011 Macbook Pro. Upon restart, it crashed.  Error message: Panic CPU  0 caller 0xffffff800064ba7b Unable to find driver for this platform \"acpi"\\n"@/sourcecache/xnu/xnu-1699.26.8/iokit/kernel/10platfor

    I installed the 829mb Apple software update on my 2011 Macbook Pro. Upon restart, it crashed.  It instructed me to hold power button to shut off and then press again to restart.  Same error message keeps coming up and computer won't boot to home screen.
    Error message:
    Panic CPU  0 caller 0xffffff800064ba7b Unable to find driver for this platform \"acpi"\\n"@/sourcecache/xnu/xnu-1699.26.8/iokit/kernel/10platform
    \"acpi"\\n"@/sourcecache/xnu/xnu-1699.26.8/iokit/kernel/10platformexpert.cpl:150 4
    Debugger called panic
    Kernal uuid a8ed611fb0f-3729-8392-e7a32c5e7d74
    THANKS FOR ANY HELP.
    ROBB

    Boot into Recovery by holding down the key combination command-R at the startup chime. Release the keys when you see a gray screen with a spinning dial.
    Note: You need an always-on Ethernet or Wi-Fi connection to the Internet to use Recovery. It won’t work with USB or PPPoE modems, or with networks that require any kind of authentication other than a WPA or WPA2 Personal password.
    When the Mac OS X Utilities screen appears, follow the prompts to reinstall the Mac OS. You don't need to erase the boot volume, and you won't need your backup unless something goes wrong. If your Mac didn’t ship with Lion, you’ll need the Apple ID and password you used to upgrade, so make a note of those before you begin.
    Don't install the Thunderbolt update -- it's defective.

  • 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.

  • 2011 Macbook Pro, running windows 7, two monitors?

    I have a 2011 Macbook Pro 13inch, running windows 7 with thunderbolt to dvi cable, can I use a dvi splitter to get two monitors with seperate desktops?
    I am currently using an external montior for one extra desktop, but I keep needing more room.

    jazzdude9792 wrote:
    It had beens sleeping running Windows 7 in my backpack while plugged in for a few hours, and you could literally cook an egg on it. It was that hot.
    If it was plugged in and recharging IN your backpack you probably got the battery hot. I don't know if there is an overheat auto-shut down feature for the battery.
    It may have woke Windows up to tell you it got hot and then crashed or tried to shutdown and couldn't.
    As far as the heat for the processor or ram, it does have an auto shut down for overheat situations but if it crash's and stays in limbo land then that part of it won't see it and it could damage things inside. Depending on how you had your backpack stuffed last time and this time it could just be a coincident on getting extra hot. Depending on what year MacPro you have you can either use the Hardware Test DVD that came with your computer (or press and hold the D key when it restarts) to check to see if it can find anything wrong.
    Or you may have a hardware problem that makes it wake up or restart by itself and Windows just happens to have the right combination to trigger it. If it's still under warranty you may want to have Apple look at it?
    Not to mention, if it's happened before then maybe it's time to see WHY it does it before it does do some damage?
    Try putting it to sleep and see if you can replicate the problem while at home.

  • LaCie Desktop Manager doesn't recognize LaCie RAID with my 2011 MacBook Pro

    Hello,
    I have a new MacBook Pro 17" but I am not able to use the LaCie Desktop Manager with the LaCie 4big Quadra Enterprise Class RAID. The drive is recognized by the finder via eSATA, FireWire, USB, but is not recognized by the LaCie Desktop Manager. This prevents me from encrypting the drive. The LaCie Desktop Manager could recognize the raid with my early 2008 MacBook Pro.
    I'd like to know if anyone else is having the same problem with their 2011 MacBook Pro.
    I have been communicating with LaCie support but he tells me that he can't check the same or similar configuration as mine.
    Thanks,
    Dennis

    Looks like the cable is the same if you still have the 2010.
    http://www.ifixit.com/MacBook-Parts/MacBook-Pro-15-Inch-Unibody-Mid-2009-Mid-201 0-Early-2011-SATA-SuperDrive-Cable/IF161-040

  • Screen blinking when turning on my Mid 2011 MacBook Pro after recent update.

    Just did the recent software update and my Mid 2011 MacBook Pro 13" when turning on the screen blinks until the computer is rebooted/restarted.  Have never had a problem before. Of course, my Apple Care just expired the end of June 2014. Is anyone else having a problem?

    When you have the problem, note the exact time: hour, minute, second.  
    These instructions must be carried out as an administrator. If you have only one user account, you are the 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.
    The title of the Console window should be All Messages. If it isn't, select
              SYSTEM LOG QUERIES ▹ All Messages
    from the log list on the left. If you don't see that list, select
              View ▹ Show Log List
    from the menu bar at the top of the screen.
    Each message in the log begins with the date and time when it was entered. Scroll back to the time you noted above.
    Select the messages entered from then until the end of the episode, or until they start to repeat, whichever comes first.
    Copy the messages to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
    The log contains a vast amount of information, almost all of it useless for solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.
    Please don't indiscriminately dump thousands of lines from the log into this discussion.
    Please don't post screenshots of log messages—post the text.
    Some private information, such as your name, may appear in the log. Anonymize before posting.

  • Can not shut down late 2011 MacBook Pro and turn it back on again without the hard drive disappearing?

    Ok, I have searched for months for an answer to this question to no avail, probably because no one has experienced it before. I am hoping however that you guys can help me figure this one out cause it is driving me nuts! Also, I am not entirely sure what section of the support I should put this under so if I stick it in the wrong place, I apologize.
    Right now my problem is very simple. When I turn off my laptop, and then try to turn it back on, my internal hard drive disappears... and I get the blinking folder with a question mark on it. I have figured out something interesting however. I have an install disk with Ubuntu Linux on it. If I boot into that first, then RESTART the laptop, not shut down and turn back on, it reads the internal hard drive just fine and I can boot as if there is nothing wrong.
    Second part to the problem... If I allow the laptop in either OSX or Windows to go to sleep (aka shut off the hard drive but the computer remains on), when I attempt to wake it up, I am greeted with the usual log in screen of whichever OS I am in, but is frozen and after a few seconds goes black and restarts the computer to find that... Surprise! The hard drive is gone
    I have tried every trick in the book that I can think of, but can not seem to come up with a solution to the problem... I know when the problem happened and if anyone thinks that that will help them figure this out I will type everything I did up till, including the crash that caused this, and my attempted fixes, but I have class right now so only if you guys want it I will type all that out.
    What I am currently running is:
    2011 MacBook Pro 13in screen
    4Gb of Ram
    1TB internal Hard Drive
    OSX 10.11.whatever the newest update is... just updated the other day again.
    Windows 8.1 on BootCamp 5 (yea I know its not supposed to work but it does) again, fully updated
    Ubuntu 13.10 (I think? Doesn't really matter, its just an install disk I use to boot the computer)
    If there is anything else that you guys need me to provide, I can, just simply ask. I can provide as much info as is necessary.

    Sorry it took me so long to write back, But unfortunately this didn't help my issue.
    My uncle and I did a lot of tests on this computer and have narrowed down the location of the problem a little bit.
    We tried to first reset the SMC and the NVRAM as suggested, but the only thing that did was make the fans run on full tilt for the first session after restarting it for some reason. After that we tried re installing OSX over the OSX that was already on the system (not removing any of the files). This also didn't do anything but make refit stop working. Then we moved onto the next task at hand by removing the hard drive entirely and booting it as an external drive from one of the USB ports... as long as you booted it with the options key held down, it worked perfectly fine. Then we put an alternative hard drive into the computer and installed OSX on that. This time there was no trouble booting anything up. Everything seemed to work flawlessly. So we made a backup of my original drive (OSX, Windows, and all) onto an external hard drive and tested booting to it via USB. That again worked perfectly fine and booted right up with no problems. So after that we formatted the original hard drive and reinstated OSX. We then proceeded to transfer all the old files from the backup onto this new installation and LOW AND BEHOLD..... we were back to square one with it refusing to recognize the hard drive again.
    So this basically told us that there appears to be something either wrong with the hard drive, or something got really screwed up in the software along the lines and by me copying all my old files back over, I just ended up bringing the screwed up file back over with it! (despite not copying over any settings of any kind) So I am still extremely confused as to what is going wrong... did some boot sector possibly get screwed up may be?

  • I spilled on my 2011 macbook pro, will not charge

    I spilled hot chocolate on my 2011 macbook pro, and it only got along the bottom front left edge of the computer, and not into any ports or on my charger. Charger was plugged in at the time. Computer shut off a couple of minutes after, so I restarted it,and the fan was running very loudly. \the trackpad was a little bit messed up, so I did an SMP reset and the computer is now fine. However, my charger will not work. When plugged into the laptop, it doesn't charge and the light doesn't come on, though it has no visible damage. Is the problem with the laptop or charger? Could the computer have damaged he charger at the time of the spill? Could the hot chocolate have seeped into the seam on the bottom of my computer? It was only wet for about 15 seconds.

      Normally, if electronic device suffers from the accident of liquid spill, you should shut down them and plug off power supply immediately to avoid possible electricity broken. In fact, it is not easy to detect visible damage by visual look. In regard to your example, i mean hot chocolate actually penetratres electronic component inside your computer and cause the fault for hardware system. What you need to do is remove the computer case and try to dry internal electrical circuit out. If this method doesn't work, you should bring to repair service. Good luck ! 

  • My 2011 Macbook Pro OSX 10.8.4 latest update won't connect to secured Wi-fi

    2011 Macbook Pro
    OSX 10.8.4 latest updates
    Suddenly stopped connecting to any wireless network which is secured, WEP/WPA/WPA2/personal/enterprise all do NOT work.
    Connects to unsecured networks just fine.
    For example, our wireless password is:
    123456890!
    I tried with WPA2, no luck.
    Tried with WPA2 and pw 1234567890, no luck.
    Tried with WPA and pw 1234567890!, no luck.
    Tried with WPA and pw 1234567890, no luck.
    Tried WEP with 1234567890, no luck.
    Tried with NO SECURITY on this wi-fi network, connected right away.
    -I did reset PRAM, no luck.
    -I deleted from Keychain, no luck.
    -I added as prefered network and removed, no luck.
    -I added new network location, no luck.
    -I removed the Wi-fi network adapter, rebooted, activated, no luck.
    -In the mac console logs, all I see are "wlEvent: en1 en1 link DOWN" when I try to connect to my secured wireless network (home or my office or even at a neighbors).
    -Wireless diagnostics tell me nothing
    -Console logs do not tell me anything
    -Warranty is expired and no AppleCare
    Seems like a bug to me, even though I have tried with a Netgear, Cisco/Linksys, D-Link router and even tried tethering to a Samsung Galaxy Note 2 and iPhone 5, all same problem, says "Connection failed."
    APPLE FRIENDS HELP ME PLEASE!

    For example, our wireless password is: 123456890!
    Well a password that weak will get cracked in about 6 hours on just about any PC in the area.
    Now: LKUY*&T&67NH(*JKÎM<PijriuÎÓyhm8t, that's a real good network password, even a huge botnet would have trouble cracking that. I know because my router was PING flooded by the Flashback botnet and survived.
    After OS X is reinstalled over itself to fix it, you might have to do more as it could be a "in user account" issue with a corrupted preference file, bad users permissions or another cause that's not OS X
    ..Step by Step to fix your Mac

  • Early 2011 MacBook Pro- The thermal paste discussion.

    It is my goal to clear up the questions and concerns Apple customers have been having regarding heat or fan related concerns with Early 2011 MacBook Pros. If your MacBook Pro was produced within the last few months the thermal issue has been resolved and it will likely not be in issue for you. If you are still wondering if your computer is effected or what the real issue is keep reading.
    The MacBook Cools itself by 2 main methods: active and passive. The active cooling is via a fan that blows air through a heatsync and into a tube called a heat pipe which leads to the back of the computer where the hot air is discharged through a vent at the bottom of the screen behind the hinge. The fan lowers the air pressure inside the case causing outside air is drawn in the case, displacing the hot air inside and helping to cool the other components.
    The computer uses passive cooling to remove the residual heat from the processor which comes mostly in the form of radiant heat. Passive cooling is also used to cool the other components of the computer (memory, disk drives, battery etc). Passive cooling works by conductive heat transfer ie. syncing to the case of the computer. Some of the heat then is radiated. Some of it is transferred from the outside of the case via convective cooling; the foot pads on the bottom cover are designed to raise it up just enough to allow air underneath for convection to occur. (Convection is the process in which hot air to rises and is displaced by cooler air.) The rest of the heat from the bottom cover is absorbed by whatever surface you have the computer on.
    The processor will not sync to the case very much if the board is assembled properly however the other components of the computer will, requiring the case to be in open air to allow for passive cooling to take place.
    If you have some sort of covering such as a plastic snap on case it will likely interfere with passive cooling in all of it's 3 of it forms, this will cause the computer to be abnormally hot. I recently saw someone in the Apple store with a MacBook Air experiencing abnormal heating due to a plastic snap case so this particular problem is not unique to MacBook Pros and it is not the cause of the issue being discussed here. I do not recommend the use or anything that covers the computer while it is running with the exception of something that covers the back of the display panel only. If you are worried about your computer getting damaged go and buy a laptop insurance policy from Worth Ave group. The insurance does not cover cosmetic damage or misplaced items but will cover accidental damage including spills. This insurance also covers theft, vandalism and natural disasters, is quite inexpensive and the claims process and deductible  is similar to most phone insurance plans (which they also offer).
    User induced overheating can also occur when the computer is placed on an improper surface such as a couch cushion, car seat, bed, pillow etc. Doing this can interfere with both passive and active cooling.
    As I mentioned earlier In all likelihood if your computer was produced after May it is not affected. I personally have been in posession of 3 MacBook Pros, one produced before May which had the problem, one after which had no problems and one produced more recently that has mind blowing thermal performance way beyond all of my expectations.
    So the question at this point is exactly what is the problem, how can it be diagnosed and how can it be rectified.
    After extensive research and testing I have determined the issue to be related to improper application thermal paste. I involuntarily became involved in this pursuit as a result of the problems I was experiencing and I did not initially come at from an objective viewpoint but rather one of cautious skepticism. I had anticipated before purchasing my computer that there may be a thermal issue. This anticipaion came as a result of reading an article on ifixit.com about the disassembly of the brand new early 2011 MacBook Pro. When the technician performing the disassembly removed the main heat sync he expressed concern about how much much thermal paste was present, expressing that it seemed excessive. This lead the technician to question wether or not it would cause heating problems.
    Proper application of thermal paste is critical to the functionality of the active cooling system and when applied improperly will not properly transfer the heat to the heat-sync which in turn gets cooled by the fan. Proper application of thermal paste insures the heat is removed from the case as efficiently as possible. Doing this both reduces the speed at which the fan needs to run in a lot of situations and prevents too much heat from the processor needing to be cooled by passive means. If is is not applied properly it will eventually lead to overheating of the case as well as the other components of the computer. This can cause damage firstly to the computer's battery and can also significantly shorten the life computer. (Or any other kind of electronic device for that matter.)
    The problem can be diagnosed by testing the computer using a program called System Load or any other software that will put your computers proscessor use up to its maximum and keep it there indefinitely. Placing full load on your GPU at the same time during the test is also recommended. Keep in mind, if you are using your computer the fan will spin up if needed for additional cooling. You should expect the fan go up to its maximum speed during the test, it is not in of itself an indication of a negative result. Make sure to have the computer plugged in, fully charged and on a proper surface. A desk or other flat surface should be fine. Exceptions would include the top of a refrigerator since it has insulation just underneath the metal exterior or any surface that is heated by any means such as a dryer or other appliance.
    (The temps to follow are in ºF)
    Run the test for up to 1 hour. If the case of the computer breaks 93 degrees your unit is likely affected. Expect the unit to even possibly reach temps approaching and exceeding 100º, if this happens immediately abort the test. Also look for the processor temp shooting up to around 180 in the first 30 seconds and the fan spinning up right away. Typically on a properly functioning unit the temperature of the case will end up being somewhere in the neighborhood of 88-91º. If this test is preformed in a room with a normal ambient room temperature of about 68 degrees. Even after an hour the case of the computer should not be significantly hot, just warm to the touch. On a normally operating unit the fan will start to kick in within 90 seconds or so and may not reach full speed even after several minuets.
    At one point the case of my computer actually reached 95º during normal web browsing.
    This is a problem that I have had successfully corrected twice by reapplication of thermal paste. The first time was on a machine produced prior to may and the second was after a logic board was replaced at the repair depot. (I suspect the inventory turnover is lower for boards than whole computers resulting in a board from the initial production run being installed in my computer.)
    If you forget everything I just wrote remember this. #1 if you are using your computer hard enough the fan will end up running at high speed at some point. #2 This problem is not in any way related to the design of the MacBook Pro, or its use/application. #3 This mostly not a problem of the CPU being too hot; these Sandy Bridge CPUs are rated for 212ºf and will routinely be in the neighborhood of 200º, this is hotter than other chips but well within design limits. #4 I have done everything in my power to make sure that this problem has been corrected and I have every logical and evidenced based reason to believe it has been resolved in machines produced after may. #5 This is not an Apple acknolidged issue. Technicians will tell you that there is no problem because these higher temps are normal and within operating limits and if they weren't the machine would shut itself off. (This is a bit extreme; just like a lot of other devices such as electronics, toaster ovens and space heaters with thermal overload protection this automatic shutoff is intended to occur when damage or risk of fire is imminent because the device is WAY outside of normal operating paramaters.) They will also not tell you when asked what these limits are, that they know what they are or in some cases that such figures they even exsist.
    I stake my personal and professional reputation on the accuracy of my findings, it is my job as a private consultant to help my clients to resolve complicated and expensive issues just like this one.
    Bottom line if you are having a problem and Apple won't fix it on warranty don't ditch your machine, just pay to have it done yourself. In most cases you can pay have it done at the Apple store. It will probably cost you less than 100.00, and it will not void your warranty as long as the work is done by Apple certified technician. It will be well worth it; after all in spite of this MacBook Pro's are hands down the best portable computers on the market, with an industry leading warranty and support to back it up. On it's worst day Apple's service and support is better than any computer/ consumer electronics company, even on its best day.
    I hope this helps to clarify this issue! I also hope it will help anyone affected to resolve the problem instead of resorting to a refund and settling for something else.

    hello all
    you can try this:
    Go to system preferences > settings > built in display >  see bottom of window.
    check "show mirroring options in the menu bar when available". then click "airplay display" > and select your device.
    That's what happened to my MBP - 15-inch, Late 2011 model.

  • 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

  • I'm trying to use Boot Camp to install Windows 7 Enterprise on a 2011 MacBook Pro, but most of the drivers aren't installing correctly.

    Apparently, the only boot camp functions that work are restarting in Mac OSX and double-touch right-clicking, which I got after downloading the BootCamp 3.2 upgrade.
    This means no sound, no Direct3d (though I've installed the Intel drivers manually and that's now working), no keyboard functions, and no internet access by ethernet port or wifi, which means I won't be able to activate Windows and this install will soon die a quiet death.

    The Bootcamp Assistant version should 5.1.x. Please see Boot Camp 5.1: Frequently asked questions about installing Windows 8 - Apple Support and Boot Camp: System requirements for Microsoft Windows operating systems - Apple Support.
    The version of Bootcamp Drivers 5.1.5621 supports your Mac
    From Boot Camp Support Software 5.1.5621
    System Requirements
    MacBook Air (11-inch & 13-inch, Mid 2011)
    MacBook Air (11-inch & 13-inch, Mid 2012)
    MacBook Pro (15-inch & 17-inch, Mid 2010)
    MacBook Pro (13-inch, & 15-inch, Early 2011)
    MacBook Pro (17-inch, Early 2011)
    MacBook Pro (13-inch,15-inch & 17-inch  Late 2011)
    MacBook Pro (13-inch & 15-inch, Mid 2012)
    MacBook Pro (Retina, Mid 2012)
    MacBook Pro (Retina, 13-inch, Late 2012)
    MacBook Pro (Retina, 13-inch and 15-inch, Early 2013)
    Mac Pro (Early 2009)
    Mac Pro (Mid 2010)
    Mac Pro (Mid 2012)
    Mac mini (Mid 2011)
    Mac mini (Late 2012)
    iMac (27-inch, Mid 2010)
    iMac (21.5-inch & 27-inch, Mid 2011)
    iMac (21.5-inch & 27-inch, Late 2012)
    iMac (21.5-inch) Early 2013
    Windows 7, Windows 8, and Windows 8.1, 64 bit

Maybe you are looking for