Server Crash after update to beta12

420masterson · July 24, 2026, 1:26pm

After update to TeamSpeak 6 beta12 on Windows Server 2019 server crashes instantly.
What i’ve tried:

reaccept license (worked)
updated Windows Server
installed newest vc++ runtime
restart server
clean install (no previous db files)
started with open console (closes too fast, i can’t see any output there), redirect console output to file creates empty file
checked logfiles (nothing written)
checked windows event-viewer (empty)

I just get a crashdump file, but i can’t see the issue there. It just shows an unknow cpp exception.

Please help, i don’t have any further ideas what to check or try.

I can’t upload the crash dump because i’m “new user”

Edit: rollback to beta11 works

Edit2: this is what i got from windbg

User Mini Dump File: Only registers, stack and portions of memory are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Windows 10 Version 17763 MP (6 procs) Free x64
Product: Server, suite: TerminalServer DataCenter SingleUserTS
Edition build lab: 17763.1.amd64fre.rs5_release.180914-1434
Debug session time: Fri Jul 24 15:13:30.000 2026 (UTC + 2:00)
System Uptime: not available
Process Uptime: not available
..............................................
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr
(bb0.35c): C++ EH exception - code e06d7363 (first/second chance not available)
ReadVirtual() failed in GetXStateConfiguration() first read attempt (error == 0.)
Invalid mini-dump Miscellaneous information in InitializeConfiguration()
For analysis of this file, run !analyze -v
ntdll!NtWaitForSingleObject+0x14:
00007ffc`6cf70394 c3              ret
0:006> .ecxr
rax=0000000000000000 rbx=0000005fa08f7f50 rcx=0000000000000000
rdx=0000000000000000 rsi=0000005fa08f8e70 rdi=0000005fa08f73b0
rip=00007ffc697e1b39 rsp=0000005fa08f6550 rbp=0000005fa08f6c20
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=0000005fa08f7520 r13=0000005fa08faff0
r14=0000000000000000 r15=0000005fa08f66c8
iopl=0         nv up ei pl nz na pe nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000206
KERNELBASE!RaiseException+0x69:
00007ffc`697e1b39 0f1f440000      nop     dword ptr [rax+rax]
0:006> !analyze -v
..............................................
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************

*** WARNING: Unable to verify timestamp for tsserver.exe

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1015

    Key  : Analysis.Elapsed.mSec
    Value: 11273

    Key  : Analysis.IO.Other.Mb
    Value: 45

    Key  : Analysis.IO.Read.Mb
    Value: 1

    Key  : Analysis.IO.Write.Mb
    Value: 89

    Key  : Analysis.Init.CPU.mSec
    Value: 875

    Key  : Analysis.Init.Elapsed.mSec
    Value: 128428

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 84

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29617.1000

    Key  : Analysis.Version.Description
    Value: 10.2604.29.1 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2604.29.1

    Key  : Failure.Bucket
    Value: CPP_EXCEPTION_e06d7363_tsserver.exe!Unknown

    Key  : Failure.Exception.Code
    Value: 0xe06d7363

    Key  : Failure.Exception.IP.Address
    Value: 0x7ffc697e1b39

    Key  : Failure.Exception.IP.Module
    Value: KERNELBASE

    Key  : Failure.Exception.IP.Offset
    Value: 0x41b39

    Key  : Failure.Hash
    Value: {14c23cac-f8a2-76c9-3837-0185ecf46a3b}

    Key  : Failure.ProblemClass.Primary
    Value: CPP_EXCEPTION

    Key  : Faulting.IP.Type
    Value: Paged

    Key  : WER.OS.Branch
    Value: rs5_release

    Key  : WER.OS.Version
    Value: 10.0.17763.1

    Key  : WER.Process.Version
    Value: 1.0.0.0


FILE_IN_CAB:  tsserver_6_0_0-beta12_windows_amd64_1784898810.dmp

CONTEXT:  (.ecxr)
rax=0000000000000000 rbx=0000005fa08f7f50 rcx=0000000000000000
rdx=0000000000000000 rsi=0000005fa08f8e70 rdi=0000005fa08f73b0
rip=00007ffc697e1b39 rsp=0000005fa08f6550 rbp=0000005fa08f6c20
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=0000005fa08f7520 r13=0000005fa08faff0
r14=0000000000000000 r15=0000005fa08f66c8
iopl=0         nv up ei pl nz na pe nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000206
KERNELBASE!RaiseException+0x69:
00007ffc`697e1b39 0f1f440000      nop     dword ptr [rax+rax]
Resetting default scope

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 00007ffc697e1b39 (KERNELBASE!RaiseException+0x0000000000000069)
   ExceptionCode: e06d7363 (C++ EH exception)
  ExceptionFlags: 00000001
NumberParameters: 4
   Parameter[0]: 0000000019930520
   Parameter[1]: 0000005fa08f8fc0
   Parameter[2]: 00007ff7facff770
   Parameter[3]: 00007ff7f9ac0000

PROCESS_NAME:  tsserver.exe

ERROR_CODE: (NTSTATUS) 0xe06d7363 - <Unable to get error code text>

EXCEPTION_CODE_STR:  e06d7363

EXCEPTION_PARAMETER1:  0000000019930520

EXCEPTION_PARAMETER2:  0000005fa08f8fc0

EXCEPTION_PARAMETER3:  00007ff7facff770

EXCEPTION_PARAMETER4: 7ff7f9ac0000

STACK_TEXT:  
0000005f`a08f6550 00007ff7`fa6028a1     : 0000005f`a08f7f50 0000005f`a08f7520 00000000`00000100 00000000`00000000 : KERNELBASE!RaiseException+0x69
0000005f`a08f6630 0000005f`a08f7f50     : 0000005f`a08f7520 00000000`00000100 00000000`00000000 00000000`00000001 : tsserver+0xb428a1
0000005f`a08f6638 0000005f`a08f7520     : 00000000`00000100 00000000`00000000 00000000`00000001 0000005f`a08f8e70 : 0x0000005f`a08f7f50
0000005f`a08f6640 00000000`00000100     : 00000000`00000000 00000000`00000001 0000005f`a08f8e70 00000000`00000000 : 0x0000005f`a08f7520
0000005f`a08f6648 00000000`00000000     : 00000000`00000001 0000005f`a08f8e70 00000000`00000000 00000000`00000000 : 0x100


STACK_COMMAND: ~0s; .ecxr ; kb

IP_IN_PAGED_CODE: 
KERNELBASE!RaiseException+69
00007ffc`697e1b39 0f1f440000      nop     dword ptr [rax+rax]

SYMBOL_NAME:  tsserver+b428a1

MODULE_NAME: tsserver

IMAGE_NAME:  tsserver.exe

FAILURE_BUCKET_ID:  CPP_EXCEPTION_e06d7363_tsserver.exe!Unknown

OS_VERSION:  10.0.17763.1

BUILDLAB_STR:  rs5_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

IMAGE_VERSION:  1.0.0.0

FAILURE_ID_HASH:  {14c23cac-f8a2-76c9-3837-0185ecf46a3b}

Followup:     MachineOwner
---------

0:006> ~0s; .ecxr ; kb
ntdll!NtWaitForSingleObject+0x14:
00007ffc`6cf70394 c3              ret
rax=0000000000000000 rbx=0000005fa08f7f50 rcx=0000000000000000
rdx=0000000000000000 rsi=0000005fa08f8e70 rdi=0000005fa08f73b0
rip=00007ffc697e1b39 rsp=0000005fa08f6550 rbp=0000005fa08f6c20
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=0000005fa08f7520 r13=0000005fa08faff0
r14=0000000000000000 r15=0000005fa08f66c8
iopl=0         nv up ei pl nz na pe nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000206
KERNELBASE!RaiseException+0x69:
00007ffc`697e1b39 0f1f440000      nop     dword ptr [rax+rax]
  *** Stack trace for last set context - .thread/.cxr resets it
 # RetAddr               : Args to Child                                                           : Call Site
00 00007ff7`fa6028a1     : 0000005f`a08f7f50 0000005f`a08f7520 00000000`00000100 00000000`00000000 : KERNELBASE!RaiseException+0x69
01 0000005f`a08f7f50     : 0000005f`a08f7520 00000000`00000100 00000000`00000000 00000000`00000001 : tsserver+0xb428a1
02 0000005f`a08f7520     : 00000000`00000100 00000000`00000000 00000000`00000001 0000005f`a08f8e70 : 0x0000005f`a08f7f50
03 00000000`00000100     : 00000000`00000000 00000000`00000001 0000005f`a08f8e70 00000000`00000000 : 0x0000005f`a08f7520
04 00000000`00000000     : 00000000`00000001 0000005f`a08f8e70 00000000`00000000 00000000`00000000 : 0x100
0:000> .frame 0n1;dv /t /v
01 0000005f`a08f6630 0000005f`a08f7f50     tsserver+0xb428a1
Unable to enumerate locals, Win32 error 0n318
Private symbols (symbols.pri) are required for locals.
Type ".hh dbgerr005" for details.

420masterson · July 27, 2026, 3:12pm

Update: AI-assisted analysis of the crash dumps and Process Monitor recording

Since I do not have the necessary debugging expertise myself, I provided both crash dumps, the official Beta 11 and Beta 12 binaries, file hashes, and a Process Monitor recording to an AI assistant for analysis.

According to that analysis, the Beta 12 installation is complete. The SHA-256 hashes of tsserver.exe, ssh.dll, tsdb_sqlite3.dll, and tsdb_mariadb.dll match the official Beta 12 release.

The Process Monitor recording contains the following event immediately before TeamSpeak creates the crash dump:

Process:   tsserver.exe
Operation: CreateFile
Path:      C:\Windows\System32\icu.dll
Result:    NAME NOT FOUND

Immediately afterwards, the server begins creating its crash dump and terminates with C++ exception 0xE06D7363.

The AI’s analysis of the exception data identified a std::system_error containing Windows error 126:

The specified module could not be found.

The Process Monitor recording also shows that the server crashes before attempting to access tsdb_sqlite3.dll or tsdb_mariadb.dll. Therefore, the database and its plugins do not appear to be involved. The executable path and current working directory were also correct during the recorded startup.

The AI suspects that this is connected to the following Beta 12 change:

Server log timestamps now use the local time zone instead of UTC

According to Microsoft’s documentation, the MSVC C++ <chrono> time-zone functionality requires Windows Server 2022 or later. Using these time-zone facilities on an older Windows version results in a runtime error:

https://learn.microsoft.com/en-us/cpp/standard-library/chrono?view=msvc-170

Microsoft also states that the combined icu.dll was introduced with Windows 10 version 1903. Windows Server 2019 uses the older build 17763/1809 platform:

https://learn.microsoft.com/en-us/windows/win32/intl/international-components-for-unicode–icu-

The AI’s conclusion is therefore that Beta 12 may have introduced an unintended incompatibility with Windows Server 2019 through the new local-time-zone logging implementation. Beta 11 continues to start correctly on the same machine.

I cannot personally verify the implementation-level conclusion, but the missing icu.dll event immediately preceding the crash is present in the Process Monitor recording.

Could the TeamSpeak developers please confirm whether Windows Server 2022 is now required, or whether Beta 12 can provide a fallback to UTC when the required time-zone functionality is unavailable?

LeonMarcelHD · July 27, 2026, 3:29pm

I’ve forwarded it to our devs and will let you know once I have a response.

LeonMarcelHD · July 28, 2026, 3:35pm

We’ve released a Hotfix v12.1. Please let us know if you still have any issues.

420masterson · July 28, 2026, 3:57pm

Thank you for the quick response and for releasing the hotfix.

I have installed v6.0.0-beta12.1 on the same Windows Server 2019 system. The server now starts normally, loads the existing database without any issues, and has been running without further crashes.

I can confirm that the hotfix completely resolves the issue on my system. Many thanks to you and the development team for investigating and fixing it so quickly!