1.7.10.0 and 1.7.11.0 Crashes On Load When Activating Packages

Bug Reporting Hub Resolved
, , ,
44

The CTDs continue when the simulator is loading / activating packages. The only difference is that when I delete all caches, the process continues, but before finishing the loading it crashes to desktop.

I have an AMD 5700X with a 6750 XT (12 GB). I am using Windows 11 fully updated and the latest AMD driver.

I have tried removing the Community folder and deleting the caches, but the problem still persists.

I had to leave the beta again, just like with the previous build. I also reinstalled the driver after cleaning everything with AMD Cleanup Utility, but the problem still persists.

I am currently using driver version 26.2.2, which worked without any issues before. In addition, everything works perfectly in SU4 and also in SU5 build 1.7.9.0. The problem only appears in the newer SU5 builds.

After leaving the beta and returning to SU4 everything works perfectly again.

I have also tested older driver versions, but the problem remains the same.

The crash log it generates is the following:

/!/ CRASH /!/TOML

[OnCrash]
Msg=“_handleSEH”
Type=“SEH”
Code=0xC0000005

[Platform]
CmdLine=

[Engine]
ReportVersion=10
ExitApp=false
PlayerSessionID=“56ACB62F-DB6C-4984-9A3B-574D4F81AEFE”
TimeUTC=2026-03-16T20:39:41Z
BuildVersion=“1.7.11.0”
UnscaledDeltaTimeMs=1.698799
TimeSpentRunningMs=36211.469255
TimeSpentPauseOffMs=34377.931576
TimeSpentTurnedOnMs=34377.931576
ContextUID=0x6D7000CC411D5C9B
MemInfoUID=0x1EF62E4C57C16FAD
DebuggerAllowed=false
AllocatedMem=4764565504
BucketMemUsed=2208
BucketMemCommit=131072
BucketMemBudget=6442450944
FrameCount=909
IsMSIXVC=true
Purpose=“GUI::CVpRootInGameData”

[AsynchCheckHandles]
Status=“Idle”
EndedXFramesAgo=910
Duration=0
Restarts=0
FreedHandles=6
SafeShutFailedCount=0
CreatedHandlesDuringACH=0
CreatedHandlesSinceEnded=818

[Hardware]
Platform=“PC”
Cpu=“AuthenticAMD”
Brand=“AMD Ryzen 7 5700X 8-Core Processor”
DriverVersion=“26.2.2”
GPUName=“AMD Radeon RX 6750 XT”
HWS_Enabled=0

[Fibers]
Cancelled=false
NumCreated_TOTAL=256
NumExternalCreated=0
NumConverted=30
NumExternalConverted=0
NumCreatedFiberMgr=256

[Renderer]
EnableD3D12=true
Model=“AMDGPU”
VR_State=“Inactive”
VideoMemoryBudget=12031590400
TexturesToDeleteCount=0
TexturesToDeleteTotalSize=0
ActiveRenderSystem=0

[Renderer_Textures]
Format=“datasize,x,y,z,n,mips,fmt,minmipcommitted,purpose,crc”
0=[33177600,3840,2160,1,1,0,“BM_B8G8R8A8_UNORM”,0,“GUI::CVpRootInGameData”,“”]
1=[16588800,1920,1080,1,1,0,“BM_D32_FLOAT_S8X24_UINT”,0,“[dont care]”,“”]
2=[16588800,1920,1080,1,1,0,“BM_D32_FLOAT_S8X24_UINT”,0,“D3D12Renderer_Z”,“”]
3=[8355840,1920,1088,1,1,0,“BM_R8G8B8A8_UNORM”,0,“CoherentGT_Backend_Z”,“”]
4=[8294400,1920,1080,1,1,0,“BM_R8G8B8A8_UNORM”,0,“CoherentGTImpl_Z”,“”]
5=[8294400,1920,1080,1,1,0,“BM_R8G8B8A8_UNORM”,0,“[dont care]”,“”]
6=[8294400,1920,1080,1,1,0,“BM_R8G8B8A8_UNORM”,0,“[default purpose]”,“”]
7=[8294400,1920,1080,1,1,0,“BM_R8G8B8A8_UNORM”,0,“[default purpose]”,“”]
8=[4194304,4194304,1,1,1,0,“BM_R8_UNORM”,-1,“PrimitiveBufferPool”,“”]
9=[4194304,4194304,1,1,1,0,“BM_R8_UNORM”,-1,“PrimitiveBufferPool”,“”]
10=[4194304,4194304,1,1,1,0,“BM_R8_UNORM”,-1,“PrimitiveBufferPool”,“”]
11=[4194304,1024,1024,1,1,0,“BM_D24_UNORM_S8_UINT”,0,“CoherentGT_Backend_Z”,“”]
12=[4194304,4194304,1,1,1,0,“BM_R8_UNORM”,-1,“PrimitiveBufferPool”,“”]
13=[4194304,4194304,1,1,1,0,“BM_R8_UNORM”,-1,“PrimitiveBufferPool”,“”]
14=[4194304,4194304,1,1,1,0,“BM_R8_UNORM”,-1,“PrimitiveBufferPool”,“”]
15=[4194304,4194304,1,1,1,0,“BM_R8_UNORM”,-1,“PrimitiveBufferPool”,“”]

[Wasm_Modules]
Format=“Handle,DebugName,PackageName,MemorySize,Status,DirtyFrame,DirtyErrorCode,DirtyJob,CurrentStep,LastStateUpdate”

[RawCallstackWin64]
0=[“amdxc64.pdb”,“DAA2677358DFA545918A59817C12CE81”,1,11172672]
1=[“amdxc64.pdb”,“DAA2677358DFA545918A59817C12CE81”,1,11167933]
2=[“amdxc64.pdb”,“DAA2677358DFA545918A59817C12CE81”,1,11163104]
3=[“amdxc64.pdb”,“DAA2677358DFA545918A59817C12CE81”,1,10990378]
4=[“amdxc64.pdb”,“DAA2677358DFA545918A59817C12CE81”,1,11082716]
5=[“amdxc64.pdb”,“DAA2677358DFA545918A59817C12CE81”,1,11043207]
6=[“amdxc64.pdb”,“DAA2677358DFA545918A59817C12CE81”,1,11039887]
7=[“amdxc64.pdb”,“DAA2677358DFA545918A59817C12CE81”,1,11039228]
8=[“amdxc64.pdb”,“DAA2677358DFA545918A59817C12CE81”,1,11035996]
9=[“amdxc64.pdb”,“DAA2677358DFA545918A59817C12CE81”,1,10993828]
10=[“amdxc64.pdb”,“DAA2677358DFA545918A59817C12CE81”,1,5973439]
11=[“amdxc64.pdb”,“DAA2677358DFA545918A59817C12CE81”,1,6090194]
12=[“amdxc64.pdb”,“DAA2677358DFA545918A59817C12CE81”,1,5998158]
13=[“amdxc64.pdb”,“DAA2677358DFA545918A59817C12CE81”,1,5308322]
14=[“amdxc64.pdb”,“DAA2677358DFA545918A59817C12CE81”,1,5394733]
15=[“amdxc64.pdb”,“DAA2677358DFA545918A59817C12CE81”,1,5425757]
16=[“amdxc64.pdb”,“DAA2677358DFA545918A59817C12CE81”,1,5327773]
17=[“amdxc64.pdb”,“DAA2677358DFA545918A59817C12CE81”,1,5339650]
18=[“amdxc64.pdb”,“DAA2677358DFA545918A59817C12CE81”,1,5630364]
19=[“amdxc64.pdb”,“DAA2677358DFA545918A59817C12CE81”,1,5630297]
20=[“amdxc64.pdb”,“DAA2677358DFA545918A59817C12CE81”,1,5625281]
21=[“amdxc64.pdb”,“DAA2677358DFA545918A59817C12CE81”,1,5312317]
22=[“amdxc64.pdb”,“DAA2677358DFA545918A59817C12CE81”,1,1840562]
23=[“amdxc64.pdb”,“DAA2677358DFA545918A59817C12CE81”,1,1839260]
24=[“amdxc64.pdb”,“DAA2677358DFA545918A59817C12CE81”,1,1829901]
25=[“amdxc64.pdb”,“DAA2677358DFA545918A59817C12CE81”,1,1525071]
26=[“d3d12core.pdb”,“E7A2E403F5D6E55DB96152EA21FE728D”,1,384481]
27=[“d3d12core.pdb”,“E7A2E403F5D6E55DB96152EA21FE728D”,1,383663]
28=[“d3d12core.pdb”,“E7A2E403F5D6E55DB96152EA21FE728D”,1,341774]
29=[“d3d12core.pdb”,“E7A2E403F5D6E55DB96152EA21FE728D”,1,340920]
30=[“d3d12core.pdb”,“E7A2E403F5D6E55DB96152EA21FE728D”,1,510889]
31=[“d3d12core.pdb”,“E7A2E403F5D6E55DB96152EA21FE728D”,1,333227]

CTD during startup (BOOT_PRESSSTART) – Exception 0xC0000005 – amdxc64.pdb

Problem Description
The simulator suffers a Crash to Desktop (CTD) during the initial loading screen, specifically during the “Press Start” phase. The crash occurs approximately 34–36 seconds after launching the application.

Crash Log Technical Details
• Exception Code: 0xC0000005 (Access Violation).
• Faulting Module: amdxc64.pdb (AMD Graphics Driver).
• Simulator State: MainState:BOOT SubState:BOOT_PRESSSTART.
• Build Version: 1.7.11.0.
• Failure Purpose: GUI::CVpRootInGameData.

System Specifications
• CPU: AMD Ryzen 7 5700X 8-Core Processor.
• GPU: AMD Radeon RX 6750 XT.
• Driver Version: 26.2.2.
• RAM: 32 GB (Total System Memory: 34,278 MB).
• OS: Windows 11 (IsMSIXVC: true).
• Graphics API: DirectX 12 Enabled.

Hardware & Rendering Context
• Video Memory Budget: 12,031 MB.
• HWS (Hardware Scheduling): Disabled (HWS_Enabled=0).

The raw callstack indicates the error is triggered within the AMD driver’s core execution while the sim is initializing the UI root data. This suggests a memory access conflict between the DX12 renderer and the specific driver version being used.

45

I’m wondering why this issue hasn’t been bug-logged yet. It seems relatively easy to trigger a CTD. Although there might be a problem if the devs don’t have these graphics card models. I’m also curious about something else, specifically the date of this topic.

image

March 10, and on that day the Windows update KB5079473 was also released, which I uninstalled because it caused quite a mess in my system. I uninstalled it and paused updates for 4 weeks. It would be good if someone checked whether the CTD still occurs after uninstalling that update.

46

Makes no difference, 1.7.11.0 CTD with my AMD RX6600

47

I hope the devs are taking this seriously. It’s not a bug, it’s a game stopper. Unable to run the sim! 1.7.9.0 was fine, 1.7.10.0 CTD.

Chewwy94 48

Hi all,

Could those of you who are experiencing this with 6000 series AMD GPU’s give details on your exact reproduction steps, just so that I can make sure to pass this forward to our Testing Team?

Thanks
The MSFS Team

1 Like
49

It’s reproduced by installing the beta and starting up the sim. Immediate CTD.

Resetting the shader cache helps so far that the sim at least starts up, but certain CTD after a few minutes. Then you’re back to immediate CTD when restarting again, until shader cache is reset again. So unable to run sim any way.

If you need any log file we will provide. Also details stated above.

50

Ryzen 5700X, RADEON RX 6800XT, 32Gb RAM DDR4 3200, WIN 11 latest upd, Adrenalin latest upd.

1.7.9.0 was super, but 1.7.10.0 CTD at this moment: “2% - activating Packages”.

51

system in the profile. somewhat same issue with a 6900XT

52

reproduces by just running latest beta 1.07.10.0 on AMD 6900XT driver 26.2.2 it would go to CDT right after login : Steam version , after the Xbox Login : CDT , go back to live , and it work like a charm , go back again to 1.7.10.0 CDT after login : BUT sometime after a fresh install it would le me go ready to fly and THEN CDT

53

After downloading the latest Beta 1.7.11.0, I got to the main screen, freeflight, but then CTD. Second attempt got less far, but without the new dialog box, then CTD. Third attempt to load got to the new screen, clicked Continue, got to Activating Packages 15%, then CTD.

Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:
P1: 141
P2: ffffa406f8843010
P3: fffff8021d48a790
P4: 0
P5: ffffa4070bd78080
P6: 10_0_26200
P7: 0_0
P8: 256_1
P9:
P10:

Attached files:
\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20251117-1818.dmp
\?\C:\WINDOWS\SystemTemp\WER-426850984-0.sysdata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.4805ab87-ccfb-451b-8174-1a23e50152f5.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.47ffa88c-d633-43e6-ad5f-4862522602db.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.eca5b723-b924-4b68-805d-6309cb19152c.tmp.txt
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.8207da6d-7ddf-40f5-b5ae-469f0acbddb0.tmp.xml

These files may be available here:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_141_ad73a6c55bfdf211f631161e2a80d1935e826b6_00000000_32879259-8d8b-45a2-b4d2-73346e7cce96

Analysis symbol:
Rechecking for solution: 0
Report Id: 32879259-8d8b-45a2-b4d2-73346e7cce96
Report Status: 2051
Hashed bucket:
Cab Guid: 0

54

Like others, all had to do was start the sim and it would consistently CTD (see error below) while loading. Usually crashed just after 2% loading. 6900XT video card. I tried older drivers, empty community folder, safe-mode. Nothing worked other than to leave beta and go back to previous version.

aulting application name: FlightSimulator2024.exe, version: 1.7.10.0, time stamp: 0x00000000

Faulting module name: amdxc64.dll, version: 32.0.21043.1005, time stamp: 0x69961426

Exception code: 0xc0000005

Fault offset: 0x0000000000aa7b40

Faulting process id: 0x4E14

Faulting application start time: 0x1DCB435E40416A8

Faulting application path: C:\Program Files\WindowsApps\Microsoft.Limitless_1.7.10.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe

Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\u0198633.inf_amd64_f6ca42135bb94c90\B025777\amdxc64.dll

55

Since 1.7.10.0, same problem with RX6950XT.

56

And same issue here with RX 6800 XT GPU. CTD during startup with 1.7.10 and 1.7.11. With or without empty community folder.

As described, resetting shader cache might let you progress a little further on first launch attempt, but no flying possible at all.

AMD driver version is 26.2.2. CPU is AMD 7800X3D.

57

Most recent CTD:

Fault bucket 1646406388697747188, type 5
Event Name: MoAppCrash
Response: Not available
Cab Id: 0

Problem signature:
P1: Microsoft.Limitless_1.7.11.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.7.11.0
P4: 00000000
P5: amdxc64.dll
P6: 32.0.21043.1005
P7: 69961426
P8: c0000005
P9: 0000000000aa7b40
P10:

Attached files:
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.cebebd23-fbef-4889-87bb-bf7c5e8ef1f6.tmp.WERInternalMetadata.xml

These files may be available here:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Microsoft.Limitl_399c83fe85dc7f9d2d63dca44396ba88bfa4_f23e9498_fe8026f4-06f3-429c-9edc-5c58b12ab74d

Analysis symbol:
Rechecking for solution: 0
Report Id: 4d14aa93-a694-41a3-8454-774e9be7df22
Report Status: 268435456
Hashed bucket: 3e8e339e4b219b9476d935e332434ef4
Cab Guid: 0

58

Same behavior, RX6900XT here, on latest AMD Drivers, MSFS 1.7.11.0.

Log entries below:

Protokollname: Application
Quelle:        Windows Error Reporting
Datum:         20.03.2026 19:30:23
Ereignis-ID:   1001
Aufgabenkategorie:Keine
Ebene:         Informationen
Schlüsselwörter:
Benutzer:      UNIMATRIX129\soich
Computer:      Unimatrix129
Beschreibung:
Fehlerbucket 1608083650932084646, Typ 5
Ereignisname: MoAppCrash
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: Microsoft.Limitless_1.7.11.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.7.11.0
P4: 00000000
P5: amdxc64.dll
P6: 32.0.21043.5001
P7: 69a76dae
P8: c0000005
P9: 0000000000aa7dc0
P10:

Angefügte Dateien:
\?\C:\Users\soich\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\AsoboReport-Crash.txt
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.f640e6a7-96a3-47e1-95d6-3274df0ce7a8.tmp.dmp
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.78faa053-5ba1-4e69-a4a2-87fee1992f66.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.75768446-20e3-45be-8643-9b3b4509e479.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.511fa39c-1e1d-4ce3-abdb-f3eb798aecf0.tmp.txt
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.b905a9ba-163c-4c8b-9b44-230c8e06836d.tmp.xml

Diese Dateien befinden sich möglicherweise hier:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Microsoft.Limitl_12206b93d94319e876938246cc581687cdc5_f23e9498_4296f5b3-b266-436b-a6c5-2e4636d4f6fd

Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: a120b72c-0954-4697-872a-4ecaaa8fa5d6
Berichtstatus: 268435456
Bucket mit Hash: 60a1decf761fe10636510f8f7eeb8fa6
CAB-Datei-Guid: 0
Ereignis-XML:



1001
0
4
0
0
0x8000000000000000

43092


Application
Unimatrix129



1608083650932084646
5
MoAppCrash
Nicht verfügbar
0
Microsoft.Limitless_1.7.11.0_x64__8wekyb3d8bbwe
praid:App
1.7.11.0
00000000
amdxc64.dll
32.0.21043.5001
69a76dae
c0000005
0000000000aa7dc0



\?\C:\Users\soich\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\AsoboReport-Crash.txt
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.f640e6a7-96a3-47e1-95d6-3274df0ce7a8.tmp.dmp
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.78faa053-5ba1-4e69-a4a2-87fee1992f66.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.75768446-20e3-45be-8643-9b3b4509e479.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.511fa39c-1e1d-4ce3-abdb-f3eb798aecf0.tmp.txt
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.b905a9ba-163c-4c8b-9b44-230c8e06836d.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Microsoft.Limitl_12206b93d94319e876938246cc581687cdc5_f23e9498_4296f5b3-b266-436b-a6c5-2e4636d4f6fd


0
a120b72c-0954-4697-872a-4ecaaa8fa5d6
268435456
60a1decf761fe10636510f8f7eeb8fa6
0

Application Error Log:

Fehlerhafter Anwendungsname: FlightSimulator2024.exe, Version: 1.7.11.0, Zeitstempel: 0x00000000
Fehlerhafter Modulname: amdxc64.dll, Version: 32.0.21043.5001, Zeitstempel: 0x69a76dae
Ausnahmecode: 0xc0000005
Fehleroffset: 0x0000000000aa7dc0
Fehlerhafte Prozess-ID: 0x3E4C
Fehlerhafte Anwendungsstartzeit: 0x1DCB89779AA6105
Fehlerhafter Anwendungspfad: C:\Program Files\WindowsApps\Microsoft.Limitless_1.7.11.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe
Fehlerhafter Modulpfad: C:\WINDOWS\System32\DriverStore\FileRepository\u0198974.inf_amd64_dcac9659486b668a\B025819\amdxc64.dll
Berichts-ID: a120b72c-0954-4697-872a-4ecaaa8fa5d6
Vollständiger Name des fehlerhaften Pakets: Microsoft.Limitless_1.7.11.0_x64__8wekyb3d8bbwe
Fehlerhafte paketbezogene Anwendungs-ID: App

System config is 5800X3D/64 GB RAM/6900XT, Windows 11 w/ all current updates.

One additional detail: Got all the way to the menu on 1st start, now instant CTDs when loading the intro video.

If devs need anything else, let me know.

59

Same problem.
Completely removed all AMD driver, Adrelalin etc. Removed FS2024, reset to SU4

Installed AMD latest Adrenalin and FS2024 SU4

All worked beautifully. Updated to SU5, and bingo, crashed just after loading.

Faulting application name: FlightSimulator2024.exe, version: 1.7.11.0, time stamp: 0x00000000
Faulting module name: amdxc64.dll, version: 32.0.21043.5001, time stamp: 0x69a76dae
Exception code: 0xc0000005
Fault offset: 0x0000000000aa7dc0
Faulting process id: 0x328C
Faulting application start time: 0x1DCB966F07AC1C8
Faulting application path: C:\Program Files\WindowsApps\Microsoft.Limitless_1.7.11.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe
Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\u0198974.inf_amd64_dcac9659486b668a\B025819\amdxc64.dll
Report Id: 1e2983b6-89ea-4c0d-ad32-b8bf469e6576
Faulting package full name: Microsoft.Limitless_1.7.11.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Copilot again reports amd driver problem. Rhe driver is now a later version than when I first had the problem.

60

Can anyone point to a current link that explains where we should get our logs? It seems we’ re inconsistent and it would probably help the devs if we are consistent.

61

I have to say I’m a bit concerned that the Devs have not yet marked this as bug logged. It feels like what happens with the AMD 9000 night light artifacts but this one is more serious since the sim doesn’t work at all. If SU5 gets released, like back in May with SU2, without the issue being resolved they will end-up with a lot of very unhappy AMD 6000 users.

BTW… for you users who have this issue I would recommend you also send bug reports to AMD as well.

62

Yes, I’m surprised this has not yet been acknowledged as “Bug-Logged”. I had followed the AMD 9000 night light issue too, so I know what you’re talking about. I agree that if SU5 is released without a fix, there will be many unhappy users. I’d like to be flying under 2024 but have gone back to 2020 for the time being.

Bug reports should start going to AMD as well, yes.

63

Has anyone using an AMD 6000 thought about going back to pre-AMD 9000 drivers? I’m thinking version 24.12.1 from Dec. ‘24 just to see if that would make a difference.