Endpoint Protection

Hello,

Recently, several of our systems are starting to experience BSODs. Overall, we are close to 10,000 SEP managed systems, all running 12.1.4013 and the number of systems with errors is small, when put in perspective. However, all of them exhibit the same problem (picture attached). Searching Google returns that this was an error in the past with some Norton products, but it was apparently resolved. A search of the Symantec forums does not really turn up any info that I could find to help me resolve the problem.

All of our systems have been on 12.1.4013 for quite a while now. We have started to migrate users from Office 2010 to Office 2013 - can that be related? The majority of our systems are 32 bit and the attached pic is from a 32 bit system. This has also happened on a handful of 64 bit systmes (SYMEFA64.SYS). Systems are all Win 7 Enterprise. Otherwise, all the BSODs are somewhat random....

Thanks!!

I believe this was a known issue in this version. Upgrade to 12.1.5 to see if that fixes it.

First step would be to upgrade to 12.1.5..

Working on updating that specific system right now. Not ready (domain wide) to update everything else yet. If this update makes a difference, then that will certainly help me get the change management request approved to update everyone. Currently our SEPMs are running 12.1.4 as well.... Thanks - I'll keep the thread alive with an update or two about the BSOD.

Yup, you can just update a few problem clients firs tto verify. SEPM 12.1.4 will manage 12.1.5 clients just fine.

Keep up posted :)

I do have another post here in the forum about 12.1.4 SEPM and 12.1.5 clients - no matter what I have tried, the 12.1.4 SEPM will not update a client to 12.1.5 - have to run the install manually. But that is a different issue and that thread has seemingly died a peaceful death, no real resolution. The update on this particular system went fine and I am hoping that the end-user will put the machine through the paces. Thanks for the quick replies!! Les

I'd have to look at logs but I can speak from experience it should work fine.

You helped me out some on that thread/problem. I think the log file is posted there. https://www-secure.symantec.com/connect/forums/cannot-create-1215-exported-package-sepm-1214 But again, not worried about that now. Especially now, I just got the word from the boss that I can update the SEPMs to 12.1.5.....

SEPMs are all updated and starting to deploy clients.  The initial post was about a system that was blue screening with an error of SYMEFA.SYS.  That system was one of the first to get updated and so far the user has not called me back (he was calling daily).

 

Regarding the other comment I made here to Brian (about https://www-secure.symantec.com/connect/forums/cannot-create-1215-exported-package-sepm-1214) - I am going to go update that thread.  Even though I updated my SEPMs, I was still having the problem I talked about there.  Tech support helped me solve that issue.