Share via

Help needed: SQL Server 2014 fails to start with error "Stack Overflow Dump not possible"

Michael Antes 0 Reputation points
2025-09-19T06:46:09.94+00:00

ERRORLOG.logHi!

An instance of MS SQL Server 2014, which is installed on Windows 11, started failing during startup.
The only error message I can see is "Stack Overflow Dump not possible".

Any ideas, what's the matter here and how to solve it?

The ERRORLOG file:

2025-09-18 16:52:18.98 Server Microsoft SQL Server 2014 (SP2) (KB3171021) - 12.0.5000.0 (Intel X86) Jun 17 2016 19:21:56 Copyright (c) Microsoft Corporation Express Edition on Windows NT 6.3 <X64> (Build 26100: ) (WOW64) (Hypervisor) 2025-09-18 16:52:18.98 Server UTC adjustment: 9:00 2025-09-18 16:52:18.98 Server (c) Microsoft Corporation. 2025-09-18 16:52:18.99 Server All rights reserved. 2025-09-18 16:52:19.00 Server Server process ID is 14972. 2025-09-18 16:52:19.00 Server System Manufacturer: 'HP', System Model: 'HP ProBook 450 15.6 inch G9 Notebook PC'. 2025-09-18 16:52:19.00 Server Authentication mode is MIXED. 2025-09-18 16:52:19.00 Server Logging SQL Server messages in file 'C:\Program Files (x86)\Microsoft SQL Server\MSSQL12.SQLEXPRESSWTS\MSSQL\Log\ERRORLOG'. 2025-09-18 16:52:19.00 Server The service account is 'CHEST-MI\DESKTOP-VBUCQ2E$'. This is an informational message; no user action is required. 2025-09-18 16:52:19.00 Server Registry startup parameters: -d C:\Program Files (x86)\Microsoft SQL Server\MSSQL12.SQLEXPRESSWTS\MSSQL\DATA\master.mdf -e C:\Program Files (x86)\Microsoft SQL Server\MSSQL12.SQLEXPRESSWTS\MSSQL\Log\ERRORLOG -l C:\Program Files (x86)\Microsoft SQL Server\MSSQL12.SQLEXPRESSWTS\MSSQL\DATA\mastlog.ldf 2025-09-18 16:52:19.00 Server Command Line Startup Parameters: -s "SQLEXPRESSWTS" 2025-09-18 16:52:19.25 Server SQL Server detected 1 sockets with 6 cores per socket and 12 logical processors per socket, 12 total logical processors; using 8 logical processors based on SQL Server licensing. This is an informational message; no user action is required. 2025-09-18 16:52:19.25 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required. 2025-09-18 16:52:19.25 Server Detected 16016 MB of RAM. This is an informational message; no user action is required. 2025-09-18 16:52:19.25 Server Using conventional memory in the memory manager. 2025-09-18 16:52:19.40 Server Default collation: Japanese_CI_AS (us_english 1033) 2025-09-18 16:52:19.43 Server The maximum number of dedicated administrator connections for this instance is '1' 2025-09-18 16:52:19.43 Server This instance of SQL Server last reported using a process ID of 7876 at 2025/09/18 16:39:46 (local) 2025/09/18 7:39:46 (UTC). This is an informational message only; no user action is required. 2025-09-18 16:52:19.43 Server Node configuration: node 0: CPU mask: 0x000000ff:0 Active CPU mask: 0x000000ff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required. 2025-09-18 16:52:19.44 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required. 2025-09-18 16:52:19.44 Server Database Instant File Initialization: disabled. For security and performance considerations see the topic 'Database Instant File Initialization' in SQL Server Books Online. This is an informational message only. No user action is required. 2025-09-18 16:52:19.46 Server Software Usage Metrics is disabled. 2025-09-18 16:52:19.46 spid8s Starting up database 'master'. 2025-09-18 16:52:19.47 spid8s 09/18/25 16:52:19 Stack Overflow Dump not possible - Exception c00000fd EXCEPTION_STACK_OVERFLOW at 0x5E60DCAD 2025-09-18 16:52:19.47 spid8s SqlDumpExceptionHandler: Address=0x5E60DCAD Exception Code = c00000fd 2025-09-18 16:52:19.47 spid8s eax=5f025b18 ebx=0469ccb0 ecx=0ca31000 edx=09e0a01c 2025-09-18 16:52:19.47 spid8s esi=0ca31000 edi=00000027 eip=5e60dcad esp=09e0a000 2025-09-18 16:52:19.47 spid8s ebp=09e0b08c efl=00010206 2025-09-18 16:52:19.47 spid8s cs=23 ss=2b ds=2b es=2b fs=53 gs=2b 2025-09-18 16:52:19.47 spid8s 1: Frame 09E0B08C Return Address 5E60DCAD 2025-09-18 16:52:19.47 spid8s 2: Frame 09E0B14C Return Address 5E60BB0B 2025-09-18 16:52:19.47 spid8s 3: Frame 09E0B1F0 Return Address 5E60B536 2025-09-18 16:52:19.47 spid8s 4: Frame 09E0C29C Return Address 5E60DCC1 2025-09-18 16:52:19.47 spid8s 5: Frame 09E0C35C Return Address 5E60BB0B 2025-09-18 16:52:19.47 spid8s 6: Frame 09E0C400 Return Address 5E60B536 2025-09-18 16:52:19.47 spid8s 7: Frame 09E0D4AC Return Address 5E60DCC1 2025-09-18 16:52:19.47 spid8s 8: Frame 09E0D56C Return Address 5E60BB0B 2025-09-18 16:52:19.47 spid8s 9: Frame 09E0D610 Return Address 5E60B536 2025-09-18 16:52:19.47 spid8s 10: Frame 09E0E6BC Return Address 5E60DCC1 2025-09-18 16:52:19.47 spid8s 11: Frame 09E0E77C Return Address 5E60BB0B 2025-09-18 16:52:19.47 spid8s 12: Frame 09E0E820 Return Address 5E60B536 2025-09-18 16:52:19.47 spid8s 13: Frame 09E0F8CC Return Address 5E60DCC1 2025-09-18 16:52:19.47 spid8s 14: Frame 09E0F98C Return Address 5E60BB0B 2025-09-18 16:52:19.47 spid8s 15: Frame 09E0FA30 Return Address 5E60B536 2025-09-18 16:52:19.47 spid8s 16: Frame 09E10ADC Return Address 5E60DCC1 2025-09-18 16:52:19.47 spid8s 17: Frame 09E10B9C Return Address 5E60BB0B 2025-09-18 16:52:19.47 spid8s 18: Frame 09E10C40 Return Address 5E60B536 2025-09-18 16:52:19.47 spid8s 19: Frame 09E11CEC Return Address 5E60DCC1 2025-09-18 16:52:19.47 spid8s 20: Frame 09E11DAC Return Address 5E60BB0B 2025-09-18 16:52:19.47 spid8s
2025-09-18 16:52:19.47 spid8s TotalPhysicalMemory = 16794497024, AvailablePhysicalMemory = 10847391744 2025-09-18 16:52:19.47 spid8s AvailableVirtualMemory = 3928674304, AvailablePagingFile = 11793674240 2025-09-18 16:52:19.47 spid8s Stack Signature for the dump is 0xE4E22AEB 2025-09-18 16:52:19.55 Server CLR version v4.0.30319 loaded. 2025-09-18 16:52:19.61 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework\v4.0.30319. 2025-09-18 16:52:20.11 spid8s External dump process return code 0x20000001. External dump process returned no errors. 2025-09-18 16:52:20.12 spid8s SQL Server shutdown has been initiated

SQL Server | Other
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Erland Sommarskog 127.7K Reputation points MVP Volunteer Moderator
    2025-09-19T16:28:28.0333333+00:00

    Sounds like you are seriously constrained on memory. I see that you have 16 GB of RAM, which should be enough one like to think. But I also note that you are running the 32-bit version of SQL Server, which maybe comes with complications.

    I also note that you are running SQL 2014 SP2, and there is a Service Pack 3, which you could try to install. Then again, that upgrade will fail if you get the same error with SP3.

    I would install a new instance with 64-bit SQL Server, preferably also a more modern version of SQL Server. You can copy your database files to the new instance and attach them.

    0 comments
  2. Dinesh Yadlapalli 0 Reputation points Microsoft External Staff Moderator
    2025-10-27T13:33:56.3866667+00:00

    Hi @Michael Antes ,Thank you for reaching out to the Microsoft Q & A Forum.

    The error "Stack Overflow Dump not possible - Exception c00000fd EXCEPTION_STACK_OVERFLOW at 0x5E60DCAD" indicates that SQL Server encountered a stack overflow during the startup process, specifically while trying to start the master database.

    Please try below steps to fix the issue.

    1. Check for corruption in master Database, Try to start SQL Server in single-user mode with below configuration.

    sqlservr.exe -f -m -T3608

    Note: This bypasses startup procedures and may allow you to access the instance.

    If it starts and then run below command.

    DBCC CHECKDB('master') WITH NO_INFOMSGS, ALL_ERRORMSGS;

    1. Restore master from Backup, If corruption is occur, Restore master.mdf and mastlog.ldf from a backup. Replace the files in below path.

    C:\Program Files (x86)\Microsoft SQL Server\MSSQL12.SQLEXPRESSWTS\MSSQL\DATA\

    1. Look for any third-party SQL Server extensions or DLLs that might be loaded during startup. Disable or remove them temporarily to see if SQL Server starts.
    2. If the issue is due to corrupted binaries, Repair the SQL Server installation via Control Panel --> Programs --> SQL Server --> Change -->Repair Or uninstall and reinstall SQL Server 2014.
    3. If SQL Server 2014 is not supported on Windows 11. upgrade to SQL Server 2019 or later, which is compatible with Windows 11.
    4. Check that .NET Framework 4.0.30319 is properly installed and not corrupted.

    I hope this information helps. Please do let us know if you have any further queries.

     

    Regards,

    Dinesh

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.