appcrash AGHHHHH

[Axionkt]

Yes the game is crashing as soon as I launch it. The crosshair appears on windows desktop and the crash occurs.

[jlv]

It sounds like it might be crashing when it tries to set the display mode. Try using the following config file, which will start you out in windowed mode.

http://mxsimulator.com/junk/config

[Axionkt]

It is still crashing at the same moment.
However your information gave me an idea and my laptop is running hybrid SLI. If I disable the chipset integrated GPU it works, which means mx sim is probably trying to run on the 9400m instead of the "real" GPU.

Is there any way to specify the GPU I want to use in the config file?

Thanks for your help.

[Axionkt]

Sorry for the double post, it seems I can't edit the previous one.
On the configuration page in MX simulator Driver info still shows the 9400m as the graphic card even if it's disabled in the BIOS.

[jlv]

I don't believe there is a way select which GPU to use. The application can only gets to ask for a specific pixel format.

Is it possible that the hybrid sli driver didn't install its opengl dlls? That might explain why it's seeing the wrong GPU.

[Axionkt]

I believe it did install the opengl dlls. (nvoglv64.dll)
I know some software don't detect the right GPU automatically but I've seen the possibility to manually select a GPU to run a game on the setup application (in a combo box before any 3D object is created).
It's not a big deal since I can now play the game thanks to you but it would be even better if I could run it without having to boot in BIOS

[discodave]

sorry been really busy. the game only works if i totally wipe my hard drive and reinstall windows so back to factory settings. but the game only works for a while then stops again i havent installed any diffrent thing or anything just all of a sudden stops. so dont know what it is the computer runs amazing in any other way its only this problem which i cannot understand thanks disco

[Axionkt]

Did you try to rename mx.exe to something else?
Today I had the same problem as you described and even if I can't understand why, I realized that MX sim 1.2 renamed as mx.old.exe worked so I tried to rename the latest snapshot and it worked

[Axionkt]

Mmm I spoked too soon, sometimes it runs and sometimes it doesn't, I just keep launching the game unitl it works.
Now the error is different and happens with 1.2 as well as with the latest snapshot.

Problem Event Name: APPCRASH
Application Name: mx.exe
Application Version: 0.0.0.0
Application Timestamp: 4a5e76a9
Fault Module Name: StackHash_0d2c
Fault Module Version: 6.1.7600.16385
Fault Module Timestamp: 4a5bd98a
Exception Code: c0000374
Exception Offset: 00008518
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1036
Additional Information 1: 0d2c
Additional Information 2: 0d2cb744cf99713306b04e954ffbcb9b
Additional Information 3: 9728
Additional Information 4: 97288afefc8bc49bbe2a0d36eb061347

[jlv]

sorry been really busy. the game only works if i totally wipe my hard drive and reinstall windows so back to factory settings. but the game only works for a while then stops again i havent installed any diffrent thing or anything just all of a sudden stops. so dont know what it is the computer runs amazing in any other way its only this problem which i cannot understand thanks disco

Does it happen if you disable windows update? It might be upgrading you to something that doesn't work.

Mmm I spoked too soon, sometimes it runs and sometimes it doesn't, I just keep launching the game unitl it works.
Now the error is different and happens with 1.2 as well as with the latest snapshot.

Does it help if follow the instructions in the second reply here?

1. Open your Start menu and click Control Panel
2. Browse to "System Maintenance" then "System"
3. In the left panel, select "Advanced System Settings" from the available links
4. You should now see the System Properties Window, which will have three sections. The top section is labeled "Performance" and has a "Settings" button. Click this button.
5. Select the "Data Execution Prevention" tab.
6. Select the option which reads "Turn on DEP for all programs and services except those I select"
7. Use the "Browse" button to locate the executable file for the application you were trying to start when you received the StackHash error, and click Open to add it to your exceptions list.
8. Click Apply or OK to commit your changes.

[Axionkt]

Unfortunately I didn't manage to reproduce this error. I tried to launch MX Sim about 150 times and out of these 150 times it started twice, once it crashed again on the menu with the ntdll.dll error and the second time it didn't crash.
In fact, if I manage to start a race before it crashes (I have to be really quick to click "New Race" & "Start Race") it doesn't crash at all until I close the game myself.
This error is quite surprising, is there any switch to enable a debug log creation or similar?

[jlv]

The last snapshot version will store some info in "%LOCALAPPDATA%\MX Simulator\lastlog.txt".

If it only happens when there isn't a track loaded, you could add --track x1b to the command line parameters as a workaround.

I just looked at that code path more carefully and there was an empty glBegin/glEnd sequence in the function that draws the title screen in that situation. I'm not sure if it's legal to do that or not. The 8/8/2009 snapshot doesn't do it anymore, so if the crash doesn't happen with that version that was the problem.

[Axionkt]

Thanks a lot for helping!

Unfortunately the trick didn't work and even worse, nothing seems wrong in the log :'(
I didn't manage to run the game a single time today (using 1.2, 2009-07-15 or 2009-08-08) , it has nothing to do with the version, this randomness is really strange.

BTW, the timestamp is +10min off the system's time.

[Axionkt]

Thought I would post the end of the log anyway:

2:50:25.54] Options:
[2:50:25.54] threaded: [on]
[2:50:25.54] Starting message processing thread
[2:50:25.54] Creating window
[2:50:26.14] DirectInput roll call...
[2:50:26.16] Souris (Souris)
[2:50:26.16] 3 axes, 7 keys
[2:50:26.16] axis 0 is relative
[2:50:26.16] axis 1 is relative
[2:50:26.16] axis 2 is relative
[2:50:26.16] Clavier (Clavier)
[2:50:26.16] 0 axes, 109 keys
[2:50:26.16] Transmetteur infrarouge Microsoft eHome (Transmetteur infrarouge Microsoft eHome)
[2:50:26.17] 0 axes, 0 keys
[2:50:26.17] Transmetteur infrarouge Microsoft eHome (Transmetteur infrarouge Microsoft eHome)
[2:50:26.18] 0 axes, 573 keys
[2:50:26.18] Wow! This thing has a lot of buttons!
The first ignored button is called "Bouton 500"
[2:50:26.18] Button count (573) doesn't match actual number of buttons (500)
[2:50:26.19] Transmetteur infrarouge Microsoft eHome (Transmetteur infrarouge Microsoft eHome)
[2:50:26.19] 0 axes, 0 keys
[2:50:26.20] Transmetteur infrarouge Microsoft eHome (Transmetteur infrarouge Microsoft eHome)
[2:50:26.20] 0 axes, 256 keys
[2:50:26.21] Ikari Laser (Ikari Laser)
[2:50:26.21] 0 axes, 0 keys
[2:50:26.21] Ikari Laser (Ikari Laser)
[2:50:26.21] 0 axes, 12 keys

[jlv]

It's crashing in the middle of enumerating the DirectInput controllers. Does it work if you disconnect "Transmetteur infrarouge Microsoft eHome"?