EQ Crashing 10x a Day+

[Gmonk]

<p><p>Was not sure where to post this, but the EQ2 game client has been crashing more than 3x a day.  This is starting to get very frustrating.  Below is a sample of the multiple EQ2 client crash problem reports that i am starting to amass on my computer.  Any help or assistance would be greatly appreciated.     </p><p><strong>Product</strong></p><p><strong> </strong></p></p><p>EQ2 Client Application</p><p><strong><p>Problem</p></strong></p><p>Stopped working</p><p><strong><p>Date</p></strong></p><p>8/18/2010 1:59 PM</p><p><strong><p>Status</p></strong></p><p>Report Sent</p><p><strong><p>Problem signature</p></strong></p><p>Problem Event Name: APPCRASH</p><p>Application Name: EverQuest2.exe</p><p>Application Version: 1.0.0.1</p><p>Application Timestamp: 4c6b2f74</p><p>Fault Module Name: EverQuest2.exe</p><p>Fault Module Version: 1.0.0.1</p><p>Fault Module Timestamp: 4c6b2f74</p><p>Exception Code: c0000005</p><p>Exception Offset: 0039c15b</p><p>OS Version: 6.0.6002.2.2.0.256.1</p><p>Locale ID: 1033</p><p>Additional Information 1: 8f4e</p><p>Additional Information 2: 700feabdc9bdf2155f413b8220896a1e</p><p>Additional Information 3: 9a6c</p><p>Additional Information 4: b22a3f36663c150f6ebd9cdda258347b</p><p> </p>

[Avirodar]

<p>A few things you may want to check...1) Windows is up to date? (windows update)2) Hardware drivers are up to date? (motherboard/bios/video card)3) Your CPU is not over heating?</p>

[heartstopper]

<p>Mine is not crashing so much as kicking me to character select about every 4th time I go to a new zone. Its annoying as I have to exit out of game completely for it to let me back in.</p>

[Gmonk]

<p>All drivers are up to date, all windows updates done.  Cpu is watercooled...the crashes, see date, were only about once a month starting in August, but since the server merge is when it likes to crash 3-10x a day.....further if you look at the problem report it states its the eq client that is having some sort of critical error causing it to stop working.  Not sure if it is a conflict with vista 64, or graffix issue, etc.</p>

[Gmonk]

<p>lol heartstopper...welcome to eq2, the character boot to select screen when zoning issue has been around for so many years that people actually quit posting about it !!</p>

[Ironcleaver]

<p>I knoew someone that was crashing a lot and I finally narrowed it down to mis-matched memory. The same memory setup ran fine till SF came out. My only guess is that some memory management subroutine was changed someplace.</p><p>What memory do you have installed? Total size and Size per stick? (can be checked with CPUZ)Have you tested the memory using memtest?Another time, I personally started crashing and found one of my sticks went bad. I was able to catch it with memtest.</p>

[heartstopper]

<p>I've been playing eq2 since launch and have not had the kick to character select problem this much. Before the merger it was maybe once every 2 weeks. now I can't manage to zone 4 times without it happening. </p>

[Avirodar]

<p><cite>Gmonk wrote:</cite></p><blockquote><p>All drivers are up to date, all windows updates done.  Cpu is watercooled...the crashes, see date, were only about once a month starting in August, but since the server merge is when it likes to crash 3-10x a day.....further if you look at the problem report it states its the eq client that is having some sort of critical error causing it to stop working.  Not sure if it is a conflict with vista 64, or graffix issue, etc.</p></blockquote><p>Ok good to know all the drivers are up to date etc.But just because a CPU is watercooled, does not mean the cooling is operating correctly. Even though you did not say it, I assume your CPU is actually confirmed to be running at a low temp?Mergers would have done nothing to affect your client side stability. Thats all on SOE's side, and if it caused cold crashes, I would assume a lot of people would be experiencing it.</p>

[Gmonk]

<p>well you did not see the zoning boot to character select really until after DoF expack.  I think it more inherent with the introduction of RoK expack is when all that noise started to happen.</p>

[Gmonk]

<p>42 degrees C</p>

[Gmonk]

<p>again....the application crash is happening within the eq2.exe file.  Guessing there is a problem with programming.</p>

[Banditman]

<p>Boot to character select is not a client crash.  It's some sort of communication issue where the client simply didn't correctly move from one zone server to another.  Totally different issue than what you are seeing.</p>

[Gmonk]

<p>or possibly the entire file may be corrupted?  Anyway....will check back in a few and see if anyone else has posted any ideas or advise that i have not already tried.  Need to get coffeeeee and breakfast going to delve into this more.  <img src="/eq2/images/smilies/136dd33cba83140c7ce38db096d05aed.gif" border="0" /></p>

[Pyrochick]

<p>first off boot to character screen:</p><p>boot to character screen is caused by a minute fluctuation in your connection to the soe servers, consider your connection to soe like a bus line, there is many many stops along the way, if a customer climbs aboard the buss and argues with the driver for a couple seconds the bus will fall behind schedule and the end stop (SOE) will shut their stop down as soon as the bus starts moving they open the stop back up but for that brief interruption a second or two there was no longer a connection the connection closed. that is whats happening with your computer, there are MANY things that can be causing it 99% of the time its your modem or your hub or your router or even your internet lan configuration, check all of these and reboot them once in a while its a good practice to reboot them all at least once a week</p><p>as far as your other complete crashes to desktop that is a whole nother matter:</p><p>I storngly recommend you cleanse your computer, remove all private server software on your computer (could be of any game) and then uninstall eq2 completely even go in and delete the folder after its uninstalled and then reinstall it should fix the problem, error <span >700feabdc9bdf2155f413b8220896a1e is associated with private server authorization, there are other things that can cause it as well but thats whats usually the trigger, personally i would just take advantage that its tuesday pop in the windows disk (AFTER saving your important files) and do a clean install and stay away from those private servers</span></p>

[Tyrus Dracofire]

<p>reason why the pre-orders get delayed, dev team need time to recover what got broken to fix it.</p>

[Brinelan]

<p>Have you done a full file check through the patcher to make sure you dont have any bad files?</p>