Crowzer Posted June 27, 2019 Share Posted June 27, 2019 (edited) I have an issue with the keyboard Corsair K70 RGB MK.2 bought a couple months ago. The keyboard is clean. PC specs in profile. After a bit the keyboard became stuck, no keys responding and I have to unplug it. - After I plug the keyboard back the issue is also back after a while - I even formated the PC (not only for keyboard) - I did the PAGEUP+PAGEDOWN reset - Forced firmware but no changes. I use the last version of iCUE (v3.17.94) and Windows 10 1903. Sould RMA ? Edited June 27, 2019 by Crowzer Link to comment Share on other sites More sharing options...
Corsair Employee Corsair Hotpot Posted July 3, 2019 Corsair Employee Share Posted July 3, 2019 PAGEUP+PAGEDOWN is not our reset process on this keyboard. Unplug the keyboard, hold down the ESC key and plug the keyboard back in while still holding the ESC key for 10 seconds. Let go and wait for the keyboard to show rainbow lighting and then unplug and plug the keyboard back in one final time. See if this helps with your issue. If not make a support ticket and they'll guide you on doing a hardreset before RMAing the unit. Link to comment Share on other sites More sharing options...
Farquaad Posted July 7, 2019 Share Posted July 7, 2019 exact the same probleme for me Windows 10 Pro 1903 ICue 3.17.94 K70 RGB MK.2 - Firmware 3.24 My Keyboard crash a lot (no keys responding)... i already try de soft reset but same probleme. Link to comment Share on other sites More sharing options...
Corsair Employee Corsair Hotpot Posted July 9, 2019 Corsair Employee Share Posted July 9, 2019 Can you make sure you have the latest Chipset and USB drivers installed for your motherboard? I recommend grabbing them from the manufacture site directly. Once you do that, try using a different USB port on a different stack to reinitialize the driver for the keyboard. Link to comment Share on other sites More sharing options...
Crowzer Posted August 31, 2019 Author Share Posted August 31, 2019 Oh sorry I forgot to reply. Issue fixed by changing a new keyboard from Amazon. Link to comment Share on other sites More sharing options...
Recommended Posts