kernel panics gone wild

hey guys, I'm having a problem and could use some help. I got my mbp in april, and since then have had about 20 kernel panics (including one the day I got it before I had any software installed). after reinstalling os x and replacing the logic board, apple finally replaced my laptop with a new 2.2ghz mbp. unfortunately, this one has the same problem. I only got the laptop 2 days ago, but I've already had 4 kernel panics! the only programs I have running are quicksilver, smcfancontrol, transmission and firefox. the kernel panics usually happen when I leave the laptop running for a bit and the screen dims, and then when I move the mouse to wake it up, it happens. I can't see it being software; the only programs I have installed are reputable, mostly stuff I've seen recomended around here and other mac forums. could I have gotten another faulty mbp? I do have an apple store around me, but unfortantely I'm in college right now without a car so I'll need to plan my trip there. basically what I'm asking is what can I do on my own? I'll post all 4 panic.logs for you guys to look at and see if you can discern any meaning from them. btw, wifi was off everytime it happened (I've heard wifi is a common source of kernel panics).

Sat Sep 8 10:29:20 2007
panic(cpu 0 caller 0x001A4A55): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x80010033, CR2: 0x0901010f, CR3: 0x01327000, CR4: 0x000006e0
EAX: 0x03f45500, EBX: 0x00000030, ECX: 0x004b0958, EDX: 0x03f33de0
CR2: 0x0901010f, EBP: 0x25883c48, ESI: 0x00000006, EDI: 0x03ed8f80
EFL: 0x00010202, EIP: 0x0901010f, CS: 0x00000008, DS: 0x00000010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x25883a18 : 0x128d08 (0x3cc0ec 0x25883a3c 0x131de5 0x0)
0x25883a58 : 0x1a4a55 (0x3d2524 0x0 0xe 0x3d1d48)
0x25883b68 : 0x19aeb4 (0x25883b80 0x202 0x25883bd8 0x1416ad)
0x25883c48 : 0x3c1e4a (0x3ed8f80 0x4415440 0x0 0x3c20a5)
0x25883c68 : 0x3c2840 (0x4415440 0x0 0x0 0x0)
0x25883ca8 : 0x3c28ad (0x4415440 0x3ed4cc0 0x3efa1c0 0x1628d8)
0x25883ce8 : 0x3875d8 (0x4417600 0x0 0x25883d28 0x3c1fb8)
0x25883d08 : 0x38adf7 (0x4930880 0x3eeff00 0x0 0x4930880)
0x25883d28 : 0x3b23e4 (0x4930880 0x3eeff00 0x25883d58 0x3bef8f)
0x25883d78 : 0x188511 (0x4930880 0x4b2e4b4 0x4b2e4c8 0x11cc32)
0x25883db8 : 0x12b4c3 (0x4b2e6b4 0x4b2e498 0x0 0x0)
0x25883df8 : 0x124b17 (0x4b2e600 0x0 0x18 0x25883edc)
0x25883f08 : 0x195a42 (0x25883f44 0x0 0x0 0x0)
0x25883fc8 : 0x19b32e (0x402e660 0x0 0x10 0x0) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xb011e428

Kernel version:
Darwin Kernel Version 8.10.3: Wed Jun 27 23:29:36 PDT 2007; root:xnu-792.23.3~1/RELEASE_I386


*********

Sat Sep 8 16:14:52 2007
panic(cpu 1 caller 0x001A4A55): Unresolved kernel trap (CPU 1, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0xffffffff, CR3: 0x01327000, CR4: 0x000006e0
EAX: 0x03ea6000, EBX: 0x00000030, ECX: 0x004b0958, EDX: 0x0441ea20
CR2: 0xffffffff, EBP: 0x258bbc48, ESI: 0x00000006, EDI: 0x07753580
EFL: 0x00010202, EIP: 0xffffffff, CS: 0x00000008, DS: 0x00000010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x258bba18 : 0x128d08 (0x3cc0ec 0x258bba3c 0x131de5 0x0)
0x258bba58 : 0x1a4a55 (0x3d2524 0x1 0xe 0x3d1d48)
0x258bbb68 : 0x19aeb4 (0x258bbb80 0x202 0x258bbbd8 0x1416ad)
0x258bbc48 : 0x3c1e4a (0x7753580 0x772ef80 0x0 0x3c20a5)
0x258bbc68 : 0x3c2840 (0x772ef80 0x0 0x0 0x0)
0x258bbca8 : 0x3c28ad (0x772ef80 0x45c5440 0x45823c0 0x1628d8)
0x258bbce8 : 0x3875d8 (0x458b700 0x0 0x258bbd28 0x3c1fb8)
0x258bbd08 : 0x38adf7 (0x4d2b200 0x860dd80 0x0 0x4d2b200)
0x258bbd28 : 0x3b23e4 (0x4d2b200 0x860dd80 0x258bbd58 0x3bef8f)
0x258bbd78 : 0x188511 (0x4d2b200 0x49d6eb4 0x49d6ec8 0x11cc32)
0x258bbdb8 : 0x12b4c3 (0x4dbe1b4 0x49d6e98 0x0 0x0)
0x258bbdf8 : 0x124b17 (0x4dbe100 0x0 0x18 0x258bbedc)
0x258bbf08 : 0x195a42 (0x258bbf44 0x0 0x0 0x0)
0x258bbfc8 : 0x19b32e (0x40433c0 0x0 0x19e0b5 0x40433c0) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xb011e448

Kernel version:
Darwin Kernel Version 8.10.3: Wed Jun 27 23:29:36 PDT 2007; root:xnu-792.23.3~1/RELEASE_I386


*********

Sun Sep 9 08:43:02 2007
panic(cpu 0 caller 0x001A4A55): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x80010033, CR2: 0x0000002b, CR3: 0x018a8000, CR4: 0x000006e0
EAX: 0x04ecfca0, EBX: 0x00000018, ECX: 0x004b0958, EDX: 0xffffffff
CR2: 0x0000002b, EBP: 0x25dd3c48, ESI: 0x00000003, EDI: 0x08734b80
EFL: 0x00010202, EIP: 0x003c1cee, CS: 0x00000008, DS: 0x02290010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x25dd3a28 : 0x128d08 (0x3cc0ec 0x25dd3a4c 0x131de5 0x0)
0x25dd3a68 : 0x1a4a55 (0x3d2524 0x0 0xe 0x3d1d48)
0x25dd3b78 : 0x19aeb4 (0x25dd3b90 0x1 0x25dd3b98 0x38)
0x25dd3c48 : 0x3c1e4a (0x8734b80 0x4d45280 0x0 0x3c20a5)
0x25dd3c68 : 0x3c2840 (0x4d45280 0x0 0x0 0x0)
0x25dd3ca8 : 0x3c28ad (0x4d45280 0x4939780 0x865d8c0 0x1628d8)
0x25dd3ce8 : 0x3875d8 (0x4d4b9c0 0x0 0x25dd3d28 0x3c1fb8)
0x25dd3d08 : 0x38adf7 (0x5234e80 0x86b40c0 0x0 0x5234e80)
0x25dd3d28 : 0x3b23e4 (0x5234e80 0x86b40c0 0x25dd3d58 0x3bef8f)
0x25dd3d78 : 0x188511 (0x5234e80 0x7cb7cb4 0x7cb7cc8 0x11cc32)
0x25dd3db8 : 0x12b4c3 (0x7cb66b4 0x7cb7c98 0x0 0x0)
0x25dd3df8 : 0x124b17 (0x7cb6600 0x0 0x18 0x25dd3edc)
0x25dd3f08 : 0x195a42 (0x25dd3f44 0x0 0x0 0x0)
0x25dd3fc8 : 0x19b32e (0x53fb220 0x0 0x19e0b5 0x53fb220) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xb011e448

Kernel version:
Darwin Kernel Version 8.10.3: Wed Jun 27 23:29:36 PDT 2007; root:xnu-792.23.3~1/RELEASE_I386


*********

Sun Sep 9 20:36:05 2007
panic(cpu 1 caller 0x001A4A55): Unresolved kernel trap (CPU 1, Type 14=page fault), registers:
CR0: 0x80010033, CR2: 0x00000004, CR3: 0x018a9000, CR4: 0x000006e0
EAX: 0x04eeee40, EBX: 0x00000028, ECX: 0x004b0958, EDX: 0x04f56a20
CR2: 0x00000004, EBP: 0x25d83c48, ESI: 0x00000005, EDI: 0x08574140
EFL: 0x00010202, EIP: 0x00000004, CS: 0x00000008, DS: 0x00000010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x25d83a18 : 0x128d08 (0x3cc0ec 0x25d83a3c 0x131de5 0x0)
0x25d83a58 : 0x1a4a55 (0x3d2524 0x1 0xe 0x3d1d48)
0x25d83b68 : 0x19aeb4 (0x25d83b80 0x202 0x25d83bd8 0x1416ad)
0x25d83c48 : 0x3c1e4a (0x8574140 0x48f5880 0x0 0x3c20a5)
0x25d83c68 : 0x3c2840 (0x48f5880 0x0 0x0 0x0)
0x25d83ca8 : 0x3c28ad (0x48f5880 0x4ea4bc0 0x4fa7c00 0x1628d8)
0x25d83ce8 : 0x3875d8 (0x48f5800 0x0 0x25d83d28 0x3c1fb8)
0x25d83d08 : 0x38adf7 (0x48f4500 0x86bfc40 0x0 0x48f4500)
0x25d83d28 : 0x3b23e4 (0x48f4500 0x86bfc40 0x25d83d58 0x3bef8f)
0x25d83d78 : 0x188511 (0x48f4500 0x7f949b4 0x7f949c8 0x11cc32)
0x25d83db8 : 0x12b4c3 (0x540c4b4 0x7f94998 0x0 0x0)
0x25d83df8 : 0x124b17 (0x540c400 0x0 0x18 0x25d83edc)
0x25d83f08 : 0x195a42 (0x25d83f44 0x0 0x0 0x0)
0x25d83fc8 : 0x19b32e (0x50843c0 0x0 0x19e0b5 0x50843c0) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xb011e448

Kernel version:
Darwin Kernel Version 8.10.3: Wed Jun 27 23:29:36 PDT 2007; root:xnu-792.23.3~1/RELEASE_I386


*********


oh and on another note, my new mbp has the bottom third of the screen in a yellowish tint. I use this laptop for photography so it's especially noticeable to me. can apple just replace the screen for me?


thanks for any help in advance!

 

In the future, please read the stickies before posting, they may already have the answer for you.

I offer some common troubleshooting tips in the Troubleshooting section of the Mac Switcher's Guide. Try the Repairing Disk Permissions and Resetting PRAM methods.

 

should've mentioned I'd already done all that...

 

Okay, that changes the story a bit. Try reinstalling OS X again, it may fix the issue (I had several kernel panics, probably due to a bad application installation; reinstalled OS X, fixed the problem).

If not, take it to the Apple Store.

 

I'm hesitant to reinstall os x because with my previous mbp it did not solve the problem. I really don't like reinstalling unless it's a last resort and I know that it'll fix the problem.

does the panic.log mean anything to you?

 

Lots of kernel panics == Bad OS X install or hardware problem.

Once you have done the PRAM and the permissions repair, and validated your disk (no errors), there is not much more than you can do. The quickest and easiest is to do what Sam suggested and try to reinstall, then return to the store.

Reinstalling OS X is pretty painless, just copy your disk contents to an external disk, reinstall, then use the Migration Assistant to get your old programs and settings back. Shouldn't take more than a few hours with the actual backup taking the longest depending on how much crap you have on your drive.

Trying to fix whatever is wrong in a bad OS X install will take forever and likely lead nowhere.

For example, I have had two bad OS X installs in the past. One was bad because I had used a tool that didn't properly clone a disk (PsyncX). The clone was just bad and unusable with pretty much all permissions wrong. The other one I had partitioned my internal drive with the Apple Partition Format instead of the "GUID" partition table which worked for the most part but caused subtle and strange bugs. If you ever formatted your internal drive yourself you might want to check that.

 

From what I have seen the majority of kernel panics are hardware induced, and in particular it's usually bad or improperly seated RAM. I would try reseating the RAM first, if that doesn't work run the machine with one DIMM at a time and see if the kernel panics follow a DIMM. Alternately, if you have a spare or can borrow some known good RAM you could try that.

I would also make sure that the machine is not overheating. You mention SMCfancontrol. With that running you should be OK, but to be safe you might try uninstalling it and let the hardware control the fan. You definitely have a serious issue. I haven't had a kernel panic in years.

 

First try what duffyanneal says above, they are good steps to try. As mentioned there many kernel panics are caused by bad RAM.

After that, erase & install would be the best way of finding out for sure whether this is a hardware or software issue. If it persists after that, it's a hardware issue.

A software-induced kernel panic can be very hard to find, which means it is usually so much easier to just make a backup and do an erase & install. This goes double for intermittent issues.

As for that not fixing it with your previous MBP, it's not a matter of resolving the issue yet, it's a matter of figuring out where the issue lies. If erase & install fixes it, all is well. If erase & install doesn't fix it, it's a hardware issue and needs to be looked at by Apple or an Apple authorized service provider.

 

well luckily I have an extra 1gb stick of ram from my previous mbp so I'll try swapping that in for each stick and seeing whether the kernel panics stop. the problem is though that they're completely random. they're impossible to reproduce so I'll never be 100% sure that I've solved the issue.

thanks for the help guys, this forum rocks!

 

Hope the suggestions help, jnev! Keep us posted on how it goes .

 

Even though they are impossible to reproduce, you have the logs, so Apple will see that it is occurring. At this point it is almost undoubtedly hardware. If the RAM does not do the trick it is time to go to the Apple Store. The panics with the yellow screen, you deserve a new one.

 

well I still haven't had time to reinstall os x or go to the apple store, but my kernel panics keep happening, at a much higher rate than my last mbp. on that one I had maybe 20 kp's in like 4 months, now, having gotten this mbp on the 7th, I've had 7 kernel panics (yes you read that correctly). not only that, but whenever I reboot my mbp after the kernel panic, spotlight often doesn't work (as in the search box either doesn't come up when I click on the icon, or nothing happens when I type something in the search box), AND my mouse settings for my vx revolution get reset to the default settings. as yo guys can probably imagine, it's very frustrating.

if I call apple would they be able to cross-ship me a new mbp and a box so I can ship this one back to them, or would they need to see the mbp first? I really cannot be without a computer at all right now, so giving it up is impossible. guess apple should be expecting a call from a very disgruntled customer tomorrow...