Results 1 to 5 of 5
Thread: Teamspeak Crashing
-
19-01-2010, 16:06 #1
-= TeamSpeak User =-
- Join Date
- Dec 2009
- Location
- Lol?
- Posts
- 4
Teamspeak Crashing
hi guys, my friend just updated to the latest beta availiable since he's done this he has not been able to connect to my teamspeak 3 server. All others users have not had any problem nor me myself.
he gets 2 errors before the client closes
http://img13.imageshack.us/img13/2754/debugshit.jpg
and
http://img11.imageshack.us/img11/558...ationerror.jpg
He is running "Vista Ultimate 32bit" with realtek sound drivers, he used to have slight problems connecting where his mic was disabled, but since the update he cannot join at all without the client crashing.
Crash Dump File
Client Log:
would be great if this can be resolved quick and easily as i'm having to talk to him via Teamspeak 2 which now sounds to me pretty bad, since i got used to TS3Code:2010-01-18 20:03:10.716740|INFO | | | Logging started, clientlib version: 3.0.0-beta11 [Build: 9881] 2010-01-18 20:03:10.888340|INFO |ClientUI | | Failed to init text to speech engine: 3584 2010-01-18 20:03:11.338340|INFO |ClientUI | | Last update check was: Mon 18. Jan 14:24:02 2010 2010-01-18 20:03:11.381340|ERROR |CapFMOD | | init: A call to a standard soundcard driver failed, which could possibly mean a bug in the driver or resources were missing or exhausted. 2010-01-18 20:03:11.397340|ERROR |CapFMOD | | init: A call to a standard soundcard driver failed, which could possibly mean a bug in the driver or resources were missing or exhausted. 2010-01-18 20:03:11.397340|ERROR |CapSoundSet | | Error getting default capture device 2010-01-18 20:03:11.398340|INFO |PreProSpeex | 1| Speex version: speex-1.2beta3 2010-01-18 20:03:11.413340|ERROR |CapFMOD | | init: A call to a standard soundcard driver failed, which could possibly mean a bug in the driver or resources were missing or exhausted. 2010-01-18 20:03:11.413340|WARNING |ClientUI | 1| Error opening capture device: could not open capture device 2010-01-18 20:03:11.459340|ERROR |FMODPlayback | | init: A call to a standard soundcard driver failed, which could possibly mean a bug in the driver or resources were missing or exhausted. 2010-01-18 20:03:11.459340|WARNING |ClientUI | 1| Error opening playback device: could not open playback device

EDIT: After reading a bit more on the forums i realise that most people are getting the error with Realtek? can anybody else confirm this? or is it just a general problem.Last edited by MrBeav2009; 19-01-2010 at 16:33.
-
20-01-2010, 02:23 #2
One of my client crashed too and he ALSO have a realtek sound card
i think it is closely related
waiting for beta12 for correction
-
20-01-2010, 10:46 #3
-= TeamSpeak User =-
- Join Date
- Jan 2010
- Location
- Ukraine
- Posts
- 5
I have the same problem with teamspeak crashing!!
Plz solve it
-
20-01-2010, 11:40 #4
-= TeamSpeak User =-
- Join Date
- Jan 2010
- Location
- earth
- Posts
- 3
Same here.
After updating to latest beta ts3 keeps crashing on start.
OS: Win XP SP3
Soundchip: RealTek ALC889 onboard
debug file:
-
20-01-2010, 11:47 #5
-= TeamSpeak Team =-
- Join Date
- Jun 2008
- Posts
- 7,762
Don't add dumpfiles here!
http://forum.teamspeak.com/showthread.php?t=46880
Thread Information
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
Similar Threads
-
Bug? Server dieing getFailedLocks()
By MichaelP in forum Bug ReportsReplies: 14Last Post: 13-01-2010, 19:01 -
Teamspeak Crashing on Startup
By Stanford in forum [TeamSpeak 2] Client SupportReplies: 1Last Post: 19-10-2009, 18:46 -
Teamspeak crashing WoW
By Tethren in forum [TeamSpeak 2] Client SupportReplies: 0Last Post: 18-01-2008, 17:28 -
Server will not remember
By Pappy in forum [TeamSpeak 2] Server SupportReplies: 17Last Post: 17-12-2007, 18:47 -
Teamspeak needs to release higher codecs, at least 44k
By Gnomore in forum [TeamSpeak 2] General QuestionsReplies: 21Last Post: 08-08-2005, 21:17


Reply With Quote

