how troubleshoot SqlDumpExceptionHandler: Process 113 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process

Ted Yin 0 Reputation points
2024-05-02T02:52:39.4733333+00:00

We use Cumulative Update 21 for SQL Server 2019, Always on with 1 Primary plus 2 secondary replicas. Recently we noticed our SQL Server had some dumps, like below. Can anyone pls help advise how troubleshoot it? Thanks

SqlDumpExceptionHandler: Process 113 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
12,912 questions
0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. LucyChenMSFT-4874 1,430 Reputation points
    2024-05-02T07:22:30.2633333+00:00

    Hi @Ted Yin,

    Thanks for your information.

    This may be a bug fixed in CU release, I've checked the CU 22:

    • 2330261: Fixes an assertion dump issue (Location: sebind.h:1206; Expression: bufferLen >= colLen) that you encounter when running an INSERT statemstatement against the table that has the nvarchar(n) column as an index column.
    • 2126481: Fixes an access violation dump issue that you might encounter when resuming an index rebuild that includes partitions (for example, ALTER INDEX [index_name] ON [schema].[TableName] RESUME WITH ( MAX_DURATION = 1, MAXDOP = 1 )).

    I suggest you update the latest SQL Server 2019 CU.

    Feel free to share your issue with us here.

    Best regards,

    Lucy Chen


    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our Documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    https://docs.microsoft.com/en-us/answers/support/email-notifications


  2. LucyChenMSFT-4874 1,430 Reputation points
    2024-05-03T01:31:15.7966667+00:00

    Hi @Ted Yin,

    Thanks for your kind feedback.

    I've found an issue like yours.

    if any way or method to capture that SQL Queries run which may trigger such termination error?

    Please check out this link, you can follow the methods to resolve your issue.

    Feel free to share your issue here.

    Regards,

    Lucy Chen


    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our Documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    https://docs.microsoft.com/en-us/answers/support/email-notifications

    0 comments No comments

  3. Javier Villegas 895 Reputation points MVP
    2024-05-03T01:32:52.9133333+00:00

    Hello @Ted Yin ,

    EXCEPTION_ACCESS_VIOLATION dumps are mainly raised because of a bug or memory corruption so I'll definitively suggest you to follow Erland suggestion an open a support case. Microsoft will ask you to upload the crash dump file *.mdmp and from there they should be able to investigate more

    As post mortem you won't be able to see all the sessions that were running just before the crash unless you have a monitoring software to keep track of activity. You can consider downloading sp_whoisactive and research the possibility of running it every minute and store the output into a table so you can analyze after the incident.

    From my experience you won't be able to get much seeing all the sessions so opening a support case is the right way to go

    Regards

    Javier


    If the Answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.