Frequent Kernal Panics

[TVilleHockey41]

Hey,

I'm a newer mac user, loving the experience so far but I'm having a problem. It seems like every few days or so my Macbook has a Kernal Panic. The first few times I thought it would be a non-issue, but now I'm getting concerned. I have the error log for you all to look at. Any help is appreciated!

Wed Dec 24 22:06:54 2008
Panic(CPU 1): Unresponsive processor
EAX: 0x0298799b, EBX: 0x00000001, ECX: 0x00000001, EDX: 0x02987992
CR2: 0x00032000, EBP: 0x34b1beb8, ESI: 0x02987990, EDI: 0x00000000
EFL: 0x00000082, EIP: 0x0019ba2d, CS: 0x00000008, DS: 0x17560010
Backtrace (CPU 1), Frame : Return Address (4 potential args on stack)
0x2e5d8f78 : 0x1af6bd (0x34b1be00 0x2e57a000 0x2e5d8fa8 0x6)
0x2e5d8f98 : 0x449c0e (0x2 0x34b1be00 0x4eb6d60 0x1)
0x2e5d8fd8 : 0x1a0551 (0x34b1be00 0x0 0x131cfb 0x2e57a000)
0x34b1beb8 : 0x19f16f (0x540c40 0x20 0xbfe00000 0x51c740)
0x34b1bef8 : 0x17c84b (0x2987990 0x3e53ea0 0x34b1bf18 0x2e565038)
0x34b1bf98 : 0x17d1a7 (0xc5 0x50ba18 0x3fc1e44 0x0)
0x34b1bfc8 : 0x1a017c (0x0 0x0 0x1a30b5 0x3d38280)
Backtrace terminated-invalid frame pointer 0

BSD process name corresponding to current thread: kernel_task

Mac OS version:
9G55

Kernel version:
Darwin Kernel Version 9.6.0: Mon Nov 24 17:37:00 PST 2008; root:xnu-1228.9.59~1/RELEASE_I386
System model name: MacBook4,1 (Mac-F22788A9)
panic(cpu 0 caller 0x00193CE7): "pmap_flush_tlbs() timeout: " "cpu(s) failing to respond to interrupts, pmap=0x53a600 cpus_to_respond=0x2"@/SourceCache/xnu/xnu-1228.9.59/osfmk/i386/pmap.c:4582
Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)
0x34ab7548 : 0x12b4f3 (0x45b13c 0x34ab757c 0x1335e4 0x0)
0x34ab7598 : 0x193ce7 (0x46126c 0x53a600 0x2 0x53a61c)
0x34ab7608 : 0x194e7b (0x53a600 0x509ac000 0x0 0x34ab7618)
0x34ab76a8 : 0x174a17 (0x52228 0x0 0x0 0x7)
0x34ab7748 : 0x16a4bb (0x5c99b7c 0x0 0x0 0x97000)
0x34ab7868 : 0x16aab8 (0x50a43000 0x0 0x0 0x0)
0x34ab78a8 : 0x182fe0 (0x420d554 0x509ac000 0x0 0x50a43000)
0x34ab7908 : 0x42ee04 (0x420d554 0x509ac000 0x0 0x97000)
0x34ab7968 : 0x42ee68 (0x642e580 0x171bf80 0x45a32c0 0x0)
0x34ab7988 : 0x42ef59 (0x45a32c0 0xe 0x0 0x0)
0x34ab79a8 : 0x42ef30 (0x45a32c0 0x0 0x2 0x1a0190)
0x34ab79c8 : 0x3ece8f (0x45a32c0 0x0 0x10292 0x0)
0x34ab79e8 : 0x6b7f8b (0x45a32c0 0x3d2ee18 0x0 0x1)
0x34ab7a48 : 0x6bc055 (0x6583c00 0x3dd5000 0x0 0x0)
0x34ab7b58 : 0x6b8cce (0x6583c00 0x5111e048 0x34ab7b98 0x698f99)
0x34ab7b98 : 0x69a9f9 (0x6583c00 0x34ab7c60 0x907 0x23d81090)
Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleIntelGMAX3100(5.3.6)@0x691000->0x75bfff
dependency: com.apple.iokit.IONDRVSupport(1.7.1)@0x683000
dependency: com.apple.iokit.IOPCIFamily(2.5)@0x596000
dependency: com.apple.iokit.IOGraphicsFamily(1.7.1)@0x5aa000

BSD process name corresponding to current thread: Skype

 

[r.j.s]

Call Apple, looks like something is wrong with one of your processors.

 

[Cave Man]

Nothing to do with the processor (he only has one). The issue is software related, probably Safari. It's really a hog - and seems to be getting worse. Try using Firefox (without using Safari) for a few days and see if that resolves the issue.

 

[TVilleHockey41]

I always use Firefox. I used it prior to owning a mac, and still do.

 

[Cave Man]

The only other app that routinely gives me kernel panic issues is Aperture. Have you tried booting from the Installer DVD and using Disk Utility to Repair the hard drive?

I also seem to be experiencing more kernel panics on my MBP since "upgrading" to 10.5.6. Also, how is your processor temperature when these panics occur?

 

[maccam]

You better call Apple and send it in. If you have AppleCare use your "Tech Tool CD" it will tell you what's wrong.

 

[Digital Skunk]

Anybody find an answer or got any other suggestions to this?

I have one of my 17" MBPs on the fritz now, and did a complete reinstall of OSX Leopard and I have still been getting a KP every ten minutes or so.

Been doing it before I had any 3rd party software installed, just the OS and iLife.

 

[Rocksaurus]

Kernel panics are (almost) always hardware issues. To the OP - back up all your files, reformat your hard drive and reinstall your OS. Run it like Digital Skunk on just stock software. If you continue to get kernel panics this reflects that the problem is hardware based and that you need to contact apple.

Also of note if you're using any third party hardware (RAM, PC/PCI Cards etc.) try taking these things out and uninstalling their drivers and seeing if that solves the problem. You need to be able to isolate what is causing the problem, so systematically remove variables from the equation to do so.

 

[IJ Reilly]

Kernel panics are (almost) always hardware issues. To the OP - back up all your files, reformat your hard drive and reinstall your OS. Run it like Digital Skunk on just stock software. If you continue to get kernel panics this reflects that the problem is hardware based and that you need to contact apple.

Also of note if you're using any third party hardware (RAM, PC/PCI Cards etc.) try taking these things out and uninstalling their drivers and seeing if that solves the problem. You need to be able to isolate what is causing the problem, so systematically remove variables from the equation to do so.

Right diagnosis, backwards repair procedure. Since kernel panics (especially chronic ones) are virtually always hardware-related, reinstalling OSX almost never helps, and can even make the situation worse. Try the hardware solutions first, particularly removing any RAM you might have added. Reinstalling the OS is the very last thing to try, but only after all hardware causes are eliminated.

 

[Digital Skunk]

Right diagnosis, backwards repair procedure. Since kernel panics (especially chronic ones) are virtually always hardware-related, reinstalling OSX almost never helps, and can even make the situation worse. Try the hardware solutions first, particularly removing any RAM you might have added. Reinstalling the OS is the very last thing to try, but only after all hardware causes are eliminated.

I think you are right, in that the OSX reinstall fixed nothing, but upon replacing the RAM, and listening to another much older Mac head, the KPs seem to have stopped for now.

I haven't had one for about an hour or so, the the book is finally updating 10.5.2 to 10.5.6 which it would never finish before after three attempts. I am starting to think the guy I bought it from didn't put the chips in correctly. Luckily I had 2GB lying around from my other MBP upgrade.

 

[mperkins37]

My experience is that it is usually a ram or logic board problem also.
It is rarely a software problem, if never.
The culprit is usually the presence of bad or malfunctioning ram.
I have had 2 logic boards do this also.
I usually pull all ram & insert 1 at a time till the culprit is isolated.

 

[Digital Skunk]

My experience is that it is usually a ram or logic board problem also.
It is rarely a software problem, if never.
The culprit is usually the presence of bad or malfunctioning ram.
I have had 2 logic boards do this also.
I usually pull all ram & insert 1 at a time till the culprit is isolated.

This seems to be the case as of now. Almost a full day of operation and no KP whatsoever.

 

[Rocksaurus]

Right diagnosis, backwards repair procedure. Since kernel panics (especially chronic ones) are virtually always hardware-related, reinstalling OSX almost never helps, and can even make the situation worse. Try the hardware solutions first, particularly removing any RAM you might have added. Reinstalling the OS is the very last thing to try, but only after all hardware causes are eliminated.

I typically tell people to backup/reinstall first because a) the first thing they need to do regardless is backup their data and b) many people aren't comfortable opening up their computers and if the reinstall doesn't fix it (which it almost never does) will just take it to Apple anyways.

 

[IJ Reilly]

I typically tell people to backup/reinstall first because a) the first thing they need to do regardless is backup their data and b) many people aren't comfortable opening up their computers and if the reinstall doesn't fix it (which it almost never does) will just take it to Apple anyways.

Backup, absolutely. Reinstall, almost never -- if for no other reason than they can easily make their problem worse, and diagnosing the issue can often be as easy as removing RAM. We see a lot of that around here. Even if the Mac ends up with a bad motherboard, how much better off will they be if they've already nuked their hard drive?

 

[rbagwell]

Similar Problem

I've had two kernel panics on my macbook pro in the last three days. I was on the internet (but not downloading or installing anything) both times. I have no extra RAM or anything. Here's the info:

Mon Feb 2 16:39:27 2009
panic(cpu 0 caller 0x0035E7EC): mbuf address out of range 0x1ddd00
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x25833b38 : 0x128d0d (0x3cc65c 0x25833b5c 0x131f95 0x0)
0x25833b78 : 0x35e7ec (0x3ed584 0x1ddd00 0x25833b98 0x19e23a)
0x25833bc8 : 0x34d6ba (0x25833bfc 0x602 0x0 0x1)
0x25833c08 : 0x69f3b3 (0x1 0x602 0x0 0x25833c3c)
0x25833c58 : 0x69f6cf (0x0 0x297 0x25833e48 0x22bb20)
0x25833c88 : 0xbc422e (0x3f53000 0x4098884 0x5ea 0x25833cff)
0x25833ca8 : 0xb96457 (0x23ec8000 0x0 0x4098884 0x5ea)
0x25833d68 : 0xb96d13 (0x23ec8000 0x0 0x5ea 0x5ea0100)
0x25833df8 : 0xb971ff (0x23ec8000 0x1 0x25833e48 0x22f8b2)
0x25833e88 : 0xbc6b0d (0x23ec8000 0x3fb3400 0x40000000 0x0)
0x25833f08 : 0x39b96f (0x23ec8000 0x3fb3400 0x1 0x4008988)
0x25833f58 : 0x39ab41 (0x3fb3400 0x136064 0x0 0x4008988)
0x25833f88 : 0x39a877 (0x3fc0640 0x0 0x25833fc8 0x2052e5)
0x25833fc8 : 0x19b21c (0x3fc0640 0x0 0x19e0b5 0x497c6c8) Backtrace terminated-invalid frame pointer 0x0
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.AppleYukon2(3.1.3b3)@0xb92000
dependency: com.apple.iokit.IONetworkingFamily(1.5.1)@0x698000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x5fa000
com.apple.iokit.IONetworkingFamily(1.5.1)@0x698000

Kernel version:
Darwin Kernel Version 8.11.1: Wed Oct 10 18:23:28 PDT 2007; root:xnu-792.25.20~1/RELEASE_I386


*********

Wed Feb 4 15:10:37 2009
panic(cpu 0 caller 0x001A49CB): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0x0c000609, CR3: 0x0131e000, CR4: 0x000006e0
EAX: 0x0c000601, EBX: 0x00000060, ECX: 0x00000060, EDX: 0x0c000601
CR2: 0x0c000609, EBP: 0x2593ba58, ESI: 0x374b6a00, EDI: 0x00000004
EFL: 0x00010202, EIP: 0x0035c436, CS: 0x00000008, DS: 0x004b0010

Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x2593b848 : 0x128d0d (0x3cc65c 0x2593b86c 0x131f95 0x0)
0x2593b888 : 0x1a49cb (0x3d2a94 0x0 0xe 0x3d22b8)
0x2593b998 : 0x19b3a4 (0x2593b9b0 0x0 0x2593b9c8 0x1a3736)
0x2593ba58 : 0xdf6eb5 (0x374b6a00 0xfffffffc 0x0 0x55f24a30)
0x2593bc58 : 0xdfc038 (0x23ef0004 0x2593bdbc 0x2593bc88 0x1a3736)
0x2593bdd8 : 0xdfd665 (0x23d632cc 0x3e8c06c 0x4bc800 0x3e8c06c)
0x2593bf08 : 0x39b96f (0x23d63000 0x43e8d00 0x1 0x3e8c06c)
0x2593bf58 : 0x39ab41 (0x43e8d00 0x136064 0x0 0x3e8c06c)
0x2593bf88 : 0x39a877 (0x43fdb40 0x43fdb40 0x450 0x1203)
0x2593bfc8 : 0x19b21c (0x43fdb40 0x0 0x19e0b5 0x4c14d90) Backtrace terminated-invalid frame pointer 0x0
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AirPort.Atheros(244.44.0)@0xdc5000
dependency: com.apple.iokit.IONetworkingFamily(1.5.1)@0x698000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x5fa000
dependency: com.apple.iokit.IO80211Family(163.1)@0xa7d000

Kernel version:
Darwin Kernel Version 8.11.1: Wed Oct 10 18:23:28 PDT 2007; root:xnu-792.25.20~1/RELEASE_I386


*********

What's going on? What do I do?

 

[TVilleHockey41]

I've been having more and more frequent kernel panics these days. It seems like I get at least one per day now. So far today, I've had three. I'm really unsure what to do at this point, so any help would be appreciated. I've got most of the error reports saved from the past few days if anyone wants to take a peek at them.

I also find my computer beach balling more and more too. I remember it never used to do it, but now it seems whenever I open a program, or even a webpage it beachballs for a few seconds then opens it. Any suggestions for this?

Thanks so much.
Derek

 

[r.j.s]

Since they are getting more frequent, it may be the hard drive dying ... I'd make sure you have an up-to-date backup before doing much else.

If the warranty is still good, call Apple or take it to an Apple store. KPs are usually hardware related, and they're in the best position to tell you exactly what is going wrong.