Mac Black screen of death!!!

Discussion in 'Mac Basics and Help' started by Ferrence, Sep 3, 2005.

  1. Ferrence macrumors member

    Joined:
    Sep 3, 2005
    #1
    I was writing to inquire about the Mac Black screen of death that makes me shut down my computer every other day (sorry if this topic has been addressed already). I am running Tiger 10.4.2 on a 15” Powerbook 1.5 Ghz PowerPC G4.

    The error prompt reads something like, “You need to restart your computer. Hold down the Restart button for several second…”

    Now, luckily I’m a constant “saver” and hardly lose any info. But the process of shutting down my computer is growing old. Any thoughts on why this is happening?

    Thanks,
    Ferrence
     

    Attached Files:

  2. mad jew Moderator emeritus

    mad jew

    Joined:
    Apr 3, 2004
    Location:
    Adelaide, Australia
    #2
    That's not right. You shouldn't be getting crashes very often, I've only ever had about ten all up on two machines over a combined four years of experience. What are you doing when it crashes and also how did you get to Tiger? Did you do an "Upgrade" (standard), an "Archive and install", or a "Format and install", or did it come preinstalled?

    At this point, it's looking like you may want to do the following, assuming it's not a single app that's causing the problems.

    1. Repair permissions form the Disk Utility in the Utilities folder in you Applications folder.
    2. Reset your PMU.
    3. Maybe reinstall the OS, but wait, because hopefully we'll fix it before that becomes a proper option.
     
  3. mkrishnan Moderator emeritus

    mkrishnan

    Joined:
    Jan 9, 2004
    Location:
    Grand Rapids, MI, USA
    #3
    Two things:

    1) The phenomenon is called a "kernel panic" in OS X lingo -- so if you google that term, you will find more information than if you google "black screen of death."

    2) You should a file called panic.log -- find it using Spotlight. The entries are written in chronological order, so find the most recent couple of them and copy and paste them into a reply, so we can help you figure out why it's happening.

    If you're getting them every day, there are three major possibilities
    A) Bad hardware
    B) Some serious incompatibility with a driver or kernel extension or haxie sort of thing
    C) Corrupted system files or corrupted HD format.

    Come back with the panic log and we will try to help you. Tiger had panic issues for a number of people with 10.4.0 and 10.4.1, but 10.4.2 seems stable for most (but not all) people. I rebooted yesterday to install some updates, but before that mine had been up without reboot for >16 days, and that is not atypical.

    EDIT: My boy MJ's suggestion of corrupted PMU firmware is also a very real fourth possibility. Definitely good to try.
     
  4. macdon401 macrumors 6502

    macdon401

    Joined:
    Jul 9, 2005
    #4
    Kernel?

    Hi, mad jew
    when I got that horrid looking window on my G4 iMac I called Apple and she took me through all kinds of Terminal prompts and other solutions...turns out I had a "kernel" stall or something! I had to bring it in, while there i saw the new G5's.... well you know the story...here I am at my new G5!
    R
     
  5. 840quadra Moderator

    840quadra

    Staff Member

    Joined:
    Feb 1, 2005
    Location:
    Twin Cities Minnesota
    #5
    if possible, check your memory,

    Pull it out, and re-seat it.. If you have spare or added memory, take out extra memory, and run your computer with reduced memory. If it still acts up, take the memory you removed, and replace the currently installed memory with that, and repeat the tests. If it still acts up, you have at least ruled out Memory as the root cause.

    In my experience, Memory is a prime cause of Kernel Panics in both the Linux world, and Mac OS X, there are many other causes, but this seems to be the most common.

    840
     
  6. Ferrence thread starter macrumors member

    Joined:
    Sep 3, 2005
    #6
    RE: Mac Black screen of death!!!

    *********
    This is what I've got on the "panic.log" just for today. I have no idea how to translate this. Thanks for all the help.

    Ferrence




    Sat Sep 3 11:47:14 2005


    Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000000000000 PC=0x000000000005CD8C
    Latest crash info for cpu 0:
    Exception state (sv=0x383D8780)
    PC=0x0005CD8C; MSR=0x00009030; DAR=0x00000000; DSISR=0x42000000; LR=0x00075D08; R1=0x21FFB5D0; XCP=0x0000000C (0x300 - Data access)
    Backtrace:
    0x00075C48 0x0007572C 0x0006B270 0x0006B544 0x00038064 0x0026297C
    0x0026F104 0x00025250 0x000ABF38 0x00026CF4 0x000A8954 0x000A8714 0x000ABB00
    backtrace terminated - frame not mapped or invalid: 0xBFFFD5A0

    Proceeding back via exception chain:
    Exception state (sv=0x383D8780)
    previously dumped as "Latest" state. skipping...
    Exception state (sv=0x37A27500)
    PC=0x8FE00068; MSR=0x0000D030; DAR=0xA1B1C243; DSISR=0x40000000; LR=0x8FE00068; R1=0xBFFFF410; XCP=0x00000003 (Unknown)

    Kernel version:
    Darwin Kernel Version 8.2.0: Fri Jun 24 17:46:54 PDT 2005; root:xnu-792.2.4.obj~3/RELEASE_PPC
    panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
    Latest stack backtrace for cpu 0:
    Backtrace:
    0x00095544 0x00095A5C 0x0002683C 0x000A819C 0x000ABB00
    Proceeding back via exception chain:
    Exception state (sv=0x383D8780)
    PC=0x0005CD8C; MSR=0x00009030; DAR=0x00000000; DSISR=0x42000000; LR=0x00075D08; R1=0x21FFB5D0; XCP=0x0000000C (0x300 - Data access)
    Backtrace:
    0x00075C48 0x0007572C 0x0006B270 0x0006B544 0x00038064 0x0026297C
    0x0026F104 0x00025250 0x000ABF38 0x00026CF4 0x000A8954 0x000A8714 0x000ABB00
    backtrace terminated - frame not mapped or invalid: 0xBFFFD5A0

    Exception state (sv=0x37A27500)
    PC=0x8FE00068; MSR=0x0000D030; DAR=0xA1B1C243; DSISR=0x40000000; LR=0x8FE00068; R1=0xBFFFF410; XCP=0x00000003 (Unknown)

    Kernel version:
    Darwin Kernel Version 8.2.0: Fri Jun 24 17:46:54 PDT 2005; root:xnu-792.2.4.obj~3/RELEASE_PPC
    *********

    Sat Sep 3 12:05:23 2005


    Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x00000000A5A5A5A5 PC=0x000000000003FCF0
    Latest crash info for cpu 0:
    Exception state (sv=0x3829EC80)
    PC=0x0003FCF0; MSR=0x00009030; DAR=0xA5A5A5A5; DSISR=0x40000000; LR=0x0003FCD8; R1=0x2202BBE0; XCP=0x0000000C (0x300 - Data access)
    Backtrace:
    0x02E70098 0x000752BC 0x00077238 0x00070EA4 0x00062438 0x000A85F4
    0x000ABB00
    Proceeding back via exception chain:
    Exception state (sv=0x3829EC80)
    previously dumped as "Latest" state. skipping...
    Exception state (sv=0x3E720000)
    PC=0x8FE15FB4; MSR=0x0200D030; DAR=0xA09A8000; DSISR=0x0A000000; LR=0x8FE15F44; R1=0xBFFFF760; XCP=0x0000000C (0x300 - Data access)

    Kernel version:
    Darwin Kernel Version 8.2.0: Fri Jun 24 17:46:54 PDT 2005; root:xnu-792.2.4.obj~3/RELEASE_PPC
    panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
    Latest stack backtrace for cpu 0:
    Backtrace:
    0x00095544 0x00095A5C 0x0002683C 0x000A819C 0x000ABB00
    Proceeding back via exception chain:
    Exception state (sv=0x3829EC80)
    PC=0x0003FCF0; MSR=0x00009030; DAR=0xA5A5A5A5; DSISR=0x40000000; LR=0x0003FCD8; R1=0x2202BBE0; XCP=0x0000000C (0x300 - Data access)
    Backtrace:
    0x02E70098 0x000752BC 0x00077238 0x00070EA4 0x00062438 0x000A85F4
    0x000ABB00
    Exception state (sv=0x3E720000)
    PC=0x8FE15FB4; MSR=0x0200D030; DAR=0xA09A8000; DSISR=0x0A000000; LR=0x8FE15F44; R1=0xBFFFF760; XCP=0x0000000C (0x300 - Data access)

    Kernel version:
    Darwin Kernel Version 8.2.0: Fri Jun 24 17:46:54 PDT 2005; root:xnu-792.2.4.obj~3/RELEASE_PPC

    *********

    Sat Sep 3 13:40:08 2005


    Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x00000000A5A5A5A5 PC=0x000000000003FCF0
    Latest crash info for cpu 0:
    Exception state (sv=0x3829EC80)
    PC=0x0003FCF0; MSR=0x00009030; DAR=0xA5A5A5A5; DSISR=0x40000000; LR=0x0003FCD8; R1=0x2202BBE0; XCP=0x0000000C (0x300 - Data access)
    Backtrace:
    0x02E70098 0x000752BC 0x00077238 0x00070EA4 0x00062438 0x000A85F4
    0x000ABB00
    Proceeding back via exception chain:
    Exception state (sv=0x3829EC80)
    previously dumped as "Latest" state. skipping...
    Exception state (sv=0x3E720000)
    PC=0x8FE15FB4; MSR=0x0200D030; DAR=0xA09A8000; DSISR=0x0A000000; LR=0x8FE15F44; R1=0xBFFFF760; XCP=0x0000000C (0x300 - Data access)

    Kernel version:
    Darwin Kernel Version 8.2.0: Fri Jun 24 17:46:54 PDT 2005; root:xnu-792.2.4.obj~3/RELEASE_PPC
    panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
    Latest stack backtrace for cpu 0:
    Backtrace:
    0x00095544 0x00095A5C 0x0002683C 0x000A819C 0x000ABB00
    Proceeding back via exception chain:
    Exception state (sv=0x3829EC80)
    PC=0x0003FCF0; MSR=0x00009030; DAR=0xA5A5A5A5; DSISR=0x40000000; LR=0x0003FCD8; R1=0x2202BBE0; XCP=0x0000000C (0x300 - Data access)
    Backtrace:
    0x02E70098 0x000752BC 0x00077238 0x00070EA4 0x00062438 0x000A85F4
    0x000ABB00
    Exception state (sv=0x3E720000)
    PC=0x8FE15FB4; MSR=0x0200D030; DAR=0xA09A8000; DSISR=0x0A000000; LR=0x8FE15F44; R1=0xBFFFF760; XCP=0x0000000C (0x300 - Data access)

    Kernel version:
    Darwin Kernel Version 8.2.0: Fri Jun 24 17:46:54 PDT 2005; root:xnu-792.2.4.obj~3/RELEASE_PPC

    *********

    Sat Sep 3 13:45:17 2005


    Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x00000000A5A5A5A5 PC=0x000000000003FCF0
    Latest crash info for cpu 0:
    Exception state (sv=0x3829EC80)
    PC=0x0003FCF0; MSR=0x00009030; DAR=0xA5A5A5A5; DSISR=0x40000000; LR=0x0003FCD8; R1=0x2202BBE0; XCP=0x0000000C (0x300 - Data access)
    Backtrace:
    0x02E70098 0x000752BC 0x00077238 0x00070EA4 0x00062438 0x000A85F4
    0x000ABB00
    Proceeding back via exception chain:
    Exception state (sv=0x3829EC80)
    previously dumped as "Latest" state. skipping...
    Exception state (sv=0x3E720000)
    PC=0x8FE15FB4; MSR=0x0200D030; DAR=0xA09A8000; DSISR=0x0A000000; LR=0x8FE15F44; R1=0xBFFFF760; XCP=0x0000000C (0x300 - Data access)

    Kernel version:
    Darwin Kernel Version 8.2.0: Fri Jun 24 17:46:54 PDT 2005; root:xnu-792.2.4.obj~3/RELEASE_PPC
    panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
    Latest stack backtrace for cpu 0:
    Backtrace:
    0x00095544 0x00095A5C 0x0002683C 0x000A819C 0x000ABB00
    Proceeding back via exception chain:
    Exception state (sv=0x3829EC80)
    PC=0x0003FCF0; MSR=0x00009030; DAR=0xA5A5A5A5; DSISR=0x40000000; LR=0x0003FCD8; R1=0x2202BBE0; XCP=0x0000000C (0x300 - Data access)
    Backtrace:
    0x02E70098 0x000752BC 0x00077238 0x00070EA4 0x00062438 0x000A85F4
    0x000ABB00
    Exception state (sv=0x3E720000)
    PC=0x8FE15FB4; MSR=0x0200D030; DAR=0xA09A8000; DSISR=0x0A000000; LR=0x8FE15F44; R1=0xBFFFF760; XCP=0x0000000C (0x300 - Data access)

    Kernel version:
    Darwin Kernel Version 8.2.0: Fri Jun 24 17:46:54 PDT 2005; root:xnu-792.2.4.obj~3/RELEASE_PPC

    *********

    Sat Sep 3 17:33:24 2005


    Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x00000000031CFF80 PC=0x00000000000661FC
    Latest crash info for cpu 0:
    Exception state (sv=0x46CE5780)
    PC=0x000661FC; MSR=0x00009030; DAR=0x031CFF80; DSISR=0x40000000; LR=0x000661EC; R1=0x220AB5C0; XCP=0x0000000C (0x300 - Data access)
    Backtrace:
    0x031AF330 0x0006A710 0x0006B054 0x0006B544 0x00038064 0x0026297C
    0x0026F104 0x00025250 0x000ABF38 0x00026CF4 0x000A8954 0x000A8714 0x000ABB00
    Proceeding back via exception chain:
    Exception state (sv=0x46CE5780)
    previously dumped as "Latest" state. skipping...
    Exception state (sv=0x46386000)
    PC=0x8FE15FAC; MSR=0x0000D030; DAR=0xA190E000; DSISR=0x40000000; LR=0x8FE15F44; R1=0xBFFFF760; XCP=0x00000003 (Unknown)

    Kernel version:
    Darwin Kernel Version 8.2.0: Fri Jun 24 17:46:54 PDT 2005; root:xnu-792.2.4.obj~3/RELEASE_PPC
    panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
    Latest stack backtrace for cpu 0:
    Backtrace:
    0x00095544 0x00095A5C 0x0002683C 0x000A819C 0x000ABB00
    Proceeding back via exception chain:
    Exception state (sv=0x46CE5780)
    PC=0x000661FC; MSR=0x00009030; DAR=0x031CFF80; DSISR=0x40000000; LR=0x000661EC; R1=0x220AB5C0; XCP=0x0000000C (0x300 - Data access)
    Backtrace:
    0x031AF330 0x0006A710 0x0006B054 0x0006B544 0x00038064 0x0026297C
    0x0026F104 0x00025250 0x000ABF38 0x00026CF4 0x000A8954 0x000A8714 0x000ABB00
    Exception state (sv=0x46386000)
    PC=0x8FE15FAC; MSR=0x0000D030; DAR=0xA190E000; DSISR=0x40000000; LR=0x8FE15F44; R1=0xBFFFF760; XCP=0x00000003 (Unknown)

    Kernel version:
    Darwin Kernel Version 8.2.0: Fri Jun 24 17:46:54 PDT 2005; root:xnu-792.2.4.obj~3/RELEASE_PPC
     
  7. Lacero macrumors 604

    Lacero

    Joined:
    Jan 20, 2005
    #7
    Bad RAM, bad USB devices and poorly written software are the usual culprits. Try doing a complete clean re-install of your OS and essential programs. If it re-occurs, then it's a definite hardware problem.
     
  8. Ferrence thread starter macrumors member

    Joined:
    Sep 3, 2005
    #8
    Oh yeah...

    I did add memory, but probably a day or two after I got the computer. So, it's hard to say whether or not that's the problem.

    I just ran "Disk Utility" and "repaired permissions." Should I wait and see if that works before moving on to the next steps?
     
  9. mad jew Moderator emeritus

    mad jew

    Joined:
    Apr 3, 2004
    Location:
    Adelaide, Australia
    #9

    I'm willing to bet a small wager that the new memory is your problem.



    Give it a little while to see if it does work. It's very unlikely, but it's still slightly possible that repairing permissions solved your problem. My next move would be to remove the memory you added and see how it foes from there. I'll bet it works well. :)
     
  10. Ferrence thread starter macrumors member

    Joined:
    Sep 3, 2005
  11. nate macrumors member

    Joined:
    Jun 28, 2003
    Location:
    Calgary, Alberta, Canada
    #11
    I once got that with my Powerbook -- it turned out that it was my airport card, which I installed myself. I didn't push the connector all the way in, which caused a kernel panic. Unplugging it and then re-plugging it fixed the problem.

    RAM that isn't in all the way can also cause the same problem, but a few people have already mentioned that one.

    good luck,


    --nate
     
  12. mad jew Moderator emeritus

    mad jew

    Joined:
    Apr 3, 2004
    Location:
    Adelaide, Australia
  13. mkrishnan Moderator emeritus

    mkrishnan

    Joined:
    Jan 9, 2004
    Location:
    Grand Rapids, MI, USA
    #13
    Ditto. What's significant is that nothing but memory addresses show up in the backtrace -- no kernel extensions or modules or anything. Usually, if you have USB or Bluetooth issues, a relevant module will be flagged, as will a program if it caused the panic.

    I would say try the Apple hardware test disc or take the RAM out and see what happens...

    FWIW, the attached kernel panic is a Bluetooth issue with the way my closed iBook and the wake-on-bluetooth-device setting interact:

    Notice the part in bold -- this is the sort of thing that none of your KP data have in them....
     
  14. hob macrumors 68020

    hob

    Joined:
    Oct 4, 2003
    Location:
    London, UK
    #14
    Stop making up words :p
     
  15. Les Kern macrumors 68040

    Les Kern

    Joined:
    Apr 26, 2002
    Location:
    Alabama
  16. Abstract macrumors Penryn

    Abstract

    Joined:
    Dec 27, 2002
    Location:
    Location Location Location
    #16
    RAM, or iScroll2 software which gives you two-finger scroll capabilities if you didn't have have one of the newer systems that included it free.
     
  17. faintember macrumors 65816

    faintember

    Joined:
    Jun 6, 2005
    Location:
    the ruins of the Cherokee nation
    #17
    If you want to test the RAM use Rember. When you start Rember to check your RAM, click on the LOG tab, and that should show you in you have any RAM failures. I recently had 4 sticks of RAM that were bad, and Rember caught them all, reporting failures in the RAM quite quickly.

    Good luck!
     
  18. Ferrence thread starter macrumors member

    Joined:
    Sep 3, 2005
    #18
    Latest...

    Okay. So, I took out the RAM and re-installed it (I had an original 512 and added another Gig from MacDirect). I was never really sure if I installed it correctly, because sometimes it wouldn't show up in my "About this computer" (or would show up as 1 Gig instead of 1.5 Gigs). But after hearing a members similar situation when he installed his Air Port card incorrectly, I figured I'd give it a try.

    Now, should I have just taken it out all together? And just run the 512? And if that was the problem, does that mean I can't add RAM to this machine?

    Thanks for all your help. Tell me where to send the payments...

    Ferrence
     
  19. mkrishnan Moderator emeritus

    mkrishnan

    Joined:
    Jan 9, 2004
    Location:
    Grand Rapids, MI, USA
    #19
    No, it definitely shouldn't mean that. What I would do is:

    - Run for a while as you did, with the RAM put back in
    - If you get more panics, then remove the RAM and run that way for a while
    - If this resolves it, you most likely means that the ram module itself is bad, not the computer, although people have reported failures with the lower ram slot specifically in powerbook 15" models (see link). So that's also a possibility, although it should be a warranted one.
     
  20. Ferrence thread starter macrumors member

    Joined:
    Sep 3, 2005
    #20
    UPDATE!!!

    Okay, I got the "Kernal Panic" screen again and shut down. I took out the memory in the lower slot and re-started the computer. No chime, just a gray screen with the Apple logo... forever. No boot.

    So, I opened up the memory door again and put the memory back into the lower slot (filling both of them again), and still no chime, just a gray screen with the Apple logo... forever. No boot.

    Is there anyway to boot, so I can pull files off that I need to work on for work tomorrow. Or, am I f*cked?!

    Please help.
     
  21. hob macrumors 68020

    hob

    Joined:
    Oct 4, 2003
    Location:
    London, UK
    #21
    Try booting into Target Mode - hold down t as you start up, this will allow you to use your computer as a firewire hard disk - just plug it into another computer.

    As far as I know any mac no matter how messed up should still boot into target mode.
     
  22. javabear90 macrumors 6502a

    javabear90

    Joined:
    Dec 7, 2003
    Location:
    Houston, TX
    #22
    your hard-drive might have been fried for some reason. That is exactly what happened to me with the no boot thing.
    hope you get it working.
    -ted
     
  23. faintember macrumors 65816

    faintember

    Joined:
    Jun 6, 2005
    Location:
    the ruins of the Cherokee nation
    #23
    Try booting with the original CD that came with your Mac. Put the CD in and hold down "C" on the keyboard as you are starting up the computer. When (if) it boots, open Disk Utility and check your HD and it's status, etc.

    Try just using your original RAM.
     
  24. verozov macrumors regular

    verozov

    Joined:
    Jan 8, 2005
    Location:
    Columbia, SC
    #24
    used to happen to me a lot... turns out it was my airport extreme card... it must've been half-in or something because once i took it out and put it back in it never (knock knock) crashed again
     
  25. yenko macrumors 6502a

    Joined:
    Aug 29, 2005
    Location:
    SouthWest-USA
    #25
    Revert

    Try just using your original RAM.[/QUOTE]


    What he said.

    Revert to original :cool:
     

Share This Page