
Symantec released this today:
We confirmed you are actually dealing with a known issue we found in SEP 14, that has to do with how we are handling network scans, and how Microsoft handles certain issues, such as "Offline File Caching".
Our official fix should be out in a couple of weeks as SEP 14 MP1. In the meantime, you should be able to change one setting in the SEPM/SEP clients that has been known to resolve this issue.
What I would like to ask/suggest, is to disable the network scanning portion of the SEP auto protect policy. To do this, please navigate to the following location on your SEPM:
SEPM > Policies > Virus and Spyware Protection > Auto-Protect > Under Network Settings > Uncheck the box that says "Scan files on remote computers".
Once SEP 14 MP1 is released, you should be able to re-enable the network scanning option, and no longer see this BSOD
*This post is locked for comments
I have the same question (0)Microsoft's answer was to increase memory on the computer and/or upgrade from 7 to 8.1 or 10.