Kernel Panic Problems

Discussion in 'Mac Basics and Help' started by markjewiss, Mar 9, 2007.

  1. markjewiss macrumors member

    Feb 8, 2007
    Dunmow, UK
    Hi there,

    First of all thanks to people who have posted here about kernel panics in the past - I've just spent an hour reading those posts on my Mini to get this MBP up and running again! Ok, here's what happend...

    Have a two week old 2.33 MBP with 3GB RAM - it was busy running Firefox, a few Finder windows and not much else. Shut it down to sleep, and about 60 seconds later I opened it again. No light on the front, no glowing Apple logo. Shut the lid, got a glowing light on the front - this went on a few times... finally pressed the power button to turn it off, then on again, and I got the KP screen.

    Rebooted a few times, the same thing. Found out about the hardware test on the install disc, ran that and all passed ok. Still couldn't boot it though, so whilst on the phone to my local Apple store (who didn't answer the phone after 5 minutes of ringing!) I booted in to fire wire disk mode, and connected to the mini - everything was there, so I started to think about backing up the drive on to an external disk. Rebooted (can't think why) and everything is back to normal. Don't appear to have lost anything from the machine, so am now just starting to calm down now after being very panicky about loosing everything!

    Just wondering why this would happen, and if the firewire disk mode would have been a useful thing to have repaired things... anyway, here's the log that I got - anyone know what it means? I'm off to buy a new external drive tomorrow just for backups!

    panic(cpu 0 caller 0x001A329B): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
    CR0: 0x8001003b, CR2: 0x0000007c, CR3: 0x00e02000, CR4: 0x000006e0
    EAX: 0x00000000, EBX: 0x3634b910, ECX: 0x00001000, EDX: 0x5dc00000
    CR2: 0x0000007c, EBP: 0x3634b668, ESI: 0x00000000, EDI: 0x04cacc04
    EFL: 0x00010202, EIP: 0x001e24be, CS: 0x00000008, DS: 0x04ca0010

    Backtrace, Format - Frame : Return Address (4 potential args on stack)
    0x3634b468 : 0x128d08 (0x3c9ac4 0x3634b48c 0x131de5 0x0)
    0x3634b4a8 : 0x1a329b (0x3cf784 0x0 0xe 0x3cefa8)
    0x3634b5b8 : 0x19a934 (0x3634b5d0 0x3634b644 0x0 0x0)
    0x3634b668 : 0x3063da (0x0 0x4cacf24 0x0 0x3634b998)
    0x3634b688 : 0x3073fe (0x3634b910 0x2 0x4d0c804 0x0)
    0x3634b9f8 : 0x305ef5 (0x4cacc04 0x1 0x0 0x0)
    0x3634bad8 : 0x1e62ac (0x4b68d00 0x0 0xbffffdb8 0x0)
    0x3634bb28 : 0x1d39e8 (0x4b68d00 0x0 0xbffffdb8 0x0)
    0x3634bf58 : 0x3788ea (0x4cd87d0 0x4a705f8 0x4a7063c 0x0)
    0x3634bfc8 : 0x19ad0e (0x4a750a0 0x0 0x19d0b5 0x4a7c4c4) No mapping exists for frame pointer
    Backtrace terminated-invalid frame pointer 0xbffffe08

    Kernel version:
    Darwin Kernel Version 8.8.5: Mon Dec 11 19:39:17 PST 2006; root:xnu-792.16.5.obj~1/RELEASE_I386

    Model: MacBookPro2,2, BootROM MBP22.00A5.B01, 2 processors, Intel Core 2 Duo, 2.33 GHz, 3 GB
    Graphics: ATI Radeon X1600, ATY,RadeonX1600, PCIe, 256 MB
    Memory Module: BANK 0/DIMM0, 2 GB, DDR2 SDRAM, 667 MHz
    Memory Module: BANK 1/DIMM1, 1 GB, DDR2 SDRAM, 667 MHz
    AirPort: spairport_wireless_card_type_airport_extreme (0x168C, 0x87), 1.0.46
    Bluetooth: Version 1.7.11f14, 2 service, 0 devices, 1 incoming serial ports
    Network Service: Parallels Host-Guest, Ethernet, en2
    Network Service: Parallels NAT, Ethernet, en3
    Serial ATA Device: Hitachi HTS541616J9SA00, 149.05 GB
    Parallel ATA Device: HL-DT-ST DVDRW GWA4080MA
    USB Device: Built-in iSight, Micron, Up to 480 Mb/sec, 500 mA
    USB Device: Apple Internal Keyboard / Trackpad, Apple Computer, Up to 12 Mb/sec, 500 mA
    USB Device: IR Receiver, Apple Computer, Inc., Up to 12 Mb/sec, 500 mA
    USB Device: Bluetooth HCI, Up to 12 Mb/sec, 500 mA


  2. yellow Moderator emeritus


    Oct 21, 2003
    Portland, OR
    No. And the odd kernel panic here and there is not unusual. It's when they're happening often, say once every 2 weeks or more. That's when you need to worry and start troubleshooting. But there's nothing really good in that KP log that points to an easy culprit.

    A backup is always a good idea.

Share This Page