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?
