Edited by TAMgames, 01 November 2013 - 01:51 AM.
![](https://static.mwomercs.com/forums//public/style_images/master/icon_users.png)
![](https://static.mwomercs.com/img/house/lonewolf.png)
Crash Receiving Memory Allocation Error
#61
Posted 01 November 2013 - 01:50 AM
#62
Posted 01 November 2013 - 06:21 AM
#63
Posted 10 November 2013 - 01:47 PM
1) Uninstall MWO
2) Make sure all files relating to (search): MWO, MechWarrior Online, PGI, and/or Piranha are gone
3) Make sure your registry is also clean of anything related to the above search terms
4) Download and attempt to use the latest version of the installer
5) If it tries to get you to uninstall, or gives you an installation error, such as the Piranha Games directory is still there
6) Run Microsoft's Fix-It , using Other. It will go through and try to figure out what might be wrong, and you should select Problem Uninstalling Game. It will generate a list of games, select MechWarrior Online, Next, and watch it go
7) Run you system tools -Disk Cleanup, Defrag, and ScanDisk
8) Try to reinstall the game
9) Have fun once you're back to stompy 'Mech-killin' action.
I have not had one single problem since I reinstalled this morning, and I think it was the fact I was still running with Beta software installed, even if it wasn't being used by anything, my registry had all sorts of bad information in it, and I still had old file folders and what-not.
Give this a try and, if it doesn't work, it's something else.
Edited by Kay Wolf, 22 November 2013 - 10:05 AM.
#64
Posted 16 November 2013 - 12:24 PM
#65
Posted 16 November 2013 - 04:04 PM
#66
Posted 17 November 2013 - 10:14 AM
My only next step is to build a new rig, I only hope it isn't some weird router issue. (and I can't afford a new rig.)
#67
Posted 22 November 2013 - 02:19 AM
#68
Posted 22 November 2013 - 10:05 AM
Edited by Kay Wolf, 22 November 2013 - 10:08 AM.
#69
Posted 23 November 2013 - 05:57 PM
#70
Posted 30 November 2013 - 07:28 AM
If you are getting this crash and are using Vista / Win7 32bit, this is a known issue with CryEngine (or with Windows, depending on who you want to blame). Without going into detail, the short version is that if you have 4+ GB of RAM, the OS can't address all of it. This makes the CryEngine sad.
The real fix is moving to a 64-bit version of the OS. The stopgap fix that worked for me is to a) drop graphics detail to medium (you can play with this, obviously, as there are other factors here) and run the following from a command prompt (prompt must be running as administrator):
bcdedit /set increaseuserva 3072
Restart the computer after running this command. What this does is increase the amount of memory that Windows will use for a given application. With that limit raised, CryEngine shouldn't run out of usable memory and {Scrap} out on you.
**HOWEVER** this fix can have other, detrimental effects. Because an application can use more memory, the OS kernel is getting squeezed into a smaller space and can run over into virtual memory. This result in long "pausies" while the machine grinds through your hard drive and, in my case, seemed to increase load times for a lot of things. Additionally, you're going to notice a lot more hard disk swapping in virtual memory, which can shorten the life of your hard drive. So I wouldn't recommend doing this long term.
To change the value back to default, run the above command except set the value to 2048 and, again, restart.
Hope this helps some people, it definitely kept the game playable for me.
#71
Posted 30 November 2013 - 08:29 PM
#72
Posted 30 November 2013 - 10:26 PM
Take care, friends. o7
#73
Posted 25 December 2013 - 09:22 AM
#74
Posted 19 January 2014 - 03:05 PM
[color=#959595]I first "clean system cache" (Button) before i launch a new game works works fine!!!!!!!!!!! [/color]
#75
Posted 19 January 2014 - 03:08 PM
I first "clean system cache" (Button) before i launch a new game works works fine!!!!!!!!!!!
![Posted Image](http://ttcshelbyville.files.wordpress.com/2010/07/memory-cleaner-after.jpg?w=640)
please like.
![;)](https://static.mwomercs.com/forums/public/style_emoticons/default/wink.png)
Edited by Sjef, 19 January 2014 - 03:20 PM.
#76
Posted 23 January 2014 - 08:40 AM
All settings are low, so no options there. The only guess I have, is the cockpit reflection, similar to the damage glow effect that had to be changed to option out, especially with 12 v 12 matches. I have tried in an atlas, and my YLW, to see if "speed" has an affect and both still give the same response.
Granted I have a HD 4650 vid card, not a high end by any means, but a solid card that has worked well to this point.
Any suggestions would be greatly appreciated, other than the sterotypical, buy a new card.
Edit >>>>>
Okay, after memory cleaner, uninstall, reg clean, etc, and much graphic tweaking.. it is working great again. Thanks to everyone who offered suggestions on fixes.
Edited by DarcStormm, 23 January 2014 - 01:55 PM.
#77
Posted 01 February 2014 - 04:20 PM
every thing did run smoothly on a 32 bit.
this is a returning problem guys please fix it because you start to look as the first class noob programers of the v2p world.
![:angry:](https://static.mwomercs.com/forums/public/style_emoticons/default/sad.png)
![:angry:](https://static.mwomercs.com/forums/public/style_emoticons/default/sad.png)
![:(](https://static.mwomercs.com/forums/public/style_emoticons/default/sad.png)
![:(](https://static.mwomercs.com/forums/public/style_emoticons/default/sad.png)
![:(](https://static.mwomercs.com/forums/public/style_emoticons/default/sad.png)
#78
Posted 04 February 2014 - 02:38 PM
#79
Posted 04 February 2014 - 04:14 PM
#80
Posted 05 February 2014 - 07:23 AM
6 user(s) are reading this topic
0 members, 6 guests, 0 anonymous users