Kernel Panic Assistance

Discussion in 'macOS' started by madjuly, Mar 29, 2010.

  1. madjuly macrumors newbie

    Joined:
    Mar 5, 2010
    #1
    I have an iMac G5 isight that is constantly having kernel panics. The errors seened to occur when I bought a a new Airport Extreme base station but it may have happened before that. The AE is brand new where the iMac is a G5. I have started the computer up with out Airport on and still had the kernel panic so I do not believe it is the AE. I have wiped the drive, zeroed out the HD, removed the extra RAM (only soldered RAM installed right now), reset the PRAM, reset the SMC, removed all peripherals and am currently looping Apple hardware test right now (currently showing no issues after 3 hours). It seems to happen when I am in the middle of installing things but also at other random times. Please see the panic log below. I have a long log but this is the most recent one. The computer only has Apple products on it that were installed from the system disk. No third party on there. Thanks

    Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x00000000070BF81E PC=0x000000000003FFD4
    Latest crash info for cpu 0:
    Exception state (sv=0x254DE000)
    PC=0x0003FFD4; MSR=0x00009030; DAR=0x070BF81E; DSISR=0x40000000; LR=0x0003FFBC; R1=0x0CCDB5F0; XCP=0x0000000C (0x300 - Data access)
    Backtrace:
    0x003D0000 0x0002BDCC 0x00304E60 0x00304FDC 0x00309694 0x00307EC8
    0x003098B0 0x002ED6E4 0x0008D960 0x00029234 0x000233F8 0x000ABEAC 0x01917B60
    backtrace terminated - frame not mapped or invalid: 0xBFFFF450

    Proceeding back via exception chain:
    Exception state (sv=0x254DE000)
    previously dumped as "Latest" state. skipping...
    Exception state (sv=0x254DD000)
    PC=0x9000B348; MSR=0x0200D030; DAR=0x01368000; DSISR=0x42000000; LR=0x9000B29C; R1=0xBFFFF450; XCP=0x00000030 (0xC00 - System call)

    Kernel version:
    Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC
    panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
    Latest stack backtrace for cpu 0:
    Backtrace:
    0x000954F8 0x00095A10 0x00026898 0x000A8204 0x000ABB80
    Proceeding back via exception chain:
    Exception state (sv=0x254DE000)
    PC=0x0003FFD4; MSR=0x00009030; DAR=0x070BF81E; DSISR=0x40000000; LR=0x0003FFBC; R1=0x0CCDB5F0; XCP=0x0000000C (0x300 - Data access)
    Backtrace:
    0x003D0000 0x0002BDCC 0x00304E60 0x00304FDC 0x00309694 0x00307EC8
    0x003098B0 0x002ED6E4 0x0008D960 0x00029234 0x000233F8 0x000ABEAC 0x01917B60
    backtrace terminated - frame not mapped or invalid: 0xBFFFF450

    Exception state (sv=0x254DD000)
    PC=0x9000B348; MSR=0x0200D030; DAR=0x01368000; DSISR=0x42000000; LR=0x9000B29C; R1=0xBFFFF450; XCP=0x00000030 (0xC00 - System call)

    Kernel version:
    Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC
    *********
     
  2. wrldwzrd89 macrumors G5

    wrldwzrd89

    Joined:
    Jun 6, 2003
    Location:
    Solon, OH
    #2
    You've done a good job of eliminating causes. RAM and software definitely are ruled out, as is the disk. That leaves the PMU (power management unit) as a possible cause, or some other hardware component. Fortunately, if it's the PMU, this is very easy to correct. Take it into an Apple Retail Store or other authorized Apple repair shop, and tell them your iMac needs its PMU reset. The Apple Retail Stores will do this for free - I don't know about other authorized repair shops.
     
  3. calderone macrumors 68040

    calderone

    Joined:
    Aug 28, 2009
    Location:
    Seattle
    #3
    I wouldn't say the disk is ruled out. A zero out doesn't fix any physical problems there may be.

    The AHT may not find any problems, but I personally do not trust it.

    Your best bet is to take it in for a diagnostic.
     
  4. madjuly thread starter macrumors newbie

    Joined:
    Mar 5, 2010
    #4
    Today I am trying one more time to install the OS. I noticed that when I run the computer off the CD I don't get any panics. So at this point I am pretty sure it may be the hard drive. It has been going all morning and nothing has happened. Thanks for the replies
     

Share This Page