aldox62

Hi Pete, here's the update ... Along the weekend I zapped c:\ and d:\ and restarted with a fresh W11 Pro installed right from the USB media. Mi previous setup was an upgrade from W10 and there was a remote suspect about the whole result, even if apparently everything worked -- not considering fsx. I moved in the meantime to FSX:SE, on d:\, and installed FSUIPC ORBX various modules and so far just PMDG T7-200 to run the test flight that I have recreated in the meantime. Now It looks it works fine, the 12 hours test flight is almost at the end without problems... maybe I got rid of the CTDs in the end!. Hope this can help someone else to solve the issue! Kind regards Aldo

Pete, the test flight crashed after minimum 6 hours, PC unattended along the night. Prior to that I rebuilt the wxstations file (new one being very different from original one) and deleted all the wx files in the user\Flight Simulator Files folder. I was quite sure it was not an FSUIPC issue, but my attention was caught by the same error that was reported in the forum and so I tried this way as well.. Thanks again for your kind and prompt support ! In case I find the solution I will post here to update Kindest regards, Aldo

sorry this is the right AppCrashView file... Aldo AppCrashviewInfo.txt

Hi Pete, added the NoWeatherAtAll flag into the ini, and relaunched the test flight It worked for some time - I think couple of hours, and then crashed. I was not at the PC at the moment, so no interactions Attached the FSUIPC4.log file the and the AppCrashView info for the kernel32 error Thanks! Aldo FSUIPC4.log AppCrashviewInfo.txt

Great thanks a lot Aldo

Thanks Pete, I will follow your kind suggestions and provide the logs as you indicated if I get a crash after setting the .ini file In case I get no crash what should I do with the wxtationlist.bin file ? I imagine I can delete all the wx files without issues Thanks again, Aldo

Hi, I am joining this thread because I am experiencing since months now exactly this error, same Fault offset: 0x00098d51. I am now running W11 Pro, FSX SP2 boxed, FSUIPC registered latest version, ASN16 public beta (works with W11), PMDG 737 all versions, PMDG 777 all versions, PMDG 747 QUOTS latest version, GSX level 2 latest version, various ORBX packages, one airport scenery (LIMF, Turin, Italy). I have 4 different simconnect versions installed, did not dare to touch them so far. The issue started when I (my fault) upgraded W7 to W10, since then I've tried almost everything: - moved to FSX:SE and then back to FSX SP2 boxed after orderly removing everything, cleaning up down to registry level and reinstalling the whole environment a piece at a time with intermediate tests - tried various tweaks, now my FSX.cfg just has the highmemfix tweak - uninstalled/reinstalled all the add-on packages: aircrafts, utilities, etc. I reached the PMDG max activation limit.. 🙂 - interacted with PMDG support via tickets - enabled/disabled the various utilities one at a time - followed CTD guides as available on internet - moved back and forth with different video (GTX570) and audio drivers - added Uiautomationcore.dll as recommended by PMDG - tested HW: memory (32GB), disks, mobo, drivers - extensively searched on FSX major forums - other debug actions I do not remember now.. Basically, I have great performance, 30fps almost everywhere, but the CTD hits randomly - usually not earlier than 1.5-4 hours of flying my EGLL-KSFO test flight with T7-200 or 747. Shorter flights with 737 usually go to the landing without issues. I also created a second test flight, EGLL-SBGR to exclude issues with the main saved test flight, to no avail. Right yesterday I got the latest W11 update that touched kernel32.dll as well, and hoped for an improvement: no, the test flight failed after 3 hours. This adds to my idea that it is not a W11 issue. The CTD appears randomly: either when I'm not sitting at the PC, or when I take some action on main FSX screen say change the flight level or work with FMC (not touching FSX menus) or when I scroll ASN16 map to keep the aircraft in view, or even when I do other things on the PC that may not directly touch the FSX environment windows on the desktop. That's it, just wanted to share my experience.. If there are any further debug hints these are more than welcome! Kind regards, Aldo