Re-ocurring Kernel Panic

Discussion in 'MacBook' started by Mr.Kernel, Nov 18, 2011.

  1. Mr.Kernel macrumors newbie

    Nov 18, 2011
    Hey I'm new to the forum and would love to know how to fix a re-ocuring kernel panic that keeps on coming up. At first I thought it was gonna go away since the first times they were within a 3 month span of each other. But latly I have been getting them rather often and don't have the money or resources to get to, and afford a trip to an Apple store.

    I have a 2010 Macbook(13inch), dual core 2.4Ghz,2 Gb DDR3 Ram, and hard-drive is the smallest(yet not taken up at all, maybe 5Gb used).I do play League of Legends, and some basic games(league being the highest that I have ever played), yet it always works fine, and I have a macro pad from logitech saying I have 2Gb of ram, usually only using 1.5Gb for the games(once again at max).

    The kernel panic always happens when I have at least 3 programs open and for some reason am moving it. Like, Ill have my virtual Box(for WinXp, with less than 50% of my dual core running it, and only 312 mb of ram) my text editor up, and usually Firefox with about 4-5 tabs open, I have to go somewhere so I close my macbook, I open it and the screen won't light. then when it does it does, but about 50% of the time I get a Kernel panic upon opening. Or the screen won't light at all but I can see that there is a kernel panic. Today two within 30 minutes of each other happened while moving from place to place.

    The code was this:

    Interval Since Last Panic Report: 788433 sec
    Panics Since Last Report: 2
    Anonymous UUID: D863CF94-3017-4ECC-8101-A09D7A5401DB

    Fri Nov 18 11:01:27 2011
    panic(cpu 0 caller 0x2aab55): Kernel trap at 0x00e186bb, type 0=divide error, registers:
    CR0: 0x8001003b, CR2: 0x00128000, CR3: 0x00100000, CR4: 0x00000668
    EAX: 0xffff96e2, EBX: 0x0000004e, ECX: 0x00000000, EDX: 0x00000000
    CR2: 0x00128000, EBP: 0x31b4bdb8, ESI: 0x00000034, EDI: 0x071dad98
    EFL: 0x00010246, EIP: 0x00e186bb, CS: 0x00000008, DS: 0x00000010
    Error code: 0x00000000

    Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)
    0x31b4bb88 : 0x21b50c (0x5d4438 0x31b4bbbc 0x223974 0x0)
    0x31b4bbd8 : 0x2aab55 (0x59623c 0xe186bb 0x0 0x59634a)
    0x31b4bcb8 : 0x2a09a8 (0x31b4bcd0 0xe40b04 0x31b4bdb8 0xe186bb)
    0x31b4bcc8 : 0xe186bb (0xe 0x48 0x10 0x10)
    0x31b4bdb8 : 0xdef88d (0x552cd00 0x71da800 0x31b4beb0 0x3)
    0x31b4be68 : 0xe3bd77 (0x211b1000 0x31b4beb0 0x58 0x226d68)
    0x31b4bed8 : 0xd79cac (0x211b1000 0x0 0x28000 0x5427b7c)
    0x31b4bf08 : 0x54c5ab (0x5518400 0x5530e40 0x1 0x29f54e)
    0x31b4bf58 : 0x54b5dc (0x5530e40 0x6cd67a8 0x31b4bfa8 0x219159)
    0x31b4bf88 : 0x54ba36 (0x551cb40 0x6cd67a8 0x52 0xffffffff)
    0x31b4bfc8 : 0x2a06cc (0x551cb40 0x0 0x10 0x6b199e0)
    Kernel Extensions in backtrace (with dependencies):>0xee0fff

    BSD process name corresponding to current thread: kernel_task

    Mac OS version:

    Kernel version:
    Darwin Kernel Version 10.6.0: Wed Nov 10 18:13:17 PST 2010; root:xnu-1504.9.26~3/RELEASE_I386
    System model name: MacBook7,1 (Mac-F22C89C8)

    System uptime in nanoseconds: 44154365873
    unloaded kexts:
    loaded kexts:
    org.virtualbox.kext.VBoxNetAdp 4.0.0 - last loaded 36665743685
    org.virtualbox.kext.VBoxNetFlt 4.0.0
    org.virtualbox.kext.VBoxUSB 4.0.0
    org.virtualbox.kext.VBoxDrv 4.0.0
    com.driver.LogJoystick 2.0 1.9.3d0 100.12.19 1.0.2d2 2.6.2 1.2.0 3.4.5 1.0.17 1.9.9f12 1.9.9f12 2.8.68 170.0.34 3.0.0d4 2.1.0 1.13 14 17 11 19 4.5.0d5 7.0.0 1.1.6 1.4.12 6.2.6 200.3.2 200.3.2 200.3.2 2.6.5 160.0.0 426.36.1 31 1.0.0d1 1.6.3 1.5 2.1.5 2.0.15 4.1.7 4.1.7 4.1.5 1.4.0 1.3.1 1.3.5 1.6 1.3.5 1.4 105.13.0 1 0 2.1.11 105.13.0 1.9.9f12 1.9.9f12 1.9.9f12 17 10 14 10 10 20 1.0.8d0 6.2.6 1.9.9f12 1.9.9f12 4.5.0d5 74.2 2.3.8f7 10.0.3 3.1.0d3 1.8.0fc1 1.3 41 1.0.8d0 6.2.6 2.2 2.2 2.3.8f7 2.3.8f7 2.3.8f7 206.6 4.1.5 4.1.5 3.9.0 2.6.5 1.6 1.6 1.6 312 402.1 2.0 1.2.5 2.6.5 2.0.4 1.9 4.1.5 4.1.7 1.4.0 1.11 2.2.7 1.6.5 1.1 1.0.0d1 6 289 1.6.2 1.3.5 2.6 1.3.0

    Now I have no idea how to read this, until last year I was always Windows, so I want to learn more about my computer, though I love PC and was raised on it, I do not hate mac. OSX is a very comforting OS, and easy to use, so I want to know more about it, and its problems,so I can fix my own computer,weather its mac or PC.

    So if one could help Please tell me what this could mean, and please explain if possible how you reached this conclusion since everywhere I go for research on Kernel Panics is a dead end. Thank you.
  2. Detrius macrumors 68000

    Sep 10, 2008
    Asheville, NC
    This part right here says that it was the AirPort (Broadcom) kernel extension that caused the panic. This may mean you have a bad AirPort card, especially if a large portion of your panic logs point to AirPort like this.

    If you turn off AirPort, your machine may stop panicking, but of course this disables your wireless networking. If you unplug or remove the AirPort card, your machine will most likely stop panicking, but this also disables BlueTooth, since it's the same card.
  3. Mr.Kernel thread starter macrumors newbie

    Nov 18, 2011
    So do you know is this something that I could fix, or do I need to bring it into a Apple store. If its something I can fix do you(or anyone else) know if it is a big money operation. Also you mentioned that if I turn of Airport it also turns off wireless, so can it also be said that if you take the card out that it will also prevent me from using wireless?
  4. Detrius macrumors 68000

    Sep 10, 2008
    Asheville, NC
    Whether or not it can be fixed by you depends on you. On that machine, the airport/bluetooth card is relatively easy to get to. Yes, unplugging or removing the card will disable your wifi.

    If the machine is under AppleCare, and it turns out to be a bad card/cable/logic board, then it should be covered (so long as there's no accidental damage that caused it).

    Otherwise, it looks like the part number is 661-5541 for the mid '10 MacBook AirPort/Bluetooth card, or 661-5388 for late '09. (it could theoretically still be the cable, the logic board, or software, but it's more likely to be the card.)
  5. Mr.Kernel thread starter macrumors newbie

    Nov 18, 2011
    If it was a cable what cable exactly would it be? As for logic board how would one go about fixing that?Software is scanned and I go through periodically to check for folders that are copies, or wont open, then check them to see what use they have. As for my mac it is not under the care plan(to much money, I didn't want to drain my parents since they bought it for my college classes) and it is a late 2010,late being was bought about a week from September 14 2010, so can you think of any immediate issues from that year?

    Also I do a LOT of switching from class to class, yet each class has their own wi-fi hub, in between classes there is no wifi, but due to neiboring buildings I constantly am being connected to other wirless networks not from the school. This causes Firefox to crash often since it constantly has to re-load the page. Could this be a cause for the Airport problems, by possibly putting to much stress on it? Since at home I am the only wireless network and I NEVER get a panic related to this at my house, last house Kernel was 5 months ago, due to heat, and was corrected with a cooling pad.I let the panic go unnoticed since it didnt return within the next 2 weeks after the first.

    Today scared me a bit since I got so many in one day, all while walking down the halls(where there is about 5-6 other networks aside from the schools).
  6. chrfr macrumors 604

    Jul 11, 2009
    While I don't disagree that it might be the Airport card, your operating system is out of date, as is Virtualbox. Update both, then see if the panic goes away before tearing your machine apart.
  7. Mr.Kernel thread starter macrumors newbie

    Nov 18, 2011
    I am currently happy with the version of virtualbox as is, and have VERY expensive software on it that I can no longer get(one time use product key for Tina Pro, and MANY more.

    As for my OS, I updated it after last kernel,thinking the same,maybe it would be fixed with new update.
  8. chrfr macrumors 604

    Jul 11, 2009
    Updating the Virtualbox application won't in any way affect your virtual machine, but there have likely been several updates which improve performance and reliability. You mention that the panics often happen when you're using Virtualbox, I don't see why you wouldn't want to update it.
    To be safe, just make a copy of the virtual machine file, so you can go back if something goes wrong.
  9. Mr.Kernel thread starter macrumors newbie

    Nov 18, 2011
    Yes sorry for that confussion, my HEAT related kernel poanics happend when VB was open but thats it, I fixed that a while ago, I just added that since I thought that it could be a possibility. Though I haven't had problems with Virtual Box ever other than heat, since I usually have 1 core going to my mac and the other on my Virtual Box to help it run smoother, its when I start to open more than 2 more programs on mac that virtual box heats up.But thats an obvious result.

    That and I dont know a lot about Virtual box, since my friend helped me with set up due to some busys times in my life where I didnt have the time to sit and learn. So I still have to learn about it so I won't screw it up. So far I think that it was my Airport card, I haven't moved at all with my mac, there are no interfering wireless networks, no kernel panics.

Share This Page