Announcement

Collapse

Got a technical problem?

Please provide the following information with any new post involving a technical issue with your G.Skill peripheral. This pertinent information will allow us to effectively troubleshoot and provide the best solution.

1) Software (SW) version and firmware (FW) version
2) Did this issue occur on a new software installation or software update?
3) What is the model number of your keyboard and layout? (e.g. KM780 RGB, NA English; etc.)
4) Which Windows OS version are you using? (e.g. Windows 7 Ultimate 64-bit; Windows 10 Pro 64-bit; etc.)
5) Which USB port did you plug the keyboard into? (e.g. USB3.0 in motherboard back panel, USB2.0 hub, etc.)
6) Your motherboard model number
7) Any antivirus/anti-malware software programs you have installed
8) Any other keyboard/mouse/similar device software you have installed

If you would like, you can also email this info to techsupport@gskill.com for our peripherals team to troubleshoot/replicate the issue.

Thank you!
See more
See less

KM780MX - .Net error

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • KM780MX - .Net error

    I'm running Windows 10, 64 bit - and had been happily using my KM780MX for some time. Several weeks ago, I started getting a .NET error, and I haven't been able to use the supplied software since.
    Microsoft .NET Framework
    Unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediate.

    Illegal characters in path.

    Details on the error are below.

    I've tried re-installing the current (though somewhat old) software for the keyboard, and re-installing the (old) required 3.5 .NET framework. Same result.

    I've also noticed that without the drivers, the . key in the numeric keypad doesn't work. Makes entering date a real pain.

    Hopefully I'm not missing something terribly obvious.

    Any suggestions on how to resolve this would be greatly appreciated.

    Thanks in advance,
    Ted W





    ---- .NET Framework details:

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

    ************** Exception Text **************
    System.ArgumentException: Illegal characters in path.
    at System.IO.Path.CheckInvalidPathChars(String path)
    at System.IO.Path.GetFileName(String path)
    at System.IO.Path.GetFileNameWithoutExtension(String path)
    at App.Struct.ModeData.LoadMode()
    at App.Struct.UsedModeManage.SetUsedModeName(String[] newName)
    at App.ProfilePanel.SwitchProfile(String profileName)
    at App.ProfilePanel..ctor(ProfileManage profileManage)
    at App.Main_Control.CreateSubPanel(BitmapBtn selBtn)
    at App.Main_Control.SwitchTab(BitmapBtn clickBtn)
    at App.Main_Control.Main_Control_Load(Object sender, EventArgs e)
    at System.Windows.Forms.Form.OnLoad(EventArgs e)
    at System.Windows.Forms.Form.OnCreateControl()
    at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
    at System.Windows.Forms.Control.CreateControl()
    at System.Windows.Forms.Control.WmShowWindow(Message& m)
    at System.Windows.Forms.Control.WndProc(Message& m)
    at System.Windows.Forms.ScrollableControl.WndProc(Mes sage& m)
    at System.Windows.Forms.ContainerControl.WndProc(Mess age& m)
    at System.Windows.Forms.Form.WmShowWindow(Message& m)
    at System.Windows.Forms.Form.WndProc(Message& m)
    at App.Main_Control.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.8784 (WinRel.050727-8700)
    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.8784 (WinRel.050727-8700)
    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.8784 (WinRel.050727-8700)
    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.8784 (WinRel.050727-8700)
    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.8784 (WinRel.050727-8700)
    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.8795 built by: WinRel
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Core/3.5.0.0__b77a5c561934e089/System.Core.dll
    ----------------------------------------
    NAudio
    Assembly Version: 1.7.3.0
    Win32 Version: 1.7.3.0
    CodeBase: file:///C:/Program%20Files%20(x86)/G.SKILL/G.SKILL%20RIPJAWS%20KM780%20MX/NAudio.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.

  • #2
    Ok... that seems to have gone nowhere fast.

    Let's try this... any outlook on updated software for the KM780/KM780R MX Mechanical Gaming Keyboard?

    Or... should I circular file this sucker, and try something else?

    Thanks,
    Ted

    Comment


    • #3
      i am getting the same error
      just did a complete reinstall of windows 10 and it still comes back the moment this program starts up
      program still works but clicking the error to skip everytime i start gets anoying

      Comment


      • #4
        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.8825 (WinRelRS3.050727-8800)
        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.8825 (WinRelRS3.050727-8800)
        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.8825 (WinRelRS3.050727-8800)
        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.8825 (WinRelRS3.050727-8800)
        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.8825 (WinRelRS3.050727-8800)
        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.8833 built by: WinRelRS3
        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.

        Comment


        • #5
          There may be some strange things going on with the temp storage files in Windows in combination with possible already stored settings within the keyboard. Let's try clearing everything out and resetting the keyboard firmware. The keyboard should function normally without any drivers.

          1. Reset the keyboard firmware, using the instructions here: http://www.gskill.us/forum/showthread.php?t=14111
          The . key should at least work in a driver-less state. Please make sure that that software is uninstalled at this point.
          If the .key still doesn't work normally, then it might be a messed up keyboard driver. Try going into device manager, and look under "Keyboards" and double click on the "HID Keyboard Device", and in the "Details" tab, under "Hardware IDs", confirm that it's "HID\VID_28DA" (which means vendor is G.SKILL), and then right click the "HID Keyboard Device" and choose to uninstall. Repeat this process for all the "HID Keyboard Device", there may be 2 or 3. After that, unplug the keyboard, and replug the keyboard into the system. The OS should then reinstall the basic keyboard drivers.

          2. Uninstall all G.SKILL software. Then in the Control Panel, find the add/remove Windows components, then uncheck the .NET framework packages. Reboot. Then go to "This PC", right click on "C" drive, go into the Properties, and choose to "Disk Cleanup", and make sure to clear out all the temp storage files (including "Clean up system files"). After that, go back into the add/remove Windows components and then check/install the .NET framework packages, and reboot. Then re-download the software from our website, to make sure your downloads before weren't corrupted, and install the software.

          Alternatively, when removing .NET framework, Microsoft should have a .NET clean uninstall program, that might help reset the .NET framework install from your system, so you have a clean slate to work from.

          Comment


          • #6
            thx it worked no more errors

            Comment

            Working...
            X