- MICROSOFT FLIGHT SIMULATOR 2017 STEAM HOW TO
- MICROSOFT FLIGHT SIMULATOR 2017 STEAM WINDOWS 10
- MICROSOFT FLIGHT SIMULATOR 2017 STEAM WINDOWS
To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.Īpplication Path: C:\Program Files (x86)\Steam\steamapps\common\FSX\fsx.exe
MICROSOFT FLIGHT SIMULATOR 2017 STEAM WINDOWS
The program fsx.exe version 5.0 stopped interacting with Windows and was closed. Hashed bucket: d4dd1865e277b67901ea24906ad87cbcĮnding a Windows Installer transaction: C:\Program Files (x86)\Steam\steamapps\common\FSX\SDK\Core Utilities Kit\SimConnect SDK\LegacyInterfaces\FSX-XPACK\SimConnect.msi. \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\ \\?\C:\Users\Dell\AppData\Roaming\Microsoft\FSX\fdr.dat \\?\C:\Users\Dell\AppData\Roaming\Microsoft\FSX\scenery.cfg \\?\C:\Users\Dell\AppData\Roaming\Microsoft\FSX\dxdiag.txt \\?\C:\Users\Dell\AppData\Roaming\Microsoft\FSX\ Report Id: 2b9cea93-5847-4b66-8ab3-92d510ffcd6bįaulting package-relative application ID:
Here are a few extracts/copy and pastes from my Windows Event Viewer Program:įaulting application name: fsx.exe, version: 5.0, time stamp: 0x559f9a9aįaulting module name: sim1.dll, version: 5.0, time stamp: 0x559f9ab4įaulting application start time: 0x01d585e36ae96c09įaulting application path: C:\Program Files (x86)\Steam\steamapps\common\FSX\fsx.exeįaulting module path: C:\Program Files (x86)\Steam\steamapps\common\FSX\sim1.dll
MICROSOFT FLIGHT SIMULATOR 2017 STEAM HOW TO
If anyone could offer any advice or if anyone knows how to fix these problems, I would be very grateful. I have also deleted and tried FSX with and without the UIAutomationCore DLL file, but either way made no difference at all. It would always not have any problems with any of the other UK2000s scenery, such as Birmingham, Manchester or Edinburgh etc, until it stopped working completely. Also, before it stopped working completely, when the first symptoms started occurring, it would load certain dates and times, and locations ok, for around 10 minutes before CTD, but it would never say “Load any London Airport or location at say 05:57am”, I also started having first symptoms, after I installed the UK2000’s - East Midlands, Newcastle, Bournemouth and Doncaster Sheffield Scenery. I am completely baffled by why my FSX SE would work for 2 weeks, and then cease working completely. I have also checked and double checked Windows Event Viewer, it didn’t come up with any errors and it did not point to any DLL files, it just said “FSX stopped interacting with Windows, and so the application was suspended.” A few days, before my FSX SE stopped working completely, I noticed some strange behaviour, when I accessed the AI traffic, or any of the “Right Click Menu Options”, it would hang/freeze, eg, it would not crash it would just cease all activity, and there was no interaction with the program at all, and then after 10-15 seconds, it would then CTD. I then tried deleting the FSX SE - Logbook File, no effect, I have tried deleting the FSX SE - Config files, still no effect, I then tried to reinstall FSX SE, it would other pass 100% and display the virtual cockpit, but then immediately within 5 seconds, I would again get a blue spinning cursor, and it would CTD after 10-15 seconds. Then recently, about a week ago, it would load, reach 100%, then I would get a blue spinning cursor, and it would CTD.
It ran very smoothly with no lagging for the last week or two. I have plenty of RAM - 8GB and an NVIDIA graphics card.
MICROSOFT FLIGHT SIMULATOR 2017 STEAM WINDOWS 10
A few weeks ago, I purchased Microsoft Flight Simulator X - Team Edition for my Windows 10 PC.
0 kommentar(er)
