Install Error?

[Ham n Cheese]

Didn't know if I should put this here or general. It's WoW related and was hoping someone here could lend me some guidance.

So I'm trying to put the game on a new system and I keep getting various errors. At first I thought it was this WinBorg software I was using instead of normal XP, so this morning I did a CHKDSK and repaired windows, still nothing. So I reinstalled a fresh copy of windows on a brand new HD (160GB Seagate SATA) and had the same problem. CHKDSK and repair on that, and nothing, system was seriously fragmented the first time I ran it, though here is how it looks now... my MFT was also like 98% used until I padded it or something .

I've tried multiple cds as well. My copy, a friend's and my roomate's, still nothing. I moved my folder over the network and would crash after I killed a mob due to some error with WoW sharing violation or something. So I uninstalled on my original system, and moved the fresh install folder over, patcher fucking up with some camera/human shit so still nothing. I've been able to install everything else without any problems, it's just WoW.

Here's a ss of the fragmentation information.


And here's the error I keep getting. It's not always this file in paticular, though it is Texture or Terrain.MPQ more than the others (they all seem to be MPQ's when failure occurs). The first time I installed I made it to CD 3 without an error, I haven't made it past CD 1 since.



Any help appreciated.

[orcmauler]

but i got the same type of errors 2 times while trying to install. I just quit, deleted everything, rebooted and started again.

Took about 5 installs, but I finally got it working. I would also reccommend disabling peer to peer patching, as every time i allow it i get game crashing corruptions. It may take longer, but I havent had a CTD yet.

[Ham n Cheese]

I've never made it to the patcher from the actual cds. Furthest I've got is cd3

[Ham n Cheese]

this is what happens if i log in after copying the folder over the network

[Deathwing]

sounds like bad ram to me, run some ram checking program overnight, that will ferret out any errors if there are any.

[Ham n Cheese]

If so, won't be easy to return ram that boots up a computer and runs everything else but this paticular game.

edit: know a good ram diag program?

going to try this http://oca.microsoft.com/en/windiag.asp


LRAND and ERAND (not sure what that is) failed. 117 Errors total

[Angerz]

Ham, if you think the RAM is bad, try playing another game.

I had a bad ram issue and every program ran fine, except games.

Either way, goofy shit happening on your computer can generally be attributited to bad ram. The list of goofy shit Ive seen it cause is pretty long.

[Frawdo]

Apparently World of Warcraft has a lot of trouble with bad ram. Bad RAM that can work for most things won't work for WoW for some reason. This is really apparent during installation because the decompression of the data is quite RAM intensive.

I had a hell of a lot of trouble installing, luckily I copied the folder over a network from another computer that had it installed, and it runs fine.

I'm not too technical, I'm not sure what to suggest. I just plugged away at it and eventually found a way to make it work. Maybe check the WoW boards; a lot of the bad RAM info is under "Installation Errors" which is a sticky in the Tech. Support area.

[orcmauler]

check the tech support forum, they have the most common causes for the errors, including your #132.

Also check the md5 checksums according to the blizzard specs.

While it may be urban legend, I do know of a few people who had this continuting problem and exchanged the game for another copy and it worked fine.

either way gluck.

[Grayson Carlyle]

Ham, had I known this, I would have pointed you to http://www.memtest86.com/

I had this error on my old computer, I had never had any RAM errors before. Turns out though, that the last 8kb was entirely dead (always returned 0 bits). Apparently, very few things had ever used that part of my RAM, but WoW would use it every time, and fail.

My solution was to build a new computer, but replacing the RAM will do

[Ham n Cheese]

Well... Ram tested bad so it's been replaced, but still can't install from the Cds. Maybe I can play without crashing via moving it over the network though.


edit: ran same ran test again and got "failed'" on LRAND (which I'm still not sure what that is). Guess I'll try a different slot?

[Ham n Cheese]

Ran that one Grayson, looking at it now it reads.


"L1 Cache: 128 - 18118MB/S
L2 Cache: 512k 4501MB/S
Memory: 1024 2107/MB/s
Chipset: nForce3 250 (ECC: Disabled)
Settings: RAM: 200Mhz (DDR401) / CAS: 2-4-2-5 / Dual Chanel (128 bits)"

Then below that are the results through 52 minutes (NOT done yet), keep in mind I bought this ram about 5 minutes ago:

Cached: 1024
RsvdMem: 84k
MemMap: e820-Std
Cache: On
ECC: Off
Test: Std
Pass: 3
Errors: 7
ECC Ers: 0

Tst ----- Pass ---- Failing Address ----------------Good ------------- Bad ------ Err-Bits ------- Count Chan

5 --------- 0 ---- 0003aaf2e20 - 938.1MB --------- 00000000 ----- 00004000 ----- 00004000 ------ 1

5 --------- 0 ---- 0003baf2e00 - 954.1MB --------- 00000000 ----- 00004000 ----- 00004000 ------ 1

7 --------- 0 ---- 0001888deb8 - 392.8MB --------- 627fcc3d ----- 6277cc3d ----- 00080000 ------ 1

7 --------- 1 ---- 0002ecc3478 - 748.1MB --------- dc7f43cd ----- dc7743cd ----- 00080000 ------ 1

5 --------- 2 ---- 0003aaf2e20 - 938.1MB --------- 00000000 ----- 00004000 ----- 00004000 ------ 1

5 --------- 2 ---- 0003baf2e00 - 954.1MB --------- 00000000 ----- 00004000 ----- 00004000 ------ 1

7 --------- 2 ---- 0002fe43198 - 766.1MB --------- dd1d2b1f ----- dd152b1f ----- 00080000 ------ 1

edit: you get the point, up to 16 errors now.

Here's the system:
motherboard
CPU
Ram
hard drive

looking at test 1-9. 1-4 had 0 errors, test 5 had 12, test 6 had 0, test 7 had 4, test 8-9 had 0

ram says its 2-3-2-6 and mine is doing 2-4-2-5. I don't know how to get that middle number down to 3 though.

[Grayson Carlyle]

The ones on the new RAM are intermittant, so they might go away with looser timings or lower clock. Fresh RAM at default settings should be able to run through that flawlessly for as long as you run it.

The middle number is TRAS (I believe, it's been a couple months). Look for it in the BIOS.

[Ham n Cheese]

Well I moved the second stick of 512 to slot 3 (disabling dual mode) and it works now (knock on wood).

[Kilivek]

I got some bad cd's with my copy, had a friend burn me copies.