Guild Wars 2

After a game crash, I was prompted to “-repair” corrupted GW2 data files…. Which lead to a VerifyResults.log detailing a 8 specific bad file entries.

2013-01-03T03:34:41Z
Client build is 16378 (101)
Manifest build is 16361
Verifying contents of archive...
Verify failed: [0x00011bc6:0x00011bc6] CRC failed
Verify failed: [0x000123e0:0x000123e0] CRC failed
Verify failed: [0x00037fd1:0x00037fd1] CRC failed
Verify failed: [0x00019717:0x00019717] CRC failed
Verify failed: [0x00014c87:0x00014c87] CRC failed
Verify failed: [0x00037ce2:0x00037ce2] CRC failed
Verify failed: [0x00014a7d:0x00014a7d] CRC failed
Verify failed: [0x0001322f:0x0001322f] CRC failed
Duration: 417 seconds
Examined 228463 of 228463 files.
Deleted 8 bad files.
Skipped 2 files (local files, different versions, etc).

Then, the game can play with no issue.

However, trying manually again and again the repair option will lead to the exact same errors (sometimes with a different order for the error lines).

So, unless this is a known issue, I’m pretty sure that my computer hardware is flaky somewhere, but only GW2 is triggering such issues (yes, I had other programs crashing, but occured mainly while GW2 was running).
GW2 is probably quite intensive in its CPU/RAM/GPU usage and something is flaky, but not enough to bring the whole system down.

But:
– memtest86 and other RAM tests are all flawless
– CPU torture tests (prime95) dont fail
– HD bad sector check = OK

GW2 “repair” mode seems the only diagnostic tool that is able to repeat reliably the issue, if any.

(hardware being a 4 year old quad-core2 and a GTX260, rock stable up to now)

I fail to figure out the faulty component! Anybody with a clue or similar experience?

Any 3rd party security software or antivirus interfering? Try running in clean boot mode. (See Part 1.1)

Hi torognek

What did you use to check you hard drive? if it was the built in windows utility then you may want to investigate further for possible hard drive errors.

Thank you for your feedbacks. But I’m now almost sure the problem is in GW launcher itself, and not on my machine.

After failing to find any problem with my disks or Windows-8 setup, I was still getting always the same fishy VerifyResults.log content (see in my top post).

Out of curiosity … I launched the “-repair” mode onto a Mac OSX MacBook (Mountain Lion), with its own installation of GW2. So, a different machine/OS/disk/installation.

= Same error log! The same CRC error offsets!

2013-01-04T00:15:59Z
Client build is 16378 (101)
Manifest build is 16361
Verifying contents of archive...
Verify failed: [0x00011bc6:0x00011bc6] CRC failed
Verify failed: [0x000123e0:0x000123e0] CRC failed
Verify failed: [0x0001322f:0x0001322f] CRC failed
Verify failed: [0x00014a7d:0x00014a7d] CRC failed
Verify failed: [0x00014c87:0x00014c87] CRC failed
Verify failed: [0x00019717:0x00019717] CRC failed
Verify failed: [0x00037ce2:0x00037ce2] CRC failed
Verify failed: [0x00037fd1:0x00037fd1] CRC failed
Duration: 366 seconds
Examined 228463 of 228463 files.
Deleted 8 bad files.
Skipped 2 files (local files, different versions, etc).

So, its a false alarm I guess, there is a problem in the error reporting of the “-repair” option, or its simply misleading !

Personally I wouldn’t believe windows if it said the hard drives passed its test, windows barely scratches the surface so-to-speak when it comes to hard drive error checking.

Tools such as this one are more advanced at detecting problems (even physical ones not relating to the disk surface itself) and have a higher success rate at repairs.

Its not a faulty drive, anyone running verify will see these failing CRC in the log.

I have exactly the same 8 lines after running it here.

2013-01-05T08:06:31Z
Client build is 16419 (101)
Manifest build is 16419
Verifying contents of archive…
Verify failed: [0×00011bc6:0×00011bc6] CRC failed
Verify failed: [0×000123e0:0×000123e0] CRC failed
Verify failed: [0×0001322f:0×0001322f] CRC failed
Verify failed: [0×00014a7d:0×00014a7d] CRC failed
Verify failed: [0×00014c87:0×00014c87] CRC failed
Verify failed: [0×00019717:0×00019717] CRC failed
Verify failed: [0×00037ce2:0×00037ce2] CRC failed
Verify failed: [0×00037fd1:0×00037fd1] CRC failed
Duration: 336 seconds
Examined 228431 of 228431 files.
Found 8 bad files.
Skipped 2 files (local files, different versions, etc).

Yes, its a GW2 faulty log issue. Everything runs smoothly.

If the admins want to close this topic and put this in the FAQ, be my guest. (well, arenanet fixing the “issue” would be even better!)