Crash to desktop without error message

MasterYodakin · August 4, 2021, 4:49pm

I have lived with them for a year. Now its the dammed 00005 error…

I still dont get it why it works fine on an inferior computer

MichaMMA · August 4, 2021, 4:53pm

important is a 00005 without any kind of mentioned " .dll " . There are 00005 errors which point to driver or hardware issues.

TwistedApe2554 · August 4, 2021, 5:06pm

lucky you !

FosselFliegt · August 4, 2021, 6:20pm

Confirmed. Yesterday CTD on the default Baron 15 min into a flight. No addons in the Community folder…

JorahdasAndal · August 4, 2021, 9:22pm

New statement from the developers regarding the different issues we’re suffering from.

Check the support team’s Twitter, can’t post links.

They’re planning an upcoming hotfix, but seems like the CTDs won’t be fixed until WU6.

That’s the 24th of August…

The hotfix will fix things like volumetric clouds.
No use for me since I can’t even play the game for more than 40 minutes before a CTD happens.
Sometimes it happens after around 10 minutes.

Disaster

DensestSnail693 · August 4, 2021, 11:10pm

Keep an eye on temperatures, it’s kind of the right timeframe for MB components to heat up.

ArisenAutumn59 · August 4, 2021, 11:50pm

If you update drivers without first uninstalling what was there, CTDs will follow.

TheAviator3506 · August 5, 2021, 7:28am

Jorahdas,

This is very frustrating for you. I noticed that my USB Saitek trim wheel was causing pauses when I operated it for the first time after the simulator had loaded. After the SU5 update, the pause had extended to around a minute! After the hot-fix, I returned to a 4 second pause.

I have found a work-around for this annoying problem which has lead to one CTD recently…

When/after I press ‘Fly’ I move my Saitek trim wheel backward and forward during the loading phase. No more pauses in the simulator when I operate the trim wheel now! I now move all my USB controllers during this loading phase however, it has only been the trim wheel causing the problems and one CTD when I used it for the first time after the simulator had loaded.

I have just discovered that moving my USB controllers during the first/initial loading phase of the simulator a CTD occurs, (Super Cub and Rhino image). This does not happen if moving my USB controllers after pressing ‘FLY’.
Solution for me: dont fiddle with my controllers during the first loading phase of the simulator!

I wonder sometimes if some people who are having CTD’s, may have manually edited or changed some of the default files before the SU5 update and if this could be a possible issue for some people too, making a change that is not compatible with this latest rendition of the simulator, (or a change that MIGHT stop a file being over written during an update). I would not assume that such changes would be over written by the update, (perhaps?).

Charles.

Simtech92 · August 5, 2021, 7:59am

I’ve a crash during loading screen, after check updates. I’ve a steam version, while with MS version i haven’t problems
This is my dump:

*** WARNING: Unable to verify checksum for WwiseLibPCx64P.dll
*** WARNING: Unable to verify checksum for CoherentGTJS.dll
*** WARNING: Unable to verify checksum for CoherentUIGTDevelopment.DLL
*** WARNING: Unable to verify checksum for CoherentUIGT.dll
*** WARNING: Unable to verify checksum for ■■■.dll

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 10593

Key  : Analysis.DebugAnalysisManager
Value: Create

Key  : Analysis.Elapsed.mSec
Value: 57774

Key  : Analysis.Init.CPU.mSec
Value: 280

Key  : Analysis.Init.Elapsed.mSec
Value: 55224

Key  : Analysis.Memory.CommitPeak.Mb
Value: 661

Key  : FailFast.Name
Value: FATAL_APP_EXIT

Key  : FailFast.Type
Value: 7

Key  : Timeline.Process.Start.DeltaSec
Value: 22483

Key  : WER.OS.Branch
Value: vb_release

Key  : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key  : WER.OS.Version
Value: 10.0.19041.1

Key  : WER.Process.Version
Value: 1.18.14.0

NTGLOBALFLAG: 0

PROCESS_BAM_CURRENT_THROTTLED: 0

PROCESS_BAM_PREVIOUS_THROTTLED: 0

APPLICATION_VERIFIER_FLAGS: 0

CONTEXT: 3fdfc0bd491f76c9 – (.cxr 0x3fdfc0bd491f76c9)
Unable to read context, Win32 error 0n30
Resetting default scope

EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00007ff8e0e6286e (ucrtbase!abort+0x000000000000004e)
ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
ExceptionFlags: 00000001
NumberParameters: 1
Parameter[0]: 0000000000000007
Subcode: 0x7 FAST_FAIL_FATAL_APP_EXIT

PROCESS_NAME: FlightSimulator.exe

ERROR_CODE: (NTSTATUS) 0xc0000409 - Il sistema ha rilevato un sovraccarico di un buffer basato su stack in questa applicazione. Il sovraccarico potrebbe consentire a un utente non autorizzato di assumere il controllo dell’applicazione.

EXCEPTION_CODE_STR: c0000409

EXCEPTION_PARAMETER1: 0000000000000007

STACK_TEXT:
00000039d497ded0 00007ff8e0e61f9f 00000039d497df00 00007ff7c42cacea 00000039d497df30 00007ff8e07cc247 00000039d497df60 00007ff8e2ff5270 00000039d497e080 00007ff8e2fdc776 00000039d497e0c0 00007ff8e2ff217f 00000039d497e130 00007ff8e2fa1454 00000039d497e160 00007ff8e2fa11a5 00000039d497e870 00007ff8e06f4ed9 00000039d497f060 00007ff8c1f96480 00000039d497f140 00007ff8d12f0b02 00000039d497f1a0 00007ff8d12f1a74 00000039d497f210 00007ff7c3c69855 00000039d497f360 00007ff82fb21c6a 00000039d497f4f0 00007ff82fd0b7f0 00000039d497f610 00007ff82fd0c7f9 00000039d497f750 00007ff7c3814178 00000039d497f7c0 00007ff7c3a26f87 00000039d497f940 00007ff7c3a264b0 00000039d497f990 00007ff7c34ddcb5 00000039d497f9d0 00007ff7c42ca7f2 00000039d497fa10 00007ff8e0fd7034 00000039d497fa50 00007ff8e2fa2651 00000039d497fa80 0000000000000000 : 0000003900000003 0000000000000003 0000004000001000 0000000001000000 : ucrtbase!abort+0x4e
: 0000000014e0c000 0000000014e0c000 0000000000000000 00000000ffffffff : ucrtbase!terminate+0x1f
: 0000000000000000 00007ff7c42cac90 0000000000000000 0000000000000000 : FlightSimulator!FlightSimGetProcessId+0x160043a
: 00000039d497e1a0 00007ff8e309663c 0000000000000000 00000039d497e138 : KERNELBASE!UnhandledExceptionFilter+0x1e7
: 00007ff8e30c2a24 00007ff8e2f50000 00000039d497e1a0 00007ff8e2f80e7b : ntdll!RtlUserThreadStart$filt$0+0xa2
: 0000000000000000 00000039d497e6a0 00000039d497f080 0000000000000000 : ntdll!_C_specific_handler+0x96
: 0000000000000000 00000039d497e6a0 00000039d497f080 0000000000000001 : ntdll!RtlpExecuteHandlerForException+0xf
: 0000000000000000 00000039d497ef20 0000000000000000 00000039d497e8b0 : ntdll!RtlDispatchException+0x244
: 00000039d497f1c0 00007ff8d130a508 00000039d497f1c0 74655370756f7247 : ntdll!RtlRaiseException+0x185
: 000000000000003f 00007ff8d13009b7 0000000000000040 00007ff8c1fa5280 : KERNELBASE!RaiseException+0x69
: 00000039d497f1c0 00007ff7c5ff3968 0000000000000000 0000017946bf9160 : VCRUNTIME140!_CxxThrowException+0x90
: 00000039d497f230 0000000000000000 0000003900000000 0000000000000000 : lib_json!Json::LogicError::LogicError+0x92
: 0000000000000000 0000000000000000 0000017946bf9160 0000017b15deecc0 : lib_json!Json::Value::asCString+0xa4
: 00000039d497f540 0000017946bf9780 00000179487d4d10 00007ff8b8a68c79 : FlightSimulator!FlightSimGetProcessId+0xf9efa5
: 0000000000000000 0000000000000000 0000000000000000 00000039d497f618 : XPlatCppWindows!PlayFab::QoS::PlayFabQoSApi::WriteEventsFailureCallBack+0x4119ba
: 0000017aff0ea260 00007ff7c3c7bb76 0000017aff0ea278 0000017b297fae00 : XPlatCppWindows!PlayFab::QoS::PlayFabQoSApi::WriteEventsFailureCallBack+0x5fb540
: 000000000000000b 000000000000000b 0000000000000000 0000000000000012 : XPlatCppWindows!PlayFab::QoS::PlayFabQoSApi::WriteEventsFailureCallBack+0x5fc549
: 0000003643182665 0000017969c56300 0000000000000000 0000000000000000 : FlightSimulator!FlightSimGetProcessId+0xb498c8
: 0000000000000000 00007ff7c62ee100 0000000000000001 0000000000000007 : FlightSimulator!FlightSimGetProcessId+0xd5c6d7
: af35876900009fe0 af358769e4469aa8 00007ff7c34e05b0 0000000000000000 : FlightSimulator!FlightSimGetProcessId+0xd5bc00
: 000000000000000a 0000000000000000 0000000000000000 01d78980f873e5d1 : FlightSimulator!FlightSimGetProcessId+0x813405
: 0000000000000000 0000000000000000 0000000000000000 00007ff82c5f0000 : FlightSimulator!FlightSimGetProcessId+0x15fff42
: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : kernel32!BaseThreadInitThunk+0x14
: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : ntdll!RtlUserThreadStart+0x21

SYMBOL_NAME: ucrtbase!abort+4e

MODULE_NAME: ucrtbase

IMAGE_NAME: ucrtbase.dll

STACK_COMMAND: .cxr 0x3fdfc0bd491f76c9 ; kb

FAILURE_BUCKET_ID: FAIL_FAST_FATAL_APP_EXIT_c0000409_ucrtbase.dll!abort

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

IMAGE_VERSION: 10.0.19041.789

FAILURE_ID_HASH: {e31753ac-c98a-8055-3663-47e707543d20}

Followup: MachineOwner

DensestSnail693 · August 5, 2021, 8:46am

As soon as I see WwiseLibPCx64 I know this is linked to Audiokinetic which I believe FBW and possibly others use for their sound recording. I don’t have a cure but would suggest a re install or even an uninstall until there’s a fix.

Simtech92 · August 5, 2021, 8:57am

It’s incredible that does not even get to the main menu, instead MS version work perfectly. Before the mega patch, steam version work perfectly too

DensestSnail693 · August 5, 2021, 9:03am

Have you tried disabling audio before loading or even swapping audio outputs? Maybe that will at least get you going.

MichaMMA · August 5, 2021, 10:48am

it’s second case I read this situation where Steam installation don’t come over the login popup in case there is a parallel MS-Store installation of MSFS on the same PC.
( CTD when connected to the internet )
( note: the heading of these topic is bit missleading )

To be sure check all other possible reasons related to the dll we seen in error message.

uninstall mods
ensure installed English Lang Pack US
check installed audio tools like Asus Sonix * ( deinstall )
check for a service called “Nahimic” and disable it
uninstall tools like Process Lasso if installed

But I assume it’s same as the other user reported. I guess somewhat with the user-rights / accounting ( may be conflict because msfs is installed twice ).

It may good idea to join into the other topic.

PS::

nope… it is a different lib

GoingLeech3 · August 5, 2021, 10:52am

Picture of Rhino…checking for updates…CTD today…
We have exceeded 5000 replies in this topic !

DensestSnail693 · August 5, 2021, 10:54am

I believe you however if I see a dll mentioned in a crash report I google and when I did that’s what it brought up. Whether it’s the actual problem or not I haven’t a clue but this tecnique has helped me in tha past… and yes audio is often the problem.

MichaMMA · August 5, 2021, 10:57am

the important point for the issue rerported from @Simtech92 is the parellel installation of MSFS over Steam AND MS-Store. I assume in this case the login fails and we see these strange error message.
But as mentioned, better discuss this situation within the existing topic about that

Simtech92 · August 5, 2021, 11:25am

Thanks for help.
Unfortunately not work also following the steps.
I uninstalled MS version before to try Steam version

MichaMMA · August 5, 2021, 11:37am

yes… similar to what the other user reported… nothing helped. I was also not 100% exact. The other user installed the MS-Store version, because Steam-install had the issue - thus may be we should better say ‘where both licenses exist’. It’s may be an accounting thing ( support can help ? ) , or a profile issue. But, on other side, we learned that sometime completly different and strange things happend

At least… don’t forget the ZenDesk ticket.

MrTreeHugger269 · August 5, 2021, 1:59pm

As I already said in the other thread, the second installation has nothing to do with the CTD since the same issue was there without the second installation present. I just installed the game pass version to check if something with my system is wrong that it cannot run FS2020 anymore. The crash is not related to the second FS installation…

MichaMMA · August 5, 2021, 2:02pm

yep… I corrected me in former post