144 replies to this topic

[Kyle Polulak]

Steps to Reproduce
0. Boot the game.
1. Login to the game.
2. Launch a Match
3. Observe CryEngine error crash at any time during the match.

Notes
CryEngine error reading "memory allocation for 2873140736 bytes failed".

Workarounds
Try the Repair Tool

[Zolaz]

So far I have had to use the repair tool 3 times in the past 2 days.

[GreySoldier]

The indicated workaround is not effective in what I have experienced.

CryEngine Memory allocation fails have significantly increased in my personal case since patch 1.2.227
Particularly so on River City where roughly 85% of matches on that map result in the CryEngine memory allocation fail error.

Not to mention that suggesting waiting 15-20 minutes for the repair tool to find no changes in files, each time the failure occurs, is not much of a workaround to begin with.

Deleting the shader cache can be done manually much quicker. But again, does not seem to change anything, a fresh launch (after shader cache deletion) still results in a CryEngine memory allocation failure.

[Arnold Carns]

From my own experience this problem only occured on a 32 bit OS and was somewhat related to the restricted amount of RAM usable. Since I changed to a 64 bit OS, this problem never came up again for me.

[Fat Amy]

If I would be sure that switching my OS to 64bit, I would probably do it (although it would be a complex effort). I´m getting a crash to the desktop every second or third game I start. I really cant count how often I have to reinstall or use the repair-tool. Support tells me it´s a known issue and that they HOPE to fix it someday. Well, I hope so too, because like this, MWO is unplayable in a group, which means I will have to stop playing someday.

Please FIX THIS SOON.

It even seems to be gettig worse with the new patch! Today I repaired several times, being able to finish exactly two games without a crash (those were not in a row). It hurts me!

[Lith Dael]

The last time I experienced this problem was waay in closed beta. And now, with the 2 latest patches, it's back. It happens every 4-5 matches from what I have seen. At least they are aware of this issue.

[Kuks Kublaa]

Seriously...I don`t know of any other game where a player can BE HAPPY when actually FINISHING THE GAME. Freezes and crashes 70% of the time , really?? All your mech adding/weapon balancing/etc is at a MOOT POINT if I can`t PLAY the %$#%$# game. A person would think this to be at the highest priority and an essential issue to fix ,....but NOOOO - getting crashes since I started playing. I`m really #$&/# ***$%#/$/**

Edited by Kuks Kublaa, 22 July 2013 - 03:53 AM.

[SlyDrJ]

This kindda crap is why i haven't played for months.

I finally update and find this new treat.....

[Deathlike]

The best solution (at least for me) is to lower the texture slider, until this stops occurring. Trying to run very high causes it to occur more frequently... so now it is set to medium and it doesn't (if ever) occurs.

There's something odd about how the game attempts to allocate memory.

[mack sabbath]

Kuks Kublaa, on 22 July 2013 - 03:52 AM, said:

Seriously...I don`t know of any other game where a player can BE HAPPY when actually FINISHING THE GAME. Freezes and crashes 70% of the time , really?? All your mech adding/weapon balancing/etc is at a MOOT POINT if I can`t PLAY the %$#%$# game. A person would think this to be at the highest priority and an essential issue to fix ,....but NOOOO - getting crashes since I started playing. I`m really #$&/# ***$%#/$/**

Same, and after numerous help tickets, they won't even restore any of my paid premium time that is being shat away.

Great PR work, PGI.

[Jhon Nova Clase]

I having problems with this new patch... i press play in the loader and it just sits there saying please wait...?

[Airborne Thunder]

Whenever a new patch comes out I usually just uninstall the whole game and do a fresh reinstall. It seems to keep the crash away for a little while at least. It actually takes less time to just reinstall then it does to let the patcher work. You guys might try it.

[Vasces Diablo]

Medium settings: Never happens.
The moment I move some sliders to higher settings: Happens almost instantly.

I have a i5 Ivy bridge proc and a HD7770 GPU. I am still running XP however.

Edit: the repair tool did not remedy the issue.

Edited by Vasces Diablo, 07 August 2013 - 06:38 AM.

[Vargo Nash]

I now have the problem after todays patch, too.

Happens every third to second match I think. Running windows 7 32 with Intel Q9450 and Radeon HD 5700. Graphic settings on high. Never had that error until today with the new patch.

[Raikael]

Texturing above medium will cause this error almost every time. Medium and below, I don't receive the error.

Win 7 Ultimate 32bit
4GB Ram
AMD X2 5600+
Nvidia GTX560 Ti 1GB

[javierucho]

creo q no se ve la imagen de los errores...error images...file:///C:WindowsTempmsohtml11clip_image001.png

Edited by javierucho, 09 August 2013 - 07:54 AM.

[Ilkahn]

hell i cant even get game to boot up half the time rest its crashing

[javierucho]

Raikael, on 08 August 2013 - 02:02 PM, said:

Texturing above medium will cause this error almost every time. Medium and below, I don't receive the error.

Win 7 Ultimate 32bit
4GB Ram
AMD X2 5600+
Nvidia GTX560 Ti 1GB

yes...it works...but why i cannot play whit high texture???

[Storm Wraith]

I ran the Fixer because I was annoyed with my Chat not working, and crashing at the end of matches. Now I crash at the very beginning of the match. So I guess I am becoming... more efficient? Maybe a full re-install is in order... (shudder).

StormWraith, Feudal Sakkran Researcher
and inventor of "Battlemech Bungee Jousting".

Oh, I should have mentioned - in my case I am using the very LOWEST of Settings... so there isn;t anything lower to go, unless someone wants to make a MineCraft version for me to try out...

[Shifty Eyes]

I just got this error for the first time on an epic game. Really sucked that it had to end that way. I'm using lowest settings. Game started locking, then it crashed with the error message.