Sidebar Sidebar
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

M

mopppish

macrumors 6502
Original poster
Nov 27, 2005
356
1
The title says it all.
The first one happened when I plugged my printer into one of the USB ports while Safari was opening (mid-bounce).
The second one happened just now when I tried to open the Airport status bar menu while Sibelius (PPC app) was loading instruments.
Should I be concerned about this? I hate that this indicates something flaky about OSX/MBP.
 
I was getting kernel panics on my C2D Macbook Pro as well... I think i might have had 3 right off the bat within the first weeks.

Two of them occurred while I was working with Windows XP and Parallels trial software. I quickly decided I'd try Boot Camp instead!

The other time, the panic happened when I unplugged a Logitech USB keyboard.

I was a little antsy at the time, but decided I'd wait and see if it happened again before calling Apple. I removed Parallels, and haven't had any trouble since. My MBP is a stock 2.16 GHz model with the factory 1 GB RAM.
 
Max Payne said:
How do you know you get a kernel panic. Will the computer freeze?
Click to expand...

Oh, you'll know it. The screen will darken and this little baby will pop up.

106227_2.jpg
 
Yeah, I'm not that worried since both times it happened I was doing two things simultaneously that may very well have clashed. With the first one, the printer driver may not be all that solid (it wasn't included with Tiger- I had to download it from HP's site), and with the second one, I had a PPC app (Sibelius) doing some heavy lifting (setting up instrument sounds) while I tried to do something else.
I originally bought a Macbook that I exchanged for this MBP, so I actually initially bought 2 1GB sticks from DMS. I may put the other one in just to rule that out.
 
mopppish said:
Yeah, I'm not that worried since both times it happened I was doing two things simultaneously that may very well have clashed. With the first one, the printer driver may not be all that solid (it wasn't included with Tiger- I had to download it from HP's site), and with the second one, I had a PPC app (Sibelius) doing some heavy lifting (setting up instrument sounds) while I tried to do something else.
I originally bought a Macbook that I exchanged for this MBP, so I actually initially bought 2 1GB sticks from DMS. I may put the other one in just to rule that out.
Click to expand...

Software including printer drivers should be virtually incapable of bringing down the OS. In the vast majority of instances, kernel panics are caused by hardware issues, and more often than not, by bad RAM. Swapping out the RAM is a good idea. Either way don't ignore this problem and hope it goes away. Find the cause and fix it -- you will be a much happier Mac owner!
 
Actually, kernel panics may happen because of bad software. I remember that 10.3.8 had fired my G5's *ss for a few weeks with kernel panics. Shortly after, Apple released the 10.3.9 update, and I hadn't any problems ever since.
 
Yeah, this is one of the few times I don't quit agree with the wise yet pungent IJ Reilly. Although most kernel panics seem to stem from RAM, I reckon there are quite a few instances when it is caused by software. Hell, I remember a thread where a widget was causing kernel panics.

Having said that, I've also noticed a much greater amount of users having trouble with wrecked file systems in the new Intel machines. Of course, fsck cleans that right up, but it seems interesting that this once uncommon problem is now so popular. I don't know if it's the change to Intel or to SATA though, I'm guessing Intel.


Umm... What were we talking about?...
 
Soulstorm said:
Actually, kernel panics may happen because of bad software. I remember that 10.3.8 had fired my G5's *ss for a few weeks with kernel panics. Shortly after, Apple released the 10.3.9 update, and I hadn't any problems ever since.
Click to expand...

I would never say never, but software issues bad enough to bring down the OS rare enough to look just about everywhere else first.

mad jew said:
Yeah, this is one of the few times I don't quit agree with the wise yet pungent IJ Reilly. Although most kernel panics seem to stem from RAM, I reckon there are quite a few instances when it is caused by software. Hell, I remember a thread where a widget was causing kernel panics.
Click to expand...

Pungent, as in smells bad? :confused: :)
 
Yeah. I mean, I didn't wanna say anything, but yeah...


:p


The integration of hardware and software on Macs is pretty tight. I think that affects whether the software can bring the OS down or not.
 
I, too would get the occasional kernel panic on PPC hardware running 10.3.8.. but normally on startup.. maybe once every couple of weeks.

With the 10.3.9 update, the occasional panic was a thing of the past! Panic free since 8/23! (2006)

Any number of things can cause a panic, tho.. i'd make a note of what you were doing (or trying to do) at the time of the kernel panic, and see if you can identify a pattern.
 
Kernel Panics in OS X

I just got a new MBP about a week ago, and I've had 2 kernel panics since then. I've discussed them with a couple of developers because I was worried about data corruption, and I've learned that there is a really nasty crashing bug in 10.4.8. Apparently Apple knows about it, but it obviously isn't fixed yet. 10.3.9 was the most stable mac OS I can remember. I used to go several months between rebooting, and when I did reboot, it was because of an update that required a restart. I think the immediate strategy is to avoid being too aggressive about running lots of stuff, and reboot regularly, at least until 10.4.9 is released and, hopefully, fixes the problem.
 
Strange. I haven't had a single panic on the ten or so PPC Macs I have running 10.4.8. It must be Intel-specific because I've noticed more and more people complaining 'bout it.





IJ Reilly doesn't wash, pass it on.
 
Well, I got another one tonight.
I got home from using the MBP to record a recital, plopped on the couch, opened the MBP, grabbed a few french fries, tried to turn on airport from the menu bar, and BAM.
:mad:
 
Some people are good at reading kernel panic logs, which might help diagnose the issue -- but I'm going to go not very far out on a limb, and guess bad RAM is at fault.
 
puckhead193 said:
try reinstalling the OS... it happened to me and now everything is A-ok!
Click to expand...

A very small chance of fixing the problem, IMO. Based on my observations at least, the probability of any given kernel panic being hardware-related is somewhere on the order of 95%. In fact I think this is the first time I've ever heard of a kernel panic issue being fixed with a reinstallation.
 
Dammit!
It just happened again.
It did the "none of your trusted networks can be found, would you like to join this one?" thing.
I said "yes", which I've done many times before, including for this particular network, and up came the dark screen.
That's #4 since I got it.
I ran the Apple hardware test twice last week, and everything (including the RAM) turned out OK.
And I did a fresh install of the OS when I first got the machine.
Here's the console log from the last 2 panics:

Sun Dec 3 22:14:38 2006
panic(cpu 1 caller 0x001A3135): Unresolved kernel trap (CPU 1, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0x00000000, CR3: 0x01859000, CR4: 0x000006e0
EAX: 0x00000007, EBX: 0x240ac308, ECX: 0x00000000, EDX: 0x00000010
CR2: 0x00000000, EBP: 0x25acb688, ESI: 0x240acd98, EDI: 0x00000000
EFL: 0x00010202, EIP: 0x3c921d80, CS: 0x00000008, DS: 0x00000010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x25acb448 : 0x128d08 (0x3c9afc 0x25acb46c 0x131de5 0x0)
0x25acb488 : 0x1a3135 (0x3cf7b0 0x1 0xe 0x3cefe0)
0x25acb598 : 0x19a904 (0x25acb5b0 0x240ac308 0x25acb5e8 0x127e77)
0x25acb688 : 0x3c921f71 (0x240acd98 0x240ac308 0x25acb7e8 0x0)
0x25acb6a8 : 0x3c922231 (0x240be004 0xc0a00071 0x40 0x0)
0x25acb808 : 0x3c9324f1 (0x240ac308 0x1 0x25acb838 0x3bbd7c)
0x25acb858 : 0x42d2358e (0x240ac000 0x4456c00 0x25acb8ac 0x0)
0x25acbc98 : 0x399892 (0x240ac000 0xc 0x5638ec1 0x0)
0x25acbcd8 : 0x42d21e84 (0x49c9980 0x42d22aae 0xc 0x5638ec1)
0x25acbd18 : 0x3b0db0 (0x240ac000 0xc 0x5638ec1 0x0)
0x25acbd68 : 0x18a18e (0x4c57200 0x0 0x5638ec0 0x5)
0x25acbdb8 : 0x12b4c3 (0x5638e98 0x453756c 0x0 0x0)
0x25acbdf8 : 0x124b17 (0x5638e00 0x0 0x34 0x25acbedc)
0x25acbf08 : 0x1955a8 (0x25acbf44 0x0 0x0 0x0)
0x25acbfc8 : 0x19ad7e (0x4af4220 0x0 0x10 0x4af4ae0) No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xbfffe278
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AirPortAtheros(210.8)@0x3c8fe000
dependency: com.apple.iokit.IONetworkingFamily(1.5.1)@0x3be4d000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x35c4a000
dependency: com.apple.iokit.IO80211Family(140.4)@0x42d19000
com.apple.iokit.IO80211Family(140.4)@0x42d19000
dependency: com.apple.iokit.IONetworkingFamily(1.5.1)@0x3be4d000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x35c4a000

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


*********

Mon Dec 11 19:38:17 2006
panic(cpu 1 caller 0x001A3135): Unresolved kernel trap (CPU 1, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0x00000018, CR3: 0x00ee2000, CR4: 0x000006e0
EAX: 0x00000018, EBX: 0x00000000, ECX: 0x0000003b, EDX: 0x0000003b
CR2: 0x00000018, EBP: 0x25aeb2e8, ESI: 0x00000018, EDI: 0x2372d4fc
EFL: 0x00010202, EIP: 0x003bab8c, CS: 0x00000008, DS: 0x00000010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x25aeb0d8 : 0x128d08 (0x3c9afc 0x25aeb0fc 0x131de5 0x0)
0x25aeb118 : 0x1a3135 (0x3cf7b0 0x1 0xe 0x3cefe0)
0x25aeb228 : 0x19a904 (0x25aeb240 0x1 0x245b601c 0x2)
0x25aeb2e8 : 0x9acf18 (0x18 0x2372d6d4 0x25aeb318 0x37f0be)
0x25aeb318 : 0x9b2d81 (0x2372d4fc 0x4b5010 0x25aeb358 0x6)
0x25aeb388 : 0x9d5e43 (0x2372d4fc 0x0 0xffffffff 0x2)
0x25aeb4e8 : 0x9dcb04 (0x2372d4fc 0x0 0xffffffff 0x19d23a)
0x25aeb508 : 0x9dbcca (0x2372d000 0x3ecce00 0x12d9d0f 0x4)
0x25aeb698 : 0x99587f (0x2372d000 0x3ecce00 0x25aeb6bc 0x1c)
0x25aeb858 : 0x9964fc (0x2372d000 0x3ecce00 0x25aebd0c 0x5ab0b6d)
0x25aebc98 : 0x399892 (0x2372d000 0x11 0x5ab0b6d 0x0)
0x25aebcd8 : 0x994e84 (0x3e978c0 0x995aae 0x11 0x5ab0b6d)
0x25aebd18 : 0x3b0db0 (0x2372d000 0x11 0x5ab0b6d 0x0)
0x25aebd68 : 0x18a18e (0x58ce100 0x0 0x5ab0b6c 0x59)
0x25aebdb8 : 0x12b4c3 (0x5ab0b44 0x5a3c56c 0x0 0x0)
0x25aebdf8 : 0x124b17 (0x5ab0b00 0x0 0x88 0x25aebedc) Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AirPortAtheros(210.8)@0x9a8000
dependency: com.apple.iokit.IONetworkingFamily(1.5.1)@0x6bc000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x580000
dependency: com.apple.iokit.IO80211Family(140.4)@0x98c000
com.apple.iokit.IO80211Family(140.4)@0x98c000
dependency: com.apple.iokit.IONetworkingFamily(1.5.1)@0x6bc000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x580000

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


*********
Any idears?
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back