Skip navigation

Error - Problem... computer must restart?

166 Views 1 Reply Latest reply: Jan 11, 2013 1:10 PM by Linc Davis RSS
brodieb Calculating status...
Currently Being Moderated
Jan 10, 2013 8:27 PM

This problem has occured on a regular basis recently. Below is the system diagnostics report. Help interpreting and fixing this is appreciated. Thanks in advance!






Thu Jan 10 20:20:46 2013

panic(cpu 0 caller 0xffffff80048b7bd5): Kernel trap at 0xffffff7f85048d39, type 14=page fault, registers:

CR0: 0x000000008001003b, CR2: 0xffffff80112c40b8, CR3: 0x00000000074f6000, CR4: 0x0000000000000660

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

RSP: 0xffffff807dca35a0, RBP: 0xffffff807dca35e0, RSI: 0xffffff80112c2004, RDI: 0xffffff80112c2004

R8:  0x0000000000000000, R9:  0x0000000000000000, R10: 0x0000000000000000, R11: 0xffffff8069489000

R12: 0xffffff80112c2804, R13: 0xffffff8011299804, R14: 0xffffff80112c2004, R15: 0xffffff801128c004

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

Fault CR2: 0xffffff80112c40b8, Error code: 0x0000000000000000, Fault CPU: 0x0



Backtrace (CPU 0), Frame : Return Address

0xffffff807dca3240 : 0xffffff800481d626

0xffffff807dca32b0 : 0xffffff80048b7bd5

0xffffff807dca3480 : 0xffffff80048ce4ed

0xffffff807dca34a0 : 0xffffff7f85048d39

0xffffff807dca35e0 : 0xffffff7f852c4875

0xffffff807dca3630 : 0xffffff7f853730e5

0xffffff807dca36d0 : 0xffffff7f84f9857b

0xffffff807dca3760 : 0xffffff7f84f9c20a

0xffffff807dca3950 : 0xffffff7f84f9d0d6

0xffffff807dca3a30 : 0xffffff7f851929ff

0xffffff807dca3ae0 : 0xffffff7f8518761c

0xffffff807dca3c60 : 0xffffff7f84f333c7

0xffffff807dca3cd0 : 0xffffff7f84f1d57b

0xffffff807dca3d40 : 0xffffff7f84f201b8

0xffffff807dca3db0 : 0xffffff7f84f1fdb4

0xffffff807dca3e10 : 0xffffff7f84ee6c04

0xffffff807dca3e50 : 0xffffff7f84ee5eef

0xffffff807dca3e80 : 0xffffff7f84ee52cb

0xffffff807dca3ef0 : 0xffffff8004c472a8

0xffffff807dca3f30 : 0xffffff8004c45daa

0xffffff807dca3f80 : 0xffffff8004c45ed9

0xffffff807dca3fb0 : 0xffffff80048b26b7

      Kernel Extensions in backtrace:
[803496D0-ADAD-3ADB-B071-8A0A197DA53D]@0 xffffff7f84ed8000->0xffffff7f84f0ffff

            dependency:[B1B77B26-7984-302F-BA8E-544DD3D75E73]@0xffff ff7f84e8d000
[86DDB71C-A73A-3EBE-AC44-0BC9A38B9A44]@0xff ffff7f84f1b000->0xffffff7f84f2cfff

            dependency:[803496D0-ADAD-3ADB-B071-8A0A197DA53D]@0 xffffff7f84ed8000

            dependency:[B1B77B26-7984-302F-BA8E-544DD3D75E73]@0xffff ff7f84e8d000
[A4C53A36-22B6-3075-82B9-9DE612A9C015]@0xffffff7f84f2f 000->0xffffff7f85231fff

            dependency:[B1B77B26-7984-302F-BA8E-544DD3D75E73]@0xffff ff7f84e8d000

            dependency:[86DDB71C-A73A-3EBE-AC44-0BC9A38B9A44]@0xff ffff7f84f1b000

            dependency:[803496D0-ADAD-3ADB-B071-8A0A197DA53D]@0 xffffff7f84ed8000
[9F3D09B5-3158-3D9E-BDA3-E71576AAD3B7]@0xffffff7f8 523f000->0xffffff7f85561fff

            dependency:[A4C53A36-22B6-3075-82B9-9DE612A9C015]@0xffffff7f84f 2f000

            dependency:[B1B77B26-7984-302F-BA8E-544DD3D75E73]@0xffff ff7f84e8d000



BSD process name corresponding to current thread: kernel_task



Mac OS version:




Kernel version:

Darwin Kernel Version 12.2.0: Sat Aug 25 00:48:52 PDT 2012; root:xnu-2050.18.24~1/RELEASE_X86_64

Kernel UUID:

Kernel slide:     0x0000000004600000

Kernel text base: 0xffffff8004800000

System model name: MacBookAir3,2 (Mac-942C5DF58193131B)



System uptime in nanoseconds: 4989232612881

last loaded kext at 364659532286:          1.8 (addr 0xffffff7f84df7000, size 229376)

last unloaded kext at 437070642482:          3.0.1 (addr 0xffffff7f86998000, size 8192)

loaded kexts:          1.8          1.60          3.0          3.10          1.9.5d0          4.0.9f33          100.12.69          2.0.5d4          2.3.1f2          1.0.0d1          7.0.0          3.2.11          122          4.0.9f33          2.3.1f2          1.0.0          1.6.0          170.2.3          3.5.10          1.0.33          8.0.0          235.4          235.4          3.1.0          1.0.0d1          1.0.0d1          34          404          2.2.2          602.15.22          5.2.5          5.2.5          5.4.0          2.4.1          161.0.0          1.6.1          1.5          1.7          1.6          1.9          1.6          1.6          196.0.0          4.0.39          2          196.0.0          1.0          10.0.6          2.3.1f2          1.8.9fc10          1.6          86.0.3          4.0.9f33          4.0.9f33          2.3.1f2          2.3.1f2          1.0.10d0          3.1.4d2          1.0.0          5.2.0d16          3.2.11          1.0.4          1.0.10d0          8.0.0          8.0.0          2.3.5          2.3.5          235.7          5.2.5          3.5.1          3.5.0          3.5.1          5.2.5          5.2.5          2.2.9          500.15          3.0          1.11          5.2.5          5.4.0          2.2.1          1.6.1          1.8.0          1.1          220          1.0.0d1          7          344          1.8          28.21          1.6          2.7.2          1.4          1.0

MacBook Air (13-inch Late 2010), OS X Mountain Lion (10.8.2)
  • Linc Davis Level 10 Level 10 (107,850 points)
    Currently Being Moderated
    Jan 11, 2013 1:10 PM (in response to brodieb)

    That panic was not caused by third-party software. If it's happened only once, and is not repeated in at least a few thousand hours of use, a reasonable choice would be to ignore it. Machines don't work perfectly. They never will.


    If the problem is recurrent, the possibilities are (1) a damaged OS X installation; (2) a fault in a peripheral device, if any; (3) an internal hardware fault; and (4) an obscure bug in OS X.


    You can rule out the first two possibilities by reinstalling the OS and testing with non-essential peripherals disconnected and aftermarket expansion cards removed, if applicable.


    If you've recently upgraded the memory, reinstall the original memory and see whether there's any improvement. Be careful not to touch the gold contacts on the memory modules when handling them. If necessary, clean them with a mild solvent such as rubbing alcohol.


    The Apple Hardware Test, though generally unreliable, will sometimes detect memory faults. A negative test can't be depended on.


    In the category of obscure bugs, reports suggest that FileVault may trigger kernel traps under some unknown conditions. Most, if not all, of these reports seem to involve booting from an aftermarket SSD. If those conditions apply to you, try deactivating FileVault.


    Otherwise, make a "Genius" appointment at an Apple Store to have the machine tested. You may have to leave it there for several days. There isn't much point in doing this unless you can reproduce the panic, or if you can't, it happens often enough that it's likely to be repeated at the store. Otherwise you may be told that nothing is wrong.


    Print the first page of the panic report and bring it with you.


    Back up all data on the internal drive(s) before you hand over your computer to anyone. If privacy is a concern, erase the data partition(s) with the option to write zeros* (do this only if you know how to restore, and you have at least  two independent backups.) Don’t erase the recovery partition, if present.


    *An SSD doesn't need to be zeroed.


More Like This

  • Retrieving data ...

Bookmarked By (0)


  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.