Crashing in EQ? Check your drivers...

htw

Developer
Joined
Aug 27, 2006
Messages
13,193
Reaction score
374
Points
83
Location
Albuquerque, NM
We've been seeing an upwards trend in crashes lately for display drivers (especially nvidia), and directx.

MQ2 might make it seem worse, due to how it hooks into some functions.

If you are having crashes, especially if they are frequent, please try to make sure you have updated drivers, updated directx, and checked your EQ installation for any necessary device updates.

Over the years, this has become frequent for people who tend to use the same EQ installation for upgraded computers, laptops, hardware, etc. - it looks like it works ok, but it really doesn't.

You can do that with your eqclient.ini recreation, eqdevices, and config. Here or in your EQ community should be able to help you make sure you don't have old settings lying around.

Audio can cause similar issues, but it is less frequent.

htw
 
We've been seeing an upwards trend in crashes lately for display drivers (especially nvidia), and directx.

MQ2 might make it seem worse, due to how it hooks into some functions.

If you are having crashes, especially if they are frequent, please try to make sure you have updated drivers, updated directx, and checked your EQ installation for any necessary device updates.

Over the years, this has become frequent for people who tend to use the same EQ installation for upgraded computers, laptops, hardware, etc. - it looks like it works ok, but it really doesn't.

You can do that with your eqclient.ini recreation, eqdevices, and config. Here or in your EQ community should be able to help you make sure you don't have old settings lying around.

Audio can cause similar issues, but it is less frequent.

htw

As you might remember I am one who is crashing a lot when I zone. I had an older computer and for a number of reasons just bought a new rig. Immediately upgraded it to Win10 and then updated all drivers for HW. I then did a clean install of EQ and MMO MQ2. Moved my ini files and I still crash a lot when zoning. Especially after I have been sitting in GL for a period of time.
Graphics card is GeForce 750.

I always send the logs to you...

Any help is appreciated.

THanks
 
Thanks HTW.

Just want to also add as I also have worked with HTW regarding similar crash issues. The crashes seemed like it was MQ2 related but it was more EQ as I was able to replicate the same issue without MQ2.

I did all the steps, new EQ directly, move over ini's and still crashed. Sometimes it is the INI's which are causing the issue. The eq character INI's have a lot of configuration in them and can cause the issues. A Fresh EQ install without the INI and just recreates it solves a lot of issues.

Windows 10 screwed up a lot for some older hardware as it does not support windows 10. Please keep that in mind when upgrading.
 
As you might remember I am one who is crashing a lot when I zone. I had an older computer and for a number of reasons just bought a new rig. Immediately upgraded it to Win10 and then updated all drivers for HW. I then did a clean install of EQ and MMO MQ2. Moved my ini files and I still crash a lot when zoning. Especially after I have been sitting in GL for a period of time.
Graphics card is GeForce 750.

I always send the logs to you...

Any help is appreciated.

THanks
Hey man. Yeah, as you can see, that trend was like, 6 months ago. It was just an unusual jump for a bit, after a certain period of updates of EQ.

If you (or anyone) wants a personal touch (as much as I can) with any dump, make sure the email correspondence has a valid email link, and a comment in the feedback on what caused the crash. Otherwise, I look at it, and whether I fix it due to being on our end, or not - it won't necessarily get mentioned (although I usually try to put it in patch notes for any grouping).

For yours in particular, I always see it ending up similiar to this:

Code:
0057c488 5aa0fcfb 0057c498 5aa579f8 5aa3ad00 EQGraphicsDX9+0x10fd44
0057c4a8 5a91f210 00ee72c8 00000000 59629350 EQGraphicsDX9+0x10fcfb
0057c580 76fadc26 00020000 00020008 00000000 EQGraphicsDX9+0x1f210
0057c5c4 76fadab8 00000000 00b80000 0057c5f4 ntdll!RtlpAllocateHeapInternal+0x146
0057c5d4 5aa15be1 00b80000 00000000 00020000 ntdll!RtlAllocateHeap+0x28
0057c5f4 5aa0fc9b 00020000 6cb00700 770793d4 EQGraphicsDX9+0x115be1
0057c618 76fa75bb 77079794 00000004 00b80000 EQGraphicsDX9+0x10fc9b
0057c634 76fd8d4c 00b80000 00b8009c 00000004 ntdll!RtlRandomEx+0x1b
0057c648 76fb0156 00b80248 76faf3fe ebb645f6 ntdll!NtAllocateVirtualMemory+0xc
00000000 00000000 00000000 00000000 00000000 ntdll!RtlpAllocateHeap+0x16e6

Sometimes the call stack is in nvd3dum.dll also. Now, I don't have the pdb (debug) files for EQ's .dll or Nvidia's, so can't see specifics. If it's being caused by us, it's not showing up in the dump (i.e., call stack).

All I can suggest, beyond what's already been said (use a fresh EQ install, don't copy over files, at least don't bulk copy, etc.):

1) If you use any docracks, try not using it for a while - if that does seem to make a difference, let me know, and which ones you use. Those poke directly into EQ's memory space, so even if one causes a crash, I can't necessarily see that - it's just going to look like eqgame.exe caused it (or a related DLL).

2) Try to isolate plugins. Start with taking 1 you usually have loaded, and don't be loading it, see if it makes a difference. You don't have to worry about core/common dll's in this case, just other custom ones (under MMOBugs or General in Plugin Configuration). 2 in particular I recommend you check might be MQ2CompassUtils and MQ2VladUtils, due to how they work and the number of funtions involved (can't test every case).

3) Use dxwebsetup.exe and make sure all dx files are up to date.
4) If you are using the drivers from nvidia.com, consider trying the wdm for a while (whatever the latest is from MS install/updates). You would need to roll back and/or fresh install any driver (Driver Rollback | NVIDIA)
5) If you DO decide to say hell with that, and use nvidia's, then make sure you don't just let it upgrade ever. Make sure you use nvidia's cleaner/uninstaller, let windows pick the best wdm one, reboot if it's still wanting to, THEN update via nvidia's installer from their web site.

Sorry for your continued issues, and as I said, am more than willing to get it nailed down.

While I'm at it, I also want to make sure anyone who is having crash issue, please send the report every time - they are small, and it will highlight the fact that you are having an issue, and not just a random unlucky crash.

Thanks.

htw
 
As you might remember I am one who is crashing a lot when I zone. I had an older computer and for a number of reasons just bought a new rig. Immediately upgraded it to Win10 and then updated all drivers for HW. I then did a clean install of EQ and MMO MQ2. Moved my ini files and I still crash a lot when zoning. Especially after I have been sitting in GL for a period of time.
Graphics card is GeForce 750.

I always send the logs to you...

Any help is appreciated.

THanks
Hey man. Yeah, as you can see, that trend was like, 6 months ago. It was just an unusual jump for a bit, after a certain period of updates of EQ.

If you (or anyone) wants a personal touch (as much as I can) with any dump, make sure the email correspondence has a valid email link, and a comment in the feedback on what caused the crash. Otherwise, I look at it, and whether I fix it due to being on our end, or not - it won't necessarily get mentioned (although I usually try to put it in patch notes for any grouping).

For yours in particular, I always see it ending up similiar to this:

Code:
0057c488 5aa0fcfb 0057c498 5aa579f8 5aa3ad00 EQGraphicsDX9+0x10fd44
0057c4a8 5a91f210 00ee72c8 00000000 59629350 EQGraphicsDX9+0x10fcfb
0057c580 76fadc26 00020000 00020008 00000000 EQGraphicsDX9+0x1f210
0057c5c4 76fadab8 00000000 00b80000 0057c5f4 ntdll!RtlpAllocateHeapInternal+0x146
0057c5d4 5aa15be1 00b80000 00000000 00020000 ntdll!RtlAllocateHeap+0x28
0057c5f4 5aa0fc9b 00020000 6cb00700 770793d4 EQGraphicsDX9+0x115be1
0057c618 76fa75bb 77079794 00000004 00b80000 EQGraphicsDX9+0x10fc9b
0057c634 76fd8d4c 00b80000 00b8009c 00000004 ntdll!RtlRandomEx+0x1b
0057c648 76fb0156 00b80248 76faf3fe ebb645f6 ntdll!NtAllocateVirtualMemory+0xc
00000000 00000000 00000000 00000000 00000000 ntdll!RtlpAllocateHeap+0x16e6
Sometimes the call stack is in nvd3dum.dll also. Now, I don't have the pdb (debug) files for EQ's .dll or Nvidia's, so can't see specifics. If it's being caused by us, it's not showing up in the dump (i.e., call stack).

All I can suggest, beyond what's already been said (use a fresh EQ install, don't copy over files, at least don't bulk copy, etc.):

1) If you use any docracks, try not using it for a while - if that does seem to make a difference, let me know, and which ones you use. Those poke directly into EQ's memory space, so even if one causes a crash, I can't necessarily see that - it's just going to look like eqgame.exe caused it (or a related DLL).

2) Try to isolate plugins. Start with taking 1 you usually have loaded, and don't be loading it, see if it makes a difference. You don't have to worry about core/common dll's in this case, just other custom ones (under MMOBugs or General in Plugin Configuration). Two in particular I recommend you check might be MQ2CompassUtils and MQ2VladUtils, due to how they work and the number of functions involved (can't test every case).

3) Use dxwebsetup.exe and make sure all dx files are up to date.

4) If you are using the drivers from nvidia.com, consider trying the wdm for a while (whatever the latest is from MS install/updates). You would need to roll back and/or fresh install any driver (Driver Rollback | NVIDIA)

5) If you DO decide to say hell with that, and use nvidia's, then make sure you don't just let it upgrade ever. Make sure you use nvidia's cleaner/uninstaller, let windows pick the best wdm one, reboot if it's still wanting to, THEN update via nvidia's installer from their web site.

Sorry for your continued issues, and as I said, am more than willing to get it nailed down.

While I'm at it, I also want to make sure anyone who is having crash issue, please send the report every time - they are small, and it will highlight the fact that you are having an issue, and not just a random unlucky crash.

Thanks.

htw
 
Last edited:
I have an Nvidia based card and randomly crash instances on Wizzie Exodus and more rarely on normal zoning of the group.
Not sure what it is yet, but has been happening since around the time I updated to Win 10; unknown if related.
Just crashed two instances out of 6 on a wizzie Exodus with no macros running and I don't have the docrack plugin enabled.
 
I have an Nvidia based card and randomly crash instances on Wizzie Exodus and more rarely on normal zoning of the group.
Not sure what it is yet, but has been happening since around the time I updated to Win 10; unknown if related.
Just crashed two instances out of 6 on a wizzie Exodus with no macros running and I don't have the docrack plugin enabled.
Can't help ya. No debug reports from you.

htw
 
Not related to MMOBugs, but a ton of my guild mates crash zoning in to various raid instances in COTF. Argin Hiz seems especially bad. Is this a known EQ problem? Could telling them to update nvidia drivers and fresh install EQ and not copy INI files over help?

I only use nvidia cards, keep my drivers fresh, and haven't clean installed EQ on any computer I've used in probably 6 or 7 years, and I can't remember the last time I crashed zoning, but I'm probably not a typical user either.

edit: Also didn't notice this thread, but it is relevant: http://www.mmobugs.com/forums/everq...21930-eq-mq2-issues-crashing-suggestions.html
 
Last edited: