Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

my first kernel panic - on my 3 week old MacBook

B

beethovengirl

macrumors regular
Original poster
Jan 15, 2004
150
1
Hi,

I just had my first kernel panic -- on my 3 week old MacBook. :( I just downloaded CoconutBattery last night. Do you think that could've caused this? To add insult to injury, I just called Apple, and Apple Care is already closed at 5:20 PST. Lame.

Here's the log. Does anyone have any suggestions on what may have caused this? thanks :)

panic(cpu 0 caller 0x001A7BED): Kernel trap at 0x0011fa0d, type 14=page fault, registers:
CR0: 0x80010033, CR2: 0x00000000, CR3: 0x0106b000, CR4: 0x00000660
EAX: 0x00000000, EBX: 0x03b96a78, ECX: 0x03000006, EDX: 0x00000450
CR2: 0x00000000, EBP: 0x21203d48, ESI: 0x06674c44, EDI: 0x00008000
EFL: 0x00010006, EIP: 0x0011fa0d, CS: 0x00000008, DS: 0x004e0010
Error code: 0x00000000

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x21203b68 : 0x12b0e1 (0x455670 0x21203b9c 0x133238 0x0)
0x21203bb8 : 0x1a7bed (0x45ea20 0x11fa0d 0xe 0x45e1d4)
0x21203c98 : 0x19e517 (0x21203cb0 0x206 0x21203d48 0x11fa0d)
0x21203ca8 : 0x11fa0d (0xe 0x48 0x2ab0010 0x2ab0010)
0x21203d48 : 0x12049d (0x8000 0x16d1438 0x5360c0 0x3b96a78)
0x21203d98 : 0x120d34 (0x6674c44 0x3000006 0x450 0x64)
0x21203df8 : 0x127206 (0x4122edc 0x3000006 0x450 0x0)
0x21203f08 : 0x196afc (0x21203f44 0x0 0x0 0x0)
0x21203fc8 : 0x19eb34 (0x3bd9640 0x0 0x10 0x0)
No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xbfffec98

BSD process name corresponding to current thread: Safari

Mac OS version:
9B18

Kernel version:
Darwin Kernel Version 9.1.0: Wed Oct 31 17:46:22 PDT 2007; root:xnu-1228.0.2~1/RELEASE_I386
System model name: MacBook3,1 (Mac-F22788C8)
 
Eidorian said:
I've noticed that Leopard's panic log has improved to help a user find a cause.
Click to expand...

How does that help? As far as I can tell, the log is only reporting that the panic occurred while the OS was processing a Safari thread. It doesn't mean Safari caused it.

As advice to the OP, I would say if it happens only this one time, don't worry about it.
 
Eidorian said:
I've noticed that Leopard's panic log has improved to help a user find a cause.
Click to expand...
That doesn't explain why I had the kernel panic. Could having insufficient RAM cause a kernel panic while having multiple windows open in Safari?

I'm planning to upgrade from 1 GB RAM to 4 GB RAM soon.
 
beethovengirl said:
Could having insufficient RAM cause a kernel panic while having multiple windows open in Safari?
Click to expand...
There's a chance that Safari didn't like how a web page was handled.

It's not the lack of RAM though. It'd be paged out if you were out of RAM. How many tabs/windows are you talking about?

Safari handles the 20-30 that I have open just fine.

I wouldn't worry unless it happens again.
 
Insufficient RAM won't give you a kernel panic. It'll just make things a little slower. I agree with old man IJ Reilly that you probably don't need to worry about a one-off.
 
2nd kernel panic :(

Just had my second kernel panic. Do you think I should return my MacBook? I never had one kernel panic for the 3.5+ years I owned my iBook G4.

Sat Dec 29 02:42:10 2007
panic(cpu 0 caller 0x001A7BED): Kernel trap at 0x0014042f, type 14=page fault, registers:
CR0: 0x80010033, CR2: 0x00000008, CR3: 0x0106b000, CR4: 0x00000660
EAX: 0x00000000, EBX: 0x00000000, ECX: 0x03b6d49c, EDX: 0x03b6d4a4
CR2: 0x00000008, EBP: 0x21077cc8, ESI: 0x04f9d7d4, EDI: 0x03b6d4a0
EFL: 0x00010002, EIP: 0x0014042f, CS: 0x00000008, DS: 0x03a70010
Error code: 0x00000000

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x21077ab8 : 0x12b0e1 (0x455670 0x21077aec 0x133238 0x0)
0x21077b08 : 0x1a7bed (0x45ea20 0x14042f 0xe 0x45e1d4)
0x21077be8 : 0x19e517 (0x21077c00 0x0 0x21077cc8 0x14042f)
0x21077bf8 : 0x14042f (0xe 0x21070048 0x14940010 0x10)
0x21077cc8 : 0x127e7e (0x3b6d49c 0x4f9d7d4 0x21077cf8 0x122aa8)
0x21077cf8 : 0x127fdd (0x4f9d7bc 0x3b6d460 0x400 0x1494c000)
0x21077d78 : 0x14cd05 (0x298d088 0x914b 0x5cf76ac 0x5cf76c0)
0x21077db8 : 0x12d165 (0x5d087a0 0x5cf7690 0x0 0x0)
0x21077df8 : 0x126247 (0x5d08700 0x0 0x24 0x21077ee4)
0x21077f08 : 0x196afc (0x21077f44 0x0 0x0 0x0)
0x21077fc8 : 0x19eb34 (0x2e78720 0x0 0x10 0x2e78720)
No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xb02207b8

BSD process name corresponding to current thread: LaunchCFMApp

Mac OS version:
9B18

Kernel version:
Darwin Kernel Version 9.1.0: Wed Oct 31 17:46:22 PDT 2007; root:xnu-1228.0.2~1/RELEASE_I386
System model name: MacBook3,1 (Mac-F22788C8)
 
no need to have coconutbattery. It is not compatible with Leopard as of now.
 
e12a said:
no need to have coconutbattery. It is not compatible with Leopard as of now.
Click to expand...

Yep, I'm starting to think CoconutBattery caused this. Other than deleting the application file for CoconutBattery, is there anything else that I need to do in order to make my computer forget I ever downloaded CB? Should I reformat my drive?

CB wasn't even open when the kernel panics happened.
 
e12a said:
no need to have coconutbattery. It is not compatible with Leopard as of now.
Click to expand...

I've been using it for some time now under Leopard, no Kernel Panics or any other issues to speak of. What doesn't work with it under Leopard?
 
mad jew said:
Insufficient RAM won't give you a kernel panic. It'll just make things a little slower. I agree with old man IJ Reilly that you probably don't need to worry about a one-off.
Click to expand...

Jut because I'm crotchety doesn't mean I'm an old man. ;)

beethovengirl said:
Just had my second kernel panic. Do you think I should return my MacBook? I never had one kernel panic for the 3.5+ years I owned my iBook G4.
Click to expand...

Now it's time to worry. The most likely cause is hardware. If I were you, I'd bring it back.
 
I have had 3 in 1 week with my MBP and I finally figured it out. For me it was the Logitech mouse and program that I was using. Went with a Mighty Mouse and my MBP has not crashed once in 6 months. On the flip side I have had 50+ with my dell using Vista.
 
IJ Reilly said:
Jut because I'm crotchety doesn't mean I'm an old man. ;)
Click to expand...


You're older than me! :p


IJ Reilly said:
Now it's time to worry. The most likely cause is hardware. If I were you, I'd bring it back.
Click to expand...


Yeah, I agree with this too. I'd eat my hat and my shoes if it was CoconutBattery causing this.


steve31 said:
I have had 3 in 1 week with my MBP and I finally figured it out. For me it was the Logitech mouse and program that I was using. Went with a Mighty Mouse and my MBP has not crashed once in 6 months. On the flip side I have had 50+ with my dell using Vista.
Click to expand...


There have been a lot of people having issues with the Logitech drivers.
 
Mechcozmo said:
I've been using it for some time now under Leopard, no Kernel Panics or any other issues to speak of. What doesn't work with it under Leopard?
Click to expand...

it doesnt report the correct # of cycles, nor the correct health (when compared with system profiler). I created a thread on this and it seems as if I am not the only one experiencing issues. No point in using it if it doesnt work. iStat widget still reports correct # of cycles and health.

to the OP, try doing an archive and install.
 
can't repair permissions

I called AppleCare [again, and this time I waited on hold for over 1.5 hrs :/ ], and the tech support guy had me reboot from the install DVD. I ran Disk Utility, which found the following problems:
Permissions differ on "System/Library/PrivateFrameworks/GraphicsAppSupport.framework/Versions/A/Frameworks/QuartzComposer.framework", should be lrwxr-xr-x , they are drwxr-xr-x .

Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAgent" has been modified and will not be repaired.

Permissions differ on "System/Library/PrivateFrameworks/GraphicsAppSupport.framework/Versions/A/Frameworks/ImageKit.framework", should be lrwxr-xr-x , they are drwxr-xr-x .

I repaired the permissions, but after verifying them again, they still showed as "differing." The tech support guy asked what 3rd party applications I downloaded, and he was suspicious of CoconutBattery and had me delete it. He said that if the problem with permissions had been created by Apple software, Disk Utility should've been able to repair it; therefore, it must've been CB's fault. I then asked him if we should repair the permissions again after I deleted CB, and he said I didn't need to. I found that odd, and after I got off the phone, I tried repairing and verifying the permissions again, and I'm getting the same error message.

I've been running Mail, Safari, Firefox, Preview, TextEdit, and MS Word 2004. I have not reset the PRAM or re-installed the OS. Should I try, or should I just return it?

thanks for all your help :)
 
Kernel panics are rarely caused by software, though sometimes third-party drivers can be to blame. Sadly I have found Apple's tech support to be generally clueless where these issues are concerned. Permission repairs are a wild goose chase. I don't know if they had you check for disk errors, though -- which is always a possible result of kernel panics, but not likely to be the initial cause. I still advise insisting on factory service.
 
IJ Reilly said:
Kernel panics are rarely caused by software, though sometimes third-party drivers can be to blame.
Click to expand...
I haven't downloaded any third-party drivers.

So, do you think I should just return it while I still can? Besides the 2 kernel panics, it also irks me that my computer has non-repairable permissions problems.

I got it from Amazon, so I actually have until 1/31 to return it.
 
Eidorian said:
It's probably time to try reinstalling the operating system then.
Click to expand...
I notice that you have the same MacBook. Do you have CoconutBattery installed? Did it "break" your permissions too?

So, these are my thoughts: I have until 1/31 to return it to Amazon. There is a restocking fee unless the MacBook is defective. If I return my MacBook with unrepairable "broken" permissions, I think I have a clear-cut case that the MB is defective. On the other hand, if I re-install the OS, I assume that automatically fixes the broken permissions...? And, if I continue to get kernel panics but no unrepairable "broken" permissions, I might have to pay a restocking fee. Or worse, I start getting kernel panics 5 weeks from now after which I can't return it. [it took 3 weeks for my first kernel panics]

hmm...
 
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