I am seeing the event logs fill up on Windows 10 systems with the following errors:
Faulting application name: fcags.exe, version: 11.0.700.18, time stamp: 0x5bf3a399
Faulting module name: fcags.exe, version: 11.0.700.18, time stamp: 0x5bf3a399
Exception code: 0xc0000005
Fault offset: 0x00000000001e8a6d
Faulting process id: 0x57498
Faulting application start time: 0x01d5ad35b2f2d24c
Faulting application path: C:\Program Files\McAfee\DLP\Agent\fcags.exe
Faulting module path: C:\Program Files\McAfee\DLP\Agent\fcags.exe
Report Id: 0cf28c97-0b28-4eb2-99d2-0fb224351a0b
Faulting package full name:
Faulting package-relative application ID:
The errors are generated over and over every minute (and numerous machines have this issue). Is this an actual problem with the DLP agent or is this just noise?
Has anyone else seen this? I am running ePO 5.10 with DLPe 11.0.700 and ENS 10.6.1.
I read through Data Loss Prevention 11.x.x Known Issues and found the following workaround for version 11.0.400 for a similiar issue. However I do not see where to add the process name in the Windows Client configuration of DLP policy. (Technical Articles ID: KB89301)
Issue: An error appears in the Windows 10 Event Viewer shows one or more of the following:
Faulting module name: fcagpph32.dll
Faulting module name: fcagpph64.dll
Faulting module name: fcagcbh32.dll
Faulting module name: fcagcbh64.dll
Workaround: Add the process name that appears in the event viewer error, to clipboard whitelisted processes in Windows Client configuration.
I submitted an SR with McAfee Support. They advised since 11.0.700 is going end of life in March, I needed to upgrade to version 11.3 and see if the issue persists. I upgraded two devices and so far the errors are no longer showing up in event viewer logs.
Hi @ReallyWhy ,
Thank you for writing in here.
Application error ID 1000 means that DLP is getting crashed.
Is this a problem only on one machine? Windows version along with the build number?
Kindly make sure you have the exclusions set for DLP in ENS as per the article below,
Then, make sure you have DLP access protection enabled, DLP watchdog services enabled in the DLP Windows Client Configuration policy.
If fcag.exe still crashes after performing the above, kindly make sure you enable debug logging for DLP and enabling dump creation for fcag.exe process using the windows client configuration policy. Make sure that you assign a separate windows client config policy with debug and dump enabled only to this machine.
The next time when fcag.exe crashed after assigning the debug policy, kindly collect the MER and submit to the SR for further troubleshooting from the Support Engineer.
Was my reply helpful?
If you find this post useful, Please give it a Kudos! Also, Please don't forget to select "Accept as a solution" if this reply resolves your query!
Hi @ReallyWhy ,
Thank you for the update. We would need to analyze the crash dumps for this fcag.exe which is getting crashed frequently to understand why its crashing.
Let us wait for further update from Technical Support in here.