[harrisjamieh]

I have an iMac Core Duo as well as my new MacBook. Since I have had my iMac (about a week after they came out), I have had no kernal panics, and it has been a great machine. Since I have had my MacBook (just over a week), I have had 2 kernal panics.

Now I know 2 is hardly the end of the world or anything to cry home about, but I've heard people who have had machines for 5 or 6 years and have not once had a kernal panic, and then theres me, with a one week old machine, which has already had 2.

They happened in no particular place either, one was when the computer was simply idle-ing - on but doing nothing, and the other was whilst playing a DVD...

Has anyone else had an increased number of KPs compared to older machines on their new MBs?

I know these kind of threads can be tedious, but do I have any cause for concern?

Cheers

[seanc]

Well, can you post the panic.log?

My iBook G4 has had it's fair share of Kernel Panics but that was caused by my bluetooth dongle when I was running Panther and a wireless USB driver I had installed. Did you have anything connected at the time?

[harrisjamieh]

OK, found the logs, one for each of the 2 panics:

Thu May 25 16:09:38 2006
panic(cpu 0 caller 0x0019C9EF): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0x0bd62002, CR3: 0x00d25000, CR4: 0x000006e0
EAX: 0x02052340, EBX: 0x02051740, ECX: 0x00000000, EDX: 0x004969b0
ESP: 0x0bd62002, EBP: 0x0b213db4, ESI: 0x004969b0, EDI: 0x006a8918
EFL: 0x00010202, EIP: 0x0204d5e1, CS: 0x00000008, DS: 0x0b210010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0xb213c30 : 0x128b5e (0x3bbf84 0xb213c54 0x131bbc 0x0)
0xb213c70 : 0x19c9ef (0x3c13b4 0x0 0xe 0x3c116c)
0xb213d20 : 0x197b8d (0xb213d34 0xb213db4 0x204d5e1 0x48)
0xb213d2c : 0x204d5e1 (0x48 0x1bf0010 0x6a0010 0xb210010)
0xb213db4 : 0x6a8987 (0x2051740 0x4969b0 0x1bf3164 0x10001)
0xb213e04 : 0x6a894b (0x1d77e00 0x1e97000 0xb213e24 0x38c8d3)
0xb213e24 : 0x38e264 (0x1d77e00 0x1e97000 0x0 0x0)
0xb213e64 : 0x6a890d (0x1e203c0 0x6a8918 0x1e97000 0x0)
0xb213e94 : 0x37d088 (0x1d77e00 0x0 0x1e97000 0x3ae14e)
0xb213ec4 : 0x380dd4 (0x1e97000 0x1e96840 0x1 0x1e97000)
0xb213f44 : 0x380c95 (0x1e97000 0x1fc7600 0x0 0x3b3881)
0xb213f94 : 0x3823de (0x1e97000 0x0 0x20aa950 0x0)
0xb213fd4 : 0x197a29 (0x20aa950 0x0 0x2af54f8 0x2051740) Backtrace terminated-invalid frame pointer 0x0
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.IOBluetoothFamily(1.7.4f16)@0x69d0 00

Kernel version:
Darwin Kernel Version 8.6.2: Thu Apr 13 18:48:29 PDT 2006; root:xnu-792.9.59.obj~1/RELEASE_I386


*********

Sat Jun 3 10:15:03 2006
panic(cpu 1 caller 0x0019C9EF): Unresolved kernel trap (CPU 1, Type 14=page fault), registers:
CR0: 0x80010033, CR2: 0x00000000, CR3: 0x00d4f000, CR4: 0x000006a0
EAX: 0x037c64c0, EBX: 0x00000003, ECX: 0x0f633c50, EDX: 0x024a0500
ESP: 0x00000000, EBP: 0x0f633d38, ESI: 0x037c1a40, EDI: 0x03487480
EFL: 0x00010293, EIP: 0x00000000, CS: 0x00000008, DS: 0x003d0010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0xf633bc4 : 0x128b5e (0x3bbf84 0xf633be8 0x131bbc 0x0)
0xf633c04 : 0x19c9ef (0x3c13b4 0x1 0xe 0x3c116c)
0xf633cb4 : 0x197b8d (0xf633cc8 0xf633d38 0x0 0xf630048)
0xf633cc0 : 0x0 (0xf630048 0x3b0010 0x37c0010 0x3d0010)
0xf633d38 : 0x3a5056 (0x3487480 0x37c1a40 0x25c4504 0x121887)
0xf633d98 : 0x189395 (0x25c4500 0x27f25ac 0x2f5ffb4 0x2f5ffc8)
0xf633dd8 : 0x12b389 (0x27f2584 0x2f5ff98 0x0 0x0)
0xf633e18 : 0x124902 (0x27f2500 0x0 0x48 0xf633efc)
0xf633f28 : 0x192f04 (0xf633f54 0x0 0x0 0x0)
0xf633fd8 : 0x19805b (0x21e9880 0x21e9880 0x3 0x0) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xbfffe658

Kernel version:
Darwin Kernel Version 8.6.2: Thu Apr 13 18:48:29 PDT 2006; root:xnu-792.9.59.obj~1/RELEASE_I386


*********


And no, nothing active was connected to the machine, just power & headphones

[icruise]

I have no idea what that log means, but where did you get your memory?

[seanc]

Thats what I was suspecting, maybe it's faulty...

[harrisjamieh]

At present, the MacBook has 768 RAM in it - 1 x 256 that came with the MacBook, and 1 x 512 that came with my iMac Core Duo (that has been replaced with a higher amount in the iMac).

I doubt its the RAM, as one panic was with the stock 512, and one with the re-config'd 768. Tonight I am exchanging the 256 stick for another 512, giving a total of 1 gig, so it will be interesting to see if I get any more KPs

[harrisjamieh]

Just incase anyone is interested; I found this thread over at dealmac forums, and it seems the problem is to do with unplugging headphones whilst audio is playing, and others are experiencing it:

http://forums.dealmac.com/read.php?4,2574054

[wilsonng]

Isn't it strongly recommended to pair the memory up with same speed and size? While putting two unmatched RAM chips may work, Apple says it will work better if the RAM chips were to interleave....

[drbrett]

Originally Posted by wilsonng

Isn't it strongly recommended to pair the memory up with same speed and size? While putting two unmatched RAM chips may work, Apple says it will work better if the RAM chips were to interleave....

Sure, it'll run faster if you have matched RAM. It should work fine with unmatched ram as well, and not panic.

[harrisjamieh]

Originally Posted by wilsonng

Isn't it strongly recommended to pair the memory up with same speed and size? While putting two unmatched RAM chips may work, Apple says it will work better if the RAM chips were to interleave....

I now have 2 x 512s in my MB

[snoopy199]

Since adding the paired memory have you noticed any KPs

Has performance increased significantly? It's been reported running non matched paired memory modules seems to cause a major performance hit on the MBs.

[harrisjamieh]

I havent had any KPs, no, but as I said, I have only had 2, over a period of 2 weeks, and I have only had this extra RAM 1 day.

Anyway, yes, there seems to be quite a bit of a performance increase, most probably due to the extra RAM rather than the paired RAM.

[snoopy199]

I've read (I'm not sure if its true) but a performance hit of 20% can be realized by not using matched pairs of ram thanks to the dual channel
here's the KB on the dual channel but it doesn't state any specific increase in using matched pairs of ram.

[stuffedmonkey]

It is indeed the audio jack - I saw a couple of complaints on the Apple discussion forums.... I assume that an upcoming driver release will fix it.

[Jerommeke]

I have had 2 kernel panics which had nothing to do with audio jacks or whatsoever. Just when launched, the screen went black and nothing happened. Next launch, it turned out to be a panic. And one on shutting down after coming from sleep. Really weird.

This machine is getting back. Please get me a MacBook Improved.

[berkowit28]

I aslo have somteimes kernel panics with my new MacBook, after it wakes up from sleep. Its also a page fault (14) :/ I didn't add ram (i've 2x512 from Apple), ran memtest, diskcheck, all OK.. did PMU reset.. no idea what to do now

[Tarcat]

Can't help you. Mine works fine. The only Mac I ever had a Kernel panic on was my old 533 G4. And it was a one time thing.

[stuffedmonkey]

I think the problem is that we are still on the build of 10.4.6 that came on the machine. That and the Intel builds are all fairly recent, where OS X has had 5+ years to mature on PPC code. I bet that most of this goes away when 10.4.7 comes.

[greenamp]

Originally Posted by stuffedmonkey

I think the problem is that we are still on the build of 10.4.6 that came on the machine. That and the Intel builds are all fairly recent, where OS X has had 5+ years to mature on PPC code. I bet that most of this goes away when 10.4.7 comes.

Hopefully they will fix the screen dimming thing too that happens when you unplug the power cord.

edit: nvm this is actually an energy saver setting that makes it do this. Durr.

[blackbird_1.0]

I had the audio jack problem on my MacBook, yesterday.