may be the lib is already unloaded and a part of msfs wants to use it ( or may be a mod )… but, really a big guess 
Yup! That’s what I meant…stop adding features and modifying further, till the basic aspect of flying is corrected. We all would appreciate an un-interrupted launch / flight 
for sure, but you must use minimum voltages, what keep pc stable, especially io and sa, but for cpu too, and it’s not only about overclocking it’s about factory overclocking xmp for memory and turbo frequency for cpu, because you will have overheat your system and have other way instability… bios set very big overvolt for cpu, sa and io voltages(if xmp is on), and you have to reduce them, have to change cpu voltage, and must to change sa and io voltages those two values not about only overheat they about memory controller rail, one of them in any way, and if you have overvolt it too long, you can destroy your system physically
1 Like
XMP is no overclocking though. XMP is a “method” of using the speed settings the RAM is certified for and on newer Ryzen Processors 3200 MHz is considered to be stable. But you are right about the voltages, I have to set it manually to 1.35V or the “standard” voltage of 1.2V would be applied. This would result in an unstable system in general though and not just cause CTD with FS.
yes, people calls it overclock, but it’s not, may be problem start when use 4 sticks, i didn’t check voltage with 2 sticks, when i ordered my pc, i go in web and found 4 sticks double channels faster than 2 sticks, with same freq/latency, so i ordered 4 optimal i found in 2018 it was 3600 15 15 15 35, any way after 3 years use sa io auto voltage i catch very big problem, and remember what i read about sa io and ignore it, now i don’t after had black screen without opportunity to start pc, so all i wrote it’s about my own experience + what i read long time before in the web
p.s. 1.35 is overkill, in any way, i don’t remember what i use right now, but about 1.2, i start from minimum what stay white in bios, and up step by step, you can found info in the internet… and xmp use same way for amd and intel is no matter
Show me anything from Ryzen saying xmp isn’t overclocking? … You won’t find it and that’s why you get the opportunity to turn it off as any debugging app will tell you to do for the purpose. There are no rules governing what does or doesn’t work with xmp and only once you have a stable sim is it time to experiment with it’s use. You certainly can’t discount it.
Please stop this discussion about memory here, it’s leading nowhere. Again: If your system settings regarding RAM are unstable there would be at least one other game or app except FS that would have a problem with it. If your PC e.g. is Prime95 stable in memory torture tests you can be pretty certain that memory settings are not the cause of FS crashes.
Also https://www.amd.com/en/products/ryzen-compatible-memory states that my memory G.Skill Flare X for AMD is compatible in its XMP profile configuration and nowhere does it state that it is considered unsupported overclocking. Also the motherboard vendors compatbility list states this memory as compatible in 2 and 4 DIMM configurations. It doesn’t matter if I have JEDEC timings or XMP timings activated or if I use 2 or 4 of the DIMMs. The CTDs with FS stay the same, general system stability stays the same.
I am really … by people who can’t see how … the development of this game is and then accuse users of configuring their PC wrong. I can’t repeat it often enough: I am using WHQL certified drivers, Windows 10 certified hardware in supported, compatible configurations and get a perfect system stability from Windows itself (no system crash since I have Windows 10) and no CTDs from dozens of other games and no issues with apps. FS is the ONLY software with repeated and constant CTDs so I am more than certain it’s a software issue with FS and not my inability to read compatibility lists to choose the right hardware combination.
Also suggestions like have you checked the Logitech software show me how people just make blind suggestions. I already stated that the CTD issues are present on a CLEAN system, i.e. with only Steam and FS and nothing else except the out-of-the-box Windows software installed.
5 Likes
All I’m saying is Microsoft have changed the way memory syncs in the sim, it may even be a unique solution and as yet may not support all xmp profiles… And Microsoft can usually do what they like, it is always the rest that have to conform.
1 Like
In windows search bar type system information.
Launch system information app.
Attach system information report from system information app.
How to
https://nvidia.custhelp.com/app/answers/detail/a_id/2507/~/how-to-generate-a-microsoft-system-information-report-%28msinfo32%29
In windows search bar type dxdiag.
Launch directx diagnostic tool.
Create a dxdiag report.
Attach dxdiag report file.
How to
https://support.microsoft.com/en-us/windows/open-and-run-dxdiag-exe-dad7792c-2ad5-f6cd-5a37-bf92228dfd85
not again this discussion. it is overclocking, with a promise of manufactors that the memory should works fine in specific condititions.. CTD Help, Possibly - XMP II - Overclock - #8 by MichaMMA
But again.. this is not the topic here… we gave you hints which can you try or not. If it to hard for you to simple switch for a test-case to normal JEDEC frequencies, then not ask for hints 
i now no fly much, replay fps games, but all my ctd for now in the same time, when i had mouse conflict with ministick mouse on my right throttle(cursor moves itself) i had this problem from may be first month i use my joystick, and this trouble can appear and stay minutes - days, or disappear at months, whatever it is after all last ctds i have cursor moves by itself, then ok, second stuff i found, and not only me, i read about this on this forum, at first versions of msfs we got freeze after remove something from usb or change it like start charging mouse and so change usb port and type of unit, and in one of versions that’s was fixed, sim found those change and told us - hey, i found new device, would you change settings, or stay default… or something like that with normal english of course, but now, after update we get back to the past and have same problem if try to recalibrate joy by reconnect it, or start charging mouse, or whatever happens in the usb world… so i think we just have now new-old causes for ctd freeze etc.
In an odd coincidence, I upgraded to Windows 11 and for some reason seem to be getting more descriptive error logs in Event Manager. This is what I got last night:
If you Google RADAR_PRE_LEAK_64, you’ll find it’s a mechanism in Windows to catch memory leaks in applications.
To me at least, we don’t have memory hardware issues, there’s a real memory leak of some kind.
2 Likes
and may be you find also such kind of analyses from MS , just for a different tool:
e.g.
This doesn’t appear to be an actual indication of a memory leak. It’s likely that the heavy allocation workload, along with bulk freeing, is firing a heuristic erroneously.
1 Like
Great find! I didn’t catch that. Thank you! This seems to be the only message I get now at time of crash. Not sure where else to look now, since this message appears to be 50/50 if it’s real or erroneous.
I thought this are only warnings… ? This RADAR tool send the data to the ms telemetry servers.
But, it is windows 11 beta and we can not realy compare with windows 10 whats happens in background.
Windows 11 is GA now as of 10/5. But I do hope that the telemetry is sent and something can be done to help troubleshoot and solve the issue.
2 Likes
As @sttovo stated Windows 11 is GA and should have the same stability Windows 10 had. Also since the CTD issues on a fresh Windows 10 and Windows 11 installation are exactly and reproducably the same, I highly doubt there is a new issue with Windows 11 so I am personally fine by testing on the “current” OS.
Btw … a reason why the developers don’t believe us that the game is broken might be that the CTD issues DO NOT occur when you activate developer mode in the game. However this disables all achievements and game progress in your profile and also some other things don’t work ready for production use.
1 Like
as long as there is not an official statement from MSFS developers about windows 11, I assume it is not confirmed compatible ( but yes, I also assume it should works )
as mentioned: you understood the posts in that community forum in a wrong way. We are not the developers and we not know what they might think. We are here a community to find/discuss possible solutions, workarounds, etc.. and this can again help the developers to find/and fix quicker possible existing issues. It just sounds for me like that you entered into the community with a pre-defined opinion " the game have a bug “. We instead say " may be there is a bug in game , but we also know there are many other reasons possible.. let us discuss..”.
thats a realy intressting information !
May be other affected users can re-check that ( @sttovo ? ).
I never use the developer mode, in former releases it caused itself issues, and have still have no single CTD.
The developer mode in itself causes all sorts of issues e.g. with autopilot functionality, but it stops the CTDs. I was hoping to get a better error message with developer mode on but it seems to disable the game functionality that causes the CTDs.
1 Like
Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: d3d11.dll, version: 10.0.19041.1202, time stamp: 0x899ced78
Exception code: 0xc0000005
Fault offset: 0x00000000000e754e
Faulting process id: 0x2ca8
Faulting application start time: 0x01d7bb720f7c2e21
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.19.9.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Windows\SYSTEM32\d3d11.dll
Report Id: f75450c5-0fec-439e-98de-b98ffbe345c9
Faulting package full name: Microsoft.FlightSimulator_1.19.9.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: AppFaulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: d3d11.dll, version: 10.0.19041.1202, time stamp: 0x899ced78
Exception code: 0xc0000005
Fault offset: 0x00000000000e754e
Faulting process id: 0x2ca8
Faulting application start time: 0x01d7bb720f7c2e21
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.19.9.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Windows\SYSTEM32\d3d11.dll
Report Id: f75450c5-0fec-439e-98de-b98ffbe345c9
Faulting package full name: Microsoft.FlightSimulator_1.19.9.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
and as you can see nothing unusual except commit charge peak to 20gb before crash
