Thunderbolt display update crash
Hello,
During Thunderbolt Display Firmware update 1.2 my computer stuck and turn off. Thunderbolt display stop working, computer shows no thunderbolt devices. I also try connect to MacBook Pro with same result. Is any way how to recover display?
Thank for your help.
Petr
Message was edited by: brhelp_zr
I am sorry i wrote post with same problem like https://discussions.apple.com/thread/6759865
..and solved. The secret seemed to be to follow these steps. Have no idea if they are all necessary but it worked for me.
In Display preferences hit gather window to bring the thunderbolt display preferences onto the mac screen
Uncheck Adjust brightness automatically and save
disconnect the display from the mac.
Restart the mac
Power down the display and leave for a few minutes
Power up the display
Reconnect the display to the mac
The screen returned to life. Let's see if it stays that way, I will report if it doesn't.
Similar Messages
-
Thunderbolt display update 1.2 causes unresponsive display
After running the thunderbolt display update 1.2 my display now displays the very thing the update was designed was supposed to correct - a black unresponsive screen (which I have ironically never suffered fro at all ever - grrrr).
I cannot get the thunderbolt display to come back to life although the mac can see it and thinks it is there and is extending the desktop to it.
Anyone else have this issue or ideas to solve?..and solved. The secret seemed to be to follow these steps. Have no idea if they are all necessary but it worked for me.
In Display preferences hit gather window to bring the thunderbolt display preferences onto the mac screen
Uncheck Adjust brightness automatically and save
disconnect the display from the mac.
Restart the mac
Power down the display and leave for a few minutes
Power up the display
Reconnect the display to the mac
The screen returned to life. Let's see if it stays that way, I will report if it doesn't. -
HT6093 Thunderbolt Display Update fail
I continue to get notices of a Thunderbolt Display update but it fails each time before loading. What should I do?
Same.
I have three thunderbolt displays connected to a Mac Pro. I got the error message, then read that no more than two displays could be connected during the update. I disconnected one of them and restarted. Then connected the other and disconnected the first and restarted again.
I'm not sure any of that worked and have no "active" notification that they were updated. I checked the firmware version following that update per the instructions and they match the version, but I'm still getting the random flicker. -
Stuck on White Screen on Thunderbolt Display Update - Lion
Anyone else have this problem? After the Thunderbolt display update, I get a white screen at the login after I restart my MacBook Pro. I either have to unplug my laptop so I can see the screen again to login, or I can hit enter and then blindly put in my password while he screen is blank and then it will pop back up again. It's annoying.
I didn't have this problem running Snow Leopard and I reset the PRAM and SMC already. This is also a clean install of Lion.I've actually just posted a similar post on the Thunderbolt thread. Is there anyway to rollback the firmware? This is so frutrating to have to wait so long before actually getting to the login screen.
If the Thunderbold display is unplugged then the MacBook has no problems and instantly goes into the login screen - on the other hand having the Thunderbolt display connected to the MacBook - same as you describe - Power on Macbook - white screen for about 1-3 minutes before the Apple logo appears and proceeds to the login screen
Hope someone can read and sort thins out soon. -
Thunderbolt Displays Cause Crash
Hi,
I have a macbook pro retina and two of the external thunderbolt displays (daisy chained).
Every time that I plug my MBP into the thunderbolt displays while it is asleep and try to wake the computer, it crashes. It sometimes reboots on its own, but usually I have to open the lid and hold the power button down.
This is a huge issue for me -- has anyone else had a similar problem? Can anyone offer any advice?Hey Chett,
I know this is a few years old now, but I have the same issue, but no advice.
Currently looking into this. -
No matter how many times I accept this update it comes back. What is <i>wrong<i/>?
Failure of a firmware update can be caused by some Thunderbolt or FireWire peripherals. Disconnect all such devices and try again.
-
Mac OS X 10.8 crashes after disconnecting the Thunderbolt display
Wondering if anyone can help my Mac OS X 10.8.5 crashes after I disconnect the thunderbolt display.
I normally work in the studio with my macbook connected to an external display.
When I go to use it without the thunderbolt display it crashes - 4 times in one day, which really isn't ideal when your freelancing.
I've checked my log files and I have a list of panic reports. I'm not too sure what I'm supposed to be looking for, but each of the reports refer to the graphics control. I've read online it might have something to do with the display sleep, so I've reset that.
GPU Panic: [<None>] 5 3 7f 0 0 0 0 3 : NVRM[0/1:0:0]: Read Error 0x00000100: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0xd2000000 0xffffff808013e000 0x0a5480a2, D0, P3/4\n"@/SourceCache/AppleGraphicsControl/AppleGraphicsControl-3.4.5/src/AppleM uxControl/kext/GPUPanic.cpp:127
I'd be very grateful if anyone could help
ChloeHi Chloebat,
I'm sorry to hear you are having issues with your MacBook Pro. If you continue to have intermittent but persistent crashing issues with your Mac, possibly related to the display, you may find the troubleshooting steps outlined in the following article helpful:
OS X: When your computer spontaneously restarts or displays "Your computer restarted because of a problem." - Apple Support
Regards,
- Brenden -
MacBook Pro fans running when plugged into Thunderbolt displays
I just got a sweet setup at work - a new MacBook Pro and 2 Thunderbolt displays. However, immediately upon setup I noticed the fans on the Mac Book operating constantly, even when I was just surfing the net or working in one Microsoft program.
I just spent a few hours working on the laptop - not plugged in to the Thunderbolt displays - and the fans did not go on at all. Within minutes of plugging it in to the displays, the fans started up again. So I think it may have something to do with the Mac Book being plugged into the Thunderbolt displays.
Can anyone help?
Mac Book Pro, Version 10.7.2, 2.4 GHz Intel Core i7, 8 GB 1333 MHz DDR3Hello,
I'm so sorry for the slow response! I ended up calling Apple because I was still mystified and no one was responding here.
The nice gentleman at Apple told me the following. The MacBook Pro can handle two Thunderbolts max. If the CPU is constantly running hot, then it could be an issue in the long term.
We went through the software update process for the Thunderbolt displays again, and it turns out that the software was NOT updating!!! It's not the usual "click install and the computer takes care of it all" sort of update - unfortunately I don't remember exactly what we did, but you have to go to the Applications folder and actually install something.
You'll know if you haven't followed these steps if, when you go back to check for updates, the Thunderbolt display update keeps popping up.
Since installing that firmware update, I have been using my MacBook with only one display. In the next week, I will probably plug it in to the second display and see if there are fan issues. If so, then Apple told me to call them back and see about further troubleshooting.
I hope this was somewhat helpful. If you are still unclear, I'd say call Apple! They were really helpful! Good luck! -
Macbook pro 17 inch primo 2011 and thunderbolt display crashes
I have a Macbook pro 17 inch primo 2011 and thunderbolt display which has recently started to crash.
Only modifications I have doen lately is I swapped the CD/DVD drive for a harddrive and put in 16 GB of ram
but it has been running for more than a month with these hardware additions without problems.
Today my Macbook has started to crash frequently within 10 min to 1 hour after plugging in my thunderbolt display.
I tried to check CPU heat, change RAM but it keps crashing.
When it crashes it either gives me a blue screen, a black screen or a distorts everythings and freeze up.
When rebooting I have to press Command-Option-P-R to clear NVRAM / PRAM.
I found a few support threads from people having similar problems so I started to disconnect the thunderbolt display
and without plugging it in my laptop works fine.
I have done a SMC reset also but that has not resolved my issue.
Below is the crash report and if anybody has any suggestions what to do to resolve this please let me know
My thunderbolt display was purchased in late 2011
If this is not solveable what options do I have ?
Thanks !
Interval Since Last Panic Report: 2527129 sec
Panics Since Last Report: 6
Anonymous UUID: 5309BD58-3CBB-321E-545E-6EE6BED7E0E2
Tue Feb 5 17:02:21 2013
Machine-check capabilities 0x0000000000000c09:
family: 6 model: 42 stepping: 7 microcode: 26
Intel(R) Core(TM) i7-2720QM CPU @ 2.20GHz
9 error-reporting banks
threshold-based error status present
extended corrected memory error handling present
Processor 0: machine-check status 0x0000000000000004:
machine-check in progress
MCA error-reporting registers:
IA32_MC0_STATUS(0x401): 0x0000000000000000 invalid
IA32_MC1_STATUS(0x405): 0x0980000000000000 invalid
IA32_MC2_STATUS(0x409): 0x0000000000000000 invalid
IA32_MC3_STATUS(0x40d): 0xbe00000000800400 valid
MCA error code: 0x0400
Model specific error code: 0x0080
Other information: 0x00000000
Threshold-based status: Undefined
Status bits:
Processor context corrupt
ADDR register valid
MISC register valid
Error enabled
Uncorrected error
IA32_MC3_ADDR(0x40e): 0x00003f7f85769a95
IA32_MC3_MISC(0x40f): 0x000000000003ffff
IA32_MC4_STATUS(0x411): 0x0000000000000000 invalid
IA32_MC5_STATUS(0x415): 0x0020000000000000 invalid
IA32_MC6_STATUS(0x419): 0x0020000000000000 invalid
IA32_MC7_STATUS(0x41d): 0x0020000000000000 invalid
IA32_MC8_STATUS(0x421): 0x0020000000000000 invalid
Processor 1: machine-check status 0x0000000000000005:
restart IP valid
machine-check in progress
MCA error-reporting registers:
IA32_MC0_STATUS(0x401): 0x0000000000000000 invalid
IA32_MC1_STATUS(0x405): 0x0980000000000000 invalid
IA32_MC2_STATUS(0x409): 0x0000000000000000 invalid
IA32_MC3_STATUS(0x40d): 0xbe00000000800400 valid
MCA error code: 0x0400
Model specific error code: 0x0080
Other information: 0x00000000
Threshold-based status: Undefined
Status bits:
Processor context corrupt
ADDR register valid
MISC register valid
Error enabled
Uncorrected error
IA32_MC3_ADDR(0x40e): 0x00003f7f85769a95
IA32_MC3_MISC(0x40f): 0x000000000003ffff
IA32_MC4_STATUS(0x411): 0x0000000000000000 invalid
IA32_MC5_STATUS(0x415): 0x0020000000000000 invalid
IA32_MC6_STATUS(0x419): 0x0020000000000000 invalid
IA32_MC7_STATUS(0x41d): 0x0020000000000000 invalid
Package 0 logged:
IA32_MC8_STATUS(0x421): 0x0020000000000000 invalid
Processor 2: no valid machine-check state
Processor 3: no valid machine-check state
Processor 4: machine-check status 0x0000000000000004:
machine-check in progress
MCA error-reporting registers:
IA32_MC0_STATUS(0x401): 0x0000000000000000 invalid
IA32_MC1_STATUS(0x405): 0x0980000000000000 invalid
IA32_MC2_STATUS(0x409): 0x0000000000000000 invalid
IA32_MC3_STATUS(0x40d): 0xbe00000000800400 valid
MCA error code: 0x0400
Model specific error code: 0x0080
Other information: 0x00000000
Threshold-based status: Undefined
Status bits:
Processor context corrupt
ADDR register valid
MISC register valid
Error enabled
Uncorrected error
IA32_MC3_ADDR(0x40e): 0x00003f7f85fa3e1f
IA32_MC3_MISC(0x40f): 0x000000000003ffff
IA32_MC4_STATUS(0x411): 0x0000000000000000 invalid
IA32_MC5_STATUS(0x415): 0x0020000000000000 invalid
IA32_MC6_STATUS(0x419): 0x0020000000000000 invalid
IA32_MC7_STATUS(0x41d): 0x0020000000000000 invalid
IA32_MC8_STATUS(0x421): 0x0020000000000000 invalid
Processor 5: machine-check status 0x0000000000000005:
restart IP valid
machine-check in progress
MCA error-reporting registers:
IA32_MC0_STATUS(0x401): 0x0000000000000000 invalid
IA32_MC1_STATUS(0x405): 0x0980000000000000 invalid
IA32_MC2_STATUS(0x409): 0x0000000000000000 invalid
IA32_MC3_STATUS(0x40d): 0xbe00000000800400 valid
MCA error code: 0x0400
Model specific error code: 0x0080
Other information: 0x00000000
Threshold-based status: Undefined
Status bits:
Processor context corrupt
ADDR register valid
MISC register valid
Error enabled
Uncorrected error
IA32_MC3_ADDR(0x40e): 0x00003f7f85fa3e1f
IA32_MC3_MISC(0x40f): 0x000000000003ffff
IA32_MC4_STATUS(0x411): 0x0000000000000000 invalid
IA32_MC5_STATUS(0x415): 0x0020000000000000 invalid
IA32_MC6_STATUS(0x419): 0x0020000000000000 invalid
IA32_MC7_STATUS(0x41d): 0x0020000000000000 invalid
IA32_MC8_STATUS(0x421): 0x0020000000000000 invalid
Processor 6: no valid machine-check state
Processor 7: no valid machine-check state
panic(cpu 0 caller 0xffffff80048b83c9): "Machine Check at 0xffffff7f85769a95, registers:\n" "CR0: 0x000000008001003b, CR2: 0x000000010cd0e30c, CR3: 0x00000000072b4000, CR4: 0x00000000000606e0\n" "RAX: 0xffffff802516f800, RBX: 0xffffff802516f800, RCX: 0xffffff80253ab800, RDX: 0x0000000000000001\n" "RSP: 0xffffff8207ad3e90, RBP: 0xffffff8207ad3ec0, RSI: 0xffffff8207ad3edf, RDI: 0xffffff802520e000\n" "R8: 0xffffff8004ebec60, R9: 0x7fffffffffffff00, R10: 0xffffff8004ebdc20, R11: 0x0000000000000201\n" "R12: 0xffffff80253ab800, R13: 0xffffff81d60d2000, R14: 0xffffff8207ad3edf, R15: 0xffffff802520e000\n" "RFL: 0x0000000000010282, RIP: 0xffffff7f85769a95, CS: 0x0000000000000008, SS: 0x0000000000000010\n" "Error code: 0x0000000000000000\n"@/SourceCache/xnu/xnu-2050.18.24/osfmk/i386/trap_native.c: 280
Backtrace (CPU 0), Frame : Return Address
0xffffff800470bd20 : 0xffffff800481d626
0xffffff800470bd90 : 0xffffff80048b83c9
0xffffff800470bf00 : 0xffffff80048cedbf
0xffffff8207ad3ec0 : 0xffffff7f856d75b4
0xffffff8207ad3ef0 : 0xffffff8004c472a8
0xffffff8207ad3f30 : 0xffffff8004c45daa
0xffffff8207ad3f80 : 0xffffff8004c45ed9
0xffffff8207ad3fb0 : 0xffffff80048b26b7
Kernel Extensions in backtrace:
com.apple.driver.AirPort.Brcm4331(602.15.22)[5BDCA43F-AD42-3F05-BCCF-BC364D17E1 5F]@0xffffff7f856ca000->0xffffff7f858bbfff
dependency: com.apple.iokit.IOPCIFamily(2.7.2)[B1B77B26-7984-302F-BA8E-544DD3D75E73]@0xffff ff7f84e72000
dependency: com.apple.iokit.IO80211Family(500.15)[4282DF5A-86B9-3213-B9B1-675FAD842A94]@0xf fffff7f8565e000
dependency: com.apple.iokit.IONetworkingFamily(3.0)[28575328-A798-34B3-BD84-D708138EBD17]@0 xffffff7f85015000
BSD process name corresponding to current thread: kernel_task
Mac OS version:
12C60
Kernel version:
Darwin Kernel Version 12.2.0: Sat Aug 25 00:48:52 PDT 2012; root:xnu-2050.18.24~1/RELEASE_X86_64
Kernel UUID: 69A5853F-375A-3EF4-9247-478FD0247333
Kernel slide: 0x0000000004600000
Kernel text base: 0xffffff8004800000
System model name: MacBookPro8,3 (Mac-942459F5819B171B)
System uptime in nanoseconds: 6197670207287
last loaded kext at 6133447331639: com.apple.driver.AppleUSBCDC 4.1.22 (addr 0xffffff7f86cb5000, size 16384)
last unloaded kext at 5379727445407: com.apple.driver.AppleUSBCDC 4.1.22 (addr 0xffffff7f86cb2000, size 12288)
loaded kexts:
com.apple.driver.AppleUSBCDC 4.1.22
com.apple.iokit.SCSITaskUserClient 3.5.1
com.apple.filesystems.smbfs 1.8
com.apple.filesystems.afpfs 10.0
com.apple.nke.asp_tcp 7.0.0
com.apple.driver.AudioAUUC 1.60
com.apple.driver.AppleHWSensor 1.9.5d0
com.apple.filesystems.autofs 3.0
com.apple.filesystems.ntfs 3.10
com.apple.iokit.IOBluetoothSerialManager 4.0.9f33
com.apple.driver.AGPM 100.12.69
com.apple.driver.AppleMikeyHIDDriver 122
com.apple.driver.AppleHDA 2.3.1f2
com.apple.iokit.IOUserEthernet 1.0.0d1
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.driver.ApplePolicyControl 3.2.11
com.apple.iokit.BroadcomBluetoothHCIControllerUSBTransport 4.0.9f33
com.apple.driver.AppleUpstreamUserClient 3.5.10
com.apple.driver.AppleIntelHD3000Graphics 8.0.0
com.apple.driver.AppleMCCSControl 1.0.33
com.apple.kext.AMDFramebuffer 8.0.0
com.apple.driver.SMCMotionSensor 3.0.2d6
com.apple.driver.ACPI_SMC_PlatformPlugin 1.0.0
com.apple.driver.AppleMikeyDriver 2.3.1f2
com.apple.driver.AppleLPC 1.6.0
com.apple.driver.AppleSMCLMU 2.0.2d0
com.apple.AMDRadeonAccelerator 1.0.0
com.apple.driver.AppleSMCPDRC 1.0.0
com.apple.driver.AppleMuxControl 3.2.11
com.apple.driver.AppleIntelSNBGraphicsFB 8.0.0
com.apple.driver.AppleUSBTCButtons 235.4
com.apple.driver.AppleUSBTCKeyboard 235.4
com.apple.driver.AppleIRController 320.15
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.BootCache 34
com.apple.driver.XsanFilter 404
com.apple.iokit.IOAHCIBlockStorage 2.2.2
com.apple.driver.AppleUSBHub 5.2.5
com.apple.iokit.AppleBCM5701Ethernet 3.2.5b3
com.apple.driver.AirPort.Brcm4331 602.15.22
com.apple.driver.AppleFWOHCI 4.9.6
com.apple.driver.AppleAHCIPort 2.4.1
com.apple.driver.AppleUSBEHCI 5.4.0
com.apple.driver.AppleEFINVRAM 1.6.1
com.apple.driver.AppleIntelCPUPowerManagementClient 196.0.0
com.apple.driver.AppleSmartBatteryManager 161.0.0
com.apple.driver.AppleACPIButtons 1.6
com.apple.driver.AppleRTC 1.5
com.apple.driver.AppleHPET 1.7
com.apple.driver.AppleSMBIOS 1.9
com.apple.driver.AppleACPIEC 1.6
com.apple.driver.AppleAPIC 1.6
com.apple.nke.applicationfirewall 4.0.39
com.apple.security.quarantine 2
com.apple.driver.AppleIntelCPUPowerManagement 196.0.0
com.apple.iokit.IOSCSIBlockCommandsDevice 3.5.1
com.apple.iokit.IOFireWireSerialBusProtocolTransport 2.1.1
com.apple.iokit.IOFireWireSBP2 4.2.0
com.apple.security.SecureRemotePassword 1.0
com.apple.kext.triggers 1.0
com.apple.iokit.IOSCSIArchitectureModelFamily 3.5.1
com.apple.iokit.IOSerialFamily 10.0.6
com.apple.driver.DspFuncLib 2.3.1f2
com.apple.iokit.IOAudioFamily 1.8.9fc10
com.apple.kext.OSvKernDSPLib 1.6
com.apple.iokit.IOSurface 86.0.3
com.apple.iokit.IOBluetoothFamily 4.0.9f33
com.apple.iokit.AppleBluetoothHCIControllerUSBTransport 4.0.9f33
com.apple.driver.IOPlatformPluginLegacy 1.0.0
com.apple.driver.AppleSMBusController 1.0.10d0
com.apple.driver.AppleSMBusPCI 1.0.10d0
com.apple.driver.AppleSMC 3.1.4d2
com.apple.iokit.IOAcceleratorFamily 19.0.26
com.apple.kext.AMD6000Controller 8.0.0
com.apple.kext.AMDSupport 8.0.0
com.apple.driver.AppleHDAController 2.3.1f2
com.apple.iokit.IOHDAFamily 2.3.1f2
com.apple.driver.IOPlatformPluginFamily 5.2.0d16
com.apple.driver.AppleGraphicsControl 3.2.11
com.apple.driver.AppleBacklightExpert 1.0.4
com.apple.iokit.IONDRVSupport 2.3.5
com.apple.iokit.IOGraphicsFamily 2.3.5
com.apple.iokit.IOFireWireIP 2.2.5
com.apple.driver.AppleThunderboltDPInAdapter 1.8.5
com.apple.driver.AppleThunderboltDPAdapterFamily 1.8.5
com.apple.driver.AppleThunderboltPCIDownAdapter 1.2.5
com.apple.driver.AppleUSBMultitouch 235.7
com.apple.iokit.IOUSBHIDDriver 5.2.5
com.apple.driver.AppleUSBMergeNub 5.2.5
com.apple.driver.AppleUSBComposite 5.2.5
com.apple.driver.CoreStorage 274.7
com.apple.driver.AppleThunderboltNHI 1.6.0
com.apple.iokit.IOThunderboltFamily 2.1.1
com.apple.iokit.IOUSBUserClient 5.2.5
com.apple.iokit.IOEthernetAVBController 1.0.2b1
com.apple.iokit.IO80211Family 500.15
com.apple.iokit.I
Model: MacBookPro8,3, BootROM MBP81.0047.B27, 4 processors, Intel Core i7, 2.2 GHz, 16 GB, SMC 1.70f5
Graphics: Intel HD Graphics 3000, Intel HD Graphics 3000, Built-In, 512 MB
Graphics: AMD Radeon HD 6750M, AMD Radeon HD 6750M, PCIe, 1024 MB
Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1333 MHz, 0x029E, 0x434D534F384758334D314131333333433920
Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1333 MHz, 0x029E, 0x434D534F384758334D314131333333433920
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xD6), Broadcom BCM43xx 1.0 (5.106.98.81.22)
Bluetooth: Version 4.0.9f33 10885, 2 service, 11 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
Serial ATA Device: APPLE SSD TS256C, 251 GB
Serial ATA Device: ST750LX003-1AC154, 750,16 GB
USB Device: hub_device, 0x0424 (SMSC), 0x2514, 0xfa100000 / 3
USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0246, 0xfa120000 / 5
USB Device: BRCM2070 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0xfa110000 / 4
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x821a, 0xfa113000 / 6
USB Device: FaceTime HD Camera (Built-in), apple_vendor_id, 0x8509, 0xfa200000 / 2
USB Device: hub_device, 0x0424 (SMSC), 0x2514, 0xfd100000 / 2
USB Device: USB Receiver, 0x046d (Logitech Inc.), 0xc51b, 0xfd130000 / 5
USB Device: iPhone, apple_vendor_id, 0x12a0, 0xfd120000 / 4
USB Device: IR Receiver, apple_vendor_id, 0x8242, 0xfd110000 / 3
FireWire Device: My Book 111D, WD, 800mbit_speedThe other day I got the blue screen, the fan going on high, and then when I disconnect my thunderbolt connection from my macbook pro - i get a shutdown.
Today I got flickering followed by the fan on high and then again I disconneced my thunderbolt cable and after a minute or two a shudown.
This never happened before. Actually I was suprised to hear about a firmware update for flickering since that's never happened to me but since updating I now get the flicker.
Any ideas?? Any help would be greatly appreciated as this is my work labtop. -
Why is my 15" rMPB crashing when using 2 Thunderbolt Displays?
Over the last few days my 2012 15" rMBP has been crashing periodically.
Today it continued to crash every few minutes, I tried resetting PRAM and SMC - didn't seem to help. After reading somewhere (not here) people having issues with Multiple external Displays, I onlly plugged in one of my 2 Thunderbolt Displays and it seems to be stable.
In my normal set up I use 2 - 27" TBD's and a 55" Sanyo TV via HDMI - it has worked great for over a year but now I am experiencing continued crashing when I have everything plugged in.
Is this a known issue?
I think this may be an issue with the last update - which was installed on my rMBP on the 9th or Jan (only 9 days ago)... that is about when I first started noticing an issue.
Is there anything I can do?Welcome to Apple Support Communities
Note that your MacBook Pro is using the dedicated GPU and you have got two GPUs. The dedicated GPU generates more heat, and even more if you are using the GPU to display image in three displays (including your built-in display). I would not be worried if fans are working correctly -
27 inch thunderbolt display blacks out after Thunderbolt Firmware Update 1.2
Bought 2 new 27 inch TB displays for two different machines and after a couple of days the Thunderbolt Firmware Update 1.2 appears on my Mac Pro with one of the displays installed. So I install the firmware update. Now my display blacks out periodically and I keep getting Graphic Display Errors with a request to sent the errors to Apple. Running a 32 GB Mac Pro (late 2013 circular style) I have three monitors connected (two 20 inch cinema displays and the new 27 inch display). This machine is supposed to be able to handle three 4k monitors or 6 standard TB displays. I've seen the posts about the blacking out with this monitor but I didn't have any problems before the firmware update and now I've got them pretty regularly. I had the blacking out problem on an earlier monitor and took one of the monitors back and Apple gave me another one and this is the replacement. Same problem, but this one only started after the update. I'm hoping someone from Apple reads these messages and can let me know what's up.
BTW, I also have an older 27 inch Apple monitor that ran perfectly on this machine so I'm disappointed that I spent all this money and now get the blacking out issue.
Mac Pro (Late 2013)
Processor 3.7 GHz Quad-Core Intel Xeon E5
Memory 32 BG
Graphics AMD FirePro D300 2048 MBI have my Thunderbolt display connected to my MacBook Pro and have been experiencing the same issue, getting worse over time. The folks at my local Apple store did not know what to do about it. So, I looked around and tried different thing.
The one thing that seems to be working is to System Preferences > Build-in Display > uncheck “Automatically adjust brightness.”
I hope this helps. -
No sound from Thunderbolt Display after update to OS X 10.9.3
So I updated to 10.9.3 this morning only to find there is no sound coming from my Thunderbolt Display after installation. Sound is now only audible from my MacBook Pro (late 2011). Also, see image below, there is no sign of any connected inputs other than my MBP now. I've shutdown and restarted a number of times, but still no audio from the display.
Really starting to wonder why it's worth spending so much on Apple products now...I sent my TB Display in for repair. They had it almost a week and didn't find anything wrong with it. Instead they took in my MacBook Pro and replaced the logic board (2nd time it had been replaced) and the Display seems to be working fine now.
...except that for using 3rd party video conf apps, those apps only pick up the MBP camera (even though i try to change settings in app), not the TBD camera... but FaceTime and Skype find the TBD camera.
Strange.
Nickkett wrote:
I Bought all Apple to be 100% compatible and "Just Work"...
I completely agree with that sentiment. That's why we pay through the nose for their products, so it feels very bad when they don't just work. -
Thunderbolt Display USB ports not working after 1.2 firmware update
I installed the Thunderbolt Display Firmware Update 1.2 a few days back, and following that update, the USB ports on my display have stopped working completely. The display's Thunderbolt port and Ethernet jacks are working fine, as is the Thunderbolt/power cable connection to my MacBook Air (mid-2011, 11 inch, running OS X Yosemite 10.10.1). Any ideas on a fix?
Do an SMC and PRAM reset.
-
IMac won't start with Thunderbolt Display connected after firmware update
After updating my thunderbolt display firmware to version 1.2 this morning via the App Store, my mid-2014 iMac won't start up with the external display connected. I can get the iMac to start up only by disconnecting the display's thunderbolt connector. After the iMac comes up, I can reconnect the display and everything appears to function normally. I've tried several restarts and the iMac won't start up with the display connected. Anyone else experience this?
Hello rameta,
It may help to reset your Mac's SMC and PRAM.
Intel-based Macs: Resetting the System Management Controller (SMC)
http://support.apple.com/kb/HT3964
Reset your computer’s PRAM
http://support.apple.com/kb/HT1379
Cheers,
Allen -
the new firmware for the thunderbolt display now is making the screen go black all the time. _the fix created the problem!!!
how do I uninstall this update?
JonYou can't. There is a long discussion in the Thunderbolt forum. Look there.
Maybe you are looking for
-
Can't get Ipod classic to work with video out to TV
I have 80gb IPOD classic,3rd gen. I bought the Dynex docking station w/video & audio out to TV kit. I have it hooked up exactly as they instuct. I also have my settings on IPOD to TV out enabled, NTSC, and captions on. But when I try and play a video
-
Is there any BAPI or FM which updates or modifies FD32 transaction
Is there any BAPI or Function module which updates or modifies the fields of FD32 transaction screens
-
I want to download Firefox for my Mac Powerbook G4, os X, older version please.
Firefox no longer works or opens on my desktop computer
-
Hello, I'm looking for a easy-to-use tool/library to be integrated into my application that is able to render a PDF page into a bmp or similar lossless image file format. Is there anybody of you guys, that can suggest me some handy product coming dir
-
Home Network Speeds Using BT Infinity ?
I have networked x2 Windows 7 computers and I'm getting 10 MB/sec speeds when transferring files between the two rigs. Is this about right or can I improve transfer speeds ? computer A = has gigabit LAN and connects to Gb port on BT Home Hub 3a compu