Eqgame.exe crash on exit with WinEQ 2.0 Pro

WinEQ 2.0 Pro discussion and support

Moderators: Lavish Software Team, Moderators

Post Reply
Mannwin
GamingTools Subscriber
Posts: 18
Joined: Tue Jul 13, 2004 10:55 am

Post by Mannwin » Fri May 19, 2006 6:15 am

If this will help, today's crash on exit had the following:

The instruction at "0x01b71976" referenced memory at "0x0000003c". The memory could not be "read".
Top
Maliki2
GamingTools Subscriber
Posts: 43
Joined: Tue Jul 13, 2004 12:18 am

Post by Maliki2 » Fri May 26, 2006 12:06 pm

Having same error still with CTD.
Top
drynyks
GamingTools Subscriber
Posts: 10
Joined: Fri Aug 05, 2005 12:00 am

Post by drynyks » Sat May 27, 2006 2:09 pm

For this reason I have been letting it slide for a bit while I work on other pressing issues
This crash is becoming a pain for me. Switching accounts sucks. I have to do it all the time and the crash slows everything down. Please fix it =)

Thanks,
drynyks
Top
Kaycee
Non-Subscriber
Posts: 61
Joined: Thu Jul 08, 2004 9:55 pm

Post by Kaycee » Mon Jun 05, 2006 5:35 pm

Just curious if there has been any update regarding this issue with wineq2 ?

Kaycee
Top
fearless
Non-Subscriber
Posts: 345
Joined: Mon Jul 19, 2004 5:27 pm

Post by fearless » Mon Jun 05, 2006 6:23 pm

Last I heard it was still being tracked down / waiting to be fixed.
Top
nullz
GamingTools Subscriber
Posts: 1
Joined: Thu Feb 10, 2005 6:21 am

Post by nullz » Wed Jun 07, 2006 4:50 am

Well still have the crash problem but.........it is nothing that stops me from playing and only happens when i am quiting so does not bother me that much 'casue i was quitting anyways .......and i know Lax will get it fixed sooner or later ..........and on all the other problems that have occured in the past 2 years have been fixed quickly and effecintly......GREAT JOB Lax keep up the great work!!!!!!!!!
Top
ronis
GamingTools Subscriber
Posts: 75
Joined: Wed Nov 02, 2005 11:49 pm

Post by ronis » Fri Jun 09, 2006 4:19 pm

Lax, Im getting this problem too and have been for quite some time with EQ1. After carefully reviewing your replies to other people I would like to tell you that my problem is identical but I am NOT out of video memory or system memory. I run 3 accounts and my video memory hovers at 250ish MB and system memory hovers around 750ish MB and I still get the "EQGAME.exe has encountered a problem and needs to close..." on nearly every time.

If you need me to post my full info I will.
Top
kebienu
GamingTools Subscriber
Posts: 10
Joined: Sat Apr 23, 2005 9:10 am

same

Post by kebienu » Fri Jun 09, 2006 5:15 pm

i am having the same problems when i exit to.
Top
Lax
Owner
Posts: 6634
Joined: Fri Jun 18, 2004 6:08 pm

Post by Lax » Mon Jun 19, 2006 3:15 pm

I've been trying to track this thing down for a while now. Basically, EQ is resetting the direct3d device while exiting to server select, and failing to do so unchecked (then EQ crashes during some sort of assumption that the display is valid). When this happens at other times, you would get a "ResetDevice() failed" box from EQ instead of this all-too-fun seemingly random crash.

Technical mumbo jumbo follows:
Anyway, with some investigation, this crash is due to EQGraphicsDX9.dll allocating some resources (specifically, index and vertex buffers), and not releasing them before attempting to reset the device. Direct3D debugging outputs this

Code: Select all

Direct3D9: (ERROR) :All user created D3DPOOL_DEFAULT surfaces must be freed before Reset can succeed. Reset Fails.
What this means to ME is that this issue does not appear to be related to WinEQ 2 at all, but a bug of some sort in EQ's Direct3D handling that leaves some resources unfreed. But, given that everyone here says it is, I will keep trying to find the solution under the assumption that it is somehow WinEQ 2's fault. I'll keep you posted.
Top
uevrwndry
Non-Subscriber
Posts: 11
Joined: Tue Sep 13, 2005 1:41 pm

Post by uevrwndry » Thu Jun 22, 2006 11:06 am

After reading Lax's last post I would like to add that I do NOT have this issue when I run normal EQ without WinEQ2. The crash on exit only happens when I am using WinEQ2. Since it never happened to me when running just normal EQ, I figured it to be a WinEQ2 problem and posted it as such. :?
Top
KlangFV
GamingTools Subscriber
Posts: 1
Joined: Wed Jul 14, 2004 2:31 am

Post by KlangFV » Mon Jun 26, 2006 1:16 am

Having the same problem, certainly not a showstopper.

Is EQ doing something cheesy to catch the error and hide it Lax? They did that push to the new direct x version, wonder if that's part of it...

Good luck, if you need people to help test let me know.
Top
Lax
Owner
Posts: 6634
Joined: Fri Jun 18, 2004 6:08 pm

Post by Lax » Mon Jun 26, 2006 2:34 am

Heh. Unfortunately this crash is easy to reproduce, but not to actually figure out the problem, because the crash is well after the actual problem. Like I said, working on it..
Top
SamDaMan
GamingTools Subscriber
Posts: 42
Joined: Wed Jan 26, 2005 3:41 am

Well...

Post by SamDaMan » Tue Jun 27, 2006 9:40 am

Ya I get some kind of error message on all six computers every time I log out also, no big deal though, dosn't really effect me. Something like "eqgame has causes errors and will be closed by windows" or something. Happens 100 percen of the time, I have win2K.

Again though, it has no effect on me at all.
Top
Lax
Owner
Posts: 6634
Joined: Fri Jun 18, 2004 6:08 pm

Post by Lax » Wed Jun 28, 2006 1:51 pm

I have observed that this problem may have subsided with WinEQ 2.14.

Let me know if it's still happening 100% of the time
Top
SamDaMan
GamingTools Subscriber
Posts: 42
Joined: Wed Jan 26, 2005 3:41 am

Well

Post by SamDaMan » Mon Jul 03, 2006 11:53 am

Still happening ... 100percent of the time.

Only clue I can offer is if I do /camp desktop on all three toons on a computer within a short time of each other I only get one error message total, but if I wait awhile I get the error message for each toon.

Again though, I can't see any real downside to it cept having to close the error window lol ..
Top
Post Reply

Return to “GamingTools Members::WinEQ 2.0 Pro”