Kernel Panic, should I be worried?

Discussion in 'Mac Basics and Help' started by ghall, Sep 1, 2006.

  1. ghall macrumors 68040

    ghall

    Joined:
    Jun 27, 2006
    Location:
    Rhode Island
    #1
    I opened up Photo Booth a few minutes ago on my MacBook Pro, and the screen went gray, and the message saying to hold down the power button came up.

    I recently installed a 1 GB RAM chip and it's been working fine, but could that be the issue?
     
  2. mad jew Moderator emeritus

    mad jew

    Joined:
    Apr 3, 2004
    Location:
    Adelaide, Australia
    #2
    That could very well be the issue and it's the first thing I'd look at. Generally speaking I let the first kernel panic go but in this case, maybe check Console in the Utilities folder too see what it says. :)
     
  3. ghall thread starter macrumors 68040

    ghall

    Joined:
    Jun 27, 2006
    Location:
    Rhode Island
    #3
    Checked it up, but this is all gibberish to me. Could I get an English translation?

    Fri Sep 1 21:07:12 2006
    panic(cpu 1 caller 0x0019CADF): Unresolved kernel trap (CPU 1, Type 14=page fault), registers:
    CR0: 0x80010033, CR2: 0xe000038b, CR3: 0x00d5f000, CR4: 0x000006a0
    EAX: 0xe00002e7, EBX: 0x0306c920, ECX: 0x0306c920, EDX: 0x04925000
    ESP: 0xe000038b, EBP: 0x1c673d08, ESI: 0x0332138c, EDI: 0x0375f800
    EFL: 0x00010213, EIP: 0x005a44de, CS: 0x00000008, DS: 0x00000010

    Backtrace, Format - Frame : Return Address (4 potential args on stack)
    0x1c673bc0 : 0x128b5e (0x3bc46c 0x1c673be4 0x131bbc 0x0)
    0x1c673c00 : 0x19cadf (0x3c18e4 0x1 0xe 0x3c169c)
    0x1c673cb0 : 0x197c7d (0x1c673cc4 0x1c673d08 0x5a44de 0x48)
    0x1c673cbc : 0x5a44de (0x48 0x4920010 0x3750010 0x10)
    0x1c673d08 : 0x5a6604 (0x2eb5000 0x306c920 0x1c673d38 0x3ae636)
    0x1c673d38 : 0x3a35d5 (0x375f800 0x306c920 0x332138c 0x3321390)
    0x1c673d88 : 0x18a315 (0x375f800 0x6 0x48280c4 0x1)
    0x1c673dd8 : 0x12b389 (0x482809c 0x3321364 0x0 0x0)
    0x1c673e18 : 0x124902 (0x4828000 0x0 0x30 0x1c673efc)
    0x1c673f28 : 0x193034 (0x1c673f54 0x0 0x0 0x0)
    0x1c673fd8 : 0x19814b (0x3373ca8 0x3373ca8 0x306c920 0xe000038b) No mapping exists for frame pointer
    Backtrace terminated-invalid frame pointer 0xb0220678
    Kernel loadable modules in backtrace (with dependencies):
    com.apple.ATIRadeonX1000(4.3.2)@0x59f000
    dependency: com.apple.iokit.IOPCIFamily(2.0)@0x566000
    dependency: com.apple.iokit.IOGraphicsFamily(1.4.3)@0x575000
    dependency: com.apple.iokit.IONDRVSupport(1.4.3)@0x590000

    Kernel version:
    Darwin Kernel Version 8.7.1: Wed Jun 7 16:19:56 PDT 2006; root:xnu-792.9.72.obj~2/RELEASE_I386


    *********
     
  4. disconap macrumors 68000

    disconap

    Joined:
    Oct 29, 2005
    Location:
    Portland, OR
  5. mad jew Moderator emeritus

    mad jew

    Joined:
    Apr 3, 2004
    Location:
    Adelaide, Australia
    #5
    Hmm... I'm no good at these things. There's mention of your GPU but I don't think that's the problem. Run the memory test app that the wise disconap mentions but remember that these tests aren't 100% accurate and can sometimes not find fault with bad RAM. I'd maybe leave it for a while and if it happens again soon, then take out the new RAM. :)
     
  6. ghall thread starter macrumors 68040

    ghall

    Joined:
    Jun 27, 2006
    Location:
    Rhode Island
    #6
    I ran the test and everything checked out fine. Huh, I wonder what happened. Could have just been a freak thing, but I will keep this in mind incase it happens again.
     
  7. disconap macrumors 68000

    disconap

    Joined:
    Oct 29, 2005
    Location:
    Portland, OR
    #7
    Run a permissions repair and, if needed, boot from the OS disc and run disk repair. But I really wouldn't worry about it if it only happens once, as the ever benevolent mad jew has mentioned; these things sometimes just happen, and it's not worth worrying about if it doesn't happen again...
     

Share This Page