reanimated35 Posted September 9, 2014 Share Posted September 9, 2014 Every time I connect the passthrough USB, windows keeps popping up saying it can't recognise the device. In device manager it shows as "Unknown USB Device (Device Descriptor Request Failed)" Any ideas how to fix this? Link to comment Share on other sites More sharing options...
Anorax Posted September 9, 2014 Share Posted September 9, 2014 Yes I have the same unknown device message on my Win 8.1. Link to comment Share on other sites More sharing options...
reanimated35 Posted September 9, 2014 Author Share Posted September 9, 2014 Not sure if it's related but since connecting the keyboard, when I shut the computer down it doesn't actually power off. It's only been doing that since using this keyboard. The fans and everything will still spin, and the power light stays on, the only way to completely turn it off is to switch off the power supply. I have to do that before I can restart the computer too. Link to comment Share on other sites More sharing options...
Corsair Employees Fauxbeard Posted September 9, 2014 Corsair Employees Share Posted September 9, 2014 Every time I connect the passthrough USB, windows keeps popping up saying it can't recognise the device. In device manager it shows as "Unknown USB Device (Device Descriptor Request Failed)" Any ideas how to fix this? In which order did you connect the USB cables and into which ports did you connect them to? Let me preempt and say that the power dongle (passthrough symbol) cable must be connected first into a USB port (USB 2.0 preferrably) before connecting the power/data cable (keyboard symbol). Not sure if it's related but since connecting the keyboard, when I shut the computer down it doesn't actually power off. It's only been doing that since using this keyboard. The fans and everything will still spin, and the power light stays on, the only way to completely turn it off is to switch off the power supply. I have to do that before I can restart the computer too. That is by design. Enable EuP or ErP setting in the power setting tab in your BIOS. That should turn off they keyboard lights when you shut down your computer. Link to comment Share on other sites More sharing options...
Anorax Posted September 9, 2014 Share Posted September 9, 2014 In which order did you connect the USB cables and into which ports did you connect them to? Let me preempt and say that the power dongle (passthrough symbol) cable must be connected first into a USB port (USB 2.0 preferrably) before connecting the power/data cable (keyboard symbol). Why the distinction between USB 2.0 and USB 3.0. Is this keyboard not compatible with USB 3.0? Regarding the "Unknown Device (Device Descriptor Request Failed)" message the order of plugging in the connectors made no difference. Even so I will ensure I connect the power cable in first before the data cable and also ensure I only use the USB 2.0 ports. Link to comment Share on other sites More sharing options...
fordjared Posted September 10, 2014 Share Posted September 10, 2014 I am having the exact same issue. I took the keyboard and installed it on my Windows 7 machine with no issues. It's only with my Windows 8.1 machine that I'm experiencing this issue. Also on every boot it suggests I do the firmware update which has already been successfully completed? Cheers Jared Link to comment Share on other sites More sharing options...
reanimated35 Posted September 10, 2014 Author Share Posted September 10, 2014 In which order did you connect the USB cables and into which ports did you connect them to? Let me preempt and say that the power dongle (passthrough symbol) cable must be connected first into a USB port (USB 2.0 preferrably) before connecting the power/data cable (keyboard symbol). That is by design. Enable EuP or ErP setting in the power setting tab in your BIOS. That should turn off they keyboard lights when you shut down your computer. Re the shutdown issue - that seems to have been fixed up after the latest firmware update and drivers. (Hadn't shut the PC down prior to making the post) Re the connection, I'll unplug it and try again in just a sec and let you know what happens. edit- exact same issue, nothing changes. Device most recently connected not recognised Link to comment Share on other sites More sharing options...
fordjared Posted September 10, 2014 Share Posted September 10, 2014 Okay I have it working with a rainbow profile I downloaded through the forum, however I am still getting "Unknown USB Device (Device Descriptor Request Failed)" in device manager which is the "power dongle (passthrough symbol)" cable. Let's hope the bugs are sorted out quickly. ** Worked for about 20 minutes , then keyboard colour got stuck on half the rainbow wave theme. Windows lock key/brightness button stopped working etc. ** Link to comment Share on other sites More sharing options...
nightst4r Posted October 3, 2014 Share Posted October 3, 2014 Windows 8.1 64-bit. Same problem, the keyboard works for about twenty minutes and then freezes. It takes multiple re-connects after that to get it working again. In the control software it says either ? ? for the version, or it says the version number and Malfunction for the status. Link to comment Share on other sites More sharing options...
vernz Posted October 17, 2014 Share Posted October 17, 2014 Same, windows 8.1 64 bit, when I plug the keyboartd in, I got a message that says usb isnt recognized, why that, any fix to that ? Link to comment Share on other sites More sharing options...
VoidSt4r Posted October 17, 2014 Share Posted October 17, 2014 I'm also experiencing issues with windows 8.1. When the computer goes to sleep all lights stays on (not sure if that's normal but that's not what I want). When I wake the computer, the firmware seems to have crashed and the CUE software hangs for a bit and then display the firmware update dialog so it does detect the keyboard. The keyboard itself still works (I can type) but some functions such as caps/num lock are not working. Replugging the keyboard fixes the issue. When it happened again, in the device and printers, I clicked on "troubleshoot" and windows told me "The USB device might have stopped responding" and it fixes the issue and it works again. That doesn't always work though. My logs show a lot of these messages: [2014-10-17T15:43:20]: Get status and mode failed. Execution result = 1, result = 0, platform error code = 121 [2014-10-17T15:43:20]: Get device info failed.Execution result = 1, result = 0, platform error code = 121, internal device status = 0. [2014-10-17T15:43:30]: Get status and mode failed. Execution result = 1, result = 0, platform error code = 121 [2014-10-17T15:43:45]: Get status and mode prepare failed. Execution result = 0, result = 1, platform error code = 0 [2014-10-17T15:43:45]: Get device info prepare failed.Execution result = 0, result = 1, platform error code = 0, internal device status = 0. [2014-10-17T15:43:55]: Get status and mode prepare failed. Execution result = 0, result = 1, platform error code = 0 [2014-10-17T15:43:55]: Get Serial Number timed out.Execution result = 0, result = 0, platform error code = 995, internal device status = 0. [2014-10-17T15:44:00]: Get status and mode prepare failed. Execution result = 0, result = 1, platform error code = 0 [2014-10-17T15:44:00]: Get Serial Number timed out.Execution result = 0, result = 0, platform error code = 995, internal device status = 0. Hope this helps. Link to comment Share on other sites More sharing options...
Corsair Employees Corsair James Posted October 17, 2014 Corsair Employees Share Posted October 17, 2014 Same, windows 8.1 64 bit, when I plug the keyboartd in, I got a message that says usb isnt recognized, why that, any fix to that ? Hi Vernz, I saw you post the problem you're having across multiple threads. Can you provide more details to your system? What hardware are you using, and what USB ports are you connected to? Did you do any BIOS and chipset updates lately? Link to comment Share on other sites More sharing options...
Corsair Employees Corsair James Posted October 17, 2014 Corsair Employees Share Posted October 17, 2014 I'm also experiencing issues with windows 8.1. When the computer goes to sleep all lights stays on (not sure if that's normal but that's not what I want). When I wake the computer, the firmware seems to have crashed and the CUE software hangs for a bit and then display the firmware update dialog so it does detect the keyboard. The keyboard itself still works (I can type) but some functions such as caps/num lock are not working. Replugging the keyboard fixes the issue. When it happened again, in the device and printers, I clicked on "troubleshoot" and windows told me "The USB device might have stopped responding" and it fixes the issue and it works again. That doesn't always work though. My logs show a lot of these messages: [2014-10-17T15:43:20]: Get status and mode failed. Execution result = 1, result = 0, platform error code = 121 [2014-10-17T15:43:20]: Get device info failed.Execution result = 1, result = 0, platform error code = 121, internal device status = 0. [2014-10-17T15:43:30]: Get status and mode failed. Execution result = 1, result = 0, platform error code = 121 [2014-10-17T15:43:45]: Get status and mode prepare failed. Execution result = 0, result = 1, platform error code = 0 [2014-10-17T15:43:45]: Get device info prepare failed.Execution result = 0, result = 1, platform error code = 0, internal device status = 0. [2014-10-17T15:43:55]: Get status and mode prepare failed. Execution result = 0, result = 1, platform error code = 0 [2014-10-17T15:43:55]: Get Serial Number timed out.Execution result = 0, result = 0, platform error code = 995, internal device status = 0. [2014-10-17T15:44:00]: Get status and mode prepare failed. Execution result = 0, result = 1, platform error code = 0 [2014-10-17T15:44:00]: Get Serial Number timed out.Execution result = 0, result = 0, platform error code = 995, internal device status = 0. Hope this helps. Hi Void, there is a workaround to getting your keyboard to turn off when the system is in sleep mode or to turn off. Go into your BIOS and enable ErP (if available) and then change your sleep mode to S3 (which will allow any key press to wake the system). This will disable the lighting but still allow the keyboard on key press to wake the system. We are aware of the issue with the software upon awakening from sleep, but you don't need to unplug the keyboard. You can simply restart the software to re-establish connection with the keyboard (or toggle the BIOS switch). Link to comment Share on other sites More sharing options...
Protocol48 Posted October 17, 2014 Share Posted October 17, 2014 Go to the Motherboard Bios and there find the USB section. I changed mine from "Only USB devices that are attached" to check all ports, as with an SSD, a couple of my devices including the keyboard take a "second" to be "seen". I had to keep unplugging/replugging the devices. So this fix worked for me, so then I changed the Bios to "Fast Boot", which saves me time, and I never had another problem with this keyboard. Link to comment Share on other sites More sharing options...
vernz Posted October 18, 2014 Share Posted October 18, 2014 Hi Vernz, I saw you post the problem you're having across multiple threads. Can you provide more details to your system? What hardware are you using, and what USB ports are you connected to? Did you do any BIOS and chipset updates lately? I reinstalled windows 8.1 today, with lastest chipset, bios everything from the asus support drivers, I have windows 8.1, asus maximus VII hero z97 chipset, I tried both usb 2.0 and 3.0 still the error unknown device Link to comment Share on other sites More sharing options...
Corsair Employees Corsair James Posted October 19, 2014 Corsair Employees Share Posted October 19, 2014 I reinstalled windows 8.1 today, with lastest chipset, bios everything from the asus support drivers, I have windows 8.1, asus maximus VII hero z97 chipset, I tried both usb 2.0 and 3.0 still the error unknown device Are you getting the unknown device even when only using one of the USB connectors from the keyboard for USB 3.0? Link to comment Share on other sites More sharing options...
vernz Posted October 19, 2014 Share Posted October 19, 2014 Are you getting the unknown device even when only using one of the USB connectors from the keyboard for USB 3.0? The one with the keyboard on it, no the one with arrows yeah I do, but CUE will freeze and I'll have the other problem malfunction, so yeah I don't get any unknown device with the one with a keyboard on it, thanks for the reply. As I said before, I tested it on my windows 7 computer, had not problem at all, no unknown device. Link to comment Share on other sites More sharing options...
vernz Posted October 19, 2014 Share Posted October 19, 2014 Well, I installed windows 7 on this system, its working great, windows 8.1 is the problem Link to comment Share on other sites More sharing options...
terabyte Posted October 19, 2014 Share Posted October 19, 2014 Seems that a lot of people having issues have a z97 chipset, at least I've seen plenty of this reports around here on the forum. Link to comment Share on other sites More sharing options...
vernz Posted October 19, 2014 Share Posted October 19, 2014 Depends, it works on windows 7 on the same system, I'll keep windows 7 ATM. Link to comment Share on other sites More sharing options...
ErrorNumber419 Posted October 21, 2014 Share Posted October 21, 2014 Is there any update to this? I am running into the same problems with mine. I have: Updated firmware and software. Uninstalled Removed corsair directories in C:\Users\...\AppData\Roaming\ as well as Local. Rebooted Reinstalled I have tried all of the above on USB 2 as well as USB 3. [2014-10-21T17:07:22]: Get Serial Number timed out.Execution result = 0, result = 0, platform error code = 995, internal device status = 0. [2014-10-21T17:07:27]: Get status and mode prepare failed. Execution result = 0, result = 1, platform error code = 0 [2014-10-21T17:07:27]: Get Serial Number timed out.Execution result = 0, result = 0, platform error code = 995, internal device status = 0. [2014-10-21T17:08:18]: Get status and mode prepare failed. Execution result = 0, result = 1, platform error code = 0 [2014-10-21T17:08:18]: Get device info prepare failed.Execution result = 0, result = 1, platform error code = 0, internal device status = 0. [2014-10-21T17:08:28]: Get status and mode prepare failed. Execution result = 0, result = 1, platform error code = 0 [2014-10-21T17:08:28]: Get device info prepare failed.Execution result = 0, result = 1, platform error code = 0, internal device status = 0. [2014-10-21T17:08:38]: Get status and mode prepare failed. Execution result = 0, result = 1, platform error code = 0 [2014-10-21T17:08:38]: Get Serial Number timed out.Execution result = 0, result = 0, platform error code = 995, internal device status = 0. [2014-10-21T17:08:43]: Get status and mode prepare failed. Execution result = 0, result = 1, platform error code = 0 [2014-10-21T17:08:43]: Get Serial Number timed out.Execution result = 0, result = 0, platform error code = 995, internal device status = 0. [2014-10-21T17:11:26]: Get status and mode failed. Execution result = 1, result = 0, platform error code = 121 [2014-10-21T17:11:26]: Get device info failed.Execution result = 1, result = 0, platform error code = 121, internal device status = 0. [2014-10-21T17:11:36]: Get status and mode failed. Execution result = 1, result = 0, platform error code = 121 [2014-10-21T17:11:51]: Get status and mode prepare failed. Execution result = 0, result = 1, platform error code = 0 [2014-10-21T17:11:51]: Get device info prepare failed.Execution result = 0, result = 1, platform error code = 0, internal device status = 0. [2014-10-21T17:12:01]: Get status and mode prepare failed. Execution result = 0, result = 1, platform error code = 0 [2014-10-21T17:12:01]: Get Serial Number timed out.Execution result = 0, result = 0, platform error code = 995, internal device status = 0. [2014-10-21T17:12:06]: Get status and mode prepare failed. Execution result = 0, result = 1, platform error code = 0 [2014-10-21T17:12:06]: Get Serial Number timed out.Execution result = 0, result = 0, platform error code = 995, internal device status = 0. [2014-10-21T17:18:01]: Get status and mode prepare failed. Execution result = 0, result = 1, platform error code = 0 [2014-10-21T17:18:01]: Get Serial Number timed out.Execution result = 0, result = 0, platform error code = 995, internal device status = 0. [2014-10-21T17:18:06]: Get status and mode prepare failed. Execution result = 0, result = 1, platform error code = 0 [2014-10-21T17:18:06]: Get Serial Number timed out.Execution result = 0, result = 0, platform error code = 995, internal device status = 0. Link to comment Share on other sites More sharing options...
Grippy Posted October 23, 2014 Share Posted October 23, 2014 Well, I installed windows 7 on this system, its working great, windows 8.1 is the problem No the keyboard and/or software is the problem Link to comment Share on other sites More sharing options...
vernz Posted October 24, 2014 Share Posted October 24, 2014 No the keyboard and/or software is the problem Why then I didnt have any ISSUE for 1 week now on window 7, no malfunction, and it's recognized Link to comment Share on other sites More sharing options...
Glen_Accounting Posted October 26, 2014 Share Posted October 26, 2014 Why then I didnt have any ISSUE for 1 week now on window 7, no malfunction, and it's recognized I think the point that's being made is that keyboards are designed around OS's, not the other way around. The point is the onus is on Corsair to fix this, which given that this has been happening for a month and not really been addressed as far as I can tell, Corsair is not making it a top priority. I'm running into the same problems. I hope this is being fixed... Link to comment Share on other sites More sharing options...
Corsair Employees Corsair James Posted October 29, 2014 Corsair Employees Share Posted October 29, 2014 I think the point that's being made is that keyboards are designed around OS's, not the other way around. The point is the onus is on Corsair to fix this, which given that this has been happening for a month and not really been addressed as far as I can tell, Corsair is not making it a top priority. I'm running into the same problems. I hope this is being fixed... It is a top priority as a fix but it's also very difficult to track the issue as it works on some USB 2.0, some 3.0, etc. We also are investigating the various USB controllers directly to see if that may be a cause too. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.