SQL Server is terminating because of fatal exception 80000003

Question

good afternoon,

I have a SQL server 2012 (11.0.7001) that closes unexpectedly, it sends me the following message

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

SQL is installed on a Windows Server 2012 R2 Standard server
122GB of Ram.

Can someone show me the way to diagnose the problem? 90901-sqldump0062.log

Answer 1

Stack dumps like this can due to a bug in SQL Server itself, but the culprit can also be external code that executes in the SQL Server process space. This includes:

1. Extended stored procedures.
2. CLR assemlies.
3. OLE DB providers and ODBC drivers for Linked servers that runs in-process.
4. COM-objects invoked through sp_OAxxxx

In the stack dump, I see sqlncli11, which indeed is an OLE DB provider, but one that is very much tested and tried. I also see OLEAUT32. That could indicate that you are using sp_OAxxxx, but since it comes right after sqlncli, I think this is more part of OLE DB.

Then again, the culprit is necessarily not on the call stack, as the erroneous component may have scribbled memory that pulls the carpet for other processes.

Another possible reason is a bad memory stick, that is a hardware problem. Have you run memory diagnostics?

Have you gotten stack dumps like this more than once? In such case, is the stack trace always the same, or is it random? A random stack trace is more an indication of a bad memory stick or a scribbler. If the stack dump is always the same, it seems more like a bug in the product.

I would first investigate if you have any of the four items above, as well as the possibility of a bad memory stick. When it comes to linked servers, ignore linked servers from Microsoft. If you can rule out these issues, open a support case with Microsoft. That is really the only way to get it resolved. Not that SQL 2012 is out of mainstream support.

The reason you should make your own investigations is that the cost for opening a support ticket is not that cheap. If it is a bug in the product, you will be refunded, but certainly not if it is your home-brewed extended stored procedure that kills the server.

Answer 2

Hi,

Is this the first time you have encountered this problem? Does this happen suddenly or after some specific operation is performed. Please check whether any relevant information is recorded in the Windows log.

Less people on this forum could analysis dump file. I would suggest you ask MS professional engineer for help. https://support.microsoft.com/en-us/assistedsupportproducts. Usually they have the necessary tools to analyze the dump file. You should provide them the error log and dump files so they can perform their troubleshooting.

Answer 3

ErlandSommarskog, Criszhan-msft :

I will start looking for the options you give me if I do not go for a case with Microsoft, thank you very much!