Error Code 3007

Zachary,

The next time you get the error, please post your D3Debug.txt file.

It's located in the main Diablo III game folder. Edit out your account name first though. It's going to appear in a few places in the file.

Elektr0ns,

I might be able to help. The 3007 error just means you were disconnected, it doesn't tell us why. The D3Debug file may provide a clue which is why I ask for it. That's just the first step usually though. If nothing turns up there, we'll dig deeper looking for possible causes.

Zachary,

Could you try doing a trace route to us.actual.battle.net and posting the results?

Follow the steps in this article but for the target, use us.actual.battle.net

https://us.battle.net/support/en/article/performing-a-traceroute

The command would look like this then:

tracert us.actual.battle.net > c:\tracert.txt

I changed it up a little from the article's example.

Make sure you allow time for the trace to run

Zachary ,

Make sure you type the command like this:

tracert us.actual.battle.net > c:\tracert.txt

You may also need to start the CMD prompt up as an administrator. To do that, type cmd into the "search programs and files" box, and when it pops up on the top, right click it and select Run as Administrator

Zachary,

Look on your C drive for the text file. Open it with NotePad and cut and paste the contents here.

Zachary,

That looks pretty bad actually. Try running it a couple more times, using a different destination filename instead of tracert.txt, maybe tracert2.txt and so on.

We want to see if there are still * occurring on the same hops, excluding any after hop 15 which are all normal. When they happen anywhere else, they're indicating packet loss. The high ms numbers also indicate a lot of latency going on.

If several traces are consistent, you'll probably want to contact your ISP.

I'm also curious since you say EU works ok for you, try a trace to eu.actual.battle.net and compare the two.

Zachary ,

I'd like to see the EU trace for comparison to the US one.

Zachary,

Those look much better, we'll have to call the first one a "fluke".

Could you try the steps in the two articles below and then see if it lets you in to the US server?

https://us.battle.net/support/en/article/resetting-network-devices?utm_source=internal&utm_medium=support_forums&utm_campaign=BlizzardCS

https://us.battle.net/support/en/article/ip-release-renew-and-flush-dns?utm_source=internal&utm_medium=support_forums&utm_campaign=BlizzardCS

Zachary,

Hmm, try this support article next.

https://us.battle.net/support/en/article/deleting-the-battlenet-cache-folder-pc?utm_source=internal&utm_medium=support_forums&utm_campaign=BlizzardCS

Zachary,

Try booting in selective startup once and seeing if it lets you connect.

http://us.blizzard.com/support/article/backgroundapps

Zachary ,

I have no idea then, something on your system isn't letting it connect. That would typically be a firewall but your trace route doesn't indicate anything being blocked. Being able to play on the other realms shows port 1119 is open too.

Unfortunately, I'm off in a minute so I'll have to pick this up again tomorrow when I get in at noon Pacific Time.

Zachary,

Could you please list your running processes and services?

Hit the Windows key + R, and type:

msinfo32

Then hit Enter or Ok.

This will bring up System Information.

Click on the + sign next to Software Environments
Click on Running Tasks
Click on one item on the right side
Click on Edit, and then Select All (Or hit Ctrl-A)
Click on Edit, and the Copy (Or hit Ctrl-C)

Then Paste everything into a reply.

Then click on Services
Click on one item on the right side
Click on Edit, and then Select All (Or hit Ctrl-A)
Click on Edit, and the Copy (Or hit Ctrl-C)

Paste everything into the post.

Zachary,,

If you know you can reinstall it again later, can you uninstall "cfosspeed"?

Zachary,

cfosspeed.exe c:\program files\asrock\xfast lan\cfosspeed.exe 2452 8 200 1380 2/22/2013 1:25 PM 6.61.1880.0 1.37 MB (1,441,152 bytes) 2/19/2013 6:18 PM

http://www.cfos.de/en/cfosspeed/cfosspeed.htm

It probably came bundled with your motherboard.

Zachary,

Reboot and try the game again. Run the processes list again to verify cfosspeed isn't running any more. No need to post it.

Zachary,

It should be but I'm just making sure it's not causing a problem.

Let's get a look at the Agent logs being generated when you connect.

First, we'll want to delete all the previous log entries so we're not dealing with really large files.

Navigate to C:\ProgramData\Battle.net\Agent\Logs

Delete everything in that folder which will be all the old log files.

Then try connecting to the US again with the game.

Wait a couple of minutes after it fails and then you should have two new entries in that folder.

Post the contents of each in your reply.

Zachary,

I apologize, I had the wrong folder for you to look in, go to

C:\ProgramData\Battle.net\Agent\Agent.1637\Logs

Delete the log files there then retry the game and post the new log files generated. Allow a minute or two after exiting or you may get an access denied message for one of them as it's being written.

Zachary,

02/22/2013 03:42 PMPosted by Zachary

Is that going to be a problem that I deleted what was in the \Agent\Log file?

No, one of our troubleshooting steps has you delete the entire Battle.net folder containing all the agent files anyway. What's important will be reacquired if it's missing whenever the game launches.

Zachary,

Let's check the Launcher logs next.

Navigate to C:\ProgramData\Battle.net\Client\Blizzard Launcher.1974\Logs and delete everything in there. Run the game again and after a minute or two after it fails, post the new files that are generated.

Zachary,,

There's just no sign of an error being reported anywhere.

It's a bit of a reach but try the steps we have in a sticky post above for people that were getting connection problems a week or two ago mostly. It was a regional problem affecting SouthEast Asia but it can't hurt to try it.

http://us.battle.net/d3/en/forum/topic/7708811770

It's basically just going to set you up to use a free third party DNS service instead of the one your ISP provides.

Zachary,

Ok, login to your Battle.net Account management page and try removing the mobile authenticator you have on the account. Also, do a password change for the account and then test the game. Put the authenticator back on afterwards.

Zachary,

Do you have access to another computer you can try connecting with, preferably on a different internet provider?

Zachary,

It will still help us narrow down the cause I hope. If your laptop does the same thing, it tells us it's most likely not a problem with the PC and instead is related to your connection.

Zachary,

I'm only here between 12 noon and 9 PM Pacific Monday thru Friday.

Post the results when you have them and I'll reply when I can.

Zachary,

Does your laptop work on the sites your desktop doesn't? What happens on the desktop when the sites won't load? Is there any sort of message?

Zachary,

See if there's a proxy being used in Internet Explorer on your desktop. That could explain the weirdness.

Please open up Internet Explorer, click on "Tools" then "Internet Options". Now go to the "Connections" tab and click on the button that says "LAN settings". Make sure that "Automatically detect settings" is checked, and that you are not using a proxy server and then click "OK." If you had to change the setting, try the game again.

Zachary,

It has to be something on the computer and it's likely to be something security or connection-related.

Let me get you to send my your dxdiag and msinfo data. We'll use email as I'd rather not have you post it all here.

Please send an e-mail to [email protected] with the following attached files, dxdiag and msinfo files. The directions below will give you steps to create them.

Click on Start.
Type in DXDIAG into the "Search Programs and Files" box and press Enter or click OK, this will locate the DirectX diagnostic tool at the top which you can then click on to start. When it's done running after a minute or two -
Click on the Save All Information Button (save this file to your windows desktop and name it dxdiag).
Now do the same steps for DXDIAG but use MSINFO32 instead.
When it comes up, select File and Export and save the file on the desktop, calling it MSInfo. Make sure it's saved as a text file, the default setting already.

Send both of these file to the address I gave above as attachments.

Zachary,

Thanks for the files. Unfortunately, nothing really stands out as a possible cause to me. A couple of things are concerning though.

Does your Runescape game run properly? I see a launcher (I assume) for it that's running and showing up in a few places. Do you also use it on your laptop?

You might want to uninstall Splashtop too. It shouldn't be causing any problems but we're just making sure. I use it at home too and it hasn't interfered with any of my apps.

Lastly, it looks like you tried to run Malwarebytes? I see where it had an error running. Malware could be a cause of your problem so it's essential we perform a detailed scan of the system. Have you been able to do so successfully with Malwarebytes yet? You'd need to do a full scan after making sure the app was updated.

Zachary ,

We've pretty much exhausted all I can help with via this format. In addition, it's grown way beyond the scope of what we'd be able to help you with. We know the game works from your location as evidenced by it working on your laptop.

As your desktop is exhibiting connection issues in several ways, I'd have to suggest either taking it in to someone to be checked out thoroughly for malware and see if they can get it connecting to the sites you're having problems with. If it's under warranty, by all means contact the manufacturer and ask them what they suggest. If it's out of warranty and you don't want to spend money on having someone else fix it for you, I'd have to suggest a complete reinstallation of the operating system. I don't say this lightly by the way as I never suggest this in the course of troubleshooting, but you've got a problem that's not going to be easy to resolve unless a tech is able to get "hands on".