Hi!
I've made same question here, but this seems a more technical place.
I'm debugging a crash of an application in Microsoft Windows Server 2019 Datacenter [Ver: 10.0.17763.4131].
This is the basic information
Faulting application name: wazuh-agent.exe, version: 0.0.0.0, time stamp: 0x643571e1
Faulting module name: RPCRT4.dll, version: 10.0.17763.4252, time stamp: 0xa85fd1e2
Exception code: 0xc0000005
Fault offset: 0x000281cb
Faulting process id: 0x93c
Faulting application start time: 0x01d97e69405fd862
Faulting application path: C:\Program Files (x86)\ossec-agent\wazuh-agent.exe
Faulting module path: C:\WINDOWS\System32\RPCRT4.dll
Report Id: 3b1c0bfd-324b-4357-b758-370aee2e848e
Faulting package full name:
Faulting package-relative application ID:
After analyzing a core dump, we were able to get a backtrace
Entry point cryptnet!CryptRetrieveObjectByUrlWithTimeoutThreadProc
Create time 5/29/2023 5:30:33 AM
Time spent in user mode 0 Days 0:0:0.15
Time spent in kernel mode 0 Days 0:0:0.31
rpcrt4!NdrGetBuffer+3b
rpcrt4!NdrAsyncClientCall+1ce
winnsi!RpcNsiRegisterChangeNotification+23
winnsi!NsiRpcRegisterChangeNotificationEx+147
winnsi!NsiRpcRegisterChangeNotification+49
IPHLPAPI!InternalRegisterChangeNotification+7b
IPHLPAPI!NotifyIpInterfaceChange+6e
winhttp!NetworkChangeMonitor::Startup+79
winhttp!StartGlobalNetworkChangeMonitor+4e
winhttp!WxRegisterForNetworkChangeNotification+35
winhttp!InitializeNetworkChangeMonitor+64
winhttp!INTERNET_SESSION_HANDLE_OBJECT::LoadAutomaticProxyResolvers+90
winhttp!INTERNET_SESSION_HANDLE_OBJECT::SetProxySettings+77
winhttp!WinHttpSetOptionInternal+8b1
winhttp!WinHttpOpen+3cd
cryptnet!InetGetBindings+1a
cryptnet!CInetSynchronousRetriever::RetrieveObjectByUrl+160
cryptnet!InetRetrieveEncodedObject+58
cryptnet!CObjectRetrievalManager::RetrieveObjectByUrl+9f
cryptnet!CryptRetrieveObjectByUrlWithTimeoutThreadProc+80
kernel32!BaseThreadInitThunk+19
ntdll!__RtlUserThreadStart+2f
ntdll!_RtlUserThreadStart+1b
But still, it isn't clear why our application is calling this thread.
Is it a know issue related to the library version?
Should we install a specific KB to fix it ?
Thank you.