Same problem here happens a few seconds after loading into the gameworld only since move to new EU Server.

Through much effort and extremely many DCs, I've managed to get to the stable and train my mount for the day. Phew, what a chore. I can't even get my bearing most of the time before...Unknown Error.

I usually have a second or two before it happens.

zivak.zivakeb17_ESO wrote: »

The problem persists. Has anyone had any luck solving this?

If they keep blaming on Microsoft, I have no idea...

Another day same problem anyone working on it.

No, it is still not working for me.

That's just great. We are unable to log in for the second day without even an update on what's going on, I've just spent another hour on banging my head against the wall trying to figure it out what I can do to log in, tried everything with my router, cleaning my registry, messing with windows settings and nothing, game is still crashing second after logging into game world .
It must be loggin server somehow messed up for many times as someone mentioned in other topic I had to retype my password as it was seeing it incorrect when it wasn't. I feel really gutted, so far I was believer and defending this game but this silence and just leaving it as it is with part of us unable to even use it, this is a blow, huge blow in my belief.

Brabok wrote: »

Did anyone try to flush their DNS cache yet?

Just thinking, same domain name but new IP.....
"How To" under this link:
http://technet.microsoft.com/en-us/library/cc781949(v=ws.10).aspx

For some reason cannot do it, getting 'could not flush DNS resolver cache: function failed during execution' message.

Brabok wrote: »

Did anyone try to flush their DNS cache yet?

Just thinking, same domain name but new IP.....
"How To" under this link:
http://technet.microsoft.com/en-us/library/cc781949(v=ws.10).aspx

have you even bothered reading the 2(!!!!) pages of this thread?

I and at least one person confirmed it did not work...

Just for clarification I have tried:

1.) Flushing my DNS (propertly)
'ipconfig /release', 'ipconfig /renew', 'ipconfig /flushdns', 'ipconfig / registerdns'

2.) Disabling Firewalls both on PC and on the Router

3.) Forwarding all the ports that are associated with the game
24100 through 24131
24300 through 24331
24500 through 24507
443
80

4.)Powercycling the network
(shutting down the router and all connected devices for several minutes, turning the router on, waiting until it recieves new IP, turning on other devices, flushing DNS)

5.)Clean reinstall of graphics drivers
(Completely removing them and all associated registry entries, installing through safemode)

6.) Verifying gamedata

7.) Registry and drive check for errors.

After each step suggested by the support staf, I sent them newly generated report.txt from the Game Consultant tool...

Last time I heard from them, they said they will send my report.txt to their specialists (9hours ago)

I guess analyzing 1400 lines of report is not as quick as one would imagine but I have faith in them

For the record I am from Slovakia (eastern europe) My ISP is T-com, I am using D-Link 2641R Router and I also have the VoIP ports forwarded (9987, 10011, 30033)

Martinus72 wrote: »

If it may help in anything sometimes it crashes to desktop with Runtime Error R6025. And yes I have clean registry, even following wiki-errors splashed my money on errorEND program but nothing can fix this...

That again points to packet loss... If I reckon correctly I was having errors related to assets not loading a few days back - not the same error, but the same problem

Same, I want to play. The most I've managed to be on, is 4 seconds.

ZOS_AmeliaR wrote: »

Hey folks. Thanks for reporting this issue. We're investigating and will get back to you as soon as we have more information or possible troubleshooting steps.

Possible troubleshooting steps??? That's insulting. Myself and countless others now have this "Unknown Error" and boot back to the login screen as a direct result of the server move, so no amount of troubleshooting on our part will do ANYTHING. YOU have to fix this, and quickly.

That's what I got 5 hours ago from their support:

Thank you for getting back to me, I really do understand your frustration, but I think there's been a miscommunication. You ran SFC, a Windows tool, and it detected corrupted files in your Windows installation that it couldn't fix. This is nothing to do with ESO, but I believe they may be the cause of ESO crashing. I'm not sure how you explained it to their support, as in, if you requested help fixing ESO they'll send you here, if you explain you ran SFC and Windows won't fix the errors, they'd have no information that would suggest to send you to us.

I really do want to get this sorted and get you playing again, but I do not have the expertise to troubleshoot an Operating System. I can try, but I do not wish to damage your computer in any way, that is my major concern.

There seem to be a number of suggestions available on the internet for repairing corrupt files SFC has detected but cannot replace, one of which is to repair the installation. Again, I can't provide support on doing this, you do so at your own risk but I can link you to the Microsoft instructions on their website for information: http://windows.microsoft.com/en-IE/windows-8/restore-refresh-reset-pc

In regards to the log file, it's much more verbose than the SFC window will put out. So that I can see what you can see, please complete an SFC scan and take a screenshot of the full completion screen and what it details to you. Please send that back to me so that I can have a look.

Again, I'm really sorry for the frustration this has caused and I will do my utmost to continue to troubleshoot this with you to the best of my ability.

Interesting... before the move ESO ran perfectly fine - after the move I can only play for a couple of seconds, and It's on my end? Nothing has changed on my end.. so go figure.

ZOS_AmeliaR wrote: »

Thank you all for the additional details you've provided in this thread. Just wanted to let everyone know that we are continuing to investigate this issue and will provide more information as soon as we have it. Thanks for your patience!

Thank you for letting us know that at least we aren't left in the dark. This is the real test of patience indeed...