game crashed and the mdmp file

[Rod Redline]

so my fsx crashed and basically i run windbg and check the mdmp file and this is what i got :


Microsoft (R) Windows Debugger Version 10.0.25200.1003 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Program Files (x86)\Steam\steamapps\common\FSX\fsx_62615_crash_2022_10_12T6_46_26C0.mdmp]
Comment: 'Minidump: C:\Program Files (x86)\Steam\steamapps\common\FSX\fsx.exe
'
User Mini Dump File: Only registers, stack and portions of memory are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Version 19043 MP (16 procs) Free x86 compatible
Product: WinNt, suite: SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Debug session time: Wed Oct 12 13:46:27.000 2022 (UTC + 7:00)
System Uptime: not available
Process Uptime: 0 days 0:08:04.000
................................................................
................................................................
................................................................
............................................
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(5494.6744): Access violation - code c0000005 (first/second chance not available)
For analysis of this file, run !analyze -v
eax=00000000 ebx=44491ca8 ecx=00530053 edx=009cc000 esi=44491c58 edi=44491c68
eip=772839bc esp=00aaca20 ebp=00aaca2c iopl=0 nv up ei pl nz ac po nc
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00200212
ntdll!NtGetContextThread+0xc:
772839bc c20800 ret 8
0:000> !analyze -v
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************


KEY_VALUES_STRING: 1

Key : AV.Fault
Value: Execute

Key : Analysis.CPU.mSec
Value: 4421

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 62751

Key : Analysis.IO.Other.Mb
Value: 5

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 48

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

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

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

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

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: 10.0.62615.0


FILE_IN_CAB: fsx_62615_crash_2022_10_12T6_46_26C0.mdmp

COMMENT: Minidump: C:\Program Files (x86)\Steam\steamapps\common\FSX\fsx.exe


CONTEXT: (.ecxr)
eax=9152e0c0 ebx=00007576 ecx=00530053 edx=009cc000 esi=7c5f3a50 edi=0000800a
eip=0c2572ff esp=00aaf624 ebp=00aaf638 iopl=0 nv up ei ng nz na pe nc
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00210286
0c2572ff ?? ???
Resetting default scope

EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 0c2572ff
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000008
Parameter[1]: 0c2572ff
Attempt to execute non-executable address 0c2572ff

PROCESS_NAME: fsx.exe

EXECUTE_ADDRESS: c2572ff

FAILED_INSTRUCTION_ADDRESS:
+0
0c2572ff ?? ???

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 00000008

EXCEPTION_PARAMETER2: 0c2572ff

IP_ON_HEAP: 0c2572ff
The fault address in not in any loaded module, please check your build's rebase
log at <releasedir>\bin\build_logs\timebuild\ntrebase.log for module which may
contain the address if it were loaded.

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
00aaf620 7c5edd92 9152e0c0 0000800a 000a0c3c 0xc2572ff
00aaf638 7c5ee0b4 000a0c3c 917d1ea8 00aaf6dc uiautomationcore!EventMap::AddEntry+0x31
00aaf650 7c5d7999 917d1ea8 00007576 07a50003 uiautomationcore!MsaaBridge::RaiseAutomationPropertyChangedEvent+0x7c
00aaf6bc 07a0292c 917d1ea8 00007576 07a50003 uiautomationcore!UiaRaiseAutomationPropertyChangedEvent+0x90
00aaf6ec 07a02ad0 917d1ea8 00007576 07a50003 xuipc!XuiShowMessageBox+0xbac
00aaf724 079e70c6 000f0a16 00000004 07a50003 xuipc!XuiShowMessageBox+0xd50
00aaf804 079eac34 000f0a16 000d0b0e 00000001 xuipc!XuiMenuPush+0x376
00aaf8dc 079ddfcf 00aaf950 00000000 916bbad0 xuipc!XuiDynamicMenuInvalidate+0xab4
00aaf8f0 079d1a12 000f0a16 00aaf950 9152ead0 xuipc!XuiReturnAutomationProvider+0xb36f
00aaf90c 079d1ae3 000f0a16 00aaf950 00aaf950 xuipc!XuiSendMessage+0xc2
00aaf924 079e18e7 000f0a16 00aaf950 084030a0 xuipc!XuiBubbleMessage+0x33
00aaf978 07439b16 00aaf998 00010000 00000200 xuipc!XuiProcessMouse+0x157
00aaf9f8 7a1ccb16 084030a0 000a0c3c 00000200 api!Ordinal157+0x1426
00aafa18 75f00bcb 000a0c3c 00000200 00000000 ui!SimXUIWindow_SynthesizeMouseMoveEvent+0x146
00aafa44 75ef7b8a 7a1ccad0 000a0c3c 00000200 user32!_InternalCallWinProc+0x2b
00aafb28 75ef58fa 7a1ccad0 00000000 00000200 user32!UserCallWinProcCheckWow+0x33a
00aafb9c 75ee7a90 00aafbb4 79880000 00df47c0 user32!DispatchMessageWorker+0x22a
00aafba4 79880000 00df47c0 00df47c0 00aafbe8 user32!DispatchMessageA+0x10
00aafbb4 0741fd28 00df47c0 00393410 00393410 gameoverlayrenderer!OverlayHookD3D3+0x1d470
00aafbe8 07448c21 00393410 00393410 ffffffff api!Ordinal17+0x2bf8
00aafc14 0741f8b7 00aafcc8 00392757 00392730 api!Ordinal222+0xc261
00aafc1c 00392757 00392730 00393410 79f6cd96 api!Ordinal17+0x2787
00aafcc8 75d2fa29 009c9000 75d2fa10 00aafd34 fsx+0x2757
00aafcd8 77277b5e 009c9000 6a872357 00000000 kernel32!BaseThreadInitThunk+0x19
00aafd34 77277b2e ffffffff 77298cb7 00000000 ntdll!__RtlUserThreadStart+0x2f
00aafd44 00000000 0039189c 009c9000 00000000 ntdll!_RtlUserThreadStart+0x1b


STACK_COMMAND: ~0s; .ecxr ; kb

SYMBOL_NAME: uiautomationcore!EventMap::AddEntry+31

MODULE_NAME: uiautomationcore

IMAGE_NAME: uiautomationcore.dll

FAILURE_BUCKET_ID: SOFTWARE_NX_FAULT_c0000005_uiautomationcore.dll!EventMap::AddEntry

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x86

OSNAME: Windows 10

IMAGE_VERSION: 6.0.6001.18000

FAILURE_ID_HASH: {5cf31e53-cd69-3a4d-13a9-92adc8c30463}

Followup: MachineOwner
---------

Any tips to fix this?

[JJ FSX]

Better to post the text of the application event log crash event and identifying the secondary module in the event than posting this. Along with at least "some" description of your conditions and environment. Is this a new install or has it been working before but stopped working after an update etc, for example.

If it's not a new install, then define what changed since it last ran and post that information too. to give the people your asking help from some real info and not just a memory dump of which barely anyone knows or how to interpret or could interpret without specific technical info about your system and the exact conditions at the time of the crash.

Perhaps my step by step guide on how to successfully install FSX on Windows 11 & 10, will help, you might find your "symptom" there.

https://steamcommunity.com/app/314160/discussions/1/5427423328680814797/?tscn=1663703489

[Rod Redline]

Originally posted by JJ FSX:

Better to post the text of the application event log crash event and identifying the secondary module in the event than posting this. Along with at least "some" description of your conditions and environment. Is this a new install or has it been working before but stopped working after an update etc, for example.

If it's not a new install, then define what changed since it last ran and post that information too. to give the people your asking help from some real info and not just a memory dump of which barely anyone knows or how to interpret or could interpret without specific technical info about your system and the exact conditions at the time of the crash.

Perhaps my step by step guide on how to successfully install FSX on Windows 11 & 10, will help, you might find your "symptom" there.

https://steamcommunity.com/app/314160/discussions/1/5427423328680814797/?tscn=1663703489

Thank you mate

[Rod Redline]

Originally posted by JJ FSX:

Better to post the text of the application event log crash event and identifying the secondary module in the event than posting this. Along with at least "some" description of your conditions and environment. Is this a new install or has it been working before but stopped working after an update etc, for example.

If it's not a new install, then define what changed since it last ran and post that information too. to give the people your asking help from some real info and not just a memory dump of which barely anyone knows or how to interpret or could interpret without specific technical info about your system and the exact conditions at the time of the crash.

Perhaps my step by step guide on how to successfully install FSX on Windows 11 & 10, will help, you might find your "symptom" there.

https://steamcommunity.com/app/314160/discussions/1/5427423328680814797/?tscn=1663703489

OKay, i try it and after a slightly 20 minutes of flying i got ctd and when i check the event viewer this is what i got :

Faulting application name: fsx.exe, version: 10.0.62615.0, time stamp: 0x559f9a9a
Faulting module name: KERNEL32.DLL, version: 10.0.19041.1889, time stamp: 0x20566761
Exception code: 0xc0000005
Fault offset: 0x0001e86b
Faulting process id: 0x54b0
Faulting application start time: 0x01d8e2fc7e6cfe49
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\FSX\fsx.exe
Faulting module path: C:\WINDOWS\System32\KERNEL32.DLL
Report Id: 9824de6a-1f2e-4a92-a9d8-573366d4da34
Faulting package full name:
Faulting package-relative application ID:

any ways to fix this?