Crash on menu, ATI notebook. Tried other fixes. - by waveform
waveform on 7/4/2010 at 11:51
Hi, I'm excitedly revisiting Thief Gold but can't get past the intro movie.
Running the fixed exe called "thieffixedg.exe", but same happens with the original EXE. Intro movies start (Eidos logo, etc. them story intro). Upon clicking any key (even Alt, as I tried alt-tabbing to set affinity) it exits the movie to go to the menu, but crashes straight away.
I get the menu for a split second before it crashes. I even hear a split-second of that lovely, clanky-clanky ambience. :) It correctly shows in 800x600 as well. The error is a Windows "memory can't be read" error:
Inline Image:
http://i42.tinypic.com/2m7ur8x.gifIt does exactly the same thing with thieffixedg.exe.
My notebook is an HP 8510P, Centrino dual core, ATI Mobility HD2600. Driver is ATI (not Omega) v8.620. Running XP SP2. Kerio firewall and Avast a/v, nothing else notable.. no startup bloat like Adobe, Google update, Nero etc, it's a very clean setup.
Interestingly, when I set it to Win95 compatibility, the game doesn't even start, as it won't recognise my disk (keeps asking me to insert it). So I can't even get that option to work.
So I'm a bit stumped... any ideas? :-s
bikerdude on 7/4/2010 at 17:14
I've seen this error before, but can't remember what the fix is. I'm sure someone will be along with the fix.
Matthew on 7/4/2010 at 17:21
The Eidos and Sold Out support sites suggest that this is due to a failure of the graphics card to support DirectX and suggest that you try different drivers, if that's of any help.
waveform on 7/4/2010 at 17:31
Quote Posted by Matthew
The Eidos and Sold Out support sites suggest that this is due to a failure of the graphics card to support DirectX and suggest that you try different drivers, if that's of any help.
Thanks for the help, but not sure if that's the case here, since I've played many other games on this notebook, even Crysis and Assassin's Creed. Definitely doesn't have a problem with DX games.. unless there's something specific in the config that Thief might be looking for?
Matthew on 7/4/2010 at 17:42
Not DirectX per se, DirectX 7. Sometimes newer drivers can drop support for older versions of DirectX and that can cause problems. Sorry I forgot to make that clear.
Just a thought though, as I've not come across this problem myself.
waveform on 8/4/2010 at 02:21
Quote Posted by Matthew
Not DirectX per se, DirectX
7. Sometimes newer drivers can drop support for older versions of DirectX and that can cause problems. Sorry I forgot to make that clear.
Just a thought though, as I've not come across this problem myself.
I wonder then if Windows 95 compatibility mode will help? It seems to have helped others, but the problem is when I try that, the first thing that happens is it asks me for the CD, even though it's in the drive. Is there a fix for that behaviour?
Matthew on 8/4/2010 at 12:07
Urgh, no idea. The only thing I can think of is that the CD-ROM drive's drivers are 16-bit instead of 32-bit, but I have no clue if that would be the case here.
