Kernel Panic Crashes

Discussion in 'Mac Basics and Help' started by rottenapple2.0, Nov 1, 2018.

  1. rottenapple2.0 macrumors newbie


    Nov 1, 2018
    hey, my mbp crashed a couple of times over the past weeks and months. today it did it again... i'd like to know why. i use etrecheck, but i dont understand the reports. is there someone who can help me understand it?

    Thu Nov 1 09:15:28 2018

    *** Panic Report ***
    panic(cpu 5 caller 0xffffff8000dfd245): Kernel trap at 0xffffff800115b4c7, type 13=general protection, registers:
    CR0: 0x000000008001003b, CR2: 0x000000015ebe3000, CR3: 0x00000004540ab00a, CR4: 0x00000000000626e0
    RAX: 0xbfffff8038a758b0, RBX: 0x0000000000000000, RCX: 0x0000000000000900, RDX: 0xffffff8038a758b0
    RSP: 0xffffff91ea843ea0, RBP: 0xffffff91ea843f60, RSI: 0xffffff8038a75800, RDI: 0x00b8a7580010b000
    R8: 0x0000000000000000, R9: 0x0000000000000000, R10: 0x0000000000000000, R11: 0xffffff81de4d6058
    R12: 0xffffff8038a758a0, R13: 0xffffff8038a75800, R14: 0xffffff803841f640, R15: 0x0000000000000000
    RFL: 0x0000000000010246, RIP: 0xffffff800115b4c7, CS: 0x0000000000000008, SS: 0x0000000000000010
    Fault CR2: 0x000000015ebe3000, Error code: 0x0000000000000000, Fault CPU: 0x5, PL: 1, VF: 0

    Backtrace (CPU 5), Frame : Return Address
    0xffffff8000b4dc50 : 0xffffff8000ce756c
    0xffffff8000b4dcd0 : 0xffffff8000dfd245
    0xffffff8000b4deb0 : 0xffffff8000c985a3
    0xffffff8000b4ded0 : 0xffffff800115b4c7
    0xffffff91ea843f60 : 0xffffff800115ba81
    0xffffff91ea843fb0 : 0xffffff8000c97957

    BSD process name corresponding to current thread: plugin-container

    Mac OS version:

    Kernel version:
    Darwin Kernel Version 16.7.0: Thu Jun 21 20:07:39 PDT 2018; root:xnu-3789.73.14~1/RELEASE_X86_64
    Kernel UUID: CA05D43A-8B83-3114-828D-72E83BEC8DD9
    Kernel slide: 0x0000000000a00000
    Kernel text base: 0xffffff8000c00000
    __HIB text base: 0xffffff8000b00000
    System model name: MacBookPro8,2 (Mac-94245A3940C91C80)

    System uptime in nanoseconds: 7088707090654
    last loaded kext at 136524695838: 3.1.2 (addr 0xffffff7f818e2000, size 425984)
    loaded kexts:
    com.radiosilenceapp.nke.filter 2.2 3.1.2 1.70 3.0 1.9.5d0 110.23.17 1.0.2d2 131 3.14.49 279.48 279.48 279.48 1 3.6.4 1.0.1 1.5.1 5.0.5f3 7.0.0 1.5.1 3.0.8 1 10.0.2 1.5.1 1.0.0 1 208 4.0.0 3.14.49 1.0.0 170.9.20 1.3.4 3.0.4d1 3.1 10.0.2 4.1.0 5.0.5f3 540.30.1 3.0.1 1.0.0d1 1.0.0

    System Profile:
    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xD6), Broadcom BCM43xx 1.0 (
    Bluetooth: Version 5.0.5f3, 3 services, 27 devices, 1 incoming serial ports
    Thunderbolt Bus: MacBook Pro, Apple Inc., 22.1
    Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x029E, 0x434D5341384758334D314131363030433131
    Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x029E, 0x434D5341384758334D314131363030433131
    USB Device: USB 2.0 Bus
    USB Device: Hub
    USB Device: IR Receiver
    USB Device: USB 2.0 Bus
    USB Device: FaceTime HD Camera (Built-in)
    USB Device: Hub
    USB Device: Apple Internal Keyboard / Trackpad
    USB Device: BRCM2070 Hub
    USB Device: Bluetooth USB Host Controller
    Serial ATA Device: Samsung SSD 750 EVO 250GB, 250,06 GB
    Serial ATA Device: Samsung SSD 850 EVO 500GB, 500,11 GB
    Model: MacBookPro8,2, BootROM MBP81.0047.B32, 4 processors, Intel Core i7, 2 GHz, 16 GB, SMC 1.69f4
    Network Service: Wi-Fi, AirPort, en1
    Graphics: Intel HD Graphics 3000, Intel HD Graphics 3000, Built-In
    Graphics: AMD Radeon HD 6490M, AMD Radeon HD 6490M, PCIe, 256 MB
  2. chabig macrumors 603

    Sep 6, 2002
    I have a healthy skepticism about apps that install kernel extensions. So just looking through the list and looking for things that aren't from Apple, Radio Silence jumps out immediately. Most ad blockers don't muck around with the core of the operating system. Try uninstalling that and see what happens. Also, your machine can run Mojave, which recently had its first update since release. Consider updating your OS.
  3. rottenapple2.0 thread starter macrumors newbie


    Nov 1, 2018
  4. hobowankenobi macrumors 6502a

    Aug 27, 2015
    on the land line mr. smith.
    Historically, RAM has been the cause of most KPs. If this is an older MBP with user upgradeable RAM, it could be the culprit. Any RAM changes recently?

    Obviously if it is a newer model with integrated RAM (not upgradeable), you will want to focus on kexts as mentioned.
  5. rottenapple2.0 thread starter macrumors newbie


    Nov 1, 2018
    RAM is upgraded. but that happend almost 2 years before the panic started...
  6. hobowankenobi macrumors 6502a

    Aug 27, 2015
    on the land line mr. smith.
    So likely not the issue.

    Rare...but RAM does go bad occasionally. For no visible reason.

    Could be a manufacturing defect, or exposure to static (during handling/install) that can cause latent damage. Either way...if a stick is bad, it will have to be replaced.

  7. chscag macrumors 68040


    Feb 17, 2008
    Fort Worth, Texas
    Appears you removed the Optical Drive and installed an SSD in its place along with another SSD which replaced the original hard drive. Make sure you use something like DriveDX to check both those SSDs as one of them could be the cause of your KPs. I doubt it's memory and the indication from the KP report says nothing about the GPU. One thing you can try... is startup in SAFE mode and run for awhile to see if the KP occurs again. If it happens in SAFE mode it's almost sure to be a hardware problem.

Share This Page

6 November 1, 2018