Constant CTD's after Jan 2022 update

I couldn’t find any way to uninstall it but just disabling it seems to have done the trick.

I’m still not happy though seeing as I have windows update set to not update hardware drivers so why did I get this BS that I have no need for pushed on me.

Is’nt this mixer part of asus sonic studio 3 ?

yep… a guess: may be there was a change with a windows update, not sure… At least some file-update-timestamps match with a windows-update-install date in my case ( I not have these tools installed, but the nahimic service ). May be these correlates with these lots of reports at nearly “same” time … a while ago there was a similar “report wave”, therefore it is included in FAQ :slight_smile:

Uninstall or disable Sonic permenently and update/reinstall your chipset and other mainboard drivers. Guaranteed fix.

somewhere in big ctd thread I mentioned that these sonic-tool was agin auto-re-installed. But since second uninstall, I never again seen this stuff.

1 Like

I’m also experiencing frequent crashes after this new update, I had just gotten it the day before the update came out and it was perfectly fine then (besides the pains of the download system since I got it from steam, and there were a couple of crashes while it was downloading but none while actually playing)

Unfortunately I don’t have an Asus board or Sonic Studio and unlike a lot of you guys I don’t have a terribly high end setup.

Faulting application name: FlightSimulator.exe, version:, time stamp: 0x00000000
Faulting module name: clr.dll, version: 4.8.4420.0, time stamp: 0x6109cbc8
Exception code: 0xc0000005
Fault offset: 0x00000000000b222f
Faulting process ID: 0x1de0
Faulting application start time: 0x01d806dc9c25063a
Faulting application path: FlightSimulator.exe
Faulting module path: v4.0.30319\clr.dll
Report ID: b6f94d1d-1968-4043-a4da-ff4b27e452d4
Faulting package full name:
Faulting package-relative application ID:

you not have Capture one installed ?

I do have it installed but I’ve not started it and have rebooted my machine multiple times without starting it.

The forum wouldn’t let me post the full path earlier due to it being flagged as a URL, and I didn’t realise I could use markdown codeblocks.
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll

Capture-One… the second big trouble maker: As example

EDIT: would point to this topic

the problem is that these tool have a explorer extension…
( there is a way to disable this , then it should also work )

May be I should repeat the link to the FAQ with the list of known in-comp. apps , or we need a forum banner :joy: :

You may not have started it but something has … modules do not crash while sitting domant on a harddrive.

I have CTD now 15 minutes after departure on LPPR.

Using Cessa Longitude.

Nome da aplicação com falha: FlightSimulator.exe, versão:, carimbo de data/hora: 0x00000000
Nome do módulo com falha: FlightSimulator.exe, versão:, carimbo de data/hora: 0x00000000
Código de exceção: 0xc0000005
Desvio de falha: 0x000000000013d963
ID do processo com falha: 0x3a6c
Hora de início da aplicação com falha: 0x01d806fc57457bd7
Caminho da aplicação com falha: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.21.18.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Caminho do módulo com falha: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.21.18.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
ID do Relatório: 6a32edd2-2d1b-4f44-a937-11a91321edef
Nome completo do pacote com falha: Microsoft.FlightSimulator_1.21.18.0_x64__8wekyb3d8bbwe
ID da aplicação relativa ao pacote com falha: App

Following the advice of renaming the dll as outlined in the above post and it hasn’t crashed yet :smiley:

1 Like

Constant crash to desktops.

Updated to hotfix Jan. Constant ctd.

Emptied commuty folder. Still crash to desktop.

Loading into flights and exiting flights. Loading the bar and just freezes.

I have had enough of this now.

Yep. Confirmed. Longitude is broken causing CTD

is there a topic about ?

Reinstalled Nvidia drivers without the HD sound…CTD stopped. I’m pretty sure the CTD is sound related as right before it crashed, I always got a sound stutter. FWIW, I don’t have the Sonic Studio but I do have the Realtek sound drivers and app. I think the Nvidia HD sound is somehow conflicting with Realtek and other sound packages when using MSFS2020.

I assume these is the main-root-cause for all issues, these realtek stuff. I forgot why I no longer installed these nvidia sound-drivers. Doing so since a long time ( before msfs was released ) … I only remember that I had some issues with it.

1 Like

The real question is what changed with MSFS2020 this patch to make it unstable with these drivers. I know for a fact that the Realtek drivers aren’t new and I’ve never had CTDs until the Jan MSFS2020 patch.

1 Like

I use Nvidia HD 2:1 stereo sound exclusively and have never had a problem. Realtek is disabled on all 3 of my PCs and unless something changes it always will be, their drivers are nothing but trouble.


Sorry, I am lost a bit, how do you use Nv drivers for a Realtek chip ?

Disable RT in the device manager, in fact I actually have it uninstalled in W11, presumably NV puts other drivers in it’s place. All audio now runs through my HDTV monitor on a Bluetooth 5.1 dongle although I can also enable the PC’s native BT 5.0 for audio if I choose.