My computer experienced a kernel panic while running the process lasievef_1.10_x8. I have previous experienced kernel panics while running WUs from another BOINC project, World Community Grid, which have implicated the Autodock program. I am curious as to whether NFS runs Autodock, or another docking program, which may be not playing nice with 10.8.2. Of note, I have run work units for a dozen other BOINC projects without difficulty, so I do not believe it is the BOINC client itself causing the issue; nor have I been able to find anything within the error logs to indicate a problem with RAM or the graphics processor.

If someone can provide additional information, or has heard anything about NFS projects causing these issues on other computers running 10.8.2, I would be greatly appreciative. Thank you.

Nope, NFS@Home does not run Autodock.
lasievef can consume hundreds of MBs of RAM per WU, but in any well-behaved OS (and MacOS X is usually classified as one), if the OS cannot allocate enough memory, it tends to kill applications instead of yielding a panic.
(unless, of course, it's configured to panic when it's out of memory; Linux can be configured that way, I don't know about MacOS X).

Do you have special device drivers or applications ?
Do you leave dozens of applications open for weeks on your MacOS X computer ?
How much RAM does your computer have ?

No special device drivers or applications that I know of.

12 GB RAM. I did put in two new blocks of 8 last week, and I do know that that's a potential source of kernel panics; however, testing the RAM has not yielded any problems, and the error logs make no mention of anything going odd with the RAM. Additionally, I had quite a bit of available RAM when I turned in for the night, on account of having experienced kernel panics earlier that day and having had fewer programs open in order to test the RAM, so there should have been ample RAM available for NFS to use.

I do have a tendency to leave about 7-8 applications open for prolonged periods of time. However, this computer is a very recent acquisition, and I have not had time to leave these applications on for prolonged periods of time on this configuration. Additionally, I have done the same for all my previous computers and have never experienced a kernel panic that wasn't associated with a hardware failure.

These kernel panics have only occurred after starting an application through BOINC that has not been run on this configuration. Yesterday it was WCG applications using Autodock. Today it was NFS. I have not experienced problems with the majority of projects I am linked to - I've run work units for over a dozen other projects without incident.

I consider it possible that something in the process is not playing well with 10.8.2. Considering that it is a recent update, there's a chance that there are some bugs. I have saved the logs of the last three kernel panics and looked into the information contained within. There have not been a lot of conclusive results, but I have seen a significant number of reports of kernel panics in 10.8.2 - none that were specifically linked to BOINC, NFS, or WCG, but often to applications that weren't working together well with the OS.

Of course, so far I've yet to hear of any pattern of panics for either project. It's possible that this is simply because few Macs running 10.8.2 are using BOINC and connected to these projects. It's also possible that it is a problem localized to my machine, though I'm hard-pressed to find good supporting evidence for that within the logs (different CPUs have been involved, the backtraces have not consistently marked offending extensions, no indication of RAM faults, etc.).

In any event, I wanted to bring it to attention. If a pattern does emerge, then it can be addressed. I'm continuing to monitor the situation on my computer, and if I determine anything more, I will present it here.

Does not appear that NFS tasks were actually causing the problem. Even though none of my tests have indicated as such, I've replaced the RAM and that appears to have cleared up the issue.