Mcafee

Cause
The event occurs when the McAfee Agent loads certain DLL files. These libraries (cryptocme2.dll or ccme_base.dll) do not contain a necessary McAfee signaturerequired for inspection by VSE 8.8. This scenario is solved in newer releases of the McAfee Agent.

Solution 1
Identification - Troubleshooting
This step is necessary toidentify other possible causes and to provide the solutions.

Know why the event occurs for your environment - it could be malware.
Review the Event ID to determine whichprocess is involved. Most commonly this is VSTSKMGR.EXE as described in the Problem section. Other process names include MCSHIELD.EXE and SVCHOST.EXE.

Identify theindividual DLL(s) and owning applications for files that load themselves into that process.
Download Microsoft Process Explorer fromhttp://technet.microsoft.com/en-us/sysinternals/bb896653
Run the Process Explorer tool procexp.exe on the computer where you see the event 516.
From the Process Explorer main menu, click Options and selectVerify Image Signatures.
From the main menu click View and select Show Lower Pane.
Click View, Lower Pane View, and select DLLs.
Click View, Select Columns.
In the newwindow click the DLL tab, and select Verified Signer, then click OK.
In the upper pane, expand winnt.exe, services and scroll down, then select VsTskMgr.exe.

The lowerpane now shows all the DLLs that are loaded for the VsTskMgr.exe process.

In the lower pane click the Verified Signer column to organize the DLLs. This allows any unsignedDLLs to be grouped together as Unable to Verify.
Inspect the list of DLLs for non-McAfee and non-Microsoft files (ignoring the file WscAv.dll which is also a McAfee file)