Dead 17" display

I had my 17" Studio Display set up as a secondary display on my Mac system. I was working this morning and suddenly its screen went black. The ready light was normal, not blinking. The primary display, a 20" cinema display, was fine. I'm unable to connect the 17" to another port because it's a different plug.
The secondary display was a convenience, not a necessity. So I can live without it if the repair costs are too great.
Any diagnosis or suggestions.

Try an SMC reset:
http://support.apple.com/kb/HT3964

Similar Messages

  • "Dead" TB display as of this morning

    I didn't install the 1.2 firmware and I have the same "dead" TB display as of this morning. It was working yesterday. I unplugged power cords for more than an hour, tired a new LAN cable…nothing. My monitor is only 6 weeks old. Does anyone have ideas?
    I have a 2014 MacBook Pro.

    More information needed for someone to help... please click below and provide the requested information
    -Information FAQ http://forums.adobe.com/message/4200840
    Also, what you describe is USUALLY caused by an automatic Windows update (are you Windows?) that "breaks" something in the graphics display driver as it relates to PPro
    So... what is your graphics adapter, and have you gone to the vendor site (NOT Windows Update!!!) to check for a newer device driver
    IF you have an nVidia card, How to determine your nVidia driver version
    Right click in any open area of the Windows desktop
    Select NVIDIA Control Panel from the popup window
    Select SYSTEM INFORMATION at the lower left corner
    Driver version should be the 1st line in Details
    I have a GTX285 using driver 296.10

  • Mac air 2010 model just had screen replaced but its dead, no display nothing. the thunderbolt port works fine, this is how I'm asking my question i.e.; on the mac air, if anyone can help get this new screen

    hi
    im a newby to this but i really need help fixing my macbook air a1369 2010 model display screen, i have replaced all new but its just dead a black screen with no power getting to it at all even the backlit led is dead so the inverter isnt getting power to it either. everything works perfectly through another monitor hoocked into the thunderbolt port, its just theres no power going into the built in display.
    i would really appreciate some pointers as to whether theres any fuses that i could change or any pointers on getting the display to work at all. thank you for taking the time to read this and hope you can help a newby get back up & running.

    Confused, if you just had screen replaced was it working when you picked it up? I'd call whoever fixed it and report it ASAP.

  • Use dead iMac Display as monitor?

    I have a dead iMac (mobo fried) and was wondering if there is any way I can extract the display panel, and use either a bought or DIY/hacked adapter to use it as a standard monitor.

    K Shaffer wrote:
    This topic has been well-played here; the replies
    given to several inquiries have been researched.
    I'm not an expert, only having owned, repaired &
    donated to charities, some 140 Macintoshes.
    And I've not been heavily into dissecting my four
    iMac G4 computers with 17" LCD displays. But
    I do know the computer with a failed logicboard
    will not support the display; the graphics or video
    processor is integrated, and the panel has only
    a few of the necessary support circuits with it
    above the chrome arm in the panel's case.
    There are a few ways of integrating a different
    fully self-contained display into the dead iMac
    case and perhaps use the existing LCD or an
    other LCD and put additional circuitry into the
    base of the iMac G4 instead of the dead LB.
    And the earlier reply was essentially spot-on.
    Other discussions on this topic are most likely
    to be found in the proper forum for iMac G4,
    Apple - Support - Discussions - iMac G4 flat panel:
    http://discussions.apple.com/category.jspa?categoryID=137
    Later G5 & Intel-based iMac cases could be
    used, empty, to support an entire complete
    display of similar size; and the circuits likely
    would fit if the case had room enough, empty.
    An apology would be in order, if you came in
    to a retail establishment and talked to a tech
    with a determined to fail attitude like that.
    Good luck & happy computing!
    {edited to add correct iMac G4 forum link}
    My attitude was like that because i know what I am talking about. I now it is not a display. That is what bugged me. he talked to me like I had no idea what I am talking about. he also did not provide an answer like you that was well thought out and seemingly well researched, he said "I guess." I will, and have accepted, that this is not really possible. It was not his answer, it was his attitude towards the question. and just a BTW, I am talking about the intel imac. The white one, not the g4.

  • 22 inches of sad dead Apple Display

    Hello Everyone,
    Time and time again I have returned to Apple Discussions, looked over someone's shoulder, and solved some small issue. Tonight I return with the desperation of a man who with a big problem: a dead 22 inch Cinema Display. I am really hoping that my description of the symptoms may inspire one of the resident geniuses to pity poor novice me and guide me to the light of a working Cinema display.
    I have a 3 year old 22 inch display that has been the envy of all my friends. Just recently it has been dying. It looks great but it just dies from time to time. I get no response from the usb or power switch. I can turn my G5 on from the computer so i think it works. If I connect the keyboard straight to the G5 I can get the eject and stuff to work. Even if the Display is burned out shouldn't the circuitry enable the keyboard to work?
    I think it is the Display. I wiggled the cord and card once and got it to work, but to no avail this time. I don't think there is a cord issue. The latest death came while i was working on a letter- there was no jostle. The display just went dead.
    I will be starting the process of repairs tomorrow, as it has died and not come back tonight. Mine is three years old, but only has a year of work life on it. I expect more from Apple and a $3K display. Unless this fixes easy- and cheaply- it will be the last display I buy. Anybody else experience this? What is the next step to recovery?
    Good luck and Thanks.

    I wish my reply could be more helpful, but all I can say at this time is I feel your pain. Almost exactly. I too have a 3-year-old 22-inch Cinema Display, and a G5. I also have a second monitor, an older 15-inch Cinema Display. I leave my CPU running in sleep mode when I'm not using it. Two days ago, when I tried to awaken it in the morning, the 22-inch display was dead. Fortunately the 15-inch still works, but I miss those wide open spaces. The 22-inch could not be more lifeless. No LED indicators. I had the keyboard plugged into its USB port, but that didn't work any more either, so now I've plugged the keyboard into a separate USB hub.
    Were you able to resolve your issue? I'm trying to figure out troubleshooting steps. It would be nice if Apple offered tech support of some kind, but if they do, they do an excellent job of keeping that fact hidden.

  • Internal display dead, external display works fine

    Hi,
    I left my machine unplugged over the summer. When I came back, the internal display was dark.
    The machine was making all the right noises at startup, and the Caps Lock key worked, and I could make it beep louder and softer with the volume F-keys, so I hooked it up to an external monitor. It works perfectly with the external monitor.
    I went through the troubleshooting procedures - zap the pram, reset the power manager, boot from a CD - no video on the internal display.
    While connected to the external monitor, I ran the System Information program and looked for the internal display device. It wasn't there! Only the external one shows up.
    Does anyone have any suggestions?
    I can post screenshots or System Information reports if anyone wants them.
    Thanks,
    Doug

    Someone took it off my hands. They're going to use it with an external display.
    Thanks all!

  • Fix for Dead eMac Display

    I found a fix for my dead psychedelic eMac:
    1. Reset the PMU (explained in the battery replacement screen)
    2. Reset the PRAM on the first start (Option-Command-P-R)
    3. Hold the Power Button down on the first start. Listen for the loud tone.
    This worked for my dead eMac. I had tried everything. It was dead for two months. Sometimes I'd get weird psychedelic colored vertical lines.
    The Apple Store looked at it and wanted to replace the Logic Board for $700. I said "Thanks, but No".
    PS. Unfortunately, I got so frustrated that I bought a new Windows machine. I'm ashamed now. What a waste.

    Given Macfixit is an independent entity from Apple and has a tendency to hide many of its repairs behind a pay only site, I would printout their suggested repair, and take it with you when you next visit an authorized repair shop and ask them if they can see whether they think that repair would fix your machine.

  • X220 dead ips display - return instructions?

    Apologies if this has been covered somewhere in the forums and I missed it.
    I have a new X220 with the IPS display and after a couple weeks of use, the laptop display no longer works.
    The laptop seems fine otherwise, and it works with an external display port monitor.  When I have the monitor in mirrored mode, I can see a faint- not-readable screen on the laptop.  I'm certain that it is not just the brightness setting, as I can turn that all the way up with no effect (and view the brightness dialog working both on the external and barely perceivable on the laptop monitor).
    It seems like my display was just a lemon (maybe the backlight for the screen was poorly soldered/connected?).  Has anyone else experienced this?
    Regardless, my tolerance is pretty low for hardware failure so I'd like to unload this laptop with maximum velocity.
    How do I go about doing that?

    http://forum.lenovo.com/t5/Welcome-FAQs/Mark-s-Advice-About-DOA-Systems/td-p/55647
    Try this number:  800-426-7378
    Dave
    T430u, x301, x200T, x61T, x61, x32, x41T, x40, U160, ThinkPad Tablet 1838-22R, Z500 touch, Yoga Tab 2 Windows 8.1, Yoga Tablet 3 Pro
    Did someone help you today? Press the star on the left to thank them with a Kudo!
    If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"!
    If someone helped you today, pay it forward. Help Someone Else!
    English Community   Deutsche Community   Comunidad en Español   Русскоязычное Сообщество

  • Facing dead links in Webclipping and Omniportlet (wwwc - 44234)

    Hi all,
    I�am deploying webclipping and omniportlet. It is nice stuff and works very well (sometimes performance is bad).
    But, when a clipped Webpage is deleted, then in my nice webclipping-portlet an error occurs:
    Error: Page not found (wwwc - 44234).
    This looks somehow ugly. So, is there a way of detecting dead links and offer an alternativ content in the webclipping-content? Or, is there a way of getting notified, when portal detected a dead link / displayed the (wwwc - 44234) - Error?
    Many thanks,
    Michael

    Hello Tugdual Grall,
    thanks for inviting me, to contribute my experience and wishes with webclipping and omniportlet.
    Here is, what I would like to see:
    A Edit Default Section
    =======================
    1. Field: notify eMail:
    eMail to post dead-link occurrence to (including: dead url, time, date, name of the portlet, page-path, owner etc.):
    2. Field: Alternative content (when error occurs):
    "The content does not show up in the moment, please click [[email protected]] and visit us again later. Apology for the inconvienience."
    3. Fiel: Alternative link (if an error occurs):
    error-in-webclipping-page-on-myportal.html
    --> it would be groovie, if this alternative link could also be clipped!
    4. Field: Message for Time Out:
    "Please press the refresh button on your browser - thanks!"
    5. The error-detector should work, when a timeout occured, a dead link (wwwc - 44234) or some other error occured.
    B New Administering Portlet for the Portlet Provider of Webclipping / Omniportlet:
    ==================================================
    Similar to the Notification Portlet, there could be a portlet, which shows all the dead links / errors in omniportlet and webclipping portlets on one sight. Therfore the error-detector should be adding the dead link and connected information (including: dead url, time, date, name of the portlet, page-path etc.) into a table, which can be deployed by an omniportlet/webclipping-dead-link portlet for administering:
    date | dead url | page-path | portlet-name | owner | etc
    ===============================================================================================
    24.11.03 | www.yahoo.com | /pagegroup1/clippings/myYahooClipp | Yahoo_2 | Michael |
    The Page-Administrator can therefore easyly view errors and manage them.
    Thanks for asking me.
    With regards,
    Michael

  • Lost the LCD info display on the 7D

    I have lost the info display on the rear LCD of the Canon 7D. When I turn the camera on, nothing displays on the LCD, the screen is black. Before when I turned the camera on, it gave me basic information regarding settings, battery life, number of shots available. I no longer have that information. I am not sure if I turned something off somewhere, but I can't seem to get this information back again. I know there are settings on the top LCD, but I would like to see them on the back LCD also.  Is there any way I can get this screen to appear again?

    Does Live View work? If neither Live View or cycling through the Info button does nothing, then you probably have a dead rear display. (Don't forget, one of the Info button cycles is an off rear display.)

  • New Socket takes too long / how to stop a Thread ?

    Hello to everyone,
    I have a problem that I have been hunting this ol' Sun website all day for a suitable answer, and have found people who have asked this same question and not gotten answers. Finally, with but a shred of hope left, I post...
    My really short version:
    A call to the Socket(InetAddress,int) constructor can take a very long time before it times out. How to limit the wait?
    My really detailed version:
    I have a GUI for which the user enters comm parameters, then the program does some I/O while the user waits (but there is a Cancel button for the Impatient), then the results are displayed. Here is quick pseudocode (which, by the way, worked great before there were Sockets in this program -- only serial ports):
    Main (GUI) thread:
         --> reset the stop request flag
         --> calls workerThread.start(), then brings up a Cancel dialog with a Cancel button (thus going to sleep)
         --> (awake by dialog closing -- dialog may have been closed by workerThread or by user)
         --> set stop request flag that worker thread checks (in case he's still alive)
         --> call workerThread.interrupt() (in case he's alive but asleep for some reason (???))
         --> call workerThread.join() to wait for worker thread to be dead (nothing to wait for if he's dead already)
         --> display worker thread's result data or "Cancelled..." information, whichever worker thread has set
    Worker thread:
         --> yield (to give main thread a chance to get the Cancel Dialog showing)
         --> do job, checking (every few code lines) that stop request flag is not set
         --> if stop request, stop and set cancelled flag for Main thread to handle
         --> if finish with no stop request, set result data for Main thread to handle
         --> take down Cancel Dialog (does nothing if not still up, takes down and wakes main thread if still up)
    THE PROBLEM: Worker thread's job involves doing IO, and it may need to instantiate a new Socket. If it is attempting to instantiate Socket with bad arguments, it can get stuck... The port int is hardcoded by the program, but the IPAddress must be typed by user.
    If the arguments to Socket(InetAddress, int) constructor contain a valid-but-not-in-use IP address, the worker thread will get stuck in the Socket constructor for a LONG time (I observed 1m:38s). There is nothing the Main thread can do to stop this wait?
    EVEN WORSE: If the user clicks the Cancel Button during this time, the dialog goes away soon/immediately, but then the GUI appears to be hanging (single-threaded look) until the long wait is over (after which the "Cancelled..." info is displayed).
    MY QUESTION: Is there nothing the Main thread can do to stop this wait?
    Your answers will be sincerely appreciated. Despite my hopeless attitude (see above), the folks at this forum really have yet to let me down ...
    /Mel

    http://developer.java.sun.com/developer/technicalArticles/Networking/timeouts/

  • MacBook Pro is not turning on

    I close my Macbook, and a few minutes ago, I tried to power on again, and it doesn´t turn on.
    It seems to be dead.
    Display is black like powered off.

    Thank you very much, Csound1 (Far from anything.....? I think so close...) 

  • Buttons Wont work

    I have not used my 30gb color video Ipod for about a month. I got it yesterday to use it and it would not turn on. I switched the button lock back and fourth, nothing. then I plugged it in to charge it and it started to charge, but it wasn't dead. the display came on and it looked like it was frozen in mid song as the title appeared but the counter wasn't moving. I tried to reboot it but that is when I started to realize that the buttons were not responding. the lock button works as the lock icon turns on and off as i slide the switch but the buttons or the click wheel do not respond yet they feel supple and click and feel like they are fine. I have since plugged it into my computer and it syncs and such but no go with the controls. Any ideas anyone??? Thanks in advance.
    core2duo   Windows XP  

    If you can plug that in to the computer, then I recommand a restore of your iPod. Plug it in and iTunes should show up. Go to the iPod preferences under the Source list of iTunes. There is a restore button. Press it and follow the instructions. Restoring the iPod means that it will erase all the content on the iPod -- including music and other files and its own software -- and restalling it with new data.

  • ITunes 10.2.2.12 crashes system with full screen visualizer

    Can't seem to find a useful answer.  1 year old HP Pavillion running Win 7 (fully up to date), Core 2 Quad Q8200, 64-bit, 4Mb L2 cache, 6Gb DDR3, NVIDIA GeForce G210.  A few months back I noticed that whenever I had iTunes full screen visualizer running, after about 1/2 hour or so (time varies but seems to play for a while before crapping out) my system would freeze and become completely unresponsive, requiring a hard power-down (keyboard and mouse - dead, monitor displays "no input signal").
    I do not have this issue when visualizer isn't running.  Also don't see this happening (yet) when visualizer isn't full screen.
    My first round with this led me to believe there was a conflict with Windows going idle and iTunes not working with Windows to keep it active.  So I disabled my idle times completely and that seemed to resolve it.  Was able to listen to hours of playback without issue.  Now, this week, it started happening again.  Play iTunes, turn on full screen visualizer, after a short while sound will stop, screen will die, system will freeze.
    Not interested in rolling back to earlier versions of iTunes.  I want iTunes to work properly.  I can't use it if it doesn't work.
    Ideas on what I should be looking at/for?  Video card problem?  Temperature problem?  ???
    I work in IT, but not with hardware, so this is a little outside my area.

    update:  it's starting to happen much more quickly and frequently - basically all the time now.  last time was 43 secs into the first song.  I can no longer use the visualizer at all.  This is the first real problem I've had with this machine since purchasing it 1/2010.
    To clarify a little:  my system doesn't go "dead" - if it means anything the indicator lights are blue whereas they're orange when inactive.  It's the UI that dies - no signal to the monitor, no sound, no mouse or keyboard input, and no way to move forward without pulling the plug and restarting. Everything seeeems to come back ok when I restart, although I did start having wireless issues yesterday (a 3yr old linksys N).  Separate issue or not, not sure.
    I'm thinking it's gotta be hardware related, but i've been wrong once before.
    Basic out of the box box:
    64 bit Quad-Core
    Intel G43
    NVIDIA GeForce G210
    512MB DDR2 dedicated to graphics
    PCI Express 2.0 x16
    Memory:
    6GB DDR3 1066, max 8GB

  • T21 just stopped working!

    Hi, I'm new to the forum.  I have a trusty T21 that I use for general work and serial interfacing .  It has been stored for a few months - I plugged it in and got nothing on switch-on.  I have replaced the main battery with a new one - still nothing.  The HDD led lights and there is a very quiet hum from the laptop.  Screen is dead - no display at all.   HELP!  Any ideas / fixes? Please.....

    You can try that as well :
    1.) Unplug the power cord and the battery.
    2.) Press the 'Power' Button 10 times repeatedly.
    3.) Then hold the 'Power' Button down for 25 seconds.
    4.) Put the battery back in and plug the power cord back in.
    5.) Turn on the system.
    Knowledge is of two kinds. We know a subject ourselves, or we know where we can find information on it.
    ThinkPad T510 4313-CTO Windows 8 x64 - Intel Core i7-620M - NVIDIA NVS 3100M - 8GB RAM - 240GB SSD- Intel Centrino Ultimate-N 6300 - Gobi 2000.
    ThinkPad Helix 3697-CTO Windows 8.1 x64 - Intel Core i7-3667U - Intel HD Graphics 4000 - 8GB RAM- 256GB SSD - Intel Centrino Advanced-N 6205 - Ericsson C5621gw

Maybe you are looking for