mx.exe crash's?

[Yames]

i try to play the game and hit start and it goes to the loading screen and says loading bikes then the exe crashes,any ideas?

windows xp media center edition
version 2002 service pack 3

CPU: Intel(R) Celeron(R) D CPU 3.20GHz
2 Gb DDR2 of ram
GPU:ATI Saphire HD 2600
Video RAM 512.0 MB ddr2
3D Yes
Hardware T&L Yes
Pixel Shader version 3.0
Vertex Shader version 3.0

[jlv]

Check the crash details for "Fault Module Name". It's probably the OpenGL driver (atioglxx.dll) crashing.

Try getting the latest driver from ATI.

[Yames]

idk, in the error report it says

"AppName: mx.exe ModName: atioglxx.dll
ModVer:6.14.10.10151 Offset: 00b6696f"

is that what your talking about? i updated it not to long ago,i tried to play the game a few months ago and it still did the same thing,way before i updated it..so idk

Driver Packaging Version 8.762-100803a-103687C-ATI
Catalyst™ Version 10.8
Provider ATI Technologies Inc.
2D Driver Version 6.14.10.7111
Direct3D Version 6.14.10.0775
OpenGL Version 6.14.10.10151

[Yames]

updated through steam and its still doing it,it just says ModVer: 6.14.10.10188 now..man this is annoying

[jlv]

Try the driver cleaner from yzmxer's graphics driver installation guide.

[Yames]

tried that twice still doing it..

[Yames]

idk man,i cant get it to go past the loading bikes thing no matter what i do..think i should try uninstalling the driver then going back to 10.4? everyone says that version works with everything but i don't see that changing anything either

[jlv]

10.4 seemed to be very solid, but I don't think anyone has been getting crashes with 10.9. What does the driver info in the graphics/sound setup screen say?

Also, make sure you don't have "Ground Texture Resolution" set too high in the game. 256x256 is plenty.

[Yames]

the Ground Texture Resolution was set at 128x128,i tried it at 256x256 with no change.

the driver info in the graphics/sound setup says
Drive info:
ATI Technologies inc.
ATI Radeon HD 2600 PRO
3.3.10188 compatibility profile context

[jlv]

It might be worth trying enabling or disabling framebuffer objects and shaders since the game might not trigger the bug on those paths. Other than that, all I can think of is trying a fresh install of Windows and the ATI Catalyst driver.