SQL Server 2019 service terminated unexpectedly at startup but manually starts

I've had a SQL Server 2019 server working great for the past few months, but it started stopping by itself since last Friday. This morning, I installed latest cumulative update on it.

Here is my version

Microsoft SQL Server 2019 (RTM-CU8-GDR) (KB4583459) - 15.0.4083.2 (X64) Nov 2 2020 18:35:09 Copyright (C) 2019 Microsoft Corporation Developer Edition (64-bit) on Windows Server 2019 Standard 10.0 (Build 17763: ) (Hypervisor)

I've also had the problem with SQL Server 2019 Standard edition (RTM-CU8-GDR).

Each time, a minidump was created. After analyzing the dumps, I can see a kernel base exception.

This server runs only SQL Server, I have nothing more running on the machine.

In SQL's log file I see the dump being taken just after this message.

In the Windows Event Viewer, I only have an error saying that SQL is stopping.

And just before that error, I have tree "Windows Error reporting" error about SQLException64.

Restarting the SQL Server doesn't change anything. But, if I open SQL Management Console and I start the SQL Service, it starts just fine.

I don't really know where to check, how to diagnose it further.

Here is the mini dump file.

```
2021-01-18 10:15:18.56 spid58 ex_terminator: Possible termination due to exception during stack unwinding.
2021-01-18 10:15:18.56 spid58 CImageHelper::Init () Version-specific dbghelp.dll is not used
2021-01-18 10:15:18.56 spid58 Using 'dbghelp.dll' version '4.0.5'
2021-01-18 10:15:18.56 spid58 **Dump thread - spid = 0, EC = 0x000001B929A93670
2021-01-18 10:15:18.56 spid58 ***Stack Dump being sent to E:\SQL Databases 2019\MSSQL15.SQL2019\MSSQL\LOG\SQLDump0002.txt
2021-01-18 10:15:18.56 spid58 ****
2021-01-18 10:15:18.56 spid58 *
2021-01-18 10:15:18.56 spid58 * BEGIN STACK DUMP:
2021-01-18 10:15:18.56 spid58 * 01/18/21 10:15:18 spid 58
2021-01-18 10:15:18.56 spid58 *
2021-01-18 1

Microsoft finally fixed the problem with SQL Broker in SQL 2019.

BUG 14288658

Fixes an issue where SQL Server 2019 stops responding and crashes due
to "ex_terminator - Last chance exception handling" when you use SQL
Server Service Broker.

The fix is available in SQL2019 CU14

StackExchange Database Administrators Q#283500, answer score: 2