MacBook Pro 17" late 2009 - Black screen on boot, not even a grey screen

Question

MacBook Pro 17" late 2009 - Black screen on boot, not even a grey screen

Got a monstrous problem.

Started up my MacBook Pro (bought in Feb. This year, core 2 duo 2.88GHz/4 Gb RAM - basically the top specced model.)

Booted up today, no grey start-up screen. No screen at all. Yet I can still log into Snow Leopard, but again no screen. Rebooted into boot camp, heard windows start. Managed to log in again no screen. Volume controls, keyboard illumination work. Just a black screen.

I have tried resetting PRAM, etc. with no success. Cannot use hardware test as the screen simply does not start.

Any ideas before I throw the effing thing from a 5th floor window in frustration?

Is this the Nvidia problem other folk have experienced?

I am tempted to ask for a new machine spending 2 months on and off with my previous MacBook Pro in and out of repair if this is a hardware problem that has been fixed in recent Macs.

Regards,
J

MacBook Pro 17" 2.88, Mac OS X (10.6.3), Edinburgh, Scotland

Posted on Oct 24, 2010 3:23 PM

Reply

Answer 1

eww

Level 9

53,052 points

Oct 24, 2010 4:44 PM in response to John Boettcher

You obviously have a hardware problem, and since your machine is under warranty, it would seem wiser to take it in for a free repair than to throw it out the window.

The NVidia problem you're referring to is probably the one experienced by owners of 2007 and early 2008 MBPs that have NVidia 8600M GT graphics processors. Your machine doesn't, so you don't have that problem.

You aren't eligible to have your machine replaced with a new one unless it has been in for multiple unsuccessful repairs.

Reply

Answer 2

Oct 24, 2010 5:29 PM in response to eww

I tend to throw things out of windows when infuriated. You name it, PS3s, laptops, etc. Perhaps I should take extra diazepam as my G.P. Suggests... 😉

I'll see what John Lewis will offer; I have spent a fortune there and the staff know what problems I have had before.

I am not prepared to wait weeks for my machine to get fixed. The repair company my branch uses is hopeless.

Do you have any ideas what the problem might be, since I can boot into either partition, yet no graphics?

Faulty screen or chip?

Regards,
John

Reply

Answer 3

eww

Level 9

53,052 points

Oct 24, 2010 7:30 PM in response to John Boettcher

Faulty screen or chip?

Yes. Do you get any display on an external monitor?

Reply

Answer 4

Oct 24, 2010 7:44 PM in response to eww

No, alas. My first thought was to use the mini display port to connect to either a monitor or LCD screen; I am unsure which cable to buy though - they appear very short.

Regards,
John

Message was edited by: John Boettcher

Reply

Answer 5

eww

Level 9

53,052 points

Oct 24, 2010 7:55 PM in response to John Boettcher

Sorry — it's not clear to me whether or not you've connected an external display to your computer yet. If you haven't, doing so will be a very useful diagnostic exercise. If an external display shows a normal image while the built-in display remains dark or otherwise anomalous, there's a problem with the video cable or the LCD panel. If an external display behaves the same as the built-in screen, your logic board needs to be replaced.

Which video cable adapter to use depends on what input ports the display offers. The simplest way to run a test may be to make a Genius Bar appointment, where the necessary hardware will be on hand without your needing to buy anything.

Message was edited by: eww

Reply

Answer 6

Oct 27, 2010 8:24 AM in response to John Boettcher

I had the same problem just now. My 15" MBP (6.2). I followed the following steps and it worked for me. I used another Mac in my house to use screen sharing to accomplish these things:

1) access the /private/var/vm/ directory on the nonworking computer from the working computer. This is invisble so you will have to press cmd shiftg in the finder and go to /volumes/YOURHARDDISKNAME/private/var/vm to get there or use an application that lets you view invisble folders like PathFinder.
2) delete the sleepimage file
3) delete the /system/library/extensions.mkext file
4) eject the drive (drag to the trash)
5) press the power button to turn off the non working computer
6) turn the nonworking computer back on normally(cross your fingers) then if it works,
7) open up the the terminal.app in /applications/utilities
8) type sudo pmset -a hibernatemode 0
9) make sure there is no sleepimage file again

That worked for me...hope it helps for you!

Reply