Game crashes all the time in wvw

#1 - Nov. 7, 2013, 11:40 a.m.
Blizzard Post

Hello! I haven’t played Gw2 for a while. When i did, the game crashed on occasion (every 1-2 hours). Now I have returned, and now it crashes after 1 min in wvw.

The crash report i get is:

—> Crash <—
OOM: arena=Environment, cat=Prop Packfile, allocBytes=634596, arenaBytes=130655240, fallbackBytes=141728, align=0 ,
App: Gw2.exe
Pid: 3204
Cmdline:
BaseAddr: 00400000
ProgramId: 101
Build: 25625
When: 2013-11-07T17:35:04Z 2013-11-07T18:35:04+01:00
Uptime: 0 days 0:05:02
Flags: 0

I have tried setting the game to auto detect, and every setting on low, with no improvement..

Any ideas and help would be appreciated! =)

#2 - Nov. 7, 2013, 12:29 p.m.
Blizzard Post

Hi there Jabbiz – Are you on a 64-bit or a 32-bit OS? If you’re using a 32-bit OS, more than likely this is the cause of your issue if you’ve got more than around 3.5 GB of memory (including the additional video memory) in your system. This is simply due to a limitation of 32-bit operating systems.
This is where it gets a little complicated, but the short version is that the additional memory can push your total available memory into negative numbers resulting in crashes or simply, “out of memory errors.” Some players have resolved this by upgrading to a 64-bit operating system. Others simply have removed physical RAM from the system to bring the memory totals closer to values intended for that revision of Windows (32-bit). Obviously removing RAM from your PC is not an ideal solution but I wanted to give you all the information we have learned regarding these issues. You can read more about this issue from Microsoft here: http://support.microsoft.com/kb/929605 The important part is listed below:

“For example, if you have a video card that has 256 MB of onboard memory, that memory must be mapped within the first 4 GB of address space. If 4 GB of system memory is already installed, part of that address space must be reserved by the graphics memory mapping. Graphics memory mapping overwrites a part of the system memory. These conditions reduce the total amount of system memory that is available to the operating system.”

One solution presented by players being affected by this is to change the “Maximum pre-rendered frames” in the Nvidia control panel. To do this:

1. Right-click on your desktop and select “Nvidia Control Panel.”
2. Select "Manage 3D Settings.”
3. Scroll down until you find “Maximum pre-rendered frames” and change it from “Use the 3D application settings” to “1.”

Once completed, click “Apply” to save your changes and try Guild Wars 2 again.

Hope this helps!

#5 - Nov. 7, 2013, 1:57 p.m.
Blizzard Post

Hi there!

Switching to a 64-bit OS would probably be your best bet but I certainly can’t tell you to go out and do this. I think there’s a couple of other workarounds that have worked for other players with a 32-bit OS – unfortunately these are some suggestions that I cannot personally offer. I’d check out the other threads where players have reported the same issue to see if you stumble across it unless someone else chimes in to this thread to help you out.

Sorry I couldn’t offer any information other than this – generally turning down some of your in-game graphics options can alleviate some of the crashing but it sounds like this is something that you’ve already tried.