Client just shuts down

[Drakul]

Have you tried rebooting or checking to see that the game isn't making your processor or video card run too hot?

This started happening to me last week, but I found that my laptop seemed to be overheating... I downloaded speedfan (has built in temperature sensors) and I noticed running EQ was raising the temps in my laptop quite a bit. I have to qualify this by saying that I think the fan inside my laptop may have died recently because it's been running hot in general, but games seem to push it past it's limit lately.

I got a regular housefan and pointed it directly at the hot part of my laptop where the fan is, the temps went down, and EQ stopped shutting down on me for a few days... until last night when EQ crashed three times in a half hour... no errors, just shutdown. After the third time I rebooted my laptop and did not have anymore crashes over the course of the next few hours.

[Threepoint]

This just happened to me as well. Ofcourse while I was kiting a number of hill giants. I knew what the outcome would be as soon as it shut down (naked at bind). I am not too comfortable shutting down chips or cores or w/e. Can anyone verify if that works. Better yet, if there is any other solutions ?

[Onadan]

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

This just happened to me as well. Ofcourse while I was kiting a number of hill giants. I knew what the outcome would be as soon as it shut down (naked at bind). I am not too comfortable shutting down chips or cores or w/e. Can anyone verify if that works. Better yet, if there is any other solutions ?

You're not "shutting down chips or cores" you are setting the executables process threads to use a single processor rather than 2 or 4 processors.

[danno]

Setting the affinity on my computer solved some problems a long time ago, (aka; lack of animation, slow motion, inevitable crashing), but it has not solved the Insta-Client-Poof problem. Atleast not on my computer. I already had the affinities set on my command lines a long time before this problem began affecting me. Not saying it shouldn't be tried, just that it hasn't been the be-all, end-all fix.

[Morticon]

This was happening to me a lot too a month or so ago -- complete client shutdown usually while in combat with a log message about "String not found."

I noticed that it typically happened soon after logging in especially if I hadn't zoned yet. Once I started routinely zoning at least once after logging in, the problem went away. I'm not sure if that is a coincidence or not, but it is painful to test out thoroughly given the xp loss I usually suffer when it happens.

For those that have experienced the problem, does the lack of zoning scenario sound familiar? Does your log file support that?

--Morticon

[Evilmog]

Core issues? I know many MMO's that progressed through-out this decade had to make optimization for Multicore processors, I figured EQ had to be one of them, and would've been implemented sometime before the Titanium pack release.

Could be wrong, but Duo Core has ran this game flawless so far. Although it may just be a ticking time bomb given the time frame you provided.

I'm heading into my 3rd week too, so maybe I can expect this issues over the weekend.

Thanks for the heads up [You must be logged in to view images. Log in or Register.]

[Klath]

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

For those that have experienced the problem, does the lack of zoning scenario sound familiar?

Yes, that seems to fit with what I've observed as well. Zoning may provide a workaround. I'm going to make a point of zoning at least once shortly after logging in and see if I get any more client poofing.

[Klath]

I played around with this a bit today and discovered that I don't get any client-poofing when I log in another character prior to logging in the one I actually want to play.

My meager test cases don't really comprise a statistically significant sample set but, if this problem is causing you grief, you might give this a try and see how it works for you.

[Klath]

I've been running into this problem intermittently for a while now. It's frustrating because it's rare enough that it's hard to know if you've managed fix it.

I've tried the following:

* Setting the process affinity by starting the game like:
cmd.exe /C start /affinity 1 eqgame.exe patchme

* Launching the game through WinEQ (v2.15)

* Using /loadskin to run with different user interfaces

* Updating/removing the maps in the map directory

* Changing/reducing graphics/sound settings (still playing with this)



The string errors I've seen since enabling logging are:

ERROR: String not found. (2105441918)
ERROR: String not found. (-2139061115)
ERROR: String not found. (-2139062144)
ERROR: String not found. (-2139062144)
ERROR: String not found. (-2139062144)
ERROR: String not found. (1904643202)


My system:
Video driver: ATI Radeon 5800 Series v8.732.0.0
CPU: i7 920 @ 2.67GHz
RAM: 12GB
OS: Windows 7 Ultimate (64-bit)


Has anyone been able to successfully eliminate this problem? Given the rarity I've wondered if it might be related to the in-game weather changes but that's little more than a wild guess.

[XDrake]

This has happened to me over a dozen times this weekend. Always during pulls with my Necromancer. I am always pressing something when it happens. It has killed me four times now. [You must be logged in to view images. Log in or Register.] And there are never GMs around to rez me.