I, also, have had random crashes, tho they seem to happen mostly after (but not during) zoning. I *always* have 2 instances running on the same (XP) desktop, and it *always* crashes on the first instance loaded, never the second.
This used to happen (starting in October or thereabouts) several times a night. now it only happens once and this is why... I get the message that MQ is blocking the crash report, but I never press the ok button. I play on two monitors, I just move the crash dialog to the other monitor and the instance continues to run just fine, with one exception... The voice chat channels are gone completely.
I can't play EQ without MQ, so I have no idea if this also occurs without MQ loaded.
I am not reporting this as a problem because I run, more or less, just fine - I can prevent the actual crash by ignoring the dialog box - Just wanted to pass along a little info about my experience with it.
I am running XP, 2GB RAM, 3.2 GHz. 2 Monitors, WinEQ, bare bones plugins, custom UI that I customized myself, mostly for larger font faces (nothing fancy).
All drivers up to date, all compiles latest. This has been ongoing for months.
The changes to EQ over the past few months, UI, sound (voice), etc., have really started to cause people issues, esp. if using multiple instances on the same PC.
While that popup is from MQ2, it is catching the function that EQ uses to pop up a window asking if you want to send crash information back to SOE. So the function itself is being called by EQ, not MQ2.
One thing you could do to try to minimize issues, is use different INI files when you launch EQ, per session (wineq2 & innerspace both can set this up for you automatically), that way you can have 1 session with voice chat on, the others with it off, or other options like that (sound on/off, video options such as details, etc.).
Another thing you could try, is running EQ in different directories per session, so that any file access (UI, logs, etc.) would be independent of any other session, and they wouldn't "fight" over access, and perhaps cause some kind of crash.
As far as MQ2 goes, no, it's not perfect. However, I would place good money on that if you try running just as you are, mulitple instances, etc., without MQ2 running, you will find you get those crashes with the same frequency you did with it running.
My 2c!
htw
