Hardware is tops, still dealing with a MX software bug

[FrancisJ]

I just installed the new MX Gaming Keyboard and it's working great, BUT the system (Windows 10, Dell 8900) is still reporting an exception with the G.skill Keyboard App:




See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.IndexOutOfRangeException: Index was outside the bounds of the array.
at App.Hid.HidProcess.TransKeyDataToBtnKey(Byte byMode, Byte byFWCode, FWBtnSetFunc fwBtnFunc, Object obj, BtnKey& btnKey)
at App.Hid.HidProcess.GetBtnSetting(Byte byMode, Byte byFWCode, FWAllKeyData fwAllKeyData, BtnKey& btnKey)
at App.Hid.HidProcess.GetModeKeySetting(Byte byMode, ModeData modeData)
at App.Hid.HidProcess.GetDeiceInfo(Boolean bInit)
at App.Hid.HidProcess.OnDeviceChange(Object sender, EventArgs e)
at App.Hid.UsbDriver.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.O nMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.W ndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8689 (QFE.050727-8600)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
App
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Program%20Files%20(x86)/G.SKILL/G.SKILL%20RIPJAWS%20KM780%20MX/App.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8670 (QFE.050727-8600)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8690 (QFE.050727-8600)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8681 (QFE.050727-8600)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8679 (QFE.050727-8600)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Core
Assembly Version: 3.5.0.0
Win32 Version: 3.5.30729.8693 built by: QFE
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

[robertmiket]

I also had this problem yesterday right before I had to rma the keyboard when it refused to operate
I reviewed past posts and I did not have any profiles or macros saved. The keyboard worked fine until I unplugged it to install a second graphics card(sli) then I got this error and a non operating keyboard

my rig
windows 10 home
6700k overclocked to 4350ghz
msi gaming 7 motherboard x170
16 gb corsair 3000 cl15
2 evga gtx sc 970 sli overclocked
corsair 750 gold supply

[FrancisJ]

Now the darn keyboard is CRASHING (no lights) after normal power off, power on sequence.

I've pretty much had it with this keyboard and may request a refund --- it's just too flakey.

[robertmiket]

I just rma this board to newegg today and still recieving the same error..I guess that I will just have to return this one as well and change my good reviews to bad ones ..this really makes me mad as I really wanted to have this keyboard work out from these folks
I guess no one reads these forums as well..so much for support from here

[G.SKILL]

Hi robertmiket,

Sorry about the delayed response. Have you tried reflashing the firmware to an older version and then upgrading it again to the latest version? Please also make sure that the keyboard is installed directly into the rear panel of the motherboard (and connect both USB connectors). In some cases, a miscommunication between the keyboard and software may cause this issue.

For other possibilities, please contact our tech support team at techsupport@gskill.com. Thank you!