#0 - Oct. 25, 2010, 8:44 p.m.
If you get the following crash report saying that you run out of storage space, then here is the fix for it :D
Q u o t e:
This application has encountered a critical error:
Not enough storage is available to process this command.
Program: C:\Program Files (x86)\World of Warcraft\Wow.exe
File: .\MapMem.cpp
Line: 517
Requested 1919248 bytes of memory
And to no tanks to Blizzard, i found out my self how to fix it, and i dont even know sh*t about programing >_<
I just found a program that will set the ''/LARGEADDRESSAWARE'' flag for you, and bin successfully trying it out till now, whit all video settings to max!.
Till now it has bin working great (have come up to 2.327.117KB=2.2GB that over 2.097.152KB=2GB limmit)
Do have not tested it out on Wednesday ore Sunday late.
Here you can find the program http://forums.techpowerup.com/showthread.php?t=112556
you need at least 3GB memory
(otherwise windows will use the swap-file as memory and will stall the program as if it was crashed)
If you running a 32 bit Windows then you need to do some changes to your Windows settings.
(read the instructions on the page!!!!)
If you running a 64 bit Windows then you need to do noting just run the program and set the flag.
So this solution should fixes all the problems
Also let me know if its working ore not, i would like to know, so leave a post behind, specially let me know if you have a Windows 32bit version.
If you have problems, i will have a check at it then, and see if i can find out ware the problem is.
tho i need to know Windows version XP/Vista/7, 32/64bit, CPU type, and memory amount.
If you dont know what you got run the program down here, and copy / paste all the info.
http://www.filehippo.com/download_speccy
Anyway, have fun running crash free!!!!!
And for anyone that is worried about being banned for modifying the WoW.EXE, according to a GM, this will not result in to a ban of your account, so no worries.
See here screen-dump from the GM response
http://tweakers.net/ext/f/oBvZbwcdTSf56VTi3SGJCBwN/full.png
<End update>
_________________________________________________________________________________
<Original post>
WoW crashes now all the time after the 4.0.1 patch
This is a problem for all players that uses +4 mega pixel display like 30" 2560 x 1600, ore even worse like me whit a 7 mega pixel Eyefinty setup 5760 x 1200 like i have.
Before 4.0.1 it was all ready bad, but after 4.0.1 patch it got real bad, crashing all the time now
When is Blizzard gone make a WoW64.EXE ore at least make it ''/LARGEADDRESSAWARE''
And all the blue post on this subject are more ore less useless as the only diminishes the problem not fixing it , and now after the bug infested 4.0.1 i cant be in Dalaran anymore when there are a lot of people there >_<
As i done a clean install whit no AddOns, i still have crashes do less ofc then whit the addons
The guy that post on the US forum explains the problem well, AND THAT WAS A YEAR AND A HALF AGO !!!!!!!!!!
http://forums.worldofwarcraft.com/thread.html?sid=1&topicId=14133415207
Q u o t e:
Since the cause of the 100 or so of these errors I've reported hasn't been fixed, I did a little investigation of my own.
To preface this, my day job is assembly-level reverse-engineering and OS-level development on both Windows and Linux. I know volume 3 of the Intel reference manuals like the back of my hand. I have over 8 years experience in this area and work on a project which, among many other things, in 2001 developed (and coined the term) ASLR (Address Space Layout Randomization) which is now used in Vista, Mac OS X, Linux, and OpenBSD.
Some notes about my system:
Vista X64 SP1
Running at 2560x1600 in maximized window mode
All effects set to "High"
6GB RAM, 8GB pagefile
Some things that do not solve the problem:
Clearing the cache/WTF/WDB
Running the repair tool
Disabling all addons (though disabling addons can make the problem take longer to appear purely due to the fact that the addons use up memory, and this is a memory-related issue)
REMOVING all addons
If you've seen this error, here's what it looks like:
This application has encountered a critical error:
Not enough storage is available to process this command.
Program: C:\Program Files (x86)\World of Warcraft\Wow.exe
File: .\MapMem.cpp
Line: 517
Requested 1949222 bytes of memory
It generally happens in-flight or sometimes in Dalaran when heavily populated (both cases make memory usage shoot up).
I'll reply to this post with an error log demonstrating the bug with all addons disabled.
There are a number of posts in these forums with misinformation about this bug. First, it's not a disk space issue (I presume the "not enough storage" message comes from an ambiguous error code -> string conversion within WoW). So freeing up disk space, as suggested in several posts, is completely irrelevant to this bug.
I've been monitoring my WoW process, particularly paying attention to the commit size column, and noticed before the crashes that it was around 1.7GB. Note that this isn't an exact measure of the amount of virtual address space in use by WoW, since virtual allocations can be either in a non-committed (reserved) or committed state. AFAIK it's not possible to get a view of WoW's actual address space without violating the AUP/EULA, so I have not done so. However, I imagine the problem is this:
The commit size + reserved size (some of the reserved ranges won't be available for heap/mmap allocations from WoW) + address space fragmentation is causing a situation where there's no place for the ~2MB attempted allocation to go, causing it to fail and producing the error above. The WoW binary is not large address aware, so even on 64bit OSes (or systems with the /3GB boot time option) it is restricted to a 2GB userland virtual address space. It's not possible to modify the WoW binary (say with editbin.exe /LARGEADDRESSAWARE) to enable this support, as some game verification performed at login time includes the PE header in its hash calculations.
So, we need Blizzard to acknowledge this problem and either enable large address awareness, or perform some cache trimming at these locations where they fail on virtual address space exhaustion. Physical memory isn't at issue here: only 3GB of my 6GB of physical memory was in use at the time of the crashes. The bug is not incredibly common among WoW users because it requires high graphics settings (turning effects to "low" cuts commit size from 1.7GB to 700MB in Dalaran, for instance).
I hope this post was informative and will result in a solution for the large number of users I've seen while searching the forums for this problem whose problems have gone unanswered.
-spender
This is a problem only blizzard can fix by enabling 64 bit addressing ore at least by make WoW.EXE large address aware, do i talked whit some programmers and that last option may not always be possible.
This is a bug that will not go away, and even more and more people are getting it as multy display like Eyefinity and 3D surround are getting more and more popular.
SO eider Blizz fixes this ore i am forced to stop playing the game as +2 crashes a hour is just getting on my nerves
