Random fatal crash with external display

I have an iMac 9,1 (Intel c2d @ 2.93GHz) running OSX 10.6.1
I have my Sony Bravia KDL-46W4500 hooked up to it through display-port -> hdmi adapter -> hdmi cable. 9 out of 10 times, this works great. But occasionally, when I turn on my tv (my iMac is always on before I turn on my tv), I can see the screen being detected, followed by a complete crash/freeze of my iMac. Not even a "you have to restart" screen. It just fails, epic. I think I have seen this problem also a few times with OSX 10.5.x, so it is not something new to Snow.
Anyone care to have a guess as to what is causing it?

Hi alcohol
20 or 24" iMac?
Which graphic's chip does it have?
How much RAM does it have?
Some models have a graphic's chip that shares RAM with the main memory.
Dennis

Similar Messages

  • Macbook crashes with external displays, Macbook crashes with external displays

    Dear Community,
    I have a problem with my new (Dec. 2013) Macbook Pro. Everything worked fine until two weeks ago. Then, I connected my Macbook via VGA-adapter (original) with an LCD Monitor at home (I had done this before without any problems). My Mac froze and nothing happened, so I had to reboot it manually (press the on/off button 5 seconds). The Macbook would show a grey display und would not reboot, no matter what I tried. The secure boot program did not work, either. I could start it with disk utility and load my last time machine backup.
    After I did this, everything worked fine again. Last week I tried to connect my Mac with another LCD display at work (which had also worked fine before). Same error! Mac froze and nothing worked and I had to load a backup again.
    I brought my Mac to the next Apple store, where a hardware check revealed no defects.
    Nonetheless, they exchanged the logic board and told me everything was fine, again.
    Today, I have worked the whole day using my external display at work. Everything was ok, but I could only use the external display and not the Notebook display. When I tried to sync the two monitors to work with the Mac and the external display together – same error!
    I have called the Apple store, but they had no idea and just told me that the Apple warranty does not cover third-party displays. The Apple hotline suggested looking for a driver for the external displays, but there are none. And again: Until two weeks ago, everything worked without problems.
    Has anybody an idea what to do with this?
    Julia

    I was searching and found that the Matrox DualHead2Go maybe work. Any idea?
    Thanks

  • No Wireless Internet with External Display, Other Issues

    Hello,
    When I connect an external monitor to my MBA, I lose my connection to the Internet. The wi-fi signal remains strong, but pages will not load (I tried many) and I cannot retrieve email. The connection times out when I try to ping as well. This occurs whether I have the MBA open or closed. The loss of Internet happens immediately when I connect an external display using the supplied dongle, and returns the moment I disconnect it. It is clearly an issue with external displays.
    On the advice of an Apple Genius, I also tried disabling bluetooth. I did so, and turned off all my bluetooth devices (Apple keyboard and mouse, iPhone), but the problems persist.
    The other trouble I am having is difficulty connecting to a network for the first time in a session. In other words, I was connected all day yesterday, take the MBA home, and return to the office the next day. MBA takes a long time to see the network, then fails to accept the password. If I carry the MBA closer to the wireless router, it finds and connects automatically as I'd saved my password. When I return to my desk, I remain connected with full signal strength. This has happened in two locations, one with an Airport Extreme, the other with a Netopia 802.11g router. When my Macbook Pro is sitting right next to the MBA, it recognizes and connects to the same networks almost instantaneously.
    Anyone have any suggestions? Much appreciated.

    Just a quick update... I was on the phone with Apple Support on Saturday morning and I thought we were making progress. The basic idea behind the proposed solution was that there was some "Preferences" that were causing the problem. We started over with a clean Preferences folder and tried connecting up the external monitor. At first, this approach was showing progress. The suggestion was to copy over my original Preferences (I had made a backup copy) just a few at a time until we figured out which ones caused the problem. The problem with this approach is that immediately after I got off the phone, the internet started not to work again. So, even with a clean Preferences folder, the internet would quit working after connecting up the external monitor.
    So, I'm back to the drawing board. I have since restored my Preferences folder and I don't have my external monitor and internet working at the same time. BTW, I also upgraded to 10.5.3 and it didn't help.
    Still bummed,
    Kevin

  • Help with external displays

    Just installed Lion and afterward I noticed that things work differently with external displays. In the past I could have my laptop open to mirror but now it must be  shut and the mirrior button or selection isn't available within the display preferences. So my question is, 1. does any one know how to better manage displays? and 2. does anyone know how to mirror while having the laptop screen open?
    I know trhis sounds petty but where I work it is very hot and it seems like with the screen shut the computer syncs heat away a lot less efficiently.
    Thanks

    Thanks,
    I now know how to turn on and off mirrioring with command/F1 (didn't know that yet), but would you know how I can use my external display in mirror mode with the laptop display completely turned off, not dimmed till black, but off?
    Before lion I was able to do this by shutting the laptop screen which would put the machine  into sleep mode and then  by clicking the mouse or hitting a key on the keyboard it would wake it. Once the external display came on then I would open the laptop and the laptop display would remain off while using the external display. Hope that makes sense. Any suggestions?

  • MBP Retina low performance with external displays

    Hi everyone!
    I have a very bad performance with my MBP 15´´ retina display when it comes to ad an external display. I have a FUL HD LG monitor that looks very bad when i connect the HDMI or the thunderbot port with the proper adapter (as bad as you can´t even read). I want to know if this may ba a hardware problem just with my computer or if it is a software problem, any ideas? does anyone have the same issue?
    How can i update my NVIDIA card???
    Thanks a lot!

    Topic seems to come up here often. Apple has a tendency to dismiss the issue.
    Its a pretty well known problem that Mac font smoothing doesn't seem to work well on high resolution third party external displays, making text hard to read. In addition, I think the Mac HDMI resolution support is limited to 1080p, so you must use DP or DVI video interfaces to see full monitor resolution.
    The OS default is no font smoothing on external displays (except perhaps the apple display). There is a terminal command that will enable font smoothing for any external monitor, but it often doesn't work well enough. I found that using the OS zoom feature magnifies text to the point to be easily readable. You can set zoom parameters in the accessibility systems preference panel.
    For some reason, sometimes the Mac OS thinks some monitors are TVs and use YCbCr instead of RGB. You can open the color sync utility and brouse the settings to see what is being used. There are scripts available that can fix that but are more complicated to install than an app.
    It seems that PCs are way ahead of Macs with external display implementation. Most folks having monitor problems with a Mac do not see the same issue with PCs or Unix/Linux OSs.
    Oh as far as updating the video card, can't. The monitor  "drivers" are built into the OS. When a new display is connected, the OS finds the profile for it.

  • MBP randomly crashes when in clamshell with external display

    Hi Mac people.
    As described in the "subject field" i have been encountering some random crashes after i startet using my MBP in clamshell with my newly pruchased 24" 16:10 NEC display .
    typically it occurs after about 10-20 minutes of playing world of warcraft.
    -the screen goes black, saying no signal, and the MBP doesn't react to anything else but holding down the on/off button.
    i have tried using the key combination alt-cmd-eject to see if i could make the computer sleep and then turn it on by opening the lid.-getting it out of clamshell to get the built-in display active again.
    but none of that worked.
    i also checked the dvi<->mini-displayport adapter for lose connections but i didn't find any
    i have had my NEC display for about a month, and the problem has occured about 8 times now.
    befor i started using my MBP in clamshell with an external display, i had no problems.
    Interval Since Last Panic Report: 73505 sec
    Panics Since Last Report: 3
    Anonymous UUID: C8DD4168-ECC7-4842-9EF5-233F8D9763C9
    Fri Jan 7 11:41:39 2011
    panic(cpu 0 caller 0x00C566A4): NVRM[0]: Read Error 0x00009410: BAR0 0xa4000000 0x3f92e000 0x096380c1 D0 P3/4
    Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)
    0x304fad98 : 0x12b4c6 (0x45f91c 0x304fadcc 0x13355c 0x0)
    0x304fade8 : 0xc566a4 (0xe86e80 0xe86e80 0xe4b6d4 0x0)
    0x304fae48 : 0xf0fdf0 (0x539a004 0x533c804 0x9410 0xc92d06)
    0x304fae88 : 0xf3a57d (0x533c804 0x9410 0x5c00 0x9)
    0x304faec8 : 0xd5814f (0x533c804 0x46eb004 0x0 0x0)
    0x304faee8 : 0xc983f1 (0x46eb004 0x304faf74 0x0 0x0)
    0x304faf28 : 0xeabdb8 (0x533c804 0x3d0900 0x304faf74 0x0)
    0x304fafa8 : 0xee10e4 (0x533c804 0x54a1804 0x1 0x1)
    0x304fb138 : 0xee5479 (0x533c804 0x54a2004 0x4bc6a44 0x0)
    0x304fb298 : 0xca227b (0x533c804 0x54a2004 0x0 0x8b46184)
    0x304fb348 : 0xc63a19 (0xc1d00041 0xbeef0003 0xcafe1691 0x8b46300)
    0x304fb3b8 : 0xc547ed (0x304fb548 0x6 0x0 0x0)
    0x304fb518 : 0xc462d4 (0x0 0x600d600d 0x7057 0x304fb548)
    0x304fb5d8 : 0x114c77b (0xc1d00041 0xbeef0003 0xcafe1691 0x8b46300)
    0x304fb658 : 0x114ca53 (0x20552000 0x8b46300 0x8b48404 0x0)
    0x304fb698 : 0x11136e7 (0x20552000 0x8b48400 0x304fb6a8 0x20555068)
    Backtrace continues...
    Kernel loadable modules in backtrace (with dependencies):
    com.apple.GeForce(5.4.8)@0x10f9000->0x1190fff
    dependency: com.apple.NVDAResman(5.4.8)@0xc3d000
    dependency: com.apple.iokit.IONDRVSupport(1.7.3)@0xc2f000
    dependency: com.apple.iokit.IOPCIFamily(2.6)@0x63e000
    dependency: com.apple.iokit.IOGraphicsFamily(1.7.3)@0x791000
    com.apple.nvidia.nv50hal(5.4.8)@0xe9c000->0x10effff
    dependency: com.apple.NVDAResman(5.4.8)@0xc3d000
    com.apple.NVDAResman(5.4.8)@0xc3d000->0xe9bfff
    dependency: com.apple.iokit.IONDRVSupport(1.7.3)@0xc2f000
    dependency: com.apple.iokit.IOPCIFamily(2.6)@0x63e000
    dependency: com.apple.iokit.IOGraphicsFamily(1.7.3)@0x791000
    BSD process name corresponding to current thread: World of Warcraf
    Mac OS version:
    9L30
    Kernel version:
    Darwin Kernel Version 9.8.0: Wed Jul 15 16:55:01 PDT 2009; root:xnu-1228.15.4~1/RELEASE_I386
    System model name: MacBookPro5,1 (Mac-F42D86C8)
    System uptime in nanoseconds: 565038856165
    unloaded kexts:
    com.apple.driver.InternalModemSupport 2.4.0 - last unloaded 149627740291
    loaded kexts:
    com.apple.filesystems.cddafs 2.3.0 - last loaded 171968100440
    com.apple.driver.AppleHWSensor 1.9d0
    com.apple.filesystems.ntfs 2.1
    com.apple.filesystems.autofs 2.0.2
    com.apple.driver.AppleUSBTCButtons 1.7.4f1
    com.apple.driver.AppleMikeyHIDDriver 1.0.6
    com.apple.driver.AppleUpstreamUserClient 2.7.5
    com.apple.driver.AppleMikeyDriver 1.7.1a2
    com.apple.driver.AppleHDA 1.7.1a2
    com.apple.driver.AGPM 100.8.7
    com.apple.driver.AppleHDAController 1.7.1a2
    com.apple.iokit.IOBluetoothSerialManager 2.1.9f10
    com.apple.driver.SMCMotionSensor 2.1.1d2
    com.apple.DontSteal_Mac_OSX 6.0.3
    com.apple.iokit.IOFireWireIP 1.7.7
    com.apple.driver.AppleIRController 113
    com.apple.driver.AudioIPCDriver 1.0.6
    com.apple.kext.AppleSMCLMU 1.4.5d1
    com.apple.driver.AppleGraphicsControl 2.8.15
    com.apple.driver.ACPISMCPlatformPlugin 3.4.0a17
    com.apple.driver.NVSMU 1.1.7
    com.apple.driver.AppleSMBusPCI 1.0.1d1
    com.apple.driver.AppleLPC 1.3.1
    com.apple.GeForce 5.4.8
    com.apple.nvidia.nv50hal 5.4.8
    com.apple.driver.AppleUSBMultitouch 189.35
    com.apple.driver.AppleUSBTCKeyboard 1.7.4f1
    com.apple.driver.AppleHIDKeyboard 1.0.9b4
    com.apple.driver.BroadcomUSBBluetoothHCIController 2.1.9f10
    com.apple.driver.AppleUSBMergeNub 3.5.2
    com.apple.iokit.IOSCSIMultimediaCommandsDevice 2.1.1
    com.apple.iokit.SCSITaskUserClient 2.1.1
    com.apple.driver.XsanFilter 2.7.91
    com.apple.iokit.IOAHCISerialATAPI 1.1.2
    com.apple.iokit.IOAHCIBlockStorage 1.2.3
    com.apple.driver.AppleAHCIPort 1.7.0
    com.apple.driver.AppleUSBHub 3.4.9
    com.apple.iokit.IOUSBUserClient 3.5.2
    com.apple.driver.AirPortBrcm43xx 365.91.19
    com.apple.driver.AppleFWOHCI 3.9.7
    com.apple.nvenet 1.0.54
    com.apple.driver.AppleUSBEHCI 3.4.6
    com.apple.driver.AppleUSBOHCI 3.4.6
    com.apple.driver.AppleEFINVRAM 1.2.0
    com.apple.driver.AppleSmartBatteryManager 158.10.5
    com.apple.driver.AppleRTC 1.2.3
    com.apple.driver.AppleHPET 1.4
    com.apple.driver.AppleACPIPCI 1.2.5
    com.apple.driver.AppleACPIButtons 1.2.5
    com.apple.driver.AppleSMBIOS 1.4
    com.apple.driver.AppleACPIEC 1.2.5
    com.apple.driver.AppleAPIC 1.4
    com.apple.security.seatbelt 107.12
    com.apple.nke.applicationfirewall 1.8.77
    com.apple.security.TMSafetyNet 3
    com.apple.driver.AppleIntelCPUPowerManagement 76.2.0
    com.apple.driver.DiskImages 199
    com.apple.BootCache 30.4
    com.apple.driver.DspFuncLib 1.7.1a2
    com.apple.driver.AppleSMBusController 1.0.1d1
    com.apple.iokit.IOHDAFamily 1.7.1a2
    com.apple.iokit.IOSerialFamily 9.4
    com.apple.iokit.IOAudioFamily 1.6.9fc5
    com.apple.kext.OSvKernDSPLib 1.1
    com.apple.driver.IOPlatformPluginFamily 3.4.0a17
    com.apple.NVDAResman 5.4.8
    com.apple.iokit.IONDRVSupport 1.7.3
    com.apple.iokit.IOGraphicsFamily 1.7.3
    com.apple.driver.AppleSMC 2.3.1d1
    com.apple.iokit.IOUSBHIDDriver 3.4.6
    com.apple.driver.AppleUSBBluetoothHCIController 2.1.9f10
    com.apple.iokit.IOBluetoothFamily 2.1.9f10
    com.apple.driver.AppleUSBComposite 3.2.0
    com.apple.iokit.IOSCSIBlockCommandsDevice 2.1.1
    com.apple.iokit.IOBDStorageFamily 1.5
    com.apple.iokit.IODVDStorageFamily 1.5
    com.apple.iokit.IOCDStorageFamily 1.5
    com.apple.iokit.IOSCSIArchitectureModelFamily 2.1.1
    com.apple.iokit.IOAHCIFamily 1.5.0
    com.apple.iokit.IO80211Family 216.1
    com.apple.iokit.IOFireWireFamily 3.4.9
    com.apple.iokit.IONetworkingFamily 1.6.1
    com.apple.iokit.IOUSBFamily 3.5.2
    com.apple.driver.AppleEFIRuntime 1.2.0
    com.apple.iokit.IOSMBusFamily 1.1
    com.apple.iokit.IOStorageFamily 1.5.6
    com.apple.iokit.IOHIDFamily 1.5.5
    com.apple.driver.AppleACPIPlatform 1.2.5
    com.apple.iokit.IOPCIFamily 2.6
    com.apple.iokit.IOACPIFamily 1.2.0
    Any help would be much appreciated

    Lets give it a try. 1st of all post your s/n (so I can run a check on your specific model) or check with system profiler if your machine has the NVidia Geforce 8600 M GT. Or see for yourself: http://www.chipmunk.nl/cgi-fast/applemodel.cgi
    IF SO:
    Surely, you've heard about the generic problems with this specific video chip: sooner or later most of them will fail due to chip packaging/bonding issues. If yours has not failed before, it may be doing so now because you're driving it harder with a larger external monitor attached, thus probably running the affected videochip hotter. Very useful link: http://www.xlr8yourmac.com/feedback/MacBookProvideofailure.html#novideotip , loads of other useful links on the subject therein.
    To solve this, Apple has instigated an extended warranty, so do not tread on the tail of your machine's capabilities any more. Once it will not boot (which may eventually happen), it gets really hard to run diagnostics. Have it checked by at least 1, preferably more ASPs (see link), and kindly ask them to reiterate the test 2 or 3 times. Often, the problem will not show up on the 1st try.
    I am reading increasing numbers of questions and complaints about this on the Flemish/Belgian Apple forum "Intermactivity", most users seem to be unaware of the problem (though this has been common knowledge for years), and moreover, most ASPs are reluctant to acknowledge it.
    So if your machine is one of the affected, you will really have to stand your case. Especially in Europe!

  • Using hdmi with external display crashes mac pro

    I have late 2013 model Macbook pro. I have connected it via HDMI plug to external display via hdmi bridge. The other device connected to this hdmi bridge is a pc. Everything works fine until pc enters sleep mode, and switches display off. The result is immediate crash of my mbp either with reboot, or with screen requiring me to push power button long enough. Interestingly this problem seems not to appear if I am using this 30 bucks thunderbolt hdmi adapter. I am kind of infurious that my over 2 k MBP is crashing all the time. As the full-hd display works perfectly with PC, and with this extra adapter - what is the problem with my shiny premium MBP? anything to avoid this?

    An articulating VESA mount and a cheap display or this Dell would be far simpler. The iMac G4 20" had to be specially weighted to hold just a 20" panel. 
    This Dell in particular has a host of display connectors that Apple doesn't offer on it's panels so multiple devices can be connected simultaneously:
    http://accessories.us.dell.com/sna/productdetail.aspx?sku=223-4890&cs=19&c=us&l= en&dgc=SS&cid=27530&lid=627063
    cheers
    mrtotes

  • Photoshop 2014 crashing unless external display is present

    Hello -
    Running Photoshop CC 2014 on a 2013 Macbook Pro Retina Display. 16 gb ram, OS X 10.9.5 with all software updates installed as of Nov 1 2014. Recently, I've discovered that Photoshop crashes on startup if my Macbook Pro is not connected to an external display. *any* external display connected remedies the problem if it's set at the primary display, and Photoshop starts up just fine. Photoshop is the only CC 2014 app giving me this issue. Photoshop CC doesn't - it launches fine without an external display connected.
    I have tried a complete uninstall of Photoshop CC 2014 and reinstall, even used Adobe's clean uninstall tool. Have tried removing Photoshop preferences. Have disabled 3rd party plugins. Have started in "safe mode." Have turned off Extensis Suitcase's auto-activation plugin. Have tried without Suitcase open at all. Nothing has remedied the problem except for having ANY external display connected and designated as the primary display.
    Will post my error log - wondered if anyone else has experienced this?

    Error report from when this happens is below. Hoping something stands out to someone here for a remedy?
    Process:         Adobe Photoshop CC 2014 [536]
    Path:            /Applications/Adobe Photoshop CC 2014/Adobe Photoshop CC 2014.app/Contents/MacOS/Adobe Photoshop CC 2014
    Identifier:      com.adobe.Photoshop
    Version:         15.2.1 (15.2.1.257)
    Code Type:       X86-64 (Native)
    Parent Process:  launchd [153]
    Responsible:     Adobe Photoshop CC 2014 [536]
    User ID:         502
    Date/Time:       2014-11-01 22:12:06.764 -0500
    OS Version:      Mac OS X 10.9.5 (13F34)
    Report Version:  11
    Anonymous UUID:  E5B6AC5D-74CE-231A-3696-6D8742E43C11
    Crashed Thread:  0  Main Thread  Dispatch queue: com.apple.main-thread
    Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000050
    VM Regions Near 0x50:
    -->
        __TEXT                 000000010c67e000-0000000110f59000 [ 72.9M] r-x/rwx SM=COW  /Applications/Adobe Photoshop CC 2014/Adobe Photoshop CC 2014.app/Contents/MacOS/Adobe Photoshop CC 2014
    Thread 0 Crashed:: Main Thread  Dispatch queue: com.apple.main-thread
    0   com.extensis.AutoActivationPlugin.PS15 0x00000001bccf5bb8 CTFontDescriptorCopyAttributeOverride(__CTFontDescriptor const*, __CFString const*) + 44
    1   com.apple.CoreText             0x00007fff923e031c TFont::InitMatrix(CGAffineTransform const*, __CTFontDescriptor const*) + 112
    2   com.apple.CoreText             0x00007fff923dff80 TFont::TFont(__CTFontDescriptor const*, double, CGAffineTransform const*, __CTFontDescriptor const*) + 70
    3   com.apple.CoreText             0x00007fff923dce8e CTFontCreateWithFontDescriptor + 114
    4   com.apple.AppKit               0x00007fff924ea6ed -[__NSSharedFontInstanceInfo _platformFont] + 573
    5   com.apple.AppKit               0x00007fff924ea195 -[__NSSharedFontInstanceInfo _textTransform] + 33
    6   com.apple.AppKit               0x00007fff924ea163 -[__NSSharedFontInstanceInfo _matrix] + 22
    7   com.apple.AppKit               0x00007fff924ea0b9 -[NSFont initWithInstanceInfo:renderingMode:] + 105
    8   com.apple.AppKit               0x00007fff924e9dea -[__NSSharedFontInstanceInfo fontInstanceForRenderingMode:] + 383
    9   com.apple.AppKit               0x00007fff924e9ae9 -[__NSFontTypefaceInfo fontInstanceForFontDescriptor:size:affineTransform:renderingMode:] + 671
    10  com.apple.AppKit               0x00007fff9251a346 -[NSFont initWithCoder:] + 1731
    11  com.apple.Foundation           0x00007fff950e1522 _decodeObjectBinary + 2534
    12  com.apple.Foundation           0x00007fff950e09dd _decodeObject + 288
    13  com.apple.AppKit               0x00007fff92541489 -[NSButtonCell initWithCoder:] + 224
    14  com.apple.Foundation           0x00007fff950e1522 _decodeObjectBinary + 2534
    15  com.apple.Foundation           0x00007fff950e09dd _decodeObject + 288
    16  com.apple.AppKit               0x00007fff92516e26 -[NSControl initWithCoder:] + 265
    17  com.apple.AppKit               0x00007fff92539ca2 -[NSButton initWithCoder:] + 44
    18  com.apple.Foundation           0x00007fff950e1522 _decodeObjectBinary + 2534
    19  com.apple.Foundation           0x00007fff950e262f -[NSKeyedUnarchiver _decodeArrayOfObjectsForKey:] + 1774
    20  com.apple.Foundation           0x00007fff950e282b -[NSArray(NSArray) initWithCoder:] + 202
    21  com.apple.Foundation           0x00007fff950e1522 _decodeObjectBinary + 2534
    22  com.apple.Foundation           0x00007fff950e09dd _decodeObject + 288
    23  com.apple.AppKit               0x00007fff924d05ac -[NSView initWithCoder:] + 1949
    24  com.apple.AppKit               0x00007fff924d2294 -[NSClassSwapper initWithCoder:] + 528
    25  com.apple.Foundation           0x00007fff950e1522 _decodeObjectBinary + 2534
    26  com.apple.Foundation           0x00007fff950e09dd _decodeObject + 288
    27  com.apple.AppKit               0x00007fff924d1cb8 -[NSResponder initWithCoder:] + 63
    28  com.apple.AppKit               0x00007fff924cfe6f -[NSView initWithCoder:] + 96
    29  com.apple.AppKit               0x00007fff92516d50 -[NSControl initWithCoder:] + 51
    30  com.apple.AppKit               0x00007fff92539ca2 -[NSButton initWithCoder:] + 44
    31  com.apple.Foundation           0x00007fff950e1522 _decodeObjectBinary + 2534
    32  com.apple.Foundation           0x00007fff950e09dd _decodeObject + 288
    33  com.apple.AppKit               0x00007fff924a9ccd -[NSNibConnector initWithCoder:] + 106
    34  com.apple.AppKit               0x00007fff924a9b4e -[NSNibOutletConnector initWithCoder:] + 73
    35  com.apple.Foundation           0x00007fff950e1522 _decodeObjectBinary + 2534
    36  com.apple.Foundation           0x00007fff950e262f -[NSKeyedUnarchiver _decodeArrayOfObjectsForKey:] + 1774
    37  com.apple.Foundation           0x00007fff950e282b -[NSArray(NSArray) initWithCoder:] + 202
    38  com.apple.Foundation           0x00007fff950e1522 _decodeObjectBinary + 2534
    39  com.apple.Foundation           0x00007fff950e09dd _decodeObject + 288
    40  com.apple.AppKit               0x00007fff924a8782 -[NSIBObjectData initWithCoder:] + 205
    41  com.apple.Foundation           0x00007fff950e1522 _decodeObjectBinary + 2534
    42  com.apple.Foundation           0x00007fff950e09dd _decodeObject + 288
    43  com.apple.AppKit               0x00007fff924a856f loadNib + 232
    44  com.apple.AppKit               0x00007fff924a7b6c +[NSBundle(NSNibLoading) _loadNibFile:nameTable:withZone:ownerBundle:] + 288
    45  com.apple.AppKit               0x00007fff9273c4d2 +[NSBundle(NSNibLoading) loadNibFile:externalNameTable:withZone:] + 140
    46  com.apple.AppKit               0x00007fff92813e3c _NXLoadNib + 193
    47  com.apple.AppKit               0x00007fff9281384f -[NSAlert init] + 95
    48  com.adobe.Photoshop           0x000000010c71472c 0x10c67e000 + 616236
    49  com.adobe.Photoshop           0x000000010c7145b8 0x10c67e000 + 615864
    50  com.adobe.Photoshop           0x000000010c77da13 0x10c67e000 + 1047059
    51  com.adobe.Photoshop           0x000000010c77e68a 0x10c67e000 + 1050250
    52  com.adobe.Photoshop           0x000000010c71b088 0x10c67e000 + 643208
    53  com.adobe.Photoshop           0x000000010c9bd67b 0x10c67e000 + 3405435
    54  com.adobe.Photoshop           0x000000010c9bd829 0x10c67e000 + 3405865
    55  com.adobe.Photoshop           0x000000010c680d34 0x10c67e000 + 11572
    Thread 1:: Dispatch queue: com.apple.libdispatch-manager
    0   libsystem_kernel.dylib         0x00007fff8d589662 kevent64 + 10
    1   libdispatch.dylib             0x00007fff8b6af421 _dispatch_mgr_invoke + 239
    2   libdispatch.dylib             0x00007fff8b6af136 _dispatch_mgr_thread + 52
    Thread 2:
    0   libsystem_kernel.dylib         0x00007fff8d588e6a __workq_kernreturn + 10
    1   libsystem_pthread.dylib       0x00007fff8daf9f08 _pthread_wqthread + 330
    2   libsystem_pthread.dylib       0x00007fff8dafcfb9 start_wqthread + 13
    Thread 3:
    0   libsystem_kernel.dylib         0x00007fff8d588e6a __workq_kernreturn + 10
    1   libsystem_pthread.dylib       0x00007fff8daf9f08 _pthread_wqthread + 330
    2   libsystem_pthread.dylib       0x00007fff8dafcfb9 start_wqthread + 13
    Thread 4:
    0   libsystem_kernel.dylib         0x00007fff8d588e6a __workq_kernreturn + 10
    1   libsystem_pthread.dylib       0x00007fff8daf9f08 _pthread_wqthread + 330
    2   libsystem_pthread.dylib       0x00007fff8dafcfb9 start_wqthread + 13
    Thread 5:
    0   libsystem_kernel.dylib         0x00007fff8d588e6a __workq_kernreturn + 10
    1   libsystem_pthread.dylib       0x00007fff8daf9f08 _pthread_wqthread + 330
    2   libsystem_pthread.dylib       0x00007fff8dafcfb9 start_wqthread + 13
    Thread 6:
    0   libsystem_kernel.dylib         0x00007fff8d588e6a __workq_kernreturn + 10
    1   libsystem_pthread.dylib       0x00007fff8daf9f08 _pthread_wqthread + 330
    2   libsystem_pthread.dylib       0x00007fff8dafcfb9 start_wqthread + 13
    Thread 7:
    0   libsystem_kernel.dylib         0x00007fff8d588e6a __workq_kernreturn + 10
    1   libsystem_pthread.dylib       0x00007fff8daf9f08 _pthread_wqthread + 330
    2   libsystem_pthread.dylib       0x00007fff8dafcfb9 start_wqthread + 13
    Thread 8:
    0   libsystem_kernel.dylib         0x00007fff8d588e6a __workq_kernreturn + 10
    1   libsystem_pthread.dylib       0x00007fff8daf9f08 _pthread_wqthread + 330
    2   libsystem_pthread.dylib       0x00007fff8dafcfb9 start_wqthread + 13
    Thread 9:
    0   libsystem_kernel.dylib         0x00007fff8d584a56 semaphore_wait_trap + 10
    1   libtbb.dylib                   0x0000000111c60550 tbb::internal::rml::private_worker::thread_routine(void*) + 480
    2   libsystem_pthread.dylib       0x00007fff8daf8899 _pthread_body + 138
    3   libsystem_pthread.dylib       0x00007fff8daf872a _pthread_start + 137
    4   libsystem_pthread.dylib       0x00007fff8dafcfc9 thread_start + 13
    Thread 10:
    0   libsystem_kernel.dylib         0x00007fff8d584a56 semaphore_wait_trap + 10
    1   libtbb.dylib                   0x0000000111c60550 tbb::internal::rml::private_worker::thread_routine(void*) + 480
    2   libsystem_pthread.dylib       0x00007fff8daf8899 _pthread_body + 138
    3   libsystem_pthread.dylib       0x00007fff8daf872a _pthread_start + 137
    4   libsystem_pthread.dylib       0x00007fff8dafcfc9 thread_start + 13
    Thread 11:
    0   libsystem_kernel.dylib         0x00007fff8d584a56 semaphore_wait_trap + 10
    1   libtbb.dylib                   0x0000000111c60550 tbb::internal::rml::private_worker::thread_routine(void*) + 480
    2   libsystem_pthread.dylib       0x00007fff8daf8899 _pthread_body + 138
    3   libsystem_pthread.dylib       0x00007fff8daf872a _pthread_start + 137
    4   libsystem_pthread.dylib       0x00007fff8dafcfc9 thread_start + 13
    Thread 12:
    0   libsystem_kernel.dylib         0x00007fff8d584a56 semaphore_wait_trap + 10
    1   libtbb.dylib                   0x0000000111c60550 tbb::internal::rml::private_worker::thread_routine(void*) + 480
    2   libsystem_pthread.dylib       0x00007fff8daf8899 _pthread_body + 138
    3   libsystem_pthread.dylib       0x00007fff8daf872a _pthread_start + 137
    4   libsystem_pthread.dylib       0x00007fff8dafcfc9 thread_start + 13
    Thread 13:
    0   libsystem_kernel.dylib         0x00007fff8d584a56 semaphore_wait_trap + 10
    1   libtbb.dylib                   0x0000000111c60550 tbb::internal::rml::private_worker::thread_routine(void*) + 480
    2   libsystem_pthread.dylib       0x00007fff8daf8899 _pthread_body + 138
    3   libsystem_pthread.dylib       0x00007fff8daf872a _pthread_start + 137
    4   libsystem_pthread.dylib       0x00007fff8dafcfc9 thread_start + 13
    Thread 14:
    0   libsystem_kernel.dylib         0x00007fff8d584a56 semaphore_wait_trap + 10
    1   libtbb.dylib                   0x0000000111c60550 tbb::internal::rml::private_worker::thread_routine(void*) + 480
    2   libsystem_pthread.dylib       0x00007fff8daf8899 _pthread_body + 138
    3   libsystem_pthread.dylib       0x00007fff8daf872a _pthread_start + 137
    4   libsystem_pthread.dylib       0x00007fff8dafcfc9 thread_start + 13
    Thread 15:
    0   libsystem_kernel.dylib         0x00007fff8d584a56 semaphore_wait_trap + 10
    1   libtbb.dylib                   0x0000000111c60550 tbb::internal::rml::private_worker::thread_routine(void*) + 480
    2   libsystem_pthread.dylib       0x00007fff8daf8899 _pthread_body + 138
    3   libsystem_pthread.dylib       0x00007fff8daf872a _pthread_start + 137
    4   libsystem_pthread.dylib       0x00007fff8dafcfc9 thread_start + 13
    Thread 16:: com.apple.CFSocket.private
    0   libsystem_kernel.dylib         0x00007fff8d5889aa __select + 10
    1   com.apple.CoreFoundation       0x00007fff8f408a03 __CFSocketManager + 867
    2   libsystem_pthread.dylib       0x00007fff8daf8899 _pthread_body + 138
    3   libsystem_pthread.dylib       0x00007fff8daf872a _pthread_start + 137
    4   libsystem_pthread.dylib       0x00007fff8dafcfc9 thread_start + 13
    Thread 0 crashed with X86 Thread State (64-bit):
      rax: 0x0000000000000000  rbx: 0x00007fff7c688680  rcx: 0x0000000000010f80  rdx: 0x0000610000086180
      rdi: 0x0000610000086180  rsi: 0x00007fff7c688680  rbp: 0x00007fff5357e2e0  rsp: 0x00007fff5357e2c0
       r8: 0x00007fff9249331e   r9: 0x0000000000000032  r10: 0x00007fff92493306  r11: 0x00007fff9249331e
      r12: 0x0000000000000000  r13: 0x0000610000086180  r14: 0x0000610000086180  r15: 0x0000000000000000
      rip: 0x00000001bccf5bb8  rfl: 0x0000000000010202  cr2: 0x0000000000000050
    Logical CPU:     0
    Error Code:      0x00000004
    Trap Number:     14

  • Macbook pro retina quit working with external displays

    Just got a new external display, and can't get it to work with my MBP. I tried it via the mini display port and also via the HDMI connection. Then I tried to use my flatscreen tv just to test things out via HDMI and now that doesn't work either, I've done that quite a bit in the past. The only thing thats changed is I updated to Yosemite. I even tried different cables.
    Thoughts?
    Txs,
    Jeff

    When I unplug the cable from the mac, the monitor does display this message:
    "No Display Port Cable"
    So it does seem like the display knows that its connected to a mac, just nothing shows up. Don't get anything in System Prefs > Displays either.

  • MacBook Pro with external display sometimes

    I want to use my MacBook Pro with my external display (Apple 23 inch Cinema) when I'm at my office, and to have Spaces set up and optimized for that. When I'm at home or on the road, I want Spaces set up differently, optimized for the MacBook Pro display only (no external display). Can I do this? Do I need to set up separate accounts on the MBP to do this, or can I do it some other way? Can you have sets, or multiple instances of Spaces? Otherwise, I want both options -- at work with MBP display plus Apple 23 inch Cinema or MBP display only -- to be able to access all of my files and software. The only real difference in the two setups would be the amount of screen real estate and where/how Spaces works within these different screen "landscapes."

    You will always have to use the power button to turn it on, and you'll have to open the display for that.
    Apple supports using the machine with its display closed, provided you follow the instructions in this article. As long as you do that, it shouldn't cause any harm. But I wouldn't recommend seeing how hot you can get the MBP with the display closed.

  • Update to 10.6.8 colour problems with external display

    I have a mid-2010 13" macbook pro. I use a mini DVI to HDMI adaptor to connect to my Philips LCD TV. It has always worked perfectly including audio. Since update to 10.6.8 (yesterday) there is a colour-cast on the external display that makes it unusable. I have tried a hard reset of the mac with no effect except that the colour cast changed from green to red (strange!).
    Anyone had a similar problem or have any ideas how I could solve it? (no time machine so I can't downgrade unfortunately)

    Though I am using and iMac 27 and not a macbook, I have the similar issues since the 10.6.8 update.
    I too am using the adapter to connect to a Philips 42' LCD.
    You can see my post here: (has a pic of what my TV image now looks like since update.)
    https://discussions.apple.com/message/15488605#15488605
    I ended up going back to 10.6.7, not a fix, but no other alternative..
    I used to have this problem a year ago on a PC that happened to have the same ATi Graphics card. I just used the ATI control center and changed a setting to YBR component or something like that in some color settings. But unfortunately we don't have the ATI control panel for mac, least I don't think we have any kind of alternative, but would prolly fix it..

  • Unable to install OS X 10.4 with external display

    My display died quite awhile ago (broken hinges, broken cables, etc etc) but since then I've used an external LCD display without problems. Once I set the display to mirror, everything has been working great.
    However, I tried to install OS X 10.4 and discovered that, after booting up from the disc, the install program wants to display everything only on the nonexistent original monitor. If I keep moving the mouse to the right, it eventually appears on my external monitor. But pressing F7 won't toggle back to mirror mode -- the toggle capability seems to be disabled or something.
    Any suggestions? Is there some way (hardware-based or maybe command line?) to tell the machine that the original display no longer exists and to only use the external display?
    Thanks for any help!

    Hi, llkohler. The limited-purpose OS on the installer disc that underlies the installer application and boots the computer probably doesn't expect to have its life complicated by a second monitor, and doesn't contain the code that would allow you to toggle the display mode. If I were you, I'd look to connnect the Powerbook to another Mac in Firewire Target Disk Mode (with the PB as the Target) and perform the installation on it from the host Mac. Once you get Tiger installed, you should be able to toggle the display mode on it in the usual way.

  • Won't boot with external display connected

    My MacBook Pro (circa 1997) won't boot with the external display connected. I can connect the external display (20in flat planel) after it has started, and it works just fine.
    I have tried two different DVI cables (one of which I think is a DVI-A cable) and the DVI-to-VGA cable. The result is the same.
    During the boot phase I get the tone, the apple logo and the progress wheel. After 30 seconds to one minute those disappear to be replaced by an empty blue screen.

    In case anyone wonders, my "solution" was to change to a WB Elements Desktop 3TB (only USB 2.0 is currently available for this model). I miss the speed of USB 3.0, but it's much nicer to not have to remember to unplug and plug in the hard drive each time I boot.
    Still hoping to see a proper solution to this (since I don't have the WB My Book anymore, I can't test adaher's suggestion).

  • How to stop sleep/hibernation with external display & lid down

    What is the proper way to get my MBA to not sleep, hibernate, etc. when I have an external display attached and lid closed while watching a movie or webcast. In such a case I am not touching the mouse, trackpad, or keyboard.
    I have bluetooth keyboard and usb wireless mouse attached.
    I also disabled the sleep/poweroff options in the energy settings while watching.
    The MBA still would go to sleep or something after 10 or 15 minutes of no agitation.
    Also, the Monitor goes blank since their is not signal coming through to it.
    Was this just not a use case that was thought through: Watch video stream with external monitor and lid closed? Make sure the MBA knows this scenario invalidates the powersave options????? And yes, the power was plugged.
    Thanks

    Caffeine puts a little coffee cup icon at the top bar. Click to turn it off and on - it is on when the cup is dark, ie has coffee in it. However, this won't solve your problem - the MBA will still sleep with the lid closed. There are settings to allow use of an external monitor but what I did was download InsomniaX. This little free app keeps your computer from going to sleep when you close the lid. That way you can close the lid, walk down a hall or do something, then open the lid and keep working. Just don't forget it is on and leave the Mac too long or it will run out of battery.
    Insomnia isn't in the App store, had to download it at http://www.macupdate.com/app/mac/22211/insomniax

  • Not waking up with external display in closed clamshell mode.

    Hello all!
    I have the newest Macbook (late 2009), and have had it docked in a BookArc using an external display, keyboard and mouse. Everything has been working perfectly since I got it a couple months ago. I've traveled with the Macbook and redocked it at home a few times. This morning, I woke the computer and the display lit up as usual. A moment later, the display went black, said no signal and the power light went yellow (it's blue when operating). I hit the keyboard and clicked the mouse to wake it again to no avail. Took the Macbook out of the stand, opened the display and it works perfectly. Checked my energy saver settings, fine. Closed the clamshell, redocked, wont wake/start the external display. Took it out of the dock again, everything is fine, rebooted. Docked again, no wakey. I'm using it now as a normal laptop typing this. Any ideas as to suddenly why it wont wake/work with the external display? Thanks!

    Last week I bought an Acer X223W 22 inch display for my MacBook (13-inch, Late 2009) – Model A1342 Polycarbonate Unibody and an Apple Keyboard MB110LL/A - Also using a Apple wireless Magic Mouse but not a BookArc. ( Just leaving on the desk next to the Acer display )
    I've found that you have to have the MacBook connected to the AC Power Supply to keep the MacBook awake when trying to use an external display. It's kinda a pain sometimes, I usually boot up my MacBook before connecting the Display and Keyboard then once I'm logged in......
    and Once everything is loaded I plug in the Keyboard first then The Display adapter cable, Close the MacBook up then Click/Move the Magic Mouse ( System Preferences settings - Bluetooth ( Advanced: Allow Bluetooth Devices To Wake This Computer - checked ) Energy Saver AC and Battery set to 3 hours ( All other settings Unchecked )
    Sometimes takes a few clicks before the Desktop appears on the external display, Now once its on I can open the MacBook ( just enough to help keep it running cooler ) and unplug the AC Adapter unless it needs charging.

Maybe you are looking for