Ask Different is a question and answer site for power users of Apple hardware and software. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top
nterval Since Last Panic Report:  835635 sec
Panics Since Last Report:          3
Anonymous UUID:                    FE016DAD-F74D-CFED-FEBF-38D3994B54B5

Fri Jan 11 19:09:31 2013
panic(cpu 0 caller 0xffffff80228b7bd5): Kernel trap at 0xffffff80baddecaf, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0xffffff80baddecaf, CR3: 0x000000002513e000, CR4: 0x00000000000606e0
RAX: 0xffffff80357d6e00, RBX: 0xffffff7fa2f18790, RCX: 0x0000000000000001, RDX: 0x0000000000000000
RSP: 0xffffff8113d2be48, RBP: 0xffffff8113d2be80, RSI: 0xffffff803687ecc0, RDI: 0xffffff80357d6e00
R8:  0x00000000000007d0, R9:  0x0000000000000000, R10: 0x00000000ffffffff, R11: 0xffffff8022e7de88
R12: 0xffffff803687ea00, R13: 0xffffff80367b7c00, R14: 0x0000000036706200, R15: 0x0000000000000001
RFL: 0x0000000000010246, RIP: 0xffffff80baddecaf, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0xffffff80baddecaf, Error code: 0x0000000000000010, Fault CPU: 0x0

Backtrace (CPU 0), Frame : Return Address
0xffffff8113d2bae0 : 0xffffff802281d626 
0xffffff8113d2bb50 : 0xffffff80228b7bd5 
0xffffff8113d2bd20 : 0xffffff80228ce4ed 
0xffffff8113d2bd40 : 0xffffff80baddecaf 
0xffffff8113d2be80 : 0xffffff7fa2f05884 
0xffffff8113d2bf20 : 0xffffff8022c49e4a 
0xffffff8113d2bf60 : 0xffffff802283dcde 
0xffffff8113d2bfb0 : 0xffffff80228b26b7 
     Kernel Extensions in backtrace:[AB9DA44C-0632-35D7-94FE-6D18C4C7ABFA]@0xffffff7fa2f03000->0xffffff7fa2f0ffff

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: 69A5853F-375A-3EF4-9247-478FD0247333
Kernel slide:     0x0000000022600000
Kernel text base: 0xffffff8022800000
System model name: MacBookPro8,3 (Mac-942459F5819B171B)

System uptime in nanoseconds: 3816460790282
last loaded kext at 33635384604:    10.0 (addr 0xffffff7fa4ca8000, size 348160)
last unloaded kext at 425117387768:   5.2.5 (addr 0xffffff7fa320c000, size 65536)
loaded kexts:
com.jft.driver.PdaNetDrv    1.0.64
com.displaylink.driver.DisplayLinkDriver    1.8 10.0   7.0.0  97  1.9.5d0    3.0  3.10  1.60    122   2.3.1f2  4.0.9f33 4.0.9f33    4.0.9f33   100.12.69   2.3.1f2   1.0.0  4.0.9f33    1.0.0   8.0.0    2.0.2d0   1.6.0    3.5.10   1.0.33  1.0.0d1  1.0.0   7.0.0 3.2.11   8.0.0    8.0.0    3.2.11    3.0.2d6  235.4 235.4  320.15 1.0.0d1 1.0.0d1 34    5.2.5 404  2.2.2   602.15.22    3.2.5b3    4.9.6  2.4.1   5.4.0  1.6.1   161.0.0 196.0.0   1.6   1.5  1.7    1.9    1.6  1.6   4.0.39   2   196.0.0 1.0    97   97    97  97   97    97  97 1.0 2.3.1f2   1.8.9fc10    1.6  10.0.6 4.0.9f33 1.0.0 5.2.0d16   1.0.10d0    2.2.5   86.0.3 2.3.1f2 2.3.1f2  1.0.10d0 19.0.26   4.0.9f33    8.0.0   8.0.0   3.2.11   1.0.4   2.3.5    2.3.5   3.1.4d2   3.5.1    1.8.5    1.8.5 1.2.5   3.5.0   3.5.1 235.7  5.2.5    274.7   5.2.5  5.2.5    1.6.0 2.1.1 5.2.5   500.15 1.0.2b1  3.0    4.5.5    2.2.1 5.4.0    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
Model: MacBookPro8,3, BootROM MBP81.0047.B27, 4 processors, Intel Core i7, 2.3 GHz, 8 GB, SMC 1.70f5
Graphics: Intel HD Graphics 3000, Intel HD Graphics 3000, Built-In, 512 MB
Graphics: AMD Radeon HD 6750M, AMD Radeon HD 6750M, PCIe, 1024 MB
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1600 MHz, 0x0198, 0x393930353432382D3034372E4130304C4620
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1600 MHz, 0x0198, 0x393930353432382D3034372E4130304C4620
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xD6), Broadcom BCM43xx 1.0 (
Bluetooth: Version 4.0.9f33 10885, 2 service, 18 devices, 1 incoming serial ports
Network Service: Ethernet Adaptor (en3), Ethernet, en3
Network Service: Wi-Fi, AirPort, en1
Serial ATA Device: M4-CT128M4SSD2, 128.04 GB
Serial ATA Device: WDC WD7500BPKT-00PK4T0, 750.16 GB
USB Device: hub_device, 0x0424  (SMSC), 0x2514, 0xfa100000 / 3
USB Device: ExpCard Adpt, 0x0781  (SanDisk Corporation), 0xb6d0, 0xfa140000 / 6
USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0245, 0xfa120000 / 5
USB Device: BRCM2070 Hub, 0x0a5c  (Broadcom Corp.), 0x4500, 0xfa110000 / 4
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x821a, 0xfa113000 / 7
USB Device: FaceTime HD Camera (Built-in), apple_vendor_id, 0x8509, 0xfa200000 / 2
USB Device: hub_device, 0x0424  (SMSC), 0x2514, 0xfd100000 / 2
USB Device: IR Receiver, apple_vendor_id, 0x8242, 0xfd110000 / 3
share|improve this question

Kernel panics are all but inevitably caused by either hardware problems or rogue kernel extensions--specifically drivers. Panic reports list all the loaded and unloaded extensions in the expectation that the culprit is a non-Apple driver.

In your case, there are two: one for PdaNet and one for DisplayLink. A web search revealed no complaints about the DisplayLink driver's behavior, but the same could not be said for the one from PDANet; it shows up in a large number of KP reports.

I downloaded the PDANet desktop application (iPhone model, version 1.0.64). Glancing through an ASCII dump of the com.jft.driver.PdaNetDrv extension discloses it was built using a 10.6 SDK, so it's quite possible, if not likely, the driver is incompatible with Mountain Lion.

I suggest uninstalling the PDANet application and the driver extension. You should have gotten an uninstall shell script with the installation package which will remove the driver; if not, contact June Fabrics and request one. Simply removing the application will not do the job.

If the panics stop occurring, let a few days go by before you consider the problem solved. It could just be a coincidence, and if another one occurs, you would then almost certainly be looking at a hardware issue.

share|improve this answer

Put in the first Mac OS install disk and reboot holding the D key down. This will cause Hardware test to run. It will test all the hardware. This panic looks like a ram issue. All the numbers are memory address. Most likely you have a ram stick that went bad.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.