I have a weird issue with my FSX. It has been a few months since I played it, and even then it was right after I installed Windows 7 home 64 bit. It worked, I tried it right after I installed it, and then never again until today.
I have tried installing the updates (SP1 and SP2), and have looked everywhere on the internet.
I have a Fujitsu PC with dual Core Duo processors, 8 gb RAM, FX5600 video card, ect. When I did try it, I was able to max out most sliders so I don't think it is a performance issue.
When I launch FSX it goes in this sequence:
1. Pop-up says "The color scheme has been changed to Windows 7 Basic"
2. Then is shows the "Building database for new scenery files......"
3. Then it shows a dialogue box that says "Microsoft Flight Simulator has stopped working, windows is checking for a solution"
4. Finally it says "Microsoft Flight Simulator has stopped working, A problem has caused the program to stop working correctly. Windows will close the program and notify you if a solution is available"
When I look at the event viewer for windows I see this:
The program fsx.exe version 10.0.60905.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
Process ID: 12a8
Start Time: 01cd62ccaf7ad8d1
Termination Time: 17
Application Path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
Faulting application name: fsx.exe, version: 10.0.60905.0, time stamp: 0x44fd0a92
Faulting module name: multiplayer.dll, version: 10.0.60905.0, time stamp: 0x44fd0f33
Exception code: 0xc0000409
Fault offset: 0x00047c21
Faulting process id: 0x17f8
Faulting application start time: 0x01cd62cc7bd91497
Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
Faulting module path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\multiplayer.dll
Report Id: da8ebdc5-cebf-11e1-89d0-00e08173d9b9
Report Id: 1781229b-cec0-11e1-89d0-00e08173d9b9
So is it the multiplayer.dll causing this issue?