2012 i7 Mac Mini on Yosemite Crashes

Discussion in 'Mac mini' started by brycenesbitt, Dec 2, 2014.

  1. brycenesbitt macrumors newbie

    Joined:
    Aug 15, 2008
    #1
    Seemingly related to sleep or wake, I am getting a series of kernel panics on a 2012 Mac Mini:


    Sun Nov 23 18:51:27 2014

    *** Panic Report ***
    panic(cpu 6 caller 0xffffff802597a49d): "a freed zone element has been modified in zone vm objects: expected 0xffffff8146d91960 but found 0xffffff8046d91960, bits changed 0x100000000, at offset 0 of 240 in element 0xffffff80469683c0, cookies 0x3f0011c602bda028 0x53521edef25e81b"@/SourceCache/xnu/xnu-2782.1.97/osfmk/kern/zalloc.c:496

    *** Panic Report ***
    panic(cpu 6 caller 0xffffff802700453e): "Possible memory corruption: pmap_pv_remove(0xffffff80276dfd48,0xffffff822f02c000,0x100000, 0x100000000, 0xffffff8228a63968): empty hash"@/SourceCache/xnu/xnu-2782.1.97/osfmk/i386/pmap_internal.h:822
    Backtrace (CPU 6), Frame : Return Address

    Thu Nov 27 13:21:10 2014

    *** Panic Report ***
    panic(cpu 0 caller 0xffffff8022a1e80a): Kernel trap at 0xffffff7fa33c4974, type 14=page fault, registers:
    CR0: 0x000000008001003b, CR2: 0x00000008000000a0, CR3: 0x000000002472b001, CR4: 0x00000000001626e0
    RAX: 0xffffffffffffffe8, RBX: 0xffffff8049cec0c0, RCX: 0x0000000000000001, RDX: 0x7fffffffffffffff
    RSP: 0xffffff8223e1b9c0, RBP: 0xffffff8223e1b9e0, RSI: 0x0000000000000038, RDI: 0x0000000000000001
    R8: 0x0000000000000023, R9: 0xffffff81c15b6000, R10: 0xffffff80266e7c30, R11: 0xffffff8051a0ee70
    R12: 0xffffff804af525a0, R13: 0x0000000000000000, R14: 0x0000000000000038, R15: 0x0000000800000000
    RFL: 0x0000000000010297, RIP: 0xffffff7fa33c4974, CS: 0x0000000000000008, SS: 0x0000000000000010
    Fault CR2: 0x00000008000000a0, Error code: 0x0000000000000002, Fault CPU: 0x0

    Fri Nov 28 22:43:53 2014

    *** Panic Report ***
    panic(cpu 2 caller 0xffffff800401e80a): Kernel trap at 0xffffff800435a806, type 14=page fault, registers:
    CR0: 0x000000008001003b, CR2: 0x0000000100000030, CR3: 0x0000000005ddf001, CR4: 0x00000000001626e0
    RAX: 0x0000000100000000, RBX: 0xffffff803bf9f780, RCX: 0x0000000025000000, RDX: 0x0000000000000000
    RSP: 0xffffff81f197bd00, RBP: 0xffffff81f197bd20, RSI: 0x0000000000000002, RDI: 0xffffff803bf9daf0
    R8: 0x0000000000000001, R9: 0x0000000000000000, R10: 0x0000000000002000, R11: 0x000000000000000c
    R12: 0xffffff803bf9f780, R13: 0x0000000000000000, R14: 0xffffff81f197be18, R15: 0xffffff803bf9daf0
    RFL: 0x0000000000010206, RIP: 0xffffff800435a806, CS: 0x0000000000000008, SS: 0x0000000000000010
    Fault CR2: 0x0000000100000030, Error code: 0x0000000000000000, Fault CPU: 0x2

    Sun Nov 30 00:30:44 2014

    *** Panic Report ***
    panic(cpu 0 caller 0xffffff802881e80a): Kernel trap at 0xffffff802894bc05, type 14=page fault, registers:
    CR0: 0x000000008001003b, CR2: 0xffffff8153d3f2e8, CR3: 0x0000000025e2f001, CR4: 0x00000000001626e0
    RAX: 0xffffff8053d69c40, RBX: 0xffffff8053d3f1e0, RCX: 0x0000000000000000, RDX: 0xffffff8153d3f2d0
    RSP: 0xffffff8228c43cd0, RBP: 0xffffff8228c43cd0, RSI: 0x000000004463b68e, RDI: 0xffffff8053d3f1e0
    R8: 0xffffff80482b9b80, R9: 0x0000000000000002, R10: 0x0000000000000000, R11: 0x0000000000000246
    R12: 0x0000000000000008, R13: 0xffffff8053d3f230, R14: 0x0000000000000040, R15: 0x0000000000000020
    RFL: 0x0000000000010282, RIP: 0xffffff802894bc05, CS: 0x0000000000000008, SS: 0x0000000000000010
    Fault CR2: 0xffffff8153d3f2e8, Error code: 0x0000000000000002, Fault CPU: 0x0

    Sun Nov 30 04:54:13 2014

    *** Panic Report ***
    panic(cpu 4 caller 0xffffff802aa04707): "Possible memory corruption: pmap_pv_remove(0xffffff802b0dfd48, 0xffffff8256e0f000, 0x100000, 0x100000000, 0xffffff8215013974, 0xffffff8215013968): pv not on hash, head: 0xffffff802b0dfd48, 0xffffff8300000000"@/SourceCache/xnu/xnu-2782.1.97/osfmk/i386/pmap_internal.h:841
    Backtrace (CPU 4), Frame : Return Address
    0xffffff82150137b0 : 0xffffff802a93a811
    0xffffff8215013830 : 0xffffff802aa04707
    0xffffff82150139a0 : 0xffffff802a9a85e0
    0xffffff8215013a30 : 0xffffff802a997f2b
    0xffffff8215013a70 : 0xffffff802a9995f4
    0xffffff8215013ae0 : 0xffffff802a9981b5
    0xffffff8215013b10 : 0xffffff802a99a721
    0xffffff8215013b50 : 0xffffff802a99f378
    0xffffff8215013d00 : 0xffffff802a9a3902
    0xffffff8215013f20 : 0xffffff802aa1ec9c
    0xffffff8215013fb0 : 0xffffff802aa3a355

    BSD process name corresponding to current thread: com.apple.WebKit

    Tue Dec 2 02:18:16 2014

    *** Panic Report ***
    panic(cpu 2 caller 0xffffff800d61e80a): Kernel trap at 0xffffff800d742b58, type 14=page fault, registers:
    CR0: 0x000000008001003b, CR2: 0xffffff8147008b68, CR3: 0x000000000a768001, CR4: 0x00000000001626e0
    RAX: 0xffffff8047008a70, RBX: 0xffffff802c414c00, RCX: 0xffffff8147008b40, RDX: 0xffffff802c414c50
    RSP: 0xffffff8021fa3d30, RBP: 0xffffff8021fa3dd0, RSI: 0x000000000000e000, RDI: 0xffffff802c414c18
    R8: 0x0000000000000001, R9: 0x0000000000000000, R10: 0x0000000000002000, R11: 0x0000000000000022
    R12: 0xffffff8047008a50, R13: 0x0000000000000000, R14: 0xffffff802c414c18, R15: 0xffffff802c414c50
    RFL: 0x0000000000010282, RIP: 0xffffff800d742b58, CS: 0x0000000000000008, SS: 0x0000000000000000
    Fault CR2: 0xffffff8147008b68, Error code: 0x0000000000000002, Fault CPU: 0x2

    Tue Dec 2 19:03:09 2014

    *** Panic Report ***
    panic(cpu 4 caller 0xffffff8000a05d82): "Possible memory corruption: pmap_pv_remove(0xffffff8023f28d68,0x7f953aea6000,0x100000, 0x100000000, 0xfffffe93a6557530): empty hash"@/SourceCache/xnu/xnu-2782.1.97/osfmk/i386/pmap_internal.h:822
    Backtrace (CPU 4), Frame : Return Address
    0xffffff81eb3f3b80 : 0xffffff800093a811
    0xffffff81eb3f3c00 : 0xffffff8000a05d82
    0xffffff81eb3f3cf0 : 0xffffff8000a065e5
    0xffffff81eb3f3d50 : 0xffffff80009b6b4a
    0xffffff81eb3f3e60 : 0xffffff80009acd2c
    0xffffff81eb3f3e90 : 0xffffff800095c747
    0xffffff81eb3f3ed0 : 0xffffff8000dc45ff
    0xffffff81eb3f3f40 : 0xffffff8000dc425c
    0xffffff81eb3f3f50 : 0xffffff8000e4dcb2
    0xffffff81eb3f3fb0 : 0xffffff8000a3ac46

    BSD process name corresponding to current thread: mcxalr


    Model Name: Mac mini
    Model Identifier: Macmini6,2
    Processor Name: Intel Core i7
    Processor Speed: 2.3 GHz
    Number of Processors: 1
    Total Number of Cores: 4
    L2 Cache (per Core): 256 KB
    L3 Cache: 6 MB
    Memory: 16 GB
    Boot ROM Version: MM61.0106.B03
    SMC Version (system): 2.8f0
    ************************************************

    I've tried the SMC/PRAM reset. The machine has a clean load of Yosemite done from a USB stick. Apple Hardware Test (AHT) gives the ram a clean bill of health.

    Is this possibly a Yosemite thing? A very infrequent hardware bug?
     
  2. ahendarman macrumors member

    ahendarman

    Joined:
    Feb 23, 2013
    #2
    Do you have 3rd party RAM? Try the original and see if the problem persist. There is also a sleep related fix in 10.10.1 make sure you update.
     
  3. jdphoto macrumors 6502

    jdphoto

    Joined:
    Jan 13, 2014
    #3
    Indeed it looks like you have a bad memory stick, hence the "Possible memory corruption" messages. If you got the upgrade through crucial and it's still under warranty I've had good experience getting a new one from them.
     
  4. newellj macrumors 603

    Joined:
    Oct 15, 2014
    Location:
    Boston, MA, US
    #4
    Check both RAM chips for proper insertion. It's easier than you'd think to goof the physical installation of new RAM. :eek:
     
  5. brycenesbitt thread starter macrumors newbie

    Joined:
    Aug 15, 2008
    #5
    OP here: the ram is indeed third party. But the machine runs overnight with memtest86, and completes AHT without error.
     
  6. cinealta macrumors 6502

    Joined:
    Dec 9, 2012
  7. brycenesbitt thread starter macrumors newbie

    Joined:
    Aug 15, 2008
    #7
    Nor does it need to be.
     
  8. blueroom macrumors 603

    blueroom

    Joined:
    Feb 15, 2009
    Location:
    Toronto, Canada
    #8
    Change the RAM back to factory. Macs are fussy about RAM.
     
  9. cinealta macrumors 6502

    Joined:
    Dec 9, 2012
    #9
    No but not all RAM is equal. Some RAM is very finicky. What RAM did you use? Are the specs exactly the same (voltage, speed etc) as factory RAM? Your error report is telling you right there that your memory could be corrupted.
     
  10. newellj macrumors 603

    Joined:
    Oct 15, 2014
    Location:
    Boston, MA, US
    #10
  11. brycenesbitt, Dec 4, 2014
    Last edited: Dec 4, 2014

    brycenesbitt thread starter macrumors newbie

    Joined:
    Aug 15, 2008
    #11
    The memory, installed by a former owner, is Corsair CMSX16GX3M2A1600C10
    The machine passes overnight memtest86 runs.
    Unfortunately I don't have the factory ram.

    The original owner claims the machine ran fine, under the prior OS, for years.
     
  12. cinealta macrumors 6502

    Joined:
    Dec 9, 2012
    #12
    Try replacing it. Corsair is a reseller and not a primary RAM manufacturer. Pity you just missed Cyber Monday sales on RAM.
     
  13. newellj macrumors 603

    Joined:
    Oct 15, 2014
    Location:
    Boston, MA, US
    #13
    There's nothing about Yosemite that should be causing your problems. Have you tried a completely virgin reinstall, from internet recovery rather than from the recovery partition? My Mini was goofy after I reinstalled 10.10 from the recovery partition. A totally virgin installation totally solved the problems.
     
  14. blueroom macrumors 603

    blueroom

    Joined:
    Feb 15, 2009
    Location:
    Toronto, Canada
    #14
    Mavericks & Yosemite use memory more aggressively than previous OSX's. Buy some Apple compatible memory from a vendor that'll allow you to return it if it doesn't solve your problem.

    Plus as the previous post mentioned, it wouldn't hurt to reinstall Yosemite from scratch.
     
  15. tennisproha, Dec 4, 2014
    Last edited: Dec 5, 2014

    tennisproha macrumors 6502a

    Joined:
    Jun 24, 2011
    Location:
    Texas
  16. cinealta macrumors 6502

    Joined:
    Dec 9, 2012
    #16
    Not necessarily but it has to be good quality RAM.
     
  17. brycenesbitt thread starter macrumors newbie

    Joined:
    Aug 15, 2008
    #17
    Note: This machine was clean installed with Yosemite from a USB boot drive.
    The main trouble now is the crash is so infrequent, it's hard to verify any particular action actually changes things.
     
  18. Fishrrman macrumors G4

    Fishrrman

    Joined:
    Feb 20, 2009
    #18
    Suggestion:
    (may or may NOT make a difference)

    Remove, and then reseat, your RAM.
     
  19. brycenesbitt thread starter macrumors newbie

    Joined:
    Aug 15, 2008
    #20
    PRAM reset was already done (mentioned above).
    I just removed and reseated the ram.

    Is there an in-service (while the machine is booted) memory fade test (One that writes a pattern to the memory, and later checks if it's still there)?
     
  20. QuietGamer macrumors member

    QuietGamer

    Joined:
    Nov 23, 2014
    Location:
    US
    #21

    My Bad.
     
  21. brycenesbitt thread starter macrumors newbie

    Joined:
    Aug 15, 2008
    #22
    Ahah. Caught it. Test 12 and 13 (bit fade and hammer) of the current MemTest86 found a problem, perhaps just in one bank. Tests 1-11 all passed multiple times.

    [​IMG]

    Test Start time 2014-12-06 07:40:14
    Elapsed Time 9:58:53
    Memory Range Tested 0x0 - 46F600000 (18166MB)
    Lowest Error Address 0xAD562BC (173MB)
    Highest Error Address 0x464DFEBFC (17997MB)
    Bits in Error Mask 00000000FFBCFF73
    Test 10 [Bit fade test, 2 patterns, 1 CPU] (100%)
    Test 13 [Hammer] 343 Errors
    [Data Error] Test: 13, CPU: 0, Address: 45C3FE7FC, Expected: 00000000, Actual: 02000000
    [Data Error] Test: 13, CPU: 0, Address: 45AC44FAC, Expected: 00000000, Actual: 01000000
    [Data Error] Test: 13, CPU: 0, Address: 459E47154, Expected: 00000000, Actual: 01000000
    [Data Error] Test: 13, CPU: 0, Address: 43A646AD4, Expected: 00000000, Actual: 04000000
    [Data Error] Test: 13, CPU: 0, Address: 439A4668C, Expected: 00000000, Actual: 04000000
     

Share This Page