MSSQL services Getting stopped in the AWS server. we have checked a logs getting - SQLException64 Error

Can you share the output of "SELECT @@version"?

Crashes like this often indicates bugs in SQL Server. But since you are on SQL 2016 which is out of mainstream support for more than four years, you chances to get a bugfix are nil.

Crashes can also be due to external software that runs in the SQL Server address space. This includes:

• External stored procedures.
• OLE objects invoked through sp_OAxxxx.
• Unsafe assemblies.
• Third-party linked servers running in-process.

So if you are running any of these, consider them to be prime suspects.

Possibly, such crashes can also be caused by faulty hardware. This is something you would need to sort out with Amazon.

The SQLException64 event and the presence of SQLDump00xx files indicate that the SQL Server process (sqlservr.exe) is crashing and generating a stack dump, which in turn causes the MSSQL service to stop.

To move toward root cause on this AWS Windows Server, use the crash dumps and error logs that are already being produced:

1. Locate and review the SQL Server error logs
   • On Windows, the default error log path is:
     • C:\Program Files\Microsoft SQL Server\MSSQL.<n>\MSSQL\LOG\ERRORLOG.
   • In this case, the dump files are already in:
     • C:\Program Files\Microsoft SQL Server\MSSQL13.MSSQLSERVER\MSSQL\LOG\SQLDump0093.*
   • Open the corresponding ERRORLOG and ERRORLOG.<n> files around the time 3/3/2026 6:04:39 PM to see the exact error and stack dump header that preceded the crash. This will show whether the crash is due to access violation, memory assertion, CLR, OLE DB, etc.
   • If the instance won’t start or is unstable, the logs can still be viewed directly from disk or via SSMS Log File Viewer as described in the documentation.
2. Use the dump files for deeper diagnosis
   • The .mdmp and .txt files (for example SQLDump0093.mdmp, SQLDump0093.txt, SQLDump0093.log) contain the call stack at the time of the crash.
   • These dumps are primarily intended for Microsoft Support or experienced engineers. If the error log shows a repeating pattern (for example, access violation in a specific module, or a known call stack like those documented for certain bugs), correlate that with any custom components (CLR, extended stored procedures, linked servers, third‑party drivers) or recent changes.
3. Correlate with Windows logs
   • Use Windows Event Viewer (Application and System logs) and compare timestamps with the SQL Server error log entries. This helps identify whether there were OS‑level issues (disk, memory, network, or other services) at the same time as the SQLException64 crash.
   • The SQL Server Management Studio Log File Viewer can integrate SQL Server, SQL Server Agent, and Windows logs into a single view to simplify this correlation.
4. Check for known issues and updates
   • The problem signature shows sqllang.dll with a specific build (2015.131.7060.1). Compare this build with the latest cumulative update for SQL Server 2016 and apply the latest CU if not already done, as many crash conditions are fixed in later builds.
   • If the crash pattern matches known issues (for example, access violations or memory assertions similar to those described in Microsoft KB articles that produce stack dumps), applying the relevant hotfix or CU is typically required.
5. Monitor for recurrence and refine logging
   • Since the crash has occurred twice in a month, continue monitoring the SQL Server error log and Windows logs for new occurrences.
   • Ensure error log retention and size are configured so that older logs are not overwritten before analysis (configure maximum number of error logs and size in SSMS under Management → SQL Server Logs → Configure).

If the error log or dump stack shows a specific assertion, access violation, or module name, that information will be the key to the exact root cause and should be used to decide whether to remove/patch a component, change configuration, or open a support case with Microsoft including the .mdmp and ERRORLOG files.

References:

• View the SQL Server error log
• Monitor the error logs
• SQL Server Configuration Manager: Configure SQL Server error logs
• My SQL Server Services getting stopped automatically - Microsoft Q&A
• Error 24-09-2025 08:25:06 Service Control Manager 7034 None The SQL Server (SQLEXPRESS) service terminated unexpectedly. It has done this 1 time(s). - Microsoft Q&A
• SQL Server service stops unexpectedly – Microsoft SQL Server Standard (64-bit) v15.0.4445.1 - Microsoft Q&A