iMac Kernel Panic

Discussion in 'iMac' started by AutumnSkyline, Aug 3, 2007.

  1. AutumnSkyline macrumors regular


    Oct 5, 2006
    So my iMac had a Kernel Panic, I would like to know the cause of it, and anyway to prevent these from happening in the future. I was restarting my iMac anyway, but it unsettles me that I had a kernel panic.

    Please help, here is the report:

    panic(cpu 0 caller 0x001A4A55): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
    CR0: 0x8001003b, CR2: 0x00000037, CR3: 0x00e69000, CR4: 0x000006e0
    EAX: 0x10004004, EBX: 0x00000017, ECX: 0x00000000, EDX: 0x004bb51c
    CR2: 0x00000037, EBP: 0x00000000, ESI: 0x0000001f, EDI: 0x0000001f
    EFL: 0x00010206, EIP: 0x00000037, CS: 0x00000008, DS: 0x00000010

    Backtrace, Format - Frame : Return Address (4 potential args on stack)
    0x1c9dba58 : 0x128d08 (0x3cc0a4 0x1c9dba7c 0x131de5 0x0)
    0x1c9dba98 : 0x1a4a55 (0x3d24b8 0x0 0xe 0x3d1cdc)
    0x1c9dbba8 : 0x19aeb4 (0x1c9dbbc0 0x48 0x10 0x4c) Backtrace terminated-invalid frame pointer 0x0

    Kernel version:
    Darwin Kernel Version 8.10.1: Wed May 23 16:33:00 PDT 2007; root:xnu-792.22.5~1/RELEASE_I386

    Model: iMac5,1, BootROM IM51.0090.B03, 2 processors, Intel Core 2 Duo, 2 GHz, 1.5 GB
    Graphics: ATI Radeon X1600, ATY,RadeonX1600, PCIe, 128 MB
    Memory Module: BANK 0/DIMM0, 1 GB, DDR2 SDRAM, 667 MHz
    Memory Module: BANK 1/DIMM1, 512 MB, DDR2 SDRAM, 667 MHz
    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x87), Broadcom BCM43xx 1.0 (
    Bluetooth: Version 1.9.0f8, 2 service, 0 devices, 1 incoming serial ports
    Network Service: Built-in Ethernet, Ethernet, en0
    Serial ATA Device: ST3160812AS Q, 149.05 GB
    Parallel ATA Device: PIONEER DVD-RW DVR-K06
    USB Device: Built-in iSight, Micron, Up to 480 Mb/sec, 500 mA
    USB Device: Hub in Apple Pro Keyboard, Mitsumi Electric, Up to 12 Mb/sec, 500 mA
    USB Device: Apple Optical USB Mouse, Primax Electronics, Up to 1.5 Mb/sec, 100 mA
    USB Device: Apple Pro Keyboard, Mitsumi Electric, Up to 12 Mb/sec, 250 mA
    USB Device: psc 1200 series, Hewlett-Packard, Up to 12 Mb/sec, 500 mA
    USB Device: Bluetooth USB Host Controller, Apple, Inc., Up to 12 Mb/sec, 500 mA
    USB Device: IR Receiver, Apple Computer, Inc., Up to 12 Mb/sec, 500 mA
    FireWire Device: LaCie Hard Drive FireWire+, LaCie Group SA, Up to 400 Mb/sec
  2. yellow Moderator emeritus


    Oct 21, 2003
    Portland, OR
    There's nothing here that is a real indicator of what caused it. Looks like it's unlikely that it was caused by software.

    Unless this is a repeatable/consistant issue, I wouldn't worry about it. Transient KPs are not worth the headache.
  3. neven macrumors 6502a

    Oct 10, 2006
    Portland, OR
    Sorry to be harsh, but do you really expect that any of us here will be able to deduce anything from that log, even if we wanted to invest the time to go through it?
  4. yellow Moderator emeritus


    Oct 21, 2003
    Portland, OR
    I can, and have. It's not that difficult.

    For example, it's pretty clear where this issue is based:

  5. AutumnSkyline thread starter macrumors regular


    Oct 5, 2006
    okay, thanks yellow, I was thinking it was a software issue, I was installing software, and I figured I would reboot. I installed it, rebooted, and before it shut down, the kernel panicked. So, thank you for your help, needless to say I trashed the software.

    Neven, I have seen people post crash logs before, and people have figured out the cause of the issue, so I figured I would give it a shot.
  6. yellow Moderator emeritus


    Oct 21, 2003
    Portland, OR
    Well, there's no assurances that it ISN'T software related.. but typically when it is, you'll see some sort of reference in the KP log that points to something other than random hexidecimal memory space. Of course, if what you installed had installed a kernel extension, all bets are off. :)

    So, like I said.. it's all up to you in pursing the issue dependant upon how often it happens, or if it's reproducable.
  7. nigrunze macrumors regular

    Jul 28, 2007
    Montreal, Quebec, Canada
    So as long as we're talking about kernel panics, just over a month ago I got a blue screen of death on Windows Vista. I was just shutting down, it was taking a ridiculously long time, and then the screen turns completely blue. Looks sort of like the XP one(how can it look any different, it's just blue) but there was no text whatsoever. When I restarted my computer and got back to my desktop, it showed an error report titled "Blue Screen". Out of the 8 months that I've had Vista installed, that was the only time I've seen the BSOD.

    Anyway, as long as your computer doesn't crash or kernel panic often, I wouldn't worry about it. Sometimes this kind of stuff can happen.

    But if you do get a kernel panic often, the first place to check would probably be the RAM. Try taking out one at a time and leave the other inside the computer. That is if you don't have a Mac Mini.
  8. rookiemac macrumors newbie

    Aug 2, 2007
    what if we installed some software where everytime u boot you get the kernel panic, how woudl u resolve this problem? a total reinstall of tiger?
  9. DoFoT9 macrumors P6


    Jun 11, 2007
    ^^ that would be a software related issue. most likely a full harddrive wipe and reinstall would fix it.
  10. yellow Moderator emeritus


    Oct 21, 2003
    Portland, OR
    No. It would most likely be related to a kernel extension that the software installed.
    Just boot into Safe Mode and remove the errant kext.
    Problem solved.
  11. rogersmj macrumors 68020


    Sep 10, 2006
    Indianapolis, IN
    For the record, I experienced two kernel panics within a day of getting my new Aluminum iMac last week. I had a funny feeling it was the Logitech Control Center software for my VX Revolution (which was the only thing different that I had installed compared to my old iMac)...and sure enough, since I removed it and replaced it with USB Overdrive, no more kernel panics. *Looks for wood to knock on...*

    I love Logitech's hardware, but MAN do they SUCK at writing software.

Share This Page