New machine randomly reboots

Discussion in 'OS X Mavericks (10.9)' started by luckytaxi, Aug 8, 2014.

  1. luckytaxi, Aug 8, 2014
    Last edited: Aug 8, 2014

    luckytaxi macrumors newbie

    Jul 29, 2014
    So, my refurb laptop arrived earlier this week. All was well until earlier today when it randomly reboots with the following message. "Your computer restarted because of a problem."

    I'm a new Mac user so I'm still trying to figure out stuff. Below is the error message it produces.


    Fri Aug 8 09:33:46 2014
    panic(cpu 0 caller 0xffffff80106dc24e): Kernel trap at 0xffffff80106a3699, type 14=page fault, registers:
    CR0: 0x0000000080010033, CR2: 0x0000010000000028, CR3: 0x0000000021363008, CR4: 0x00000000001606e0
    RAX: 0x0000000000000001, RBX: 0x0000010000000000, RCX: 0xffffff8023b33140, RDX: 0x0000000000000821
    RSP: 0xffffff8113613d20, RBP: 0xffffff8113613d50, RSI: 0x0000000023c34600, RDI: 0xffffff8014d48aa0
    R8: 0x0000000000000000, R9: 0xffffff8113613ed0, R10: 0x0000000024885e75, R11: 0x0000000000000100
    R12: 0xffffff8014d48aa0, R13: 0xffffff8013d35000, R14: 0x0000000000004000, R15: 0xffffff8023f04920
    RFL: 0x0000000000010206, RIP: 0xffffff80106a3699, CS: 0x0000000000000008, SS: 0x0000000000000000
    Fault CR2: 0x0000010000000028, Error code: 0x0000000000000000, Fault CPU: 0x0

    Backtrace (CPU 0), Frame : Return Address
    0xffffff81136139b0 : 0xffffff8010622f79
    0xffffff8113613a30 : 0xffffff80106dc24e
    0xffffff8113613c00 : 0xffffff80106f3746
    0xffffff8113613c20 : 0xffffff80106a3699
    0xffffff8113613d50 : 0xffffff801067833e
    0xffffff8113613f20 : 0xffffff80106dc68c
    0xffffff8113613fb0 : 0xffffff80106f364b

    BSD process name corresponding to current thread: diskarbitrationd

    Mac OS version:

    Kernel version:
    Darwin Kernel Version 13.3.0: Tue Jun 3 21:27:35 PDT 2014; root:xnu-2422.110.17~1/RELEASE_X86_64
    Kernel UUID: BBFADD17-672B-35A2-9B7F-E4B12213E4B8
    Kernel slide: 0x0000000010400000
    Kernel text base: 0xffffff8010600000
    System model name: MacBookPro11,1 (Mac-189A3D4F975D5FFC)

    System uptime in nanoseconds: 2492047980
    last loaded kext at 1679881832: 240.2 (addr 0xffffff7f91e59000, size 20480)
    loaded kexts: 240.2 240.2 240.2 3.6.6 3.4.1 404 2.6.0 3.0.5 3.0.1 1.0.0d1 1.0.0d1 1.0.0d1 35 683.4.0 842.21.65 683.4.0 161.0.0 2.0 2.0 1.8 2.1 2.0 1.7 153 3 240.9 3.1.7 3.1.7 1.4.5 3.6.6 3.6.0 3.6.6 650.4.0 660.4.0 656.4.1 2.6.5 660.4.2 2.0.1 3.3.1 640.36 1.0.1b5 3.2 683.4.0 2.0 2.0 2.0.0 1.1 278.11.1 1.0.0d1 7 2 371.1 1.9 23 28.30 2.0 2.9 1.4 1.0 1
    Model: MacBookPro11,1, BootROM MBP111.0138.B07, 2 processors, Intel Core i5, 2.4 GHz, 8 GB, SMC 2.16f63
    Graphics: Intel Iris, Intel Iris, Built-In
    Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1600 MHz, 0x02FE, -
    Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1600 MHz, 0x02FE, -
    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x112), Broadcom BCM43xx 1.0 (
    Bluetooth: Version 4.2.6f1 14216, 3 services, 15 devices, 1 incoming serial ports
    Network Service: Wi-Fi, AirPort, en0
    Serial ATA Device: APPLE SSD SD0256F, 251 GB
    USB Device: Internal Memory Card Reader
    USB Device: Apple Internal Keyboard / Trackpad
    USB Device: BRCM20702 Hub
    USB Device: Bluetooth USB Host Controller
    Thunderbolt Bus: MacBook Pro, Apple Inc., 17.2
  2. satcomer macrumors 603


    Feb 19, 2008
    The Finger Lakes Region
  3. Weaselboy Moderator


    Staff Member

    Jan 23, 2005
    Often this last loaded kext is a clue. Do you have any USB devices attached?

    If not, and you have not installed any third party software that might be causing a conflict, I would take it back to Apple.

    What you are seeing there is called a kernel panic.
  4. smithrh macrumors 68020


    Feb 28, 2009
    Certainly not normal, if you haven't done anything to it (or added any USB devices as Weaselboy points out), I'd really be thinking about returning it to Apple.

    Kernel Panics are typically - but not always - associated with hardware issues. Many times they can be resolved by un-doing whatever hardware changes you just did, such as removing a new USB device.
  5. NoBoMac macrumors 68000

    Jul 1, 2014
    Before going back to Apple, maybe try reinstalling the OS?

    Had a similar USB issue many years ago with, if I remember correctly, Snow Leopard or Lion. Something got borked during the install/update, so, reinstalled to hopefully get the extensions back in order.

    I'd probably reformat the OS volume and then do a fresh install.

    Worst comes to worst, waste under 1 hour before making the trip.

Share This Page