*--> Crash <--* MainCli.cpp(510)

#9 - Sept. 6, 2012, 5:31 p.m.

For those who are encountering this issue, here’s what would be super helpful:

Run a memory diagnostic such as MemTest86 (make sure it’s thorough; some memory-errors are fleeting and require sustained use or special conditions).

If the memory diagnostic shows errors, post here saying so! After that, I suggest contacting your manufacturer. = )

If no errors are found, then please open the “Guild Wars 2” folder inside of your Documents folder. You should see one or many files with names similar to “Corrupt-ab48d7ad.dat”. Attach some of those to a post here; if you have many, just pick a few. Also, please attach the file “CorruptArchive.log”, which will be in that same folder.

There’s a good chance that there’ll be too many responses for me to personally examine all of the files, so I apologize in advance if I don’t personally respond to your post. = (

#11 - Sept. 6, 2012, 7:03 p.m.

Yeah, I’ve since learned that too. = (

Maybe it’ll accept them with a .jpg extension instead? Otherwise I’ll have to ask around for an alternative method of getting these files.

#16 - Sept. 7, 2012, 12:47 p.m.

Remembrance.2639:

Paul,

Make sure the 64bit users are using memtest86+ or they will get erroneous results and you guys will chase the issue around in circles.

Thanks for the tip! I haven’t needed to use MemTest86 myself in a while, so I didn’t realize it was forked. x_x

#17 - Sept. 7, 2012, 1:01 p.m.

codeblink.4306:

I get this error all the time also. It happens most often if I am switching between characters, or teleporting to waypoints (I will teleport, and then half a second after the loading screen ends and shows me, it will crash). It’s happened a few times also just before a cut-scene starts.

I couldn’t figure out how to run MemTest86, but here are my corupt dat files as a 7 zip link download: https://s3.amazonaws.com/mypersonals3/guild-wars-2-corupt-dat-files.7z

Codeblink, I took a look at your mountain of Corrupt-*.dat files. = )

There was one completely scrambled file, but every single other file showed the exact same pattern of corruption. It’s always a single-bit error on addresses along the lines of “0x?? ?? ?? 10”, and always the bit for “8”.

I highly recommend that you run a thorough test with MemTest86+. Unfortunately I don’t have a good set of instructions on running that for you. Here are a couple of links via Google, though:

http://www.geekstogo.com/forum/topic/246994-guide-to-using-memtest86/
http://www.overclockers.com/forums/showthread.php?t=409152

Nowadays most computers support booting from USB sticks, and I personally find that to be much easier than digging out a CD-R or hunting at garage sales for a floppy-disk drive. ; )

#32 - Sept. 10, 2012, 3:27 p.m.

paradisegamer.7034:

Here’s my theory. Where other games may find and skip over bad sections of your RAM, GW2 says, “Hey, sorry buddy, I’m gonna crash now.” 12 GB out of my 16 GB of RAM were a-ok. For what reason GW2 works this way and none of my other games do, I’m not sure. But there are a ton of people playing this game. If that’s what GW2 is programmed to do, I wouldn’t be surprised to see a fair amount of people come out of the woodwork who don’t realize one of their sticks is bad. I know I sure as heck didn’t.

The main reason the game is vulnerable to errors like this is because we store the data in a compressed format on disk. Since the whole point of compression is to reduce redundant information, it can’t tolerate even small defects like a single-bit error. If you flip a single bit, you could end up interpreting all of the following data incorrectly and end up with garbage. To ward against insidious issues like this, we validate the data as we stream it from disk. In many cases, we’re not able to recover from bad data, so we do the best we can: crash and ask the user to repair Gw2.dat the next time they run the game.

I’m very happy to hear that you’re back in the game, running without issue! Hopefully we can get everybody else back in as well. = )