unexplained Kernal Panic

Discussion in 'Mac Pro' started by chama98, Mar 6, 2016.

  1. chama98 macrumors regular

    Feb 13, 2014
    This morning I woke up my mac to find that it had a kernel panic in the early hours of the morning for no expected reason.

    I was wondering if some one could have a look at the log and let me know what it wrong. I have windows 8.1 pro on as a boot camp partition. All software is up to date.


    *** Panic Report ***

    panic(cpu 3 caller 0xffffff801add255a): Kernel trap at 0xffffff7f9c548eb3, type 14=page fault, registers:

    CR0: 0x000000008001003b, CR2: 0x0000000000000000, CR3: 0x000000002ee7a000, CR4: 0x00000000001626e0

    RAX: 0x0000000000000001, RBX: 0x0000000000000000, RCX: 0x0000000000000000, RDX: 0x0000000000000000

    RSP: 0xffffff820a333b70, RBP: 0xffffff820a333c10, RSI: 0xffffff7f9c8e1747, RDI: 0x0000000000000000

    R8: 0xffffff820a333c98, R9: 0x0000000000000074, R10: 0x0000000000000000, R11: 0x0000000000000000

    R12: 0x0000000000000000, R13: 0xffffff7f9c8e1747, R14: 0xffffff81c9923000, R15: 0xffffff7f9c8e1747

    RFL: 0x0000000000010282, RIP: 0xffffff7f9c548eb3, CS: 0x0000000000000008, SS: 0x0000000000000000

    Fault CR2: 0x0000000000000000, Error code: 0x0000000000000000, Fault CPU: 0x3, PL: 0

    Backtrace (CPU 3), Frame : Return Address

    0xffffff820a333800 : 0xffffff801acdf792

    0xffffff820a333880 : 0xffffff801add255a

    0xffffff820a333a60 : 0xffffff801adf0233

    0xffffff820a333a80 : 0xffffff7f9c548eb3

    0xffffff820a333c10 : 0xffffff7f9c47a4a9

    0xffffff820a333c70 : 0xffffff7f9c471733

    0xffffff820a333d20 : 0xffffff7f9c46ee94

    0xffffff820a333db0 : 0xffffff7f9c46e641

    0xffffff820a333de0 : 0xffffff801b2b7ef8

    0xffffff820a333e50 : 0xffffff7f9c46f3d6

    0xffffff820a333e80 : 0xffffff801b293d2d

    0xffffff820a333ec0 : 0xffffff801b293836

    0xffffff820a333f30 : 0xffffff801b28e4ea

    0xffffff820a333f70 : 0xffffff801b2944cc

    0xffffff820a333fb0 : 0xffffff801adccf77

    Kernel Extensions in backtrace:


    dependency: com.apple.driver.corecapture(1.0.4)[B80FBC9C-24F9-3399-B347-01816E4EDD46]@0xffffff7f9c353000

    dependency: com.apple.driver.mDNSOffloadUserClient(1.0.1b8)[DC173C97-9F4D-39D5-8814-68B0BAD27370]@0xffffff7f9c009000

    dependency: com.apple.iokit.IO80211Family(1110.26)[A7F70957-7DBC-39ED-ACA7-3A7BA653D115]@0xffffff7f9c37d000

    dependency: com.apple.iokit.IOPCIFamily(2.9)[F398CE94-0FBD-3E8E-A7AB-55F7F05A81ED]@0xffffff7f9b52c000

    dependency: com.apple.iokit.IONetworkingFamily(3.2)[35F05D83-F2EC-3047-8422-E65BAF0144B2]@0xffffff7f9ba00000

    BSD process name corresponding to current thread: kernel_task

    Boot args:

    Mac OS version:

    Not yet set

    Kernel version:

    Darwin Kernel Version 15.3.0: Thu Dec 10 18:40:58 PST 2015; root:xnu-3248.30.4~1/RELEASE_X86_64

    Kernel UUID: DECC9F02-27D7-31F0-9599-A9EF2873902C

    Kernel slide: 0x000000001aa00000

    Kernel text base: 0xffffff801ac00000

    __HIB text base: 0xffffff801ab00000

    System model name: MacPro6,1 (Mac-F60DEB81FF30ACF6)
  2. chrfr macrumors 604

    Jul 11, 2009
    This indicates it seems to be Wifi related. If it only happens once, I wouldn't be concerned. If it recurs, you may have a hardware problem with the wifi equipment in the computer.
  3. chama98 thread starter macrumors regular

    Feb 13, 2014

Share This Page