TeamSpeak 6 crash on startup – invalid pointer read in TeamSpeak.dll (6.0.0.4528)

[Bhaalz]

Hello TeamSpeak Support,

I am experiencing a consistent startup crash with TeamSpeak 6 (version 6.0.0.4528) on Windows.

The client crashes immediately on launch before the UI appears.

I captured and analysed the generated crash dump using WinDbg, and the failure appears to originate inside TeamSpeak.dll during an internal UTF-16 string scan routine.

Crash details

Application: TeamSpeak 6
Version: 6.0.0.4528
OS: Windows 11 (build 26200)
Crash type: Access violation (NULL pointer read)

Faulting instruction:

TeamSpeak.dll +0x1c6df22

vpcmpeqw ymm1,ymm2,ymmword ptr [rdx]

At the time of the crash:

rdx = 0x0000000000000000
rcx = 0x0000000000000000

The crash occurs in a vectorised UTF-16 scanning routine.

Call path

TeamSpeak.dll!RunWinMain+0x973822
TeamSpeak.dll+0xd77535
TeamSpeak.dll+0xea736c
TeamSpeak.dll+0xd600e7
TeamSpeak.dll!RunWinMain+0xf1a
TeamSpeak.exe

The immediate caller passes a pointer loaded from [rsp+38h]:

mov rcx, qword ptr [rsp+38h]
call TeamSpeak!RunWinMain+0x9737b0

That pointer resolves to:

000001f8`530808d0

However, inspecting that memory shows it is not a raw UTF-16 string pointer but appears to be a structure or object containing embedded short-string data.

Example memory contents:

000001f8`530808d0  00007ffe`a1e7c298 00007ffe`a1e7c468
000001f8`530808e0  000001f8`530808d0 00007ffe`a1e7c488
...
000001f8`53080940  02 00 00 00 4e 00 65 00

The bytes at offset +0x70 decode to:

Length = 2
UTF-16 characters = “Ne”

This suggests the code may be passing a string object / small-string structure into a routine expecting a raw wchar_t* buffer, eventually causing the scan routine to dereference a null pointer.

What has already been tested

• Fresh reinstall of TeamSpeak 6

• Verified all program files present

• No compatibility mode enabled

• No command line flags present

• Crash occurs before UI startup

• Reproduces consistently

Given the pointer type mismatch seen in the dump, this appears to be an internal pointer/type handling issue during early startup rather than an environmental problem.

If useful, I can also provide the full crash dump file for analysis.

Please let me know if any additional diagnostic information would help.

Kind regards,
Andrew

[LeonMarcelHD]

Sorry for the late response but, I’ve forwarded it to a dev to check on what is causing the issue. We’ll let you know once we know more.

Can you please check your client logs and check the mentioned path for crash dumps:

How to retrieve logs from your TeamSpeak client

This thread is a how-to retrieve logs from TeamSpeak 6 to help us identify an issue. NOTE: the logs may include confidential information like server addresses and usernames of people you are chatting with. So before uploading please have a quick look over them and censor or send them via a DM to the person who has requested them. Search in the search bar for Developer Tools (or if you’r client is not set to English you need to search for it in the translated language. See the list down bel…

[Bhaalz]

@LeonMarcelHD

Can you please check your client logs and check the

Hi, I cant upload the dmp file as I’m a “new” user. the CEF file shows you nothing of any use as its not even starting the client, so i cant get anythingthing from developer tools either…

: [8312:12296:0317/082932.973:ERROR:..\571da4\1\chromium\src\chrome\installer\util\google_update_settings.cc:265] Failed opening key Software\Chromium to set usagestats; result: 5
[8312:3548:0317/082932.981:WARNING:..\571da4\1\chromium\src\chrome\browser\signin\account_consistency_mode_manager.cc:74] Desktop Identity Consistency cannot be enabled as no OAuth client ID and client secret have been configured.

Your help in this matter is greatly apprieciated

Kind regards,

Andrew.

[Bhaalz]

3666bf17-777c-4534-9065-ebd1e0142f67.dmp (1.7 MB)

cef.log (409 Bytes) User level was updated, Thanks, attached dmp file

[revide]

Thanks a lot, that was very insightful.

It seems your Download Data directory is not correctly set for your User Profile - I fixed that this does not crash the app anymore in the next release, until then, you might try to fix that yourself and everything should work after that again.

Along the steps from How do I change and cleanup my default Download location in Windows 10? - Microsoft Q&A

• Open RegEdit
• Go to HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders
• Add/Modify {374DE290-123F-4565-9164-39C4925E467B} to REG_EXPAND_SZ (type) and “D:\your\new\path”

Start TS and retry

You may want to check though why that is broken in the first place, maybe a somewhat incomplete Windows/User Profile setup?

[Falkthewolf]

Since a few days I have the problem, that my TS6 Client just stops at the start screen bootup logo.
I´m using it on Windows 11.
I tried to reinstall it, reinstall with all files deleted after the uninstall in appdata and elswhere but nothing works.
I saw a post with the same issue but there the guy did say he fixed it with a reinstall….but sadly thats not the problem solver in my case.

I put my log here:

\[10072:21040:0321/201711.417:WARNING:..\\571da4\\1\\chromium\\src\\chrome\\browser\\signin\\account_consistency_mode_manager.cc:74\] Desktop Identity Consistency cannot be enabled as no OAuth client ID and client secret have been configured.
\[10072:21040:0321/201712.185:INFO:CONSOLE:2\] “Notification Settings loaded. \[object Object\],\[object Object\],\[object Object\],\[object Object\],\[object Object\],\[object Object\],\[object Object\],\[object Object\],\[object Object\]”, source: tsui://default/main.js (2)
\[10072:21040:0321/201712.185:INFO:CONSOLE:2\] “Message Notification settings loaded. \[object Object\],\[object Object\],\[object Object\],\[object Object\],\[object Object\],\[object Object\],\[object Object\],\[object Object\],\[object Object\]”, source: tsui://default/main.js (2)
\[10072:21040:0321/201712.186:INFO:CONSOLE:2\] “Whisper Settings loaded.”, source: tsui://default/main.js (2)
\[10072:21040:0321/201712.292:INFO:CONSOLE:2\] “Uncaught (in promise) \[object Object\]”, source: tsui://default/main.js (2)
\[10072:21040:0321/201715.293:ERROR:..\\571da4\\1\\chromium\\src\\components\\device_event_log\\device_event_log_impl.cc:198\] \[20:17:15.293\] USB: usb_service_win.cc:105 SetupDiGetDeviceProperty({{A45C254E-DF1C-4EFD-8020-67D146A850E0}, 6}) failed: Element not found. (0x490)
\[10072:28376:0321/201715.713:ERROR:..\\571da4\\1\\chromium\\src\\google_apis\\gcm\\engine\\registration_request.cc:292\] Registration response error message: PHONE_REGISTRATION_ERROR
\[10072:28376:0321/201715.714:ERROR:..\\571da4\\1\\chromium\\src\\google_apis\\gcm\\engine\\registration_request.cc:292\] Registration response error message: PHONE_REGISTRATION_ERROR
\[10072:28376:0321/201715.740:ERROR:..\\571da4\\1\\chromium\\src\\google_apis\\gcm\\engine\\mcs_client.cc:700\]   Error code: 401  Error message: Authentication Failed: wrong_secret
\[10072:28376:0321/201715.740:ERROR:..\\571da4\\1\\chromium\\src\\google_apis\\gcm\\engine\\mcs_client.cc:702\] Failed to log in to GCM, resetting connection.
\[10072:28376:0321/201715.748:ERROR:..\\571da4\\1\\chromium\\src\\google_apis\\gcm\\engine\\registration_request.cc:292\] Registration response error message: PHONE_REGISTRATION_ERROR
\[10072:28376:0321/201740.547:ERROR:..\\571da4\\1\\chromium\\src\\google_apis\\gcm\\engine\\registration_request.cc:292\] Registration response error message: DEPRECATED_ENDPOINT
\[10072:28376:0321/201826.804:ERROR:..\\571da4\\1\\chromium\\src\\google_apis\\gcm\\engine\\registration_request.cc:292\] Registration response error message: DEPRECATED_ENDPOINT
\[10072:28376:0321/202009.048:ERROR:..\\571da4\\1\\chromium\\src\\google_apis\\gcm\\engine\\registration_request.cc:292\] Registration response error message: DEPRECATED_ENDPOINT
\[10072:21040:0321/202011.517:ERROR:..\\571da4\\1\\chromium\\src\\services\\on_device_model\\public\\cpp\\service_client.cc:36\] Unexpected on_device_model service disconnect:
\[10072:28376:0321/202312.110:ERROR:..\\571da4\\1\\chromium\\src\\google_apis\\gcm\\engine\\registration_request.cc:292\] Registration response error message: DEPRECATED_ENDPOINT
\[10072:28376:0321/203020.574:ERROR:..\\571da4\\1\\chromium\\src\\google_apis\\gcm\\engine\\registration_request.cc:292\] Registration response error message: DEPRECATED_ENDPOINT
\[10072:21040:0321/203236.374:WARNING:..\\571da4\\1\\chromium\\src\\cef\\libcef\\browser\\frame_host_impl.cc:665\] virtual CefFrameHostImpl::SendProcessMessage sent to detached frame 5-780CB05D68227625A5A71ECA3AA729D5 (main) will be ignored

I hope some1 can help me with that.
To add something relevant maybe, my pc crashed the other day and i think it has something to do with this.

[LeonMarcelHD]

Can you check if this solution works for your?

TeamSpeak 6 crash on startup – invalid pointer read in TeamSpeak.dll (6.0.0.4528)

Thanks a lot, that was very insightful. It seems your Download Data directory is not correctly set for your User Profile - I fixed that this does not crash the app anymore in the next release, until then, you might try to fix that yourself and everything should work after that again. Along the steps from How do I change and cleanup my default Download location in Windows 10? - Microsoft Q&A Open RegEdit Go to HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\User Shell Fol…

---

If it does not, please check for crash dumps and upload them here. The file path is linked in this post:

And if a ts5_client.log is created this may also be useful.

How to retrieve logs from your TeamSpeak client

This thread is a how-to retrieve logs from TeamSpeak 6 to help us identify an issue. NOTE: the logs may include confidential information like server addresses and usernames of people you are chatting with. So before uploading please have a quick look over them and censor or send them via a DM to the person who has requested them. Search in the search bar for Developer Tools (or if you’r client is not set to English you need to search for it in the translated language. See the list down bel…

[Falkthewolf]

Wow, Thank you very much.

This step made it work again.

Strange that this little setting made it crash.