Opening Maps periodically crashes client

snoopy3525

Lifetime Member
Joined
Oct 25, 2006
Messages
59
Reaction score
34
Points
18
Upon opening Maps, my client periodically crashes. Seems like it recently started within a past couple of either mmobugs or EQ client updates.

Doesn't happen too often, but timing can sometimes suckkk.

Some things I can note:
-The zone doesn't matter, seems fully random.
-Windows 11 OS on 22H2
-Reinstalling MMOBugs MQNext Live didn't fix the issue

Anyone have any input on how to fix? I did submit a bug report once if that hopefully helped.
 
  • Like
Reactions: EQDAB
Is it not an issue with your computer resources? CPU or mem maxing out with the map window?
 
  • Like
Reactions: EQDAB
I can't believe so. Happens on two different desktops and a laptop. All very high powered and different specs.

Only thing I can think of maybe something with Goods maps causing it, but Goods maps hasn't been updated in ages.

I'm debating on freshly imaging a Windows 10 machine just to see if it happens on there as well out of curiousity.
 
  • Like
Reactions: EQDAB
I can't believe so. Happens on two different desktops and a laptop. All very high powered and different specs.

Only thing I can think of maybe something with Goods maps causing it, but Goods maps hasn't been updated in ages.

I'm debating on freshly imaging a Windows 10 machine just to see if it happens on there as well out of curiousity.
Have you tried default or Brenwall's map pacs?

Shooting in the dark here BtW.
Also, I have a high end system and get MAJOR lag initially when I open the maps in a populated zone. Hasn't crashed me but I take a major hit for a bit.

BB
 
  • Like
Reactions: EQDAB
I'll switch over to Brewall's maps and see what happens. Yeah I get the lag too in heavily populated zones. But this crashing happens randomly. Full zones, empty zones with only a couple NPC's as well.

Last resort I'll reinstall with Windows 10 instead and see what happens. I have a funny feeling Windows 11 and its new memory related management crap is causing issues.
 
  • Like
Reactions: EQDAB
I'm officially out of ideas. Wiped two different computers back to Windows 10 with fresh installs, opening maps occasionally still crashes. No overclock (one's a factory OEM HP)

Tried Brewall's maps, crashed. Goods maps, crashed.

At this point It's a waiting game. I've submitted bug reports multiple times through mmobugs. Will see what happens. Can't see how I'm the only one considering it's likely not hardware related on my end.
 
  • Like
Reactions: EQDAB
From your reports, it looks video related. What drivers are you using (WHQL, etc.)? Are you using any 3rd party hooks or overlays (steam or other)? I can try to grab a couple dumps later tonight see if anything pops out. You might also consider looking at your windows event log(s) and see what that shows after a crash.
 
  • Like
Reactions: EQDAB
From your reports, it looks video related. What drivers are you using (WHQL, etc.)? Are you using any 3rd party hooks or overlays (steam or other)? I can try to grab a couple dumps later tonight see if anything pops out. You might also consider looking at your windows event log(s) and see what that shows after a crash.

Interesting. Thanks for the response. One PC I am using newest AMD WHQL, 23.5.2, The other PC I am using newer nVidia WHQL (would have to check what driver). Submitted bug reports on both PC's

The only common denominator is MSI Afterburner. However, I am not using the Rivatuner Statistics overlay (considering I know that causes problems). I didn't think Afterburner would cause problems in itself.

I guess if it's Maps related, It may not necessarily be related to MQ Next, but it may be related to MQ2 itself.

I am going to uninstall MSI Afterburner and see what happens. Will report back in either a few days, or a crash (whichever comes first).

Thanks again!
 
  • Like
Reactions: EQDAB
Uninstalled Afterburner. Crash still occurring. Right now it's a vanilla Windows 10 Install with just Everquest and MQNext on it.

Will switch to older AMD drivers, if that doesnt work, will switch to intel iGPU and see what happens.
 
Last edited:
  • Like
Reactions: EQDAB
I'll take a further look at the code, I did analyze your latest report:

Code:
STACK_COMMAND:  ~0s; .ecxr ; kb

FAULTING_SOURCE_LINE:  C:\MQ2\mmobugs\MQNext\src\main\MQ2Utilities.cpp

FAULTING_SOURCE_FILE:  C:\MQ2\mmobugs\MQNext\src\main\MQ2Utilities.cpp

FAULTING_SOURCE_LINE_NUMBER:  6596

FAULTING_SOURCE_CODE:  
  6592: {
  6593:     if (pSpawn == nullptr)
  6594:         return NONE;
  6595: 
> 6596:     switch (pSpawn->Type)
  6597:     {
  6598:     case SPAWN_PLAYER:
  6599:         return PC;
  6600: 
  6601:     case SPAWN_NPC:


SYMBOL_NAME:  MQ2Main!GetSpawnType+16

MODULE_NAME: MQ2Main

IMAGE_NAME:  MQ2Main.dll

FAILURE_BUCKET_ID:  INVALID_POINTER_READ_c0000005_MQ2Main.dll!GetSpawnType
 
  • Like
Reactions: EQDAB
And also:

Code:
0000003c`350fd6f0 0000021e`0c09c968     : 00007ff9`632ca7ff 0000021e`0c09c950 00000000`00000208 0000021d`81f9ba00 : eqgame+0x2e1333
0000003c`350fd6f8 00007ff9`632ca7ff     : 0000021e`0c09c950 00000000`00000208 0000021d`81f9ba00 00007ff9`637c4659 : 0x0000021e`0c09c968
0000003c`350fd700 00007ff9`62669acc     : 0000003c`350fd7d0 00000000`00000000 00007ff9`62792092 00007ff9`6266728c : eqlib!eqlib::CXStr::assign+0x9f
0000003c`350fd730 00007ff9`62669d0a     : 0000021e`0c09c950 00000000`00000000 00000000`00000000 00007ff9`62792091 : MQ2Map!MapObject::SetText+0x8c
0000003c`350fd780 00007ff9`62677c9b     : 0000021e`00000001 0000021e`0c09c950 00000000`00000000 00000000`00000001 : MQ2Map!MapObjectSpawn::Update+0x10a
0000003c`350fd7d0 00007ff9`6266efae     : 00000166`000001e6 0000021d`b8afef68 00000000`000000ff 00000000`ffffffff : MQ2Map!MapUpdate+0x14b
0000003c`350fd820 00007ff6`ef8fb9b3     : 0000021d`b8afef68 00000000`000000ff 00000000`ffffffff 0000021d`b8afef68 : MQ2Map!MapViewMapOverride::PostDraw+0xe
0000003c`350fd850 0000021d`b8afef68     : 00000000`000000ff 00000000`ffffffff 0000021d`b8afef68 00000161`000001e1 : eqgame+0x58b9b3
 
  • Like
Reactions: EQDAB
Looking through several more, it's pretty consistent in that it is accessing an invalid spawn, when looking at GetSpawnType or GetSpawnColor etc.

I'm not at home now, but will see what I can find out as soon as I get a chance.
 
  • Like
Reactions: EQDAB
Thank you!

Yeah, very odd considering I haven't seen any other posts regarding this.

Just to follow up anyway. I tried an nVidia, Intel integrated GPU, and AMD, all same results regardless of drivers.

The only thing I do after a fresh install of MMObugs is turn the filter ground items off.
 
  • Like
Reactions: EQDAB
Could you post or PM me your specific map settings (from MQ2Map.ini) so I can take a look?
 
  • Like
Reactions: EQDAB
I presume this may be fixed in last mmobugs update? Haven't had a crash all day :)
 
  • Like
Reactions: EQDAB
It's possible. Would have to be a core change though, we don't touch anything with MQ2Map on our end.
 
  • Love
Reactions: EQDAB