Vostro 5620, Windows 11 22H2, Audiodg.exe crashing when using 3CX

Hi all, 

Recently our IT department have been ordering both the Dell Vostro 5620 and Dell OptiPlex 3000 MFF devices for our staff to use. We have been deploying them using MDT and we have had no issues with previous models. 

Our main calling software for inhouse calls and outbound calls is 3CX. We have been using 3CX for a couple of years now and had no issues with errors or connection issues with calls before. However, when purchasing these devices, we are getting an error in our Event Viewer that says the following;

Faulting application name: AUDIODG.EXE, version: 10.0.22621.1344, time stamp: 0xc4144450
Faulting module name: ntdll.dll, version: 10.0.22621.1485, time stamp: 0xb7f0154a
Exception code: 0xc0000374
Fault offset: 0x000000000010be19
Faulting process ID: 0x0x11D8
Faulting application start time: 0x0x1D97E5C318578A2
Faulting application path: C:\windows\system32\AUDIODG.EXE
Faulting module path: C:\windows\SYSTEM32\ntdll.dll
Report ID: 88626603-337f-417d-b25d-7816d522a302
Faulting package full name:
Faulting package-relative application ID:

Audiodg.exe keeps crashing and when we are trying to take a call that comes in, we get a pop up saying "Could Not Find Audio Source" , and when looking in the details tab in Task Manager, Audiodg.exe is no longer running (crashed).

We have been having this issue for a couple months now. However due to us upgrading a lot of users devices to these new ones, we would like this issue to be resolved, or at least have a work around that doesn't make us either restart the device or reload the driver. We have read that this may have something to do with the latest Windows update for Windows 11 (22H2) however I would have thought by now that if this was already raised, it would be sorted. 

We like to keep all our devices Dell and due to us already purchasing these devices, we do not want to return them and go elsewhere. We have had no other issues with these devices other than our Audio Drivers crashing with 3CX.

To try and resolve this, we have had our 3CX supplier come and see us to take a look and we have done everything under the sun to try to resolve this issue, this would include redeploying a fresh Windows image, updating drivers, rolling back updates for drivers and many others. 

If anyone has a fix or any knowledge on why this may be happening that would be great to know as it really is starting to be a pain for users and especially our tele sales.

Thanks!