Mac Mini 2011 crash

Discussion in 'OS X Yosemite (10.10)' started by Joao Mag, Sep 2, 2015.

  1. Joao Mag, Sep 2, 2015
    Last edited: Sep 2, 2015

    Joao Mag macrumors newbie

    Sep 2, 2015
    I there.
    Any help for this error message?!

    NOTE: I had 2 equal RAM modules, one in each slot, but only one appears in the error message ... !!!

    Wed Sep 2 00:36:59 2015

    *** Panic Report ***

    panic(cpu 1 caller 0xffffff802c016df2): Kernel trap at 0xffffff802c3601e3, type 13=general protection, registers:

    CR0: 0x0000000080010033, CR2: 0x00007f9888720008, CR3: 0x0000000237d2e053, CR4: 0x00000000000626e0

    RAX: 0x50443180414153a8, RBX: 0x0000000000000000, RCX: 0xffffff80405a6000, RDX: 0x0000000000000000

    RSP: 0xffffff8137d8b4f0, RBP: 0xffffff8137d8b5c0, RSI: 0x0000000000000000, RDI: 0xffffff80420b5e20

    R8: 0x00000000fffffffe, R9: 0xffffff803f45d808, R10: 0xffffff802c147950, R11: 0x00000000000000c0

    R12: 0x0000000000000000, R13: 0xffffff80420b5e20, R14: 0x0000000000000000, R15: 0xffffff8137d8b858

    RFL: 0x0000000000010246, RIP: 0xffffff802c3601e3, CS: 0x0000000000000008, SS: 0x0000000000000010

    Fault CR2: 0x00007f9888720008, Error code: 0x0000000000000000, Fault CPU: 0x1

    Backtrace (CPU 1), Frame : Return Address

    0xffffff812e7fde10 : 0xffffff802bf2ad21

    0xffffff812e7fde90 : 0xffffff802c016df2

    0xffffff812e7fe050 : 0xffffff802c033ca3

    0xffffff812e7fe070 : 0xffffff802c3601e3

    0xffffff8137d8b5c0 : 0xffffff802c16ccdb

    0xffffff8137d8b640 : 0xffffff802c122cd2

    0xffffff8137d8bd00 : 0xffffff802c1250a1

    0xffffff8137d8bf00 : 0xffffff802c11e257

    0xffffff8137d8bf50 : 0xffffff802c44b376

    0xffffff8137d8bfb0 : 0xffffff802c0344a6

    BSD process name corresponding to current thread: fontworker

    Mac OS version:


    Kernel version:

    Darwin Kernel Version 14.5.0: Wed Jul 29 02:26:53 PDT 2015; root:xnu-2782.40.9~1/RELEASE_X86_64

    Kernel UUID: 58F06365-45C7-3CA7-B80D-173AFD1A03C4

    Kernel slide: 0x000000002bc00000

    Kernel text base: 0xffffff802be00000

    __HIB text base: 0xffffff802bd00000

    System model name: Macmini5,2 (Mac-4BC72D62AD45599E)

    System uptime in nanoseconds: 46513752156

    last loaded kext at 6638289373: 1.70 (addr 0xffffff7fade2e000, size 32768)

    loaded kexts: 1.70 1.9.5d0 3.0 2.2.0d4 1.0.2d2 110.19.6 4.3.6f3 1 124 272.18.1 3.6.1 1.2.12 1.3.2 3.10.25 272.18.1 1.3.2 2.0.2 272.18.1 1.0.0 10.0.0 4.1.0 3.10.25 1.0.0 1.3.2 4.3.6f3 4.3.6f3 1.0.1 7.0.0 1 1 4.0.0 1.7.3 10.0.0 327.5 3.0.1 1

    Model: Macmini5,2, BootROM MM51.0077.B12, 2 processors, Intel Core i5, 2.5 GHz, 4 GB, SMC 1.75f0

    Graphics: AMD Radeon HD 6630M, AMD Radeon HD 6630M, PCIe, 256 MB

    Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80CE, 0x4D34373142353137335148302D594B302020

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

    Bluetooth: Version 4.3.6f3 16238, 3 services, 18 devices, 1 incoming serial ports

    Network Service: Ethernet, Ethernet, en0

    Serial ATA Device: Samsung SSD 850 EVO 250GB, 250,06 GB

    USB Device: Hub

    USB Device: Trust Webcam

    USB Device: BRCM20702 Hub

    USB Device: Bluetooth USB Host Controller

    USB Device: Hub

    USB Device: Hub

    USB Device: 2.4G Wireless Mouse

    USB Device: Keyboard Hub

    USB Device: Apple Keyboard

    USB Device: IR Receiver

    Thunderbolt Bus: Mac mini, Apple Inc., 22.2
  2. keysofanxiety macrumors G3


    Nov 23, 2011
    Download and run SMART Utility, check HDD. Anything other than passed means corrupted HDD.

    If that's OK, run volume verification in Disk Utility. If it fails, run a volume repair through recovery OS (quote this if you need assistance)

    If that's OK, download and install MemTest here. Open Terminal. Type in memtest all 10. If your system shortly kernel panics after doing this, it's likely to be the RAM. You can run an extended test outside the OS by booting into Single User Mode (holding CMD+S on startup), and typing in the same command (memtest all 10). Any errors here will confirm it's the RAM. You can change the amount of times it runs the memtest by changing the number 10 to a different number.
  3. Joao Mag thread starter macrumors newbie

    Sep 2, 2015

    I have a SSD Samsung 850EVO, brand new (the Apple Service says that the earlier SSD was "the" problem...)
    I will try your tips as soon as possible
    Thanks again
  4. Joao Mag thread starter macrumors newbie

    Sep 2, 2015

    But I also tested both memories in both slots.
    Both of them do not have problems with a (bank 1), but both have another problem in (bank 0)
  5. keysofanxiety macrumors G3


    Nov 23, 2011
    Oh. In which case it's an issue with one of the RAM slots on the Logic Board.
  6. Joao Mag thread starter macrumors newbie

    Sep 2, 2015

    But in this case, the AHT should not detect the failure?!
    I have run the application and did not yield any error ...
    So I put the error message to see if someone could detect something ...
    Thanks anyway
  7. keysofanxiety macrumors G3


    Nov 23, 2011
    If you've tried with individual DIMMs - 1 DIMM at a time - and if both work in one slot, but neither work in the other slot or it kernel panics in the other slot - it's the Logic Board.

    Run a MemTest anyway.

    Also AHT is rubbish for picking up these sorts of things.
  8. Joao Mag thread starter macrumors newbie

    Sep 2, 2015

    :) Ok. Thanks

Share This Page