Is my Mac Pro eating monitors? Am I going crazy? A great mystery....

Something very bizarre is happening, and it doesn't make a lot of sense to me. Maybe someone here can offer a theory. Here's my setup, and here's what's been happening....
Mac Pro (early 2009), 2.66 GHz Quad-Core, 8 gigs of RAM, running Mac OS X 10.5.7.
ATI Radeon HD 4870. A very nice system, still has that new Mac smell.
Primary display is a 24" HannsG HH251 (a nice, if inexpensive large flat-panel).
Secondary display is a 20" Viewsonic VP200s. This is an older flat-panel (about 4 years old). I own three of these Viewsonic displays - they were a good primary workhorse monitor in their day, now I use them (mostly) as the 2nd monitor on my Macs and PCs (I have several).
Here's what's been happening...
The primary display is fine. The secondary display has been "failing". When I first hooked up the Viewsonic monitor (as the second display), it was fine. We'll call this "Viewsonic #1". After a couple of months, though, it started flickering - not a subtle flicker (as you might see with a low refresh rate), but a complete, violent flicker where the screen redraws instantly. At first, the big flicker would only occur intermittently - once every few minutes - but eventually it would start happening more and more frequently, then happened every second or two, then became constant - to the point where stuff on that monitor became completely unusable - I couldn't see the cursor clearly, couldn't close windows, etc. Initially, if I turned the monitor off for a moment, then back on, it would come back briefly. But the big flicker would start again soon. Powering down the computer and leaving it off for a while (like overnight), then starting it up again, the 2nd display (Viewsonic #1) would be OK for a while, but eventually the flashing started again. Rinse, lather, repeat.
I figured some hardware component was going bad - probably the monitor, but I was hoping it might be the cable or perhaps even the video card (still under warrantee). So I did a little swapping to see: I used a different video cable. Same problem. I thought, "****, the display is toast." I was bummed, but not heartbroken: I had 2 more of these monitors, and I could swap another one in. So I pulled an identical monitor from an older Windows PC that I'm not using much (we'll call this Viewsonic #2), and swapped that. As I suspected, using Viewsonic #2, the 2nd display on the Mac Pro came up nice and flicker-free, rock-steady and looking good. And when I boot up the Windows PC that now has the "bad" display (Viewsonic #1, removed from the Mac Pro), sure enough, it's flickering and flashing and just about impossible to use.
OK, so this seemed to confirm my theory: that Viewsonic #1 was simply in the process of dying. No hardware lasts forever, and although I'm used to getting 5-10 years out of my monitors (really - I've been at this a long time), that rule of thumb is from CRT days - I figured maybe flat panel LCDs only go about 5 years. I shrugged and made my peace with it. Since I was back in 2-monitor heaven, I wasn't worried about it (since I don't need to use the Windows PC with the funky display).
Turns out, there's more to it. This is where it gets strange.
It was about 3 or 4 days ago that I did the monitor swap. Since then, Viewsonic #2 has been fine, as I expected, solid, looking good. But about 6 hours ago, I was shocked to see Viewsonic #2 - now hooked up as my secondary display on the Mac Pro - has just started the same flicker. And it started getting worse, pretty quickly. Within an hour or so, it was becoming unusable. Once again, turning it off helped - a little - and so did shutting done the Mac and leaving it off. But soon after powering it up, it starts going haywire again. It's got the exact same problem that killed the other monitor.
I am thinking that the odds of two different monitors failing (hardware going bad) like this is extremely unlikely. I know it's not the cable or plug, because when I moved Viewsonic #1 to a different computer, it's still broken. I don't think it's the video card, because the "badness" moves with the bad monitor, and the primary display is fine.
The only think that makes any sense (and I'll admit it doesn't make much), is that there's something about this Mac Pro that is causing the 2nd monitor to fail - actually damaging the monitor. That sounds pretty unlikely, but it's the least unlikely think I can think of. Could it be outputting a signal that kills the monitor hardware? I know that sounds crazy....I'm open to suggestions if anyone has another theory.
I've never heard of a computer (or a video card) causing a display to fail, but given the fact that these monitors were both fine before I hooked them up to this Mac, and that both of them seem to have gone belly-up now (and they stay broken if moved back to another computer) really leaves me scratching my head.
What on earth is happening here? Any ideas?

Hi Ltm,
Is your set up is like this? Main monitor attached to dvi port on 4870, other displays attached to the mini port via adapter?
If it is, those mini ports have been the source of many peoples problems here. Maybe not even so much the ports but the adapters. Some seem to work better than others. I bought two in the 20 dollar range from Apple and they both worked poorly (and I have all Apple displays!). Apparently Apple sells one for about 100 bucks that works the best, but I changed cards before buying that.
OWC has an interesting mini-display port connecter now that looks good but also goes for a hundred or so.
But what is precisely going on with your Viewsonics to seemingly destroy them, I don't know. I've read of similar problems to yours, but the displays never stayed in a poor condition after the problem was found. Yours is the first post I've read of displays being actually killed off.
If you could take the now damaged display and one that isn't to an Apple store to try on one of their Macs, maybe they could turn up something for you, an incompatibility somewhere maybe. But it's a pretty bizarre situation made worse by Apples decision to introduce unnecessary variables by going with that mini-display port.

Similar Messages

  • Mac pro turns on but screen goes black after a while what could be wrong please help!!!

    Hello mac community, I am new,
    I updated a program today everything was working fine yesterday and now today I was updating PLAY a music engine program it seems to have caused the mac to go crazy. I also updated VE PRO 5 another music program. Everything has gone crazy. It turns on but then then the screen goes black after a while 5-10mins. I managed to get the crash report.
    Why is the graphics card all of a sudden effected by program updates.
    Sat Sep 28 10:49:06 2013
    panic(cpu 20 caller 0xffffff7f80f4775c): "ATICLASS::detectPowerDown: GPU is not found. PCI config access fails!!!\n"@/SourceCache/GraphicsDrivers/GraphicsDrivers-6.36.10/Common/IONDRV/ ATI/IOFramebuffer/ATIFramebuffer/Controller/Sources/R800/EvergreenClocks.cpp:825
    Backtrace (CPU 20), Frame : Return Address
    0xffffff83d2693a90 : 0xffffff8000204d15
    0xffffff83d2693b90 : 0xffffff7f80f4775c
    0xffffff83d2693bb0 : 0xffffff7f80f493dc
    0xffffff83d2693bd0 : 0xffffff7f8158cbe5
    0xffffff83d2693c00 : 0xffffff7f8158677c
    0xffffff83d2693c40 : 0xffffff7f80d9ac80
    0xffffff83d2693cc0 : 0xffffff7f80d99750
    0xffffff83d2693d00 : 0xffffff80005281dd
    0xffffff83d2693d70 : 0xffffff8000553deb
    0xffffff83d2693de0 : 0xffffff80002ba770
    0xffffff83d2693e50 : 0xffffff8000205536
    0xffffff83d2693e80 : 0xffffff80002029eb
    0xffffff83d2693ef0 : 0xffffff8000274176
    0xffffff83d2693f60 : 0xffffff80002c3095
    0xffffff83d2693fa0 : 0xffffff80002e4894
    Kernel Extensions in backtrace (with dependencies):
    com.apple.kext.ATIFramebuffer(6.3.6)@0xffffff7f81585000->0xffffff7f81598fff
                dependency: com.apple.iokit.IOACPIFamily(1.3.0)@0xffffff7f80800000
                dependency: com.apple.iokit.IOPCIFamily(2.6.5)@0xffffff7f80804000
                dependency: com.apple.iokit.IOGraphicsFamily(2.2.1)@0xffffff7f80d88000
                dependency: com.apple.kext.ATISupport(6.3.6)@0xffffff7f80e02000
    com.apple.kext.ATI5000Controller(6.3.6)@0xffffff7f80f30000->0xffffff7f80f5afff
                dependency: com.apple.iokit.IOACPIFamily(1.3.0)@0xffffff7f80800000
                dependency: com.apple.iokit.IOPCIFamily(2.6.5)@0xffffff7f80804000
                dependency: com.apple.iokit.IOGraphicsFamily(2.2.1)@0xffffff7f80d88000
                dependency: com.apple.kext.ATISupport(6.3.6)@0xffffff7f80e02000
    com.apple.iokit.IOGraphicsFamily(2.2.1)@0xffffff7f80d88000->0xffffff7f80daffff
                dependency: com.apple.iokit.IOPCIFamily(2.6.5)@0xffffff7f80804000
    BSD process name corresponding to current thread: WindowServer
    Mac OS version:
    10K549
    Kernel version:
    Darwin Kernel Version 10.8.0: Tue Jun  7 16:32:41 PDT 2011; root:xnu-1504.15.3~1/RELEASE_X86_64
    System model name: MacPro5,1 (Mac-F221BEC8)
    System uptime in nanoseconds: 12612076511
    unloaded kexts:
    (none)
    loaded kexts:
    com.audinate.dante.driver.DanteVirtualSoundcard     0.9.3
    com.paceap.kext.pacesupport.snowleopard       5.8
    com.Areca.ArcMSR  1.3.3
    com.apple.filesystems.autofs    2.1.0
    com.apple.driver.AppleTyMCEDriver 1.0.2d2
    com.apple.driver.AGPM    100.12.31
    com.apple.driver.AppleHWSensor     1.9.3d0
    com.apple.driver.AudioAUUC    1.57
    com.apple.driver.AppleUpstreamUserClient       3.5.7
    com.apple.driver.AppleMCCSControl 1.0.20
    com.apple.driver.AppleMikeyHIDDriver      1.2.0
    com.apple.kext.ATIFramebuffer        6.3.6
    com.apple.driver.AppleIntelPenrynProfile   17
    com.apple.Dont_Steal_Mac_OS_X    7.0.0
    com.apple.driver.AppleMikeyDriver    2.0.5f14
    com.apple.ATIRadeonX3000     6.3.6
    com.apple.driver.AppleIntelNehalemProfile        11
    com.apple.driver.AppleHDA      2.0.5f14
    com.apple.driver.AudioIPCDriver       1.1.6
    com.apple.driver.AirPortBrcm43xx     423.91.27
    com.apple.driver.Intel82574L    2.1.8b1
    com.apple.driver.AppleIntelMeromProfile   19
    com.apple.driver.AirPortBrcm43224  428.42.4
    com.apple.driver.ACPI_SMC_PlatformPlugin     4.7.0a1
    com.apple.driver.AppleLPC       1.5.1
    com.apple.driver.AppleIntel8254XEthernet 2.1.3b1
    com.apple.filesystems.ntfs        3.4
    com.apple.iokit.SCSITaskUserClient  2.6.8
    com.apple.iokit.IOAHCIBlockStorage 1.6.4
    com.apple.driver.AppleUSBHub 4.2.4
    com.apple.driver.AppleFWOHCI        4.7.3
    com.apple.driver.AppleUSBEHCI       4.2.4
    com.apple.BootCache       31.1
    com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
    com.apple.driver.AppleAHCIPort       2.1.7
    com.apple.driver.AppleUSBUHCI       4.2.0
    com.apple.driver.AppleEFINVRAM    1.4.0
    com.apple.driver.AppleRTC       1.3.1
    com.apple.driver.AppleHPET     1.5
    com.apple.driver.AppleACPIButtons  1.3.6
    com.apple.driver.AppleSMBIOS        1.7
    com.apple.driver.AppleACPIEC 1.3.6
    com.apple.driver.AppleAPIC      1.4
    com.apple.driver.AppleIntelCPUPowerManagementClient  142.6.0
    com.apple.security.sandbox      1
    com.apple.security.quarantine   0
    com.apple.nke.applicationfirewall       2.1.14
    com.apple.driver.AppleIntelCPUPowerManagement   142.6.0
    com.apple.iokit.IOSCSIBlockCommandsDevice 2.6.8 - last loaded 12365095188
    com.apple.driver.AppleProfileReadCounterAction       17
    com.apple.driver.AppleProfileTimestampAction  10
    com.apple.driver.AppleProfileThreadInfoAction  14
    com.apple.driver.AppleProfileRegisterStateAction      10
    com.apple.driver.AppleProfileKEventAction        10
    com.apple.driver.AppleProfileCallstackAction     20
    com.apple.iokit.IOSurface 74.2
    com.apple.iokit.IOBluetoothSerialManager 2.4.5f3
    com.apple.iokit.IOSerialFamily  10.0.3
    com.apple.driver.AppleHDAHardwareConfigDriver     2.0.5f14
    com.apple.driver.DspFuncLib    2.0.5f14
    com.apple.iokit.IONDRVSupport        2.2.1
    com.apple.iokit.IOAudioFamily  1.8.3fc2
    com.apple.kext.OSvKernDSPLib       1.3
    com.apple.driver.AppleSMBusController    1.0.10d0
    com.apple.iokit.IOFireWireIP     2.0.3
    com.apple.kext.ATI5000Controller     6.3.6
    com.apple.kext.ATISupport       6.3.6
    com.apple.iokit.AppleProfileFamily     41
    com.apple.driver.AppleHDAController        2.0.5f14
    com.apple.iokit.IOGraphicsFamily     2.2.1
    com.apple.iokit.IOHDAFamily    2.0.5f14
    com.apple.iokit.IO80211Family  320.1
    com.apple.driver.AppleSMC      3.1.0d5
    com.apple.driver.IOPlatformPluginFamily   4.7.0a1
    com.apple.driver.AppleSMBusPCI     1.0.10d0
    com.apple.iokit.IONetworkingFamily  1.10
    com.apple.driver.BroadcomUSBBluetoothHCIController     2.4.5f3
    com.apple.driver.AppleUSBBluetoothHCIController    2.4.5f3
    com.apple.iokit.IOBluetoothFamily     2.4.5f3
    com.apple.driver.AppleUSBMergeNub       4.2.4
    com.apple.driver.AppleUSBComposite       3.9.0
    com.apple.driver.XsanFilter       402.1
    com.apple.iokit.IOSCSIMultimediaCommandsDevice 2.6.8
    com.apple.iokit.IOBDStorageFamily   1.6
    com.apple.iokit.IODVDStorageFamily        1.6
    com.apple.iokit.IOCDStorageFamily  1.6.1
    com.apple.iokit.IOUSBUserClient      4.2.4
    com.apple.iokit.IOAHCISerialATAPI   1.2.6
    com.apple.iokit.IOFireWireFamily      4.2.6
    com.apple.driver.AppleFileSystemDriver    2.0
    com.apple.iokit.IOAHCIFamily   2.0.6
    com.apple.iokit.IOUSBFamily    4.2.4
    com.apple.iokit.IOSCSIParallelFamily        2.1.1
    com.apple.iokit.IOSCSIArchitectureModelFamily        2.6.8
    com.apple.driver.AppleEFIRuntime    1.4.0
    com.apple.iokit.IOHIDFamily     1.6.6
    com.apple.iokit.IOSMBusFamily        1.1
    com.apple.security.TMSafetyNet       6
    com.apple.kext.AppleMatch      1.0.0d1
    com.apple.driver.DiskImages    289
    com.apple.iokit.IOStorageFamily       1.6.3
    com.apple.driver.AppleACPIPlatform 1.3.6
    com.apple.iokit.IOPCIFamily     2.6.5
    com.apple.iokit.IOACPIFamily   1.3.0
    Cubase has this error
    Process:         Cubase 6 [222]
    Path:            /Applications/Cubase 6.app/Contents/MacOS/Cubase 6
    Identifier:      com.steinberg.cubase
    Version:         6.0.7.364 (6.0.7.364)
    Code Type:       X86-64 (Native)
    Parent Process:  launchd [144]
    Date/Time:       2013-09-28 10:50:35.845 +0100
    OS Version:      Mac OS X 10.6.8 (10K549)
    Report Version:  6
    Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes: KERN_INVALID_ADDRESS at 0x000000012473fd9f
    Crashed Thread:  0  Dispatch queue: com.apple.main-thread
    Thread 0 Crashed:  Dispatch queue: com.apple.main-thread
    0   ???                             0x000000012473fd9f 0 + 4906548639
    1   dyld                             0x00007fff5fc0c839 ImageLoader::link(ImageLoader::LinkContext const&, bool, bool, ImageLoader::RPathChain const&) + 201
    2   dyld                             0x00007fff5fc04d48 dyld::link(ImageLoader*, bool, ImageLoader::RPathChain const&) + 118
    3   dyld                             0x00007fff5fc08f68 dlopen + 490
    4   libSystem.B.dylib                 0x00007fff87a9be40 dlopen + 61
    5   com.apple.CoreFoundation          0x00007fff8223eef7 _CFBundleDlfcnLoadBundle + 231
    6   com.apple.CoreFoundation          0x00007fff8223de97 _CFBundleLoadExecutableAndReturnError + 1191
    7   com.apple.CoreFoundation          0x00007fff822cb30e CFBundleLoadExecutableAndReturnError + 14
    8   com.steinberg.cubase                  0x00000001011e8e55 CSOLOISTExtendedAnalysis::~CSOLOISTExtendedAnalysis() + 69941
    9   com.steinberg.cubase                  0x00000001011e93f0 CSOLOISTExtendedAnalysis::~CSOLOISTExtendedAnalysis() + 71376
    10  com.steinberg.cubase                 0x0000000100402690 0x100000000 + 4204176
    11  com.steinberg.cubase                 0x00000001011d8e77 CSOLOISTExtendedAnalysis::~CSOLOISTExtendedAnalysis() + 4439
    12  com.steinberg.cubase                 0x00000001011e86b7 CSOLOISTExtendedAnalysis::~CSOLOISTExtendedAnalysis() + 67991
    13  com.steinberg.cubase                 0x00000001011e892e CSOLOISTExtendedAnalysis::~CSOLOISTExtendedAnalysis() + 68622
    14  com.steinberg.cubase                 0x00000001011e8a64 CSOLOISTExtendedAnalysis::~CSOLOISTExtendedAnalysis() + 68932
    15  com.steinberg.cubase                 0x00000001007c68ab 0x100000000 + 8153259
    16  com.steinberg.cubase                 0x0000000100d149c0 0x100000000 + 13715904
    17  com.steinberg.cubase                 0x0000000101277b99 CSOLOISTExtendedAnalysis::~CSOLOISTExtendedAnalysis() + 654969
    18  com.steinberg.cubase                 0x0000000100d16dbd 0x100000000 + 13725117
    19  com.steinberg.cubase                 0x000000010116b048 0x100000000 + 18264136
    20  com.steinberg.cubase                 0x00000001000d39c4 0x100000000 + 866756
    Thread 1:  Dispatch queue: com.apple.libdispatch-manager
    0   libSystem.B.dylib                 0x00007fff87aaec0a kevent + 10
    1   libSystem.B.dylib                 0x00007fff87ab0add _dispatch_mgr_invoke + 154
    2   libSystem.B.dylib                 0x00007fff87ab07b4 _dispatch_queue_invoke + 185
    3   libSystem.B.dylib                 0x00007fff87ab02de _dispatch_worker_thread2 + 252
    4   libSystem.B.dylib                 0x00007fff87aafc08 _pthread_wqthread + 353
    5   libSystem.B.dylib                 0x00007fff87aafaa5 start_wqthread + 13
    Thread 2:
    0   libSystem.B.dylib                 0x00007fff87aafa2a __workq_kernreturn + 10
    1   libSystem.B.dylib                 0x00007fff87aafe3c _pthread_wqthread + 917
    2   libSystem.B.dylib                 0x00007fff87aafaa5 start_wqthread + 13
    Thread 3:  FThread
    0   libSystem.B.dylib                 0x00007fff87a95dce semaphore_timedwait_trap + 10
    1   com.steinberg.cubase                  0x00000001014f8437 CSOLOISTExtendedAnalysis::~CSOLOISTExtendedAnalysis() + 3278615
    2   com.steinberg.cubase                  0x00000001007c8be0 0x100000000 + 8162272
    3   com.steinberg.cubase                  0x00000001014f8eb0 CSOLOISTExtendedAnalysis::~CSOLOISTExtendedAnalysis() + 3281296
    4   libSystem.B.dylib                 0x00007fff87b7129a _pthread_body + 24
    Thread 4:
    0   libSystem.B.dylib                 0x00007fff87aafa2a __workq_kernreturn + 10
    1   libSystem.B.dylib                 0x00007fff87aafe3c _pthread_wqthread + 917
    2   libSystem.B.dylib                 0x00007fff87aafaa5 start_wqthread + 13
    Thread 5:
    0   libSystem.B.dylib                 0x00007fff87a95dda semaphore_timedwait_signal_trap + 10
    1   libSystem.B.dylib                 0x00007fff87ad4772 _pthread_cond_wait + 1015
    2   com.apple.CoreVideo                   0x00007fff82fbade6 CVDisplayLink::waitUntil(unsigned long long) + 252
    3   com.apple.CoreVideo                   0x00007fff82fba2a2 CVDisplayLink::runIOThread() + 644
    4   com.apple.CoreVideo                   0x00007fff82fb9fe3 startIOThread(void*) + 139
    5   libSystem.B.dylib                 0x00007fff87acefd6 _pthread_start + 331
    6   libSystem.B.dylib                 0x00007fff87acee89 thread_start + 13
    Thread 6:
    0   libSystem.B.dylib                 0x00007fff87aafa2a __workq_kernreturn + 10
    1   libSystem.B.dylib                 0x00007fff87aafe3c _pthread_wqthread + 917
    2   libSystem.B.dylib                 0x00007fff87aafaa5 start_wqthread + 13
    Thread 0 crashed with X86 Thread State (64-bit):
      rax: 0x00000001211f4000  rbx: 0x00007fff5fc43ae8  rcx: 0x00007fff5fc019df  rdx: 0x00007fff5fbfdd20
      rdi: 0x00000001211f4000  rsi: 0x00000001211f4000  rbp: 0x00007fff5fbfe170  rsp: 0x00007fff5fbfdce8
       r8: 0x0000000000000000   r9: 0x00007fff8abcf420  r10: 0x0000000000000000  r11: 0x00007fff8abcf420
      r12: 0x00000001224521e0  r13: 0x00000001211f4000  r14: 0x000000012473fd9f  r15: 0x00007fff5fbfdcf0
      rip: 0x000000012473fd9f  rfl: 0x0000000000010212  cr2: 0x000000012473fd9f
    Binary Images:
           0x100000000 -        0x1022a4fe7 +com.steinberg.cubase 6.0.7.364 (6.0.7.364) <CFFF5ABF-970D-896D-4A88-78FFF87878C1> /Applications/Cubase 6.app/Contents/MacOS/Cubase 6
           0x10268c000 -        0x1026dcff7  com.apple.audio.midi.CoreMIDI 1.7.1 (42) <E7DBCE93-A637-ABA2-B623-6A76B82EE243> /System/Library/Frameworks/CoreMIDI.framework/Versions/A/CoreMIDI
           0x102704000 -        0x10270aff7  com.apple.agl 3.0.12 (AGL-3.0.12) <014CA38F-CB49-8214-4C16-DF73FC6EFCE1> /System/Library/Frameworks/AGL.framework/Versions/A/AGL
           0x105f00000 -        0x105f89ff2 +com.eLicenser.POSAccess-DLL ??? (1.12.1.0) <66A02345-5109-F38C-1262-D00D8189324C> /Library/Application Support/eLicenser/pos/Synsoacc.bundle/Contents/MacOS/Synsoacc
           0x1170a6000 -        0x1170ccfff  GLRendererFloat ??? (???) <38621D22-8F49-F937-851B-E21BD49A8A88> /System/Library/Frameworks/OpenGL.framework/Resources/GLRendererFloat.bundle/GL RendererFloat
           0x11a17a000 -        0x11a30dfe7  GLEngine ??? (???) <BCE83654-81EC-D231-ED6E-1DD449B891F2> /System/Library/Frameworks/OpenGL.framework/Resources/GLEngine.bundle/GLEngine
           0x11a33e000 -        0x11a730fff  com.apple.ATIRadeonX3000GLDriver 1.6.36 (6.3.6) <282E53E2-ABB3-B97D-F298-6A8FE21F3A5A> /System/Library/Extensions/ATIRadeonX3000GLDriver.bundle/Contents/MacOS/ATIRade onX3000GLDriver
           0x11b243000 -        0x11b249fe7  libFontStreams.A.dylib 545.0.0 (compatibility 64.0.0) <87272933-FB21-81D0-00E6-92BC3D7583FB> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libFontStreams.A.dylib
           0x1211f4000 -        0x121303fff +com.steinberg.omffilter 4.0.0.179 (4.0.0.179) <C05588E9-6173-ECEF-2BF1-92AE05B78913> /Applications/Cubase 6.app/Contents/Components/omffilter.bundle/Contents/MacOS/omffilter
        0x7fff5fc00000 -     0x7fff5fc3bdef  dyld 132.1 (???) <69130DA3-7CB3-54C8-ABC5-423DECDD2AF7> /usr/lib/dyld
        0x7fff80003000 -     0x7fff80059fe7  libTIFF.dylib ??? (???) <2DBEC120-DAA7-3789-36A2-A205BCDF2D72> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libTIFF.dylib
        0x7fff8008f000 -     0x7fff8011ffff  com.apple.SearchKit 1.3.0 (1.3.0) <4175DC31-1506-228A-08FD-C704AC9DF642> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchK it.framework/Versions/A/SearchKit
        0x7fff80132000 -     0x7fff80179ff7  com.apple.coreui 2 (114) <923E33CC-83FC-7D35-5603-FB8F348EE34B> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI
        0x7fff80453000 -     0x7fff8048dfff  libcups.2.dylib 2.8.0 (compatibility 2.0.0) <4F2A4397-89BD-DEAC-4971-EE838FFA0964> /usr/lib/libcups.2.dylib
        0x7fff80c2c000 -     0x7fff81626ff7  com.apple.AppKit 6.6.8 (1038.36) <4CFBE04C-8FB3-B0EA-8DDB-7E7D10E9D251> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
        0x7fff81627000 -     0x7fff816dcfe7  com.apple.ink.framework 1.3.3 (107) <8C36373C-5473-3A6A-4972-BC29D504250F> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework /Versions/A/Ink
        0x7fff8189e000 -     0x7fff81938fff  com.apple.ApplicationServices.ATS 275.19 (???) <2DE8987F-4563-4D8E-45C3-2F6F786E120D> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ATS.framework/Versions/A/ATS
        0x7fff8199c000 -     0x7fff81c1efff  com.apple.Foundation 6.6.8 (751.63) <E10E4DB4-9D5E-54A8-3FB6-2A82426066E4> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
        0x7fff81c1f000 -     0x7fff81c1fff7  com.apple.Carbon 150 (152) <C0E61968-57F3-6EE1-8524-32A18955BAF0> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
        0x7fff81c20000 -     0x7fff81c26ff7  com.apple.CommerceCore 1.0 (9.1) <3691E9BA-BCF4-98C7-EFEC-78DA6825004E> /System/Library/PrivateFrameworks/CommerceKit.framework/Versions/A/Frameworks/C ommerceCore.framework/Versions/A/CommerceCore
        0x7fff81c7f000 -     0x7fff81c8cfe7  libCSync.A.dylib 545.0.0 (compatibility 64.0.0) <1C35FA50-9C70-48DC-9E8D-2054F7A266B1> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libCSync.A.dylib
        0x7fff81c8d000 -     0x7fff82196ff7  com.apple.RawCamera.bundle 3.14.0 (646) <75A96BFC-1832-808B-F430-C4C9379C5A98> /System/Library/CoreServices/RawCamera.bundle/Contents/MacOS/RawCamera
        0x7fff82197000 -     0x7fff821ecff7  com.apple.framework.familycontrols 2.0.2 (2020) <F09541B6-5E28-1C01-C1AE-F6A2508670C7> /System/Library/PrivateFrameworks/FamilyControls.framework/Versions/A/FamilyCon trols
        0x7fff821ed000 -     0x7fff821f1ff7  libCGXType.A.dylib 545.0.0 (compatibility 64.0.0) <DB710299-B4D9-3714-66F7-5D2964DE585B> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libCGXType.A.dylib
        0x7fff821f4000 -     0x7fff8236bfe7  com.apple.CoreFoundation 6.6.6 (550.44) <BB4E5158-E47A-39D3-2561-96CB49FA82D4> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
        0x7fff823b7000 -     0x7fff82482fff  ColorSyncDeprecated.dylib 4.6.0 (compatibility 1.0.0) <86982FBB-B224-CBDA-A9AD-8EE97BDB8681> /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ColorSync.f ramework/Versions/A/Resources/ColorSyncDeprecated.dylib
        0x7fff82483000 -     0x7fff824c1fe7  libFontRegistry.dylib ??? (???) <395D7C0D-36B5-B353-0DC8-51ABC0B1C030> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ATS.framework/Versions/A/Resources/libFontRegistry.dylib
        0x7fff824c2000 -     0x7fff82681fff  com.apple.ImageIO.framework 3.0.6 (3.0.6) <92882FD3-CB3F-D0BE-DDDA-43B4BEE10F58> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/ImageIO
        0x7fff82682000 -     0x7fff82686ff7  libmathCommon.A.dylib 315.0.0 (compatibility 1.0.0) <95718673-FEEE-B6ED-B127-BCDBDB60D4E5> /usr/lib/system/libmathCommon.A.dylib
        0x7fff82687000 -     0x7fff82687ff7  com.apple.Accelerate 1.6 (Accelerate 1.6) <15DF8B4A-96B2-CB4E-368D-DEC7DF6B62BB> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
        0x7fff82688000 -     0x7fff82745fff  com.apple.CoreServices.OSServices 359.2 (359.2) <BBB8888E-18DE-5D09-3C3A-F4C029EC7886> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServi ces.framework/Versions/A/OSServices
        0x7fff82746000 -     0x7fff82747ff7  com.apple.audio.units.AudioUnit 1.6.7 (1.6.7) <49B723D1-85F8-F86C-2331-F586C56D68AF> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
        0x7fff827c6000 -     0x7fff827d7ff7  libz.1.dylib 1.2.3 (compatibility 1.0.0) <97019C74-161A-3488-41EC-A6CA8738418C> /usr/lib/libz.1.dylib
        0x7fff827d8000 -     0x7fff82842fe7  libvMisc.dylib 268.0.1 (compatibility 1.0.0) <AF0EA96D-000F-8C12-B952-CB7E00566E08> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvMisc.dylib
        0x7fff82843000 -     0x7fff82959ff7  libxml2.2.dylib 10.3.0 (compatibility 10.0.0) <3814FCF9-92B9-A6AB-E76A-F7021894AA3F> /usr/lib/libxml2.2.dylib
        0x7fff82cad000 -     0x7fff82ccdfff  com.apple.DirectoryService.Framework 3.6 (621.16) <0ED4A74A-F8FB-366D-6588-F13EA397326F> /System/Library/Frameworks/DirectoryService.framework/Versions/A/DirectoryServi ce
        0x7fff82da6000 -     0x7fff82e24ff7  com.apple.CoreText 151.13 (???) <5C6214AD-D683-80A8-86EB-328C99B75322> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreText.framework/Versions/A/CoreText
        0x7fff82e25000 -     0x7fff82f5afff  com.apple.audio.toolbox.AudioToolbox 1.6.7 (1.6.7) <F4814A13-E557-59AF-30FF-E62929367933> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
        0x7fff82fb5000 -     0x7fff82fb7fff  com.apple.print.framework.Print 6.1 (237.1) <CA8564FB-B366-7413-B12E-9892DA3C6157> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framewo rk/Versions/A/Print
        0x7fff82fb8000 -     0x7fff82fddff7  com.apple.CoreVideo 1.6.2 (45.6) <E138C8E7-3CB6-55A9-0A2C-B73FE63EA288> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo
        0x7fff82fde000 -     0x7fff8311cfff  com.apple.CoreData 102.1 (251) <9DFE798D-AA52-6A9A-924A-DA73CB94D81A> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
        0x7fff8311d000 -     0x7fff831cdfff  edu.mit.Kerberos 6.5.11 (6.5.11) <085D80F5-C9DC-E252-C21B-03295E660C91> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos
        0x7fff831ce000 -     0x7fff8328ffef  com.apple.ColorSync 4.6.8 (4.6.8) <7DF1D175-6451-51A2-DBBF-40FCA78C0D2C> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ColorSync.framework/Versions/A/ColorSync
        0x7fff832c0000 -     0x7fff8339dfff  com.apple.vImage 4.1 (4.1) <C3F44AA9-6F71-0684-2686-D3BBC903F020> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.fr amework/Versions/A/vImage
        0x7fff8339e000 -     0x7fff8339eff7  com.apple.vecLib 3.6 (vecLib 3.6) <96FB6BAD-5568-C4E0-6FA7-02791A58B584> /System/Library/Frameworks/vecLib.framework/Versions/A/vecLib
        0x7fff8339f000 -     0x7fff8369dfff  com.apple.HIToolbox 1.6.5 (???) <AD1C18F6-51CB-7E39-35DD-F16B1EB978A8> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox
        0x7fff8369e000 -     0x7fff836c0ff7  libexpat.1.dylib 7.2.0 (compatibility 7.0.0) <8EC31253-B585-D05E-F35D-AE3292FB790B> /usr/lib/libexpat.1.dylib
        0x7fff83722000 -     0x7fff8376bfef  libGLU.dylib ??? (???) <B0F4CA55-445F-E901-0FCF-47B3B4BAE6E2> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib
        0x7fff8376c000 -     0x7fff83851fef  com.apple.DesktopServices 1.5.11 (1.5.11) <39FAA3D2-6863-B5AB-AED9-92D878EA2438> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/Desk topServicesPriv
        0x7fff8389f000 -     0x7fff838e2ff7  libRIP.A.dylib 545.0.0 (compatibility 64.0.0) <5FF3D7FD-84D8-C5FA-D640-90BB82EC651D> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libRIP.A.dylib
        0x7fff83904000 -     0x7fff83904ff7  com.apple.ApplicationServices 38 (38) <10A0B9E9-4988-03D4-FC56-DDE231A02C63> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Application Services
        0x7fff83914000 -     0x7fff83af6fef  libType1Scaler.dylib ??? (???) <7892C4D7-3E5E-D7DA-AA4E-8D4ACED143D9> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ATS.framework/Versions/A/Resources/libType1Scaler.dylib

    I havent had the exact same problem as you but I am having a similar problem where lately I noticed when working in Pro Tools (mainly because I use my mac pro for audio work) or even when on the internet whatever it may be that my screen has been flickering a little bit or gets slightly glitchy.
    Yesterday upon startup for the first time the screen went black. Had to do a force shutdown. Unplugged all external devices. Reset everything as well. Slowly checked everything was on the phone with Apple even during the process. Seemed to correct the issue. Then of course I get off the phone, restarted my computer and it goes black randomly again.
    Rebooted fine. Checked all my hard disks internal and external, verified and repaired permissions on main drive and clone. Since then nothing yet...But I still feel its either the Video Card or the Monitor as everything else is fully operational.
    I plan on taking it in to look at as my applecare is up in November but I cant point my finger on it. And really am trying to avoid lugging the mac pro and monitor in at the same time...(Not the easiest thing with lack of parking in nyc..)
    If the display was dying I feel like it would have konked out already.
    The funny thing is I have had to replace video cards and monitors in the past but this time I cant quite figure out what the **** is going on.
    I am leaning towards the video card as I noticed it flickered a little when opening plug in windows in pro tools or multiple windows in sfari but it doesnt make sense.
    Worst part is I cant do a hardware test cause for some reason this computer doesnt have the software installed. It does nothing when I hold down the D button...
    I  totally baffled but the randomness of this.

  • Mac Pro Dual Monitors in Boot Camp Windows 8.1 Pro

    I just set up my 2013 Mac Pro with Bootcamp using Windows 8.1 Pro x64 and so far everything works great (albeit the initial setup was a struggle) except that Windows won't use my 2nd monitor.  In device manager I see both displays but one has the exclamation on it saying there was a problem and it won't be enabled (yes, that generic too, gotta love Microsoft).  I really want to be able to use both displays when I am in boot camp, is there anything I can do to fix this?  I have made sure both Windows and Mac are fully updated and still no love.

    Thank you for the link but it wasn't helpful as it only really said compatibility.  What did finally resolve the issue was going directly to AMD and finding that they updated the BootCamp specific drivers.  For other that stumble upon this, you cannot use the normal drivers from AMD but you must search for the bootcamp specific drivers (which also includes an updated Catalyst utility and a couple extra things not included in Apples release of the drivers).

  • Mac Pro and monitor compatibility

    Hi
    Just ordered a new Mac Pro (ATI Radeon HD 4870 512MB), couldn't afford an apple display.
    I'm looking to take advantage of the dual monitor option.
    Can anyone tell me whether I need an adapter to connect the following monitors? Or even if the following monitors will work with the NEW Mac Pro?
    Main monitor - Samsung T220 22" TFT Monitor 1680x1050 20,000:1 2ms VGA/DVI.
    Secondary monitor - Dell E151FPp 15" VGA.

    Be careful about mixing the 4870 with third party monitors. Make sure to test it out thoroughly before you return period is up. There have been display issues with the 4870 and any third party monitors. It is not guaranteed, however quite common.
    Check for mouse jumping, display anomalies, etc. The monitors listed should work however, it seems you need two adapters:
    This one should be included with your mac pro:
    http://store.apple.com/us/product/M8754G/A?mco=NDcyMDY3OA
    It depends on which monitors you want to hook up, but there are also these adapters:
    http://store.apple.com/us/product/MB572Z/A?mco=NDcwMjAzMA
    http://store.apple.com/us/product/MB570Z/A?mco=NDY5Nzg0OQ
    You could just hook your samsung DVI to DVI, then use the MDP to VGA for the Dell, however make sure to read the reviews carefully, as MDP to VGA (and MDP to DVI for that matter) hasn't had a really great track record according to a lot of people.

  • Does Yosemite support mac pro duel monitors?

    Does Yosemite on early 2008 mac pro support duel monitors to the extent to make one desk top?

    as long as that box is checked, each display is independent.
    If you want the original "Extended Desktop":
    Uncheck the box
    close the preference pane or switch to another and save changes.

  • Will mac pro and monitors ordered together ship at the same time?

    Will Mac Pro and Thunderbolt monitors, if ordered together, ship at the same time? Or will they ship the in-stock monitors now initiating the Applecare start date for the whole order even though the Mac Pro is not expected to ship until sometime in March?

    I ordered the new Mac Pro (model 6.1) on December 18, 2013 along with a 27 in. Apple thunderbolt display.  The fully maxxed out new Mac pro shipped on January 8, 2014 and arrived January 13, 2014.  My Thunderbolt display shipped within 1-2 days of placing the order, i.e. the week of December 18th and arrived before Christmas.  A few days after receivng my new Mac Pro, I received the Apple Care paperwork and both the new Mac Pro and the Apple Thunderbolt display were listed with a start date of January 7, 2014, i.e. the day that my new Mac {ro was prepared for shipment -- not the day my thunderbolt display was shipped.
    Tom

  • MAC PRO  -  5K Monitor möglich?

    Kann mir jemand sagen, ob der neue MAC PRO mit dem zum Jahreswechsel erscheinenden 5K Monitor arbeiten kann. Kann man auch 2x einen 5K Monitor an den neuen MAC PRO anschliessen?
    Mit wie viel Hertz läuft dann der 5K Monitor in der höchsten Auflösung? Gilt das dann auch für mehrere 5K Monitore?

    Can anyone tell me if the new MAC PRO can work with the year appearing 5K monitor me. Can also connect 2x a 5K monitor to the new MAC PRO?
    With how much Hertz then the 5K monitor is in the highest resolution? Then Is that also true for several 5K monitors?
    Apple has not said anything about the compatibility of the 2013 Mac Pro with any 5K monitors. I would contact the monitor manufacturer.
    I have not seen any previous post concerning 5K monitors in this forum.

  • Mac Pro- 2 monitor Time Machine screen redraw issue

    Late 2013 Mac Pro
    OSX V. 10.10.3 (which includes the supplemental install that came a week later)
    30 Inch Cinema HD Display
    23 Inch Cinema HD Display
    When I enter Time Machine I see the attached image on my 30 inch display (my primary display). the 23 Inch does NOT go black- it just displays whatever was showing prior to entering TM. The black box appears to be the 23 Inch Display's "cover" that has been slid over onto the 30 inch display. Time Machine DOES back up regularly according to the TM pull down. You can see the cancel button obscured by the black box.

    Open the Mission Control pane in System Preferences and uncheck the box marked
              Displays have separate Spaces
    Test.

  • Mac Pro / System Gets "Choppy" / File Goes Missing

    Hi all,
    I recently got a Mac Pro Quad-Core ($2,499 stock model) MB871LL1/A. I am using a Microsoft Intellimouse Optical and MS Comfort Curve Keyboard 2000 that did not come with the system itself that has never given me problems before.
    For the first few nights, everything seemed fine with the included iLife apps (such as iMovie, iDVD, etc)
    I later received the Final Cut Studio 3 Upgrade last night, so I installed and started experimenting with applications. Namely. FCP and Motion. Earlier projects were updated and saved and rendered speedy and normal.
    Two things happened while rendering a NEW project with either Motion 4 itself as well as Compressor 3.5:
    ISSUES:
    1. Mouse movement became extremely erratic, and the cursor would jump across the screen instantaneously. I couldn't control the mouse at all. Every movement would cause the cursor to jump around erratically. It felt like someone may have been sabotaging the mouse movement! I turned Bluetooth off as well as disconnected my LAN cable just to be sure. Still happening.
    2. System 'responsiveness' became very choppy, and in some cases would remain that way after closing the apps (though not always).
    3. I rebooted my system and reloaded my project. The project used just one font (Garamond). Motion reported that the font was missing - I checked with Font Book as well as the /Fonts directory itself and Garamond was indeed erased from the system.
    SOLUTIONS?
    I tried using "Rember" (freeware memtest app) and RAM checked out fine. Disk Utility reported the disk was fine.
    I may consider re installing everything before my Genius Bar appointment (next available is "Tuesday 9:15am" at my nearest store), and I'd like to think that it's just this project file causing the problem (it's basically one Camera that dollies forward through four words in 3d space, pretty simple). However I want to prevent this from happening again and I'm worried there might be something wonky in the hardware on my Mac.
    I know this is all very strange, but has anyone heard of an issue like this or might know why that was happening?

    Jumpy mice gets mentioned, some attribute it to video problems I think.
    I assume you have the latest MS Optical driver.
    Always clone a system before installing apps or updates so you have a backup you can boot from.
    Don't rely on just Apple DU First Aid. Time to invest in 3rd party, though if you plan on jumping to Snow immediately might want to wait on that.
    You may find 3GB RAM is just not going to cut it though, that is extremely minimum and base system, not what you want for what you are doing. With quad 4-dimm setup, I'd look at either 4 x 2GB or 3 x 4GB to give you 8-12GB RAM. 3 x 2GB should be minimum (unless just using it for email and web).
    Also, optimize your files and storage if you haven't: boot drive, editing and scratch, media files on 3rd drive, maybe setup 2-3 drive RAID at some point.
    Lot of adjusting and changes that go along with any new system regardless of what you ran before.

  • I hear a sound like clock pendulum inside my mac pro, not a time related, everything else looks great, could anybody help please?

    Hi all, i am hearing a sound inside my Mac Pro over 2 months before, on both power and battery, not a time specific, i hear a "tictac" sound like Wall Clock Pendulum, beneath the keyboard, i can feel it my hand while typing, it is very clear, could anybody of help please?

    Start your MBP with the StartupManager:
    http://support.apple.com/kb/HT1310
    You should see two HDD icons.  Select the recovery partition (on the right).
    From the 4 option menu select Disk Utility,
    Select Disk Utility>First Aid, and run Verify and then Repair.
    This should tell you if there are any issues with the HDD.
    Do backup your data if you value it.
    Ciao.

  • HT201343 If you have a Mac Pro and want to use airplay, this work great with an apple TV set up!

    http://airparrot.com/download/Mac/AirParrot.dmg
    Now like my iOS and MacBook Air I can use apple tv on my Mac Pro tower! Try before you buy!

    Yes count your self lucky.  AirPlay is extremely failure prone and very aggravating to most users.  Espeically if you do not have EXTREMELY high end networking hard ware if you are using WiFi.  If you insist on going down this road you can look into an app called AirPariot.  It might let you use AirPlay..... but again I wouldn't

  • I've got a Mac Pro and monitor reads

    Entering power save. Every time I restart this comes on, and the screen is black. HELP!!

    HI,
    Did you mean this to be in Older Displays and Monitors ?
    I would also try a PRAM reset.
    Shut down the computer.
    Restart it holding down Apple/CMD ( or ⌘)+ALT( ⌥)+P+R Keys until you have heard three Start Up Bongs.
    9:36 PM      Saturday; December 24, 2011
    Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"
      iMac 2.5Ghz 5i 2011 (Lion 10.7.2)
     G4/1GhzDual MDD (Leopard 10.5.8)
     MacBookPro 2Gb (Snow Leopard 10.6.8)
     Mac OS X (10.6.8),
    "Limit the Logs to the Bits above Binary Images."  No, Seriously

  • 2013 Mac Pro DisplayPort Monitor does not wake from Sleep.

    On my 2013 MP I have dual monitors:
    One connected DVI-to-MiniDisplayPort a ViewSonic 24"
    Second connected DisplayPort-to-MiniDisplayPort a MonoPrice 27" 2560x1440
    When the computer comes out of Sleep or Off the 27" display does not come out of Sleep Mode.
    If I unplug and replug the MiniDisplayPort connection from the MP the Display will turn on correctly.
    Never had this issue with the 24" both monitors go into a sleep/hibernate mode(yellow power light on displays) when the computer turns off or goes to sleep.
    When the computer comes out of sleep the 27" backlight turns on briefly but then goes back into sleep mode.
    Troubleshooting: PRAM Reset and alternative ports on the MacPro with no luck.
    Any thoughts??
    Thanks in advance.

    Hello natemac00,
    Thank you for using Apple Support Communities.
    For more information, take a look at:
    Apple computers: Troubleshooting issues with video on internal or external displays
    http://support.apple.com/kb/ht1573
    Have a nice day,
    Mario

  • Dual monitor on Mac Pro Xeon, monitors messed up after sleep

    Only recently, I find that sometimes, after waking up my computer, open pallettes have either switched sides or else a set workspace in a particular program is gone and all the pallettes are jammed over to one side. The only changes I've made recently are upgrading to Adobe CS6, upgrading to FormZ7, upgrading to Parallels 7 and adding RAM. Interestingly, though I trust my Mac tech, the RAM is faster than the spec for this machine, but the tech (20 years experience) says that's not a problem.
    Help would be appreciated.

    When using two displays, you create a much larger Extended Desktop on which various windows are arranged.
    When you remove a display, every window shown on the original (much larger) Extended Desktop  must be moved onto the desktop as it exists now, without the removed display. That sounds like what happens to you in the case where palettes are jumbled onto an edge of the screen.
    If one display is slow to acknowledge that is is still there and willing to work, it could cause Mac OS X to mark it "not present" and move everything to the other display. That might also explain certain other kinds of swapping to the other display.

  • Mac Pro Dual Monitor Problem

    I have a MacPro 4,1 with an ATI Radeon HD 5770 video card. I'm running OS X 10.6.8.  I have an Apple 20" Monitor and a Hannspree 23" monitor.  The problem I have is that when the computer goes into standby mode, 2 times out of 5 it will come back up with the primary monitor switched from the Apple to the Hannspree.  I then have to go into the Display Preferences and switch the monitor arrangement, and the menu bar.  Not a huge problem I grant you, but one that is vexing me nonetheless.
    Also on an occasion...perhaps 1 time out of 25 the Apple monitor has a case of the jaggies, and is only fixable by shutting down the whole computer and restarting.  This is really bad, considering it reminds me of when I get migrane headaches and my vision is constricted.  It almost makes me nautious.

    Apple's has three, 2xMDP + DVI
    https://support.apple.com/kb/TS3477

Maybe you are looking for