BESClient 11.0.6.137 crashing repeatedly with exit code 0xC0000005

Usage and Config Platform
1

Hi everyone,

I am running into a widespread issue in my environment where the BigFix Agent version 11.0.6.137 is crashing repeatedly on multiple endpoints.

The client (BESClient.exe) is failing with exit code 0xC0000005 (a critical Access Violation error). This seems to happen when the client is consuming higher system resources, attempting to read/write to a protected memory location.

A few observations:

  • This behavior appears to be entirely isolated to version 11.0.6.137. Older agent versions (like 11.0.5 or 11.0.4) do not crash in the same environment.

  • I suspect this might be related to a third-party security tool or agent (like an EDR, AV, or 0patch) injecting DLLs into the BESClient process memory space, which this specific BigFix version isn't handling well.

Has anyone else experienced this specific crash with 11.0.6.137? Is this a known bug with this build, and are there any recommended workarounds other than universally downgrading our endpoints back to 11.0.5?

Any insights or specific path/process exclusions that have worked for you would be greatly appreciated!

Thanks in advance.

2

yes! Installation BESClient 11.0.6.137 fails because of error 1920 or 1923 - #7 by Hanz54

3

Yes, unfortunately we were not able to replicate the issue in a dev environment and we had to downgrade some of the agents to 11.0.4. Evidently this is caused by something introduced in 11.0.6 but we never found out.

4

I assume you are referring to Windows devices?

We have a mixture of Nix and Windows servers and not seeing any crashes that i know of. The occasional service “hang” is still around but is no worse/better then any other version. We’re talking like .001% or something.