Kernel Panic


macrumors 6502a
Original poster
May 16, 2006
I had my first kernel panic with my MBP... stupid 10.4.8... I woke my MBP from sleep and hit F12, saw Dashboard, then it happened... here is the error:
panic(cpu 0 caller 0x001A3135): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0x80018009, CR3: 0x00da4000, CR4: 0x000006e0
EAX: 0x80018001, EBX: 0x035d566c, ECX: 0x02b80d3c, EDX: 0x02b80d44
CR2: 0x80018009, EBP: 0x13f53cc8, ESI: 0x02b80d40, EDI: 0x00000001
EFL: 0x00010883, EIP: 0x0013ee1e, CS: 0x00000008, DS: 0x13f50010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x13f53af8 : 0x128d1f (0x3c9540 0x13f53b1c 0x131df4 0x0)
0x13f53b38 : 0x1a3135 (0x3cf1f4 0x0 0xe 0x3cea24)
0x13f53c48 : 0x19a8d4 (0x13f53c58 0x0 0xe 0x48)
0x13f53cc8 : 0x1267a4 (0x2b80d3c 0x35d566c 0x13f53cf8 0x121ae3)
0x13f53cf8 : 0x1268f4 (0x35d5654 0x2b80d00 0x400 0x1344a000)
0x13f53d78 : 0x14a189 (0x24cbe40 0x72c3 0x35ffdb4 0x35ffdc8)
0x13f53db8 : 0x12b4da (0x346dba8 0x35ffd98 0x0 0x0)
0x13f53df8 : 0x124b2b (0x346db00 0x0 0x24 0x13f53edc)
0x13f53f08 : 0x1955a1 (0x13f53f44 0x0 0x0 0x0)
0x13f53fc8 : 0x19ad4e (0x35f5530 0x0 0x19d0b5 0x35f5530) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xb0282d08

Kernel version:
Darwin Kernel Version 8.8.1: Mon Sep 25 19:42:00 PDT 2006; root:xnu-792.13.8.obj~1/RELEASE_I386

Model: MacBookPro1,1, BootROM MBP11.0055.B03, 2 processors, Intel Core Duo, 2 GHz, 1 GB
Graphics: ATI Radeon X1600, ATY,RadeonX1600, PCIe, 128 MB
Memory Module: BANK 0/DIMM0, 512 MB, DDR2 SDRAM, 667 MHz
Memory Module: BANK 1/DIMM1, 512 MB, DDR2 SDRAM, 667 MHz
AirPort: spairport_wireless_card_type_airport_extreme (0x168C, 0x86), 0.1.27
Bluetooth: Version 1.7.9f12, 2 service, 0 devices, 1 incoming serial ports
Network Service: Built-in Ethernet, Ethernet, en0
Network Service: AirPort, AirPort, en1
Serial ATA Device: FUJITSU MHV2080BH, 74.53 GB
Parallel ATA Device: MATSHITADVD-R UJ-857
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

can anyone explain why the kernel panic happened?


macrumors 603
Apr 29, 2005
San Francisco
Can't really explain it, but they do happened randomly at times. It really is nothing to worry about unless they start happening very frequently.


macrumors 603
Apr 29, 2005
San Francisco
risc said:
On what planet?

OP I have no idea how to read the kernel panic crash log, but they don't just happen randomly! :rolleyes:
Well I can read Crash Logs and it says "This crash is of a random nature".

So there. But seriously, it's nothing to worry about.


Moderator emeritus
Oct 21, 2003
Portland, OR
It may not happen "randomly", but his point is still valid. Unless this starts happening frequently, I wouldn't worry about it.

What does "frequently" mean? Once a week? That's too often. Once a month. Meh.. boarderline. I'd want to track it down, personally. Beyond that is a speedily dminishing point of importance.

IJ Reilly

macrumors P6
Jul 16, 2002
I don't buy the randomness theory. Something causes kernel panics. It may be a result of conditions that may not occur often, but this is different than randomness. A lot of people never experience any kernel panics. If I had one, I'd be watching the situation very closely. I'd also run fsck after any kernel panic to repair any damage that may have occurred to the hard drive directory.


macrumors 68040
Oct 24, 2002
The West Loop

Having suffered through overheated mobos and other maladies, IMHO a Kernel Panic is rather alarming to me. Usually indicative of a hardware issue.

I do get them, but maybe once or twice a year on any of my four Macs, and it's usually because of something goofy. Like a static discharge right when I'm plugging a USB into the port. But as GimmeSlack12 says, some can appear random at times - RAM bug-outs are a common cause of 'unexplainables'.

So let's take a look at your report (cracks knuckles). I see this: panic(cpu 0 caller 0x001A3135): Unresolved kernel trap (CPU 0, Type 14=page fault)
Backtrace terminated-invalid frame pointer 0xb0282d08

This is screaming RAM Cache burp. The cause of the KP appears to be a paging fault. Meaning the cache may not have returned the connection to the CPU, or forwarded the data to then next stage, this precipitated the KP. Further evidenced by the terminated backtrace - it is as if the path back to the cause of the panic dissapeared to the tracer - another indication of a cache dump. Check to see if there is a crash log at the root of your boot drive.

Ok, so now I've thrown a whole lot of technobabble at you, I'd still say this is probably a one-off. But, if it happens again with both paging faults AND a backtrace termination, seek help. It may be a symptom of a dodgy L1 cache on the Microprocessor - and this would need a new Microprocessor.