Forum Discussion
New Teams Client is crashing when Jabra Evolve 75 Headset is muted by putting the microphone up
We have a strange issue with the new Teams client.
When the Mic is put up, the headset is actually muting Teams. However, with the new Teams client, if the headset is put Teams crashes sometimes.
Teams crashes also reproducible if the mic is put up before joining a conference.
Anybody has the same problem or a solution for that?
The Evolve Headset is connected via a Jabra 370 USB dongle.
69 Replies
Christian Dyck submitted a ticket 3 weeks ago. Today I was today told a bug was found and fix is planned for GA middle of March. I donât know if this bug is related to all issues in this thread but it sounds most scenarios are similar.
- 100% the exact same issue here - just since the New Teams. Same as everyone else - everything Jabra up to date but raising the boom to mute crashes Teams almost every time, Even if you aren't in a live call.
For me it seems a bit more stable if I turn off the softphone integration in the Jabra Link settings. But it could just be a coincidence.
Update: I've been using the headset with the softphone integration turned off for a while now, and Teams no longer crash when I raise the boom. You lose some features, but at least you avoid crashing Teams...
@Same problem here with Jabra75. Tried reinstall Teams, drivers etc. No help.
TimoTheR I have the same kind of problem but with Poly Voyager 4320 series headset.
I changed from Win10 to Win11, different PC, different headset.
I have a feeling it is related to Teams more than the Headset.
eric__coutu I Removed Jabra totally, now using my Sandberg cam mic and surface audio - and all works 100%. So some issues with audio(drivers?) with teams..
Waiting for big boys to fix this soon.
- Same issue here. Using Jabra 370 and wireless headphones. Crashes in the same way. event viewer shows these errors:
Faulting application name: DAX3API.exe, version: 3.30400.413.0, time stamp: 0x62cd22f4
Faulting module name: DAX3API.exe, version: 3.30400.413.0, time stamp: 0x62cd22f4
Exception code: 0xc0000005
Fault offset: 0x000000000013ce87
Faulting process id: 0x0x14E4
Faulting application start time: 0x0x1DA55269B631505
Faulting application path: C:\WINDOWS\System32\DriverStore\FileRepository\dax3_swc_aposvc.inf_amd64_943df24ce165050e\DAX3API.exe
Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\dax3_swc_aposvc.inf_amd64_943df24ce165050e\DAX3API.exe
Report Id: 742c5428-82ad-44bb-8658-31286434c1b6
Faulting package full name:
Faulting package-relative application ID:
-----------
Faulting application name: ms-teams.exe, version: 23335.232.2637.4844, time stamp: 0x65a8bdc4
Faulting module name: RtmPltfm.dll, version: 2023.45.1.15, time stamp: 0x65599e3f
Exception code: 0xc0000005
Fault offset: 0x00000000001739b6
Faulting process id: 0x0x25E0
Faulting application start time: 0x0x1DA553037520614
Faulting application path: C:\Program Files\WindowsApps\MSTeams_23335.232.2637.4844_x64__8wekyb3d8bbwe\ms-teams.exe
Faulting module path: C:\Program Files\WindowsApps\MSTeams_23335.232.2637.4844_x64__8wekyb3d8bbwe\RtmPltfm.dll
Report Id: 05f5c9b5-b7f0-4f31-b7e4-7fe9104b5405
Faulting package full name: MSTeams_23335.232.2637.4844_x64__8wekyb3d8bbwe
Faulting package-relative application ID: MSTeams
---------
Faulting application name: ms-teams.exe, version: 23335.232.2637.4844, time stamp: 0x65a8bdc4
Faulting module name: igd10um64xe.DLL, version: 31.0.101.4255, time stamp: 0x64138759
Exception code: 0xc0000005
Fault offset: 0x0000000000055ebe
Faulting process id: 0x0x4ED0
Faulting application start time: 0x0x1DA583BA39C998C
Faulting application path: C:\Program Files\WindowsApps\MSTeams_23335.232.2637.4844_x64__8wekyb3d8bbwe\ms-teams.exe
Faulting module path: C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_84b9f8c630338fb4\igd10um64xe.DLL
Report Id: 11a67944-35ae-4205-b7e6-94f269f0785c
Faulting package full name: MSTeams_23335.232.2637.4844_x64__8wekyb3d8bbwe
Faulting package-relative application ID: MSTeamsjohnyhammDifferent but pretty similiar logs for me. Totaly forgot about eventviewer.
Here ist what I got from todays crashing - 4 times in a row:
Name der fehlerhaften Anwendung: ms-teams.exe, Version: 23335.232.2637.4844, Zeitstempel: 0x65a8bdc4
Name des fehlerhaften Moduls: ntdll.dll, Version: 10.0.22000.2713, Zeitstempel: 0x5179e735
Ausnahmecode: 0xc0000005
Fehleroffset: 0x000000000001d4d1
ID des fehlerhaften Prozesses: 0x4480
Startzeit der fehlerhaften Anwendung: 0x01da57fd7e5c6272
Pfad der fehlerhaften Anwendung: C:\Program Files\WindowsApps\MSTeams_23335.232.2637.4844_x64__8wekyb3d8bbwe\ms-teams.exe
Pfad des fehlerhaften Moduls: C:\WINDOWS\SYSTEM32\ntdll.dll
Berichtskennung: 2c80cca2-2523-4375-9b19-f5dcf4eff103
Vollständiger Name des fehlerhaften Pakets: MSTeams_23335.232.2637.4844_x64__8wekyb3d8bbwe
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: MSTeams----------
Name der fehlerhaften Anwendung: ms-teams.exe, Version: 23335.232.2637.4844, Zeitstempel: 0x65a8bdc4
Name des fehlerhaften Moduls: RtmCodecs.dll, Version: 2023.45.1.15, Zeitstempel: 0x65599e2c
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00000000001be1d7
ID des fehlerhaften Prozesses: 0x1414
Startzeit der fehlerhaften Anwendung: 0x01da58032246cd53
Pfad der fehlerhaften Anwendung: C:\Program Files\WindowsApps\MSTeams_23335.232.2637.4844_x64__8wekyb3d8bbwe\ms-teams.exe
Pfad des fehlerhaften Moduls: C:\Program Files\WindowsApps\MSTeams_23335.232.2637.4844_x64__8wekyb3d8bbwe\RtmCodecs.dll
Berichtskennung: 306cc638-1cc7-4827-ba5f-a9ba40ed97d0
Vollständiger Name des fehlerhaften Pakets: MSTeams_23335.232.2637.4844_x64__8wekyb3d8bbwe
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: MSTeams----------
Name der fehlerhaften Anwendung: ms-teams.exe, Version: 23335.232.2637.4844, Zeitstempel: 0x65a8bdc4
Name des fehlerhaften Moduls: igd10um64xe.DLL, Version: 30.0.101.1692, Zeitstempel: 0x624a6688
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00000000000d2763
ID des fehlerhaften Prozesses: 0x4aa4
Startzeit der fehlerhaften Anwendung: 0x01da58033a6b9e7e
Pfad der fehlerhaften Anwendung: C:\Program Files\WindowsApps\MSTeams_23335.232.2637.4844_x64__8wekyb3d8bbwe\ms-teams.exe
Pfad des fehlerhaften Moduls: C:\WINDOWS\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_9bec328ff2d1d2ad\igd10um64xe.DLL
Berichtskennung: f3bb82d1-07ed-4a35-bf06-bb3ebe28d29d
Vollständiger Name des fehlerhaften Pakets: MSTeams_23335.232.2637.4844_x64__8wekyb3d8bbwe
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: MSTeams----------
Name der fehlerhaften Anwendung: ms-teams.exe, Version: 23335.232.2637.4844, Zeitstempel: 0x65a8bdc4
Name des fehlerhaften Moduls: RtmPltfm.dll, Version: 2023.45.1.15, Zeitstempel: 0x65599e3f
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00000000000db501
ID des fehlerhaften Prozesses: 0x4dc8
Startzeit der fehlerhaften Anwendung: 0x01da541b871a015c
Pfad der fehlerhaften Anwendung: C:\Program Files\WindowsApps\MSTeams_23335.232.2637.4844_x64__8wekyb3d8bbwe\ms-teams.exe
Pfad des fehlerhaften Moduls: C:\Program Files\WindowsApps\MSTeams_23335.232.2637.4844_x64__8wekyb3d8bbwe\RtmPltfm.dll
Berichtskennung: 89dd60e5-6428-4f16-8b95-c20a83865375
Vollständiger Name des fehlerhaften Pakets: MSTeams_23335.232.2637.4844_x64__8wekyb3d8bbwe
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: MSTeams- I submitted a support ticket to Jabra as well.
Christian Dyckin our company in Italy with something about 180 units of Jabra Evolve 2 55 certified headset we're experiencing the same issue with mute/unmute fuction of the microphone in the latest version of the new teams. We disabled the function on the jabra direct app for now and we're waiting for a fix ASAP.
Nicola
- we're experiencing the same issue too, Jabra Bluetooth connected headsets (65, 85, Ear buds) on Dell laptops
this happens since a few weeks allready... multiple devices with different Jabra Headsets....
strangest thing i also got a new notebook, switched from a dell from 2016 to a brandnew HP one... and since the new device the crash happens almost everytime i mute or unmute... sometimes also into a call without any un-/mute...
on the old device it happend only sometimes, not always!
this is only with the "NEW, v2" Teams client, it doesn't happen with the classic teams client! đ- for me its working since ah few weeks again.. but today something else started... it doesn't properly un-/mute when using the beam ... đ¤ˇâ:male_sign:
- We have same issue with different Jabra headset as well. Also with Evolve Buds 2 so not only related to mute/unmute boom activity. Sometime the client crash as well by simply mute/unmute the teams klient from the UI and also crash sometime simply by joining a meeting?
Does all you having the issue also have the headset connected with BT on the mobile phone?If the headset is muted with the "arm up" it crashes directly, while joining a meeting - just experienced it 3 times in a row.
Headset is not connected via BT to mobile phone in my case.- We have Dell computers and facing the same problems. Do you also have Dell computers? Or no correlation with that.
Christian Dyck same issue here with a Jabra Link 380 + Jabra Evolve 2 65; I've worked around it by disabling the boom functions in Jabra direct.
I'll re-enable these once they fix whatever the issue is. It's annoying but better than crashing mid-meeting.
Same issue here. reset didn't work for me either!
