Out of Storage Error / 3.3.5

[Svpernova09]

Sticky in WoW Technical Support Forums:

http://forums.worldofwarcraft.com/thread.html?topicId=25552505632&sid=1&pageNo=1


Anyone else having this issue? I'm completely unable to login to toons in Dalaran because of this error. But I can login to a lowbie in Stormwind just fine.

TL:DR of that thread is there is a bug some people with 64 bit Windows are seeing where WoW requests more memory than it's able to handle / allowed to handle and it crashes with an "out of memory" error. The only way to fix it is to violate the ToS/EULA by modifying wow.exe to enable LAA awareness.

[Tonuss]

From what I am reading there, another possible 'fix' is to lower the graphics settings until they no longer crash your game.

[jinkobi]

I am getting a new bug since the patch. I'm pretty sure it's in the same vein as this error because it's in the memory. Just randomly I will crash with a memory access violation after an hour or so of play OR it happens the instant I log in which is odd.

Not to bore with long scrolling walls of bug info here's the jest of the error I have.

This application has encountered a critical error:
ERROR #132 (0x85100084) Fatal Exception
Program: C:\Users\Public\Games\World of Warcraft\WoW.exe
Exception: 0xC0000005 (ACCESS_VIOLATION) at 001B:003D3513
The instruction at "0x003D3513" referenced memory at "0x003D3513".
The memory could not be "written".

[lamf123]

I'm getting the same error after playing for a while, happens on just the leader window,

[Svpernova09]

From what I am reading there, another possible 'fix' is to lower the graphics settings until they no longer crash your game.


I tried this, and still no luck, I completely reverted to a clean WoW folder and still have this issue.

[Lyonheart]

>>>>> http://www.dual-boxing.com/showthread.php?t=30699 (http://www.dual-boxing.com/showthread.php?t=30699) ( turned out to have nothing to do with any of my addons in particular )

I made a post about this the first day of the patch. I think the fix will have to come on Bliz end. I deleted my cache/wtf/./ bla bla bla ..and it still does it,

[Fishbeak]

I have been seeing this error since before the patch (out of memory) maybe I am just lucky.

Pre-patch however it was ONLY when I was on all 5 toons and had them fly somewhere (flightmaster) together ... the lead would crash.

Post-patch I am getting it anytime I have all 5 and hit high traffic areas like dalaran

The Master only ever crashes (highest res).

[Drommon]

I too have been getting this error. I am unable to resolve this issue as well after trying several things that have already been mentioned. It is fortunate to know that this is a known bug and I hope blizzard fixes it soon.

[Mercurio]

I am getting a new bug since the patch. I'm pretty sure it's in the same vein as this error because it's in the memory. Just randomly I will crash with a memory access violation after an hour or so of play OR it happens the instant I log in which is odd.

Not to bore with long scrolling walls of bug info here's the jest of the error I have.

This application has encountered a critical error:
ERROR #132 (0x85100084) Fatal Exception
Program: C:\Users\Public\Games\World of Warcraft\WoW.exe
Exception: 0xC0000005 (ACCESS_VIOLATION) at 001B:003D3513
The instruction at "0x003D3513" referenced memory at "0x003D3513".
The memory could not be "written".


I get this a lot since Tuesday. With ten accounts going at once, it seems like one is always going down on me. A reboot usually fixes it for a while, but it is still a pain.

[BrothelMeister]

Note to self: DO NOT HEARTH TO DALARAN!!

[Kang]

From what I am reading there, another possible 'fix' is to lower the graphics settings until they no longer crash your game.

This is what I did, but I still have some odd lag issues I never had before the patch. My system is fully capable of running max graphics without issue. I'm really pissed I can't experience the game the way I want.

[Tonuss]

I just got the error for the first time, after turning OFF the option to use "Windowed Mode." Since I run multiple monitors, I like to use Windowed Mode (Maximized) so that I can move the mouse over to the other monitor to do other stuff (such as what I'm doing now). I turned that mode off so I could record the game with FRAPS and about an hour later, bang... closed with the error.

In Windowed Mode with the window maximized, I can run at full resolution with all effects at max and no issues whatsoever.

[jinkobi]

I get this a lot since Tuesday. With ten accounts going at once, it seems like one is always going down on me. A reboot usually fixes it for a while, but it is still a pain.


Hey Merc if you're using Nvidia there's a new driver out. Updated mine earlier and haven't had the crash since and the game performance increased heaps.

[Noids]

The lowered graphic settings helped delay the problem a bit for me, butI tried to keep viewing distance as high as possible initially. It wasn't until I lowered this that I got enough stability to actually do stuff again. If I move a lot around Dal however, it takes a bout 5-10mins in Dal to crash me. Funnily enough I managed WG alright though.

Other things that will supposedly help are running at lower resolution, reducing add ons etc. As the thread says however, it seems to be a problem in the program itself so something that Bliz will need to fix esp. if Cata follows the trend of increased resource utilisation, reducing graphics settings isn't going to do much.

[Mercurio]

Hey Merc if you're using Nvidia there's a new driver out. Updated mine earlier and haven't had the crash since and the game performance increased heaps.

Thanks, I am using an Nvidia card on one of my two computers - I'll try it out!