The MSSQLSERVER and AGENT service terminated unexpectedly

Yohany Sanchez 0 Reputation points

Dear All SQL expert,

Do you know what is the case that make The MSSQLSERVER service terminated unexpectedly?

Recently, The SQL server (MSSQLSERVER) and SQL Server Agent are stopped automatically during running import data to sql server through scheduled jobs.

We are using SQL version 2016 running on window server 2012 r2 standard.

Version SQL:

Microsoft SQL Server 2016 (SP3-GDR) (KB5029186) - 13.0.6435.1 (X64) Jul 30 2023 19:53:42 Copyright (c) Microsoft Corporation Enterprise Edition: Core-based Licensing (64-bit) on Windows Server 2012 R2 Standard 6.3 <X64> (Build 9600: ) (Hypervisor)


Faulting application name: sqlservr.exe, version: 2015.131.6435.1, time stamp: 0x64c6d582

Faulting module name: ntdll.dll, version: 6.3.9600.21620, time stamp: 0x65175333

Exception code: 0xc0000374

Fault offset: 0x00000000000f1f10

Faulting process id: 0x4a7c

Faulting application start time: 0x01daafe27d7bc77f

Faulting application path: D:\Aplicaciones\Microsoft SQL Server\MSSQL13.BI\MSSQL\Binn\sqlservr.exe

Faulting module path: C:\Windows\SYSTEM32\ntdll.dll

Report Id: 372ce518-1bed-11ef-81ac-0050569f2094

Faulting package full name:

Faulting package-relative application ID:

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
13,045 questions
Windows Server 2012
Windows Server 2012
A Microsoft server operating system that supports enterprise-level management, data storage, applications, and communications.
1,556 questions
{count} votes

2 answers

Sort by: Most helpful
  1. Erland Sommarskog 103.1K Reputation points MVP

    Such crashes are often due to bugs in SQL Server, and had you been on a fully supported version I would have to recommended you to open a support case.

    There are a few more possible causes for a crash like this. One is a hardware issue, what comes closest to mind is a bad memory stick, so you may want to run memory diagnostics.

    Another possibility is that you are using some external module that runs in-process and that scribbles the memory. This includes:

    1. Extended stored procedures.
    2. Unsafe CLR assemblies.
    3. Third-party OLE DB providers for linked servers.
    4. OLE objects invoked from sp_OAxxxx.

  2. LucyChenMSFT-4874 2,010 Reputation points

    Hi @Yohany Sanchez ,

    Thank you for reaching out and welcome to Microsoft Q&A.

    I agree with Erland. Did you have a chance to try the proposed solution he provided?

    In addition, you can try to set the SQL Server start automatically and check if the error will happen again.

    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.