August 13, 20214 yr Just fired up FS2020 after a week. Immediate CTD. I never get CTD's. Dug into things and found it was a driver update from ASUS and an app that auto-installed on my system. Something called A-volute. Uninstalled it and FS came up fine. Hope this helps someone. My suspicions are a lot of CTDs are from clashes with drivers or apps like this. "Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x00000000 Faulting module name: AudioDevProps2.dll, version: 2.6.4.0, time stamp: 0x60b0a9e5 Exception code: 0xc0000005 Fault offset: 0x000000000001ba66 Faulting process id: 0x1984 Faulting application start time: 0x01d7905fe9fd5e22 Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.15.0_x64__8wekyb3d8bbwe\FlightSimulator.exe Faulting module path: C:\ProgramData\A-Volute\A-Volute.SonicStudio3\Modules\ScheduledModules\x64\AudioDevProps2.dll Report Id: 60617870-561c-4597-9155-069c6efd4017 Faulting package full name: Microsoft.FlightSimulator_1.18.15.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App" Bennett
August 13, 20214 yr Interesting. A-Volute seems to be connected to the Sonic Studio. Good find. AMD Ryzen R9 9950X3D | Asus Astral RTX 5080 OC | 32 GB DDR5 6000 CL30 | 3440x1440 G-Sync | Logitech Pro Throttles Rudder Yoke Panels | Thrustmaster T.16000M FCS | TrackIR 5 | Oculus Rift S
August 14, 20214 yr @Jaxsimmer Thanks. BTW, how does one go about accessing all this crash data? 10900K, 3080TI, Maximus XIII, 32 GB, Win10.
Archived
This topic is now archived and is closed to further replies.