You're running the ATI drivers from here right? Given that, I'd try running it in compatibility mode just in case it's a problem with the dual GPU setup.
Other things to check would be the "lastlog.txt" file from "MX Simulator Personal Folder" under All Programs / MX Simulator (post the whole thing here) and the problem details in Windows Action Center (check for Fault Module Name).
Josh Vanderhoof
Sole Proprietor jlv@mxsimulator.com
If you email, put "MX Simulator" in the subject to make sure it gets through my spam filter.
[3:29:26.16] Logfile "C:/Users/Duncan/AppData/Local/MX Simulator/lastlog.txt" opened
[3:29:26.16] JUGL 0.31
[3:29:26.18] Registry mode is 1680x1050x32@60hz
[3:29:26.18] Found mode 640x480x8@60hz
[3:29:26.19] Found mode 640x480x16@60hz
[3:29:26.19] Found mode 640x480x32@60hz
[3:29:26.19] Found mode 720x480x8@56hz
[3:29:26.19] Found mode 720x480x16@56hz
[3:29:26.19] Found mode 720x480x32@56hz
[3:29:26.19] Found mode 720x576x8@56hz
[3:29:26.19] Found mode 720x576x16@56hz
[3:29:26.19] Found mode 720x576x32@56hz
[3:29:26.19] Found mode 800x600x8@56hz
[3:29:26.19] Found mode 800x600x16@56hz
[3:29:26.19] Found mode 800x600x32@56hz
[3:29:26.19] Found mode 1024x768x8@60hz
[3:29:26.19] Found mode 1024x768x16@60hz
[3:29:26.19] Found mode 1024x768x32@60hz
[3:29:26.19] Found mode 1152x864x8@60hz
[3:29:26.19] Found mode 1152x864x16@60hz
[3:29:26.19] Found mode 1152x864x32@60hz
[3:29:26.19] Found mode 1280x720x8@50hz
[3:29:26.19] Found mode 1280x720x16@50hz
[3:29:26.19] Found mode 1280x720x32@50hz
[3:29:26.19] Found mode 1280x768x8@60hz
[3:29:26.19] Found mode 1280x768x16@60hz
[3:29:26.19] Found mode 1280x768x32@60hz
[3:29:26.19] Found mode 1280x800x8@60hz
[3:29:26.19] Found mode 1280x800x16@60hz
[3:29:26.19] Found mode 1280x800x32@60hz
[3:29:26.19] Found mode 1280x960x8@60hz
[3:29:26.19] Found mode 1280x960x16@60hz
[3:29:26.19] Found mode 1280x960x32@60hz
[3:29:26.19] Found mode 1280x1024x8@60hz
[3:29:26.19] Found mode 1280x1024x16@60hz
[3:29:26.19] Found mode 1280x1024x32@60hz
[3:29:26.19] Found mode 1360x768x8@60hz
[3:29:26.20] Found mode 1360x768x16@60hz
[3:29:26.20] Found mode 1360x768x32@60hz
[3:29:26.20] Found mode 1400x1050x8@60hz
[3:29:26.20] Found mode 1400x1050x16@60hz
[3:29:26.20] Found mode 1400x1050x32@60hz
[3:29:26.20] Found mode 1440x900x8@60hz
[3:29:26.20] Found mode 1440x900x16@60hz
[3:29:26.20] Found mode 1440x900x32@60hz
[3:29:26.20] Found mode 1600x1200x8@60hz
[3:29:26.20] Found mode 1600x1200x16@60hz
[3:29:26.20] Found mode 1600x1200x32@60hz
[3:29:26.20] Found mode 1680x1050x8@60hz
[3:29:26.20] Found mode 1680x1050x16@60hz
Are you sure that's the whole file? The end of that file would be the most useful part since that will show what was happening when it crashed. See if you can find the crash details in Windows Action Center too.
Josh Vanderhoof
Sole Proprietor jlv@mxsimulator.com
If you email, put "MX Simulator" in the subject to make sure it gets through my spam filter.
The next thing it would have done after the DirectInput enumeration is create an OpenGL context. For it to crash that early the OpenGL driver would have to be extremely buggy or corrupted. Try using the driver cleaner from yzmxer's topic just in case you have a corrupted dll somewhere. If it's possible to run it in single GPU mode I'd try that too.
Josh Vanderhoof
Sole Proprietor jlv@mxsimulator.com
If you email, put "MX Simulator" in the subject to make sure it gets through my spam filter.