Guild Wars 2

I repaired my client once to fix some problems with crashing, it reinstalled the ENTIRE game, and it didn’t fix the crashing.

The problem now is that it doesn’t want to stop repairing itself, AND reinstalling the entire game every time I start the launcher.

Yes I have removed the “-repair” from the command line.

Is there any way to fix this other then deleting the entire game and reinstalling for a 3rd time?

Try to disable UAC? then run the client.

Alpha Dragon.4576:

Try to disable UAC? then run the client.

No dice, started another repair, as well as started to redownload files.

Hmm let it finish the repair ? Is there any logs file or corrupted dat on your Gw2 folders (check Documents\Guildwars2 as well)

I have this issue as well. I am starting to think that the 15gb dat file is too much for our computers to work with.

Uploaded my crash log for all of my crashes, the latest crashes are at the bottom.

Was the latest crash have UAC turned off or on? Are you running the game as admin as well?(right click run as admin or check properties and run it as admin )

Alpha Dragon.4576:

Was the latest crash have UAC turned off or on? Are you running the game as admin as well?(right click run as admin or check properties and run it as admin )

I always run the game as admin, and I’m not worried about the crashing, I know its because my computer has a bad stick of memory, I’m worried about getting the game to stop repairing itself.

Did you remove the memory? Afaik everytime you launch the game it checks your hardware and the dat file.

Alpha Dragon.4576:

Did you remove the memory? Afaik everytime you launch the game it checks your hardware and the dat file.

I have 4 sticks or ram, and no idea which one is bad, I’ve been crashing for a long time now, and it only started repairing itself after I told it to repair the first time (which it completed)

Try checking your memory with memtest. Also check https://forum-en.gw2archive.eu/forum/support/tech/Game-crashing-Memory-violation-c0000005-possible-solution/first#post129965

Alpha Dragon.4576:

Try checking your memory with memtest. Also check https://forum-en.gw2archive.eu/forum/support/tech/Game-crashing-Memory-violation-c0000005-possible-solution/first#post129965

Again, I’m not worried about the memory… I plan to get a new computer in a few months so I’m not trying to fix the memory.

All I’m seeing is that there is no way to stop this from repairing, if it does it again I’ll just do a full uninstall and reinstall.

Temp solution is to remove the bad memory(hence the memtest). As I’ve said game checks your hardware for faults.

Could be a long shot but is it possible the shortcut you are using to start the game has “-repair” added to its command line?

I have a shortcut as such purposely when/if i have issues.

I too have made 2 posts about my client forcing a re-DL of the game down my throat at a whopping average of 210kb/s. (not a peach) the funny thing is, first post got closed because i replied to people with the same courtesy as they posted in my thread, ignoring their point. Not to mention the Mod sent me to a PoS QA’s that had absolutely no help, the second post was more fertile despite not having a solution, i removed the game, removed game files from documents Guild Wars 2 and removed installer, re DL’d installer and now in the process of re-dling the game(hopefully works this time around) i am currently at 59% at 87K+ files left, let it keep DLing over night, but it is still gonna take forever, if this does not work, i might go for a refund and start playing borderlands 2… atleast they got competent support, and their game client doesnt for BS like this down my throat. xD

Edit: Removed an Ascii arrow since the forums dont understand it, lol!

Alpha Dragon.4576:

Temp solution is to remove the bad memory(hence the memtest). As I’ve said game checks your hardware for faults.

1 bad ram stick still should not force the game to re-dl itself :S

If you know your memory is bad thats your problem. Its gonna screw up the repair process anytime it hits that bad segment, and its never going to get out of it because it’ll never end with a correct hash value.

Obligatory brain damage example:
-Let say you can’t comprehend the number 22, and your counting jelly beans that need 50 per jar. Every time you reach 22, you realize something is wrong and have to double check your count to make sure you didn’t make mistake. After several attempts of this, you give up and think something must be wrong with the batch, throw it out, and start from scratch. That is kind of whats happening with the system when its doing a file check.

This, while not entirely accurate, is a lot funnier. http://xkcd.com/371/