Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Kernel Panics on New MacBook

I have a new MacBook (the black one) running 10.4.10, and have had 3 kernel panics today. Can someone with more knowledge on these issues than me give me some suggestions?

Thanks

jackholexxxx

Sat Jun 23 11:06:00 2007
panic(cpu 0 caller 0x001A4A55): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0xd279a033, CR3: 0x01ec1000, CR4: 0x000006e0
EAX: 0xd279a003, EBX: 0x80000003, ECX: 0x61ffd980, EDX: 0x0f859300
CR2: 0xd279a033, EBP: 0x37513bf8, ESI: 0x61ff3300, EDI: 0x35bdb2c8
EFL: 0x00010202, EIP: 0x009d1974, CS: 0x00000008, DS: 0x00000010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x375139b8 : 0x128d08 (0x3cc0a4 0x375139dc 0x131de5 0x0)
0x375139f8 : 0x1a4a55 (0x3d24b8 0x0 0xe 0x3d1cdc)
0x37513b08 : 0x19aeb4 (0x37513b20 0x49293400 0x1 0x1)
0x37513bf8 : 0x9aacc2 (0x35bde004 0x61ff3300 0xf859300 0xd279a003)
0x37513dd8 : 0x9ad059 (0x35bdb2c8 0x3d766a0 0x37513f48 0x0)
0x37513f08 : 0x39b3c3 (0x35bdb000 0x6098980 0x1 0x5bf7fe4)
0x37513f58 : 0x39a595 (0x6098980 0x2 0x37513f78 0x4b2038)
0x37513f88 : 0x39a2cb (0x6092500 0x6ab0894 0x15c57000 0xffffffff)
0x37513fc8 : 0x19ad2c (0x6092500 0x0 0x10 0x664a2e0) Backtrace terminated-invalid frame pointer 0x0
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AirPort.Atheros(230.8.5)@0x979000
dependency: com.apple.iokit.IONetworkingFamily(1.5.1)@0x7c4000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x577000
dependency: com.apple.iokit.IO80211Family(160.2)@0x7da000

Kernel version:
Darwin Kernel Version 8.10.1: Wed May 23 16:33:00 PDT 2007; root:xnu-792.22.5~1/RELEASE_I386


*******

Sat Jun 23 11:41:08 2007
panic(cpu 0 caller 0x001A4A55): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0xfffffe0b, CR3: 0x01ec1000, CR4: 0x000006e0
EAX: 0x00000006, EBX: 0x35da5107, ECX: 0xfffffe0b, EDX: 0x35a4ca5c
CR2: 0xfffffe0b, EBP: 0x374cbbf8, ESI: 0xfffffe11, EDI: 0x35a4c2c8
EFL: 0x00010206, EIP: 0x00198d64, CS: 0x00000008, DS: 0x00000010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x374cb9f8 : 0x128d08 (0x3cc0a4 0x374cba1c 0x131de5 0x0)
0x374cba38 : 0x1a4a55 (0x3d24b8 0x0 0xe 0x3d1cdc)
0x374cbb48 : 0x19aeb4 (0x374cbb60 0x3e8 0x374cbb98 0x9c7df5)
0x374cbbf8 : 0x9aae1e (0xfffffe0b 0x35da5107 0x6 0x62008850)
0x374cbdd8 : 0x9ad059 (0x35a4c2c8 0x1 0x4b285c 0x6)
0x374cbf08 : 0x39b3c3 (0x35a4c000 0x6082980 0x1 0x5bf1000)
0x374cbf58 : 0x39a595 (0x6082980 0x135eb4 0x0 0x5bf1000)
0x374cbf88 : 0x39a2cb (0x6085680 0x0 0x1036258 0x13818b)
0x374cbfc8 : 0x19ad2c (0x6085680 0x0 0x19e0b5 0x656d6ac) Backtrace terminated-invalid frame pointer 0x0
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AirPort.Atheros(230.8.5)@0x979000
dependency: com.apple.iokit.IONetworkingFamily(1.5.1)@0x7c4000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x577000
dependency: com.apple.iokit.IO80211Family(160.2)@0x7da000

Kernel version:
Darwin Kernel Version 8.10.1: Wed May 23 16:33:00 PDT 2007; root:xnu-792.22.5~1/RELEASE_I386


*******

Sat Jun 23 20:57:53 2007
panic(cpu 0 caller 0x0035DC60): mbuf address out of range 0xc9ed1fe4
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x3762bab8 : 0x128d08 (0x3cc0a4 0x3762badc 0x131de5 0x0)
0x3762baf8 : 0x35dc60 (0x3ecf78 0xc9ed1fe4 0x3762bb18 0x35afc4c0)
0x3762bb48 : 0x35dfe3 (0x3762bb7c 0x1 0x1 0x1)
0x3762bb88 : 0x34c765 (0x1 0x35afd758 0x3762bbb8 0xa261f4)
0x3762bba8 : 0xa476f6 (0x1 0x3762bbdc 0x3762bbf8 0xa28f79)
0x3762bbf8 : 0xa5793f (0x6265ee0 0x49389800 0x37 0x27808027)
0x3762bdd8 : 0xa59059 (0x35afc2c8 0x1 0x4b285c 0x6)
0x3762bf08 : 0x39b3c3 (0x35afc000 0x613d400 0x1 0x5ca3254)
0x3762bf58 : 0x39a595 (0x613d400 0x135eb4 0x0 0x5ca3254)
0x3762bf88 : 0x39a2cb (0x6146dc0 0x3c 0x0 0x0)
0x3762bfc8 : 0x19ad2c (0x6146dc0 0x0 0x19e0b5 0x672d624) Backtrace terminated-invalid frame pointer 0x0
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AirPort.Atheros(230.8.5)@0xa25000
dependency: com.apple.iokit.IONetworkingFamily(1.5.1)@0x731000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x5f3000
dependency: com.apple.iokit.IO80211Family(160.2)@0x837000

Kernel version:
Darwin Kernel Version 8.10.1: Wed May 23 16:33:00 PDT 2007; root:xnu-792.22.5~1/RELEASE_I386

Mac Pro 2.66 Mac OS X (10.4.9)

MacBook 2.16 Mac OS X (10.4.10)

Posted on Jun 23, 2007 9:14 PM

Reply
30 replies

Jul 15, 2007 4:31 PM in response to Krav

The majority of the reports of problems like this started with the 10.4.10 update; it's probably fair to say it's a problem with that update, and possibly related to some specific hardware versions, since not all MacBooks suffer from it.

It's unfortunate if you're so new to Mac that this dominates your first impression, but, in fact, such screwups are quite unusual. I've been using Macs (PowerBook, mini, Quad G5, MacBook, MacBook Pro) exclusively for the past few years, and have never had any trouble with any updates. I've used about every OS X version since 10.3.3, and have often installed them immediately upon their release.

So, if you can, stick with it. Apple will probably straighten this out, then you can go on to a long and happy relationship with Macs and OS X. If you're like most users, you'll come to believe it's way better than any of the alternatives.

MacBook 2.0GhzCore2Duo, 2.Gig, 160G HD, PowerBook G4 1.5Ghz 15" Mac OS X (10.4.10) Logic Pro 7.2.3, Focusrite Saffire...

Jul 25, 2007 9:17 PM in response to jackholexxxx

Been having the same problem. Brand new Macbook. Only a week old. Upon starting up the machine, I installed 10.4.10 right away. I didn't notice any problems the first 3 days because I was at home, often connected to AC power.

Then I took the laptop over my friend's apartment. Got the grey screen of death. Total panic set in.

Next day, brought it to work. Another grey screen of death.

Both times this occured, I was connected to a network using Airport and running off the battery. As we speak, I am back at my friend's apartment and have been using the WiFi connection without a hitch for several hours...but probably only because I'm tethered to an AC connection.

Every discussion forum I've gone to mentions the Aiport/battery problem. I hope it's only that and sincerely hope it's fixable in a patch...and soon. This is ridiculous.

Jul 26, 2007 5:05 AM in response to Operator No. 9

Hey Man, I would seriously consider going to the Apple Store and have them install 10.4.8 back on your machine if you don't think that you can do it. Then do the updates to get to 10.4.9. It really has been a godsend for me. I was having the same exact problems with my two month old MacBook. Last night I was unconnected from the AC for about 2 hours with no problems.

Jul 29, 2007 10:05 AM in response to jackholexxxx

I have one of the original MacBooks and I have not been impressed at all with it considering its my third mac that I have bought. Its also the only mac I have owned which has ever had any problems.

It now suffers from a perpetual loop of crashes which started with jsut a couple of kernal panic crashes every other day. This first started a few weeks back. Now it will not start up properly at all and alternates on boot ups between the grey screen which tells you to re-boot, to a black page which is listed below.

So - having done some searching and seeing just how many people have this problem - IS THIS A MAC VIRUS?

For over 2 days now I can not get further than the "you need to re-start your computer. etc " or occasionally the black page listing below.

I thought macs didn't do this sort of thing?



panic(cpu 0 caller 0x00190BBC); pmap-remove: mapping not in pv-list!
Debugger called: <panic>
Backtrace, Format - Frame : Return Address (4 potential arts on stack)
0x1407bc18 : 0x128d08 (0x3cc0a4 0x1407bc3c 0x131de5 0x0)
0x1407bc58 : 0x190bbc (0x3cf290 0x8fe00000 0x0 0x1a37c0)
0x1407bcb8 : 0x193c43 (0xdc2000 0xdc2258 0x0 0x19a986)
0x1407bd08 : 0x16535c (0x2600984 0x8fe00000 0x0 0x8fe4b000)
0x1407bdf8 : 0x165b10 (0xffe00000 0x0 0x0 0x0)
0x1407be38 : 0x13a676 (0x14165dc 0x0 0x0 0xffe00000)
0x1407be88 : 0x33b493 (0x25fe2a0 0x0 0x1407bee8 0x25fe2a0)
0x1407bec8 : 0x345947 (0x2c3f000 0xb 0x0 0x0)
0x1407bee8 : 0x346072 (0x2c3f000 0xb 0x0 0x0)
0x1407bf58 : 0x346258 (0xb 0x1 0x1407bf78 0x240f9038)
0x1407bf78 : 0x1273f9 (0x2615160 0xffffff7f 0x0 0x6)
0x1407bfa8 : 0x1a373d (0xffffffff 0x1 0x19add5 0x260da80)
0x1407bfc8 : 0x19ae16 (0x0 0x0 0x10 0x260da80) Backtrace terminated-invalid frame pointer 0x1407bef8

Kernel version:
Darwin Kernel Version 8.10.1: Wed May 23 16:33:00 PDT 2007; root:xnu-792.22.5~1/RELEASE_I386

Jul 30, 2007 8:33 AM in response to jackholexxxx

i am new to macs. everything was going well until i installed 2 gigs of ram. now i get the kernal panics and it takes me about 10-15 minutes just to get the mac started and able to go online. when i do start it the screen will flash and shut down then i have to press the power again. would the 2 gigs be related to the problem with my wireless? my brother made fun of me for getting a mac and as soon as he saw this problem he made fun of me even more. i do notice that the problem gets worse when i am on battery. can some one tell me how to uninstall 10.4.10 and reinstall 10.4.9?


thank you so much for any help, i know mac people have a tendency to help each other out and i also need to show my brother up


pat

Jul 30, 2007 9:11 AM in response to patman948

Overall, memory is usually the #1 cause of kernel panics, especially immediately after installing new memory.

Memory might be defective, or incompatible, or simply not firmly inserted in the sockets.

What I'd do - reseat memory, turn OFF airport, and test thoroughly. Download 'rember', a memory tester. Run the standalone 'memtestx', run Apple Hardware Test.

Once the memory is verified, you're stuck with the airport problems affecting many other 10.4.10 users.

Jul 30, 2007 10:47 AM in response to patman948

go here to do either a clean install or an archive and install, whichever suits your needs.

http://docs.info.apple.com/article.html?path=Mac/10.4/en/mh1103.html

I sympathize with all of you. I've got a pre-SR MBP and have had the lost connections, kernel panics on battery power, et al. It ain't no fun for new mac users.

I reverted back to 10.4.9 and it did help but I eventually got another KP after about a week or so. On my fourth call to AppleCare I finally got escalated to Level Two when I told them I had gotten a KP on 10.4.9 and the panic log clearly indicated airport. They had me send them my computer and they replaced the main logic board and apparently they also replaced the airport card. When i got the computer back the airport card firmware had reverted to an earlier version than what was on the machine originally. So, I do think the airport firmware plays a big role in the issue and I'm sure it's related to the new wireless N standard.

I've had my machine back for close to two weeks now and have NOT had another another KP yet. Keeping my fingers crossed and staying away from 10.4.10.

jim

Message was edited by: jmitro

Jul 30, 2007 1:08 PM in response to jackholexxxx

I bought my macbook 3 weeks ago. I had two times this kernel panic window. I phoned to aftersales, they told me it was hardware problem, and because I had this machine for less than 2 weeks, I immediately would get a new one. I'm typing right now on this new one in this forum cause I had this SAME problem allready twice today ! Jezus, "Hi I'm a MAC and I'm a PC ...". I watched them many times cause they're so funny, but it's not funny at all anymore.

Is it because of bootcamp (I need windows for software like autocad) ? Is it because only 1G of RAM when I had following applications open at same time: mail, safari, adresbook, iphoto, iweb ???

Little bit disillusioned in Apple ... :o((( My PC's (have 2) NEVER crash ... :o(((

johnnybaccus

Kernel Panics on New MacBook

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.