Skip navigation

Random Kernal Panic in Moutain Lion 10.8.2

152 Views 2 Replies Latest reply: Jan 30, 2013 9:33 AM by shadfar RSS
shadfar Calculating status...
Currently Being Moderated
Jan 29, 2013 7:51 AM

Hello everyone!  I'm pretty new to the Mac World, so i apologize for any dumb questions...but my notebook just randomly kernal panics.   I've repaired disk permissions and even used Disk Warrior to no avail.  It doesn't happen daily, but it still is pretty annoying..Below is my Panic Log, i greatly appreciate any help and your time.  Thank you in advance.




Interval Since Last Panic Report:  619131 sec

Panics Since Last Report:          1

Anonymous UUID:                    0A8FEEE7-EF1B-4275-A09E-C4C5C2CB7563


Tue Jan 29 08:00:13 2013

panic(cpu 6 caller 0xffffff80002c4794): Kernel trap at 0xffffff7f81ddc267, type 14=page fault, registers:

CR0: 0x000000008001003b, CR2: 0xffffff80d49f5a38, CR3: 0x0000000000100000, CR4: 0x00000000001606e0

RAX: 0xffffff7f81e7b520, RBX: 0x0000000000000000, RCX: 0x0000000000000000, RDX: 0x0000000000000008

RSP: 0xffffff80e4193c80, RBP: 0xffffff80e4193cb0, RSI: 0xffffff8014b20000, RDI: 0xffffff80d3a15000

R8:  0x0000000000000000, R9:  0xffffff8014b6d700, R10: 0x0000000000000000, R11: 0x0000000000083d60

R12: 0xffffff80d3a15228, R13: 0xffffff80d49ed000, R14: 0xffffff8014b20000, R15: 0xffffff80d3a15000

RFL: 0x0000000000010286, RIP: 0xffffff7f81ddc267, CS:  0x0000000000000008, SS:  0x0000000000000010

CR2: 0xffffff80d49f5a38, Error code: 0x0000000000000000, Faulting CPU: 0x6


Backtrace (CPU 6), Frame : Return Address

0xffffff80e4193930 : 0xffffff8000220792

0xffffff80e41939b0 : 0xffffff80002c4794

0xffffff80e4193b60 : 0xffffff80002da55d

0xffffff80e4193b80 : 0xffffff7f81ddc267

0xffffff80e4193cb0 : 0xffffff7f81ddbab3

0xffffff80e4193ce0 : 0xffffff7f81ddbdf5

0xffffff80e4193d10 : 0xffffff7f80861832

0xffffff80e4193d50 : 0xffffff7f80893528

0xffffff80e4193dc0 : 0xffffff7f80893d9f

0xffffff80e4193e20 : 0xffffff7f808654c5

0xffffff80e4193e60 : 0xffffff7f80865628

0xffffff80e4193e90 : 0xffffff7f80868fd7

0xffffff80e4193ef0 : 0xffffff800063d4d6

0xffffff80e4193f30 : 0xffffff800063c250

0xffffff80e4193f70 : 0xffffff800063c0f4

0xffffff80e4193fb0 : 0xffffff8000820057

      Kernel Extensions in backtrace:
[D0A1F6BD-E66E-3DD8-9913-A3AB8746F422]@0 xffffff7f80856000->0xffffff7f8088efff

            dependency:[5C23D598-58B2-3204-BC03-BC3C0F00BD32]@0xffffff 7f8082b000
[7C8672C4-8B0D-3CCF-A79A-23C62E90F895]@0xff ffff7f8088f000->0xffffff7f808a0fff

            dependency:[D0A1F6BD-E66E-3DD8-9913-A3AB8746F422]@0 xffffff7f80856000

            dependency:[5C23D598-58B2-3204-BC03-BC3C0F00BD32]@0xffffff 7f8082b000
[7E1D7726-416F-3716-ACCB-E1E276E35002]@0xffffff7f81dd90 00->0xffffff7f81e9bfff

            dependency:[97284661-2629-379E-B86B-D388618E8C30]@0xffffff7f808 a1000

            dependency:[7C8672C4-8B0D-3CCF-A79A-23C62E90F895]@0xff ffff7f8088f000

            dependency:[5C23D598-58B2-3204-BC03-BC3C0F00BD32]@0xffffff 7f8082b000

            dependency:[D0A1F6BD-E66E-3DD8-9913-A3AB8746F422]@0 xffffff7f80856000


BSD process name corresponding to current thread: kernel_task


Mac OS version:



Kernel version:

Darwin Kernel Version 11.4.2: Thu Aug 23 16:25:48 PDT 2012; root:xnu-1699.32.7~1/RELEASE_X86_64

Kernel UUID: FF3BB088-60A4-349C-92EA-CA649C698CE5

System model name: MacBookPro10,1 (Mac-C3EC7CD22292981F)


System uptime in nanoseconds: 514443873268562

last loaded kext at 200013614711833:          3.2.1 (addr 0xffffff7f80d48000, size 36864)

last unloaded kext at 200140857658801:          3.0.6 (addr 0xffffff7f80828000, size 8192)

loaded kexts:          3.0.6          3.2.4b8          4.9.0          70.12          9.8.1          6.0.1          1.7.2          1.9.5d0          3.0          122          100.12.75          2.0.5d3          5.0.0d8          2.2.5a5          2.2.5a5          3.5.9          1.59          5.0.0d8          1.0.0d1          2.0.1d2          4.0.8f17          7.0.0          7.3.2          1.2.3          3.1.33          1.6.0          3.1.33          1.0.33          7.3.2          7.3.2          227.6          4.0.8f17          227.6          1.0.0d1          1.0.0d1          33          404          2.1.0          561.7.22          1.2.2          5.1.0          1.6.1          2.3.1          5.1.0          1.1.0          161.0.0          1.5          1.5          1.7          1.9          1.5          1.6          195.0.0          3.2.30          1.4          8          195.0.0          3.2.1          2.1.0          4.2.0          2.2.5          4.4.8          1.2.5          231.4          4.0.8f17          1.0          1.0          3.2.1          2.2.5a5          80.0.2          10.0.5          2.2.5a5          2.2.5a5          1.8.6fc18          1.3          1.0.10d0          3.1.33          5.1.1d6          3.1.3d10          5.1.1d6          1.0.4          7.3.2          1.0.10d0          7.3.2          2.3.4          2.3.4          4.0.8f17          4.0.8f17          1.8.5          1.8.5          1.2.5          230.5          5.0.0          5.1.0          5.0.0          1.6.0          2.0.3          420.3          1.0.1b1          2.1          5.0.0          2.0.8          5.1.0          1.6.1          1.7.1          1.1          177.8          1.0.0d1          331.7          1.7.2          28.18          1.5          2.7          1.4

Model: MacBookPro10,1, BootROM MBP101.00EE.B02, 4 processors, Intel Core i7, 2.6 GHz, 8 GB, SMC 2.3f32

Graphics: NVIDIA GeForce GT 650M, NVIDIA GeForce GT 650M, PCIe, 1024 MB

Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In, 512 MB

Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54333531533642465238432D50422020

Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54333531533642465238432D50422020

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

Bluetooth: Version 4.0.8f17, 2 service, 18 devices, 1 incoming serial ports

Network Service: Wi-Fi, AirPort, en0

Serial ATA Device: APPLE SSD SM512E, 500.28 GB

USB Device: hub_device, 0x8087  (Intel Corporation), 0x0024, 0x1a100000 / 2

USB Device: FaceTime HD Camera (Built-in), apple_vendor_id, 0x8510, 0x1a110000 / 3

USB Device: hub_device, 0x8087  (Intel Corporation), 0x0024, 0x1d100000 / 2

USB Device: hub_device, 0x0424  (SMSC), 0x2512, 0x1d180000 / 3

USB Device: BRCM20702 Hub, 0x0a5c  (Broadcom Corp.), 0x4500, 0x1d181000 / 5

USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8286, 0x1d181300 / 8

USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0262, 0x1d182000 / 4

MacBook Pro with Retina display, OS X Mountain Lion (10.8.2)
  • Linc Davis Level 10 Level 10 (107,375 points)
    Currently Being Moderated
    Jan 29, 2013 6:27 PM (in response to shadfar)

    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. Sometimes a clean reinstallation (after erasing the startup volume) may solve a problem that isn't solved by reinstalling in place, without erasing.


    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 a fault. A negative test can't be depended on. Run the extended version of the test.


    In the category of obscure bugs, reports suggest that FileVault may trigger kernel traps under some unknown conditions. Most, though 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.