SQL Server 2022 CU18 Crashing with EXCEPTION_ACCESS_VIOLATION

Anonymous
2025-03-18T23:00:19.1266667+00:00

SQL Server 2022 CU18 is experiencing crashes approximately 1-2 times a month since installation. The error log shows the following message:

2025-03-18 08:20:04.77 spid70 SqlDumpExceptionHandler: Process 70 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.

The stack dump details include:

2025-03-18 08:20:04.77 spid70 * BEGIN STACK DUMP:

2025-03-18 08:20:04.77 spid70 * 03/18/25 08:20:04 spid 70

2025-03-18 08:20:04.77 spid70 *

2025-03-18 08:20:04.77 spid70 *

2025-03-18 08:20:04.77 spid70 * Exception Address = 0000023996E87DE0 Module(UNKNOWN)

2025-03-18 08:20:04.77 spid70 * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION

2025-03-18 08:20:04.77 spid70 * Access Violation occurred writing address 0000023996E87DE0

2025-03-18 08:20:04.77 spid70 * Input Buffer 504 bytes -

2025-03-18 08:20:04.77 spid70 * SET TRANSACTION ISOLATION LEVEL READ COMMITTED;

2025-03-18 08:20:04.77 spid70 * EXECUTE dbo.setContextInfo @StrCompany=N' ', @strU

2025-03-18 08:20:04.77 spid70 * serName=N'TESTUSER', @StrCultureName='en-US', @StrAuditingE

2025-03-18 08:20:04.77 spid70 * nabled='Y', @StrAuditSource=N'DTK';

Analysis of the dump file reveals:

STACK_COMMAND: ~0s; .ecxr ; kb

SYMBOL_NAME: sqllang+e072

MODULE_NAME: sqllang

IMAGE_NAME: sqllang.dll

FAILURE_BUCKET_ID: SOFTWARE_NX_FAULT_c0000005_sqllang.dll!Unknown

OS_VERSION: 10.0.20348.1

BUILDLAB_STR: fe_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

IMAGE_VERSION: 2022.160.4185.3

FAILURE_ID_HASH: {59f8ba3b-e82a-323d-1f68-12f12220217a}

What steps can be taken to troubleshoot this issue further or resolve it?

SQL Server Database Engine
{count} votes

2 answers

Sort by: Most helpful
  1. Erland Sommarskog 128.9K Reputation points MVP Volunteer Moderator
    2025-03-18T23:06:22.03+00:00

    I would recommend that you open a support case. Crashes like this are often token of bugs in SQL Server. Although, you may want to check if you are using of these:

    • Extended stored procedures.
    • Unsafe assemblies.
    • sp_OAxxxxx.
    • Linked servers to non-Microsoft data sources that run in-process.

    These are components that could scribble the memory and pull the rug for SQL Server.

    It is very difficult to analyse these stack dumps without access to the source code, hence my suggestion to open a support case.


  2. Olivier Castonguay 0 Reputation points
    2025-04-03T16:52:36.0866667+00:00

    Hi !

    I was wondering if you had any come back from Microsoft regarding this?

    Also, just to make sure you're saying it happens 1-2 times a month but CU18 was released on March 13th. Is there something I am missing?

    Thank you

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.