It is a new install, and if it was a driver or oom problem it would show up in the logs somewhere like Windows Error Reporting.
No, it's exactly the opposite. If it's a driver issue, since drivers runs with a permission level higher than anything else, they are able to freeze Windows even BEFORE it has a chance to log an error Event.
I'll repeat it again: GSX, by itself, CANNOT FREEZE FSX, it's theoretically impossible, since it runs entirely external to it, there's no way for GSX to access the FSX process.
An OBJECT created by the sim, on behalf of GSX, could freeze the Sim or even the whole Windows, but not because the object is "bad", only because there's a problem with a video driver setting or tweak, or an FSX setting or tweak, which is causing a problem TO the video driver, which is the ONLY thing that can crash FSX or Windows.
A SOUND created by GSX, could also freeze the Sim or even the whole Windows, but not because the sound is "bad", only because there's a problem with the AUDIO driver, which is the ONLY (it's a driver) thing that can also crash FSX or Windows.
I'll repeat it again, since you haven't said you ever TRIED to do what I suggested:
To fix a video driver problem:
- Be sure your video driver is updated
- Set your video driver to default settings.
To fix a problem with FSX settings and tweaks:
- Remove the %APPDATA%\Microsoft\FSX\FSX.CFG file, so FSX will create a new one with all default settings on the next restart.
Don't touch anything, and try the same airport and the same gate, using a DEFAULT airplane so, at least, we might be reasonably sure it's not a memory-hungry airplane that is OOM-ing the sim.