Page 1 of 3
game crash question
Posted: Mon Aug 06, 2007 4:27 am
by Night Hawk
If eq crashes, and the debugger returns something related to eqgame.exe itself, that is just a general EQ-related crash, correct?
For example:
Code: Select all
(7e4.cd4): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
eax=064e3210 ebx=0314cff8 ecx=00000224 edx=0000008c esi=00000000 edi=00000224
eip=00600070 esp=0012e6c8 ebp=0314cff8 iopl=0 nv up ei pl nz ac po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010212
*** WARNING: Unable to verify checksum for C:\Program Files\EverQuest\eqgame.exe
*** ERROR: Module load completed but symbols could not be loaded for C:\Program Files\EverQuest\eqgame.exe
eqgame+0x200070:
00600070 8b01 mov eax,dword ptr [ecx] ds:0023:00000224=????????
Posted: Mon Aug 06, 2007 4:40 am
by ieatacid
Not necessarily.
Posted: Mon Aug 06, 2007 4:44 am
by ieatacid
Custom plugins?
Posted: Mon Aug 06, 2007 12:51 pm
by Night Hawk
Hmm ok. I only ever get this crash, usually after I zone a bunch of times. I figured it was just EQ-related, but thought I would ask. I saved the crash info from what I posted above.
Using the latest zip as always.
Debugger view:
Code: Select all
[MQ2]MQ2Map::OnRemoveGroundItem(2)
[MQ2]MQ2Map::OnRemoveGroundItem(3)
[MQ2]MQ2Map::OnRemoveGroundItem(5)
[MQ2]MQ2Map::OnRemoveGroundItem(63)
[MQ2]MQ2Map::OnRemoveGroundItem(310)
[MQ2]MQ2Map::OnRemoveGroundItem(373)
[MQ2]MQ2Map::OnRemoveGroundItem(381)
(7e4.cd4): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
eax=064e3210 ebx=0314cff8 ecx=00000224 edx=0000008c esi=00000000 edi=00000224
eip=00600070 esp=0012e6c8 ebp=0314cff8 iopl=0 nv up ei pl nz ac po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010212
*** WARNING: Unable to verify checksum for C:\Program Files\EverQuest\eqgame.exe
*** ERROR: Module load completed but symbols could not be loaded for C:\Program Files\EverQuest\eqgame.exe
eqgame+0x200070:
00600070 8b01 mov eax,dword ptr [ecx] ds:0023:00000224=????????
r:
Code: Select all
eax=064e3210 ebx=0314cff8 ecx=00000224 edx=0000008c esi=00000000 edi=00000224
eip=00600070 esp=0012e6c8 ebp=0314cff8 iopl=0 nv up ei pl nz ac po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010212
eqgame+0x200070:
00600070 8b01 mov eax,dword ptr [ecx] ds:0023:00000224=????????
kv:
Code: Select all
ChildEBP RetAddr Args to Child
WARNING: Stack unwind information not available. Following frames may be wrong.
0012e6c4 00419081 7c802442 00000001 004ddc3e eqgame+0x200070
0012e6d0 004ddc3e 064e3210 7c802442 0012e7ec eqgame+0x19081
*** WARNING: Unable to verify checksum for C:\Program Files\MacroQuest2\Release\MQ2Main.dll
0012e6f4 0302a850 0012e790 00000048 008fc5f0 eqgame+0xddc3e
0012e714 004e0dd1 006ebe28 0063ea4a 004e0dff MQ2Main!memchecks+0xd0 (FPO: [Uses EBP] [5,1,0]) (CONV: cdecl) [c:\program files\macroquest2\mq2main\mq2detourapi.cpp @ 240]
0012e7ec 0051e526 002d0272 00400000 00520cd9 eqgame+0xe0dd1
0012fc8c 00523724 0084dac7 0012fe06 00000000 eqgame+0x11e526
0012fca8 7c91e85c 00245740 00245740 0354fee5 eqgame+0x123724
0012fda8 006b62b3 0012ffb0 006bd9ae ffffffff ntdll!LdrDisableThreadCalloutsForDll+0xab1
0012fdb0 006bd9ae ffffffff 00523dfe 00400000 eqgame+0x2b62b3
0012ffc0 7c816fd7 ff4e525c ff343841 7ffd4000 eqgame+0x2bd9ae
0012ffe0 7c839aa7 7c816fe0 00000000 00000000 kernel32!BaseProcessStart+0x23 (FPO: [Non-Fpo])
0012ffe8 00000000 00000000 00000000 006a6129 kernel32!_SEH_epilog+0x18
Posted: Mon Aug 06, 2007 1:04 pm
by dont_know_at_all
No, it's not EQ. You either have bad hardware or a bad plugin.
Posted: Wed Aug 08, 2007 3:42 am
by Night Hawk
Here's a new crash log. Takes forever to produce it, seems kind of random. Again, happens on zoning.
Following plugins loaded:
[Plugins]
mq2labels=mq2labels
mq2itemdisplay=mq2itemdisplay
mq2custombinds=mq2custombinds
mq2hud=mq2hud
mq2map=mq2map
mq2chatwnd=mq2chatwnd
mq2eqbugfix=mq2eqbugfix
mq2cast=mq2cast
mq2advpath=mq2advpath
mq2reward=mq2reward
mq2xptracker=mq2xptracker
DBG output (right under removing all the spawns):
Code: Select all
(2cc.8d0): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
eax=064e3210 ebx=02abcff8 ecx=00000224 edx=0000008c esi=00000000 edi=00000224
eip=00600070 esp=0012e6c8 ebp=02abcff8 iopl=0 nv up ei pl nz ac po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010212
*** WARNING: Unable to verify checksum for C:\Program Files\EverQuest\eqgame.exe
*** ERROR: Module load completed but symbols could not be loaded for C:\Program Files\EverQuest\eqgame.exe
eqgame+0x200070:
00600070 8b01 mov eax,dword ptr [ecx] ds:0023:00000224=????????
r:
Code: Select all
eax=064e3210 ebx=02abcff8 ecx=00000224 edx=0000008c esi=00000000 edi=00000224
eip=00600070 esp=0012e6c8 ebp=02abcff8 iopl=0 nv up ei pl nz ac po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00010212
eqgame+0x200070:
00600070 8b01 mov eax,dword ptr [ecx] ds:0023:00000224=????????
kv:
Code: Select all
ChildEBP RetAddr Args to Child
WARNING: Stack unwind information not available. Following frames may be wrong.
0012e6c4 00419081 7c802442 00000001 004ddc3e eqgame+0x200070
0012e6d0 004ddc3e 064e3210 7c802442 0012e7ec eqgame+0x19081
*** WARNING: Unable to verify checksum for C:\Program Files\MacroQuest2\Release\MQ2Main.dll
0012e6f4 0302a850 0012e790 00000048 008fc5f0 eqgame+0xddc3e
0012e714 004e0dd1 006ebe28 0063ea4a 004e0dff MQ2Main!memchecks+0xd0 (FPO: [Uses EBP] [5,1,0]) (CONV: cdecl) [c:\program files\macroquest2\mq2main\mq2detourapi.cpp @ 240]
0012e7ec 0051e526 000501fa 00400000 00520cd9 eqgame+0xe0dd1
0012fc8c 00523724 0084dac7 0012fe06 00000000 eqgame+0x11e526
0012fca8 7c91e85c 002446d8 002446d8 0314fee5 eqgame+0x123724
0012fda8 006b62b3 0012ffb0 006bd9ae ffffffff ntdll!LdrDisableThreadCalloutsForDll+0xab1
0012fdb0 006bd9ae ffffffff 00523dfe 00400000 eqgame+0x2b62b3
0012ffc0 7c816fd7 ff4e525c ff343841 7ffd6000 eqgame+0x2bd9ae
0012ffe0 7c839aa7 7c816fe0 00000000 00000000 kernel32!BaseProcessStart+0x23 (FPO: [Non-Fpo])
0012ffe8 00000000 00000000 00000000 006a6129 kernel32!_SEH_epilog+0x18
would you still say it's a hardware problem AKA memory leak from EQ maybe, just causing it to possible crash after zoning so many times?
Posted: Wed Aug 08, 2007 1:35 pm
by dont_know_at_all
You are crashing in a place that cannot crash. Either the hardware is bad or the memory is corrupted.
Posted: Thu Aug 09, 2007 11:21 am
by A_Enchanter_00
do you have multi core system amd ? intel ?
i have had crash problems also with eq and multi core, never make a debug on it sine it was not mq related.
Posted: Thu Aug 09, 2007 1:47 pm
by Night Hawk
yes.
AMD 64 X2 6000+
2x 1GB Crucial Ballistix DDR2 800
I have the XP-released dualcore hotfix, the AMD drivers, and the AMD Dual-Core Optimizer.
But like I said, the crash is somewhat uncommon, but after zoning so many times, it is bound to happen eventually. Not really a big problem. Only takes a minute or to log back in.
Posted: Thu Aug 09, 2007 2:10 pm
by A_Enchanter_00
for eq, the issue with dual cores is excactly crashing when you zone ( most often ).
http://forums.station.sony.com/eq/posts ... c_id=15343
see: 5. Dual-core crashing/stuttering/model corruptions
but since you have AMD Dual-Core Optimizer, i guess it could be something else ..
i would rum memtest, and a cpu stress test
Posted: Thu Aug 09, 2007 2:20 pm
by Night Hawk
Yeah, I have all the hotfixes/drivers required. I may try a stress-test/memtest as you said, but I'm not too worried. I just wanted to rule out anything else first.
Posted: Thu Aug 09, 2007 2:36 pm
by TehWraith
overnight dual prime95s in stress mode, no harm in doing that, and you will find out if your cpu is stable.
Posted: Thu Aug 09, 2007 3:06 pm
by fearless
Crucial Ballistix memory has been known to fail early and often.
Posted: Thu Aug 09, 2007 6:13 pm
by ieatacid
I have no crash problems with my dual-core AMD.
Posted: Sat Aug 11, 2007 6:51 pm
by Night Hawk
I ran MemTest 3.5, a windows application, which ran for about 4-5 hours, and got up to like 1034% or something with 0 errors.
I'll have to run some ones mentioned above though. The ones that you boot to I suppose.
Hopefully can figure out something, but again, it's more of an uncommon annoyance than it is a "problem". Don't have any trouble with any other games going on.