xbox controller seems never ending story ( similar to usb unplug, or bluetooth )… may be the newest topic around is: CTD - Wireless Xbox Controller disconnect
Interessting might be… which messages is logged in event viewer in this case ?
I had this issue with Windows 10 Insider and new OS releases (for many months) didn’t help it work. Sent a Zendesk and after some back and forth, they came back with the below remedy.
This is currently the only way I can run MSFS on Win10 Insider:
(if this works, you can make a shortcut with the “cmd.exe …” action and leave it on the desktop)
**STUCK ON A BLACK SCREEN AFTER HITTING PLAY**
If you are stuck on a black screen after clicking **Play** or **Launch**, skip the intro.
1. Close Microsoft Flight Simulator
2. In the Windows search bar type Powershell
3. Select Run as administrator
4. In the pop-up window that appears, copy-paste the following command:
cmd.exe /C start shell:AppsFolder\Microsoft.FlightSimulator_8wekyb3d8bbwe!App -FastLaunch
5. If prompted, authorize the program to run.Thanks for this, but unfortunately it has made no difference in my case as still black screen for a few seconds and then disappears with no start up
Thanks for the response in any case.
welcome
yeah, so many different “problems” makes it hard to give good advice. My MSFS would just start, a few spins in the bottom right, and just sit in a blank window “forever”. Then the ‘cmd’ helped skip the intro part and it’s worked ever since. Hopefully things can be solved to get it more reliable!
Hi.
Today i had my first screen freeze during a flight from EGGP to EGLC with TBM930
I did the flight twice and the game freeze always on the same place.
ODVOD intersection during STAR procedure to EGLC.
Then i can’t close the game as it is all freeze.
Is anyone experience this isssue too ?
Thanks.
please check windows event log for a “grammar.pggmod” message. In case you find such a message, please report issue here : 100% reproducible CTD at specific coordinates for months [grammar.pggmod]
( and of course in ZenDesk )
1 Like
My event log say something about mobex.dll fault.
Do you have any knowledge on this one ?
can you show us the message ?.. quickly I found only somewhat about Samsung application ( have you installed the S…studio , may be also LG ? ) … or do you mean a MoBEX Event ?
mobex event.
I only have ASUS XONAR AE on my ASUS pc.
never instaled other one.
I did a clean with Amswsoft PC Optimizer to clean junk files.
And the windows viewer report were erased too. Sorry not be able to provide the windows event log.
I’m about to start the flight again and see what happen this time.
If i have another CTD i’ll come back and show you the windows event report.
Thanks
1 Like
yep… this is only event type , not a dll 
Let us know whether you can re-create the CTD at the same coords.
Hi
I won’t be able to reproduce the CTD as i just pass on the coords point and i went trough.
Sort out this one.
Now need to check other coords where i have CTD too.
The CTD i was having is at ODVOD intersection north EGMA airport in England.
The other one i have is at HIJ VOR in Spain when i do the flight LEMD to SAEZ on the B787-10
A lot of the cleaning files done by Amswsoft PC Optimizer where on appdata\Local\Temp folder.
Oh well.
I can’t even start MSFS anymore without getting a CTD just before the main menu. This has happened before (it has started with Sim Update 4), has worsened over time (CTD every 2nd time I open the game), but since a few days it has become impossible to even start the game.
Of course, no error message, no logs, only the cryptic Windows event log because why giving your customers a clue about what’s happening, right?
Needless to say, nothing changed on my PC since these problems started to happen and then worsen, and all other games still run just fine.
I think I’ll give up at this point and hope they fix their product at some point. Just like back in October, when clouds started flickering, and they didn’t fix it until December.
I’m just super glad I didn’t invest any more money into this apart from the initial shelf price. I’ll update my product review accordingly. Good luck to everyone else.
3 Likes
… it would be very unfortunate for you if you continue to use this game against your will …
@Gsx31 I wanted to invest in the CRJ But since having these problems there’s no point in purchasing anything else for MSFS
1 Like
I will send you a private message
1 Like
show us the message 
Are this still your PC specs ?
I would be shocked to see this rig launch MSFS back in August. I had very similar spec on release and couldn’t get it it fire up. I had already ordered new hardware at the time but wanted to see if I could maybe pass the old system to my son so he could run MSFS, even dialed back. NOPE.
That GPU exceeds the minimum but does not quite the recommended. I remember some arguments about how the required spec has shifted upwards during development. I would imagine this will continue as DX12 comes in, and new effects are added by developers.
The GPU is borderline yes, but that 6700 plugs into the 100 series MB. It isn’t always about CPU/GPU. Sometimes its about the pipes in between.
1 Like
Version=1
EventType=MoAppCrash
EventTime=132682468739462833
ReportType=2
Consent=1
UploadTime=132682468812599471
ReportStatus=268435462
ReportIdentifier=f180b0f1-021f-4513-a949-f51db17cd61a
IntegratorReportIdentifier=638c140a-85c4-4f26-92d8-16f791918c87
Wow64Host=34404
NsAppName=praid:App
AppSessionGuid=00002bf0-0002-013b-672f-cc4ff961d701
TargetAppId=U:Microsoft.FlightSimulator_1.16.2.0_x64__8wekyb3d8bbwe!App
TargetAppVer=1.16.2.0_x64_!2021//05//19:14:34:31!0!FlightSimulator.exe
BootId=4294967295
TargetAsId=2053
UserImpactVector=269497136
IsFatal=1
EtwNonCollectReason=1
Response.BucketId=07ef316c8e83cb0144b901610641d187
Response.BucketTable=5
Response.LegacyBucketId=1493226267678462343
Response.type=4
Sig[0].Name=Nome completo pacchetto
Sig[0].Value=Microsoft.FlightSimulator_1.16.2.0_x64__8wekyb3d8bbwe
Sig[1].Name=Nome applicazione
Sig[1].Value=praid:App
Sig[2].Name=Versione applicazione
Sig[2].Value=0.0.0.0
Sig[3].Name=Timestamp applicazione
Sig[3].Value=60a521f7
Sig[4].Name=Nome modulo con errori
Sig[4].Value=xgameruntime.dll
Sig[5].Name=Versione modulo con errori
Sig[5].Value=10.0.19041.7547
Sig[6].Name=Timestamp modulo con errori
Sig[6].Value=3342cc8a
Sig[7].Name=Codice eccezione
Sig[7].Value=c0000005
Sig[8].Name=Offset eccezione
Sig[8].Value=00000000000652fb
DynamicSig[1].Name=Versione SO
DynamicSig[1].Value=10.0.19043.2.0.0.256.48
DynamicSig[2].Name=ID impostazioni locali
DynamicSig[2].Value=1040
DynamicSig[22].Name=Informazioni aggiuntive 1
DynamicSig[22].Value=85de
DynamicSig[23].Name=Ulteriori informazioni 2
DynamicSig[23].Value=85de6de0f85ec6108091f6fd860f4f51
DynamicSig[24].Name=Ulteriori informazioni 3
DynamicSig[24].Value=4772
DynamicSig[25].Name=Ulteriori informazioni 4
DynamicSig[25].Value=4772db3a76ed304ebe70287960b226e5
UI[2]=C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.16.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
System Information
Time of this report: 6/15/2021, 21:36:06
Machine name: MIG
Machine Id: {9DAF5CD7-006A-45CE-B6A1-6EF753CAB44C}
Operating System: Windows 10 Pro 64-bit (10.0, Build 19043) (19041.vb_release.191206-1406)
Language: Italian (Regional Setting: Italian)
System Manufacturer: ASUS
System Model: System Product Name
BIOS: BIOS Date: 11/02/20 17:00:46 Ver: 05.00011 (type: BIOS)
Processor: Intel(R) Core(TM) i7-10700K CPU @ 3.80GHz (16 CPUs), ~3.8GHz
Memory: 32768MB RAM
Available OS Memory: 32668MB RAM
Page File: 6205MB used, 33885MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 12
DX Setup Parameters: Not found
User DPI Setting: 168 DPI (175 percent)
System DPI Setting: 144 DPI (150 percent)
DWM DPI Scaling: Disabled
Miracast: Available, no HDCP
Microsoft Graphics Hybrid: Not Supported
DirectX Database Version: 1.0.8
DxDiag Version: 10.00.19041.0928 64bit Unicode
Display Devices
Card name: NVIDIA GeForce GTX 1080
Manufacturer: NVIDIA
Chip type: NVIDIA GeForce GTX 1080
DAC type: Integrated RAMDAC
Device Type: Full Device (POST)
Device Key: Enum\PCI\VEN_10DE&DEV_1B80&SUBSYS_37171458&REV_A1
Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER]
Device Problem Code: No Problem
Driver Problem Code: Unknown
Display Memory: 24412 MB
Dedicated Memory: 8079 MB
Shared Memory: 16333 MB
Current Mode: 3840 x 2160 (32 bit) (60Hz)
HDR Support: Not Supported
Display Topology: Extend
Display Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709
Color Primaries: Red(0.633789,0.340820), Green(0.311523,0.635742), Blue(0.158203,0.061523), White Point(0.312500,0.329102)
Display Luminance: Min Luminance = 0.500000, Max Luminance = 270.000000, MaxFullFrameLuminance = 270.000000
Monitor Name: Generic PnP Monitor
Monitor Model: U28E590
Monitor Id: SAM0C4D
Native Mode: 3840 x 2160(p) (59.997Hz)
Output Type: Displayport External
Monitor Capabilities: HDR Not Supported
Display Pixel Format: DISPLAYCONFIG_PIXELFORMAT_32BPP
Advanced Color: Not Supported
Driver Name: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_a494df49ba2f9f36\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_a494df49ba2f9f36\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_a494df49ba2f9f36\nvldumdx.dll,C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_a494df49ba2f9f36\nvldumdx.dll
Driver File Version: 27.21.0014.6627 (English)
Driver Version: 27.21.14.6627
DDI Version: 12
Feature Levels: 12_1,12_0,11_1,11_0,10_1,10_0,9_3,9_2,9_1
Driver Model: WDDM 2.7
Hardware Scheduling: Supported:True Enabled:True
Graphics Preemption: Pixel
Compute Preemption: Dispatch
Miracast: Not Supported by Graphics driver
Detachable GPU: No
Hybrid Graphics GPU: Not Supported
Power P-states: Not Supported
Virtualization: Paravirtualization
Block List: No Blocks
Catalog Attributes: Universal:False Declarative:True
Driver Attributes: Final Retail
Driver Date/Size: 23/04/2021 02:00:00, 1050080 bytes