That panic was not caused by third-party software. If the problem is recurrent, the possibilities are:
A stale or corrupt kernel cache
A damaged OS X installation
A fault in a peripheral device, if any
Corrupt non-volatile memory (NVRAM)
An internal hardware fault (including incompatible memory)
An obscure bug in OS X
You may already have ruled out some of these.
Rule out #1 by booting in safe mode and then rebooting as usual. Note: If FileVault is enabled, or if a firmware password is set, or if the boot volume is a Fusion Drive or a software RAID, you can’t do this. Post for further instructions.
You can rule out #2 and #3 by reinstalling the OS and testing with non-essential peripherals disconnected and aftermarket expansion cards removed, if applicable. Sometimes a clean reinstallation may solve a problem that isn't solved by reinstalling in place.
Corrupt NVRAM, which rarely causes panics, can be ruled out by resetting it.
If your model has user-replaceable memory, and you've upgraded the memory modules, reinstall the original memory and see whether there's any improvement. Be careful not to touch the gold contacts. Clean them with a mild solvent such as rubbing alcohol. Aftermarket memory must exactly match the technical specifications of the machine.
Apple Diagnostics or 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, if applicable.
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.
Connecting more than one display is another reported trigger for OS X bugs.
If your system is not fully up to date, running Software Update might get you a bug fix.
Credit to Linc Davis for this response