WoW error in dalaran.

[chriso132]

Hi,

Everytime im in dalaran i keep getting a WoW critical error which reads "not enough storage space to complete the command", its on my ssd which has 9 gigs left but it done the same on my main HDD which has 800gb free. Ive tryed the repair and also deleted the WTF folder, cache and interface addons but still no luck.

Im running windows 7, asus rampage extreme III, intel i7, 2x GTX 480s, 6 gig DDR3. Im also running triple monitors if this makes a difference.

Does anyone know anything else i can try to fix it.

Thanks

 

[Adsta]

Re-install ?

Its a pain I know but thats the only thing I can think of

 

[iviv]

Hi,

Everytime im in dalaran i keep getting a WoW critical error which reads "not enough storage space to complete the command", its on my ssd which has 9 gigs left but it done the same on my main HDD which has 800gb free. Ive tryed the repair and also deleted the WTF folder, cache and interface addons but still no luck.

Im running windows 7, asus rampage extreme III, intel i7, 2x GTX 480s, 6 gig DDR3. Im also running triple monitors if this makes a difference.

Does anyone know anything else i can try to fix it.

Thanks

That isn't hard drive storage, its actually running out of memory. Have the task manager running on the second monitor, you'll see WoW hit the 2Gb (Around 1.7Gb reported in task manager) mark fairly quickly in Dalaran, and being a 32-bit process it can't address more than 2Gb of ram, so it crashes out. Turn the graphics down a notch or two and there won't be as many textures to load into the ram, and you shouldn't crash as much.

Unfortunately, until Blizz get around to fixing this, there's not much we can do I don't think.

EDIT:

Apparently, someone on the forums found a fix for the issue. Or rather, a program that applies the 'large address aware' tag to the exe. While this is technically editing the game's .exe file, someone in the thread posted a GM screenshot chat apparently saying that the use of the program will not result in the account getting banned. Still, use at your own risk:
http://forums.wow-europe.com/thread.html?topicId=15111071794&sid=1&pageNo=1

 

[unknownsock]

Must be just a bug, I'm running with 3 1680x1050 monitors maxed out minus shadows and AA/AF etc on a 1gb 5870, q9300 @ 3.0 with 4gb ram.

You've tried all that i can suggest. Reinstall it is.

I think i do recall this after one of the late 3.3/4.x patches, it may just need a patch for some users.

 

[iviv]

I must admit, I was having the crash tons during 3.3.3 but haven't had it once since 4.0.1, but people have been saying they've had it more since the patch.

 

[Adsta]

if its the case iviv is saying maybe try sticking more RAM in your PC ?

I've never had a problem but then again I have 6gb ram and a 480GTX so... *shrugs*

 

[Davepen]

I have an issue in Dalaran also, which I fixed, which is similar in a way....

If I goto Dalaran or another highly populated city after a patch has been released, my wow disconnects and also my wireless connection disconnects also, requiring a reconnect.

It turned out that the large amount of data that was trying to load was causing the buffer on my wi-fi adapter to overflow and crash.

To solve this I had to bridge my wi-fi and lan connections, which seems to solve the problem...


I know this isnt the same as your issue but it may give you some ideas?

 

[Bumhug]

When you load the launcher does it say "applying critical updates"

I used to get this a lot and found that if I let it finish updating before I hit play game would work fine

 

[iviv]

if its the case iviv is saying maybe try sticking more RAM in your PC ?

I've never had a problem but then again I have 6gb ram and a 480GTX so... *shrugs*

Its not a lack of RAM, its the fact that a 32-bit exe can only address 2Gb of memory, unless it has the /largeaddressaware tag. To quote from the linked thread:

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.