144 replies to this topic

[McQueen]

I am also having this problem. The weird thing for me is that I can finish the match after the error message pops up. I just have to live with the error message window being in the center of my screen. I lose my HUD but everything else seems fine. if I click on the OK button to acknowledge the error I crash to desktop.

[Dino1a]

In my case I can't even log in. and if i am lucky enough to get into the mechlab when I try to change settings I crash as soon as I hit save. Sent email to support just waiting to see what they say.
P.S.
Repair tool did not work at all

[The Incredible Microbe]

Haven't got an answer on my request for refunding premium-tim yet... and I think I won't get it back anyway... this is really annoying, as i PAYED MONEY for this. 2 weeks Premium shot in the sand...

[valt901]

I can't even play this game anymore. What's worse is i don't really care. I don't want to play with others because i know i will crash thus depriving my team of an extra player. Can't play by myself because i crash now every other game. In fact i crash more now that i have run the repair tool than i did before. If PGI can't fix the problem i will excuse myself and spend my money elsewhere. I'll come back eventually when they get it fixed but now this is just a waste of time.

[Pharcyide]

Experiencing same memory allocation error on an older machine running Win XP. Upgrade to Win 7 ultimate 64-bit and took care of the issue. My guest would receive the error every time he tried to drop. Upgrading the o/s resolved the issue.

I'm guessing the issue lies with machines running close to the min specs or machines running 32 bit o/s.

Edited by Pharcyide, 11 February 2014 - 06:30 AM.

[Elric Tchernovkov]

As I stated in previous posts to this thread, I could not get through 3 entire matches without this error occurring. I tried the first solution I told you I was going to do by upgrading my OS to 64 bit. Finally completed the download of the game this morning, Tue Feb. 11, and immediately jumped into the game. I played 5 matches straight with no error. I believe I have resolved this issue for myself anyways. For anyone else experiencing this issue I recommend getting a copy of Windows 8. Even after you install it will create a folder labeled Windows.old everything you had on your HD before the install will be saved to this folder. However MWO will not run from this folder. I did not try to move it out, just reinstalled the game again. Hopefully this will help you guys.

[Napoleon_Blownapart]

i end up having to install 13.1 drivers from jan 2013 to crash less.

[Jakspanky]

not sure if it is this problem but every match i am crashing out

[str0be]

I have tried nearly every video setting combo i can think of and still only get a max 2 games in before crashing. Most of the time, i'm lucky if i get to onto the dropzone. I've reinstalled 20ish times, run the repair tool 2-3 times per installation, and manually deleted the shaders folder. Still, memory allocation error.

Even though Microsoft gave up on Mechwarrior, I'm starting to think MS has got its hands in here somewhere. This ongoing and seemingly "unfixable" error is benifiting them by MWO nearly requiring a 64bit OS. We buy/upgrade 64bit OS, Microsoft gets more money. I think i'll just reinstall MW:4. Strangly, piloting seemed more realistic on that game anyways. I just really missed the online function.

Maybe if this gets fixed, i'll try it again. For now, it seems, the majority of 32bit OS users are SOL.

[Greimouserii]

I am running a win 8 alienware, 12gb ram, 3gb video, less then 6 monthe old bought new(i can get the exact specs but why)
this never happened before the last patch and hot fix, it seem it is another fine example of a game fixing something not really broke and screwing the pooch to hell

[Phelans Ghost]

I'm having the same issue, and the only work around that's been proven to work for me is after each battle I have to exit out of the game completely and then go back in. It takes an extra minute but it beats getting your mech stuck in a game for 20 minutes.

My system is WinXP 32bit.
Video is Asus EAH6570 series
Game visuals is set to medium
8gb ram (system doesn't see all 8 until I upgrade to Win7)
I also run in Windowed mode

Ran repair tool, didn't help. Reinstalled the game and that didn't help.
I would get the memory allocation crash every 2-3 battles before I started using this workaround.

Hope that helps some people. It's definitely frustrating!

[Kahles]

Arnold Carns, on 23 June 2013 - 12:22 PM, said:

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.

I just went from XP 32 to 7 64 bit. Don't think I've seen this crash since. Saw it at least once a night before.

[Husker Adama]

All my guildmates had the problem after the today's patch.

Only experienced in group : it's the group leader who lunch the game, who crash.

[str0be]

ah man. i was able to get in a game or two max before the patch. Now, i barely get past drop first game. They are making this worse.

[Kalidane]

Unable to play since patch/hotfix.

Can run around testing ground no issue and mechlab is fine.

Heading to a game and it gets to the splash screen for the map and the progress bar fills all the way then the memory allocation error.

I've deleted shader cache and run the repair tool to no avail.

[str0be]

When i can play some of the most demanding games with my Win7 32bit machine with max settings (Crysis series and F.E.A.R series) with zero issues, it is sad that i can't even play this with all settings to "low" without a memory error. Yet, they hope you will pay money to buy a few 'mechs that will cost as much as a normal game would. Not while they can't fix such a massive flaw.

Everytime i drop i feel bad for the team that is now a man short.

[Igchy]

Any update on fixing this,its gets really worse after ui2.0 and 18 feb patch.

(have try : preset to low / reinstall / repair tool / memboost program / create user.cfg file..... nothing works)

[martino2k6]

Getting this error nearly every game now, extremely infuriating.

[Lobokai]

Get this all the time. Driving me nuts

[Kalidane]

Switching to 'Low' graphics and windowed allowed me to play 5 games before the problem returned.

Now I just play 4 games then quit, clear shader cache just in case, and repeat. So far that has worked fine.

I still feel bad for all the blue teams missing a guy every time I had this problem...