Announcement

Collapse
No announcement yet.

error when starting windows

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

  • error when starting windows

    just installed the software for my km780mx keyboard and get this error every time windows boots

    i have 2 totally separate drives with 2 copies of windows 10 running on each and get the same error



    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.8745 (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.8745 (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.8750 (QFE.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.8745 (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.8745 (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.8763 built by: WinRel
    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.

  • #2
    It's likely that the firmware on the keyboard is corrupted. Please use the reflash method (linked below) to delete and reset your firmware. Please make sure to also use a new re-downloaded file for installation after the reset.

    Please let us know if the issue continues after the reflash.

    Firmware Downgrade/Reset Thread: http://www.gskill.us/forum/showthread.php?t=14111

    Also, please double check to make sure you use the correct file for your keyboard.

    Comment


    • #3
      Originally posted by G.SKILL View Post
      It's likely that the firmware on the keyboard is corrupted. Please use the reflash method (linked below) to delete and reset your firmware. Please make sure to also use a new re-downloaded file for installation after the reset.

      Please let us know if the issue continues after the reflash.

      Firmware Downgrade/Reset Thread: http://www.gskill.us/forum/showthread.php?t=14111

      Also, please double check to make sure you use the correct file for your keyboard.
      Please provide new firmware for these issues. Almost 4 months have been passed.

      Comment


      • #4
        Please understand that there's nothing wrong with the functionality of the firmware. The issue here is that the firmware itself is corrupt inside the keyboard, so it has some bad bits and bytes. And as long as the flash memory itself isn't faulty, all you have to do is to delete the firmware file, rewrite it, and re-update it to the latest version.

        Unless you're indicating another issue, in which case, can you further clarify which bug you are referring to for the firmware?

        Comment


        • #5
          I followed your other links instruction, and now even when I don't have anything in the pinhole pressing the switch down or whatever you have in there, it keeps letting me access CRP1 ENABLD and wont light back up or work as a keyboard. Just a big paperweight now :/

          Comment


          • #6
            Hi Snebbik,

            First, did you copy in the correct BIN file into the CRP1 ENABLD drive? The BIN file is the firmware, and that is required for the keyboard to operate. If you used an incorrect BIN file, then it won't work. Different keyboard models have different firmware BIN files.

            Second, after copying in the BIN file into the CRP1 ENABLD drive, for the system to recognize the keyboard, please reinsert the USB connector without pressing down on the pinhole switch.

            Comment


            • #7
              Originally posted by fuzun View Post

              Please provide new firmware for these issues. Almost 4 months have been passed.
              I agree there needs to be an updated firmware for this issue since I to have this issue reoccurring every month to two months. I have had to reset the firmware 3 times now.

              Comment

              Working...
              X