Crashing still occuring post update

[crowdx]

So just logged in this morning and have the same issue. Both 5 boxing and also duo boxing. I have a laptop with an nVidia video card and my desktop with an ATI video card, both are crashing.
The bizarre part is that the laptop was fine on Friday night and then the following day was crashing. So somthing changed without a notification to cause this issue
Very frustrated right now

[Norrin]

Someone on the ISBoxer forums pointed out that the magic time/number was around 15 minutes. I have run 4 tests so far and each time the first client crashes at 14/15 minutes from enter game world.

I guess we can rule out video card though. At first I thought it had to do with ATI cards. Guess not.

I did some research into the actual crash. Looking at the Event Log, the exception that is getting raised is a general access violation error. I just ran a test with the Rift client exe running as Admin along with ISBoxer. I still get the crash.

Well I am out ideas now.

[crowdx]

Another point is that even single boxing with ISBoxer is causing a crash. Whereas single boxing without ISboxer the clients is stable.

[Norrin]

I was thinking maybe it was related to an AFK timer, and that maybe if the client was not focused when that timer hit, the act of setting afk would cause a crash. But I have been setting in game solo (no ISBoxer) for almost 30 minutes and its been unfocused the whole time. Also I never went in AFK so, I guess that got ruled out.

I can't seem to reproduce a crash at all, without ISBoxer running the client.

[crowdx]

I was thinking maybe it was related to an AFK timer, and that maybe if the client was not focused when that timer hit, the act of setting afk would cause a crash. But I have been setting in game solo (no ISBoxer) for almost 30 minutes and its been unfocused the whole time. Also I never went in AFK so, I guess that got ruled out.

I can't seem to reproduce a crash at all, without ISBoxer running the client.

Yeah, definitely an ISBoxer issue.

[Smedbox]

Smedbox, are you using ISBoxer? When I don't use ISBoxer it works fine. Well the games run fine that is.
I don't think it is ISBoxer causing any problems. ISBoxer has not changed at all in the last few days. And before the update I had no problems at all.

I am running an ATI 5870 graphics card, and it powering 5 monitors. Not that I think that has anything to do with it either.
One thing I have not tried yet though is playing the games on the same crappy low setting that I normally box with. I was thinking maybe it was a conflict with ATI's Catalyst drivers. I did do a complete uninstall of the ATI drivers and reinstall them yesterday. That made no change.

Anyway will continue to play it with it today.

I'm running with ISBoxer and InputDirector with no problems. Haven't tried with more than three characters per machine, but I have zero problems. I've stood idle in Meridian for 15+ min, I've been in Runic Descent for 40 min, I've played PvP, no problems.

My two machines are using different OS (Win7 and Vista), but both are 64-bit. The only problems I'm having are that the summon friend dialog box won't go away until you hit /reloadui or re-log and that one machine doesn't get any voice overs even though it's enabled in the settings.

[Norrin]

I'm running with ISBoxer and InputDirector with no problems. Haven't tried with more than three characters per machine, but I have zero problems. I've stood idle in Meridian for 15+ min, I've been in Runic Descent for 40 min, I've played PvP, no problems.

My two machines are using different OS (Win7 and Vista), but both are 64-bit. The only problems I'm having are that the summon friend dialog box won't go away until you hit /reloadui or re-log and that one machine doesn't get any voice overs even though it's enabled in the settings.

You are on separate machines for each character. All mine are on the same machine.
Maybe that has something to do with it. However I think Crowdx has seen it crash with just one client running.

[crowdx]

You are on separate machines for each character. All mine are on the same machine.
Maybe that has something to do with it. However I think Crowdx has seen it crash with just one client running.

Yup, just a single client logged in and it still crashed :-(

[Smedbox]

You are on separate machines for each character. All mine are on the same machine.
Maybe that has something to do with it. However I think Crowdx has seen it crash with just one client running.

As you can see in my post, each machine is running up to three characters.

[Norrin]

As you can see in my post, each machine is running up to three characters.

Even so, for Crowdx and I, it doesn't matter how many we run, even just one it crashes.

What are you running different that has it so you don't crash.

And by InputDirector, I assume you mean innerspace?