39 replies to this topic

[leptoon]

When I try to launch the game, I get the error "Memory allocation at *insert long random number* failed!". I get two of those errors with different numbers and the game crashes. This happens every time I am loaded into a map. I have four gigs of available RAM and a 2 GB discrete video card so I'm not sure what the problem is... Thanks for any assistance.

[Rifter]

Try to reinstall the game, i have had similar issues in beta and it always traced back to corrupt map data.

[leptoon]

I just watched the memory usage during loading and as soon as Free Memory gets to zero, the memory allocation error occurs. No cached RAM is reallocated (like it should) and there's usually over 1400 megs of it.

[The Gunman]

leptoon, on 29 October 2012 - 10:17 PM, said:

... I have four gigs of available RAM ...

What do you mean by "available RAM"?

Secondly, what operating system are you using? And is it 32-bit or 64-bit?

[leptoon]

The Gunman, on 29 October 2012 - 11:10 PM, said:

What do you mean by "available RAM"?

Secondly, what operating system are you using? And is it 32-bit or 64-bit?

I have eight gigs of memory but I'm running Windows 7 32 bit so I can only use four gigs, hence I have four gigs of available RAM.

This isn't the only game I run out of memory with. My system cache never releases, so when my free memory is used up, the game crashes. Is there a way I can disable system ram caching?

Edited by leptoon, 29 October 2012 - 11:43 PM.

[leptoon]

Any suggestions?

[Belorion]

I would upgrade to 64bit if that option is available to you.

[Rifter]

Upgrade to 64 bit, it will solve your issue. Worked for lots of people in the closed beta.

[jimb0nes]

I get the same error everytime a few minutes into the game

i have only 2gb ram and 32bit win 7. are there any other known fixes apart from upgrading my pc?

[Rifter]

jimb0nes, on 30 October 2012 - 02:52 AM, said:

I get the same error everytime a few minutes into the game

i have only 2gb ram and 32bit win 7. are there any other known fixes apart from upgrading my pc?

Wait for PGI to fix their leaky programming i guess is the only other option.

[Deiphobus]

I had this problem tune down the graphics then it should be able to handle the data transfer rate

[Mister Blastman]

Welcome to the freeze frame graphics pause bug! Welcome to hell!

I have this bug... and support has said before... oh, that's fixed next patch... only to not be fixed.

Rivercity is unplayable due to this bug.

Rifter, on 30 October 2012 - 02:48 AM, said:

Upgrade to 64 bit, it will solve your issue. Worked for lots of people in the closed beta.

Nope. Not for me! 64-bit Win 7 here and the problem ruins the game.

[Carl Wrede]

This problem is most likely linked to the 4FPS bug.

[Mister Blastman]

I can confirm that it is. Some people get heavy disk access and freeze-framing and others get 4 fps depending on hardware.

[LogicSol]

Upgrade to 64-bit.

Your problem is you are running a 2GB video card on a 32-bit system.
This means you don't have 4GB available memory, your actually only have 2GB.

A 32-bit system can only allocate 4GB RAM TOTAL, over every component in the system.

[Name48928]

A memory allocation error occurs when two programs are trying to use the same memory address. You may have a program loaded (such as anti-virus, desktop widget, etc etc) that requires the same address as part of MWO. Sounds like PGI is aware of it though and they will probably be removing the hard-coded address requirement from their code.

Assuming that's the problem.

Edited by MinionJoe, 30 October 2012 - 11:37 AM.

[LogicSol]

Yea, there are two problems, one is the shared allocation issue 64-bit gamers run into. That ones a bug.
The other is trying to run the game with 2GB of addressable RAM. That's a 32-bit limitation.

[Matthew Kidomen]

[Perf] Ok, same issue "Cryengine Error: Memory allocation for 11141848 bytes failed" I am running an Intel Quad core Q6600 @ 2.40 GHz
4 GB of ram
Windows Vista Home Premium 32 bit.

I didn't have this issue too much in closed beta, but I have started running C3, (although I haven't found anyone to talk to while playing).

I am going to try two things. 1) turn off C3 and 2) cut back on the graphics level. I will let you know the results

[Matthew Kidomen]

[Perf]
After turning off C3, and reducing almost all graphics levels to "medium"

I was able to play 3 matches in a row with out any crash to "Memory allocation....." So now I am going to try to run C3 again, since I believe communication is more important than better graphics. (Some day I am going to have to figure out how to actually talk to some one else playing, but that is a different issue.) If that works, then I am going to start to increase graphics levels on individual items. See if there is a certain setting that effects crashes more than others.

[Matthew Kidomen]

[Perf] Ok now I have turned on C3 and it is working just fine. So now I am going to start to cranking up graphics. Wonder which graphic feature will have the most image improvement? Or are there graphics features that work together? Anyway I will tell you what I increase and the results.