Jump to content
Corsair Community

icue + void problem


Recommended Posts

win7 64bits

--pro node (had to reinstall same usb update that was already installed to get it recognized in icue)

--, m65 pro rgb, strafe rgb (work fine)

--corsair void wireless > ISSUES

started right around end of warranty i think (battery suddenly never charged, wont charge : not a usage thing but I resolved to using it on usb charger permanent in order to still have audio from a 120 euro headset. Not the main issue.

 

MAIN ISSUE:

Recently I added the pro node to my setup, ofcourse my older CUE version didnt not recognize it so i updated stupidly to 4.1. Turns out that doesnt recognize this headset made by the your own company for whatever reason (I kinda would like to know, its not that old).

Found the ONLY other available iCUE version that recognizes the headset: 3.38.68. Installed it, after the usb update all peripherals show. I luck out, this version seems to support all my devices!

 

Now heres where the problems start.

1. Corsair void wireless starts up with sound, but when 'used' by programs, beyond the first application using the headset they will crash or produce no audio.I can watch a few hours of youtube vids but as soon as i load teamspeak and close a youtube tab and open it somewhere else it will fail within a few minnutes and lose audio. Keeping it in teamspeak for instance but causing icue to crash aswell The only way to get audio back is either by reinstalling icue, deinstalling void drivers on device manager, restarting two times, putting the dongle in a different usb and repairing,

----Or the fastest route: close icue (close the part that refuses to close in task manager, it prolly crashed because u actually wanted to use your headset) go to device manager and uninstall the corsair void headset driver, opt not to restart and put the dongle in a different usb. wait till it lights up. You might want to have headset powered off while doing this or not doesnt seem to really matter much. U will have audio again, until ofcourse u launch a program where u either want to use the microphone or select it from an input devices drop tab.

 

Things done:

1. Updated chipset/usb, latest versions

2. enabled xhci in bios

3. tried all usb ports with and without a dongle to distance for possible 2.4gh interference

4. updated firmware in icue to 3.092 or something it worked a few times, failed a few times, seems to just reinstall same audio driver on pc and do nothing but power of the headset and reiniate it. Also after completing that it will show as not connected with a yellow sign (while working) or as charging (soon to lose audio) with a previous set backlight setting.

5. scoured all forum posts relating to the corsair void and to my suprise if found more questions than fixing replies. Most end up in RMA.

I dont want an RMA, i want this thing that obviously works, has worked to work again. The only difference is the driver used by the void in this Icue? Can u send me the driver from an older CUE version for the VOID because you have not listed any downloads for firmware or older cue software/drivers anyhere and those that are go to a dead link download section of corsair,

 

Thanks for any help, i await your reply @Corsair team

Link to comment
Share on other sites

after investigating the idea that somehow some of the wrong drivers are loaded causing icue to glitch out i figure perhaps it has something to do with signed drivers. Did they lapse? Because when i disable fast boot in my BIOS now (all i saw was this or CSM options and i wasnt touching those) so i figure i give it that a shot, the boot wasnt slowed down by it. BUT for the first time i was able to join discord and unmute/mute my audio and mic (didnt test if it actually worked yet) without insta crash ( i had it working once but it cause icue to crash in the end before the fast boot disablement) but on default device. Discord closed without crashing. I checked Teamspeak after it seemed to work and upon starting it gave a warning that my headset listed as Corsair (VOID RGB WIRELESS) or something wasnt available (true, i have only seen it listed in devices of software as (2 VOID RGB WIRELESS) as if a duplicate of something. (Possible prior driver set or something involving interfering with current?) . Anyway I left teamspeak on default on both aswell and tested that seemed to work, also closed without crash. Normally i would have atleast one iCUE crash by now but still nothing. I checked with windows voice recorder if it was actually taking input and putting it thru and not just 'finding it' and it was a decent recording. And i checked some browser youtube vids in reloads in between to check if the driver crashed the audio as it would do previously causing videofiles to either spin load forever n crash with a 'wait for bla to load

' or play without audio.

 

Havent tried having OBS open yet I will next and keep on the look for crashes.

 

-Anyone know if iCue software requires AERO to be active to prevent crashes?

 

-Possible recognition problem of two registered CORSAIR VOID RGB WIRELESS as a 'deleted /whitespaced version 1/0) and the showing up but malfunctioning 2 CORSAIR VOR RGB WIRELESS

 

thinking possible cause could be the installation of iCue 4.1s audio driver that is incompatible with the VOID RGB creating nr1 and the second install doesnt override that with 3.38, causing some type of input device glitch problem in programs on the microphone mostly where default will be going to 2 and 2 isnt loaded propperly driverwise or recognition wise somehow. T

-That gets me to why is the 3.38 not recognized properly and i got to the driver signing part and booting with signed drivers /fast-slow boot.

Link to comment
Share on other sites

obs worked recording to after setting device to default.

 

So to list the things ive done to get this to work so far for others

 

Setup: Z170 Pro Gaming, 970GTX 630W gold+ 16gb

5 LL120MM RGB corsair

Lightening node pro

Strafe RGB

M65 Pro RGB

+qck prism cloth usb mousemat

VOID RGB Wireless Headset on perma usb for battery does not charge.

 

with issue: microphone causing program freezes, icue freezes, loss of audio, system crashes.

 

current working solution:

iCue 3.38.61

enabled XHCI in bios motherb

disabled fast boot in bios motherb

went into devices previously and uninstalled the headset under sound devices and took the driver from the programfiles/corsair/driver/audio.

"Put the headset to off directly after booting (so it does not take icue light setup) but then relaunch it again with powerbutton and wait a few sec till after the red light it turns green. (not sure i had to do this after last boot. mighve still been on green (is not the solid color choice))"

 

not touching headset in iCUE, it states charging and firmware update available. Might be tempted to do that now i disabled fast boot.

 

Would it perhaps be the magical path to get the battery to even recharge again?

 

+ I still havent solved the issue where it should just be listed as a single device with no 2 in its name as some duplicate that from the looks of it still lingers around

Link to comment
Share on other sites

iCUE crashed at 6:45 after being stable around 2 hours playing a game with steam on in background + discord. It closed itself (fans went rainbow) but still had a remainder open i had to end in task manager. Restarted it, kept game open and it seems as before the iCUE crash.
Link to comment
Share on other sites

downloaded iCue 3.34.170 from https://www.driverscloud.com/

tested a few of the mic using programs that caused crashes earlier, managed to actually put input device to the headset instead of default on all of them which which is new.

Interestingly system seems a lot smoother at the beginning of these start up after new drivers compared to 4-5 hours in.

 

On this one it says battery 100% instead of charging or not connected also new,

lets see how long this lasts ;)

Link to comment
Share on other sites

more additions made:

in Administrative Tools > Services i have put all options in recovery tab of the 'Windows Audio' and the Windows Audio something something under it to auto reconnect.

 

I also put iCUE on a list of exception made programs in PrecisionXserver64 in case theres some OSD problem between the two programs. my card is an evga leafblower.

 

For a while it seems somehow my videocard suddenly thermothrottled for a single start up but went back to its regular allways close to full setting i prefer (the throttling causes jitter in games).

 

The headset is still kinda the same but now when the audio fails where it used to completely go it reloads it in a fashion that works but doesnt seem to satisfy the OS much and cause playing audio to have a stutter or high pitch 1-2ms blliep sound on failure before it restarts, or when to many programs use the audio drivers.

 

Another new addition is some sporadic loss of network.

 

I also noticed i use Asus AI and it might also interfer with iCUE. That would make it the ?th program on the list to interfer? Added to that i found theres an Asus AI Charger+ option to quick recharge iphones and such, i wonder if that was enabled previously tanking the battery of the corsair void, small possibility since i had it on disabled.

 

Programs having problems with iCUE/audio drivers:

1. All microphone using programs

2. Having multiple sources of audio/input overlapping each other

3. Windows itself (usb drivers)

4. Discord (glitches during start up or conversations (disappearing icons, app audio warnings delayed)

5. PrecisionX16 (perhaps this has to do with iCUE dashboard)

6. Asus AI

7. iCUe with itself (some crashes a leftover part remains that does not close automatically > needs to be shut down in task manager before restarting app is possible.

8. Steam (being called sound delayed, entering a voice talk takes ages n glitches 2 out of 3 times, glitches in steamsoftware connecting to input)

9. im prolly forgetting some things.

 

After reboots i have to shutdown headset 1 or 2 times to get it to the green light (not greyed out or disco bling). It will say charging but it won't charge **** (ive opened it up to check out the battery yesterday and it was puffed up af like most ive seen on youtube before replacements). After a while it gives up and say charge complete. Usually it doesnt take long after this for the first big problems to arise like the audio falling away or the input device bug (like the entire thing just de-registered) but shows no signs of being off (neither dongle or headset) but it seems after all my changes that just exiting and reloading iCUE fixes this altho it introduces some noticable system lag compared to previous operation (like things are waiting for a certain audio driver to kick in a lot, because im fighting autodisconnects with autoreconnects like a swampbrain).

 

Theres not much left for me to do other than try and swap out the battery in the headset for a replacement, try and reinstall reconnect and attempt the exit bootloader mute button (i can't now it will just power off as theres not enough remaining battery). I looked around for the specific battery but it seems both expensive local or real iffy from some chinese ebay equivalents. Im no great solderer and would prefer my replacement to have the PS plug included. I was thinking this might work: https://shoppingcart.aliexpress.com/shopcart/shopcartDetail.htm?spm=a2g0o.detail.0.0.35bbd20fya4Ok4

Link to comment
Share on other sites

ive noticed this in USBdeview;

 

perhaps.jpg

 

The usbaudio.sys wireless headset one is not enabled in the list and cant be for some reason

 

The hidusb is on the Wireless Headset on that is enabled and the Dongle is on usbccgp.sys and enabled. It does not list the names of the mouse or keyboard but they are also on a usbcgp sys and enabled.

Link to comment
Share on other sites

that might have been a double dongle entry.

Listed as 100mA.

I did an iCUE repair after changing the windows driver automatic update to only when nothing found on pc but i fear it all changed nothing

Link to comment
Share on other sites

i performed a clean install of 3.15

by cleaning service and regedit local machine etc of corsair maps, in local machine system currentcontrolset services i found an old entry to a corsair vengeance headset i had years ago (also just died one day but was pretty old and banged up so that was a logical one).

 

It seems to have somehow changed the issue, it now does register the microphone and allows me to use it and switch different programs n audio inputs while using it.

The headset goes green lit on the big led on side and is not responsive to the volume button. It also every few minutes gives a battery charged, battery charging message i switched off, that did work.

 

My mouse however will not retain DPI and pointerspeed/calibration settings and seems now to amp up in DPI and pointerspeed at random + at restarts. High or low, its also very annoying. Im now trying to see if i can fix that problem. However it does establish the fact there is some weird communication disruption issue between iCUE and USB devices introduced but im still lost from what angle. Note i am not loading AI Suite 3 but i am loading Precision X16 (dont want to fry this notoriously hot vidcard)

Link to comment
Share on other sites

took out one of the two Strafe RGB usb cables (the usb hub one i gather for that single port in the back)

and put the mouse in that port, it failed in the others, and after the required restart for drivers to work albeit slowly the iCUE started and remembred the mouse dpm and allows for changing aswell.. now lets see if my headset shuts down xd

Link to comment
Share on other sites

my fans are acting up now sometimes crashing back to blue

 

021-06-07T20:42:42 I cue.autoshutdown: Subject working state changed: AudioStreamProxyFilter::StreamState::Active

2021-06-07T20:42:42 I cue.autoshutdown: Autoshutdown state: 1 Ignore: false

2021-06-07T20:42:49 W cue.clinkclient.requesthandler: CLink request failed: 5 "Request timeout"

2021-06-07T20:43:01 W libpng warning: iCCP: known incorrect sRGB profile

2021-06-07T20:43:25 W cue.sensors.system_info: Values request failed: 5 "Request timeout"

2021-06-07T20:43:25 W cue.sensors.system_info: Values request failed: 5 "Request timeout"

2021-06-07T20:43:25 W cue.devices.enum.clink: "Failed to get device list. code=5. Request timeout"

2021-06-07T20:43:25 W cue.clinkclient.requesthandler: CLink request failed: 5 "Request timeout"

2021-06-07T20:45:09 W cue.sensors.system_info: Values request failed: 5 "Request timeout"

2021-06-07T20:45:09 W cue.clinkclient.requesthandler: CLink request failed: 5 "Request timeout"

2021-06-07T20:45:09 W cue.devices.enum.clink: "Failed to get device list. code=5. Request timeout"

2021-06-07T20:45:10 W cue.sensors.system_info: Values request failed: 5 "Request timeout"

2021-06-07T20:45:10 W cue.devices.enum.clink: "Failed to get device list. code=5. Request timeout"

2021-06-07T20:45:10 W cue.clinkclient.requesthandler: CLink request failed: 5 "Request timeout"

2021-06-07T20:45:11 W cue.sensors.system_info: Values request failed: 5 "Request timeout"

2021-06-07T20:45:11 W cue.devices.enum.clink: "Failed to get device list. code=5. Request timeout"

2021-06-07T20:45:11 W cue.clinkclient.requesthandler: CLink request failed: 5 "Request timeout"

2021-06-07T20:45:13 W cue.sensors.system_info: Values request failed: 5 "Request timeout"

2021-06-07T20:45:13 W cue.devices.enum.clink: "Failed to get device list. code=5. Request timeout"

2021-06-07T20:45:13 W cue.clinkclient.requesthandler: CLink request failed: 5 "Request timeout"

2021-06-07T20:45:14 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:14 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:26 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:27 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:29 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:29 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:30 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:30 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:30 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:31 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:32 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:33 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:34 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:34 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:34 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:35 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:36 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:36 W cue.clinkclient.requesthandler: CLink request failed: 5 "Request timeout"

2021-06-07T20:45:36 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:36 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:37 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:37 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:37 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:38 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:38 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:39 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:39 W cue.clinkclient.requesthandler: CLink request failed: 5 "Request timeout"

2021-06-07T20:45:39 W cue.clinkclient.requesthandler: CLink request failed: 5 "Request timeout"

2021-06-07T20:45:39 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:39 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:40 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:40 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:40 W cue.clinkclient.requesthandler: CLink request failed: 5 "Request timeout"

2021-06-07T20:45:40 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:40 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:40 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:41 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:41 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:41 W qrc:/qml/collection/ColorPicker.qml:42: TypeError: Cannot call method 'updateCurrentColor' of null

2021-06-07T20:45:41 W qrc:/qml/collection/ColorPicker.qml:48: TypeError: Cannot call method 'updateCurrentColor' of null

2021-06-07T20:45:41 W qrc:/qml/ui/settings/DeviceSettings.qml:40:11: QML ColumnLayout: Binding loop detected for property "contentHeight"

2021-06-07T20:45:42 W qrc:/qml/delegate/TabViewTabDelegate.qml:21: TypeError: Cannot read property 'top' of null

2021-06-07T20:45:42 W cue.devices.enum.clink: "Failed to get device list. code=5. Request timeout"

2021-06-07T20:45:42 W cue.clinkclient.requesthandler: CLink request failed: 5 "Request timeout"

2021-06-07T20:45:43 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:43 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:43 W cue.devices.enum.clink: "Failed to get device list. code=5. Request timeout"

2021-06-07T20:45:43 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:44 W cue.devices.enum.clink: "Failed to get device list. code=5. Request timeout"

2021-06-07T20:45:45 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:45 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:45 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:45 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:45 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:45 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:45 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:45 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:45 W cue.devices.enum.clink: "Failed to get device list. code=5. Request timeout"

2021-06-07T20:45:45 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:45 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:45 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:46 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:46 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:46 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:46 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:46 I cue.clinkclient: Error connecting to service: 2

2021-06-07T20:45:46 I cue.clinkclient: Error connecting to service: 2

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...