144 replies to this topic

[Fantastic Ergo]

I am not experiencing this issue myself, but some of the people I have spoken to who have this issue are running a 32bit OS. Or not running enough Virtual Memory, Like the users that shut down virtual memory because they are running an SSD. This is an issue on how cryengine addresses memory even back on crye2.

For 64bit users, check your virtual memory settings and make sure the size is managed by windows, or raise the maximum to a higher size if you wan to leave static sizes. I let windows manage it myself since w7 does a good job keeping the drives from fragmenting.

For 32 bit users, there is a workaround but it may have adverse effects so b careful to leave the original line and add the line as indicated in this steps..

Windows support a switch option in BOOT.INI called the /3GB switch, which adjusts the way memory is allocated between the user and the operating system. By default, the split is fifty-fifty -- up to two gigabytes for the user and two for the operating system. The /3GB switch option sets those limits at three gigs maximum for the user and one gig for the operating system.

As the name implies, /3GB was originally meant to be used in systems that have 3 GB or more of RAM -- something that is no longer quite as rare as it used to be! However, even if you don't have 3 GB or more of memory, you can still use the /3GB switch successfully if you are running memory-hungry desktop applications. Photoshop, for instance, is infamous for staking out as much RAM as it can. With /3GB enabled, there's that much more memory that the application can use.

To add the /3GB switch as a separate boot option:

1-In My Computer | Properties | Advanced | Startup and Recovery, click Settings.





2-Click the Edit button under System Startup to edit the BOOT.INI file.


3-Find the current boot entry, which typically looks like this:

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect


4-Copy the line on step 3, from your own BOOT.INI not from this post, and paste it at the end of the BOOT.INI file as a second entry, and change the description and add the /3GB flag, something like this:

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional 3GB Switch" /fastdetect /3GB
This lets you choose between a conventional boot entry and the /3GB boot entry. If something goes wrong when you use /3GB, you can always boot back into the original configuration.

5-Save and close BOOT.INI.

6-Click OK to close the Startup and Recovery panel.

7-Click Settings again, and in the "Default operating systems:" dropdown, choose the newly created boot entry with the /3GB switch.

8-Click OK to close everything. Reboot into the new profile.

Hope this helps someone

Ergo

Edited by Fantastic Ergo, 20 February 2014 - 08:21 PM.

[Arnold Carns]

Kahles, on 18 February 2014 - 05:19 AM, said:

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.

From my point of view it's a glitch in the code for memory menagement of the CryEngine3 that got implemented when they added the "River City" map back in the Closed Beta days. Something that tries to allocate data into the memory area that's reserved for Windows once the available memory runs out instead of using virtual memory. And because Win don't let it do that the Game crashes. After I got that nagging error for dozens in a row I started to watch the Resource Monitor. Everytime MW:O crashed there was absolutely no increasement in virtual memory usage. I wrote a lengthy article about how to circumvent this, but unfortunately the thread got buried due to the regularly reincarnation of the forums after every update. That's the reason I didn't and won't write that one again.

[Lobokai]

Typical of the IGP staff. Break things without testing, then hot fix the problem that we aren't having. Come on! People are paying for premium time and then the lack of fix on this memory allocation error is making that time wasted. You're going to start driving people away IGP. Fix the game that you broke after taking people's money instead of throwing the Clans out early for crying out loud.

[Gator809]

Game was crashing 3 out of 5 times in a match. I ran the repair tool. Now it crashes at the beginning if each match. I've uninstalled and reinstalled to no avail.

Thanks PGI

[Igchy]

Fantastic Ergo, on 20 February 2014 - 07:23 PM, said:

For 32 bit users, there is a workaround but it may have adverse effects so b careful to leave the original line and add the line as indicated in this steps..

Windows support a switch option in BOOT.INI called the /3GB switch, which adjusts the way memory is allocated between the user and the operating system. By default, the split is fifty-fifty -- up to two gigabytes for the user and two for the operating system. The /3GB switch option sets those limits at three gigs maximum for the user and one gig for the operating system.

As the name implies, /3GB was originally meant to be used in systems that have 3 GB or more of RAM -- something that is no longer quite as rare as it used to be! However, even if you don't have 3 GB or more of memory, you can still use the /3GB switch successfully if you are running memory-hungry desktop applications. Photoshop, for instance, is infamous for staking out as much RAM as it can. With /3GB enabled, there's that much more memory that the application can use.

To add the /3GB switch as a separate boot option:

1-In My Computer | Properties | Advanced | Startup and Recovery, click Settings.






2-Click the Edit button under System Startup to edit the BOOT.INI file.


3-Find the current boot entry, which typically looks like this:

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect


4-Copy the line on step 3, from your own BOOT.INI not from this post, and paste it at the end of the BOOT.INI file as a second entry, and change the description and add the /3GB flag, something like this:

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional 3GB Switch" /fastdetect /3GB
This lets you choose between a conventional boot entry and the /3GB boot entry. If something goes wrong when you use /3GB, you can always boot back into the original configuration.

5-Save and close BOOT.INI.

6-Click OK to close the Startup and Recovery panel.

7-Click Settings again, and in the "Default operating systems:" dropdown, choose the newly created boot entry with the /3GB switch.

8-Click OK to close everything. Reboot into the new profile.

Hope this helps someone

Ergo

This works for me i'm using 32 bit Thank u very much

[str0be]

Running Win7 32bit and i couldn't do the instructions above. I tried the "bcdedit /set IncreaseUserVa 3072" and have been able to play 3 games in a row without the error. I'll try more testing later. I'm hopefull.

[Naclador]

Vasces Diablo, on 06 August 2013 - 07:50 PM, said:

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.

It is not an OS issue, I am experiencing this problem on Win 8.1 as well. I am too using a HD7770, but just an old Phenom II X4 920 CPU. The repair tool did precisely nothing for me.

It is possible that on a 64 bit system with, say, 16 Gigs of RAM the problem becomes unnoticeable, but I am not willing to compensate for shoddy programming by buffing my hardware. Also, the game ran fine before the latest patch.

[Phantom02]

Same thing here. First I couldn't play at all I would start client to install patches(7 needed to be installed). But it kept closing itself out. Tried the repair tool. Was able to update my patches. Got 5 games out, just enough to complete the challenge thank goodness, then the cry engine error started happening. I can do the training ground but I can't play online if u know what I mean. This needs to be fix.

[martino2k6]

I managed to decrease the occurrence of this error by setting all my graphic settings to low, changing to native resolution, and fullscreen. It seemed to have been worse when I was running at non-native and switching between windowed/fullscreen with Alt+Enter.

I also emailed support an apparently they're looking into... but who knows when the fix will come around. Memory leaks are some of the most annoying bugs to fix.

[Dramborleg]

Happens very frequently for me in 32bit windows 7, even on lowest settings. With all settings on lowest except object detail and texture detail (both medium), it actually happens roughly 1/4 of the time. I understand that I'm limiting myself to 4gb of memory, but this game was advertised as running on that minimum, and I do expect it to run. Have run the repair tool and nothing happened.

Edited by Dramborleg, 28 February 2014 - 05:26 PM.

[str0be]

Dramborleg, on 28 February 2014 - 05:25 PM, said:

Happens very frequently for me in 32bit windows 7, even on lowest settings. With all settings on lowest except object detail and texture detail (both medium), it actually happens roughly 1/4 of the time. I understand that I'm limiting myself to 4gb of memory, but this game was advertised as running on that minimum, and I do expect it to run. Have run the repair tool and nothing happened.

Have you tried the 3gb switch?

str0be, on 25 February 2014 - 03:55 PM, said:

Running Win7 32bit and i couldn't do the instructions above. I tried the "bcdedit /set IncreaseUserVa 3072" and have been able to play 3 games in a row without the error. I'll try more testing later. I'm hopefull.

I was able to get in 4 games at max settings except for texture at high and it gave me the error. I decreased texture to medium and the rest of the settings to High and rarely have the issue now. I don't think it solved it, but, it has helped A LOT.

[Jaricho]

Getting Memory Allocation Error's since February 4th's UI 2.0h-0h
I run Win7 32bit OS

Have tried : running with AV shutoff / deleting shaders folder / running graphics at low / complete uninstall and reinstall / use of repair tool (6 times) / changing Win page file sizes and management -- all to no avail for the past 26 days.

All that's required to repeat this problem is simply log on and try to play.

Crashes happen as often as every other map or as infrequently as a dozen maps before *error*
Is impossible to see a trend except most crashes happen with Terra Therma map.
Sometimes crash happens in the middle of match but mostly at map load screen.

It is having a detrimental effect on my guildplay as I can't be depended upon to drop successfully.

-------------------------------------------

If it has been a known issue for 10 months why hasn't it been addressed yet?

When are those of us who do not wish to upgrade to Win 64bit going to be helped with this bug?

Why didn't you state in the game requirements that a 32bit OS would not be sufficient?

Just how much do I have to pay you to fix this?

I feel these are valid questions and would appreciate a response in the form of answers.

Edited by Jaricho, 01 March 2014 - 11:46 PM.

[Kalidane]

Rebuilt machine with SSD and Windows 8.1 64 bit. Solved this problem.

The biggest problem now is disconnecting during play or even after death.

A fun one is that it seems that if you die, are then disconnected, and blue team wins, it uses your 2x XP for first win of the day but you get no cash and no XP. Neat feature.

Oh yeah chat doesn't work most times now and I usually can't spectate after death. The button just ain't there.

Not sure if this is my definition of 'premium time'

[martino2k6]

Jaricho, on 01 March 2014 - 11:46 PM, said:

Why didn't you state in the game requirements that a 32bit OS would not be sufficient?

Don't get your hopes us, as 64-bit may not solve the problem. It's a memory leak and/or bad memory allocation in the MWO client, something only PGI can fix.

[Revengex]

I have run game fix, gotten new memory, vid card, and updated drivers, run this on win 7 and win 8.1, 32 and 64 bit. Read read and read forums. I have changed the settings. Performed a small animal sacrifice.

My conclusion is that this is happening to many customers but the fault and repair is in the hands of PGI. If its not fixed, its their fault. Can’t fix low performance by the developers if they don’t care enough to fix this.

[KKillian]

After crashing at a cruicial moment in a match a few days ago I took some time off, woke up today decided to give it a go. Mind you since early closed beta crash issues were solved for me I had no problems until UI 2.0 came to pass, now I crash up to 50% of the time yet today im 3/3 crashing starting matchs. As soon as the map loads "memory allocation error".

I run Win 7 64bit with a quad 3.4 phenom2, 16gb ram and a HD 7950 3gb radeon with all settings max, entire system runs under 120F and I never had any issues with framerate or desync or latency, the only problem is an outright crash when loading a map.

This is a HUGE game breaker for many people and not refunding their lost premium time while the game is unplayable for so many is a seriously insulting situation with how expensive the "micro" transactions in this game are. If you are going to charge upper eschelon prices, we demand programming quality.
While I myself am asking for no compensation, I see 1-2 disconnects EVERY match these days, these are numbers we saw in early beta, these numbers during live are unacceptable.

I also notice no difference in quality with DX11 other than frame loss and lag so after a few matchs I reverted to dx9. My system is more than powerful enough to handle any game on the market at the moment, yet swapping MWO into dx11 causes lag like this machine has never seen before. These crash issues popped up around the same time dx11 was introduced although I have had no luck clearing them up reverting to dx9 and they happen just as frequently in either mode.

[LowSubmarino]

It is weird but I never ever had this kind of error which just crashes the game and every thrid time the entire os so nothing works, not even task manager only a reset.

I never had this in any other game before and before the latest patch I have been one of those lucky guys that almost never crashed or disconnected.

Since latest patch it happens roughly every third game. Since it is not good for my computer to crash so often and to reset it I have stopped playing for now until they fix this.

Too bad. But in 10 games it happend 4 or 5 times. I don't know what they did with this memory allocation business but they definitely messed something up.

As I said I never had this before only since latest patch.... :-(

[LowSubmarino]

KKillian, on 15 March 2014 - 08:11 AM, said:

After crashing at a cruicial moment in a match a few days ago I took some time off, woke up today decided to give it a go. Mind you since early closed beta crash issues were solved for me I had no problems until UI 2.0 came to pass, now I crash up to 50% of the time yet today im 3/3 crashing starting matchs. As soon as the map loads "memory allocation error".

I run Win 7 64bit with a quad 3.4 phenom2, 16gb ram and a HD 7950 3gb radeon with all settings max, entire system runs under 120F and I never had any issues with framerate or desync or latency, the only problem is an outright crash when loading a map.

This is a HUGE game breaker for many people and not refunding their lost premium time while the game is unplayable for so many is a seriously insulting situation with how expensive the "micro" transactions in this game are. If you are going to charge upper eschelon prices, we demand programming quality.
While I myself am asking for no compensation, I see 1-2 disconnects EVERY match these days, these are numbers we saw in early beta, these numbers during live are unacceptable.

I also notice no difference in quality with DX11 other than frame loss and lag so after a few matchs I reverted to dx9. My system is more than powerful enough to handle any game on the market at the moment, yet swapping MWO into dx11 causes lag like this machine has never seen before. These crash issues popped up around the same time dx11 was introduced although I have had no luck clearing them up reverting to dx9 and they happen just as frequently in either mode.

It is also weird because you have a very strong system whereas I run it on minimum settings where it is smooth but I run it on win xp, 2 gb, 250 gts. So my ancient system and your high end system both have this same error. Somebody said it can be prevented by reducing video settings such as details and what not but that clearly isnt a solution.

[LowSubmarino]

It would be great if we could get an announcment concerning the time frame. Like if there will be a hotfix today or tomorrow or if I have to wait much longer cause then I won't check the forum so often.

[FIRESTORM91]

The issue arises when the game attempts to allocate memory in a location that is write protected (like the current run-time of your OS) or when it tries to allocate a chunk of memory larger than you physically have. The last I knew (I could be wrong) Windows 7 uses a little under half a gigabyte of RAM just to turn on. So those running 32-bit systems can only address up to 4 GB of RAM without serious adverse effects. Now that the game has been updated to have 12-players per team and with larger, more complex, maps the amount of RAM needed to play increases quite a bit. So those running lower spec machines are taxed even further which increases the chance of a memory allocation failure. Memory leaks may be a cause, but I haven't personally noticed anything. What to get out of what I said, is you either push most of your settings to minimums or look for a workaround. Lastly, you just may need to simply upgrade. Harsh, I know, but sometimes it has to be done. My machine only has 6 GB of RAM, a GTX 660 and an AMD Phenom II, and I rarely have crashing issues. Don't get me wrong occasionally something pops up, but I've never had a memory allocation failure. As for KKillian you may be experienceing a driver, or some other problem, related to your AMD video card. The game does seem to have Nvidia features under development first and foremost. I could be totally wrong in saying this but I hope my explanation helps shed some light on the possible cause for this.