My MacBook Pro overheats when connected to Thunderbolt Display

I've had these since August 30 of this year. I switch to Mac and brough home two Pro's and two Thunderbolts. They have been doing fine, not a problem yet. Until Friday, when mine started overheating. My MacBook Pro Retina runs fine on it's own. But I came home, plugged it into the Thunderbolt, and immediately it started overheating. It did the same thing, when I woke up Saturday it was so hot, I could not pick it up with my hands. I found another thread with similar problems, but it was four pages of "I have this problem, too". It's not sitting on a desk, it's in the stand sold by Apple, and I"ve had it plugged up to the Thunderbolt 80% of the time since we bought it, but never had a problem until five days ago. Clamshell mode in a stand with wireless Keyboard and Track Pad, all the newest releases of Pro Retina and Thunderbolt. All the updates, everything. Any ideas?

Connecting an external monitor/display turns on the high-performance graphics adapter which can generate significant heat. The base-plate can get pretty hot (Apple states this and for this reason says to not use the MacBook Pro on your lap. They don't even refer to them as laptops.). Just make sure that nothing is blocking the cooling ports under the display hinge. If the MacBook Pro actually overheats, it will shut down. So, don't worry yet.

Similar Messages

MacBook pro 15" Retina - connecting to Thunderbolt display issue

Hi
Is everyone else have trouble connecting the thunderbolt to the MacBook Pro with Retina? With my air it was plug and play (nomatter if the MBA were asleep or awake - it would just wake up when I uesed the wirless mouse or keyboard), but now I have to restart my Mac everytime I connect it to the thunderbolt display.
It simply will not "wake" when I connect the thunderbolt cable. I have to open the screen and the restart..
Also there is a lot of "flickering" . almost like it is "trying" to work.. but have to be reastartet everytime.

Mine is even worse...after connecting it the display flickers and turns black...the mainboard of the display was changed but the symptoms returned after some few hours of usage...

I recently purchased a Macbook Pro and when connecting my iPhone 5 to the Macbook's Messages app, I clicked cancel after seeing the 6 digit code. I thought I could easily get that code back to my phone, but can't figure it out at all. Any help?

I recently purchased a Macbook Pro and when connecting my iPhone 5 to the Macbook's Messages app, I clicked cancel after seeing the 6 digit code. I thought I could easily get that code back to my phone, but can't figure it out at all. Any help?

Hello Unconscious2015,
Thanks for using Apple Support Communities.
If you are trying to configure your Mac to use SMS continuity with your iPhone, then please follow the directions below to configure SMS Continuity.
To use Continuity for SMS and MMS with your iPhone and your Mac, iPad or iPod touch
Your iPhone, iPad, and iPod touch need to use iOS 8.1, and your Mac needs to use OS X Yosemite.
Sign in to iMessage on your iPhone, your other iOS devices, and your Mac using the same Apple ID.
On your iPhone:
Go to Settings > Messages > Send & Receive > You Can Be Reached By, and add a check to both your phone number and email address.
Go to Messages > Text Message Forwarding, and enable the device(s) you would like to forward messages to.
Your Mac, iPad, or iPod touch will display a code. Enter this code on your iPhone to verify the SMS feature.
Connect your iPhone, iPad, iPod touch, and Mac using Continuity - Apple Support
Take care,
Alex H.

What display is more suitable for a macbook pro, an iMac or a Thunderbolt Display?

I am currently deployed in Afghanistan and will be purchasing a Macbook Pro upon my return. This will be my first time owning a mac as I have always been a Windows user so I am unaware of which product works the best with one another. I am curious to know though which display will work the best with a macbook pro; an iMac or a Thunderbolt Display? Any guidance or advice anybody could offer would be greatly appreciated, thank you.

Both work very well with the MBP.
In essence the iMac is the ThunderBolt Display with an added Mac computer inside.
If you don't need a second Mac computer save the money, get the Display and invest the money in more RAm or a bigger harddisk for the MBP.
Stefan

MacBook Pro crashes when connecting via external modem

My new MacBook Pro crashes when I try to connect to the Internet via an external modem. Is it a SW or HW problem? In the latter case might it by the computer or the modem (original).
Sarah
MacBook Pro 1,1 Mac OS X (10.4.6)

This is Bob Simpson again from Paris. I followed the advice given in this forum and took out the set of HP printer drivers from the drivers pre-installled in my MacBook Pro and put them on my desktop. After that, the modem worked perfectly. If I want to use my HP Laserjet 1200 printer, I plug it into a USB port on the computer, the computer recognizes it and prints. If I want to use the modem again, I have to take that printer out of my list of printers in the print center. This is a bit of a pain in the neck, but it works. No one at any of the Apple distributers or Apple Care centers was able to figure all this out. Our forum did the job and we should get free awards from Apple, like the installation of the update on all our computers that will settle this problem. Otherwise, my BMacBook pro works like a dream. Many thanks to all of you and jackplug, you don't have to throw away your printer.

MacBook Pro Retina hangs on startup when connected to Thunderbolt Display

I have a MacBook Pro Retina and it's basically almost always connected to my Thunderbolt Display. Each time I start it up, I open the MacBook just slightly and press the power button - and almost instantly the MacBook goes ontop the startup Login screen and at this point is where I close the MacBook and login through the Thunderbolt Display.
Since last night for the very first time - My MacBook Pro hangs on a white screen and takes a long time before going to the Login screen. I've tried to swith the Thunderbolt Display off from the mains - I've also tried to boot up my MacBook on it's own without it being connected to the Thunderbold Display and all is fine (it almost immediatelly shows the Apple logo and then staright onto the Login screen then BUT as explained, as soon as the MacBook is connected to the Thunderbolt Display and I power it up - it hangs on a white screen for about 30 - 60 seconds before it goes to the login screen!
I have no idea how from one day to the next this could happen? Perhaps it's some Apple updates I've made recently which I cant really recall because I usually just update software when required to do so.
Hoping anyone can help.

Hello FunkTunes,
I recommend this section of the article Apple computers: Troubleshooting issues with video on internal or external displays found here http://support.apple.com/kb/ht1573.
Check connections
When using an external display be sure to check the following:
If you're using an Apple notebook, confirm the AC power cable or adapter is securely connected to the computer and the cable providing power to the display is also secure. It is always good to have your notebook connected to AC power when an external display is in use.
Confirm display adapters are fully seated in their respective connections and that they are supported models and for the computer and display. Refer to these articles to assist you with adapter compatibility and further configuration information:
Monitor and Display Adapter Table
About Mini DisplayPort to HDMI adapters
Apple Mini DisplayPort adapters: Frequently asked questions (FAQ)
Thunderbolt ports and displays: Frequently asked questions (FAQ)
Remove all display cable extenders, KVM switches, or other like devices and retest to determine if the issue is resolved.
Try unplugging the video adapter or cable and then plug it back in.
If more than one video adapter is in use (or "daisy-chained"), troubleshoot by using only one adapter.
Example: A mini DisplayPort to DVI adapter connected to a DVI to HDMI adapter is an unsupported configuration because there is a series of adapters in use.
If available, try using a different display and or adapter (or use a different connector by using DVI instead of VGA, for instance).
Reset the system
You can reset the Mac's parameter RAM and SMC.Reset the resolutionStart by resetting the Mac's parameter RAM. If the display does not come up, was previously set to an unsupported resolution, and still results in no video:
Start up in Safe Mode.
From the Apple () menu, choose System Preferences.
Choose Displays from the View menu to open the preferences pane.
Select any resolution and refresh rate that your display supports.
Restart your computer.
All the best,
Sterling

Slow wifi on MacBook Pro when connected to Thunderbolt Display

Hello everyone,
I've had my MacBook pro (2012) for about a year now, and I bought the Thunderbold Display last christmas.
Everything has been working fine until a few days ago, when I realised that my wifi connection speed was very very low (less than 0.5 mb or even no connection) whilst my other devices like iPhone and Windows pc were doing fine on 10mb.
I tried changing the router channel options but it wouldn't work. Then I disconnected the MacBook from the TB and wifi speed went up immediately...
Consequently I'm guessing it's the TB's fault. Can anyone help me find a solution? Or if i should bring it back for repair? (btw it's slow both with lid open or closed)
Thank you!

I am also experiencing very similar issues. For the past few weeks I have been suffering from really poor wifi performance on a Macbook Pro 13" Retina (Late 2012).
I have gone as far as purchasing a new router, changing router channels, encryption, switching back to 802.11g etc and nothing has really helped.
I downloaded a free app called NetSpot to help diagnose the problem. Today I had it open whilst plugging in my external monitor and I noticed a huge difference in signal to noise. The screenshot below shows that difference and I can re-produce it over and over again.
The external screen is plugged in via Thunderbolt. Interestingly only one of my thunderbolt ports seems to work with the screen (not sure if that is how it should be).
I can also see almost double the number of wifi networks with the screen unplugged and the internet performance is much better.
So my conclusion so far is that an external screen via thunderbolt is causing some serious performance issues. I am going to test the HDMI port later today and see if that helps the situation.

Brand new macbook pro 15" when connected to external LCD display in high resolution ,flickers often

Hi,
I have brand new macbook pro 15" with retina display.
I have connected external LCD display (Samsung B2230) using Apple VGA adaptor & thunderbolt port. But LCD display flickers quite oftenly. I read community blogs where many macbook pro users like me are facing similiar issue.
There is no problem with LCD display as it works fine with Lenova laptops.
Can anybody please provide me the solution to this problem.?
Regards,
Sam

Hello there, Sam.
The following Knowledge Base article provides some great steps for troubleshooting your issue:
Apple computers: Troubleshooting issues with video on internal or external displays
http://support.apple.com/kb/ht1573
Thanks for reaching out to Apple Support Communities.
Cheers,
Pedro.

HT5219 When I close the lid on my MacBook Pro the print on the thunderbolt display gets very small & hard to read. How do I prevent this?

When I close the lid on my MacBook Pro the print on thunderbolt screen is very small & hard to read. If i keep the lid open on the MacBook Pro the print is big and easy to read. How do I prevent this from happening?

Hi JanStran,
You may need to check your Display settings and/or resolution.
The article below explains how to used Clamshell mode "closed display" on your Macbook Pro, versus "mirroring."
Mac notebooks: How to use your computer in closed clamshell (display closed) mode with an external display
Hope this information helps ...
- Judy

My MacBook Pro, even when connected to the power chord, will turn on for a few seconds then shut back off. Any ideas on what is wrong?

I Am trying to turn on my MacBook Pro laptop, but when I do, it starts to turn on for a few seconds then shuts off again. It has around 80% charge and even if the power chord is connected it won't turn on. Need some help because I am out of the US right now and there are not a Mac store or anything that I could go to.

HAve you tried using a different power chord? If the power chord is not the issue, it could be the power supply inside your mac.

Macbook Pro Freezes When Connected to iPod Classic!

I have a mid 2010 Macbook Pro that is acting a little funky. Whenever I plug in my iPod Classic to add music everything works perfectly fine until I eject the iPod. My computer then basically freezes up (gives the rainbow spinwheel of death) and it will not recover. The iPod icon doesn't disappear, it just turns light grey and everytime my only option is to force quit iTunes. The problem doesn't end there, my computer is completely bogged down and I have to force shut it down. It is incredibly annoying... The iPod works perfectly fine when I plug it into my fiancee's older Macbook Pro, it ejects fine and I've run disk utility on it using that computer and there are no problems with the iPod. My mid 2010 Macbook Pro runs other USB devices just fine (iPhone, iPad, Flash Drives etc.) it's just the iPod.
Additionally, every since I upgraded to OS X 10.7 the computer will not shut down/restart. It just goes to a grey screen with a spinny wheel and won't fully shut down (I've left it over night to no success still grey screen). I have reinstalled OS X several times so I'm confused on this one as well. Any information on either of these issues would be greatly GREATLY appreciated.

I should add that I can quit iTunes with the iPod connected. When I try to eject the iPod by manually dragging the icon to the trash the funkiness begins (icon doesn't disappear just turns light grey, and the computer freezes). I have found the computer behaves if I put it to sleep with the iPod connected (the iPod will eject properly) and when I wake the computer up, everything works w/o funkiness, however the greyed out iPod icon will still be on the desktop. This is the only way I've found to be able to manage this iPod when connected to this MBP.

Can I turn off my MacBook Pro screen when connected to an external monitor?

I have my 13' MacBook Pro connected an external Samsung monitor, is it possible to have the laptop screen turned off so that it is only displayed on the monitor screen?

This is the Mac Pro desktop forum. I requested your post be moved to the MacBook Pro laptop forum.

MacBook Pro freezes when connected to LCD projector

I just bought this computer in January 2014 and it's running 10.9.4. I am so frustrated because every time I hook it up to the projector where I teach, it hangs and then eventually freezes entirely, prompting a hard reboot. I don't understand why it is doing this to me. I just used it at a conference in March and it didn't do this. But suddenly at this new school, it cannot deal with the projector. I have looked at previous threads with similar titles and they are unresolved. Any ideas?

here are some of the messages from my console at around the time it failed to connect and then froze.
Sep 3 2:35:44.690 PM WindowServer[103]: Received display connect changed for display 0x42731c0
Sep 3 2:35:44.692 PM WindowServer[103]: Found 15 modes for display 0x042731c0 [15, 0]
Sep 3 2:35:44.741 PM WindowServer[103]: Received display connect changed for display 0x3f003d
Sep 3 2:35:44.743 PM WindowServer[103]: Found 14 modes for display 0x003f003d [14, 0]
Sep 3 2:35:44.743 PM WindowServer[103]: Display 0x003f003d changed state to online
Sep 3 2:35:44.786 PM WindowServer[103]: Received display connect changed for display 0x3f003e
Sep 3 2:35:44.786 PM WindowServer[103]: Found 1 modes for display 0x003f003e [1, 0]
Sep 3 2:35:44.787 PM WindowServer[103]: Received display connect changed for display 0x3f003f
Sep 3 2:35:44.787 PM WindowServer[103]: Found 1 modes for display 0x003f003f [1, 0]
Sep 3 2:35:44.821 PM WindowServer[103]: MPServiceForDisplayDevice: Invalid device alias (0)
Sep 3 2:35:44.821 PM WindowServer[103]: Display 0x042731c0: GL mask 0x1; bounds (0, 0)[1280 x 800], 15 modes available
Main, Active, on-line, enabled, built-in, boot, OpenGL-accel, Vendor 610, Model 9cc7, S/N 0, Unit 0, Rotation 0
UUID 0xcb5a19e16c20c98ebb2d70fc3bb550b4, ColorProfile { 2, "Color LCD"}
Sep 3 2:35:44.821 PM WindowServer[103]: GLCompositor: GL renderer id 0x01024400, GL mask 0x0000001f, accelerator 0x000034ab, unit 0, caps QEX|MIPMAP, vram 1024 MB
texture max 16384, viewport max {16384, 16384}, extensions FPRG|NPOT|GLSL|FLOAT
Sep 3 2:35:44.821 PM WindowServer[103]: Display 0x003f0040: GL mask 0x10; bounds (2304, 0)[1 x 1], 2 modes available
off-line, enabled, OpenGL-accel, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 4, Rotation 0
UUID 0xffffffffffffffffffffffffffffffff
Sep 3 2:35:44.821 PM WindowServer[103]: GLCompositor: GL renderer id 0x01024400, GL mask 0x0000001f, accelerator 0x000034ab, unit 0, caps QEX|MIPMAP, vram 1024 MB
texture max 16384, viewport max {16384, 16384}, extensions FPRG|NPOT|GLSL|FLOAT
Sep 3 2:35:44.822 PM WindowServer[103]: Display 0x003f003f: GL mask 0x8; bounds (2305, 0)[1 x 1], 1 modes available
off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 3, Rotation 0
UUID 0xffffffffffffffffffffffffffffffff
Sep 3 2:35:44.822 PM WindowServer[103]: Display 0x003f003e: GL mask 0x4; bounds (2306, 0)[1 x 1], 1 modes available
off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 2, Rotation 0
UUID 0xffffffffffffffffffffffffffffffff
Sep 3 2:35:44.822 PM WindowServer[103]: Display 0x43800001: GL mask 0x2; bounds (1280, 0)[1280 x 720], 14 modes available
Active, on-line, enabled, Vendor 170e, Model 0, S/N 0, Unit 1, Rotation 0
UUID 0x9e557102dcc80bcde4a898a435908d02
Sep 3 2:35:44.823 PM Dock[235]: Set a breakpoint at CGSLogError to catch errors as they are logged.
Sep 3 2:35:44.823 PM Dock[235]: CGSCopyDisplayUUID: Invalid display 0x43800001
Sep 3 2:35:44.823 PM Dock[235]: uuid_callback_master: failed to retrieve UUID for display 0x43800001 (1001) (invariant failure)
Sep 3 2:35:44.823 PM Dock[235]: CGSCopyDisplayUUID: Invalid display 0x43800001
Sep 3 2:35:44.823 PM Dock[235]: uuid_callback_master: failed to retrieve UUID for display 0x43800001 (1001) (invariant failure)
Sep 3 2:35:44.823 PM Dock[235]: CGSCopyDisplayUUID: Invalid display 0x43800001
Sep 3 2:35:44.823 PM Dock[235]: uuid_callback_master: failed to retrieve UUID for display 0x43800001 (1001) (invariant failure)
Sep 3 2:35:44.824 PM Dock[235]: CGSCopyDisplayUUID: Invalid display 0x43800001
Sep 3 2:35:44.824 PM Dock[235]: uuid_callback_master: failed to retrieve UUID for display 0x43800001 (1001) (invariant failure)
Sep 3 2:35:44.824 PM Dock[235]: CGSCopyDisplayUUID: Invalid display 0x43800001
Sep 3 2:35:44.824 PM Dock[235]: uuid_callback_master: failed to retrieve UUID for display 0x43800001 (1001) (invariant failure)
Sep 3 2:35:44.824 PM Dock[235]: CGSCopyDisplayUUID: Invalid display 0x43800001
Sep 3 2:35:44.824 PM Dock[235]: uuid_callback_master: failed to retrieve UUID for display 0x43800001 (1001) (invariant failure)
Sep 3 2:35:44.824 PM Dock[235]: CGSCopyDisplayUUID: Invalid display 0x43800001
Sep 3 2:35:44.824 PM Dock[235]: uuid_callback_master: failed to retrieve UUID for display 0x43800001 (1001) (invariant failure)
Sep 3 2:35:44.824 PM Dock[235]: CGSCopyDisplayUUID: Invalid display 0x43800001
Sep 3 2:35:44.824 PM Dock[235]: uuid_callback_master: failed to retrieve UUID for display 0x43800001 (1001) (invariant failure)
Sep 3 2:35:44.825 PM Dock[235]: CGSCopyDisplayUUID: Invalid display 0x43800001
Sep 3 2:35:44.825 PM Dock[235]: uuid_callback_master: failed to retrieve UUID for display 0x43800001 (1001) (invariant failure)
Sep 3 2:35:44.908 PM WindowServer[103]: Display 0x042731c0: Unit 0: Mode 1280 x 720, CGSThirtytwoBitColor, Resolution 1, ioModeID 0x80007008, ioModeDepth 0x0, IOReturn 0x0
Sep 3 2:35:44.959 PM WindowServer[103]: hw_mirror_device_if_possible: windowserver picks master 0x43800001 as primary (driver did not pick)
Sep 3 2:35:44.959 PM WindowServer[103]: Display 0x042731c0: Unit 0: Startup Mode 1280 x 720, CGSThirtytwoBitColor, Resolution 1, ioModeID 0x80007008, ioModeDepth 0x0, IOReturn 0x0
Sep 3 2:35:44.960 PM WindowServer[103]: Display 0x43800001: Unit 1: Startup Mode 1280 x 720, CGSThirtytwoBitColor, Resolution 1, ioModeID 0x80007004, ioModeDepth 0x0, IOReturn 0x0
Sep 3 2:35:44.960 PM WindowServer[103]: Display mode changed
Sep 3 2:35:44.960 PM WindowServer[103]: Display added
Sep 3 2:35:44.960 PM WindowServer[103]: Display removed
Sep 3 2:35:44.960 PM WindowServer[103]: Displays mirrored
Sep 3 2:35:44.962 PM WindowServer[103]: Display 0x43800001: GL mask 0x2; bounds (0, 0)[1280 x 720], 14 modes available
Master in mirror set; Main, Active, on-line, enabled, Vendor 170e, Model 0, S/N 0, Unit 1, Rotation 0
UUID 0x9e557102dcc80bcde4a898a435908d02
Sep 3 2:35:44.962 PM WindowServer[103]: _CGXGLDisplayContextForDisplayDevice: acquired display context (0x7fe9b9412310) - enabling OpenGL
Sep 3 2:35:44.962 PM WindowServer[103]: GLCompositor: GL renderer id 0x01024400, GL mask 0x0000001f, accelerator 0x000034ab, unit 0, caps QEX|MIPMAP, vram 1024 MB
texture max 16384, viewport max {16384, 16384}, extensions FPRG|NPOT|GLSL|FLOAT
Sep 3 2:35:44.962 PM WindowServer[103]: Display 0x042731c0: GL mask 0x1; bounds (0, 0)[1280 x 720], 15 modes available
Hardware mirror of 0x43800001; on-line, enabled, built-in, boot, Vendor 610, Model 9cc7, S/N 0, Unit 0, Rotation 0
UUID 0xcb5a19e16c20c98ebb2d70fc3bb550b4, ColorProfile { 2, "Color LCD"}
Sep 3 2:35:44.963 PM WindowServer[103]: Display 0x003f0040: GL mask 0x10; bounds (2304, 0)[1 x 1], 2 modes available
off-line, enabled, OpenGL-accel, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 4, Rotation 0
UUID 0xffffffffffffffffffffffffffffffff
Sep 3 2:35:44.963 PM WindowServer[103]: GLCompositor: GL renderer id 0x01024400, GL mask 0x0000001f, accelerator 0x000034ab, unit 0, caps QEX|MIPMAP, vram 1024 MB
texture max 16384, viewport max {16384, 16384}, extensions FPRG|NPOT|GLSL|FLOAT
Sep 3 2:35:44.963 PM WindowServer[103]: Display 0x003f003f: GL mask 0x8; bounds (2305, 0)[1 x 1], 1 modes available
off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 3, Rotation 0
UUID 0xffffffffffffffffffffffffffffffff
Sep 3 2:35:44.963 PM WindowServer[103]: Display 0x003f003e: GL mask 0x4; bounds (2306, 0)[1 x 1], 1 modes available
off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 2, Rotation 0
UUID 0xffffffffffffffffffffffffffffffff
Sep 3 2:35:45.123 PM WindowServer[103]: MPAccessSurfaceForDisplayDevice: Set up page flip mode on display 0x43800001 device: 0x7fe9b9412310 isBackBuffered: 1 numComp: 3 numDisp: 3
Sep 3 2:35:46.741 PM WindowServer[103]: **DMPROXY** (2) Found `/System/Library/CoreServices/DMProxy'.
Sep 3 2:35:46.787 PM WindowServer[103]: **DMPROXY** (2) Found `/System/Library/CoreServices/DMProxy'.
Sep 3 2:35:46.845 PM WindowServer[103]: Display 0x43800001: Unit 1; ColorProfile { 3, "Display"}; TransferFormula (1.000000, 1.000000, 1.000000)
Sep 3 2:35:46.908 PM WindowServer[103]: Display 0x042731c0: Unit 0; ColorProfile { 2, "Color LCD"}; TransferTable (256, 12)
Sep 3 2:35:46.921 PM WindowServer[103]: **DMPROXY** (2) Found `/System/Library/CoreServices/DMProxy'.
Sep 3 2:35:46.925 PM WindowServer[103]: **DMPROXY** (2) Found `/System/Library/CoreServices/DMProxy'.
Sep 3 2:35:46.957 PM WindowServer[103]: Display 0x43800001: Unit 1; ColorProfile { 3, "Display"}; TransferFormula (1.000000, 1.000000, 1.000000)
Sep 3 2:35:46.958 PM WindowServer[103]: Display 0x042731c0: Unit 0; ColorProfile { 2, "Color LCD"}; TransferTable (256, 12)
Sep 3 2:35:46.984 PM WindowServer[103]: Display 0x43800001: Unit 1; ColorProfile { 3, "Display"}; TransferFormula (1.000000, 1.000000, 1.000000)
Sep 3 2:35:46.985 PM WindowServer[103]: Display 0x042731c0: Unit 0; ColorProfile { 2, "Color LCD"}; TransferTable (256, 12)
Sep 3 2:35:47.021 PM WindowServer[103]: Display 0x43800001: Unit 1; ColorProfile { 3, "Display"}; TransferFormula (1.000000, 1.000000, 1.000000)
Sep 3 2:35:47.022 PM WindowServer[103]: Display 0x042731c0: Unit 0; ColorProfile { 2, "Color LCD"}; TransferTable (256, 12)
Sep 3 2:35:47.054 PM WindowServer[103]: Display 0x43800001: Unit 1; ColorProfile { 3, "Display"}; TransferFormula (1.000000, 1.000000, 1.000000)
Sep 3 2:35:47.055 PM WindowServer[103]: Display 0x042731c0: Unit 0; ColorProfile { 2, "Color LCD"}; TransferTable (256, 12)
Sep 3 2:35:47.073 PM WindowServer[103]: Display 0x43800001: Unit 1; ColorProfile { 3, "Display"}; TransferFormula (1.000000, 1.000000, 1.000000)
Sep 3 2:35:47.074 PM WindowServer[103]: Display 0x042731c0: Unit 0; ColorProfile { 2, "Color LCD"}; TransferTable (256, 12)
Sep 3 2:35:47.102 PM WindowServer[103]: Display 0x43800001: Unit 1; ColorProfile { 3, "Display"}; TransferFormula (1.000000, 1.000000, 1.000000)
Sep 3 2:35:47.103 PM WindowServer[103]: Display 0x042731c0: Unit 0; ColorProfile { 2, "Color LCD"}; TransferTable (256, 12)
Sep 3 2:35:47.141 PM WindowServer[103]: Display 0x43800001: Unit 1; ColorProfile { 3, "Display"}; TransferFormula (1.000000, 1.000000, 1.000000)
Sep 3 2:35:47.142 PM WindowServer[103]: Display 0x042731c0: Unit 0; ColorProfile { 2, "Color LCD"}; TransferTable (256, 12)
Sep 3 2:35:48.000 PM kernel[0]: **** [IOBluetoothHostControllerUSBTransport][SuspendDevice] -- Suspend -- suspendDeviceCallResult = 0x0000 (kIOReturnSuccess) -- 0xdc00 ****
Sep 3 2:35:49.354 PM com.apple.launchd.peruser.501[173]: (com.lexmark.bmlaunchd[1244]) Exited with code: 1
Sep 3 2:35:49.354 PM com.apple.launchd.peruser.501[173]: (com.lexmark.bmlaunchd) Throttling respawn: Will start in 10 seconds
Sep 3 2:35:59.415 PM com.apple.launchd.peruser.501[173]: (com.lexmark.bmlaunchd[1245]) Exited with code: 1
Sep 3 2:35:59.415 PM com.apple.launchd.peruser.501[173]: (com.lexmark.bmlaunchd) Throttling respawn: Will start in 10 seconds
Sep 3 2:36:09.423 PM com.apple.launchd.peruser.501[173]: (com.lexmark.bmlaunchd[1247]) Exited with code: 1
Sep 3 2:36:09.423 PM com.apple.launchd.peruser.501[173]: (com.lexmark.bmlaunchd) Throttling respawn: Will start in 10 seconds
Sep 3 2:36:11.079 PM mds[40]: (Normal) ImportServer: Ignoring blacklisted Spotlight importer plugin:/Developer/Applications/Xcode.app/Contents/Library/Spotlight/SourceCode. mdimporter uuid:548A3091-3C5D-498A-A329-B532A6C896BB version:1801
Sep 3 2:36:11.463 PM mds[40]: (Normal) ImportServer: Ignoring blacklisted Spotlight importer plugin:/Developer/Applications/Xcode.app/Contents/Library/Spotlight/SourceCode. mdimporter uuid:548A3091-3C5D-498A-A329-B532A6C896BB version:1801
Sep 3 2:36:19.463 PM com.apple.launchd.peruser.501[173]: (com.lexmark.bmlaunchd[1250]) Exited with code: 1
Sep 3 2:36:19.463 PM com.apple.launchd.peruser.501[173]: (com.lexmark.bmlaunchd) Throttling respawn: Will start in 10 seconds
Sep 3 2:36:29.536 PM com.apple.launchd.peruser.501[173]: (com.lexmark.bmlaunchd[1251]) Exited with code: 1
Sep 3 2:36:29.536 PM com.apple.launchd.peruser.501[173]: (com.lexmark.bmlaunchd) Throttling respawn: Will start in 10 seconds
Sep 3 2:36:39.578 PM com.apple.launchd.peruser.501[173]: (com.lexmark.bmlaunchd[1253]) Exited with code: 1
Sep 3 2:36:39.578 PM com.apple.launchd.peruser.501[173]: (com.lexmark.bmlaunchd) Throttling respawn: Will start in 10 seconds
Sep 3 2:36:49.641 PM com.apple.launchd.peruser.501[173]: (com.lexmark.bmlaunchd[1254]) Exited with code: 1
Sep 3 2:36:49.641 PM com.apple.launchd.peruser.501[173]: (com.lexmark.bmlaunchd) Throttling respawn: Will start in 10 seconds
Sep 3 2:36:59.719 PM com.apple.launchd.peruser.501[173]: (com.lexmark.bmlaunchd[1255]) Exited with code: 1
Sep 3 2:36:59.719 PM com.apple.launchd.peruser.501[173]: (com.lexmark.bmlaunchd) Throttling respawn: Will start in 10 seconds
Sep 3 2:37:09.795 PM com.apple.launchd.peruser.501[173]: (com.lexmark.bmlaunchd[1257]) Exited with code: 1
Sep 3 2:37:09.795 PM com.apple.launchd.peruser.501[173]: (com.lexmark.bmlaunchd) Throttling respawn: Will start in 10 seconds
Sep 3 2:37:19.863 PM com.apple.launchd.peruser.501[173]: (com.lexmark.bmlaunchd[1258]) Exited with code: 1
Sep 3 2:37:19.863 PM com.apple.launchd.peruser.501[173]: (com.lexmark.bmlaunchd) Throttling respawn: Will start in 10 seconds
Sep 3 2:37:29.939 PM com.apple.launchd.peruser.501[173]: (com.lexmark.bmlaunchd[1259]) Exited with code: 1
Sep 3 2:37:29.939 PM com.apple.launchd.peruser.501[173]: (com.lexmark.bmlaunchd) Throttling respawn: Will start in 10 seconds
Sep 3 2:37:40.019 PM com.apple.launchd.peruser.501[173]: (com.lexmark.bmlaunchd[1261]) Exited with code: 1
Sep 3 2:37:40.019 PM com.apple.launchd.peruser.501[173]: (com.lexmark.bmlaunchd) Throttling respawn: Will start in 10 seconds
Sep 3 2:37:50.090 PM com.apple.launchd.peruser.501[173]: (com.lexmark.bmlaunchd[1262]) Exited with code: 1
Sep 3 2:37:50.090 PM com.apple.launchd.peruser.501[173]: (com.lexmark.bmlaunchd) Throttling respawn: Will start in 10 seconds
Sep 3 2:38:00.168 PM com.apple.launchd.peruser.501[173]: (com.lexmark.bmlaunchd[1263]) Exited with code: 1
Sep 3 2:38:00.168 PM com.apple.launchd.peruser.501[173]: (com.lexmark.bmlaunchd) Throttling respawn: Will start in 10 seconds
Sep 3 2:38:10.240 PM com.apple.launchd.peruser.501[173]: (com.lexmark.bmlaunchd[1265]) Exited with code: 1
Sep 3 2:38:10.240 PM com.apple.launchd.peruser.501[173]: (com.lexmark.bmlaunchd) Throttling respawn: Will start in 10 seconds
Sep 3 2:38:20.318 PM com.apple.launchd.peruser.501[173]: (com.lexmark.bmlaunchd[1266]) Exited with code: 1
Sep 3 2:38:20.318 PM com.apple.launchd.peruser.501[173]: (com.lexmark.bmlaunchd) Throttling respawn: Will start in 10 seconds
Sep 3 2:38:30.399 PM com.apple.launchd.peruser.501[173]: (com.lexmark.bmlaunchd[1267]) Exited with code: 1
Sep 3 2:38:30.399 PM com.apple.launchd.peruser.501[173]: (com.lexmark.bmlaunchd) Throttling respawn: Will start in 10 seconds
Sep 3 2:38:40.467 PM com.apple.launchd.peruser.501[173]: (com.lexmark.bmlaunchd[1269]) Exited with code: 1
Sep 3 2:38:40.467 PM com.apple.launchd.peruser.501[173]: (com.lexmark.bmlaunchd) Throttling respawn: Will start in 10 seconds
Sep 3 2:38:50.548 PM com.apple.launchd.peruser.501[173]: (com.lexmark.bmlaunchd[1270]) Exited with code: 1
Sep 3 2:38:50.548 PM com.apple.launchd.peruser.501[173]: (com.lexmark.bmlaunchd) Throttling respawn: Will start in 10 seconds
Sep 3 2:39:00.609 PM com.apple.launchd.peruser.501[173]: (com.lexmark.bmlaunchd[1271]) Exited with code: 1
Sep 3 2:39:00.609 PM com.apple.launchd.peruser.501[173]: (com.lexmark.bmlaunchd) Throttling respawn: Will start in 10 seconds
Sep 3 2:39:10.680 PM com.apple.launchd.peruser.501[173]: (com.lexmark.bmlaunchd[1273]) Exited with code: 1
Sep 3 2:39:10.680 PM com.apple.launchd.peruser.501[173]: (com.lexmark.bmlaunchd) Throttling respawn: Will start in 10 seconds
Sep 3 2:39:20.763 PM com.apple.launchd.peruser.501[173]: (com.lexmark.bmlaunchd[1274]) Exited with code: 1
Sep 3 2:39:20.763 PM com.apple.launchd.peruser.501[173]: (com.lexmark.bmlaunchd) Throttling respawn: Will start in 10 seconds
Sep 3 2:39:30.842 PM com.apple.launchd.peruser.501[173]: (com.lexmark.bmlaunchd[1275]) Exited with code: 1
Sep 3 2:39:30.842 PM com.apple.launchd.peruser.501[173]: (com.lexmark.bmlaunchd) Throttling respawn: Will start in 10 seconds
Sep 3 2:40:21.000 PM bootlog[0]: BOOT_TIME 1409769621 0

Macbook pro looses login settings with thunderbolt display

I've noticed that on occasion my MacBook Pro looses its desktop settings when connected to a Thunderbolt display. Why Thunderbolt display discards my MacBook Pro window environment settings upon boot-up is unknown to me. I can tell when this happens when my desktop loads different backgrounds from those on my MacBook Pro. Furthermore, the option in the System Preferences for changing my desktop background will cease to function. I even notice system wide speed degradation.
In order to correct this and reload my MacBook Pro settings I must identify a specific file named “com.apple.loginwindow.plist” and delete it. Doing so resolves whatever existing conflict so that Thunderbolt displays the correct background and enables System Preferrences to work properly.
I would appreciate very much if anyone has a resolution for this problem.
Respectfully,
TomBoltz

I think you need to do a search of the of these forums to see if there is an answer. I saw a lot of suggestions, but the #1 solution is buying a brand new cable. I have personal experience with that. My son recently switched from an HP to a MacBook Pro. The HDMI cable worked perfectly with the HP. It didn't with the Mac. He got a new cable for the Mac, everything resolved itself.
I have heard all kinds of speculation on it, but it happens frequently enough that there must be something going on. I'd spend $30 on a new MiniDisplayPort to DVI connector or whatever you use.

Store audio preferences when connected to Thunderbolt Display

We have a Macbook Pro Retina that we use with two thunderbolt displays at home. Connected to one of them is a Bose Companion 5 Soundsystem. Is there any way to tell the rMBP to automatically select the Bose soundsystem as playback device when we connect it? So far we always have to change that in the system preferences? Thanks!

We have a Macbook Pro Retina that we use with two thunderbolt displays at home. Connected to one of them is a Bose Companion 5 Soundsystem. Is there any way to tell the rMBP to automatically select the Bose soundsystem as playback device when we connect it? So far we always have to change that in the system preferences? Thanks!

My MacBook Pro overheats when connected to Thunderbolt Display

Similar Messages

Maybe you are looking for