Game closes down - no error msg.

[Thetan]

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

No, I'm using the standard Titanium client and I'm running it on a intel quadcore. I never had any problems whatsoever, until this week. The only noticeable change is that I downed the new Service Pack for Windows 7.

Leave it to MS to screw up to OSs in the same week.

They messed up Windows Mobile updates this week too.

Here's a link to DL WinEQ2: http://www.lavishsoft.com/downloads.php?p=wineq2

Give it a try and see if it helps.

[fugazi]

Thanks, installed it and I'll try it out for a little. I'm sick and tired like shit, so it's a time as good as any to play some EQ.

[mwatt]

Just adding another data point to the pot, if you will pardon my mixed metaphor. I too am having this problem - it happens about 0 to 2 times per play session. Normally it happens when I have engaged a mob and am running for distance, or else kiting with my Necro. Rathe Mtns has been the zone I've experienced this in.

I run Windows 7 with SP1. If I remember right, I did crash to desktop once or twice in South Karana with a Druid or Shammy, but it truly does seem to be more frequent after the service pack.

One last point of possible interest. I used to use the SoF client. The problem never happened for me with SoF, only Titanium. I should also note however, that when I was running SoF, it was before the Windows 7 SP1 was installed.

[Rasah]

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

Normally it happens when I have engaged a mob and am running for distance, or else kiting with my Necro.

I have noticed it in the following activities:

Running while kiting a DoT'ed mob.
Casting DoTs on a rooted mob.
Watching a pet beat on a mob.
Looting a corpse.

So moving isn't a requirement, nor is having DoTs on something.

I used to believe that if it happened once after opening up my laptop, it wouldn't happen again for that session, but 2 nights ago I dropped twice. So that theory is out the window.

I have WinEQ2, and that hasn't solved the issue.

[Omnimorph]

I had this happen to me on a draco pull. I was all ready to cure people's diseases, then boom, desktop.

Oh well XD

[Funkyguru]

I used to be a 67 pound assling, then I tried this solution!

1. Locate your EQ folder
2. Open your EQ folder then create a new text doc within it
3. Open the text doc you just created and copy/paste in the following line:

c:\windows\system32\cmd.exe /C start /affinity 1 eqgame.exe patchme

3. Save the text doc then right-click it and rename as eqgame.bat
4. Run the eqgame.bat file you just created (Or make a shortcut on your desktop, whatever tickles your fancy)

This issue was haunting me for ages and was totally random; some days it would happen several times in short span and then not again for several days. I also tried lowering the frame rate to ~30 fps which 'appeared' to lessen the frequency of the issue to some degree (Pretty hard to tell considering how random it had been) but did not resolve the issue completely.

After some investigation I found out that the issue might stem from the fact that EQ, at least the Titanium version I am using, can have some kind of conflict with multiple cores as it was never designed specifically with them in mind. The .bat basically forces EQ to run on 1 processor (/affinity 1 being CPU 0). After trying this solution I've not had the issue occur and it's now been ~8 weeks (I would of posted sooner but really wanted to be sure that the problem wasn't occurring anymore). No guarantees, of course, but I feel confident that this should resolve the issue at least for some (assuming it was resulting from the same cause as mine).


No more desktop sand kicked in this assling's face!


Adding my system info for comparison if that helps anyone.

------------------
System Information
------------------
Time of this report: 3/6/2011, 00:56:03
Machine name: KELLY-PC
Operating System: Windows 7 Professional 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_rtm.101119-1850)
Language: English (Regional Setting: English)
System Manufacturer: System manufacturer
System Model: System Product Name
BIOS: BIOS Date: 08/27/10 17:41:31 Ver: 08.00.15
Processor: Intel(R) Core(TM) i7 CPU 870 @ 2.93GHz (8 CPUs), ~3.7GHz
Memory: 8192MB RAM
Available OS Memory: 8190MB RAM
Page File: 3484MB used, 12894MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7601.17514 32bit Unicode
------------------


Cheers!

Bottom - Assling Drood - lvl 50 - Project 1999 Server

[Rasah]

Thanks Funky. I have been following this issue in the *multiple* threads on the topic. I have seen corrections similar to this, as well as people suggesting to use WinEQ, and a number of other ideas. When I installed WinEQ, that helped a little, but didn't fully fix it.

I thought I read that some people didn't get the success they hoped for with your solution. I will try it, simply because my gameplay has been overly cautious due to the fear of dropping.

Thanks for the detailed fix.

[aggresor223]

I used to get it some times, then it stopped. Now every time I log my rogue in it crashes about a minute later. I logged my bard in and sat in the same zone for hours and no crash. So Weird.

[mwatt]

Funky,

I have done as you suggested. So far so good, though obviously this will take some time to prove out. Still, this solution has "the ring of truth". I fully expect this to solve the problem and encourage others to try the same solution.

[mwatt]

Well, ring of truth was a bit premature. I crashed again.

GOOD NEWS however. There is a patch for issues with games crashing if they are using DirectX 9.

I downloaded and installed, so far so good. You can probably find it under your optional downloads.

See http://support.microsoft.com/kb/2488113