Fatal Error Crash to Desktop

[Borealis]

Shortly after getting to the Kazakhstan level, I get a Fatal Error Crash that takes me to desktop. I've checked drivers, uninstalled and reinstalled, and gone back to earlier saves with the same result. The error reads as follows:

A fatal error has occured while playing Tomb Raider: Legend. Please refer to the ReadMe file for information which might help you solve this problem, or contact Eidos customer support.

If there is a ReadMe file buried in the installation, I can't find it. Has anyone else run into this problem?

[stevefreiman]

Program Files/Steam/SteamApps/common/Tomb Raider Legend/read me

I also had a crash I couldn't get through in Angel of Darkness, forum posts mentioned sound card (?). Good luck

[Borealis]

Thanks for your response and your suggestion Steve. Unfortunately that did not solve the crashing issue, unless it is now tied into the save file. I'll try an earlier save, or even start over to see if that might be the case. I saved the detailed description from the crash message, and here it is:

Exception at: 03/06/2013 at 07:06:12
Exception code: Access violation (c0000005): (Read of address: 0x0163f8c0)
Exception address: 0x005c136b

CPU info:
---------
EAX = 0x0163f8c0
EBX = 0x0a0e4f80
ECX = 0x3f800000
EDX = 0xc2058480
ESI = 0x0ae7da9c
EDI = 0x0afb4980
EIP = 0x005c136b
ESP = 0x0018e820
EBP = 0x0018e908

I also ran DXDIAG since the helpfile mentioned DirectX 9.0c, and I am running version 11, but I was under the impression DirectX supported legacy versions without issues. I'd hate to have to revert to an earlier version everytime I wanted to play Legacy...

[Mister E]

You may try disabling DEP in windows. I was having a similar problem and it helped. Although, I just went to start the Kazhakstan level myself and it popped up again (I haven't tried it again since).

[Borealis]

I ended up installing Legend to my laptop (it's an older laptop) and other then one time on the train getting the Fatal Error crash, it's worked fine since. I'm wondering if the problem might be linked to using a quad-core.

[Mister E]

Update: I kept getting the crash when starting Kazhakstan again. There's another thread here that suggested disabling Next Gen Content from the initial settings -- that seems to have done the trick for me. I actually disabled it from the launcher settings, then enabled them in-game, and haven't had an issue

[Mister E]

Originally posted by jbezdecny:

I ended up installing Legend to my laptop (it's an older laptop) and other then one time on the train getting the Fatal Error crash, it's worked fine since. I'm wondering if the problem might be linked to using a quad-core.

That's a good observation -- I have to wonder. It seems to be some kind of memory addressing problem. I assumed it might be because of x64 (which most quad-cores probably are at this point)

[OnWednesdaysWeWearBlack]

Im getting the fatal error crash at the end of bolivia- I just went and completed croft manor and I've gone back in to my game to do Paraiso but I keep getting fatal error crash

[tom]

I'm getting the Kazakhstan crash also - after some Googling I disabled my Norton 360 antivirus and that helped - I was able to start the level, but still crash after a few minutes. I'll try the Next Gen Content fix next.

[Fizz]

Just read this post about an hour ago as my game was crashing at kazakhstan too. Just thought I'd dd that turning off the Next Gen fixed it for me too. Thanks guys :)

[tom]

The Next Gen fix did, in fact work for me. :) +1 to FizzWizz for his reply, wihch prompted me to post.

[admcmei]

Originally posted by tom:

The Next Gen fix did, in fact work for me. :) +1 to FizzWizz for his reply, wihch prompted me to post.

I confirm, too... and then immediately after I had another issue where a checkpoint instead of triggering the next sequence throws me back a couple minutes!

[Ozric]

Originally posted by jbezdecny:

I ended up installing Legend to my laptop (it's an older laptop) and other then one time on the train getting the Fatal Error crash, it's worked fine since. I'm wondering if the problem might be linked to using a quad-core.

The problem is not linked to using a quad core. I'm using a 64 x2 dual core rig on Windows 7 64bit and keep getting the fatal crash, but it only started appearing in the Kazakhstan level. Everything was running perfectly before this with no problems whatsoever. I'll try disabling the Next Gen content to see if that works. The game crashes where Lara sees the poison gas for the first time, so it may be some graphical conflict.

[Ozric]

Originally posted by Mister E:

Update: I kept getting the crash when starting Kazhakstan again. There's another thread here that suggested disabling Next Gen Content from the initial settings -- that seems to have done the trick for me. I actually disabled it from the launcher settings, then enabled them in-game, and haven't had an issue

This seems to have worked for me too, at the moment anyway. I'll post an update if the error shows up again. As you say, disable Next Gen in the launcher set up, then enable it again in-game. Seems to have done the trick. Cheers : )

[monsterseventeen]

i went to set up from the steam launcher, set all back to default, then in game switched the best displays on, it was still to small for my screen, after exiting the game i went back to set up and all but "v sync" was checked, i put to my resolution and left v sync alone, it seems ok now, i hope this works for you too

[Agent under Fire]

this is an old problem that was never fixed, you must disable next gen content in this level