Macbook won't detect external display anymore - Random shutdown injury??

Hi,
my Macbook has the dreaded random shutdown thing happening, often it can't even get through the startup sequence. If I reset the PMU and PRAM and check the disk every week I can keep it running. Applecare are making not particularly helpful suggestions like "run it in safe mode" - hello people, random means it can take days to happen again... I use this computer for work so I need it at full capacity every day!!!
Anyway, enough angry ranting. The casualty of today's RS and subsequent PRAM PMU resetting is my external display (Viewsonic LCD). The macbook is no longer sending signals to it (display says "no signal"). When I ask the macbook to "detect displays" nothing happens. I have restarted the macbook several times and unplugged and replugged the display connection it doesn't help. Yes, I have the AC power cable plugged in on the Macbook (I know it doesn't like talking to the screen if I don't).
The display and macbook have always worked fine together in the past...
Does anyone have any suggestions on how to test for causes or fix this display related problem?
MacBook   Mac OS X (10.4.8)  
Powerbook G4   Mac OS X (10.4.2)  

You don't mention ever having brought the problem to Apple's attention, or what resulted from your request for Apple's help with it. This isn't a universal or widespread problem. It may be a hardware fault in your own equipment that needs to be resolved with a repair, or it may be a software problem (corrupt file, incompatible software conflict, update needed, etc., etc.). You seem to think Apple should have fixed it for you without your lifting a finger, and you're eager to complain about Apple's lack of support. But you've offered nothing to indicate that Apple even knows you need support. You do have to ask for it. Have you done so?
We have no idea what steps you've taken to try to narrow down the possibilities, e.g., making sure the monitor is turned on; trying a different video cable as iVmichael has suggested; testing the monitor with the same cable on a different computer; testing a different monitor with the same cable and then with a diferent cable on your computer; substituting a different cable adapter, if you are using one; applying all applicable system software updates and then Repairing Permissions and Repairing Disk; starting in Safe Mode and seeing whether the monitor is recognized and activated then; seeing whether the monitor is detected in System Profiler; and so on. You may have done some of these things, but you haven't told us about them or about the results.

Similar Messages

  • HT5167 after I updated to 10.7.4 my macbook pro 2011 doesn't detect external display anymore what should I do?

    after I updated to 10.7.4 my macbook pro 2011 doesn't detect external display anymore what should I do?

    after I updated to 10.7.4 my macbook pro 2011 doesn't detect external display anymore what should I do?

  • My mid-2010 10.8.2 iMac won't detect external displays.

    My mid-2010 10.8.2 iMac won't detect external displays. I've tried using a third-party minidisplay port to DVI adapter, as well as an Apple-brand minidisplay port to VGA adapter. The monitor I'm using is a Dell SP2008WFPt. It is a functional monitor. I've tried resetting the PRAM, repairing my disk permissions, rebooting, and doing all sorts of wacky stuff with the order I plug things in. Is there a solution? It seems like lots of folks are having the same problem.
    Thanks! This is really starting to make me angry.

    If 10.7.0 or later...
    Bootup holding CMD+r, or the Option/alt key to boot from the Restore partition & use Disk Utility from there to Repair the Disk, then Repair Permissions.
    If that doesn't help Reinstall the OS.

  • Macbook will not detect external display

    Was using a $7 aftermarket minidisplay port to HDMI cable with success for about 2 months with no problems detecting external display.  Started having problems (it would randomly detect until it eventually would not at all) and tried all solutions I could find in discussion boards to no avail.  I recently bought a $40 cable from the apple store and it worked fine for about a month and now it only recognizes my external display about 50% of the time (which is how the problem began the first time).  Very frustrating!  What is the deal here? 

    Did you have any luck resolving this? I have had exactly the same issue when updating the EFI Firmware to Version 2.8 (the latest for a Mid-2013 MacBook Air 6.2 model) - MBA61.0099.B12
    I've tried flushing the NVRAM/PRAM and also resetting the SMC but no joy. I'm trying to drive an AOC Q2963 monitor using a display port connector. Annoyingly, I don't think there's a way to rollback to a previous firmware version.

  • Imac running Yosemite won't detect external display

    I previously was using a 2008 iMac desktop and running OS X Yosemite. I was using dual monitors (other monitor being Insignia brand) and everything worked fine. Since this was an earlier mac version, I was using the Mini DVI to VGA Adapter to connect. Last week, I got a brand new iMac (Mid 2014 version). I am running OS X Yosemite as well, but now it won't detect any displays. I'm now using the Thunderbolt cable to connect so I wonder if that has anything to do with it. But I have used that same Thunderbolt cable before on my macbook and it worked just fine.
    I've tried restarting, resetting the PRAM and everything. I don't know what else to do. Help!

    Thanks for the reply, but tried everything and it still won't work. Rebooted, installed updates, cleared PRAM, everything. It will not detect the displays at all. Maybe there is something wrong with my VGA cable.

  • Hello Apple Fix the display issue.  MAcbooks suddenly stop detecting external display!!!

    Bought another new minidisplay to HDMI and suddenly stopped detecting external display!   However, it works randomly with no rhyme or reason.  I have tried everything.

    No answer

  • New macbook pro 15" won't detect external display using vga adapter

    Hi there
    I've tried multiple monitors and connectors but i can't get my mac to detect an external display. it responds as if nothing is connected. I'm fully up to date software-wise.
    any ideas?
    thanks for any help!!

    Hi, I'm having the same problem, tried to connect both a Viewsonic and a Hanspree. Was happy to find your response here, but I just got the Moshi adapter with the macbook pro so it seems silly it would have gone bad. :/
    I suppose I'll take it into the Apple Store and see what they say. Thanks!
    ^_^

  • MBPro won't detect external display on DVI

    Hi Folks,
    I have a strange problem that gives me quite some headache:
    Is use a MacBook Pro 3,1 2.2 Ghz, 4GB RAM, 128MB NVidia something together with a Samsung SyncMaster 215TW.
    For the past year I was using my external screen without any trouble, connecting it via DVI to the mac. Every night I turn down the lid putting the notebook in sleep mode and switch off the monitor. Exactly as I did yesterday. But this morning however the external display didn't wake up as usual it did just nothing - was not even detected via the detect display function. And this is still the case right now.
    So when I plug (or unplug) the DVI to the external something is still going on. I get the blue screen (don't get that wrong that used to appear just before it would expand the desktop to the external screen, but then it switches back as if there would be nothing connected.
    No relevant entries in any logfile. System Profiler shows "Status: No display connected". The display itself says some no connection message if unplugged and - get this - falls to sleep mode right after I plugin the dvi connector to the mac.
    I tried all this:
    -reboot (with display connected & without display connected and all other imaginable combinations) - no positive result
    -the display via DVI-VGA adapter works (but the image is not as nice unfortunately)
    -reset PRAM (boot with optioncommand+PR)
    -reset the entire thing (no power, no battery and hold the powerkey for 10 secs.) nothing
    -connect some other external display to the mac via DVI - works perfectly
    -connect the display via DVI to an other macbook pro computer - works perfectly too
    -hard reset the display via the (red) support menu - no result
    -an other DVI cable - no result
    -booted from the leopard install cd - same thing
    -booted from an other harddisk with 10.4.10 (removing the internal disk)- same strange behaviour with the old system
    -booted ubuntu linux 8.04 - even here the same problem X doesn't recognize the external display if it is attached to the DVI port also no entries to the logs here.
    -SwitchResX and tried to reset the display setting from there (vendor id 4c2d & product id 213 & 214) but still no success.
    - called the apple support and my distributer of trust - no ideas but could be a hardware fault (mmh ok... but why do all other display I tried work perfectly with that beast of macbook pro but not any SyncMaster 215TW?!? that worked great for the whole last year)
    I guess the macbook had a very bad dream that very last night about mac eating foo-bars that crawl through DVI cables from any 215TW display.
    As for now I have a date with the local apple service partner -- in three weeks (it's holiday time in g.o. germany). Don't know what to tell him: Probably I'll need to go there with the screen to show them the entire scenario. Hopefully they (still) think it's a problem with faulty apple hardware (or system software) and replace the logic board.
    But I'm still in hope! Is there anybody out there having an idea with what I could try next to bring back the love between my macbook and the lovely 215TW display?
    greetings,
    brutus banane

    I have recently bough a new Macbook Pro 15.4", it worked first time with a Samsung Syncmaster 2493HM but after a few days the 'detect display' utility ceased to connect, then a short while after on start up I was getting a blank screen with a flashing folder with '?' on it, preventing me from booting up successfully.
    I tried the reset p-ram, didn't work then I tried an archive install of OSX and that ironed out all the creases - for a day, there has been no flashing folders on start up but the Samsung has failed to be detected and this morning wouldn't work no matter how many restarts or cable disconnecting attempts.
    So I called Apple helpline, told the guy what had happened, he mentioned to try the install discs again with the display connected to see of the MBP sent a signal to it, after choosing the language in the OSX installer, the display was once again recognized! I didn't have to proceed any further with the install discs so quit, reset and ejected the install discs and all seems well again.
    For how long i wonder?
    I have no idea of this will work for anyone else but it works for me at the moment.
    Interested to see when and how this finally gets solved!
    T.
    Message was edited by: Tyke Tyler
    Message was edited by: Tyke Tyler

  • Macbook Air stopped detecting external displays

    My MBA (Mid 2011) has stopped detecting ANY external display. Have tried different leads (MDP > HDMI and VGA) with no luch, My MBA (Mid 2011) has stopped detecting ANY external display. Have tried different leads (MDP > HDMI and VGA) with no luck. It seems to have happened since I have updated to Mountain Lion a few days ago.
    Has anyone had similar problems?

    You should also ask this in the MacBook Air forum. This is the forum for the white and black plastic MacBooks that were discontinued in 2010. You should also post this question there to increase your chances of getting an answer.
    https://discussions.apple.com/community/notebooks/macbook_air
    And the Mountain Lion Forum https://discussions.apple.com/community/mac_os/os_x_mountain_lion

  • MacBook no longer detects external display

    When I hook my computer up in my home office I connect an external display using the Apple VGA dongle.
    Previously, when I inserted the dongle the display would blank out for a moment while detecting the display, then reappear with the VGA output enabled. This is no longer the case. When I insert the dongle, my screen doesn't blank out, and the VGA output will not enable. Its like it doesn't even know I'm inserting the dongle.
    I have inspected the dongle for broken pins and dirt, but it appears to be making a good connection.
    Is there something wrong with my Mac, or is it the dongle? Is it worth taking this to a genius bar in hopes they can try a different dongle, or shed some light on the situation? Thanks in advance.

    Try plugging the display in and then going to System Preferences>Displays and clicking the "Detect Displays" button.

  • Help: 2011 imac 27" won't detect External Display connected via thunderbolt to HDMI

    I have an 2011 imac 27" and I'm trying to connect an Acer 23" monitor as an external display. I'm using a miniDV(thunderbolt) to hdmi cable. For some reason the computer is unable to detect the display. However when I reboot into windows via bootcamp, the display is detected and works perfectly.. Any way to force thunderbolt to detect this?

    Well, weird outcome... I took the monitor back and exchanged it for a better model, better brand. The thunderbolt to hdmi cable works fine with this new monitor in osx. Thanks again..

  • Macbook Pro 2011 won't detect external display.

    Firstly - I've searched this problem several times now and I've found this problem in four of five discussion topics on this board, each with 4 or 5 pages of people adding "I'm having the same problem" but in all of that there wasn't a single response from Apple, instead they just 'archived' the discussions and hoped that people would just go away.
    That's pretty ******* disgusting customer service, considering the amount of money we're paying for your products. You owe us at least for them to ******* work properly - not just ignore major problems, which are clearly present for quite alot of your customers.
    For months I've had no problems just plugging my MBPro into an external monitor by DVI using the Apple certified DVI-thunderbolt connector.
    For some reason, a few weeks ago, the MBPro stopped detecting the monitor.
    I have to spend about 20 minutes ******* around, unplugging and replugging in the leads, restarting with and without the leads plugged in, resetting the p-ram, reinstalling OSX 10.7 and it always seems to be just a random time when it decides to start working.
    I'm not just some kid ******* around with an expensive computer for the fun of it. I make a living using this system and I need the big screen for the work I do. I don't have the time to spare every sodding day to be ******* around with **** that doesn't work properly.
    At first I thought the problem was restricted to just my work display as it appeared to work fine on all other displays. However, last week I was giving a presentation at work to a company who were potentially about to spend mega bucks giving us some work. I turn on the screen and plug in my computer to show the presentation. Nothing happened. luckily I was able to quickly transfer the presentation to another working computer (a PC) and continue on.
    But seriously, please justify spending over £1000 on a computer that can't perform the simplest of tasks without spazzing out?
    And secondly - stop ignoring this problem and get fixing it. Now!

    Hi, I'm having the same problem, tried to connect both a Viewsonic and a Hanspree. Was happy to find your response here, but I just got the Moshi adapter with the macbook pro so it seems silly it would have gone bad. :/
    I suppose I'll take it into the Apple Store and see what they say. Thanks!
    ^_^

  • Macbook can't detect external display via DVI cable

    I just bought Samsung PX2370 monitor and attempt to connect it with my Macbook Aluminum (late 2008). I have mini display port to DVI adapter and DVI cable. When I hook up my Mac, nothing comes up. The screen on macbook goes blue briefly and then back to normal, but nothing has been detected. I've manually set the source of signal to DVI, and tried to use Detect Display but nothing happens. Even I try to detect the monitor by using Windows 7 (via bootcamp), the display remains idle.
    I had tested the monitor using DSLR although by HDMI, it work.
    Any help would be much appreciated.

    Hey hparekh and welcome to the forum -
    It looks like you have the correct hardware. You should check your connections... make sure your using the Mini DisplayPort and not the Ethernet port (common mistake) and all of the connections are plugged completely. Make all of your connections with your MacBook on and then turn your Dell on. You might need to go through your Dell's setup to make sure that it's recognizing a DVI input rather then HDMI.
    Might be a bad DVI cable or a defective monitor or maybe a bad Mini DisplayPort to DVI adapter. Are they all new products?

  • Macbook Pro not detecting external display

    I can't seem to make this work. I'm using a MiniDP-DVI cable which is plugged into an DVI cable plugged into an external monitor. I know it works because I have tried it on other computers and it has worked on the Macbook (erratically).
    I've reset the PRAM several times and it has not fixed the problem. I did it in this order:
    1. Remove adapter from computer
    2. Shutdown
    3. Press Option Command P R until the second chime is heard.
    4. Log on as usual
    5. Reconnect adapter to MBP
    This is what the system log states when I plug the adapter in:
    Oct 27 20:47:01 SMBP.local WindowServer[80]: Received display connect changed for display 0x42732c0
    Oct 27 20:47:01 SMBP.local WindowServer[80]: Created shield window 0x66 for display 0x042732c0
    Oct 27 20:47:01 SMBP.local WindowServer[80]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1
    Oct 27 20:47:01 SMBP.local WindowServer[80]: Received display connect changed for display 0x3f003d
    Oct 27 20:47:01 SMBP.local WindowServer[80]: Received display connect changed for display 0x3f003e
    Oct 27 20:47:01 SMBP.local WindowServer[80]: Received display connect changed for display 0x3f003f
    Oct 27 20:47:02 SMBP.local WindowServer[80]: Display 0x042732c0: GL mask 0x1; bounds (0, 0)[1280 x 800], 9 modes available
              Main, Active, on-line, enabled, built-in, boot, OpenGL-accel, Vendor 610, Model 9ccb, S/N 0, Unit 0, Rotation 0
              UUID 0x0000061000009ccb00000000042732c0, ColorProfile { 3, "Color LCD Calibrated 2012-06-28"}
    Oct 27 20:47:02 SMBP.local WindowServer[80]: GLCompositor: GL renderer id 0x01024301, GL mask 0x0000000f, accelerator 0x00004333, unit 0, caps QEX|QGL|MIPMAP, vram 451 MB
              texture units 8, texture max 8192, viewport max {8192, 8192}, extensions FPRG|NPOT|GLSL|FLOAT
    Oct 27 20:47:02 SMBP.local WindowServer[80]: Display 0x003f003f: GL mask 0x8; bounds (2304, 0)[1 x 1], 1 modes available
              off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 3, Rotation 0
              UUID 0xffffffffffffffffffffffff003f003f
    Oct 27 20:47:02 SMBP.local WindowServer[80]: Display 0x003f003e: GL mask 0x4; bounds (2305, 0)[1 x 1], 1 modes available
              off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 2, Rotation 0
              UUID 0xffffffffffffffffffffffff003f003e
    Oct 27 20:47:02 SMBP.local WindowServer[80]: Display 0x003f003d: GL mask 0x2; bounds (2306, 0)[1 x 1], 1 modes available
              off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 1, Rotation 0
              UUID 0xffffffffffffffffffffffff003f003d
    Oct 27 20:47:02 SMBP.local WindowServer[80]: Created shield window 0x68 for display 0x042732c0
    Oct 27 20:47:02 SMBP.local WindowServer[80]: Created shield window 0x69 for display 0x003f003f
    Oct 27 20:47:02 SMBP.local WindowServer[80]: Created shield window 0x6a for display 0x003f003e
    Oct 27 20:47:02 SMBP.local WindowServer[80]: Created shield window 0x6b for display 0x003f003d
    Oct 27 20:47:02 SMBP.local WindowServer[80]: Display 0x042732c0: MappedDisplay Unit 0: Startup Mode 1280 x 800, CGSThirtytwoBitColor, Resolution 1, IOMode 0x80000000, IODepth 0x0, IOReturn 0x0
    Oct 27 20:47:02 SMBP.local WindowServer[80]: Display added
    Oct 27 20:47:02 SMBP.local WindowServer[80]: Display removed
    Oct 27 20:47:02 SMBP.local WindowServer[80]: Display 0x042732c0: GL mask 0x1; bounds (0, 0)[1280 x 800], 9 modes available
              Main, Active, on-line, enabled, built-in, boot, OpenGL-accel, Vendor 610, Model 9ccb, S/N 0, Unit 0, Rotation 0
              UUID 0x0000061000009ccb00000000042732c0, ColorProfile { 3, "Color LCD Calibrated 2012-06-28"}
    Oct 27 20:47:02 SMBP.local WindowServer[80]: GLCompositor: GL renderer id 0x01024301, GL mask 0x0000000f, accelerator 0x00004333, unit 0, caps QEX|QGL|MIPMAP, vram 451 MB
              texture units 8, texture max 8192, viewport max {8192, 8192}, extensions FPRG|NPOT|GLSL|FLOAT
    Oct 27 20:47:02 SMBP.local WindowServer[80]: Display 0x003f003f: GL mask 0x8; bounds (2304, 0)[1 x 1], 1 modes available
              off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 3, Rotation 0
              UUID 0xffffffffffffffffffffffff003f003f
    Oct 27 20:47:02 SMBP.local WindowServer[80]: Display 0x003f003e: GL mask 0x4; bounds (2305, 0)[1 x 1], 1 modes available
              off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 2, Rotation 0
              UUID 0xffffffffffffffffffffffff003f003e
    Oct 27 20:47:02 SMBP.local WindowServer[80]: Display 0x003f003d: GL mask 0x2; bounds (2306, 0)[1 x 1], 1 modes available
              off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 1, Rotation 0
              UUID 0xffffffffffffffffffffffff003f003d
    Oct 27 20:47:03 SMBP.local WindowServer[80]: **DMPROXY** (2) Found `/System/Library/CoreServices/DMProxy'.
    Oct 27 20:47:03 SMBP.local WindowServer[80]: Display 0x042732c0: MappedDisplay Unit 0; ColorProfile { 3, "Color LCD Calibrated 2012-06-28"}; TransferTable (256, 3)
    Oct 27 20:47:04 --- last message repeated 1 time ---
    Oct 27 20:47:04 SMBP.local WindowServer[80]: **DMPROXY** (2) Found `/System/Library/CoreServices/DMProxy'.
    Oct 27 20:47:04 SMBP.local WindowServer[80]: Display 0x042732c0: MappedDisplay Unit 0; ColorProfile { 3, "Color LCD Calibrated 2012-06-28"}; TransferTable (256, 3)

    I had the exact same behavior and log and I solved the issue by replacing the MiniDP-DVI adapter. I tried the "broken" adapter on another set of laptop+display and it was working there, so that made me think the adapter was ok, when apparently it was not.

  • Solution to 'my macbook won't detect my wifi anymore'

    So my macbook connected to my wifi fine, then suddenly it stopped detecting it even though every other device I had detected it fine. After hours of searching the web I finally found a solution that worked for me. I saw that this problem is fairly common so I thought I'd share it on here aswell.
    All you need to do is go to network preferences, select airport, then advanced, then under preferred networks delete the network you're trying to detect (you may want to write down its name at this point), then click apply. Turn off airport then turn it on again. Then click 'join other network' and manually type in your networks name and password in and it should connect.
    This method worked for me and hopefully it'll work for anyone else having this problem.

    You should mark this post with the "This solved my question" check mark so that others no there is a solution here rather than a post with only views and no replys.  Good find by the way!

Maybe you are looking for

  • Suggestions for SAP BI/BW training

    Hello All, I am a newbie to SAP without any prior knowledge of programming. I am a data analyst by profession with 5 years of working experience. Now I would like to learn SAP BI/BW module. I would like to take training in SAP BI. I am not fully awar

  • Is there any apps for the apple ipod 6g.

    The apps I already have are getting really old really fast.

  • Hey friends need some help !

    I have to create an IDOC  when the credit memo is created. I have the outbound idoc generation code  and also the ale configured .Shall I use a user exit for VF01 and paste the IDoc generation code there ?

  • List of materials with valid Group Counters (No. of valid routing variant)

    Hi, do you know, how to get a list of the materials together with the information, what Group Counter is currently valid? That means if a material have 3 variants of routings, to show for example that the variant number 3 is currently valid. Thank yo

  • Speeding up rsync (Gigabit NIC)

    I'm replacing a fileserver running 2.6.20-ARCH and need to transfer about 2.9 Terabytes from the old to the new (also running 2.6.20-ARCH.)  Both servers are from SuperMicro, the first has an 8 drive (each drive = SATA, 500 GB) hardware RAID5 array r