Application crashing -The process was terminated due to an unhandled exception.

Question

Environment : OS Microsoft Windows Server 2019

Dotnet framework: 4.7

SQL : SQL Server 2019

Note: Previously our application was working fine in 2016 OS. Once we upgraded to OS 2019 we are facing below issue

Application level - Event viewer log

Faulting application name: XXXX.exe, version: XXXX, time stamp: 0x66338cfc Faulting module name: ntdll.dll, version: 10.0.17763.5458, time stamp: 0x761f6403 Exception code: 0xc0000005 Fault offset: 0x00056007 Faulting process id: 0x3a9c Faulting application start time: 0x01daa07dba30b473 Faulting application path: C:\Program Files (x86)\XXX.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id: 41b0c901-aa9f-460b-a492-487d8ccd1b58 Faulting package full name: 

Dotnet run time Level - Event Viewer log

Application: XXXX.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: exception code c0000005, exception address 77D26007 Stack:

We are using some Avaya dlls(C#) in our CPP code.

awaiting for the reply

Regards,

Chandra

Answer 1

Hello

Is it possible to reinstall the software or perform a repair install or update to the latest version from the software website?

For analyzing a application crash issue, the dump may be usefule.

We could open administrator command line, run the following command then reboot. You will get a crash dump in C:\crashdumps folder once the application crashed agagin.

Reg Add "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps" /f

Reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps" /V DumpFolder /t REG_SZ /D "C:\CrashDumps" /f

MD C:\CrashDumps

Reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps" /V DumpType /t REG_DWORD /D 2 /f

Reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps" /V DumpCount /t REG_DWORD /D 10 /f

Here is the steps for configuring windbg for analyzing dump.

Debugging steps

1. Verify that the computer is set up to generate a complete memory dump file when a crash occurs. For more information, see Method 1: Memory dump.
2. Locate the memory.dmp file in your Windows directory on the computer that is crashing, and copy that file to another computer.
3. On the other computer, download the Windows 10 SDK.
4. Start the install and choose Debugging Tools for Windows. The WinDbg tool is installed.
5. Go to the File menu and select Symbol File Path to open the WinDbg tool and set the symbol path.
   1. If the computer is connected to the internet, enter the Microsoft public symbol server: https://msdl.microsoft.com/download/symbols and select OK. This method is recommended.
      1. If the computer isn't connected to the internet, specify a local symbol path.
      2. Select Open Crash Dump, and then open the application.dmp file that you copied.
      3. Run "!analyze -v", you will get the crash application call stack.

You may ask for help from the application support as the symbol file for the third party application is only available from the application developer.