The client does not start, It briefly shows up but closes instantly (0xC00000FD)

TeamSpeak 3 Client
, ,
1

Teamspeak3 is not working. It was working fine before, but after shutting down and restarting my computer one day, the software stopped working. Uninstalling and reinstalling it didn’t work. I can only see the software logo flashing briefly in the taskbar before it closes automatically.

2

Please show us your logs.

You can find them in: %AppData% -> Roaming -> TS3Client -> logs

3 
2026-02-24 11:53:37.150899|INFO    |              |   |TeamSpeak Client 3.6.2 (2023-09-20 09:48:13)
2026-02-24 11:53:37.151902|INFO    |              |   |SystemInformation: Windows 11 (26100) x64 (AMD or Intel) Binary: 64bit
2026-02-24 11:53:37.176923|DEVELOP |Windows Audio Session|   |Hardware agc not available - 麦克风 (ToDesk Virtual Audio)
2026-02-24 11:53:37.178924|DEVELOP |Windows Audio Session|   |Hardware agc not available - 耳机式麦克风 (INZONE H5 - Chat)
2026-02-24 11:53:37.178924|DEBUG   |SoundDevManager|   |Loading dynamic soundbackend from D:/TS3/soundbackends/directsound_win64.dll
2026-02-24 11:53:37.210953|DEBUG   |Direct Sound  |   |setting timer resolution to 1ms -
2026-02-24 11:53:37.273010|DEBUG   |SoundDevManager|   |Soundbackend loaded.
2026-02-24 11:53:37.274010|INFO    |              |   |\*\*\* Time \[SPAWN_EVENTCONVERTER\]: 123
2026-02-24 11:53:37.319052|INFO    |ClientUI      |   |OpenGL Info: LibGLES, Vendor: Google Inc., Renderer: ANGLE (NVIDIA GeForce RTX 4070 SUPER Direct3D11 vs_5_0 ps_5_0), Version: OpenGL ES 2.0 (ANGLE 2.1.0.57ea533f79a7)
2026-02-24 11:53:37.320053|ERROR   |RevocationListCache|   |Failed to import revocation list from cache
2026-02-24 11:53:37.399125|INFO    |Addons        |   |Checking for addon updates…
2026-02-24 11:53:37.411135|INFO    |Plugins       |   |Plugins safemode parameter detected, not loading any plugins
2026-02-24 11:53:37.690422|INFO    |SyncImpl      |   |Creating default config in local storage
2026-02-24 11:53:37.716446|DEVELOP |Windows Audio Session|   |DeviceDeleteList::wait_for_deletes - enter - DeviceDeleteList
2026-02-24 11:53:37.716446|DEVELOP |Windows Audio Session|   |DeviceDeleteList::wait_for_deletes - leave - DeviceDeleteList
2026-02-24 11:53:38.203925|INFO    |              |   |successfully downloaded revocation list for accounting

This is the software’s runtime log. I’ve also tried running it using secure code, but it still didn’t work.

4

I’ve posted the operation log downstairs, please take a look.

5

Okay, so you’ve enabled the safemode parameter. Therefore the crash is not due a plugin.

I don’t see anything unusual in your log. The agc hardware is not available, but we’ll put that aside for the moment.

Please check whether a crash dump was created in %AppData%\TS3Client\crashdumps\ and upload it here.

6

It seems that unsupported file types cannot be uploaded here.

7

Yeah, you need to upload it via google drive or dropbox or another extern upload.

Afterwards you can share us the link.

8

I’ve uploaded the file, and you can view it now.thx

9

I analyzed the crash dump.

The crash is a stack overflow (0xC00000FD) occurring in:

gdi32full!CreateFontIndirectExW

The call stack shows the execution path going through qwindows.dll and Qt5Core.
TeamSpeak uses Qt for its UI, and this pattern is typical for a font creation / font fallback recursion loop during application startup, which means TeamSpeak crashes while trying to create or resolve a font via the Windows GDI layer, and the stack eventually overflows.

Important:
This is not a GPU/DirectX crash. The failure happens inside Windows font handling (GDI), triggered by Qt during UI initialization.

Recommended fix: Reset the Windows Font Cache

Please try the following:

  1. Press Win + R

  2. Type services.msc

  3. Stop the service named Windows Font Cache Service

  4. Delete the contents of the following folders (if they exist):

    %WinDir%\ServiceProfiles\LocalService\AppData\Local\FontCache\
    %LOCALAPPDATA%\FontCache\

  5. Reboot the system.

This type of stack overflow in CreateFontIndirectExW is commonly caused by a corrupted Windows font cache.

Please let us know if TeamSpeak starts correctly after performing these steps.

10

Thx, I’ll give it a try and get back to you later. Thanks for your hard work.

11

It didn’t work; the situation remains the same as before.

a new crash dump file has been uploaded.

12

Before we continue with the new crashdump. Please delete your TeamSpeak cache %AppData%\TS3Client\cache and restart the client.

If it still doesn’t work, let’s continue here.
From your new crashdump i can see it’s still a STACK_OVERFLOW (0xC00000FD) during font creation.
The bucket is now gdi32full.dll!InsertCFontCache, but the stack still goes through gdi32full!CreateFontIndirectExW → qwindows.dll → repeated Qt5Core frames, which strongly points to a Qt font fallback / font resolution recursion at startup.

Since resetting the Windows font cache didn’t help, the next likely cause is a problematic installed font or broken font fallback/substitution settings.

As a quick way to find a solution and to be on the safe side, I recommend that you

  1. try starting TeamSpeak 3 from a fresh Windows user profile (new local user). If it works there, it’s a per-user font/settings issue and
  2. check recently installed fonts and temporarily remove or disable them (especially any non-Microsoft fonts), then test again.

If you can confirm whether it works under a new Windows user, we can narrow this down quickly.

13

It seems to be an issue with the new font. After creating a new user locally, TS3 works fine. Thank you so much for your help.

2 Likes
14

You’re welcome. If you have any further question, feel free to ask! :grinning_face_with_smiling_eyes:

1 Like