August 21, 20223 yr Too many CTDs for me as well, mainly occurring short on final. I’ve actually stopped playing pending SU10 for this reason.
August 21, 20223 yr I suspect some server side issue. Probably something faulty in the live weather. I've had multiple crashes within the first 20 minutes of a flight since yesterday. It won't get fixed by MS on the weekend though. We'll just have to sit this one out.
August 21, 20223 yr Now i think i can forget flying, yesterday i set up a flight for the 787-10 was about a 3h flight, shortly before TOD the Sim CTD`s to desktop with no error message and i can`t find any within the event viewer.. Today i set up the same flight just to see what happens - the same tragedy as yesterday the only thing that was different, it happened after about 40 minutes, same exact thing with no error nothing in the event viewer ! So seems thats it , i did some tests before and all that seems to be OK, all other stuff i am doeing with my PC are with no probs at all - so what is this, a server issue ?? Maybe the server data is optimised for SU10 and i am still on SU9 and as far as i know both Versions use the same servers so this could be a data conflict with each other, maybe good for SU10 but not for SU9 ?? cheers 🤔 08.2024 new PC is online : ASUS ROG STRIX X670E-F GAMING WIFI Mainboard, AMD Ryzen™ 9 7950X3D Prozessor, G.Skill DIMM 64 GB DDR5-6000 (2x 32 GB) Dual-Kit, MSI GeForce RTX 4090 VENTUS 3X E 24G OC Grafikkarte, 2x WD Black SN850X NVMe SSD 4 TB - Drive C+D, WD Gold Enterprise Class 12 TB for storage HDD, Thermaltake Toughpower GF3 1000W PC - Power supply, Thermalright Phantom Spirit 120 EVO CPU Aircooler with 7 Heatpipes, Design Meshify 2 White TG Clear Tint Tower-Case, 3x 4K monitors 2x32 Samsung 1x27 LG 3840x2160, Windows11 Prof. 23H2 - now Windows11 Prof. 25H2 Flightsimulator Hardware: Honeycomb Throttle Bravo, Logitech Extreme 3D Pro, Logitech Flight Joke System, XBox Controller, some Thrustmaster stuff, Winwing CDU Panels.
August 21, 20223 yr What people should really take away from this incident here is that server side issues can cause CTDs. That's new on any flight simulator and it's the first time in flight sim history that users might not be able to influence the CTD-probability of their sim (by clearing conflicts, lowering settings, deleting faulty mods etc.). Unfortunately this makes looking for CTD causes a potential nightmare in certain cases. For transparency: I'm a community mentor at the BATC discord. However, I do not get paid for it in any way.
August 21, 20223 yr Same here. Since yesterday it is no longer possible to complete a stage of my world trip with the H145. Not good. 👎 My round the world with the H145.
August 21, 20223 yr 24 minutes ago, Farlis said: I suspect some server side issue. Probably something faulty in the live weather. I've had multiple crashes within the first 20 minutes of a flight since yesterday. It won't get fixed by MS on the weekend though. We'll just have to sit this one out. My suspicion as well. I had 3 crashes yesterday (ntdll.dll) at various points during a short flight (TDPD - TAPA) - NO GSX!! Just did the flight successfully, but turned ONLINE CONNECTIVITY to OFF, hence no Live WX, no BING streaming. I'll try it once more with only Live WX turned off, we'll see. Cheers, Søren DissingIntel i9-13900K @5.6-5.8 Ghz | ASUS ROG RYUJIN III | ASUS ROG Astral RTX 5090 OC | ASUS ROG Maximus Z790 Hero | 64Gb DDR5 @5600 | 1Tb Samsung M.2 980 PRO (Win11), 1Tb Samsung M.2 980 PRO, | ASUS ROG Helios 601 | 32” ASUS PG32UCDM 240hz 4K | Chaseplane | TM TCA Captain's Edition, Winwing FCU + EFIS L/R, Tobii 5 | Win 11 Pro 64 | MSFS 2024 | BA Virtual | PSXT, RealTraffic w/ AIG models
August 21, 20223 yr 13 hours ago, udidwht said: You can run the Command Prompt as administrator and run the command below to reinstall the .dll file. First unload the .dll file: regsvr32.exe /u ntdll.dll Then reinstall the .dll file: regsvr32.exe ntdll.dll I initially tried that as a first step but Win 11 said it could not find the file or some such message, other people saw the same issue. As an update to where I am now: Win10 re-installed, sim re-installed and just trying a 4 hour flight from OMSJ to VGEG in the Fenix A320. 1 hour in so far, looking good so far. No idea why this ntdll.dll error cropped up. My new system has been running perfectly since I built it, maybe a win update did something but strange quite a few people suddenly getting the same error. Stu i7 12700K , DDR4 64GB RAM @3600MHz, Asus Z690-Plus D4 MB, Gainward 4090 RTX Graphics, 850W Corsair PSU, Kraken AIO watercooler, Nvme 1TB ssd, 1TB ssd, 500GB ssd.
August 21, 20223 yr 16 hours ago, Rafal said: "playing with USB ports/devices while simming" occasionally the backlighting on my keyboard goes dark and unplugging/replugging the usb cable restores it, but any time I've tried this while flying MSFS it crashes the sim...EVERY time. I've learned that if I need to do anything usb related I just wait till I'm done flying - definitely annoying. i7-6700k • Gigabyte GA-Z170X-UD5 • 32GB DDR4 2666 • EVGA FTW ULTRA RTX3080 12GB
August 21, 20223 yr Tried a number of fixes - Got a 2nd CTD yesterday due to ntdll.dll. From what I have noticed when it happens on my end - It's typically happens when I am close to the approach stage or descending for the destination. The other parts of the fight seem fine. It doesn't matter what route it is - Aircraft both times has been the Fenix. I've not changed any settings or hardware at all. I will need to see if it happens in other aircraft as well. But my friend also has a very similar situation. I know the ntdl..dll is normally more related to drivers/hardware but it does seem strange I am seeing an increase of these crashes being mentioned caused by the same module on various forums/discords. Faulting application name: FlightSimulator.exe, version: 1.26.5.0, time stamp: 0x00000000 Faulting module name: ntdll.dll, version: 10.0.22000.832, time stamp: 0x3907dfbc Exception code: 0xc0000374 Fault offset: 0x000000000010c9a9 Faulting process ID: 0x4fd8 Faulting application start time: 0x01d8b4cb75957eb6 Faulting application path: F:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report ID: 571d8ae0-3b64-49f3-a827-5f1059543594 Faulting package full name: Faulting package-relative application ID: Update: I did have GSX installed but this has been uninstalled since the 1st crash just to see if it made a difference - It did not. My friend hasn't got GSX installed at all. Edited August 21, 20223 yr by Zangoose Vote to fix transparent sun visors having no effect on the sun glare effect in MSFS at: https://forums.flightsimulator.com/t/sun-shades-sun-visors-not-influencing-light-in-cockpit/691565/
August 21, 20223 yr I just finished a flight EKCH-GCLP in PMDG 700 flighttime 5hours 25 min the sim had run 6.5 hours no CTD i run SU10 beta 1.27.16 , have lot of stuff in community folder 130GB ( AIG livires 45GB) total ported to the map 270GB. AviaServer,Oi4FS,RealTraffic, PSXT-MSFS , GSX-PRO, AAO run in background. with all this GSX and other treads of CTD i was sure to get a CTD but happy that it not happend, wy dont really now Edited August 21, 20223 yr by westman http://
August 21, 20223 yr Same issue here. Last couple f months went without much issues, but since 2 days I experience CTD after CTD Even after updating Nvidia drivers to latest, emptying the community folder and even a complete re-install of the sim, the problems did not disappear. It crashes without a Windows log in the event viewer 🤔 Jasper Koelewijn Current sims: DCS, P3Dv4, P3Dv5, MSFS - Game pc: Intel I9 11900KF, Nvidia RTX 3090, 32GB RAM, 4x SSD, 1100W power supply, 2 x 40'' 4K monitor - Stream pc: Intel I7 4790K, Nvidia 1080Ti, 32GB RAM, 2x SSD, 850W power supply, 2x 27'' monitor - Other: Track-IR, Thrustmaster Wartog HOTAS, Saitek Combat rudder pedals, Saitek X-55, HP Reverb G2.
August 21, 20223 yr I too had my first CTD in months today on a flight from Copenhagen Kastrup to Lisbon Humberto Delgado. After 3+ hrs of flight, already over the Biscay Golf and about to enter northern Spain, fling the Fenix A320 at FL370, with excellent experience so far both with real world weather and online ATC + AI, it all of a sudden CTD'ed.... 😕 Lost the flight which was also supposed to be a test with Dx11. I have long been using Dx12 only, but since there were hints of an optimization for Dx11 I decided to try it. I will try to repeat the full flight latter today but in Dx12 and check if I get the same CTD. In Event Viewer I get: Faulting application name: FlightSimulator.exe, version: 1.27.16.0, time stamp: 0x00000000 Faulting module name: FlightSimulator.exe, version: 1.27.16.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x000000000227f467 Faulting process ID: 0x3c4 Faulting application start time: 0x01d8b54056ca5143 Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.27.16.0_x64__8wekyb3d8bbwe\FlightSimulator.exe Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.27.16.0_x64__8wekyb3d8bbwe\FlightSimulator.exe Report ID: 60a435fb-91fd-4320-8f7f-c51e2bef5856 Faulting package full name: Microsoft.FlightSimulator_1.27.16.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App Flying gliders since 1980 Flightsimming since 1992 AMD Ryzen 5600x, 32GB RAM, GPU Nvidia RTX 3060 Ti 8 GB, 1 TB and 500 GB nvme2 SSD drives, HP 27" 60Hz LED monitor @ 1920x1080, T16000, Hotas from old X52 Pro, Saitek Combat Rudder Pro (2010 model)
August 21, 20223 yr Decided to try out the PMDG 737 seeing as my previous two crashes in regards of ntdl.dll were in the fenix. Got to 4000ft ready to continue the descent for Athens and boom, CTD. This time it doesn't actually mention ntdll.dll: Faulting application name: FlightSimulator.exe, version: 1.26.5.0, time stamp: 0x00000000 Faulting module name: FlightSimulator.exe, version: 1.26.5.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x00000000021428c0 Faulting process ID: 0x4164 Faulting application start time: 0x01d8b55a659300b2 Faulting application path: F:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe Faulting module path: F:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe Report ID: 1232a3b6-31a0-4429-9642-5844e2b65c71 Faulting package full name: Faulting package-relative application ID: Vote to fix transparent sun visors having no effect on the sun glare effect in MSFS at: https://forums.flightsimulator.com/t/sun-shades-sun-visors-not-influencing-light-in-cockpit/691565/
August 21, 20223 yr As some one on another thread speculated: Live weather is the culprit. They've tweaked it and borked it. Edited August 21, 20223 yr by jarmstro
Archived
This topic is now archived and is closed to further replies.