Crashing Every Single Time I change Zone

[rydarthewizard]

My client is crashing every single time I change zone... looks like it's since I bought the last expansion

So I tried to reinstall the whole game....

And tried to disable every kind of form of firewall...

really wondering what's going on

[rydarthewizard]

btw this is only in the new zone

[TSR-JoshuaM]

I've received similar reports recently regarding these exact symptoms and have sent it up to be looked in to.

It may not be an issue on your end but lets cover the basics here.

Firewall/Anti-Virus/Security suite software must be disabled or configured in a manner to allow EQ2 to send/receive data.  We do not directly support these types of software and what I do suggest is disabling them while playing EQ2.

Next, you don't seem to be having a connectivity issue but there have been incidents of the game being partially blocked resulting in similar issues.  We also do not support routers directly but I can provide the port information needed to configure it yourself.

Sony Online Entertainment does not support the use of firewalls and proxies, including cable/DSL NAT routers, campus and office networks, or any type of Internet connection sharing services. However, in an effort to assist you in configuring your systems on your own, we would like to provide the following information which may help you in setting up your firewall to work with EverQuest II

EverQuest II Station Launcher and Patch Servers:

A TCP connection is initiated from a Station Launcher client port greater than 1023 to patch.station.sony.com port 7000. 

A UDP connection is initiated from the Station Launcher client port greater than 1023 to sdlaunchpad1.station.sony.com and sdlaunchpad2.station.sony.com port range 3016-3021 and 9700-9703. 

EverQuest II Patch: 

A TCP connection is initiated from the EverQuest II client port greater than 1023 to patch.everqeust2.com, abepatch.everquest2.com, laepatch.everquest2.com, or amspatch.everquest2.com at port 7010. 

Everquest II Game Client:

UDP connections are initiated from the EverQuest II client port greater than 1023 to servers on UDP ports 9100, and UDP ports in the range 32800-33000 

Additionally, ICMP messages type 0 (echo reply), 3 (unreachable), 8 (echo request) and 11 (expired) should be permitted bi-directionally between the client PC and the EverQuest II servers. 

EverQuest II Servers Subnets:

There are multiple IP addresses for the Patch and Station Launcher clusters, and they may change as the network demands, so check often using a DNS lookup tool if you provide a specific firewall rule for these services. The EverQuest II server IP addresses are currently in these subnets: 64.37.158.*, 199.108.2.*, 199.108.12.*, 199.108.202.*, 199.108.203.*, 195.33.135.* 

[rydarthewizard]

Okay it's getting weired but better

It seems my problem is attached to only ONE character..

because I took another char to the newer zone with no problem at all

[rydarthewizard]

it looks like it's my new LoN Mount that is causing the problem..since I switched back to an older mount, I had no problem at all

[TSR-JoshuaM]

What mount is that specifically?  I'll see about reproducing the issue so we can get it fixed asap.

[Cragmyre]

I'm having the same exact problem.  When using the LoN mount "Steed of the Death Mount" as either my mount, or my appearance, I crash every single time when zoning.  If I remove that mount, I can zone normally.  I hope this information will help resolve the issue.

[TSR-JoshuaM]

Can you PM me your Station Name?  I want to try to reproduce this issue and would like to use your character to do it

[Dharkone]

Same issue here on a new Win 7 64 bit machine, GTX580, 6GB memory, no firewall, Netgear router....

Log Name:      ApplicationSource:        Application ErrorDate:          5-4-2011 21:35:27Event ID:      1000Task Category: (100)Level:         ErrorKeywords:      ClassicUser:          N/AComputer:      Marcel-PCDescription:Faulting application name: EverQuest2.exe, version: 1.0.0.1, time stamp: 0x4d935dddFaulting module name: EverQuest2.exe, version: 1.0.0.1, time stamp: 0x4d935dddException code: 0xc0000005Fault offset: 0x0066f1d3Faulting process id: 0x9e4Faulting application start time: 0x01cbf3c835e1c015Faulting application path: D:EverQuest IIEverQuest2.exeFaulting module path: D:EverQuest IIEverQuest2.exeReport Id: db1d13e1-5fbb-11e0-bea8-f46d040458e1Event Xml:http://schemas.microsoft.com/win/20...08/events/event">          1000    2    100    0x80000000000000        994    Application    Marcel-PC            EverQuest2.exe    1.0.0.1    4d935ddd    EverQuest2.exe    1.0.0.1    4d935ddd    c0000005    0066f1d3    9e4    01cbf3c835e1c015    D:EverQuest IIEverQuest2.exe    D:EverQuest IIEverQuest2.exe    db1d13e1-5fbb-11e0-bea8-f46d040458e1 

[TSR-JoshuaM]

Cartaphilus@Runnyeye wrote:

Same issue here on a new Win 7 64 bit machine, GTX580, 6GB memory, no firewall, Netgear router....

Log Name:      ApplicationSource:        Application ErrorDate:          5-4-2011 21:35:27Event ID:      1000Task Category: (100)Level:         ErrorKeywords:      ClassicUser:          N/AComputer:      Marcel-PCDescription:Faulting application name: EverQuest2.exe, version: 1.0.0.1, time stamp: 0x4d935dddFaulting module name: EverQuest2.exe, version: 1.0.0.1, time stamp: 0x4d935dddException code: 0xc0000005Fault offset: 0x0066f1d3Faulting process id: 0x9e4Faulting application start time: 0x01cbf3c835e1c015Faulting application path: D:EverQuest IIEverQuest2.exeFaulting module path: D:EverQuest IIEverQuest2.exeReport Id: db1d13e1-5fbb-11e0-bea8-f46d040458e1Event Xml:http://schemas.microsoft.com/win/20...08/events/event">          1000    2    100    0x80000000000000        994    Application    Marcel-PC            EverQuest2.exe    1.0.0.1    4d935ddd    EverQuest2.exe    1.0.0.1    4d935ddd    c0000005    0066f1d3    9e4    01cbf3c835e1c015    D:EverQuest IIEverQuest2.exe    D:EverQuest IIEverQuest2.exe    db1d13e1-5fbb-11e0-bea8-f46d040458e1

Same Mount too?

[Dharkone]

Yes same mount....

Tonight I will switch to another one and see if the issue still occurs.

[Dharkone]

Did some zoning last night with a different mount and you are right, problem solved! This is quite a strange issue...

[TSR-JoshuaM]

I believe I've gathered an ample amount of data on this.  It's been reported and testing is underway, we'll have that mount looked in to very deeply and any issues resolved as soon as possible.  I'll use this thread to update if I do receive further information on it or if I need to request anything from you all towards fixing this.

[TSR-JoshuaM]

We've got most of the data we need in testing now, a fix is being developed, tested, and prepared for a live push in the very near future.  I don't have exact dates yet but the mount issue will be fixed soon!