MBP C2D Kernel Panic

[theyoda3]

Yay, so things aren't going as well as they started. I just got a kernel panic. I was using Adium, Safari, Mail, and iTunes. I was on AC charging my battery and I was using wireless. Maybe I'm damned for not having bought AppleCare yet. Here is what it says, any suggestions lol? Thanks.

panic(cpu 0 caller 0x001A3135): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0x00000000, CR3: 0x01859000, CR4: 0x000006e0
EAX: 0x00000000, EBX: 0x004b0480, ECX: 0x04b3b718, EDX: 0x004b0480
CR2: 0x00000000, EBP: 0x25db3cd8, ESI: 0x00000000, EDI: 0x00000000
EFL: 0x00010006, EIP: 0x001400c9, CS: 0x00000008, DS: 0x3b0e0010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x25db3aa8 : 0x128d08 (0x3c9afc 0x25db3acc 0x131de5 0x0)
0x25db3ae8 : 0x1a3135 (0x3cf7b0 0x0 0xe 0x3cefe0)
0x25db3bf8 : 0x19a904 (0x25db3c10 0x0 0x25db3c38 0x1)
0x25db3cd8 : 0x1402da (0x6496324 0x49d8880 0x25db3d38 0x206)
0x25db3cf8 : 0x11f9cf (0x6496354 0x4b0480 0x0 0x0)
0x25db3d58 : 0x11fbc9 (0x6496354 0x54f1900 0x25db3da4 0x0)
0x25db3db8 : 0x11f293 (0x6496354 0x54f1900 0x10 0x1)
0x25db3df8 : 0x125a0b (0x54f1900 0x10 0x1 0x0)
0x25db3f08 : 0x1955a8 (0x25db3f44 0x0 0x0 0x0)
0x25db3fc8 : 0x19ad7e (0x4b41ae0 0x0 0x19d0b5 0x4b3ed60) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xbfffe718

Kernel version:
Darwin Kernel Version 8.8.2: Thu Sep 28 20:43:26 PDT 2006; root:xnu-792.14.14.obj~1/RELEASE_I386

Model: MacBookPro2,2, BootROM MBP22.00A5.B00, 2 processors, Intel Core 2 Duo, 2.33 GHz, 2 GB
Graphics: ATI Radeon X1600, ATY,RadeonX1600, PCIe, 256 MB
Memory Module: BANK 0/DIMM0, 1 GB, DDR2 SDRAM, 667 MHz
Memory Module: BANK 1/DIMM1, 1 GB, DDR2 SDRAM, 667 MHz
AirPort: AirPort Extreme, 1.0.27p1
Bluetooth: Version 1.7.11f14, 2 service, 0 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
Serial ATA Device: FUJITSU MHW2120BH, 111.79 GB
Parallel ATA Device: MATSHITADVD-R UJ-857D
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

 

[Willis]

No! say it isnt true!!!

 

[theyoda3]

I wish it wasn't true either. I love this laptop, but I'm a little hesitant now to trust it like I trusted my PowerBook.

 

[Unorthodox]

panic(cpu 0 caller 0x001A3135): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:

It looks like your kernel panicked when it got trapped. I think it got trapped in a type "14 CPU trap".
And it's all the pages fault.


Sorry I couldn't help more...
Call Apple if it happens again.

 

[mad jew]

Try checking your RAM by taking out one stick, running it for a while, if it panics, put that stick back and take out the other stick. Is it third party memory?

 

[scott523]

Yea it seems like your MBP doesn't quite recognize one of the 1GB stick RAM you got there.

 

[cmptrs826]

Me Too!

I also experienced a kernel panic on my new mbp. I was using msn messenger and safari at the time. Its a little scary when this happens the second day you own your $2500 notebook.

 

[treblah]

Is it third party memory?

Doubtful seeing as how he has the 256MB x1600.

 

[theyoda3]

It is all Apple supplied hardware, so the RAM is from Apple. So it's possibly just bad RAM and I could reseat it and see that works? Ah I see where you can tell. System profiler recognizes it just fine.

Thanks

 

[Am3822]

Can you replicate this crash? As I'm sure you know, there's a memory testing utility you that could try if you want to be sure that all is well with your memory.

Edit: Troubling news indeed, especially since these are all run of the mill applications, and I see that you've also reported the whine.

 

[theyoda3]

Sometimes the test doesn't catch everything, but this weekend I will probably reseat the RAM and also run the test to check. After that I'll see what happens.

Also, I don't want to replicate the incident, but I'm in that same situation a lot so the opportunity for it to replicate is certainly there.

 

[theyoda3]

Actually I don't understand why you think the RAM isn't quite recognized. I thought it had something to do with the line saying BANK 0/DIMM0, but they banks a labeled bank 0 and bank 1 in system profiler.

 

[mad jew]

Doubtful seeing as how he has the 256MB x1600.

Good pickup. I'm the first one to admit I'm not very up with how much RAM comes standard in different specced machines.

Of course, a if it was bought from a reseller then it could have been specced this way, with third party RAM, but that's not the case anyway.

Sometimes the test doesn't catch everything, but this weekend I will probably reseat the RAM and also run the test to check. After that I'll see what happens.

That's an excellent idea.

Actually I don't understand why you think the RAM isn't quite recognized. I thought it had something to do with the line saying BANK 0/DIMM0, but they banks a labeled bank 0 and bank 1 in system profiler.

You're right, the RAM is being recognised but that doesn't mean it's not the problem. Still, test it to find out for us.

 

[5150 Joker]

You shouldn't let your kernel panic so easily. Give it some medication and a glass of milk.

 

[darkwing]

This is a problem with some driver code. A page fault in the kernel without a user context associated with it (such as interrupt code) can't be handled and that's why the kernel panics. If this page fault occurred in a userland application such as Adium, then this would either be a TLB miss (and the page fault would trigger a TLB refill) or the program trying to access an address that its virtual address space doesn't have in use. In the latter case, the program will be terminated by the OS.

While bad ram is a possibility, it's always the first thing people blame. If this were true you'd have all kinds of problems and not just kernel panics. This is most likely due to a bug of Apple's. There might be a couple as the c2d MBPs are still a little new. Just be patient and hope it doesn't happen again.

 

[theyoda3]

I don't think I understand any of the last post except for the last paragraph and one of the sentences saying that it seems like a driver code error lol.

 

[cilantro26]

I just experienced the 2nd kernel panic within 3 days on my brand new C2D 2.33 2GB 160HD Macbook Pro. The panic.log entries for both cases look virtually the same (see below). In both cases Firefox 2.0 was running (web browsing via wireless connection from Linksys router WRT54GS and range expander WRE54G). The panic.log entries seem to indicate that the problems may have been related to the wireless network. An additional factor that seems to substantiate this theory is that I had no network connectivity after restarting the system right after the grey screen of death... However, after a 2nd restart, everything worked fine again in both cases. I already used memtest to make sure that there are no memory problems... I've attached one of the panic.log entries below, in case anyone has seen this particular issue before or has some advice on things to try before I take my MBP to the Apple store... Thanks!!

panic(cpu 0 caller 0x001A3135): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0x45903d45, CR3: 0x00c85000, CR4: 0x000006e0
EAX: 0x45903d15, EBX: 0x1b151d15, ECX: 0x3b026a90, EDX: 0x107cc320
CR2: 0x45903d45, EBP: 0x24ffbd28, ESI: 0x3af7e320, EDI: 0x234b5308
EFL: 0x00010202, EIP: 0x3c0fec78, CS: 0x00000008, DS: 0x00000010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x24ffbae8 : 0x128d08 (0x3c9afc 0x24ffbb0c 0x131de5 0x0)
0x24ffbb28 : 0x1a3135 (0x3cf7b0 0x0 0xe 0x3cefe0)
0x24ffbc38 : 0x19a904 (0x24ffbc50 0x0 0x24ffbc78 0x127ee3)
0x24ffbd28 : 0x3c0d87f4 (0x2367d004 0x3af7e320 0x107cc320 0x45903d15)
0x24ffbf08 : 0x398f79 (0x234b5308 0x38db800 0x1 0x35f6364)
0x24ffbf58 : 0x39814b (0x38db800 0x135eb4 0x0 0x35f6364)
0x24ffbf88 : 0x397e81 (0x3cc4f40 0x380b880 0x8000 0xf0b)
0x24ffbfc8 : 0x19a77c (0x3cc4f40 0x0 0x19d0b5 0x4359ea0) Backtrace terminated-invalid frame pointer 0x0
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AirPortAtheros(210.8)@0x3c0aa000
dependency: com.apple.iokit.IONetworkingFamily(1.5.1)@0x3b1ea000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x35157000
dependency: com.apple.iokit.IO80211Family(140.4)@0x3b200000

Kernel version:
Darwin Kernel Version 8.8.2: Thu Sep 28 20:43:26 PDT 2006; root:xnu-792.14.14.obj~1/RELEASE_I386

 

[iW00t]

What can cause a page fault? Maybe a faulty stick of memory flipped a bit which contained the pointer to a bit of memory?

 

[mad jew]

I already used memtest to make sure that there are no memory problems...

Unfortunately it's not that simple. Memory tests are pretty pathetic at finding bad RAM so the best way to test it yourself is to physically remove one stick at a time and run for a while to see if you experience any more panics/troubles. From my extremely limited knowledge of everything, your log is pointing toward memory problems anyway.

What can cause a page fault? Maybe a faulty stick of memory flipped a bit which contained the pointer to a bit of memory?

Nine out of ten times, yes, it's memory. Of course, it could also be the hard drive or the logic board since they're involved in the paging process, but it's usually memory in my experience.

 

[iW00t]

Unfortunately it's not that simple. Memory tests are pretty pathetic at finding bad RAM so the best way to test it yourself is to physically remove one stick at a time and run for a while to see if you experience any more panics/troubles. From my extremely limited knowledge of everything, your log is pointing toward memory problems anyway.

Memory test is useless indeed, I've tried it before and it seems like it is not capable of testing 100% of the memory (afterall the OS needs some memory to run off). The most lightweight memory tester I've found didn't work on Macs (Memtest x86).

Turned out that the stick that memtest was "passing" was indeed faulty after all.

 

[Bidochon]

Kernel panic !

I have experienced about ten kernel panic this last two days. Itunes, safari were opened. I have formated first, i thought it was software. But just after I had another kernel panic while I was installing office.
I noticed something, when I reinstalled OS X, the istallation process froze and I had to shutdown the computer and restart it to continue the installation.
Something wrong, and something physical. Maybe the RAM. The thing is, I used my MBP intensively the first ten days without any problem and for the past two days I live with kernel panic !
I'll phone to the apple care tomorrow. I hope they will take it and change the memory.
Anybody knows how long does it take ?

here is my panic log:
Sun Nov 12 21:33:16 2006
panic(cpu 0 caller 0x001A3135): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0x00000010, CR3: 0x00eea000, CR4: 0x000006e0
EAX: 0x00000000, EBX: 0x0187dadc, ECX: 0x0045cee0, EDX: 0x00000010
CR2: 0x00000010, EBP: 0x2506bf28, ESI: 0x02c607c4, EDI: 0x00000000
EFL: 0x00010202, EIP: 0x0017e2cf, CS: 0x00000008, DS: 0x00000010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x2506bd18 : 0x128d08 (0x3c9afc 0x2506bd3c 0x131de5 0x0)
0x2506bd58 : 0x1a3135 (0x3cf7b0 0x0 0xe 0x3cefe0)
0x2506be68 : 0x19a904 (0x2506be80 0x4b5010 0x2506bea8 0x199d69)
0x2506bf28 : 0x1788e1 (0x2c607c4 0x4afc9c 0x199a51 0x38641e8)
0x2506bfa8 : 0x178c01 (0x10004003 0x178bef 0x0 0x4b8000)
0x2506bfc8 : 0x19a77c (0x0 0x0 0x19d0b5 0x38641cc) Backtrace terminated-invalid frame pointer 0x0

Kernel version:
Darwin Kernel Version 8.8.2: Thu Sep 28 20:43:26 PDT 2006; root:xnu-792.14.14.obj~1/RELEASE_I386


I use a wrt54g router too.

 

[Demon Hunter]

I won't pretend to know what the log means, but the RAM seems likely.

 

[Bidochon]

It seems to be a memory problem

I have ran the apple hardware test (reboot with install disc1 and press d). It says that is a memory problem. One of the stick must be defectuous.
I'll phone apple care tomorrow.

 

[Fredou51]

OMG. That's now four person who had kernel panic with the new C2D MBP! That's quite a lot especially since very few people have the new C2D (with the 17" not shipping!).

Frederic

 

[mad jew]

It's not really the machine's fault so much as the memory manufacturer.