This again! ntdll

General Discussion & Community Support Tech Talk
,
1

Faulting application name: FlightSimulator.exe, version: 1.27.21.0, time stamp: 0x00000000
Faulting module name: ntdll.dll, version: 10.0.19041.2130, time stamp: 0xb5ced1c6
Exception code: 0xc0000005
Fault offset: 0x0000000000050804
Faulting process ID: 0x4728
Faulting application start time: 0x01d8e3490379ecc7
Faulting application path: Z:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report ID: af461d7c-aa99-4006-988f-7ca005820302
Faulting package full name:
Faulting package-relative application ID:

Just now starting a flight i do everyday, up to date and i always restart before a flight

ntdll :roll_eyes:

2

For those having any CTD issue/s try the following…

Run the following commands…

Go through each of the following steps one at a time. Copy each line, one at a time , paste it into the Dos window (crtl + V) and press return

and it will then run. Wait until each runs and finishes before you move on to the next one.

When you are completely finished, Restart your computer and then try to see in MS2020 will start and run properly

Dism.exe /online /Cleanup-Image /checkhealth

Dism.exe /online /Cleanup-Image /scanhealth

Dism.exe /online /Cleanup-Image /Restorehealth

sfc /scannow

Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore

Dism.exe /Online /Cleanup-Image /StartComponentCleanup

RESTART your computer as the last step. Then go for a test flight.

1 Like
3

Findings: Yes it worked again and I had in fact had updates I didn’t realize this week, I’m just surprised it raised it’s head again and having to repeat the process, I can live with maybe following this procedure on a monthly basis, but I can’t imagine this is something the average end user would want to do, I don’t put this on MSFS/Asobo at all I just find it stange this dll going rouge again (at least for me) after another update… but is what it is :man_shrugging:

4

I suspect that MS has an issue when providing update/s to ones system. In effect corrupting ones install (only takes 1 file).

1 Like
5

Just ran them all thru my system all passed with exception of the sfc /scannow which found corruption. This was after updating to 22H2 19045.2130 from 21H2 19044.2130

1 Like