Hi when i close SteelSeries gg software and the default windows driver change ts3 crashes.
this is the error:
ERROR |Windows Audio Session| |[Playback] RenderDeviceContext callbackWaits2 wait exceeded 5 secs 258 - SteelSeries Sonar - Chat (SteelSeries Sonar Virtual Audio Device)
1 Like
This error message doesnāt show any crash.
It only shows that your virtual audio device took to long to answer the client.
1 Like
Itās the last thing that the log shows and this happens when i start up SteelSeries gg when ts3 is open.
1 Like
Having the same problem!
Downloaded GG yesterday to take advantage of the slide function on my SteelSeries headset, and when I close or open GG for some kind of reason TS3 crashes when trying to interact with it. Happened to a friend to. He uninstalled GG and TS3 stopped crashing.
Same here. Everytime when I connect to a server or if I want to close TS the app freezes and crashes. After starting TS3 again, I can connect without error and can see myself on the server until I time out ^^.
Last entries in a log file are always like:
2023-12-18 16:00:22.977407|INFO |SoundDevManager| |Windows Audio Session - DEVICETYPE_PLAYBACK - Default device changed: {0.0.0.00000000}.{556bba58-19fb-4e80-a5a4-ea85690cc6f8}
2023-12-18 16:00:27.981973|ERROR |Windows Audio Session| |[Capture] CaptureDeviceContext callbackWaits2 wait exceeded 5 secs 258 - Microphone (2- Logitech G733 Gaming Headset)
2023-12-18 16:00:27.981973|ERROR |Windows Audio Session| |[Playback] RenderDeviceContext callbackWaits2 wait exceeded 5 secs 258 - Headset (2- Logitech G733 Gaming Headset)
2023-12-18 16:00:32.982974|ERROR |Windows Audio Session| |[Capture] CaptureDeviceContext callbackWaits2 wait exceeded 5 secs 258 - Microphone (2- Logitech G733 Gaming Headset)
2023-12-18 16:00:32.982974|ERROR |Windows Audio Session| |[Playback] RenderDeviceContext callbackWaits2 wait exceeded 5 secs 258 - Headset (2- Logitech G733 Gaming Headset)
2023-12-18 16:00:37.983277|ERROR |Windows Audio Session| |[Playback] RenderDeviceContext callbackWaits2 wait exceeded 5 secs 258 - Headset (2- Logitech G733 Gaming Headset)
2023-12-18 16:00:37.983277|ERROR |Windows Audio Session| |[Capture] CaptureDeviceContext callbackWaits2 wait exceeded 5 secs 258 - Microphone (2- Logitech G733 Gaming Headset)
2023-12-18 16:00:39.775572|DEBUG |SB | |onUpdateClientEvent: serverId = 1, clientId = 59, invokerID = 0, invokerName = "Server", invokerUID = ""
2023-12-18 16:00:42.983974|ERROR |Windows Audio Session| |[Playback] RenderDeviceContext callbackWaits2 wait exceeded 5 secs 258 - Headset (2- Logitech G733 Gaming Headset)
2023-12-18 16:00:42.983974|ERROR |Windows Audio Session| |[Capture] CaptureDeviceContext callbackWaits2 wait exceeded 5 secs 258 - Microphone (2- Logitech G733 Gaming Headset)
2023-12-18 16:00:44.742842|INFO |SoundDevManager| |Direct Sound - DEVICETYPE_PLAYBACK - Default device changed: {28B28BD3-CEE3-4C1D-84B3-2BF56E7B4368}
What is going on ? this problem is still active for so longā¦ will any dev fix this one day or what ? all users of SteelSeries GG Sonar are facing this issue and not only the one using it, any changes related to default audio devices will make TeamSpeak crashā¦ PLEASE DO SOMETHING !
Nope, not for me (both my normal setup and tested in a clean sandbox). Could you test if it still crashes when you start TS3 with the -safemode parameter?
Also I tried to test specifically Sonar in a sandbox but (luckily for me) the spyware did not even start - so I canāt tell if they violate the Windows Audio Session Protocol somehow causing unexpected behavior 
.
Iāve already tried to use safemode and it still crashed.
And it only happens with ts3.
I tried with safemode and same resultā¦ What is the malware you are refering to?
This is not relatrd to SteelSeries GG Sonar btw the issue is only with TeamSpeak any device add or remove while TS is ON makes it crashā¦ Same story is using Nvidia Broadcast for exampleā¦ This onoy happens to TS i didnāt encouter it with any other software even similar softwares like Discord, Mumbleā¦ Other software baqed on audio neither like Skype, Telegram, WhatsAppā¦ Only TS problem that wrongly deal wtih audio devicesā¦
You could maybe focus a little more on the problem instead of just saying that logs doesnāt show anythingā¦ Problem is quite easy to reproduce and logs are showing nothing usefulā¦ It is there for months since last 2 or 3 updates i thinkā¦
As I stated before, the problem is not easy to reproduce. I just tested with, also with both the stable version of TS3, as well as with the beta version. And I switched between both hardware and software devices including NVIDIA Broadcast. When it crashes for you with any device switch, I have to assume it is not related to TeamSpeak itself but rather a faulty plugin. Try starting the client in safemode and ensure no plugins are loaded by checking in the settings. Also you may want to provide a crashdump if you really want any help.
The problem is easy to reproduceā¦ Donāt āswitchā device but make a cahnge to audio deviceā¦ So for exampleā¦ Close steelseries gg appā¦ To make sonar virtual device disappearā¦ Or having teamspeak open, simply start steelseries gg app to make sonar devices be addedā¦ And it will make TS crashā¦ Any added or removed audio device makes TS crash so it is actually easy to reproduceā¦
NO! As I said before this is exactly what I tested. Switching, adding, and whatever the default and default comms device in Windows. It did not crash! BUT, I was unable to test with Sonar, as it didnāt want to start in my sandbox.Why donāt you want to test in safemode, or at the least provide a crashdump? How do you expect to receive any help like this?
Currently iām driving, out of home, it has been tested with safe mode same problemā¦ Creator of the topic provided you logs alreadyā¦ Switching/changing existing audio device is useless as the problem is with āchanges in audio devicesā like add/remove devices while TS is runingā¦ Discord for example only shows a pop-up ānew device detected, do you want to switch to this new deviceā while TS becomes unresponsive and you have to force kill the processā¦ And restart itā¦ If someone is hope and can give you crash dump would be niceā¦ But again issue IS EASY to reproduce as it is happening with at least 10 of my friends exact same problemā¦ Windows 10 (donāt know if same issue under windows 11)ā¦ If you have any usb audio device you can also produce the bugā¦ While TS is runing just plug the audio deviceā¦ Or if was already plugged when you started TSā¦ Just unplug it and TS will become unresponsiveā¦ Try to open settings will not work o ly solution is force kill process to restartā¦
Like I said previously, I already tested the safemode and ts3 doesnāt create a crashdump (I already tried to make ts3 to crash and in the crashdump there is none of the crash date). So this is it, there is nothing more to add on our part and the problem is only ts3(and i think with everyone starts/closes sonar while itās open) because any other application doesnāt crash.
Hi all, @TS.ChrisR,
I have a crash and a hang in two slightly different - but probably related - scenarios when using TS3. I can reproduce these with a 100% success rate when switching my (playback) default communications audio device.
Scenario 1:
- Open TeamSpeak 3
- Change Windows playback default communications device (I am using the old UI for this, can be accessed with Win + R (Run) and
mmsys. cpl) - Quit TeamSpeak
- TeamSpeak appears to close correctly, but then pops up with a crash window.
Pastebin of log file. Google Drive of ts3dump.
Scenario 2:
As a prerequisite, we are using the NirCmd command-line utility to switch audio devices. One needs to have the nircmdc executable on their PATH, or have their shell in the same directory as it when running the command below. I also assume one has an enabled audio device with the name āSpeakersā, which seems to be a default for Windows.
- Open TeamSpeak 3
- Change Windows playback default communications device with the command:
NIRCMDC setdefaultsounddevice "Speakers" 2in cmd/powershell. - Open the Tools > Options UI.
- Options UI never appears, TeamSpeak hangs indefinitely and has to be killed. Clicking the cross causes windows to prompt with its āNot Respondingā dialogue. TS3 does not generate a crashdump.
Under certain unknown conditions, one does not need to open the Options UI to trigger this hang. It may be that when connected to a server, it happens when my client would receive, for example. I do not usually interact with TS3 to trigger it, but this process makes it easily reproducible.
In both scenarios TS3 does not exhibit this behaviour if I change the default device rather than the default communications device.
With (very limited - one time) testing, scenario 1 also occurs for Recording default communications device, whereas scenario 2 did not.
Scenario 2 did not used to occur with an older version of TS3 - I have been using a script to automate changing audio devices for a very long time. I actually discovered scenario 1 whilst performing testing around 2. I will try to ascertain which versions this change occurred between.
It would be great if others could follow the steps above and say whether it is now reproducible for them.
1 Like
