Kernel Panics - Late 2014 RiMac

Discussion in 'iMac' started by Fried Potato, Jul 1, 2017.

  1. Fried Potato macrumors member

    Fried Potato

    Jan 10, 2015

    Since upgrading to Sierra about three months back, I started to encounter several Kernel panics a day. I've contacted Apple Care and nothing's worked yet, so they've told me to wipe everything on my computer and restore everything from my Time machine copy. Why haven't I done this yet? Well, I need my computer every day and I haven't had any time off to be able to do it. I just thought if you guys possibly could take a look at my most recent Kernel panic log and see if you can identify the issue? Is it really the software? I'm really scared that a hardware problem has occured, I don't want to send it to Apple as this is my only computer.

    As I mentioned earlier, the Kernel Panics just started to appear after I upgrade to Sierra. I had no problems at all with Yosemite or El Capitan. I did encounter Kernels when using the earlier Mac OS versions, but that wasn't more than probably once every six months or even less than that, which's pretty normal as all computers will get an error or two sometimes. I just had three or four Kernel panics right now with just about five minutes in between each.

    *** Panic Report ***
    panic(cpu 2 caller 0xffffff800bd99958): "vm_object_iopl_request: missing/bad page in kernel object\n"@/Library/Caches/
    Backtrace (CPU 2), Frame : Return Address
    0xffffff93b5f02b80 : 0xffffff800bcea53c
    0xffffff93b5f02c00 : 0xffffff800bd99958
    0xffffff93b5f02fd0 : 0xffffff800bd99130
    0xffffff93b5f030b0 : 0xffffff800bd99016
    0xffffff93b5f03190 : 0xffffff800c2cebde
    0xffffff93b5f032a0 : 0xffffff800c2cc887
    0xffffff93b5f032e0 : 0xffffff7f8c45c62e
    0xffffff93b5f033b0 : 0xffffff7f8e08af05
    0xffffff93b5f03500 : 0xffffff800bf55065
    0xffffff93b5f03570 : 0xffffff800befb380
    0xffffff93b5f03650 : 0xffffff800befd9dc
    0xffffff93b5f036b0 : 0xffffff800befea97
    0xffffff93b5f036d0 : 0xffffff7f8df24794
    0xffffff93b5f03770 : 0xffffff7f8df25845
    0xffffff93b5f03790 : 0xffffff7f8df2710f
    0xffffff93b5f03870 : 0xffffff7f8df641d3
    0xffffff93b5f03b80 : 0xffffff7f8df66460
    0xffffff93b5f03bb0 : 0xffffff800bef7d0b
    0xffffff93b5f03f50 : 0xffffff800c224d55
    0xffffff93b5f03fb0 : 0xffffff800bc9bd96
          Kernel Extensions in backtrace:
    BSD process name corresponding to current thread: mdworker
    Mac OS version:
    Kernel version:
    Darwin Kernel Version 16.6.0: Fri Apr 14 16:21:16 PDT 2017; root:xnu-3789.60.24~6/RELEASE_X86_64
    Kernel UUID: FB2170A8-257D-3C64-B14D-BC06CC94E34C
    Kernel slide:     0x000000000ba00000
    Kernel text base: 0xffffff800bc00000
    __HIB  text base: 0xffffff800bb00000
    System model name: iMac15,1 (Mac-FA842E06C61E91C5)
    System uptime in nanoseconds: 40747678179
    last loaded kext at 20083060216:    92 (addr 0xffffff7f8ebc8000, size 61440)
    loaded kexts:
    org.pqrs.driver.Karabiner    10.22.0
    com.logitech.driver.LogiGamingMouseFilter    1
    com.driver.LogJoystick    2.0
    com.logitech.driver.LogiWheelDriver    1    92    1.70    3.0    3.13    131    279.48    279.48    279.48    110.23.17    2.7.0d0    1.0.0    3.14.47    3.6.4    1.5.1    1    1.0.1    1.5.1    5.0.4f18    10.2.5    1    7.0.0    3.14.47    10.2.5    1.0.0    170.9.20    208    4.1.0    3.1    1.5.1    1    4.0.0    1.3.1    3.0.8    5.0.4f18    540.30.1    3.0.1    1.0.0d1    1.0.0    40    366.50.19    295.20.1    1.7.6    10.2.10    1150.10.1a2    326.60.1    5.0    2.0    1.8    2.1    5.0    1.7    172    3    8    368.16    76.7    199    5.0.4f18    199    1.0    279.48    525    11    159.7    3.14.47    311.13    1.0.0    1.0.0    1.1.0    516.1    279.48    279.48    1.0.14d1    6.0.0d8    1.5.1    3.14.47    1.0    1.0.0    3.1.9    1.0.18d1    515.3    4.1.1    394.50.1    5.0.4f18    5.0.4f18    5.0.4f18    5.0.4f18    308.7    205.15    1.2.0    900.4.1    1.1    5.0.0    5.0.0    1.1    1.1    540.30.1    1    900.4.1    5.0.2    5.0.2    5.0.2    2.1.3    2.1.3    3    4.5.4    6.5.7    1.0.3b4    1200.12.2    1.0.1b8    3.2    1.0.4    288    3.0.60    1.1    1.1    1.0    900.4.1    1.1    2.1    2.0.0    2.1    1.1    300.0    1.0.0d1    2    1.0.5    1.0    1    1.1    1.0    444.50.16    2.1    31    28.30    5.0    2.9    1.4    1    1    1.0
    Model: iMac15,1, BootROM IM151.0207.B16, 4 processors, Intel Core i7, 4 GHz, 32 GB, SMC 2.23f11
    Graphics: AMD Radeon R9 M295X, AMD Radeon R9 M295X, PCIe, 4096 MB
    Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1867 MHz, 0x859B, 0x424C533847334E3138414553342E31364645
    Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1867 MHz, 0x859B, 0x424C533847334E3138414553342E31364645
    Memory Module: BANK 0/DIMM1, 8 GB, DDR3, 1867 MHz, 0x859B, 0x424C533847334E3138414553342E31364645
    Memory Module: BANK 1/DIMM1, 8 GB, DDR3, 1867 MHz, 0x859B, 0x424C533847334E3138414553342E31364645
    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x142), Broadcom BCM43xx 1.0 (
    Bluetooth: Version 5.0.4f18, 3 services, 27 devices, 1 incoming serial ports
    Network Service: Ethernet, Ethernet, en0
    Network Service: Wi-Fi, AirPort, en1
    PCI Card: pci1b21,612, AHCI Controller, Thunderbolt@193,0,0
    Serial ATA Device: APPLE SSD SM1024F, 1 TB
    Serial ATA Device: ST4000DX000-1CL160, 4 TB
    USB Device: USB 3.0 Bus
    USB Device: BRCM20702 Hub
    USB Device: Bluetooth USB Host Controller
    USB Device: FaceTime HD Camera (Built-in)
    USB Device: DA-300USB
    USB Device: USB Keyboard
    USB Device: USB Receiver
    Thunderbolt Bus: iMac, Apple Inc., 26.1
    Thunderbolt Device: d2 TBT2 USB3, LaCie, 3, 24.3

    Thank you in advance. :)
  2. DeltaMac macrumors G3


    Jul 30, 2003
    Run your diagnostics. That will give you something to check off, and might even report an error code.

    Which Logitech mouse are you using?
    You could try removing the logitech software to find out if that makes any difference.
    The Logitech mouse will work fine without that software (allowing for some changes in cursor acceleration, which might be acceptable for you... )

    Wipe and restore from backup might take about two or three hours.
    I would get tired of multiple panics within 30 minutes, after the second thirty minutes --- and would make the time.
    Sounds like you are wasting a lot of time with restarts, and the annoyance of having those panics now.

    If nothing shows up with the Diagnostics, then I would start by reinstalling your macOS --- particularly if you have never tried that yet. Make a bootable install for Sierra, if you don't already have one.
    Boot to the Sierra installer, run Reinstall macOS. Takes about 30 minutes (SSD may take significantly less time)
    This reloads the macOS, and doesn't touch your own files and apps. It leaves you at exactly the same setup that you have now, and might help with your issues.
    No help, then use your Time Machine... Boot to your installer again. Erase the drive using Disk Utility, then reinstall macOS. It will restart to complete the install, then ask if you want to restore from a Time Machine backup (along with some other choices for a restore). Depending on the amount of data to restore, again, takes probably two or three hours.

    Now, you have to decide if it's worth your time to try to make your system work more reliably.
  3. Fried Potato thread starter macrumors member

    Fried Potato

    Jan 10, 2015
    Thank you for your reply! :)

    Well, today has probably been one of the worst days when it comes to Kernel Panics. Probably had about more than ten today.

    I though if it perhaps may be the RAM that is the issue? I chose the standard amount of RAM and bought 32GB RAM afterwards as that was cheaper than buying it through Apple. I actually ran a RAM test after buying them and I got an error or two about one hour into the test. But the computer and the aftermarket RAM sticks have worked together for two years now, until Sierra. I thought if replacing the RAM sticks with the original ones might fix it?
  4. Taz Mangus macrumors 68040

    Taz Mangus

    Mar 10, 2011
    Yes replacing the original RAM that came with the computer would be a good sanity check. Another thought is that maybe try reseating the RAM again.
  5. SaSaSushi, Jul 2, 2017
    Last edited: Jul 2, 2017

    SaSaSushi macrumors 68040


    Aug 8, 2007
    Takamatsu, Japan
    Kernel panics are a very common symptom of bad RAM. If you got any errors running memory tests you have problem RAM.

    Even though the panics have increased with Sierra, the problem is more than likely your RAM.

    I agree with the last post's advice to pop back in the Apple RAM if you still have it and see if the problem resolves.
  6. DeltaMac macrumors G3


    Jul 30, 2003
    I think it is worth trying, but what was the result from the Diagnostic test?
    Run the Diagnostic test with the RAM that you are using now, and then run again with the original RAM installed.
    Did you replace the original RAM - or add to that RAM, and the original pair is still installed?
    If you have memtest, you should also try that.
    (yes, it all takes time... be patient.)
    Don't accept ANY errors on the memory test, particularly if you reseat the RAM before running the test.
    You should have a clean (no error) result from testing your memory. Any errors should prompt you to replace the memory. You can run the test again, with only one stick at a time, try to isolate to one pair, or even just one stick of memory, if possible.
  7. SaSaSushi macrumors 68040


    Aug 8, 2007
    Takamatsu, Japan
    Back in 2014 I went through kernel panic hell trying to add RAM to my Late 2013 iMac and sometimes the problem RAM would pass the Apple Hardware Test.

    100% agreement here. None of my bad RAM passed Memtest without errors. Create a Memtest USB boot flash for best testing and dump any RAM that gives any errors.
  8. Fried Potato thread starter macrumors member

    Fried Potato

    Jan 10, 2015
    Well guys, I actually changed the RAM sticks to the original ones directly after writing here about them possibly being defect. I can say that for the last two days my computer has been error free! I actually ran Memtest after installing the sticks two years ago and I got a couple of errors an hour into the test (which I mentioned in my prior post). It seems like that they held on for two years without causing any massive errors, but they wrecked havoc in the end.

    So, I'm in need of new RAM sticks now. I guess that these RAM sticks will be perfect for the job?
  9. DeltaMac macrumors G3


    Jul 30, 2003
    In my opinion --- Corsair, and "perfect for the job" doesn't always happen.
    How about this from Amazon UK? Cheaper, and reliable --- from Crucial, too.
  10. nambuccaheadsau macrumors 65816


    Oct 19, 2007
    Nambucca Heads Australia

Share This Page