Win 10 update - Corsair HIDClass 3.0.88.0

[EasterEEL]

Windows 10 update updated Corsair HIDClass to v3.0.88.0 overnight. This is causing a looping BSOD System Thread Exception Not Handled with CorsairVBusDriver.sys.

 

I had to restore to an Acronis backup of my windows installation and of course Windows Update downloaded the update again with same BSOD issue.

 

Another restore and this time disconnected internet until I stopped Windows 10 from updating hardware drivers.

 

Googling the issue I can see quite a few of your customers complaining about BSOD and CorsairVBusDriver.sys. No obvious fix though.

 

What a load of rubbish your software and drivers are. Never buying another Corsair product that requires your software to be installed.

[Itchy2k]

I am posting this so that Corsair can at least know that PCs are being bricked and maybe come up with a procedure to help people. THIS IS A PROBLEM AND IT IS NOT ISOLATED AND IT IS CATASTROPHIC WHEN IT HAPPENS.

 

I woke up this morning and had an infinite BSOD loop due to CorsairVBus driver throwing a Thread_Uncaught exception, the same as original post. Evidently, it is some sort of incompatibility with older versions of Corsair VBus driver and the latest Windows updates. Rolling back Windows to prior install and trying to boot into safe mode made no difference... it looped into BSOD every time. I was in a bricked windows state.

 

However, I was able to fix it... but, do so at your own risk. I do not recommend you try this unless you know what you are doing.

 

What I did was, in the windows "advanced options" repair screen, go to command prompt. It is really the only thing you can do without BSODing aside from completely reinstalling Windows.

 

There are a few posts out there about using windows command prompt exectuable "DSIM" to uninstall the driver. This did not work for me, so I did an alternative approach.

 

What I did was navigate using DOS commands to C:/windows/system32/drivers.... There are 2 Corsair drivers there - CorsairVBusDriver.sys and there is also an CorsairVHidDriver.sys. You can search for them with the "dir" command. I deleted both with the DOS "del" command. Afterwards, I was able to boot into Windows.

 

Once I got Windows up and running. I immediately updated to the latest ICue software in hopes that it would never get into this state again. I haven't had an issue since.

Edited December 18, 2020 by Itchy2k

[EasterEEL]

I have the Strafe RGB keyboard (about six years old I guess not mk.2). I have CUE 1.16.42 software installed and pressing update tells me it is up to date. Is there a newer version I should be using as the web site is sort of indicating not?

 

So just using as a nice keyboard and it is ridiculous that a driver for a keyboard can trash windows installation. Good job I use Acronis for an image backup every month. Should the problem return, I might need to remove CorsairVBusDriver.sys which is on my system. I can't see it is being loaded, however it did cause the looping BSOD when Windows Update updated it.

 

CorsairVHidDriver.sys is also there and seems to be loaded with Corsair composite virtual input device, whatever that is.

 

I'm not too bothered about stopping Windows update from updating my hardware drivers. But surprised the Corsair one came through; normally I have a bunch driver updates sitting in "optional updates-driver updates", which I would have to choose allow to update (not really necessary unless they fix a problem).

Edited December 18, 2020 by EasterEEL

[Muda]

Awoke to a nice BSOD relating to the Corsairvbus driver. Luckily, I was able to restore to a prior restore point, remove the corsair drivers, disconnect the K70 keyboard (which is now non-functional) and everything seems OK. Turned off Windows 10 driver updates. Haven't tried to remove the driver files in system32 as they seem to be owned by the System but don't seem to be causing a problem anymore. My old Dell PS/2 port keyboard just keeps on kicking.

 

Maybe someone at Corsair can let us know what the proper course of action is at this point.

[Corsair Notepad]

I have the Strafe RGB keyboard (about six years old I guess not mk.2). I have CUE 1.16.42 software installed and pressing update tells me it is up to date. Is there a newer version I should be using as the web site is sort of indicating not?

 

So just using as a nice keyboard and it is ridiculous that a driver for a keyboard can trash windows installation. Good job I use Acronis for an image backup every month. Should the problem return, I might need to remove CorsairVBusDriver.sys which is on my system. I can't see it is being loaded, however it did cause the looping BSOD when Windows Update updated it.

 

CorsairVHidDriver.sys is also there and seems to be loaded with Corsair composite virtual input device, whatever that is.

 

I'm not too bothered about stopping Windows update from updating my hardware drivers. But surprised the Corsair one came through; normally I have a bunch driver updates sitting in "optional updates-driver updates", which I would have to choose allow to update (not really necessary unless they fix a problem).

 

That is the original CUE software and is as old as your keyboard. We are currently on CUE3 or iCUE which is used for most of our devices including the Strafe RGB keyboard.

 

The current version can be found by going to the Corsair website and navigating to the download page.

[Corsair Notepad]

What version of the CUE/iCUE software were you all using?

[EasterEEL]

As you know I'm using CUE 1.16.42 which advises it is up to date!

 

It is not particularly clear on the website that I could update the software (newer software is shown for Strafe mk.2; older version is shown for for legacy Strafe).

 

Anyway will try new version 3.36.125 and report back. Many thx.

[Muda]

I was using Cue2 and the Utility Engine 2.67

[RShibbs]

I'm running a K55 keyboard and a Harpoon wireless mouse (via wired USB) and have paused Windows updates for a little under a month so I don't brick this thing. Is there anything I can do to prevent the new Windows 10 update from causing an issue with Corsair drivers and throwing my system into a BSoD loop? I quite like these peripherals and if there's something I can do besides "Getting rid of these things and getting new ones from a different," I'd like to know.

Also, I saw iCue version mentioned somewhere, I have firmware V. 30.08, and I'm honestly quite hesitant to update that or any Corsair stuff until this issue is resolved. Or, if it can be resolved...

[Corsair Notepad]

I'm running a K55 keyboard and a Harpoon wireless mouse (via wired USB) and have paused Windows updates for a little under a month so I don't brick this thing. Is there anything I can do to prevent the new Windows 10 update from causing an issue with Corsair drivers and throwing my system into a BSoD loop? I quite like these peripherals and if there's something I can do besides "Getting rid of these things and getting new ones from a different," I'd like to know.

Also, I saw iCue version mentioned somewhere, I have firmware V. 30.08, and I'm honestly quite hesitant to update that or any Corsair stuff until this issue is resolved. Or, if it can be resolved...

 

The issue is with old versions of CUE which are no longer developed or actively supported. If you are running the iCUE software this is not an issue.

 

 

As for those of you with this issue the resolution is to utilize your system restore to restore the computer to a point before the Windows update, remove the old CUE1 or CUE2 software you have installed, update to the latest version of iCUE by downloading it from the Corsair website, and then updating Windows.