[markw10]

My fiancee just had an odd problem start with her MBP a couple days ago. When she closes the screen to transport her laptop and then reopens the screen it doesn't come out of sleep mode properly. I thought at first it was simply staying in sleep mode but you can hear the sounds when you press any keys so I think the computer itself is out of sleep mode but the screen stays dark. The only way we can fix it is to hold down the power button a few seconds to turn the computer off and restart it. I thought it was a one time thing but it has happened every 5 or so times she's closed her laptop the last couple times. Any idea what's causing this? She hasn't made any changes with software or hardware lately and is using the latest Leopard 10.5.2 and all patches.

[adamfishercox]

This happened to me one time. I closed the lid again, and it came to life and then went to sleep again, at which point I lifted the lid and it woke up. It's not optimal, but it's a workaround until it gets fixed.

[Simon]

Have you tried letting it just sit there for a while. I observed several times that it took almost a minute for the screen to finally come on. The reason was a timeout in some part of the graphics driver.

Have you installed all the recent graphics and OS updates?

And if so, you could still try reapplying the 10.5.2 combo update from Apple's website. After I did that back on 10.5.1 the behavior disappeared.

[adamfishercox]

Ok, I just had this issue, and my previous fix didn't work. But by pressing the power button and then hitting enter, it will shut down regularly as opposed to a force shutdown.

[jlgrandam]

I had this start happening to me on a 12" G4 powerbook and it turned out that the HD was dying. It died completely within about 2 weeks. I think it doesn't spin up properly when trying to wake the computer from sleep. I'd suggest a full backup SOON.

[adamfishercox]

The HD spins up fine, everything is working. I heard a new mail sound, and Instant Messages. Th only issue is that the screen fails to come on. I also just got this MBP a couple days ago, so I doubt the HD is going already... that would be a shame.

[adamfishercox]

Annnddd... apparently I just had a kernel panic with these same symptoms. It dies look to be graphics-card-related. Installing combo update now.

Sun Mar 9 14:57:55 2008
panic(cpu 1 caller 0x001A8C8A): Kernel trap at 0x00d699c5, type 0=divide error, registers:
CR0: 0x8001003b, CR2: 0x2f693000, CR3: 0x01437000, CR4: 0x00000660
EAX: 0x003d7ca0, EBX: 0x00000000, ECX: 0x00000000, EDX: 0x00000000
CR2: 0x2f693000, EBP: 0x2eb7bac8, ESI: 0x00000384, EDI: 0xffffffff
EFL: 0x00010246, EIP: 0x00d699c5, CS: 0x00000008, DS: 0x00000010
Error code: 0x00000000

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x2eb7b8d8 : 0x12b0e1 (0x457024 0x2eb7b90c 0x13321a 0x0)
0x2eb7b928 : 0x1a8c8a (0x460550 0xd699c5 0x0 0x45fc30)
0x2eb7ba08 : 0x19eb67 (0x2eb7ba20 0x427e080 0x2eb7bac8 0xd699c5)
0x2eb7ba18 : 0xd699c5 (0xe 0x48 0xc1d00010 0x1000010)
0x2eb7bac8 : 0xd69e69 (0x2426f000 0x0 0x2eb7bb64 0xd6a935)
0x2eb7bb38 : 0xd6b6a2 (0x2426f000 0x0 0x2eb7bb64 0x0)
0x2eb7bba8 : 0xd5b4a0 (0x2426f000 0x0 0x203 0x2426f000)
0x2eb7bbc8 : 0xd5fd4a (0x2426f000 0x0 0x0 0x2eb7bc0c)
0x2eb7bc28 : 0xd51f0e (0x2eb7bdfc 0x0 0x2eb7bc58 0x50d7c40)
0x2eb7bd28 : 0xb8b572 (0x2426f000 0x2eb7bdca 0x2eb7bdca 0x84)
0x2eb7bd88 : 0xb84592 (0x47d4000 0x2eb7bdca 0x2eb7bdca 0x84)
0x2eb7be28 : 0xb847aa (0x47d4000 0x2 0x425af58 0x19d311)
0x2eb7be98 : 0xb71ef8 (0x47d4000 0x706f7772 0x2 0x4b60f20)
0x2eb7bf48 : 0xb71feb (0x47d4000 0x0 0x47d4000 0x19d311)
0x2eb7bf78 : 0x13ea34 (0x0 0x0 0xde 0x19ebf0)
0x2eb7bfc8 : 0x19e93c (0x0 0x0 0x1a20b5 0x41d0128)
Backtrace terminated-invalid frame pointer 0
Kernel loadable modules in backtrace (with dependencies):
com.apple.NVDAResman(5.2.4)@0xb8a000->0xdc9fff
dependency: com.apple.iokit.IONDRVSupport(1.5)@0xb7c000
dependency: com.apple.iokit.IOPCIFamily(2.4.1)@0x63e000
dependency: com.apple.iokit.IOGraphicsFamily(1.5.1)@0xb60000
com.apple.iokit.IONDRVSupport(1.5)@0xb7c000->0xb89fff
dependency: com.apple.iokit.IOPCIFamily(2.4.1)@0x63e000
dependency: com.apple.iokit.IOGraphicsFamily(1.5.1)@0xb60000
com.apple.iokit.IOGraphicsFamily(1.5.1)@0xb60000->0xb7bfff
dependency: com.apple.iokit.IOPCIFamily(2.4.1)@0x63e000

BSD process name corresponding to current thread: kernel_task

Mac OS version:
9C31

Kernel version:
Darwin Kernel Version 9.2.0: Tue Feb 5 16:13:22 PST 2008; root:xnu-1228.3.13~1/RELEASE_I386
System model name: MacBookPro3,1 (Mac-F4238BC8)

[hedmisten]

I had a similar issue with my Macbook earlier today. I opened it up from sleep and it said that OSX failed to restart and to hold down the power button to restart.

[adamfishercox]

The AppleCare rep told me to reset SMC, then PRAM. Can't tell if it worked or not.

[adamfishercox]

The AppleCare rep said that there is an update coming out any day now which will fix it. If you need a fix right now, downgrade to 10.5.1. 10.5.2 was what broke it.

FWIW, combo updating to 10.5.2 didn't work for me.

[SkiBikeSki]

I'm having the same problem. And I too have 10.5.2 installed and an Nvidia card, so that seems to be the culprit. Along the lines of pressing the power button and Enter to shut it down, you could press R to restart. Or even better you could press S to put it back to sleep. Then maybe waking it up again by just pressing any key will wake the screen up too. I can't test it now cause I can't recreate the problem right now, but I'll try next time it happens.

[MacDevildog]

I have the same problem with my MBP 10.5.2. It only started after updating to 10.5.2 and installing the keyboard firmware update. unfortunately there is no way to undo the firmware update. Im waiting for an update to fix this problem. it happens to me several times a day since I am a student and am always closing my computer between classes.

[Kfunk]

Happens to me all the time now, MBP 10.5.2. I also installed the keyboard update. Glad i'm not alone.

[CMYKid]

glad i'm not the only one with this also...it's been plaguing me for a week or so. It seems most prevalent when I put it to sleep while watching somthing in VLC and then open the lid later. Pain in my ass though, have to hold the power button down to kill it and restart.

[MacDevildog]

I also am having a RAM issue, I think my second stick is dying. I am going to take my MBP into apple and see what they can do about my problems while it is still under warranty. i will let you all know how it goes.

[MacosNerd]

since applying 10.5.2 this has been happening to me, kind of frustrating.

[klb5090]

i was having this problem every time i shut my MBP and put it to sleep before the 10.5.2 update, recently its been intermittent, most of the time it does not happen but every once in a while it still happens. Usually another close and open will solve the problem for me

[CMYKid]

Apps continue to process, I can hear new mail sounds, instant messages come in, etc...all perfectly functional except for a completely dark screen. I can't put it to sleep blindly by pressing power button and then the S key. Its set to require a password when exiting screensavers or waking from sleep but even if I type that in and then Power-S it doesnt resleep. Meh. Starting to REALLY annoy me though.

I also have a fuzzy circle about an 1/8" round in the lower quarter of the screen thats substantially brighter than everything else.

[MacDevildog]

I have the same problem with my screen too.

[adamfishercox]

For me, it seems that iStat Pro was causing it. No idea how, but deletin the widget entirely worked.

[klb5090]

Originally Posted by adamfishercox 

For me, it seems that iStat Pro was causing it. No idea how, but deletin the widget entirely worked.

After reading this i deleted iStat Pro also and.... no problems since...interesting

[Simon]

A friend of mine also says he hasn't had the black screen after wake issues with his MBP ever since he removed the iStat Pro widget.

So obviously something's going on there. But what kind of connection is there between a screen waking from sleep and a widget?

[adamfishercox]

No idea. Widgets are sandboxed, right? They cannot mess with system files or anything?

[CMYKid]

I realized today that this ONLY ever happens when I wake it ffrom sleep when plugged into AC power.

It occurred to me that the ONLY time this ever happens to me is when I leave for lunch, then come back to my office and unsleep it. However, it doesnt happen when I go home and unsleep it.

Turns out the difference is that when I get back to work I plug it back in at my desk, open the lid, then walk down the hall for a beer. When I come home I put it on the coffeetable, unsleep it, go to the kitchen for a beer and sit on the couch. Its only later that I plug in to AC. I've tested this theory a few times now and if I come back from lunch, unsleep it and then plug in I have no problems waking and entering my password. If I plug it in first I have problems every time. When I get the beer apparently makes no difference.

I'm not running iStat as a widget but I am using it in the menubar. Hmmmm.

[klb5090]

I put iStat pro back in dashboard today and checked for updates and found one that says it fixes bugs etc. so i'm gonna give it a try and see if i get the display problem with this new version... i'll update later

[kcwrx02]

Removing istat pro fixed it for me too. Weeks and weeks of dealing with this had me at the point of switching back to my windows machine...well, not really. Can't get 4GB of RAM in my windows pc.

Thanks so much for the workaround.

[adamfishercox]

klb5090, did the new version work?