Guild Wars 2

There is nothing special to download .. every client runs on the same patch level
no matter if you have HoT or not. The only question is if you can access the new
zone, the mastery levels and of course if you can create a Revenant.

Kylden Ar.3724:

That’s good to know. I only recently entered middle class income and am still hesitant to spend more than $20 on anything not my house. While I will have a new 64-bit rig around late December probably, not everyone in that boat can do that.

How old is your computer ? Over 10 years ? Even the first core 2 duo processors
from Intel were already 64 bit, and i can’t think you play GW2 on an old single-core ?

https://en.wikipedia.org/wiki/List_of_Intel_microprocessors#64-bit_processors:_Intel_64_.E2.80.93_Core_microarchitecture

Be happy … people always dream of having 100% from GW2 updating to DX-12
or just better multithreading.

On a more serious note .. it could be something like read errors on your harddisk
or problems with your soundcard .. or something else.

https://forum-en.gw2archive.eu/forum/support/support/64-bit-Client-Beta-FAQ

Have you tried renaming the gw2-64.exe to gw2.exe ? I have noticed there a progams
that simply use a compability list depending on the name of a program.

Kylden Ar.3724:

And people wonder why consoles even have a market… Crap like this is why.

And i bet you still play current console games on a console from 2005.

autopsie.6159:

ok… my point being…

if its broke.. fix it..

it was programmed as 32 bit game

it was designed for 32 bit systems

sold as a 32 bit game

with 32 bit requirements

if it doesnt work… they should fix it..

simple as that..

upgrading to a 64 bit client WILL NOT FIX THE ISSUE… only prolong the time it takes for it to fill the memory and crash.. IT WILL NOT PREVENT THE CRASHES…

I also wonder if people still play the current version of WoW on single core processors
with 2 GB of RAM .. because .. it was designed for that .. and god forbid an MMO
change over the years and as a result maybe use some more memory.

Heck even Everquest 2 had already OOM problems 8 years ago when
Rise of Kunark came out with zones that had twice the size than the old zones.

Next was AoC that crashed every few hours under 32-Bit and Lotro also could
consume over 3 gb since years.

Rithian Yawgmoth.6809:

I have tried EVERY THING!!!!

The launcher keeps popping between 80-100-0 kbs. I cant even get to the point where you log in. I tried using a VPN and BOOM it started downloading faster,

If it worked better with a VPN its clearly a problem with you ISP.

With 2GB of ram i guess the client will crash already after 2 minutes or whatever
if you even get it to run.

OGDeadHead.8326:

Q: Is there a hard limitation how much ram the 64 bit client will use? I would love for it to use LOTS of memory if it means smoother performance.
If I understand things correctly, it seemed yesterday it went close to using 6 gig ram, but I may have misinterpreted the numbers show in Process Lasso (taskmanager of sorts…)

The maximum memory limit for x64 processes is 8 TB, but the practical limit is far less as it depend on the amount of physical memory and the pagefile size on your system.

However problems with the performance would occur already if windows starts
to swap memory to harddisk if the process needs more than your physical RAM.

If you made a new install .. why not 64-bit ? You know that your key works for
both versions ?

Scolix.4879:

uhohhotdog.3598:

Are there really people still using 32 bit systems in 2015?

Well i have computer from 2011 and it still works fairly well and i will keep using it till it dies so yes some people are still using 32 bit.

2011 is not that old .. i use 64-Bit Windows since 2008 and the CPU i had at that
time was maybe from 2005 or 2006.

MS should really have stopped selling 32-Bit version with Win7 already.

Get rid of your ancient kittening 32-Bit windows .. because else there is no
reason to cry since they release a 64-bit client to fix it.

Try older drivers .. if it doesn’t help try even older … continue until you find a version
that runs stable on your PC. Typical procedure with NVidia drivers.

And always keep a version of the stable driver .. in case you install again a new one
and it still doesn’t work.

Do you use the windows firewall or something else ?

Also .. try if it helps to rename gw2-64.exe to gw2.exe .. in case there are firewall
rules for gw2.exe but not for gw2-64.exe.

msblueness.6781:

My game feels smoother running around central Tyria, but my load times are upwards of 5-minutes now. Also the client slightly freezes anytime a window (inventory, trading) opens which I don’t get in the 32-bit. I don’t have any crash issues in HoT areas so far but do seem to lag more… possibly as my computer is a potato on Vista.

Sounds like your physical memory is simply so full that windows starts swapping
memory to your harddisk. So either upgrade memory, restart your client when
it starts to get bad, or do what always was the tip against OOM crashes : reduce
your settings.

The game is already multithreaded .. it uses 4 cores .. but since thread often have
to wait for other threads to continue it is more or less impossible to have 100%
load on all 4 cores. So its just 1 core on 100% .. and the others mostly at 50-75%
for me that leads to maybe 60-75 % total load.

Boo.5743:

Running a 4K monitor on Windows 7 SP1. With the 32bit client I can use Properties/Compatibility/Disable display scaling on high DPI settings to make the interface display correctly but this option is greyed out on the 64bit client.

A workaround is to put this entry in the registry:
HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers

New String
Key=C:\GuildWars2\Gw2-64.exe <— use path to exe on your system
Value=HIGHDPIAWARE

Or have you tried renaming the gw2-64.exe to gw2.exe ? That also helps for
quite some issues.

I switched to Win-64 already 7 years ago because of OOM errors in Age of Conan.
Other people had OOM errors even before that when EQ2 release Rise of Kunark
that had much bigger zones than the older content.

32 bit is an ancient OS for gaming and the only real problem is that Microsoft
still sells 32-Bit version. They should haved stopped that already with Win7.

Oh an btw. you can use your Windows Key for the 32 and 64 bit version, so all
you need to do is download a 64-bit ISO from MS and make a fresh install with
it .. you don’t have to pay for a new Windows (at least if you don’t have still
XP or Windows 98)

Ravion Hawk.4736:

Gaile Gray.6029:

I already have the 32-bit client; will I have to completely download the game again?
No. The 64-bit client uses the same data as the 32-bit client. If you already have the game installed, you can follow these instructions to avoid needing to reinstall the game:

• Download the 64-bit client.
• Copy the downloaded program into your Guild Wars 2 game folder.
• Update any shortcuts to the game to point to the new file instead.
  This process will be automatic once we get out of beta.

I would like to remind you that 64bit versions Windows have two “Program Files” folders for a VERY specific reason.

C:\Program Files\ <—————— Programs run from here are run in 64bit
C:\Program Files (x86)\ <—— Programs run from here cause Windows to drop into 32bit

You just told everyone to run a 64bit client from the very same directory that causes Windows to work in 32bit.

Might I suggest that you set the 64bit beta client to do a fresh install to the “C:\Program Files\” folder then just have us advanced users (Desktop Support Tech right here) copy the gw2.dat to the 64bit installation.

You can avoid some bugs right there without having to hunt down the cause.

I would generally avoid the program files folders for games that are often patched
since there are often some strange windows rights that cause problems.

So i personally use c:\games\gw2

NeHoMaR.9812:

Looks like the 64bit version can’t play with partially downloaded client, need full download.

By the way, I want the Exe name to be Gw2.exe, because I track the time I use with applications. Maybe I can rename it? or maybe the final version of this will be in different folder? or better, remove 32bits support and change to 64bits with the same name?

You can just rename the exe .. helps also with programs like Razer Synapse and Overwolf.

Same here .. tried it different times in 2 hours .. always the same.
Other zones are no problem.

Johan Skold.4708:

Beldin.5498:

I wonder what happens on the next patch, will the patcher detect the x64 or
will it be overwritten with the x32 because of the name ?

If you renamed the 64-bit executable, it will still patch the 64-bit executable but with the new name. It should just work.

Yeah .. worked so far at the new patch

GM Kveldulf.4790:

@Beldin.5498.

Exception: c0000005 is a fun one, and there are a lot of possible root causes unrelated to the 64-bit client. I recommend submitting a support ticket about it, and we’ll run through some troubleshooting with you.

Like i said .. it was TS3Overlay i think.

I tried now Overwolf .. however for Overwolf to stay in front i first had to rename
gw2-64.exe to gw2.exe

I wonder what happens on the next patch, will the patcher detect the x64 or
will it be overwritten with the x32 because of the name ?

PinkFluff.6084:

To save time on downlaods and not having multiple dat files if I don’t need them. I’m curious if the gw2 dat file is the same for both 32 and 64 version. If I can just copy/past the 32 bit version… it’ll save some time.

Just drop the new exe in your GW2 directory and start it..

But .. bad news .. got a crash in the character select screen .. after that already before
when i restart it. I guess it could have been TS3-Overlay .. will now try it without

—> Crash <—
Exception: c0000005
Memory at address ffffffff`ffffffff could not be read
App: Gw2-64.exe
Pid: 21680
Cmdline: -autologin -maploadinfo
BaseAddr: 00007FF7BD7A0000
ProgramId: 101
Build: 54869
When: 2015-11-04T19:36:48Z 2015-11-04T20:36:48+01:00
Uptime: 0 days 0:10:40
Flags: 0

—> System <—
Name: DESKTOP-402MECB
IpAddr: 192.168.2.100
Processors: 4 [GenuineIntel:6:10:7]
OSVersion: Windows 6.2 (64 bit)

—> System Memory <—
Physical: 3853MB/ 8175MB 47%
Paged: 3868MB/ 9455MB 40%
Virtual: 134215343MB/134217727MB 3%
Load: 52%
CommitTotal: 5586MB
CommitLimit: 9455MB
CommitPeak: 6419MB
SystemCache: 4047MB
HandleCount: 33768
ProcessCount: 71
ThreadCount: 1315

—> Process Memory <—
Private: 2116MB
WorkingSet: 1550MB
PeakWorkingSet: 1550MB
PageFaults: 1563426

Even if ANet would really make a 64-bit client against the crashes, there would
still be the problem that Cider is only 32-bit. So you would also have to ask
NVidia for a 64-bit Cider now ..

Just use the patcher, it will update your current installation, while the disc will
mostly just overwrite your installation and then still patch anything that was
changed after the disc were created.

Download installer here :
https://account.arena.net/content/download/gw2/win

and best rename it to gw2.exe, move it in your GW2 directory and start it.

Faoiltiarna.4271:

Rofl. Witcher has models weighting bigger textures than entire zerg. Gw2 is 32 bit crap using dx9 that even WoW turned away from. Maybe they should reconsider using worse textures if their client can’t handle their own creation?

Than have fun playing the witcher for the next 3 years .. beacuse I don’t want
worse textures only because some people a too stubborn to change 1-2 settings.

Hm .. have no more ideas. Maybe there is something really physically broken either
on your GPU or your mainboard.
Do you have maybe still an older GPU lying around so you can test that one ?

Healix.5819:

As a temporary workaround (Win7x64), I dropped the texture quality to low which reduced the memory usage by about 800 MB. I was able to assault Tarir 4 times within the same map without issue. I did however notice that the memory usage was increasing by 100 MB after every assault, which I assume would have eventually led to a crash. It was up to 2.4 GB, compared to the 2.9 GB prior to crashing on high.

Thats memory fragmentation, that happens the longer you play, and it helps to
restart the client now and then if you know you will do a longer event.

Just imagine your memory will look like a swiss cheese after a while, and with
restarting you close all holes for a while .. until the mice come in again

http://stackoverflow.com/questions/3770457/what-is-memory-fragmentation

Faoiltiarna.4271:

I am not planning to lower anything down on a PC that can handle The Witcher 3 on 60fps and everything on ultra. Seriously i wish they already swapped to 64bit client with dx11 already. My memory is like 5gb free anytime i play so it isn’t about my PC. It is about how the game uses it’s memory. Same about graphics and processor that don’t even sweat.

Then have fun with even more crashes .. yay .. some people simply don’t want help.

Btw.: How often are there zergs with 100 player characters, all with different armor
Skins in the witcher ?

Slecrety.8049:

I look up if my GPU run at x16 and it doesn’t it only runs at x2, how can I fix that other way than cleaning my GPU? because I tried it and didn’t work, also deleted loca.dat and didn’t work. Thanks in advance!

1. Make sure your GPU is placed in the slot next to your CPU.

2. Reseat your GPU to make sure there are no contact problems.

Check if your GPU runs @x16 with GPU-z (see image below)
If it doesn’t, reseat your GPU … else delete / rename your local.dat file

So .. the R9 Fury seems to be the bad boy here.

@Faoiltiarna.4271
Have you tried to set down the character model limit ?

Kraggy.4169:

It’s interesting that Turbine are blaming a spate of crashes after the latest update to LoTRO a couple of weeks ago on Nvidia cards, even though in their case it’s clearly their game client (32-bit) trying to access more than 3.5Gb of memory according to TaskManager.

Is it the same issue here I wonder?

That said, Iv’e not so far had a GW2 crash but LoTRO crashes 2 or 3 times an hour for me in the new LoTRO zones.

Lotro has already consumed a lot of memory years ago. This picture is from 2010
and i think at that time a lot more people still had 32-Bit Windows.

You know that you account will be permanent closed if you get a refund ?

Its not that just HoT will be removed from your account, your complete
account will be shut down.

Else i would also get happily rid of HoT .. i just hate how the game now wants
to force me to things i never wanted to do, and never had to do in the past.

sirsquishy.8531:

Never crashing, But i use Medium character limits and High Character models. OOM means your client cant access paged memory for whatever reason.

All windows 64bit.

HD6970M – Win10x64
R9 M270X – Win7x64
295×2 – Win7x64
R9 280x – Win7x64
R9 270x – Win7x64
R9 390 – Win10x64 (new ITX build work in process, so cant say its 100% stable yet but no crashing yet)

So you should adjust your in game settings if you are crashing with OOM.

Oh .. i have no crashes, like i said it was just out of interest. Forgot to say i use
a R9 280x with Win10-64 and these settings :

Just out of interest .. who has constant crashes with AMD GPUs under Win-64 ?

And please don’t post if you use 32-Bit windows or a MAC .. or have an NVida GPU.

Eagelseye.6312:

So taking all the above comments, it is very clear that this OOM crash is:

1. Not a 32-bit system problem as claimed by the developers and is common to 64-bit system users as well
2. Not a problem due to game not completely patched/downloaded

32-Bit is ONE of the problems. It crashes much faster under 32-Bit since it will crash
at around 1.6-1.7 GB memory usage, while under 64-bit its around 3.5-3.6 GB.

Not completly patched leads to more memory fragmentation, so thats another
reason for crashing earlier.

Its not black & white .. everything that leads to more memory usage brings the
game to crash when the critical point is reached. Restarting the client also helps
against memory fragmentation .. and lower graphics setting leads to less
memory usage.

Win10-64, Intel i5 2500k, Radeon R9 290x , 8GB RAM

Client completly patched, no crashes at all with these settings :

Seems the streaming client also leads to more memory fragmentation and so
to more OOM crashes.

https://de.reddit.com/r/Guildwars2/comments/3r3rul/can_we_please_get_a_dev_to_acknowledge_that_this/cwkqal5

Seventh (edit): Try making sure you are fully patched up before you play; the streaming client has been pretty successful for us but if it turns out something in our memory management system was on the edge, then streaming client might have put it over, as it can increase memory fragmentation. Just let the green bar on the login screen go to the end, instead of hitting play at “playable”.

Also new information : make sure your client is completely patched, since the
streaming client leads to more memory fragmentation.

https://de.reddit.com/r/Guildwars2/comments/3r3rul/can_we_please_get_a_dev_to_acknowledge_that_this/cwkqal5

Rinn.2375:

Changing the client means changing the servers too.

Thats wrong. Also i bet the server will run mostly on 64-bit. Can’t imagine at least
that they still use a 32-bit SQL-Server for the amount of data that we have in the
BLTP.

loseridoit.2756:

Hmmm, I wonder if cider supports 64 bits windows apps. Oh well.

Cider is only 32 Bit ..

I think the biggest problem is that in the time you need to bring the 64-bit client
to run you must more or less stop every other changes on the current client.

Once you have everything running as 64-Bit it was at least for me with my Delphi
Projects, just a click to compile them as 64- or 32-bit exes.

Main problem for me were strings, however i have no dynamic memory allocation,
and i assume that will be the biggest problem in a project like an MMO and there
will be a lot sources for bugs and crashes.

But in the end there is no way around that, or they have to bring back culling.

Oh .. and then there is the problem with the MAC users, since Cider is only a
32-Bit emulation.

I tried that 8 years ago when i had constant OOM crashes in Age of Conan and it
just totally messed up my graphics.

In the end i installed Vista-64 … and never looked back. Microsoft should haved
stopped bringinng out 32-Bit systems already with Win-7.

And just as Info, if your Windows Key is original from Microsoft you can install
the 64-Bit version with the same key. Just download an ISO for free at MS, burn
a DVD, and install it.

Eagelseye.6312:

Turamarth.3248:

Eagelseye.6312:

Chris Cleary.8017:

File name:HMIPCore.dll
Publisher:My Privacy Tools, Inc. (signed by My Privacy Tools, Inc)
Product:My Privacy Tools SecureNet Service.

This is what is crashing you. Probably going to have to remove it.

I am not able to find this in my PC. Can you help with the path?

That’s because you have a completely different error according to your screenshot here.

If the error log doesn’t have the line “Module: HMIPCore.dll” this won’t help you.

Yes agreed. Mine is OOM error only. As mentioned earlier, I am using lowest graphic settings, opted for best performance and disabled the AV as well. The game still crashes. All was fine till HoT was released.

IT IS THE PATCH. Hope they fix it soon.

So why are you posting in this thread if you have a totally other problem ?
There are masses of OOM threads, post there or make your own.
Or even better, just read the tips there what can prevent OOM crashes and
try those.

Most important : upgrade to 64-Bit Windows.

Unseenchaos.7036:

lol what.

Please research before you make a topic. An engine isn’t simply a dropbox where you select “Cry Engine” or “Unreal Engine” lol.

Haha .. yeah like you can order a Mini Cooper or Beetle and select a Chevrolet,
Ferrari or Maserati motor for it

RoRo.8270:

I’ve set everything on low and still receive these crashes. I’m not sure if it’s the same as others but i’ve had crashes where I am the only person around these crashes only occur in heart of thorns areas. I’ve got a 660ti sc/i7-2600k @4.5ghz/8gb ddr3 ram.

1. You should ofc have 64-bit Windows, since under 32-bit the client already crashes
on half the amount of memory than on 64-bit Win

2. take a look into / post your crash-log to see if its an OOM (out of memory) crash
or something else.

trueanimus.4085:

btw, nvidia seems to get the oom crash far more than ati cards, while i on my intel HD shared UMA havent crashed once with OOM error, only a few bouncy chests crashes because of the UI changes,

Or NVidia user simply think that they have the best cards on the world and thus
it would be an insult to their fantastic GPU to have some settings NOT ON MAX ?

Of course i also wouldn’t wonder if its really just another issue of NVidias crappy
drivers.

trueanimus.4085:

the game has a HUGE memory leak atm… hence the OOM error. Out of Memory error.

This applys to both nvidia and radion video cards… (mostly nvidia though it seems) and will crash your game every 5-10 minutes depending on how much memory you have on your pc and on your gpu.

I have no problems with my Radeon R9 280x with character model limit and quality
set to medium.

Also the “leaks” are called “memory fragmentation” and its a problem how C++
and i think nearly every programming language allocates and frees memory.

http://stackoverflow.com/questions/3770457/what-is-memory-fragmentation

trueanimus.4085:

telling people to update from windows 32 to windows 64 (even though the client is only 32 bit)…

Oh .. and you know that a 32-Bit programm can use 4 GB under Win64 but only
2 GB under Win32 ? For that reason i upgraded to Vista-64 already 8 years ago
because of constant OOM crashes in Age of Conan.

coque.3750:

is there a quick fix for OOM errors atm to work around this?

Yes .. has been posted 1000 times, but people are not willing to use it.

Set character model limit and quality to medium .. if thats not enough to minimum.

Also if you know you will be longer in a big zone for something like Tequatl it could
help to restart your client after entering the zone to avoid memory fragmentation.

http://stackoverflow.com/questions/3770457/what-is-memory-fragmentation