Ticket Options

Question Profile

Question Details

TICKET ARCHIVE -> Computer screen goes blank.

Adam Ohrt - Mar 4, 2008 - 9:42 pm

The screen of my ibook G4 goes blank after it either gets a little bumped or even if it sits too long. This is really driving me nuts. It gives me a report ofTue Mar 4 21:26:14 2008
panic(cpu 0 caller 0x000AEB84): "Uncorrectable machine check: pc = 00000000098513B0, msr = 0000000000149030, dsisr = 42000000, dar = 00000000F0205F30\n" " AsyncSrc = 0000000000000000, CoreFIR = 0000000000000000\n" " L2FIR = 0000000000000000, BusFir = 0000000080000000\n"@/SourceCache/xnu/xnu-1228.3.13/osfmk/ppc/trap.c:975
Latest stack backtrace for cpu 0:
Backtrace:
0x0009B2F8 0x0009BC9C 0x00029DC4 0x000AEB84 0x000AEE04 0x000B28F8
Proceeding back via exception chain:
Exception state (sv=0x211eb280)
PC=0x098513B0; MSR=0x00149030; DAR=0xF0205F30; DSISR=0x42000000; LR=0x0985148C; R1=0x16F4F7B0; XCP=0x00000008 (0x200 - Machine check)
Backtrace:
0x00000000 0x0985148C 0x0985946C 0x09859510 0x0985FB4C 0x0985B134
0x09852F74 0x09860C38 0x0984CC84 0x0984CD84 0x007E1BE4 0x007E695C 0x007ED344 0x007ED630
0x007D3398 0x007D35DC 0x0003F93C 0x000B0454
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.ndrv.ATY,Via.0x984ccbc(1.0.0b94)@0x984b000->0x9869fff
com.apple.iokit.IONDRVSupport(1.5)@0x7e0000->0x7f7fff
dependency: com.apple.iokit.IOPCIFamily(2.4.1)@0x7a6000
dependency: com.apple.iokit.IOGraphicsFamily(1.5.1)@0x7ba000
com.apple.iokit.IOGraphicsFamily(1.5.1)@0x7ba000->0x7dffff
dependency: com.apple.iokit.IOPCIFamily(2.4.1)@0x7a6000
Exception state (sv=0x2a7eda00)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

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:15:19 PST 2008; root:xnu-1228.3.13~1/RELEASE_PPC
System model name: PowerBook6,5

Please help. please please please. Thank you so much.
Adam

ScottW - Mar 5, 2008 - 6:17 am

Admin,

If it wasn't for the "bump" comment, I would typically say, check your energy saver settings in System Preferences and see when your screen is set to turn-off which is usually after a period of inactive time. Adjust this will delay your screen from turning off so quickly (or at all).

The interesting question is the "bump" part. When the screen is bumped, you're saying the display will shut off? In these cases, what causes the screen to come back on? Does pressing a key or moving the house bring it back to life? Or do you have to reboot or "bump" it again.

Scott

Adam Ohrt - Mar 5, 2008 - 7:39 am

It has to be restarted. I want to say it's a loose cable but it shouldn't come back on when restarted if that was the case. I'm much more familiar with pc's this is my girlfriends computer. We just installed Leopard, Ms Office 2008, and Adobe programs for her classes so the computer has been freshly reformatted. I installed a graphics update that seemed to take care of the problem for a short period but then started up again. All of the power saving settings I shut off because we usually keep it plugged in and that's what I thought it was doing at first but, no dice.
Thanks so much for taking the time to help by the way.
-Adam

ScottW - Mar 5, 2008 - 8:30 am

When you bump it, does it always go off. Can you duplicate the bumping to get it to turn off? If there is a lose connection (even on a board) it could cause the display to go out, and not come back on, yet rebooting would fix it because the connection "reconnected" after the bump was complete, but there was not call to "turn the display on" again, but rebooting does this.

If it goes out, try and close the display and put the computer to sleep. Then lift the display back up and see if it comes on again.

This has to be a hardware issue, it would not be a driver issue or if your settings in Energy preferences are set as you say, then there is only one conclusion, hardware.

If it sits to long and shuts off as well, it could be a heat issue, something expands, and causes the display to shut off, duplicating the bump method. Probably less likely a cable issue and more of a circuit card issue would be my guess.

Scott

Adam Ohrt - Mar 7, 2008 - 9:08 am

I'll get my hand dirty and tear it open to see if it is a cable. I'm also wondering if there isn't enough ram because it seems to become more unstable when it is running large programs. Thanks for the reply.
-Adam

Adam Ohrt - Mar 10, 2008 - 8:42 am

Nope that was not the problem. I checked all the cables and they were fine. When I put it back together it didn't recognize the hard drive anymore.

TechSupport - Mar 13, 2008 - 8:50 am

We apologize for not being able to resolve the issue you asked of us. It is the absolute worst case scenario for us to do this. In our review of why this happens, it generally is related to either the particular issue being addressed or frequently, incomplete or incorrect information provided. We hope by moving your request to the public forums that you will be able to get a solution without leaving you empty handed.

Your ticket has been closed with our support team. Your request has just been posted to Mac OS X System & Mac Software and is available for your viewing at:

http://macosx.com/forums/showthread.php?t=299115

Again, thank you for using Macosx.com. We hope you will consider using us again in the future.