Thread: Launcher problems, error on Updating Game Data

My nvidia card fried (while questing in The Old Forest no less) in my new PC so I had to resort to my old PC until I get a replacement, but I can't start Lotro on it. Just started playing recently and now I can't continue my adventures from level 18. Any help would be greatly appreciated.

This thread: http://forums.lotro.com/showthread.p...%26%2365281%3B is the closest thing I found resembling the same problem, my most recent Launcher log also reads (this is on XP by the way):

00000751.347: downloading file <client_gamelogic.dat-18167> to <E:\The Lord of the Rings Online\Forward/client_gamelogic.dat-18167>
000000751.347: Current system time is Wed Jul 20 02:43:24 2011
000000751.393: ----CRASH REPORT START----
000000751.393: Program fault: ACCESS_VIOLATION (0xc0000005) trying to read from 0x00000008

In my anger 4 days ago I deleted the whole thing and the install files, but then I thought of asking here anyways and redownloaded the client.

So a week ago the problem ws the following: everytime I do a fresh install I get to the point where after the installation the laucher first starts and updates Lotro. It updates the launcher normally, then starts updating game data and gets from 1/1814 to 1814/1814, then displays 0/1814 before shutting down with a generic windows error box.

Even though I recall changing nothing, today I get stuck at 0/14 updating basic game data (pic of the error: http://i.imgur.com/IUBq1.jpg)

PatchClient.log says "Prepared to patch 4025913 bytes of data." then returns "Download failed: error 0x80004005. No alternate URLs. Sorry." for each and every file. I can manually download any file from http://download.lotro.akamai.turbine.com/, I ran pings and tracert's as well, all can safely reach the servers.

To date, I have tried the following to no avail:

-installing w/o AV or firewall

-downloading the client from a 3 different sources

-installing/running in safe-mode

-multiple clean uninstalls with cccleaner/revo uninstall

-reinstalling .net (all versions)

-running turbineregisterGDF.exe

-different RAM sticks

-checking for hard drive errors

-running after deleting the /Forward directory

-running on a new admin user account

-running as admin

-updated all drivers

Any help would be really appreciated!

HiYa !

I like your taste in literature :-)

The error you get is due to an issue with the address in memory that's specified, the thing can't read from the location specified.
Leaves us with a few options, either the data is not in that place, it's not accessible or something is messing about with this address, presumably a device driver or such.

Given, that you ran through a good number of things already, the .NET bits, we're a bit short on options here - how are we with DEP (Data Execution Prevention) ?
That might be a showstopper when it doesn;t let you write or access things in the first place ?
You might want to remove all instances of the 205, 2008 and whatnot installations that you know you can replace again (graphics card usually brings their own flavour, so do several games, you want to becareful here . .) and see to download the client updates into a different place than C:\ as windows can have interestign ideas about what users might be supposed to do on that driive.

Have a look around here for more inspiration ?:
http://www.0xc0000005.com/

Thanks for the reply, I checked DAP and it's on the default (turn on for windows and essential only) option. As for installing into a different directory, that was one of the first things I tried, after the initial update failures I installed onto my older 120gb drive root, needless to say without effect.

For now though, no more error hunting is needed because I managed to boot my new PC with an ancient S3 Trio vid card, hook it up to the old PC via LAN and copy the entire already updated client over. Now all launcher checks pass flawlessly and I can log in (thus cannot investigate the update problem anymore), my only fear is that the moment anything needs to be updated my launcher will crash on me again. Yet by then hopefully I'll get my graphic card replacement and continue to play, once again in sweet High-res mode.