Forum

Results 1 to 6 of 6
  1. #1
    Join Date
    September 2018
    Posts
    1

    Teamspeak 3.2.2 (also earlier versions) randomly closes

    Aus dem Windows-Event Log:
    Name der fehlerhaften Anwendung: ts3client_win64.exe, Version: 3.2.2.0, Zeitstempel: 0x5b9b7cc9
    Name des fehlerhaften Moduls: ucrtbase.dll, Version: 10.0.17134.254, Zeitstempel: 0xea85cc89
    Ausnahmecode: 0xc0000409
    Fehleroffset: 0x000000000006e55e
    ID des fehlerhaften Prozesses: 0x2c1c
    Startzeit der fehlerhaften Anwendung: 0x01d44d17069c9550
    Pfad der fehlerhaften Anwendung: C:\Program Files\TeamSpeak 3 Client\ts3client_win64.exe
    Pfad des fehlerhaften Moduls: C:\WINDOWS\System32\ucrtbase.dll
    Berichtskennung: e54ffd5f-0763-4552-add8-be25dc9e2c1b


    Protokollname: Application
    Quelle: Application Error
    Datum: 15.09.2018 20:22:34
    Ereignis-ID: 1000
    Aufgabenkategorie100)
    Ebene: Fehler
    Schlüsselwörter:Klassisch
    Benutzer: Nicht zutreffend
    Computer: DESKTOP-M1PMHPN
    Beschreibung:
    Name der fehlerhaften Anwendung: ts3client_win64.exe, Version: 3.2.2.0, Zeitstempel: 0x5b9b7cc9
    Name des fehlerhaften Moduls: ucrtbase.dll, Version: 10.0.17134.254, Zeitstempel: 0xea85cc89
    Ausnahmecode: 0xc0000409
    Fehleroffset: 0x000000000006e55e
    ID des fehlerhaften Prozesses: 0x2c1c
    Startzeit der fehlerhaften Anwendung: 0x01d44d17069c9550
    Pfad der fehlerhaften Anwendung: C:\Program Files\TeamSpeak 3 Client\ts3client_win64.exe
    Pfad des fehlerhaften Moduls: C:\WINDOWS\System32\ucrtbase.dll
    Berichtskennung: e54ffd5f-0763-4552-add8-be25dc9e2c1b
    Vollständiger Name des fehlerhaften Pakets:
    Anwendungs-ID, die relativ zum fehlerhaften Paket ist:
    Ereignis-XML:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2018-09-15T18:22:34.309830700Z" />
    <EventRecordID>102777</EventRecordID>
    <Channel>Application</Channel>
    <Computer>DESKTOP-M1PMHPN</Computer>
    <Security />
    </System>
    <EventData>
    <Data>ts3client_win64.exe</Data>
    <Data>3.2.2.0</Data>
    <Data>5b9b7cc9</Data>
    <Data>ucrtbase.dll</Data>
    <Data>10.0.17134.254</Data>
    <Data>ea85cc89</Data>
    <Data>c0000409</Data>
    <Data>000000000006e55e</Data>
    <Data>2c1c</Data>
    <Data>01d44d17069c9550</Data>
    <Data>C:\Program Files\TeamSpeak 3 Client\ts3client_win64.exe</Data>
    <Data>C:\WINDOWS\System32\ucrtbase.dll</Data>
    <Data>e54ffd5f-0763-4552-add8-be25dc9e2c1b</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    </EventData>
    </Event>

  2. #2
    Join Date
    June 2008
    Posts
    18,409
    This Windows Crash report tells us nothing about the crash.
    Could be anything. From client or plugin or something else.

    We need a client log or a crash report from the client itself.
    When sending me private messages: Please make sure to include reference link to your forum thread or post.

    TeamSpeak FAQ || What should i report, when i open a client thread?

  3. #3
    Join Date
    June 2007
    Location
    in a house.
    Posts
    98
    same isue here, randomly closeing the client, never had it, noticed it the last 2 versions has this.

  4. #4
    Join Date
    August 2013
    Posts
    4
    I'm seeing the same random crashes in 3.2.2 that started with the last update. Removed and reinstalled the app with no change in behavior.

    I don't see a Windows crash report or any indication of issue other than the me eventually noticing that it's gotten quiet and the window has gone away.

    I've attached a client log from my most recent crash. All the crashed logs look the same, with no entries after the connection being finalized. Additionally, the crashdumps folder is empty.
    Attached Files Attached Files

  5. #5
    Join Date
    September 2012
    Posts
    6,080
    Please try the 3.2.3 Beta client and let us know if this is still happening.
    When sending PMs please make sure to include a reference link to the thread in question in the body of your message.

  6. #6
    Join Date
    August 2013
    Posts
    4
    Tried it last night with no crashes. Fingers crossed it seems to have fixed it. Thanks Chris.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Replies: 0
    Last Post: April 8th, 2017, 06:42 PM
  2. Replies: 1
    Last Post: July 12th, 2011, 03:24 PM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •