Problem - MQ & ISBoxer - Post 64 bit, on loading accounts EQ hangs after 2 seconds and terminates after a couple of minutes.

[[email protected]]

Hi folks,

I'm running MQ Live and ISBoxer and since the move to 64 bit EQ client amd consistently finding that on loading my accounts via InnerSpace, they all load, but after a couple of seconds (from when the first eq process is started) I am unable to get a response from each EQ window, and after a couple of minutes all of the accounts close (no error message, no popups).

• Windows 11, fully patched (Ryzen 9 3900x, 64GB RAM)
• ISboxer alone works fine (latest release installed)
• MQ alone works fine (latest release installed)
• I'm not using any autologin features.
• Windows Task Manager shows each eqgame.exe as switching between 'Not Responding' and 'Suspended' in the status field for around 2 minutes
• Event Viewer shows 'faulting application' (full lof entry pasted at the bottom of this post.

Now I can log this on github (it's crashing but I'm assuming that with no MQ popup it won't be getting automatically reported), but to be honest it's such a major issue that I'm assuming it is not affecting other folks, since a lot of other people use the ISBoxer/MQ combo, and there is only one other possibly related post that I have managed to find (here).

Has anyone seen anything along these lines, or can make any suggestions on either how to fix it or what information to pull together to help investigate the problem?

Cheers.

Windows event viewer output:

Faulting application name: eqgame.exe, version: 0.0.0.0, time stamp: 0x6205cf0a
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000019be4256078
Faulting process ID: 0x5720
Faulting application start time: 0x01d824d08cfd56a6
Faulting application path: C:\Games\EverQuest_Live\eqgame.exe
Faulting module path: unknown
Report ID: d164508f-888d-4898-942d-fc97926cc10d
Faulting package full name:
Faulting package-relative application ID:

and

Fault bucket , type 0
Event Name: BEX64
Response: Not available
Cab Id: 0

Problem signature:
P1: eqgame.exe
P2: 0.0.0.0
P3: 6205cf0a
P4: StackHash_db05
P5: 0.0.0.0
P6: 00000000
P7: PCH_02_FROM_unknown+0x0000000000000000
P8: c0000005
P9: 0000000000000008
P10:

Attached files:

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_eqgame.exe_e37eac7cf5cd5022a9e27655541fffda21f3fd97_8ad94201_c71b559c-22c6-41dc-8b25-40495ecd6bf6

Analysis symbol:
Rechecking for solution: 0
Report Id: d164508f-888d-4898-942d-fc97926cc10d
Report Status: 4
Hashed bucket:
Cab Guid: 0

 

[Sic]

You need to run the developer isboxer version

 

[saar]

I run IS boxer and MQ and I had no issues last night with it on IS boxer you just need to make sure you're on the dev build you can't be on the normal build or else you will instantly crash

 

[[email protected]]

Thank you - I looked at the ISBoxer site but missed that. Fantastic, I hugely appreciate the help

--
Follow-up note:
Just for the benefit of anyone else who hits this issue, the details for updating to the developer build of ISBoxer are:

To update to the current Development build of Inner Space, right click Inner Space, select Patcher, click the Development tab, use the Check for Updates button if needed and click Install Now to actually install it.

 

[anks]

oh , and be sure to check "use 64bit ISboxer"

 

[Dragonslayer]

Couldn`t run more than 2 accounts launched via DB-launcher since patch to 64 bit. Some minutes ago I came to checke for exactly this informations.
The only thing I couldn:t find was the "use 64bit ISboxer" to check.
But after I had installed the developer-version, I could start, as I was used until the 64 patch.
Many thanks for the provided information.
Greate community, almost always I am able to find what I am looking for.

 

[zanial]

I am having a similar issue. Running InnerSphere in Dev mode, but MQNext reports denied access. Is there a specific order to launch the programs?

 

[Sic]

I am having a similar issue. Running InnerSphere in Dev mode, but MQNext reports denied access. Is there a specific order to launch the programs?

innerspace requires elevated priv - make sure you are running mq as admin to use isb

 

[zanial]

innerspace requires elevated priv - make sure you are running mq as admin to use isb

Thanks. I will try that after the patch today.