When this happens to me, it usually fixes itself within a couple of minutes to about thirty. I haven't found any problems after logging back in when it finishes.
68.83.45.183 16:10, 19 July 2007 (CDT)
- For me, it is usually 20-30 minutes. It is hellishly boring and obscenely vexing. And it happens somewhat frequently.
- It has happened:
- When logging out.
- When hitting the X to quit.
- When shutting down the computer because it crashed.
- --
Skax459 16:31, 24 November 2007 (UTC)
- It near always happens to me. It's rarer for me to NOT have RDA :P ---
-- (s)talkpage 17:03, 24 November 2007 (UTC)
- It near always happens to me. It's rarer for me to NOT have RDA :P ---
I got this once, and it wasn't able to fix all of the problems. Uninstalling and reinstalling the game did fix them. Quizzical 09:27, 28 November 2007 (UTC)
- I only got this once from rebooting my computer after a crash. Took about 30 minutes to repair. Silver Sunlight
09:43, 28 November 2007 (UTC)
- If it doesn't fix the problems, perhaps -image. After a RDA and a problem still persist, I restart GW, so it does another RDA (see my previous comment), and that fixes it too. But if you can't force it, an -image should do. ---
-- (s)talkpage 19:27, 2 December 2007 (UTC)
- If it doesn't fix the problems, perhaps -image. After a RDA and a problem still persist, I restart GW, so it does another RDA (see my previous comment), and that fixes it too. But if you can't force it, an -image should do. ---
Potentially worse problem[]
I was getting game crashes, resets and RDA constantly a year or two ago. As it turns out, I had a bad RAM module, which was potentially causing more damage than just frustrating my efforts to play. If you are getting a lot of graphical glitches and data repairs, run a memory testing program. SarielV 02:23, 21 December 2007 (UTC)
- ^^That was exactly my problem, kept getting the error at least once a day, and it went away when I replaced my RAM.
- I bought a laptop with bad RAM chips, and had to buy new ones, because the shipping charges of sending it in for repairs would have cost more than the chips themselves... We ran a RAM test, and it definitely pointed to bad RAM, but of course tech support from India didn't even know what that is. >_< Next time I'm telling him to hit Alt+F4 quickly 5 times to bring up the built in memory test. >:D RoseOfKali 11:50, February 1, 2011 (UTC)
Possible causes[]
- Data error (bad sectors on hard drive due to:
- Turning off whilst writing to HDD
- Wear and tear of the drive
- Hardware
- RAM module
- Possible future system consequences.
Solutions
Run the repair when it appears. If it repeats:
- defrag gw.dat
- Rename GW.dat to GWbackup.dat and run a -image
- Reboot and run chkdsk RT | Talk 11:52, 13 January 2008 (UTC)