Updated FW and CUE SW, Scimitar Malfunctions Now

sbeard90 · February 9, 2016

I was prompted many times this morning to update software and firmware for my Scimitar mouse and now the thumb buttons are not working. I am currently running on SW 1.15.36 and FW 2.01 (BL 0.02). It says under devices that the status is "malfunction". I have tried restarting, changing usb ports, updating software and firmware and I still have had no luck. I don't have a second computer to try this on because this is my only one. Also every time I tried to upload my log files, it tells me "invalid file". I will attempt to just quote the most recent log.

[2016-02-09T11:27:38]: UserSessionInfo: locked changed to 0.

[2016-02-09T11:27:38]: UserSessionInfo: connected changed to 1.

[2016-02-09T11:27:38]: UserSessionInfo: local changed to 1.

[2016-02-09T11:27:40]: UserSessionInfo: locked changed to 0.

[2016-02-09T11:27:40]: UserSessionInfo: connected changed to 1.

[2016-02-09T11:27:40]: UserSessionInfo: local changed to 1.

[2016-02-09T11:27:41]: UserSessionInfo: locked changed to 0.

[2016-02-09T11:27:41]: UserSessionInfo: connected changed to 1.

[2016-02-09T11:27:41]: UserSessionInfo: local changed to 1.

[2016-02-09T11:27:55]: Failed to open device: vid=1b1c pid=1b1e path=\\?\hid#vid_1b1c&pid_1b1e&mi_00#7&1bcd8b92&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

[2016-02-09T11:27:55]: Failed to open device: vid=1b1c pid=1b1e path=\\?\hid#vid_1b1c&pid_1b1e&mi_01&col01#7&89d6f54&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

[2016-02-09T11:27:55]: Created new device object: Scimitar; ready: 0

[2016-02-09T11:27:55]: Attached to device object Scimitar: b=1 a=1

[2016-02-09T11:27:55]: Attached to device object Scimitar: b=1 a=0

[2016-02-09T11:27:55]: Initializing Scimitar...

[2016-02-09T11:27:55]: Device profile (meta) for device vid=413c pid=2003 not found.

[2016-02-09T11:28:00]: Get device info failed.Device : Scimitar,Execution result = 1, result = 0, platform error code = 121.

[2016-02-09T11:28:05]: Get device info failed.Device : Scimitar,Execution result = 1, result = 0, platform error code = 121.

[2016-02-09T11:28:10]: Get device info failed.Device : Scimitar,Execution result = 1, result = 0, platform error code = 121.

[2016-02-09T11:28:15]: Get device info failed.Device : Scimitar,Execution result = 1, result = 0, platform error code = 121.

[2016-02-09T11:28:20]: Get device info failed.Device : Scimitar,Execution result = 1, result = 0, platform error code = 121.

[2016-02-09T11:28:25]: Get device info failed.Device : Scimitar,Execution result = 1, result = 0, platform error code = 121.

[2016-02-09T11:28:30]: Get device info failed.Device : Scimitar,Execution result = 1, result = 0, platform error code = 121.

[2016-02-09T11:28:35]: Get device info failed.Device : Scimitar,Execution result = 1, result = 0, platform error code = 121.

[2016-02-09T11:28:40]: Get device info failed.Device : Scimitar,Execution result = 1, result = 0, platform error code = 121.

[2016-02-09T11:28:40]: Initializing Scimitar: spent all tries on getDeviceInfo().

[2016-02-09T11:28:40]: Initializing Scimitar: failed.

[2016-02-09T11:28:40]: Get device info failed. request timed out for Scimitar

[2016-02-09T11:28:40]: Initialized (st=0) Scimitar.

[2016-02-09T11:28:45]: Get device info failed.Device : Scimitar,Execution result = 0, result = 0, platform error code = 121.

[2016-02-09T11:28:45]: Device object failed to initialize, so it won't be registered with application susbystems. Scimitar.

[2016-02-09T11:29:16]: Firmware Update: started 'C:/Program Files/Corsair/Corsair Utility Engine/fwupd path=\\?\hid#vid_1b1c&pid_1b1e&mi_02#7&31081d1d&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} path=\\?\hid#vid_1b1c&pid_1b1e&mi_01&col04#7&89d6f54&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030} image=C:\Users\TP108\AppData\Local\Temp\TK2024.Scimitar_App_V201.bin usb-vid=1b1c usb-pid=1b1e hid-up=ffc2 test-storage=true' (2).

[2016-02-09T11:29:30]: Firmware Update: tool exit code: 0, exit status: 0. Normal stop: 1

[2016-02-09T11:29:34]: Device vid=1b1c pid=1b1e is marked 'slow startup'.

[2016-02-09T11:29:35]: Created new device object: Scimitar; ready: 0

[2016-02-09T11:29:35]: Attached to device object Scimitar: b=1 a=1

[2016-02-09T11:29:35]: Attached to device object Scimitar: b=1 a=0

[2016-02-09T11:29:35]: Initializing Scimitar...

[2016-02-09T11:29:35]: Failed to open device: vid=1b1c pid=1b1e path=\\?\hid#vid_1b1c&pid_1b1e&mi_00#7&1bcd8b92&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

[2016-02-09T11:29:35]: Failed to open device: vid=1b1c pid=1b1e path=\\?\hid#vid_1b1c&pid_1b1e&mi_01&col01#7&89d6f54&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

[2016-02-09T11:29:37]: Firmware Update: killing...

[2016-02-09T11:29:37]: Firmware Download: Aborting idle process not supported.

[2016-02-09T11:29:40]: Get device info failed.Device : Scimitar,Execution result = 1, result = 0, platform error code = 121.

[2016-02-09T11:29:45]: Get device info failed.Device : Scimitar,Execution result = 1, result = 0, platform error code = 121.

[2016-02-09T11:29:50]: Get device info failed.Device : Scimitar,Execution result = 1, result = 0, platform error code = 121.

[2016-02-09T11:29:55]: Get device info failed.Device : Scimitar,Execution result = 1, result = 0, platform error code = 121.

[2016-02-09T11:30:00]: Get device info failed.Device : Scimitar,Execution result = 1, result = 0, platform error code = 121.

[2016-02-09T11:30:05]: Get device info failed.Device : Scimitar,Execution result = 1, result = 0, platform error code = 121.

[2016-02-09T11:30:10]: Get device info failed.Device : Scimitar,Execution result = 1, result = 0, platform error code = 121.

[2016-02-09T11:30:15]: Get device info failed.Device : Scimitar,Execution result = 1, result = 0, platform error code = 121.

[2016-02-09T11:30:20]: Get device info failed.Device : Scimitar,Execution result = 1, result = 0, platform error code = 121.

[2016-02-09T11:30:20]: Initializing Scimitar: spent all tries on getDeviceInfo().

[2016-02-09T11:30:20]: Initializing Scimitar: failed.

[2016-02-09T11:30:20]: Get device info failed. request timed out for Scimitar

[2016-02-09T11:30:20]: Initialized (st=0) Scimitar.

[2016-02-09T11:30:20]: Device object failed to initialize, so it won't be registered with application susbystems. Scimitar.

[2016-02-09T11:30:25]: Get device info failed.Device : Scimitar,Execution result = 0, result = 0, platform error code = 121.

[2016-02-09T11:30:36]: Device vid=1b1c pid=1b1e is marked 'slow startup'.

[2016-02-09T11:30:37]: Created new device object: Scimitar; ready: 0

[2016-02-09T11:30:37]: Attached to device object Scimitar: b=1 a=1

[2016-02-09T11:30:37]: Attached to device object Scimitar: b=1 a=0

[2016-02-09T11:30:37]: Initializing Scimitar...

[2016-02-09T11:30:37]: Failed to open device: vid=1b1c pid=1b1e path=\\?\hid#vid_1b1c&pid_1b1e&mi_00#7&1bcd8b92&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

[2016-02-09T11:30:37]: Failed to open device: vid=1b1c pid=1b1e path=\\?\hid#vid_1b1c&pid_1b1e&mi_01&col01#7&89d6f54&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

[2016-02-09T11:30:37]: Get angle snap prepare failed. Current storage 1. request timed out for Scimitar

[2016-02-09T11:30:37]: Get angle snap failed. Current storage 1. request timed out for Scimitar

[2016-02-09T11:30:42]: Get angle snap failed. Current storage 1.Device : Scimitar,Execution result = 0, result = 0, platform error code = 121.

[2016-02-09T11:30:43]: Get angle snap failed. Current storage 1. request timed out for Scimitar

[2016-02-09T11:30:43]: Device profile (meta) for device vid=413c pid=2003 not found.

[2016-02-09T11:30:48]: Get angle snap failed. Current storage 1.Device : Scimitar,Execution result = 0, result = 0, platform error code = 121.

[2016-02-09T11:30:48]: Get current dpi index (-1) failed. Current storage 1. request timed out for Scimitar

[2016-02-09T11:30:53]: Get current dpi index (-1) failed. Current storage 1.Device : Scimitar,Execution result = 0, result = 0, platform error code = 121.

[2016-02-09T11:30:53]: Get current dpi index (-1) failed. Current storage 1. request timed out for Scimitar

[2016-02-09T11:30:58]: Get current dpi index (-1) failed. Current storage 1.Device : Scimitar,Execution result = 0, result = 0, platform error code = 121.

[2016-02-09T11:30:59]: Get current dpi index (-1) failed. Current storage 1. request timed out for Scimitar

[2016-02-09T11:31:04]: Get current dpi index (-1) failed. Current storage 1.Device : Scimitar,Execution result = 0, result = 0, platform error code = 121.

[2016-02-09T11:31:04]: Get current dpi index (0) failed. Current storage 1. request timed out for Scimitar

[2016-02-09T11:31:07]: SdkController. Requesting working state leave because of transition to Suspended or Shutdown state.

[2016-02-09T11:31:07]: Requesting working state leave because of transition to Suspended or Shutdown state.

[2016-02-09T11:31:07]: Leaving working state.

[2016-02-09T11:31:09]: Get current dpi index (0) failed. Current storage 1.Device : Scimitar,Execution result = 0, result = 0, platform error code = 121.

[2016-02-09T11:31:09]: Get current dpi index (0) failed. Current storage 1. request timed out for Scimitar

Elestriel · February 9, 2016

I'm working with Corsair to figure this out. A lot of people have been reporting it. I have a Scimitar at home so I'll be able to see if I can reproduce the issue tonight.

For now, hang tight.

sbeard90 · February 9, 2016

Thanks for the quick response! Ill keep an eye out for a fix

Inheritance · February 9, 2016

Thanks for the quick response! Ill keep an eye out for a fix

contact Corsair Support and see if they help you with a hard firmware reset on the Scimitar.

Corsair James · February 10, 2016

Sbeard90, can I get the hardware specs for your system?

blamethedingus · February 11, 2016

Sbeard90, can I get the hardware specs for your system?

The specs of ones computer are going to be irrelevant in the fact that its a flaw in the firmware of the Scimitar that causes it to not be correctly recognized, quickest solution is to force update (push update) to the past firmware or make easily and readily available to the public to download so those who are affected can downgrade to re-enable the functionality of their mouse until a further patch is available to the firmware correcting the issue

Jkraghify · February 11, 2016

The specs of ones computer are going to be irrelevant in the fact that its a flaw in the firmware of the Scimitar that causes it to not be correctly recognized, quickest solution is to force update (push update) to the past firmware or make easily and readily available to the public to download so those who are affected can downgrade to re-enable the functionality of their mouse until a further patch is available to the firmware correcting the issue

Specs are totally relevant. Yes, it's a flaw with the firmware - but all the hardware this firmware/software was tested on played nicely with it. PC specs are valuable because it gives Corsair information necessary to investigate why the new firmware/software fails to function as intended on some computers.

I believe if you PM Corsair Henry with your email asking for the previous firmware he will give it to you. Old versions of CUE are available on Zheren's FAQ thread

sbeard90 · February 11, 2016

Sbeard90, can I get the hardware specs for your system?

::: BIOS

Name : Phoenix ROM BIOS PLUS Version 1.10 A16

Manufacturer : Dell Inc.

Version : DELL - 15

::: Motherboard

Product name : 0M858N

Manufacturer : Dell Inc.

::: CPU

Name : Intel® Core2 Duo CPU E7300 @ 2.66GHz

Description : x64 Family 6 Model 23 Stepping 6

Frequency : 2667

Number of cores : 2

Number of logical processors : 2

::: Physical memory

Manufacturer : AD00000000000000

Speed : 800

Form factor : DIMM

Memory type : DDR2

Capacity : 1024 MB

Manufacturer : AD00000000000000

Speed : 800

Form factor : DIMM

Memory type : DDR2

Capacity : 1024 MB

Manufacturer : AD00000000000000

Speed : 800

Form factor : DIMM

Memory type : DDR2

Capacity : 1024 MB

Manufacturer : AD00000000000000

Speed : 800

Form factor : DIMM

Memory type : DDR2

Capacity : 1024 MB

::: USB Controller

Name : Intel® ICH10 Family USB Enhanced Host Controller - 3A6A

Manufacturer : Intel

Name : Intel® ICH10 Family USB Enhanced Host Controller - 3A6C

Manufacturer : Intel

Name : Intel® ICH10 Family USB Universal Host Controller - 3A64

Manufacturer : Intel

Name : Intel® ICH10 Family USB Universal Host Controller - 3A65

Manufacturer : Intel

Name : Intel® ICH10 Family USB Universal Host Controller - 3A66

Manufacturer : Intel

Name : Intel® ICH10 Family USB Universal Host Controller - 3A67

Manufacturer : Intel

Name : Intel® ICH10 Family USB Universal Host Controller - 3A68

Manufacturer : Intel

Name : Intel® ICH10 Family USB Universal Host Controller - 3A69

Manufacturer : Intel

::: OS

Name : Microsoft Windows 7 Professional

Architecture : 32-bit

Service pack version, major : 1

Service pack version, minor : 0

::: User properties

Is run under administrator : no

User has administrator privileges : yes

::: Video hardware

Adapter name : ATI Radeon HD 3450 (Microsoft Corporation WDDM 1.1)

Driver files : atidxx32.dll,atidxx64,atiumdag.dll,atiumdva.cap,atiumd64,atiumd6a,atitmm64

Driver version : 8.56.1.16

RAM : 256 MB

Max refresh rate : 75

Min refresh rate : 56

::: Displays

Name : Generic PnP Monitor

Resolution : 1600 x 900

Refresh rate : 60

Color depth : 32

Connected to : ATI Radeon HD 3450 (Microsoft Corporation WDDM 1.1)

Name : Generic PnP Monitor

Resolution : 1600 x 900

Refresh rate : 60

Color depth : 32

Connected to : ATI Radeon HD 3450 (Microsoft Corporation WDDM 1.1)

::: Storage

Model : ST380815AS ATA Device

Interface type : IDE

Manufacturer : (Standard disk drives)

Size : 74.5049 GB

Model : WDC WD800AAJS-75M0A0 ATA Device

Interface type : IDE

Manufacturer : (Standard disk drives)

Size : 74.5049 GB

::: Chipset

Short name : Intel® 4 Series Chipset Processor to I/O Controller - 2E10

Name : Intel® 4 Series Chipset Processor to I/O Controller - 2E10

Manufacturer : Intel

Short name : Intel® 4 Series Chipset PCI Express Root Port - 2E11

Name : Intel® 4 Series Chipset PCI Express Root Port - 2E11

Manufacturer : Intel

Service : pci

::: Corsair devices

: No device found.

::: Keyboard layouts

Language ID : 0x1033

Layout ID : 0x1033

Name : English

Anonrate · February 14, 2016

Have been getting the same issue for quite some time now. I'm rather really disappointed in the time that it has taken for anything to be done. I'm aware that you guys are a big company, but that's one of the major process that need to be taken care of when releasing a new product. Properly test it and work on fixing any errors/problems etc... There is or sales are going to go down and possibly even have the product being recalled. I have already noticed that sales on this particular mouse have gone down.

But to be more specific with my problem, it's exactly the same so to speak. Same error code "121", and it always ask me to re-update the firmware every time I restart the computer or CUD. It also is never recognized in the CUD tray on the bottom. In the Settings>Device it is however.

Forcing the update from server also does not do anything but replicate the results for me.

I really hope you guys fix this because I am a Avid user of Corsair and am wanting to build my new PC around your parts, but if I can't have the mouse, the PC will not be complete because it doesn't even "Mouse Corsair". :(

Toasted · February 14, 2016

@Anonrate

PM Corsair Henry with your email for the previous firmware update file.

So first let me apologize some of you are experiencing this issue with Scimitar. I don't know how this issue started but to give you all some background, I asked Corsair Henry to give out 1.15 as a beta (along with FW 2.01) prior to this release being public. I also have given it out to the official beta testers. This meant that we had at least 40 people with very different hardware configurations (not counting internal QA) test this SW and FW together to ensure it was a smooth experience. We also wanted to ensure it solved the rare problem of Scimitar timing out every now and then.

Out of the 40+ people, we didn't receive a single case of negative feedback where it broke something and our internal testing confirmed this. This is why the issue some of you are reporting is quite perplexing. However, we are putting all of our resources into this to investigate and it may take a few days to gather the information and attempt to reproduce the issue. As of right now, we don't have any systems that can do it so your logs have been well appreciated. We'll do what we can in the quickest turnaround possible.

Sorry for the inconvenience.

http://forum.corsair.com/v3/showpost.php?p=836162&postcount=10

Grense · February 27, 2016

Hi just adding that I just bought a scimitar today and it feels solid, can't wait to start using it once this odd malfunction error goes away :) As soon as I installed the software I received the message that a new FW was available so I updated before even knowing any better. Bummer too since the MMO I bought the mouse to use in is opening its doors in less than 12 hours. I sent Corsair James an email with my specs, both logs that have generated so far and my 32 and 64 bit dxdiags. I do briefly recall seeing a post about rolling back firmware when I fist checked the forums today which I might try if it applies to my mouse, I have to find he post again to be sure.

Jkraghify · February 28, 2016

Hi just adding that I just bought a scimitar today and it feels solid, can't wait to start using it once this odd malfunction error goes away :) As soon as I installed the software I received the message that a new FW was available so I updated before even knowing any better. Bummer too since the MMO I bought the mouse to use in is opening its doors in less than 12 hours. I sent Corsair James an email with my specs, both logs that have generated so far and my 32 and 64 bit dxdiags. I do briefly recall seeing a post about rolling back firmware when I fist checked the forums today which I might try if it applies to my mouse, I have to find he post again to be sure.

Corsair Henry attached the old firmware to this post: http://forum.corsair.com/v3/showpost.php?p=837675&postcount=272

You can continue to use CUE 1.15.36 with this firmware. If you're still having problems, let the forums know :)

Updated FW and CUE SW, Scimitar Malfunctions Now

Recommended Posts

sbeard90

Link to comment

Share on other sites

Elestriel

Link to comment

Share on other sites

sbeard90

Link to comment

Share on other sites

Inheritance

Link to comment

Share on other sites

Corsair James

Link to comment

Share on other sites

blamethedingus

Link to comment

Share on other sites

Jkraghify

Link to comment

Share on other sites

sbeard90

Link to comment

Share on other sites

Anonrate

Link to comment

Share on other sites

Toasted

Link to comment

Share on other sites

Grense

Link to comment

Share on other sites

Jkraghify

Link to comment

Share on other sites

Archived

Activity