I'm still going with bad RAM.
Has anyone suggested checking the HD for directory damage yet? A longer shot, but worth trying.
Has anyone suggested checking the HD for directory damage yet? A longer shot, but worth trying.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
2 kernel panics in 3 weeks on C2D MBP
- Thread starter mopppish
- Start date
- Sort by reaction score
This may or may not be relevant, but running the new Disk Warrior for Intel utility seems to have ironed out the several weirdnesses i was experiencing on my iMac 24.
I think it's relevant. Hard drive directory corruption seems to be a fairly frequent source of kernel panics and other issues.
Yeah, I still dunno if it's the change to Intel or the change to SATA. I think it's the former because my ol' iMac G5's been fine, as have many others.
Sorry mate, must remember to scrape off the layers of sweat and grime before logging on.
Sorry mate, must remember to scrape off the layers of sweat and grime before logging on.
I did another hardware test after installing the other RAM and did a "verify disk" via Disk Utility.
I know that's not as thorough as other third party utilites, but I don't have any.
If I experience any more problems, I'll just call Apple up. I've already reinstalled the OS, and this is the third laptop I've gone through this semester (the first refurb MB showed up damaged and the whine on the store bought CD MB drove me nuts), so I don't feel like stressing about it. This is after a flawless imac G5 and ibook G4 that I sold to pay for this MBP! Oh, cruel irony!
On the bright side, if I DON'T experience any problems, than I can get a full refund from DMS on the grounds that the other RAM module is technically faulty!
I know that's not as thorough as other third party utilites, but I don't have any.
If I experience any more problems, I'll just call Apple up. I've already reinstalled the OS, and this is the third laptop I've gone through this semester (the first refurb MB showed up damaged and the whine on the store bought CD MB drove me nuts), so I don't feel like stressing about it. This is after a flawless imac G5 and ibook G4 that I sold to pay for this MBP! Oh, cruel irony!
On the bright side, if I DON'T experience any problems, than I can get a full refund from DMS on the grounds that the other RAM module is technically faulty!
Well, I just had another one. That makes 5 since I bought it which, although that averages out to around 1 a week, is unacceptable. Here's the log if anyone knows how to decipher it:
Sun Dec 17 19:27:41 2006
panic(cpu 0 caller 0x00128DA7): {0} Assertion failed: file "/SourceCache/xnu/xnu-792.14.14/libkern/c++/OSObject.cpp", line 267: mem
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x25f8b738 : 0x128d08 (0x3c9afc 0x25f8b75c 0x131de5 0x0)
0x25f8b778 : 0x128da7 (0x3c9b24 0x0 0x3ef908 0x10b)
0x25f8b7a8 : 0x3bca93 (0x3ef908 0x10b 0x3d4f20 0x663d760)
0x25f8b7c8 : 0x3cb78e54 (0x16b70 0x3cbb086c 0x0 0x41eb540)
0x25f8b7e8 : 0x3cb78228 (0x4b03580 0x3cbb086c 0x0 0x4a136c0)
0x25f8b808 : 0x3cb78564 (0x4bd5000 0x3cb98894 0x0 0x3bbd7c)
0x25f8b838 : 0x3cb691c9 (0x4bd5000 0x4a136c0 0x25f8b888 0x3cb645a7)
0x25f8b888 : 0x3cb69aeb (0x4bd5200 0x49f0b40 0x1 0x4bd6b00)
0x25f8b908 : 0x3cb65b85 (0x4bd5200 0x4bd6b00 0x6864706e 0x6973706b)
0x25f8b948 : 0x3cb63ae8 (0x4bd5200 0x3 0x25f8b978 0xc000000)
0x25f8b978 : 0x398071 (0x4b80000 0xc000000 0x0 0x0)
0x25f8b9a8 : 0x3cb63a00 (0x4a56740 0x3cb63a3e 0x4b80000 0xc000000)
0x25f8b9d8 : 0x3870e8 (0x4b80000 0xe00000ff 0x4bca300 0x25f8bf48)
0x25f8ba18 : 0x387343 (0x4bca300 0xe00000ff 0x4b80000 0x25f8bf48)
0x25f8ba48 : 0x383a53 (0x4b80000 0x25f8bb0c 0x1d8d6a4 0x5793318)
0x25f8ba88 : 0x3870a3 (0x4bca300 0x387310 0x25f8bb0c 0x41b3cc0) Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleHDA(1.2.7a9)@0x3cb5f000
dependency: com.apple.iokit.IOHDAFamily(1.2.7a9)@0x3ca7f000
dependency: com.apple.iokit.IOAudioFamily(1.6.0b3)@0x3cb0f000
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
This time I was working in Logic Pro when it happened. Seeing as to how I was doing something different for every kernel panic and have already reinstalled the OS, changed RAM, and eliminated other third party issues, I'll be making a trip to the Apple store I bought it from.
What do you think the chances of them offering me a replacement vs. repair are? I really don't have time to wait for a repair to because I've got two projects to mix in Logic during my break. Plus, this is already the third laptop. Now I'm on to either a repair or a fourth one.
Sun Dec 17 19:27:41 2006
panic(cpu 0 caller 0x00128DA7): {0} Assertion failed: file "/SourceCache/xnu/xnu-792.14.14/libkern/c++/OSObject.cpp", line 267: mem
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x25f8b738 : 0x128d08 (0x3c9afc 0x25f8b75c 0x131de5 0x0)
0x25f8b778 : 0x128da7 (0x3c9b24 0x0 0x3ef908 0x10b)
0x25f8b7a8 : 0x3bca93 (0x3ef908 0x10b 0x3d4f20 0x663d760)
0x25f8b7c8 : 0x3cb78e54 (0x16b70 0x3cbb086c 0x0 0x41eb540)
0x25f8b7e8 : 0x3cb78228 (0x4b03580 0x3cbb086c 0x0 0x4a136c0)
0x25f8b808 : 0x3cb78564 (0x4bd5000 0x3cb98894 0x0 0x3bbd7c)
0x25f8b838 : 0x3cb691c9 (0x4bd5000 0x4a136c0 0x25f8b888 0x3cb645a7)
0x25f8b888 : 0x3cb69aeb (0x4bd5200 0x49f0b40 0x1 0x4bd6b00)
0x25f8b908 : 0x3cb65b85 (0x4bd5200 0x4bd6b00 0x6864706e 0x6973706b)
0x25f8b948 : 0x3cb63ae8 (0x4bd5200 0x3 0x25f8b978 0xc000000)
0x25f8b978 : 0x398071 (0x4b80000 0xc000000 0x0 0x0)
0x25f8b9a8 : 0x3cb63a00 (0x4a56740 0x3cb63a3e 0x4b80000 0xc000000)
0x25f8b9d8 : 0x3870e8 (0x4b80000 0xe00000ff 0x4bca300 0x25f8bf48)
0x25f8ba18 : 0x387343 (0x4bca300 0xe00000ff 0x4b80000 0x25f8bf48)
0x25f8ba48 : 0x383a53 (0x4b80000 0x25f8bb0c 0x1d8d6a4 0x5793318)
0x25f8ba88 : 0x3870a3 (0x4bca300 0x387310 0x25f8bb0c 0x41b3cc0) Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleHDA(1.2.7a9)@0x3cb5f000
dependency: com.apple.iokit.IOHDAFamily(1.2.7a9)@0x3ca7f000
dependency: com.apple.iokit.IOAudioFamily(1.6.0b3)@0x3cb0f000
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
This time I was working in Logic Pro when it happened. Seeing as to how I was doing something different for every kernel panic and have already reinstalled the OS, changed RAM, and eliminated other third party issues, I'll be making a trip to the Apple store I bought it from.
What do you think the chances of them offering me a replacement vs. repair are? I really don't have time to wait for a repair to because I've got two projects to mix in Logic during my break. Plus, this is already the third laptop. Now I'm on to either a repair or a fourth one.
I've decided that I'm going to do one more clean install too (after calling the store and logging the problem) because I can't remember whether these panics started happening before or after my last clean install. That way, it will have already been taken care of when another panic occurs and I can get a replacement/repair happening tout de suite.
Here is a link to Apple's discussion boards on the kernel panics. Seems a lot of people are experiencing the problem. Many seem to feel it is airport/driver related.
Well, I did a complete erase and reinstall. The only things I carried over from the old system were my itunes library and assorted school documents via external backup.
It's been almost a week now (6 days, to be exact) with heavy Airport use, and I haven't seen any problems.
I called Applecare before doing the install to make sure that my problem had a case number, and the person I spoke with seemed to think that bad hardware, specifically bad RAM, would cause more frequent and regular panics. I kind of agree with that. Yes, I had 5 panics, which is too many, but that was over around 7 weeks time. It's very bizarre to me that there was obviously a problem, and yet the problem didn't manifest itself often enough to suggest major issues.
I'm inclined to think that it was in fact problems with the Airport driver (which has recently been updated), but I guess I'll have to wait a little longer before I'm totally satisfied. Thanks to all for your help.
It's been almost a week now (6 days, to be exact) with heavy Airport use, and I haven't seen any problems.
I called Applecare before doing the install to make sure that my problem had a case number, and the person I spoke with seemed to think that bad hardware, specifically bad RAM, would cause more frequent and regular panics. I kind of agree with that. Yes, I had 5 panics, which is too many, but that was over around 7 weeks time. It's very bizarre to me that there was obviously a problem, and yet the problem didn't manifest itself often enough to suggest major issues.
I'm inclined to think that it was in fact problems with the Airport driver (which has recently been updated), but I guess I'll have to wait a little longer before I'm totally satisfied. Thanks to all for your help.
If it happens again, take the machine back to Apple. Ask them to put it on an 'advanced diagnostics' (kind of like a very very very scary Apple Hardware Test which takes aaaaaaaages). That will pick up any issues which AHD might not.
I'd ask for a replacement if there are any issues, you don't want anything on-running...
I'd ask for a replacement if there are any issues, you don't want anything on-running...
Just had my first KP last night on a MBP 2.16 CD. I've had the laptop for about a week. It's a ReFurby, for what it's worth, with 2GB of Apple RAM. I was jacking around with playlists in iTunes while my iPod (60GB Video) was Updating. And my Logitech VX Revolution mouse was plugged in. The usual handful of apps were open.
Pisses me off, but...what can I do?
Pisses me off, but...what can I do?