Curse

Lord Sojar · Jun 18, 2008, 12:18 AM // 00:18

New .dat file, update motherboard drivers, particularly if using propriatary drivers the BUS drivers and SATA control drivers. Also update your Network control drivers if you can do that individually. Most motherboard drivers include all of the above as a package.

This is caused via a communication issue with the HDD and the HDD controller. Parts can be lost. If the issue is static, the same result will come out each time (the white boxes) When the write/read processes are complete, it corrupts the .dat file each and every time. As for the jumping NPCs... either that is the same issue or the network traffic controller is screwing with the packets. I lose all expertise when it comes to packet protocols, so I don't want to go there. But if packets are getting screwed up as they travel through the network controller or are processed via the BUS drivers, you will see this type of issue. Just do as I recommended and see what comes of it. If that doesn't work, try flashing over a new motherboard BIOS as well. The BIOS controllers may have some type of issue (there are literally billions of issues that can come from a BIOS problem)

pamelf · Jun 18, 2008, 03:58 AM // 03:58

Thanks. I'll try that tonight and report back.

Dark Kal · Jun 18, 2008, 07:23 AM // 07:23

Download SeaTools (http://www.seagate.com/www/en-us/sup...oads/seatools/) and run it. This is a free program distributed by Seagate to check if your Seagate HD is working properly. Chkdsk and Scan Disk are pretty horrible in my experience, my HD could be on fire and they'd still say "Nah, it's fine.".

It doesn't always have to be the HD, like Rahja said it could be something on the way to the HD. But if the problem persists, something is wrong, the .dat doesn't one day just decide to get corrupted because it doesn't have anything better to do.

Rahja edit: Me being an English nazi I guess, but a part of your post made me look at it about 3 times before I could make heads or tails of it. Sorry if I am stepping on toes, but wanted to clear it up so if anyone else read it didn't think they had gone insane (choice of words and order was all it was) Ok, I am done poking around in your post.

Hysteria · Jun 22, 2008, 12:32 AM // 00:32

It's been my experience with the white block issue and the data archive having to repair itself being a memory issue. I resolved this by switching to a new set but if I switch back it comes right back. It could be the memory its self, a voltage issue, and perhaps a bad power supply. Funny thing is if I run any kind of stress test to check for stability the questionable memory passes with flying colors but for some reason GW doesn't like it. My suggestion if you have this problem is to just relax your memory timings a bit and see if it helps. If it does then eaither replace it or just run the slightly slower timings.