Crash to desktop without error message

I havent had a crash again after i did the page file thing.
Even on 16gb of ram…but my other 16gb comes in today.
Glad its not a lack of RAM issue…
Seems to be sensitive to particular system configs.

What was the page file thing? Manual or system managed? If manual, what did you set it to? Thanks

To check if it’s enabled, follow these steps:

On the start menu, search for SystemPropertiesAdvanced and press Enter . On the window that opens, click the Advanced tab, then under the Performance section, click the Settings button. Then, click on the Advanced tab and click Change button under the Virtual Memory section.

Imgur

Make sure System managed size is checked.

What did you set your pagefile to with 16GB RAM? I’ve got 16 as well and would like to know. Thanks.

Hi all, not sure if it will work for most people or not, but maybe worth a try…

I sent a request to Zendesk to query my constant CTD without any error messages, everything that has been experienced here. Several re-installs, deleting old sims off different drives to make more storage (despite having enough in the first place…) They initially replied with a standard auto response which was so frustrating, because I’d explained that I’d tried most of what they had now suggested. However, I did send my dxdiag and msinfo32 info.

They then replied saying that my issue was probably related to my sound driver/software. They suggested changing my sound output to my monitor. I unplugged my speakers and headset so the only sound device showing in windows settings/devices was my monitor.

I then re-installed MSFS and noticed things happening that had not happened previously. I then opened the sim and have now run it at different settings/scenarios/varying periods of time and have not had one crash (thankfully - don’t want to tempt fate!). Zendesk did advise, once it had been installed and tested, I should then be able to connect my speakers again, which I’ve now done and there is still (fingers crossed) no issues.

Definitely worth a try if you haven’t already.

Kind regards,

Mike

You aren’t putting in any values simply clicking automatic management by windows.
If your system is already set to this then…its not your problem.

yep, i di the same and got the same response … rock solid

Did they ask you to reinstall the sim? I’m willing to try to change my sound devices but would like to avoid a reinstall (as this seemed to be ok)

Edit: But your post gave me the idea to udate all board drivers (LAN, Sound,…) to lastest version as I was running with stock Windows drivers after reinstall of OS.

This at least didn’t help so I might try to use the Monitor Audio

I’m running ultra settings at 1440p

https://forums.flightsimulator.com/uploads/default/original/3X/2/2/2250528bc5149471ef06e19669e64165c7f95e0d.png

1 Like

I had uninstalled it whilst I awaited their second reponse, as I wanted to see what they suggetsed before re-installing it again, so I’m not too sure if it will work with it already installed, sorry!

I think it may be something to do with the sound/device connections upon he installation (as silly as it sounds) so may only work if done prior to and whilst installing, but definitely worth a try :slight_smile:

Being a Software developer myself, we usually need way more than 8 hours to do anything useful :slight_smile:

I tend to say: they had a few years!

Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x5f2ed221
Faulting module name: d3d11.dll, version: 10.0.19041.1, time stamp: 0x84d2d982
Exception code: 0xc0000005
Fault offset: 0x00000000001764a0
Faulting process id: 0x296c
Faulting application start time: 0x01d677b2a3e3a9c7
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.7.12.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\WINDOWS\SYSTEM32\d3d11.dll
Report Id: 87e5ad19-fc35-44c6-aacf-6ccec8d0271b
Faulting package full name: Microsoft.FlightSimulator_1.7.12.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

My game is crashing because of d3d11.dll. I was able to play it two days ago, but I can’t play it anymore.

Hi. I have a soundcard on the mobo but my primary use is 7.1 HyperX headphones with their own USB dac. Do I need to disable other sound options? And leave only the headphones. Or I should disconnect all ports line in / mic

OK I tried to use monitor only, deactivating my onboard soundcard.

Thought it would be better, allowing me now t least to get into main menu every time but just now it crashed while loading :frowning:
But as I said already: it’s their task to fix this, not ours and I’m not willing to spend hours in trying to fix their incompetence. Every other software/game in my machine works without problems so I’m not willing to take the blame on my setup.

Anyway: if sound is a potential issu it might be worth checking if we have something in common here

My onboard sound is a Realtek chipset

I tried the monitor only too. Same error. Disabled all audio devices via Device Manager too. :frowning:

Same issue, Xeon W3690, RTX2080 TI, 24GB, installed at separate SSD (F:). Cache in default folder on Drive C:. Windows10 Version 2004 is up to date. Using a Thrustmaster T-Flight Hotas X. The time to the crash is rondom from starting the app up to to 30min.
Runned the game at 4k down to 1080p and different detail setting but no difference. Even closing several background apps and kaspersky does not make a difference.

I can confirm that even not playing at all but just staying in the menus it also crashes to the desktop.

UPDATE: Same problem on my AMD Ryzen 3950X, 32 GB.

2 Likes

I was checking event viewer and before MFS error event most of the times i have this error:
Failed with 0x57 retrieving AppModel Runtime status for package Windows.
Event ID:65
and from a fast re-search this had to do with windows 10 - GPU driver

Oh my god… If I could kiss you, I would. This very solution helped me pass the CTD that happened every time in the middle of the initial load. I had tried EVERY solution suggested here, including driver updated/reinstalls, repairing Windows, redownloading all 90gb 4 times, page files, unplugging peripherals, etc. This worked!!!

Mine was crashing with D3D11.dll, too. Try EndOfStory3817’s suggestion. It worked for me