Crashing since 1.0.8

Isboxer keeps crashing on me in Diablo 3 since patch 1.0.8. Sending the error report fails with Failed error -114. It happens like every 3-5 minutes.

I use Win7 (up2date)

The screen freezes (but still takes commands) and a moment later it will crash.

Ah bad. It got bad again.

My FPS is capped in all 4 windows, I have 60-70ms latency, my videocard and cpu are mostly idle. Yet still at some point a window (or multiple) may behave as if they had bad fps only to crash moments later. It's actually ISBoxer that crashes and not Diablo 3 according to the crash report. Not only that, Diablo 3 still takes input even after the DirectX already crashed (when the window freezes before it crashes).

http://www.privatepaste.com/bbfabd2f76

I hope you forgive the triple post, but is someone working on a fix within 'reasonable time'? Because if not then I might as well cancel my subscription within the 14 days of purchase. It's no use buying IsBoxer if it doesn't work.

[lax]

As we discussed in the ISBoxer Chat Room...

The "DrawText" crash you are getting has been around for a long time, and from my end appears to be an NVIDIA driver bug. I have tried to "fix" it numerous times over the years but as I have not been able to reproduce the bug on any of my machines -- less than 10 people have reported this issue, since about 2008 (so it's likely something specific to your PC) -- there is no reliable way for me to test and fix the problem. I've adjusted the related code numerous times since it was first reported. As of right now, I have no new information about the crash.

You may be able to avoid the crash by disabling Inner Space's FPS indicator. Select your Character Set in the top left pane and then in the bottom right pane, check "Hide FPS (framerate) indicator", and Export to Inner Space.

"Diagnostics for game crashes" from the latest ISBoxer Toolkit could also potentially provide some insight. In ISBoxer's Help menu select "About ISBoxer" and, if it gives you an update link, use it. Then use "Diagnostics for game crashes" from the Help menu and paste me the diagnostic info.

I disabled the FPS indicator and updated IsBoxer like you said (seems there was just slightly a newer version again). It didn't solve anything. After perhaps 15 seconds ingame the first window 'froze'.

Diagnostics:
http://www.privatepaste.com/d7d1c4f81d

Problem screenshot (main screen stopped rendering once again. As you can see the mage still functions by controlling it from another window.
http://www2.picturepush.com/photo/a/13054950/img/Anonymous/problem.png

What did those other < 10 people do? Because it's impossible to play like this. And it looks like this problem can't be fixed because the bug/problem may reside somewhere else (Nvidia driver for example).

[lax]

One of them said the problem was solved by reinstalling Inner Space, but I wouldn't expect any change from doing so. I'm not sure they all were able to resolve the problem.

I notice that you do have the NVIDIA stereoscopic 3d drivers installed -- C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvSCPAPI.dll. It might be worth uninstalling this feature to see if that eliminates the problem; you might have to uninstall your NVIDIA driver, and then install it again, and during the install process disable the stereoscopic 3d install. Doing so solved an unrelated issue for someone else, it's possible this could help you in this case.

I removed the "stereoscopic 3d" before like you said in chat if I remember correctly, by uninstalling the entire NVidia driver and then re-installing it without that part. It didn't help do I installed it again.

Just to be sure I uninstalled it now again (just that stereoscopic), rebooted, and tried it again. The new diagnostic confirmed that it's gone now. But still the same problems.

If it matters, all other games, including Diablo 3 without IsBoxer/InnerSpace work perfectly and I usually have to cap my FPS to prevent my videocard from running at 3000-8000 fps or something crazy like that. But I'm sure that it's not a performance problem but it's still weird that a driver (or whatever) bugs only IsBoxer and nothing else.