Mac rebbots itself periodically

Hi - i have an issue with a macbook where it reboots itself periodically, and gives the following error report. I'm not sure whether its helpful, but its the only thing i have :)  - Any help would be appreciated!

Anonymous UUID:       DD9ED56C-4651-55C1-BCA5-E23E857C36FF

Mon Jul  7 18:34:17 2014
panic(cpu 0 caller 0xffffff801aa14e5b): "soclose: NOFDREF"@/SourceCache/xnu/xnu-2422.100.13/bsd/kern/uipc_socket.c:1136
Backtrace (CPU 0), Frame : Return Address
0xffffff8124d638d0 : 0xffffff801a622fa9
0xffffff8124d63950 : 0xffffff801aa14e5b
0xffffff8124d639a0 : 0xffffff801aa32785
0xffffff8124d639c0 : 0xffffff7f9cad6f86
0xffffff8124d63ab0 : 0xffffff7f9cad3a8b
0xffffff8124d63cf0 : 0xffffff801a9c9ddd
0xffffff8124d63d30 : 0xffffff801aa16778
0xffffff8124d63e20 : 0xffffff801a9f71d0
0xffffff8124d63e50 : 0xffffff801a9f22f1
0xffffff8124d63ef0 : 0xffffff801a9f21dd
0xffffff8124d63f50 : 0xffffff801aa40653
0xffffff8124d63fb0 : 0xffffff801a6f3c56
      Kernel Extensions in backtrace:[9D914876-4363-3882-961E-22323F1FCC62]@0xffffff7f9cad2000->0xffffff7f9cad9fff

BSD process name corresponding to current thread: socketfilterfw

Mac OS version:

Kernel version:
Darwin Kernel Version 13.2.0: Thu Apr 17 23:03:13 PDT 2014; root:xnu-2422.100.13~1/RELEASE_X86_64
Kernel UUID: ADD73AE6-88B0-32FB-A8BB-4F7C8BE4092E
Kernel slide:     0x000000001a400000
Kernel text base: 0xffffff801a600000
System model name: MacBookPro6,2 (Mac-F22586C8)

System uptime in nanoseconds: 14255425950281
last loaded kext at 13641358664877:      104 (addr 0xffffff7f9cb5c000, size 49152)
last unloaded kext at 13933407380250:      104 (addr 0xffffff7f9cb5c000, size 32768)
loaded kexts:      11.1      8.0.1      1.60      1.9.5d0      100.14.15      3.0      4.2.4f1      124      8.2.4      8.2.4      2.6.1f2      2.6.1f2      8.2.4      3.5.13      4.2.4f1      1.0.0d1      7.0.0      1      3.0.4d1      1.0.0      1.0.0      2.0.4d1      1.7.0      3.5.26      1.1.12      240.2      1.0.0d1      1.0.0d1      35      240.2      325.7      3.4.1      3.6.6      404      2.5.1      666.4.0      700.20.22      5.0.2      3.8.1b2      3.0.0      660.4.0      161.0.0      2.0      2.0      1.8      2.1      2.0      1.7      217.92.1      153      3      217.92.1      1.0      3.5.26      1.0      10.0.7      8.2.4      2.6.1f2      1.0.0      1.9.7fc2      1.14      8.2.4      4.2.4f1      91.1      4.2.4f1      1.0.0      2.2.6      2.6.1f2      2.6.1f2      3.1.8      1.0.12d1      5.7.0d11      3.5.26      1.0.4      2.4.1      1.0.11d1      2.4.1      240.9      660.4.0      3.6.6      3.6.0      650.4.0      656.4.1      3.6.6      1.7      1.7.1      1.7.1      2.6.1      3.6.6      660.4.2      630.35      4.5.5      1.0.3b4      1.0.1b5      3.2      2.6.5      677.4.0      2.0      2.0      2.0.0      1.1      278.11      1.0.0d1      7      2      371.1      1.9      23      28.30      2.0      2.9      1.4      1      1.0
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Tyler VerkadeCommented:
I would try first running the Apple Hardware Test (AHT) on your MacBook to see if it comes up with anything.
You can find information on that here:

If that doesn't detect any issues, I would try starting up your Mac in SafeMode and see if you still have the same problem.

You may need to reinstall your operating system if you don't find any issues in AHT, and honestly an operating system reinstall would be favorable over failing hardware, at least it would be in my opinion.

Best of luck!
Looks like you might be having a kernel panic; which usually is some software issue, although I don't know that it can't also be caused by hardware. Not sure if it's significant, but the reference to the firewall may be telling. If it's on, try turning it off temporarily especially if you're at home and behind a router of some kind. If you go on a public wireless, turn it back on.  See if that makes a difference.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Mac OS X

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.