Guild Wars 2

Hey everyone.

Most people might know this error. It has been asked allot of times and still nobody has a fix. I cant find a topic about it anymore to find a answer, so decided to make my own.

My client crashes very random. Sometimes not for hours and sometimes every 2 min. Ive tried many things. And even gone so far to buy new memory and re-installed my pc. Right now im running a clean system fully up-to-date only running Skype, Teamviewer and GW2.

My system:

The error i get every time is attached. Was too long for the post…

• Fix for me

This is bad ram. And no memtest will not always catch it.

Oke guys,

Sorry for waiting so long. Yesterday i bought new ram… Because i can and because this ram looks sexy (nope no real reason). And just to make sure the problem isnt the ram (well maybe a reason, but just to be sure….). Guess what!? IT WAS THE RAM! After buying new ram modules 3 different times (yes its crazy how far ive gone maybe) i finally can play.

It doesn’t matter if i overclock my CPU or GPU, drivers, applications (accept the known ones) it will keep running like it should. I tried my old ram and the crashes came back.

The weird thing is that this ram isnt even suported by my motherboard. And with a vol overclock (from 1,5 to 1,6v) i got it running. And it runs great!

I gues this doesnt help anyone. And it is still a weird thing. Because i never have crashes, the system runs stable, other games/programs run stable, memtest sees nothing, i could sometimes play fine for weeks, etc, etc. And then it start crashing again.

TL;DR: IT IS FINALLY FIXED. BUT IN A WEIRD WAY! I still think it is a problem at the clients end. Because this is the only game/program that has trouble.

PS: if someone still wants me to test something else. Just PM me ore leave a post to find out if the problem was something else.

i’m having the same problem as well.. not sure wat happened but after the previous patch it happened very frequently..

Set your Textures to Medium and see if that stabilises things for you.

its alrdy on medium for me and it still crash.. and tats for stand still in town….

what are you running in the background, C5 is illegal memory access.

been like this for me for the last month. Fortunately a bit less often now than before. Ill see how long I can be bothered. (w7 64bit, i7processor,GeForce 670 gtx, 12gb ddr3 mem)

try starting gw2.exe from the Run item (Winkey+R) using the “-repair” command switch

What are you running in the background, C5 is illegal memory access.

Nothing else then what i said in my description…

• Teamviewer (already tested without)
• Skype (already tested without)
• AVG Anti virus (already tested without and added a exception)

Try starting gw2.exe from the Run item (Winkey+R) using the “-repair” command switch

I did a re-install of my whole machine and the game. And run the repair ones. Still get the same problem…
 
 
 
Yesterday i tried to see whats happening on Procmon (monitoring tool to log what your pc/process is doing). I saw that GW.exe had trouble reading some dll files in my Winsxs folder, because of the default read only rights there (this is not causing the problem because everyone has this).

I know that almost all programs look in their own folder for dll files, and if they cant find them they will look in the Winsxs folder. So, i copied all the files it was trying to access to the GW2 folder. After i copied them and started GW2 i got some sord of memory leak after a few min (15-20). My whole memory was full (8g) all used up by gw2.exe. Run fine for a while tho and didnt get the same error. And windows crashed :S.

TL;DR: Copied dll files to gw2 folder from Winsxs. After i did that my memory soon was all used up by gw2.exe. Run fine for a while tho and didnt get the same error.

I suggest you check drivers then, a leak should not occur.

Of course, it would be easier to diagnose a possible cause if you would be as kind as to post Poolmon and rammap screenshots

Squall Leonhart.2075:

I suggest you check drivers then, a leak should not occur.

Of course, it would be easier to diagnose a possible cause if you would be as kind as to post Poolmon and rammap screenshots

First, thanks for the answer.

Drivers are up-to-date sinds i re-installed my whole system yesterday and downloaded all the drivers from the sites. I installed the following:

• ATI Chipset drivers
• Gigabyte USB 3.0 drivers
• ATI GPU drivers
• Realtek LAN drivers
• Realtek HD Audio drivers
• Asus N15 Wireless card drivers (PCIe)

I guess i can try that again. Altho soudnt be necessary to copy these files to the gw2 folder in the first place. I can do that but i dont think solving a problem by creating a even worse one (wich crashes my whole pc not just the game).

PS. I don’t know if its actually a memory leak. It is just something i think that happened.

“Model ‘0×006a28’: Can’t link child ‘0×00d120’ to parent bone ‘aura’, there’s no bone with that name. Linking to root instead
Model ‘0×006a28’: Can’t unlink child ‘0×00d120’ from parent bone ‘aura’, there’s no bone with that name.”

Yesterday for the first time ever, i also had 3 crashes in short succession, with similar errors. Since i did not change anything on my system, i guess the recent patch is a cause for this.

The actual “Exception: c0000005” is a illegal memory access in “no mens land” so somehow a pointer is corrupted, which may be caused by all kinds of stuffs, ranging from bad RAM/over-clocking to bugs in the game code, used .dlls, bad error handling or simply not correctly initializing/clearing a pointer variable.

The error trace code seem to fallback/crash for some animation/“bone” related calls, which point to a actual game code problem.

“Model ‘0×006a28’: Can’t link child ‘0×00d120’ to parent bone ‘aura’, there’s no bone with that name. Linking to root instead
Model ‘0×006a28’: Can’t unlink child ‘0×00d120’ from parent bone ‘aura’, there’s no bone with that name.”

Yesterday for the first time ever, i also had 3 crashes in short succession, with similar errors. Since i did not change anything on my system, i guess the recent patch is a cause for this.

The actual “Exception: c0000005” is a illegal memory access in “no mens land” so somehow a pointer is corrupted, which may be caused by all kinds of stuffs, ranging from bad RAM/over-clocking to bugs in the game code, used .dlls, bad error handling or simply not correctly initializing/clearing a pointer variable.

The error trace code seem to fallback/crash for some animation/“bone” related calls, which point to a actual game code problem.

Thanks for your answer.

Yes, i found that in the world wide web. But that doesn’t point to the problem. I already changed my ram and my bios settings are default. Tonight im going to try to actually underclock my system. Shut off some cores and change some settings. I re-installed my system to hopefully fix dll related errors.

So whats that says is that the game just has a bug in the code? And that it is just bad luck that i am one for the few that have this problem from day 1. With some days/weeks without problems…

MoosieOfDoom.4926:

So whats that says is that the game just has a bug in the code? And that it is just bad luck that i am one for the few that have this problem from day 1. With some days/weeks without problems…

I can just speculate, so ofc in your particular case i would also assume a “system” specific problem, since otherwise more players “should” encounter this problem. After yesterdays crash’s i would point to the patch in my case, which contradicts your pre-patch crashes.

I mean soon u reach a point where, except from changing your mobo/cpu, u have done everything that remotely relates to such problems.

AndyPandy.3471:

I can just speculate, so ofc in your particular case i would also assume a “system” specific problem, since otherwise more players “should” encounter this problem. After yesterdays crash’s i would point to the patch in my case, which contradicts your pre-patch crashes.

I mean soon u reach a point where, except from changing your mobo/cpu, u have done everything that remotely relates to such problems.

Well, i was planning on changing mobo. So that will be out of the question soon. And i can buy a new cpu for €200 later or something. The one i have now is fast enough, so dont need a massive upgrade.

Anyone else got any suggestions? (bump)

1) Go into your BIOS setup and see if there is an option to change the RAM speed. If your system RAM was “overclocked” @ the factory this may cause the error you are receiving. Fiddle with the settings if possible and test to see if this fixes the issue (or simply find the “return to default” option in the BIOS and activate it).

2) Also, is your CPU overclocked? How about your GPU? If so you may want to try setting them to normal speeds if adjusting the RAM clock fails to yield favorable results.

3) Certain programs that allow voice chat (like Mumble) or programs that allow video recording of your game session can cause the c0000005 error, but it is usually a “cannot read” memory error. I do not know if Team Viewer could be the culprit, but you may wish to try running GW2 without it.

4) Lastly, you can try running a chkdsk c: /r to check for file system errors, although I highly doubt this would cause a “cannot write” memory error.

Good luck, and I hope one of these suggestions fixes your issue.

1) Go into your BIOS setup and see if there is an option to change the RAM speed. If your system RAM was “overclocked” @ the factory this may cause the error you are receiving. Fiddle with the settings if possible and test to see if this fixes the issue (or simply find the “return to default” option in the BIOS and activate it).
2) Also, is your CPU overclocked? How about your GPU? If so you may want to try setting them to normal speeds if adjusting the RAM clock fails to yield favorable results.
3) Certain programs that allow voice chat (like Mumble) or programs that allow video recording of your game session can cause the c0000005 error, but it is usually a “cannot read” memory error. I do not know if Team Viewer could be the culprit, but you may wish to try running GW2 without it.
4) Lastly, you can try running a chkdsk c: /r to check for file system errors, although I highly doubt this would cause a “cannot write” memory error.
Good luck, and I hope one of these suggestions fixes your issue.

Thanks for your detailed explanation. But if you read all my reply’s, you can see i tried all those things accept for nr. 1. My bios is at default (fail safe settings).

Im going to try to underclock everything later today. I wanted to try it yesterday but got home rlly late from work.

Ill report back later, cheers!

screenshots of all the modules loaded by the GW2.exe in processor explorer would help a bit as well, to rule out any foreign applications injecting dll hooks.

I get the same error and at random times, usually when a big event is on. I have a new computer and it never crashes anything apart from GW2. Nothing is overclocked by me and I am reluctant to mess with BIOS etc as the machine is only weeks old. I send the error report every time and hopefully some one will get so sick of it that they will fix the problem.

I get the same error and at random times, usually when a big event is on. I have a new computer and it never crashes anything apart from GW2. Nothing is overclocked by me and I am reluctant to mess with BIOS etc as the machine is only weeks old. I send the error report every time and hopefully some one will get so sick of it that they will fix the problem.

Hahaha, i know that feeling. I’m sending like 10 a day.

I’ve just tried under-clocking both my CPU and memory. But nothing changes. I also changed my Visual Effects in Windows to “Best performance” and i do experience a little lees crashes. But still no fix :S.

Going to use the process explorer now to make a screen of my hooks.

Squall Leonhart.2075:

screenshots of all the modules loaded by the GW2.exe in processor explorer would help a bit as well, to rule out any foreign applications injecting dll hooks.

Here is my Procexp:

those are all the threads currently executing, but i was after the Loaded DLL’s, you can enable this in the Lower pane menu

I started getting this error too often very shortly after logging into the game since a couple of days ago. I can’t think of anything I’ve changed on my laptop recently unless the latest Windows update messed with something the game used somehow (I kind of doubt this is the case).

After messing with my graphics settings, it seems like the problem went away. I’m not entirely sure what fixed it or if it is actually fixed. I attached a screenshot of my settings in case anyone wants to see.

Squall Leonhart.2075:

those are all the threads currently executing, but i was after the Loaded DLL’s, you can enable this in the Lower pane menu

Do you mean this? Or where exactly?

Nyaabo.7415:

After messing with my graphics settings, it seems like the problem went away. I’m not entirely sure what fixed it or if it is actually fixed. I attached a screenshot of my settings in case anyone wants to see.

Thanks. I ive already tried these settings accept for the windowed mode. But didn’t help when i tried today. Thanks for your reply and screenshot. Hope it helps others tho.

Bump having the same issue started after I transfered servers. Did a reinstall last night and still crashing.

I’ve had the same problem for last 2 days or so.
In that time I installed a new version of Win.
Of course that, with the new os comes the driver download for that os.
Started getting the c000005 error too.
I noticed that there was a line called module : atiumdag.dll
I concluded that it must be a driver issue.
Google’ed that file and found that ppl have tried in other games to just copy it to the gw2 folder and……..voilá! no more crashes.
Even if it doesn’t work for others, my best bet is that it’s a driver issue.

Always follow the golden rule. If your other games work just fine, it must be gw2 and not your cpy gpu etc etc.

This is bad ram. And no memtest will not always catch it.

zerk.9701:

This is bad ram. And no memtest will not always catch it.

only true if the module it occurs in is ntdll.dll

This is bad ram. And no memtest will not always catch it.

Oke guys,

Sorry for waiting so long. Yesterday i bought new ram… Because i can and because this ram looks sexy (nope no real reason). And just to make sure the problem isnt the ram (well maybe a reason, but just to be sure….). Guess what!? IT WAS THE RAM! After buying new ram modules 3 different times (yes its crazy how far ive gone maybe) i finally can play.

It doesn’t matter if i overclock my CPU or GPU, it will keep running like it should. I tried my old ram and the crashes came back.

The weird thing is that this ram isnt even suported by my motherboard. And with a vol overclock (from 1,5 to 1,6v) i got it running. And it runs great!

I gues this doesnt help anyone. And it is still a weird thing. Because i never have crashes, the system runs stable, other games/programs run stable, memtest sees nothing, i could sometimes play fine for weeks, etc, etc.

TL;DR: IT IS FINALLY FIXED. BUT IN A WEIRD WAY!

PS: if someone still wants me to test something else. Just PM me ore leave a post to find out if the problem was something else.

MoosieOfDoom.4926:

This is bad ram. And no memtest will not always catch it.

Oke guys,

Sorry for waiting so long. Yesterday i bought new ram… Because i can and because this ram looks sexy (nope no real reason). And just to make sure the problem isnt the ram (well maybe a reason, but just to be sure….). Guess what!? IT WAS THE RAM! After buying new ram modules 3 different times (yes its crazy how far ive gone maybe) i finally can play.

It doesn’t matter if i overclock my CPU or GPU, it will keep running like it should. I tried my old ram and the crashes came back.

The weird thing is that this ram isnt even suported by my motherboard. And with a vol overclock (from 1,5 to 1,6v) i got it running. And it runs great!

I gues this doesnt help anyone. And it is still a weird thing. Because i never have crashes, the system runs stable, other games/programs run stable, memtest sees nothing, i could sometimes play fine for weeks, etc, etc.

TL;DR: IT IS FINALLY FIXED. BUT IN A WEIRD WAY!

PS: if someone still wants me to test something else. Just PM me ore leave a post to find out if the problem was something else.

Well not weird to me.

Squall Leonhart.2075:

zerk.9701:

This is bad ram. And no memtest will not always catch it.

only true if the module it occurs in is ntdll.dll

Everthing you learn in school does not apply to the real world. I’ve been building/repairing PC’s for a long time and yes self tought.

c000005 software crashes (as opposed to stop errors) are more often an incompatible overlay injection or badly written antivirus hook injection into the executable process.

Access Violations are rarely caused by faulty ram, and are only readily blamable on DRAM if they occur in NTDLL.DLL.

I was getting these type of crashes as well on my new built system. Went though all the hardware tests for days with no fails. Started poking around with the software side of things.

The fix for me ended up being installing DX9c. Since I have Win7, I thought I was fine with DX11. Came to find out the versions of DX have their own .dlls. Read that .dlls could cause these type of issues so I gave it a go. Went from 10m-1Hr before a crash to playing 7Hrs straight with no issues.

zerk.9701:

MoosieOfDoom.4926:

This is bad ram. And no memtest will not always catch it.

Oke guys,

Sorry for waiting so long. Yesterday i bought new ram… Because i can and because this ram looks sexy (nope no real reason). And just to make sure the problem isnt the ram (well maybe a reason, but just to be sure….). Guess what!? IT WAS THE RAM! After buying new ram modules 3 different times (yes its crazy how far ive gone maybe) i finally can play.

It doesn’t matter if i overclock my CPU or GPU, it will keep running like it should. I tried my old ram and the crashes came back.

The weird thing is that this ram isnt even suported by my motherboard. And with a vol overclock (from 1,5 to 1,6v) i got it running. And it runs great!

I gues this doesnt help anyone. And it is still a weird thing. Because i never have crashes, the system runs stable, other games/programs run stable, memtest sees nothing, i could sometimes play fine for weeks, etc, etc.

TL;DR: IT IS FINALLY FIXED. BUT IN A WEIRD WAY!

PS: if someone still wants me to test something else. Just PM me ore leave a post to find out if the problem was something else.

Well not weird to me.

Because? In tried 3 different sets of ram. Do you mean i bought 2 broken ones, and only GW2 has trouble with them?

Thanks for your reply tho. But this isnt helping :P.

It could have been the dram was incompatible iwth the motherboard (it can happen)
or the auto set timings weren’t good for the rest of the system.

What did you end up buying?

Squall Leonhart.2075:

It could have been the dram was incompatible iwth the motherboard (it can happen)
or the auto set timings weren’t good for the rest of the system.

What did you end up buying?

Just the faster version of Corsair 8 GB DDR3-1600 Kit Dominator Platinum. But ive tried all different combos to make it work. Different timings, different voltage, etc.

The ram i bought before was on the motherboards compatibility list. And the only program having trouble with it was GW2. Thats what makes it weird to me.

ouch, thats fairly pricey.

you probably would’ve payed less for a 16GB Vengeance/Vengeance LP kit

Hey guys been having this issue and fixed it! The game has always worked for me until last night.

View PostRetardo_The_Great, on 25 August 2012 – 04:17 PM, said:
after disabling mumble overlays and closing mumble i was able to get into game, hope this helps some people. im still using mumble activated after going in game but the only thing i changed frrom earlier was the overlay so i think its that for me

This post was on gw2guru forums.

I don’t use mumble. I turned off the overlays in MSI afterburner and my game launched! So I think overlays with some programs are causing the problem. I just tried fraps and it let me load in. Also if you want to use overlays for FPS/Temps or whatever I was able to turn them back on in MSI Afterburner after being in game. I just can’t launch the game with overlay turned on.

I hope this helps.