the dreaded error 1017
 

I have read the troubleshooting post and countless others, I cannot figure it out!

I have disabled my firewall, connected directly to my modem
I have disabled AMD turbo core
I have manually set clocks and voltages to stock
I have downloaded and installed EQ titanium FRESH
I have added the eqemu login to windows host file
I have flushed my DNS
I have ran in compatibility mode with admin
I have a fresh install of windows 8.1

I get the same error every time!
I have tried any other EMU server and none will allow me to connect its the same errore every time.

2014-08-17 14:49:06 WorldAuthenticate: Initiating Login.
2014-08-17 14:49:09 Networking: Connection Closed [0] with 0 pending bytes.
2014-08-17 14:49:09 *** ERROR: WorldAuthenticate. My message arrival was NULL, the net has been shutdown.
2014-08-17 14:49:09 *** WorldAuthenticate. Checkpoint 3.

please someone give me some kind of clue on what I should do! I want to play

figured it out, this goes for anyone with an AMD processor

I have a 9590 that runs stock @ 4.7ghz
eq will not run with anything over 4.2ghz
I tried dropping my clock to 4.2ghz and boom EQ works.

How did you end up under-clocking? My brother has same setup and the 1017 error, but when he went to under-clock his computer wouldn't come back. He had to reset CMOS the PC to boot again.

Is this true? I never would have guessed the game would be sensitive to CPU frequency like that!

Is it just the freq or does it have to do with options on the chip?

I also had this same error yesterday. I installed a new motherboard. the CPU was clocking in at 4.35 ghz I throttled it down to just under 4 ghz and I can magically connect to the game again. Absolutely amazing.

msi afterburner should let you underclock.

I have an AMD 8350 CPU. Core is 4GHz and Turbo is 4.2. I've experienced no issues at all other than the occasional video chop, which is going to be fixed by WinEQ2 when I install it later today.

you can use AMD overdrive software to under clock may want to turn the power down a little also from under clocking though it is not essential it dose deal a lot less heat that way ...

Just to confirm, put the same install on 3 different machines.

1017 error exists on the one that has a 4.7 clock (not over clocked, standard clock speed).

As soon as I under clock the machine, game loads with no 1017 error.

Rebooting and changing my bios each time I want to play is sorta lame, but it does address the issue.