Miscellaneous: Client crashing to desktop attempting to zone into Kithicor Forest

[Proven Guilty]

As the title states, seems to happen on any character at any zoneline into Kith. This happened years ago on Blue with my warrior Provenx.

I just made a new cleric named Silverstone and I've also made a druid named Macaulay who are both halfling starting in Rivervale.

Macaulay is in zone crash loop but I have not yet zoned Silverstone (I'm going to try Misty Thicket).

I'm a pretty technical guy (operations engineer for a large CDN network) so there is a lot I can do to help if you guys wanted to try to troubleshoot/debug this issue.

I can probably get this system running in Wine under Linux, but I'm currently using Windows 7 64bit. I've replaced the zone file to eliminate the chance it was corrupt (can someone give me an md5 or sha sum if yours works/zones fine?) and my installation was from my original titanium CDs.

I've also moved the EQ folder to a different location on the hard drive to eliminate UAC permissions issue but no joy.

I'm open to ideas if there is anything you guys can suggest or if you have time, I can jump on google hangout if someone wants to try to grab a packet capture. After some searching on the forums, it looks like I may not be the only one who's ever experienced this problem.

[Man0warr]

Delete the Kithicor zone file and replace it with one from the install folder/disc.

[Proven Guilty]

Hello Man0warr, thank you for taking the time to post a reply.
Unfortunately, this is something that has already been attempted as stated in previous post, but I'm open to additional suggestions (or if someone could please provide an MD5 or SHA sum of their working kith file to rule this out as a problem).

[Man0warr]

That usually fixes the issue for me - Kithicor (and EK) are extremely glitchy zones on this server.

Don't have any other solutions, outside of petitioning the GMs to move your characters out of Kithicor.

[kaev]

Originally Posted by Proven Guilty [You must be logged in to view images. Log in or Register.]

Hello Man0warr, thank you for taking the time to post a reply.
Unfortunately, this is something that has already been attempted as stated in previous post, but I'm open to additional suggestions (or if someone could please provide an MD5 or SHA sum of their working kith file to rule this out as a problem).

$ md5deep kith*
2fe7d416fb372504582fe3bc34c4511d /cygdrive/e/Program Files/Everquest/kithicor.s3d
4f89de1768155c47e9765c7a32b97ba8 /cygdrive/e/Program Files/Everquest/kithicor_chr.s3d
3441f6e50ed2e1901eec5e46b6824c17 /cygdrive/e/Program Files/Everquest/kithicor_chr.s3d.old
624f148f30d6e1ea552cb071061a615d /cygdrive/e/Program Files/Everquest/kithicor_chr.txt
31e305cab8a2ae7e98309a60dc325a7c /cygdrive/e/Program Files/Everquest/kithicor_obj.s3d
1778f42836e414d04040942c52a42ad7 /cygdrive/e/Program Files/Everquest/kithicor_sndbnk.eff
4907b00b6b7b5919f3ab028ee16c384d /cygdrive/e/Program Files/Everquest/kithicor_sounds.eff

[Proven Guilty]

Verified all md5 hashes.
Switched to RAM disk via AMD to eliminate IO from the equation.
Copied files off to fresh OS install of Windows 7 on a different computer.
Tested from a fresh installation of Titanium.

Continues to crash zoning in Kithicor Forest. I am completely stumped.

[Proven Guilty]

This was fixed by simply repeating all efforts over again.

1. Reformat PC
2. Fresh install of titanium
3. Ran the script that allows you to shrink your p99 installation down under 2GB
4. Tested first with stock UI; fixed. Added duxa ui; still fixed.

I'll never fully understand the real root cause as both installations seem to have the same md5 hash for the zone files and passed the p99 file scans for spells and etc, but something was different causing only kith to crash.

In a related note; I soon after started having problems with disciplines activating that would crash me to desktop, whether I used a disc or someone else did.

I was able to also trace this back to having a separate window for discipline messages where I was filtering them out. Once I closed this ui window, the problem went away.