frequent reboots with El Cap/riMac

Discussion in 'OS X El Capitan (10.11)' started by siddhartha, Oct 9, 2015.

  1. siddhartha, Oct 9, 2015
    Last edited: Oct 9, 2015

    siddhartha macrumors regular


    Aug 8, 2008
    Northern Virgina
    So when I bought my riMac, it had Yosemite installed. I transferred the data from my 2011 iMac, and noticed that I had fairly frequent reboots. It would often reboot during the night, and I noticed this about 2-3 times per week (the computer is left on).

    I installed the beta version of El Cap, and those reboots disappeared. The computer was seemingly rock-stable, and I was happy.

    I'm in the beta program for the latest version, and ever since the last update, the computer is back to those reboots. I get that dialog "Your computer was restarted because of a problem" with the option to send the report to Apple, which I do every time.

    I did save the data reported in that window, and can post it later if someone's able to decipher it.

    I'm thinking I may clean-install El Cap, and wipe my Mac OS partition. Can I do this and keep my bootcamp partition safe? I do have a WinClone backup, but I worry that I might manage to mess it up, and have to reinstall Windows 10 along with El Cap-I don't want to do this if possible.

    I know nobody can say for sure, but I'm wondering if this is the best course of action (the clean install). It's a bit of a hassle, but I can do it if it will clear out any issues. I'd slowly add back the programs I'm using.

    I did notice that in the past, a USB3 hub I was using suddenly seemed to slow down the boot process to a crawl, and it sped right back up when I disconnected it. I bought 2 new USB hubs, and they both seem to work well without causing that problem. Other than that, I have a Thunderbolt->USB harddrive connected. I also use a Logitech MX Master mouse.

    I'd love to get this machine stable again. My old 2011 i7 iMac was always rock-stable, and is doing duty as a media server in the basement, on El Cap, without issue.


    Here's the info in the crash report:

    *** Panic Report ***

    panic(cpu 0 caller 0xffffff80161d4b3a): Kernel trap at 0xffffff7f98bc6efb, type 13=general protection, registers:

    CR0: 0x000000008001003b, CR2: 0x000000014d4cc000, CR3: 0x000000001a3cc000, CR4: 0x00000000001627e0

    RAX: 0xffffff7f98c22d00, RBX: 0xffffff82858d8000, RCX: 0xffffff8046211320, RDX: 0x0000000000001858

    RSP: 0xffffff82b61e7dc0, RBP: 0xffffff82b61e7df0, RSI: 0x0000000000000002, RDI: 0xffffff8046211320

    R8: 0x0000000000000000, R9: 0x0000000000000001, R10: 0x00000000ffffff9b, R11: 0x0000000000000003

    R12: 0x0000000000000000, R13: 0xffffff92e676bb90, R14: 0xffffff82858d8180, R15: 0x0000000000000000

    RFL: 0x0000000000010082, RIP: 0xffffff7f98bc6efb, CS: 0x0000000000000008, SS: 0x0000000000000010

    Fault CR2: 0x000000014d4cc000, Error code: 0x0000000000000000, Fault CPU: 0x0, PL: 2

    Backtrace (CPU 0), Frame : Return Address

    0xffffff82b61f3c50 : 0xffffff80160e3357

    0xffffff82b61f3cd0 : 0xffffff80161d4b3a

    0xffffff82b61f3eb0 : 0xffffff80161f2133

    0xffffff82b61f3ed0 : 0xffffff7f98bc6efb

    0xffffff82b61e7df0 : 0xffffff7f98bc6e13

    0xffffff82b61e7e30 : 0xffffff7f994573e7

    0xffffff82b61e7e60 : 0xffffff7f99456a0f

    0xffffff82b61e7f10 : 0xffffff7f9686913a

    0xffffff82b61e7f50 : 0xffffff7f98b2d2be

    0xffffff82b61e7f60 : 0xffffff7f98b35449

    0xffffff82b61e7f80 : 0xffffff80161d3ecc

    0xffffff82b61e7fd0 : 0xffffff80161f22f9

    0xffffff92e676bca0 : 0xffffff7f97938509

    0xffffff92e676bce0 : 0xffffff7f9793afae

    0xffffff92e676bd40 : 0xffffff7f97aba9f0

    0xffffff92e676bd60 : 0xffffff7f97980a86

    0xffffff92e676be60 : 0xffffff7f9794624a

    0xffffff92e676be80 : 0xffffff7f978a5dff

    0xffffff92e676bea0 : 0xffffff80166b94a3

    0xffffff92e676bf00 : 0xffffff80161176aa

    0xffffff92e676bfb0 : 0xffffff80161cf557

    Kernel Extensions in backtrace:[61BDE27B-F8E0-329C-889A-85143B860A10]@0xffffff7f9684d000->0xffffff7f9687cfff[295F7A91-2DF7-3FFE-9550-A0C1A6F9D575]@0xffffff7f98b26000->0xffffff7f98b85fff














    dependency: Z?`<?(pzcModel: iMac15,1, BootROM IM151.0207.B05, 4 processors, Intel Core i7, 4 GHz, 24 GB, SMC 2.23f11

    Graphics: AMD Radeon R9 M295X, AMD Radeon R9 M295X, PCIe, 4096 MB

    Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1600 MHz, 0x802C, 0x384B54463531323634485A2D314736453220

    Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1600 MHz, 0x802C, 0x384B54463531323634485A2D314736453220

    Memory Module: BANK 0/DIMM1, 8 GB, DDR3, 1600 MHz, 0x859B, 0x43543130323436344246313630422E433136

    Memory Module: BANK 1/DIMM1, 8 GB, DDR3, 1600 MHz, 0x859B, 0x43543130323436344246313630422E433136

    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x142), Broadcom BCM43xx 1.0 (

    Bluetooth: Version 4.4.2f1 16391, 3 services, 27 devices, 1 incoming serial ports

    Network Service: Wi-Fi, AirPort, en1

    PCI Card: pci1b21,1142, USB eXtensible Host Controller, Thunderbolt@195,0,0

    PCI Card: pci1b21,612, AHCI Controller, Thunderbolt@194,0,0

    Serial ATA Device: APPLE SSD SD0128F, 121.33 GB

    Serial ATA Device: APPLE HDD ST3000DM001, 3 TB

    Serial ATA Device: spsata_pm_name

    USB Device: USB 3.0 Bus

    USB Device: USB 3.0 Bus

    USB Device: USB3.0 Hub

    USB Device: USB Storage

    USB Device: USB to ATA/ATAPI Bridge

    USB Device: Hub

    USB Device: BRCM20702 Hub

    USB Device: Bluetooth USB Host Controller

    USB Device: FaceTime HD Camera (Built-in)

    USB Device: USB2.0 Hub

    USB Device: USB2.0 Hub

    USB Device: Wireless Gamepad F710

    USB Device: CanoScan

    Thunderbolt Bus: iMac, Apple Inc., 26.1

    Thunderbolt Device: Thunderbolt to eSATA+USB3.0 Adapter, Kanex, 1, 7.1
  2. siddhartha thread starter macrumors regular


    Aug 8, 2008
    Northern Virgina

    I posted this error report on another forum, and was told that these types of errors/reboots are most often related to memory. I looked up the memory I purchased (Crucial) and found that other riMac users had similar problems with it. I took out the additional memory, and so far, no reboots.

    What I find odd is that I had a period of time without any reboot/error issues, and it only seemed to worsen with the latest El Cap beta build. Also, I had next to no reboot issues when running Windows 10 in bootcamp. Perhaps OS X is more sensitive to memory issues?

    In any case, for now, problem is solved with taking out ?faulty? memory

Share This Page