The conversation on the company ControlUp discusses a crash occurring with the SECOCL64.exe application. Possible causes mentioned include a bug in the application binary, incompatible DLL injection, or a corrupt installation. It is suggested to check the event viewer, verify the installed version, and look for conflicting software. Other solutions suggested include reinstalling or repairing the application and checking for Windows updates. A custom dashboard will soon be released to make it easier to track crashes in an organization. It is also recommended to update audio drivers and disable DLL injections. Registries to enable crash dumps for SECOCL64 are provided for root cause proof.
Read the entire ‘Troubleshooting the SECOCL64.exe Crash in ControlUp.’ thread below:
Good day All
Hope that all are well
anyone else see this crash
Faulting application name: SECOCL64.exe, version: 2.0.11.35, time stamp: 0x650400f8
Faulting module name: SECOCL64.exe, version: 2.0.11.35, time stamp: 0x650400f8
Exception code: 0xc0000409
0xc0000409 means stack corruption → most likely a bug in that version of SECOCL or conflict with injected DLL
Exception Code 0xc0000409
• This is a STATUS_STACK_BUFFER_OVERRUN error.
• It means Windows detected a buffer overrun / stack corruption in the application.
• Typically causes:
◦ Bug in the application binary (`SECOCL64.exe`).
◦ Incompatible DLL injection or hook (e.g., AV/security software, Citrix hooks, injection, etc.).
◦ Corrupt installation or mismatched versions of the SECOCL driver/client.
Check Event Viewer
• Look under Windows Logs → Application for the crash event.
• Confirm if any Faulting module path is shown (sometimes it’s a DLL instead of the EXE).
Verify Installed Version
• Check if you have the latest SafeNet Authentication Client / SECOCL component.
• Compare against vendor release notes – older versions are known to crash on newer Windows builds.
Look for Conflicting Software
• AV/security agents (CrowdStrike, SentinelOne, Sophos, McAfee, etc.)
• App virtualization or DLL injectors (Citrix, etc.).
• Try disabling injection features temporarily to confirm.
Reinstall / Repair
• Download the matching version of the SafeNet Authentication Client from Thales.
• Uninstall → reboot → reinstall cleanly.
Check Windows Updates
• Sometimes after a Windows patch (especially .NET or kernel updates), older SECOCL builds start failing.
• Updating to the vendor’s supported version usually resolves it.
Memory Dump (advanced)
• Enable crash dumps for the process to capture the faulting thread.
• This helps confirm whether the exception is inside SECOCL code or triggered by an injected DLL.
u will prob need the dump to see what DLL injection is causingthe issue
Hi @member, looking on our global database, I see SECOCL64.exe crashing at 134 organisations, but usually only on a handful of devices per org
I see crashes also with version 2.0.11.61, but nothing newer than that
We see it on 2.0.11.35
per Gemini, this process is usually related to the Audio card drivers that come with the PC Manufacture (e.g. HP, Dell..)
yep, it seems many crashes occur with 2.0.11.35
I suggest updating thePC drivers via HP, Dell or Lenovo process, and check if it fixes the issue
Hi , Already done that 🙂 even run a
sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth
no issues
Love that you can see that … now only if there was a dashboard that we can see that 😄 😄 😄 😄 lol
similar complaint from a HP user… – https://h30434.www3.hp.com/t5/Notebook-Audio/I-have-SECOCLx64-that-continues-to-just-crash-causing/td-p/8991829
we shall soon release a Custom Dashboard that will make it much easier to see app crashes in your org
Yes, same here ,
got you
I guess something is off on these specific PC’s, best next steps is to update audio drivers to latest version I guess
Can you Run the below on one or two of the devices to see what DLLs are been incjected
◦ Run `tasklist /m /fi "imagename eq SECOCL64.exe"` → see which DLLs are injected.
◦ If you see AV/security/Citrix/ DLLs, test with them disabled.
I did that , will send you the screenshot in DM
Enable crash dump for SECOCL64 (if you need root cause proof)
Registry:HKLM\Software\Microsoft\Windows\Windows Error Reporting\LocalDumps\SECOCL64.exe
DumpFolder = C:\Dumps
DumpType = 2 (full dump)
Reproduce crash → collect dump → analyze in WinDb
Continue reading and comment on the thread ‘Troubleshooting the SECOCL64.exe Crash in ControlUp.’. Not a member? Join Here!
Categories: All Archives, ControlUp Dashboards, ControlUp for Desktops