View Full Version : ERROR: Out of memory requesting
06-24-2006, 06:58 PM
I've been playing the game and I keep getting this error (The memory values change).
ERROR: Out of memory requesting 50331648 bytes (80477200 total free)
I know I'm not running out of memory, I got 2 gigabytes of memory and I set my virtual memory to 2048/4095 on all my partitions (windows 2000).
I'm running with everything on including next generation content with the exception of shadows.
Here's a list of my hardware:
amd 64 dual core 4200+
nvidia 7800 gtx 512
2 GB Corsair XMS
2 400 GB WD Hard Drives in a raid 1 config
USB Headphones for sound.
Thanks for any help on this issue in advance.
06-25-2006, 03:46 AM
Well, with a system like that you can run any game with very high settings in high resolutions. Re the out of memory errors, perhaps don't take it so literally, have you got all updates from M$, basically a patched and up to date OS, you don't mention if you have applied the TRL 1.1 or 1.2 patch? These are accumulative so you don't have to worry about 1.1 if you have applied 1.2.
I run with an X1800XT 256MB and I absolutely have to turn the shadows off (like you) in the ingame menu otherwise it runs like a slideshow, other than that I have everything on, perhaps try disabling different effects like depth of field, water effects etc, until you get a more stable setup.
Lastly you could try looking for updated drivers, for your sound, graphics and chipset, I have read on another forum that new Nvidia drivers are out with loads of bugfixes!
Good luck and let us know if you find a resolution,
06-25-2006, 01:06 PM
I was running forceware 84.43 beta, then upgraded to 91.31 beta. I'm running trl v 1.2. All my windows updates are installed, and my nforce 4 drivers are "amd 6.70".
I'm completely stumped on this one, not sure what the problem is. I might just try to completely reinstall it, as the problems were not happening at first.
I did notice a significant increase in fps when I upgraded to forceware 91.31, but the crashing still persists.
If anyone has any similar issues, or knows how to fix it, I would love to hear about it.
06-25-2006, 05:40 PM
I totally reinstalled it, and it still does crashes with the same error.
06-26-2006, 11:45 PM
A hack job that seems to work (not happy about it though).
Found out how to enable more config options from some site by editing the registry, to enable them, do the following:
Open up: HKEY_CURRENT_USER/Software/Crystal Dynamics/Tomb Raider: Legend
Add a DWORD key named: ExtendedDialog with a value of 1.
Now on your shortcut for trl, add -config at the end of the command.
The only option I changes I made were:
Uncheck the "Use 3.0 Shader Features"
Switched to 8x Anisotropic Filtering from 16x
06-28-2006, 06:32 AM
Kudos to you for finding that one out and fixing it yourself! As you say though
"A hack job that seems to work (not happy about it though)."
You just shouldn't have to do this though to get the game to work, it could be crystal dynamics fault, it could be nvidias fault, pc gaming can be a nightmare really. If I was having trouble myself I'd dig in to regedit (hate it in there) and look myself but fortunately I seem to be having a good run with my gaming at the moment.
glad you appear to have trl up and running though now,
06-28-2006, 08:12 AM
Ya, it's good to finally be able to play the game. It's the only game I've had problems with since I can remember. Well, I often had to deal with performance/frame rate issues, but that's cause I crank everything up then turn things down gradually. The only game I had to do that for with my new setup though is Oblivion, that game was a beast.
Anyway, I usually don't buy console ports, but I got trl because PC Gamer gave it good reviews, so I figured I would give it a go. Now that I have it up and running, I'm having fun with it, good gameplay, and a change of pace from the normal shooters.
07-08-2006, 06:20 AM
Thanks for posting that registry hack fix Baggz! I was suffering from the same "out of memory" problem. Your fix to turn off the 3.0 shaders was the only thing that worked. :thumbsup:
vBulletin® v3.8.7, Copyright ©2000-2013, vBulletin Solutions, Inc.