D3 Process crashes

Hello guys, I have been using your software for some time, in season 1 of diablo it worked without fault but now in season 2 it has given me some trouble.
I am trying to multibox diablo 3 with three instances and when I start the team/individual character the process Diablo III.exe starts and then loads up to 23000kb memory then crashes most of the time without saying anything sometime theres an error saying something along the lines of:
Runtime Error!
Program: C:\Diablo III\Diablo III.exe
R6016 - not enough space for thread data

I can get the entire team up and running by just continuing to spam start it and after 50+ crashes it starts character number 2 then repeat and eventually i get all three instances up and running. It works now for example after trying to get it to work for 30 minutes.


diagnostics:
http://privatepaste.com/1ac9397d9e

Application Compatibility flags under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers: 0 C:\Windows\SysWow64\cmicnfgp.dll:

this is supposedly my audio driver which I have not touched since it last worked so I don't know why that should be a problem, anyone know what I can try to get it working?

[bob]

Well the error code is interesting, but maybe not for you.

http://support.microsoft.com/kb/126709 and http://stackoverflow.com/questions/2112 ... hread-data and http://stackoverflow.com/questions/1391 ... -data?lq=1

The SO post (from which you can infer it to still be an issue in certain circumstances) eventually refers to their cause as being resolved by using _beginthreadex, rather than CreateThread when calling C runtime functions:

Code:

A thread in an executable that calls the C run-time library (CRT) should use the _beginthreadex and _endthreadex functions for thread management rather than CreateThread and ExitThread; this requires the use of the multithreaded version of the CRT. If a thread created using CreateThread calls the CRT, the CRT may terminate the process in low-memory conditions.

The second SO post pointed to DLL thrashing.

Tracing back the other way through the MS post, unless you have some an older program using Win32s v1.20/v1.25 that are hooking the game, then it is probably not going to fixed by the suggestion on the MS page. The last release of Win32s, v1.30a seems to be around 1996 (C++ 4.2), i.e. Win95 era, although it was still supported in 98/ME.

Ignoring the Win32s angle, this is pointing to some application that is trying to hook the game and create a thread or a frequent load/unload cycle a DLL in it, and not following good citizen practices as it is filling the TLS space.


Anyway, I find it interesting that your D3 process that you dumped the diags from has no modules. Normally this happens if it is a 64bit module, although I thought Lax fixed that. If you could run the diagnostic again, but with a D3 not launched by Inner Space, it may be more useful as it may show the processes that are hooking your game, which are the common causes of crashes.

Potential causes I could spot are (in no specific order):

• RivaTuner (and all it's associated goodies)
• GFExperience
• KMService (okay, this is a crack/keygen rather than a virus, but it seems to be noted as not great).
• ASGT (ASUS GPU Tweak)
• FreeMeter (ok it's monitoring, but not necessary to run D3)
• FlawlessWidescreen (does some graphics stuff)
• Matrox PowerDesk (but hey if you need it) - do you have a NVidia and Matrox GPU, maybe it's getting confused about where it is running and which software is managing the screen layout?)
• MSI Afterburner
• Nvsmartmaxapp (Nvidia Surround - oh look another desktop manager)
• SUPERAntiSpyware (yes it's cool, but you may need to uninstall it to test if it is an issue)
• WeGame
• Vibrance.GUI (more graphics manipulations)

As for the Application Compatibility entries. I can see the point behind the Inner Space entry as you have disabled UAC, but it may not be necessary if Inner Space is loading as an admin process without it. As for the sound card entry. I'd remove it. There are no flags associated with it, and all it will be doing is force loading the ACLayer and/or database.

Simply the process for you will be the same as for everybody else. Unload/uninstall stuff until you get a working setup. Some people have gone so far as to clean install their systems to get rid of these annoying things as despite uninstalling all they could, some problem still existed (presumably a mismatched DLL, whether a SxS one or not, who knows).

Thanks for all the information man, very much appreciated!

Here is the diagnostic when I ran D3 straight from the launcher without Inner Space - http://privatepaste.com/b4b4a6e38c

[lax]

Thanks for providing that. We still definitely need you to narrow it down by closing programs -- this added information only shows us what things are for sure loading in the process.

For example

Code:

51. C:\Program Files (x86)\RivaTuner Statistics Server\RTSSHooks.dll
52. C:\Program Files (x86)\Matrox Graphics\PowerDesk\Matrox.PDesk.Hooks.dll
62. C:\Program Files\NVIDIA Corporation\Display\NvSmartMax.dll

I'm not sure I've seen Matrox.PDesk.Hooks.dll in a diagnostic before, I would really suggest shutting down the Matrox software first.

Simply unloading all the matrox processes seems to have solved the issue, I've rebooted several times and all I have to do is unload those specific processes. (I tried a few other combinations before noticing it was only the matrox ones)
I do not even need the software anymore so that is wonderful!

Thanks guys for the quick and great help.