Microsoft Teams crashes audiodg.exe (v10.0.22621.1344) when using USB headset (plugged directly to laptop) - message to problem with audio device restart computer

Question

Microsoft Teams crashes audiodg.exe (v10.0.22621.1344) when using USB headset (plugged directly to laptop) - message to problem with audio device restart computer

Jeremiah Penn 10

User's laptop is dell latitude 5530 and win11. When she is using teams and shares a screen or video conference calls then the USB headset will eventually stop working and teams throws up the message "problem with audio device" can't connect audio device, restart your computer". She restarted many times and this cycle continues. I have updated windows and dell drivers. The headset is plugged directly into the laptop. event view shows audiodg.exe crashing at the times.

SokiGuo-MSFT 31,551 Reputation points Microsoft External Staff

2023-05-05T07:15:55.6+00:00

Hi

Haven't received your message for a long time.

Do you have any further issue on this topic?
Anonymous

2023-06-07T05:31:03.6833333+00:00
Having the same issue with multiple different Jabra teams certified headsets on Latitude 5430's running Win11 22H2, I have ensured that all firmware on the Jabra Evolve 20 SE and Jabra Pro 9450 is up to date using Jabra Direct.
Security updates and firmware updates for the OS and Laptop are coming straight from Windows Updates and are all updated. I have reimaged the laptop's using the latest driver pack from May 2023 which had realtek audio driver updates and a few others relating to audio.

I have also tested the following before remaking the image with the latest driver packs:

disabled Audio enhancements

updated the Audio driver via Dell Support Assist

reinstalled audio drivers (Delete from device manager)

tried multiple usb audio devices, same issue (Jabra Evolve 20 and Jabra Pro 9450) I have a user testing a laptop rolled back to Win 10 21H2 to confirm that it is the OS causing the Audiodg.exe to crash currently. Application error and windows error reporting below after reimage on Win11 22H2.

Log Name:      Application
Source:        Application Error
Date:          7/06/2023 12:07:07 PM
Event ID:      1000
Task Category: Application Crashing Events
Level:         Error
Keywords:
User:          LOCAL SERVICE
Computer:
Description:
Faulting application name: AUDIODG.EXE, version: 10.0.22621.317, time stamp: 0xb43ec052
Faulting module name: ntdll.dll, version: 10.0.22621.317, time stamp: 0x6cf39caa
Exception code: 0xc0000374
Fault offset: 0x000000000010c1c9
Faulting process id: 0x0x884
Faulting application start time: 0x0x1D998D7575BBF51
Faulting application path: C:\WINDOWS\system32\AUDIODG.EXE
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 4cceb41d-cdf9-4f5f-a9fc-f9ff5b0e1b6b
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="[http://schemas.microsoft.com/win/2004/08/events/event">]
<System>
<Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" />
<EventID>1000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>100</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2023-06-07T02:07:07.0826186Z" />
<EventRecordID>2317</EventRecordID>
<Correlation />
<Execution ProcessID="10760" ThreadID="8544" />
<Channel>Application</Channel>
<Computer></Computer>
<Security UserID="S-1-5-19" />
</System>
<EventData>
<Data Name="AppName">AUDIODG.EXE</Data>
<Data Name="AppVersion">10.0.22621.317</Data>
<Data Name="AppTimeStamp">b43ec052</Data>
<Data Name="ModuleName">ntdll.dll</Data>
<Data Name="ModuleVersion">10.0.22621.317</Data>
<Data Name="ModuleTimeStamp">6cf39caa</Data>
<Data Name="ExceptionCode">c0000374</Data>
<Data Name="FaultingOffset">000000000010c1c9</Data>
<Data Name="ProcessId">0x884</Data>
<Data Name="ProcessCreationTime">0x1d998d7575bbf51</Data>
<Data Name="AppPath">C:\WINDOWS\system32\AUDIODG.EXE</Data>
<Data Name="ModulePath">C:\WINDOWS\SYSTEM32\ntdll.dll</Data>
<Data Name="IntegratorReportId">4cceb41d-cdf9-4f5f-a9fc-f9ff5b0e1b6b</Data>
<Data Name="PackageFullName">
</Data>
<Data Name="PackageRelativeAppId">
</Data>
</EventData>
</Event>

Log Name:      Application
Source:        Windows Error Reporting
Date:          7/06/2023 12:07:10 PM
Event ID:      1001
Task Category: None
Level:         Information
Keywords:
User:          SYSTEM
Computer:
Description:
Fault bucket 1195746564217989711, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0 Problem signature:
P1: AUDIODG.EXE
P2: 10.0.22621.317
P3: b43ec052
P4: StackHash_32b9
P5: 10.0.22621.317
P6: 6cf39caa
P7: c0000374
P8: PCH_28_FROM_ntdll+0x000000000009F8C4
P9:
P10: Attached files:
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.cb80b08f-6eaf-4add-ba6e-22796d32bc15.tmp.WERInternalMetadata.xml These files may be available here:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_AUDIODG.EXE_11efbd85e138cf3511532a59ba822044a1b876_a5bf7d88_8ca817a7-6e69-4fea-a23c-5fe997f443f3 Analysis symbol:
Rechecking for solution: 0
Report Id: 4cceb41d-cdf9-4f5f-a9fc-f9ff5b0e1b6b
Report Status: 268435456
Hashed bucket: 98ee7aea9ddaca6f7098252a319b6a4f
Cab Guid: 0
Event Xml:
<Event xmlns="[http://schemas.microsoft.com/win/2004/08/events/event">]
<System>
<Provider Name="Windows Error Reporting" Guid="{0ead09bd-2157-539a-8d6d-c87f95b64d70}" />
<EventID>1001</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2023-06-07T02:07:10.0181813Z" />
<EventRecordID>2319</EventRecordID>
<Correlation />
<Execution ProcessID="14764" ThreadID="9888" />
<Channel>Application</Channel>
<Computer></Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="Bucket">1195746564217989711</Data>
<Data Name="BucketType">4</Data>
<Data Name="EventName">APPCRASH</Data>
<Data Name="Response">Not available</Data>
<Data Name="CabId">0</Data>
<Data Name="P1">AUDIODG.EXE</Data>
<Data Name="P2">10.0.22621.317</Data>
<Data Name="P3">b43ec052</Data>
<Data Name="P4">StackHash_32b9</Data>
<Data Name="P5">10.0.22621.317</Data>
<Data Name="P6">6cf39caa</Data>
<Data Name="P7">c0000374</Data>
<Data Name="P8">PCH_28_FROM_ntdll+0x000000000009F8C4</Data>
<Data Name="P9">
</Data>
<Data Name="P10">
</Data>
<Data Name="AttachedFiles">
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.cb80b08f-6eaf-4add-ba6e-22796d32bc15.tmp.WERInternalMetadata.xml</Data>
<Data Name="StorePath">\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_AUDIODG.EXE_11efbd85e138cf3511532a59ba822044a1b876_a5bf7d88_8ca817a7-6e69-4fea-a23c-5fe997f443f3</Data>
<Data Name="AnalysisSymbol">
</Data>
<Data Name="Rechecking">0</Data>
<Data Name="ReportId">4cceb41d-cdf9-4f5f-a9fc-f9ff5b0e1b6b</Data>
<Data Name="ReportStatus">268435456</Data>
<Data Name="HashedBucket">98ee7aea9ddaca6f7098252a319b6a4f</Data>
<Data Name="CabGuid">0</Data>
</EventData>
</Event>

1 answer

Your answer

SokiGuo-MSFT 31,551 Reputation points Microsoft External Staff

2023-05-05T07:15:55.6+00:00

Hi

Haven't received your message for a long time.

Do you have any further issue on this topic?

Answer 1

Michael Durkan 12,241 MVP

Hi

is the headset certified for Teams use? Who is the manufacturer and does their technical specs state that the device is certified? Does the headset install its own subset of drivers that you can update?

You could also rule this out by attempting to use the same headset on an alternative device and see if you can reproduce the issue?

Thanks

Michael

If the reply was helpful please upvote and/or accept as answer as this helps others in the community with similar questions. Thanks!

Jeremiah Penn 10 Reputation points

2023-05-02T16:10:21.5333333+00:00

The USB headset is "Plantronics Blackwire 3210 Mono USB-C Headset" and Compatible Softphones (Unified Communications):

Skype

Avaya: Avaya One X, Jabber, Webex, Avaya one-X Communicator, Avaya IP Agent,

BroadSoft UC-One 20.0.1 or above,

Cisco: CUCI-Connect®, CUCI-Lync™, Cisco IP Communicator, Cisco Unified Personal, Communicator (CUPC)

CounterPath® Bria

Dragon NaturallySpeaking (by Nuance)

Netphone

IBM Lotus Sametime

Microsoft: Office Communicator, Microsoft® Lync®

I do not see or find any subset of drivers by this device. What I see is audiodg.exe crashing simultaneously when the user gets the error message. We have about 100 in production, and a handful of users are experiencing this issue. mostly running Win11, and Win10 on a dell laptop 2 years old or newer.
SokiGuo-MSFT 31,551 Reputation points Microsoft External Staff

2023-05-03T07:15:51.4066667+00:00

Hi @Jeremiah Penn

Here is a link of the currently supported devices of Microsoft Teams: USB audio and video devices certified for Microsoft Teams

Do Teams meetings work without using a USB headset?

Can the headset be used normally on other software or devices?

To troubleshoot issues with Teams clients, please try checking for issues in the Teams web client.
Jeremiah Penn 10 Reputation points

2023-06-21T12:49:33.0533333+00:00

Yes, the Plantronics Blackwire 3210 Headset is on the support device. This issue is not happening wide spread. I added another user last week. Brand new desktop and brand new headset, and same device error message by MS Teams is thrown. When I looked into event logs same finding: audiodg.exe crashed. I removed audiodg.exe and we are still experiencing the same results with the USB headset and MS teams crashing during teams meeting. I did plantonic's software add-on. For one user, this seems to have resolved the issue. The other user no good effect, still having headset crash during teams meeting.
Anonymous

2023-11-18T03:42:56+00:00

I am having the same problem with audiodg. But it happens without headphones as well, just using the built-in sound of Asus Vivobook running Win 11. I am at the point where I am ready to toss this 6 month old i7 and go with a Mac.

Share via

Microsoft Teams crashes audiodg.exe (v10.0.22621.1344) when using USB headset (plugged directly to laptop) - message to problem with audio device restart computer

1 answer

Your answer