SQL Server 2019 cu14 is terminating because of fatal exception c0000005

Question

SQL Server is terminating because of fatal exception c0000005. This error may be caused by an unhandled Win32 or C++ exception, or by an access violation encountered during exception handling. Check the SQL error log for any related stack dumps or messages. This exception forces SQL Server to shutdown. To recover from this error, restart the server (unless SQLAgent is configured to auto restart).

Answer 1

Please post the output of "SELECT @@version".

If it does not say CU14 somewhere, download and install the most recent Cumulative Update (which is CU14): https://www.microsoft.com/en-us/download/details.aspx?id=100809.

Answer 2

Hi KS-5688,

Welcome to Microsoft Q&A.
In addition, could you please check if there are any error message in the SQL Server setup log within %programfiles%\Microsoft SQL Server\150\Setup Bootstrap\Log by default?
Please refer to this article, which may help you troubleshoot this issue.

Best Regards,
Amelia

---

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.

Answer 3

The possible causes for this error is:

1. A bug in the product.
2. You are running external code in the SQL Server address space and which is misbehaving This can be:
   a. A third-party driver for a linked server or OPENROWSET.
   b. An extended stored procedure.
   c. A COM object invoked from sp_OAxxxx
   d. An unsafe CLR assembly.
3. Corruption or faulty hardware.

Of these, I hold the first point as the most likely. To resolve it, you should open a support case.

But I listed points 2a to 2d, because if you know that you are using any of these, this absolutely something you should investigate, for instance by investigating the stack dumps in the SQL Server errorlog.

You may still prefer to open a case, but the difference between point 1 and the other is that if the cause is a defect in the product, the support case will be without cost in the end. In the other case, you may have to pay the full price, depending on your support contract.

Answer 4

I'm getting the error with a quite simple statement like the following every second time it is executed:

declare @Id int = 4711

if exists (select 1
            from A
            join B on B.a_id = A.a_id
            join C on C.b_id = B.b_id
            where A.a_id = @Id
              and isnull( content, '' ) != ''

            )
print 'I''m fine'

There is nothing sophisticated about the table definitions. It's a bug in SQL Server.