Jump to content
Corsair Community


  • Posts

  • Joined

Everything posted by Kurakkon

  1. Hi all, Hopefully someone can help. Brand new build and Windows 10 install. Rather randomly, sometimes during startup, sometimes during gaming, iCue.exe will bomb out. Faulting application name: iCUE.exe, version:, time stamp: 0x5fbbd88e Faulting module name: ntdll.dll, version: 10.0.19041.662, time stamp: 0x5f641e44 Exception code: 0xc0000374 Fault offset: 0x000e6ac3 Faulting process ID: 0x754 Faulting application start time: 0x01d6d25552ca1f51 Faulting application path: C:\Program Files (x86)\Corsair\CORSAIR iCUE Software\iCUE.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report ID: 5357a42a-568d-4552-893d-0f72d38a4cd8 Faulting package full name: Faulting package-relative application ID: Any ideas?
  2. Has anyone come across this problem? The battery area for the headphones displays 'Malfunction' in red and the system tray for iCue shows a red exclamation mark, after the headphones have been in use for a while. When its not showing this, such as after charging them for a while and/or rebooting, the battery level shows a white % level for the battery. After a while it then shows the same malfunction error message. I get the impression its something to do with the battery. I've uninstalled and reinstalled the latest iCue 3.14.104, without success. Anyone else had this and successfully fixed it? Please don't tell me it's yet another fault on the hardware, I've had so many problems with this already :(
  3. Its definitely the software, IMO. I had an older version of the app and didn't have this audio problem until I reinstalled windows 10 and had no choice but to download this latest version.
  4. Absolutely its software based. In my case, my older PC that had CUE on it had an older version of CUE. I know this because when I tried to run the updater via CUE it threw an error and didnt update. On that older PC, the VOID was working without any problems. On my new PC, built 4 weeks or so ago, the issue was immediately apparent. Tested via multiple USB ports. The only difference is the version of CUE I use. I don't know what the older version was, as the old PC no longer exists, but any version of CUE that I download right now exhibits this issue. It is definitely a CUE issue, as when CUE isn't installed, the problem doesn't exist though the VOID only then works in stereo not 7.1. So objectively this is a CUE software-caused problem.
  5. Probably the reason why this thread is so silent, if that's the case. No actual fix exists.
  6. Can we please get an update on this issue? The boards here seem rife with other people experiencing static/crackling problems with the audio.
  7. Who knows. I find it incredible that a premium product like this has such a fundamental issue with sound being seemingly completely ignored. I'm borderline ready to drop Corsair headsets completely and look elsewhere.
  8. No, you can't. The dongles for the VOID are locked to the headset they're paired with. When I had an issue with my VOID, I had to return both the dongle and the headset to Corsair and they replaced both.
  9. You alter the volume levels in whatever app you're using for comms. For example, if you're using Discord, raise the volume level there and then lower it in the game you're playing to make sure they're not being drowned out. Of course, you also have volume controls in Windows itself to do that, and on the headset (under the left ear cup).
  10. Not sure what you mean, I grabbed this version from their site. It didn't say its a pre-release version. Am I running some Beta version or something? Chipset all updated, as is the BIOS. Brand new build, literally put together last week. I haven't messed around with the USB controllers because I use them all for VR. I have, however, used the dongle in a USB 2 and USB 3 controller, two for the USB 3 in fact, and its exactly the same. I'm going to have another look at their downloads, because I wasn't aware I wasn't on a general release version.
  11. I've been having issues with CUE and my VOID RGB headset where, when CUE is installed, it results in excessive static/scratching. I think its because CUE sets the sample rate too low (which then can't be changed) but the thread where I've posted seems dead. So, in the meantime, I've been installing CUE again to have more of a look around and troubleshoot. Problem is, it's causing Windows 10 to go crazy. Occasionally, when I open CUE and then close it, Windows goes very, very laggy in response to commands. Left click on the Windows 10 Home button takes minutes to resolve. Right click is instant yet resultant left click selections are not. It has all the hallmarks of somehow being related to my mouse buttons, which is a Corsair M65 RGB managed by CUE. The only way to resolve this is to restart Windows. Closing CUE down doesn't appear to resolve anything though getting Task Manager up to check its actually gone seems impossible. Has anyone else had this sort of experience? At first I thought I had a faulty M.2 (as my OS drive) but various scans and checks all come back fine. I then suspected my RAM could be faulty but again have gone through several checks, in and out of the OS, all of which threw back zero errors. I did note one post that said CUE wasn't working well with higher clocked RAM and certain BIOS revisions but I'm running mine at the stock 2600 speed. Its not overclocked. Any thoughts?
  12. Getting this too. What I've noticed is that in the Sound > VOID > Properties > Advanced > Default Format sample rate is set to just one selection that can't be changed and it looks to be quite low in terms of quality. Not even DVD level (though I can't see for sure what it is ATM as I don't have the Corsair app installed any more). However, after I uninstalled the Corsair utility app and then reviewed the same I can choose, for example, 2 channel, 16 bit, 48000hz (DVD Quality) out of several selections and at that level, I don't get the crunchy, static effect when actions are performed in game. In my case, the game I've noticed it in is Fortnite, when farming trees and brick. There's a scratching, static noise that accompanies the end of an action. This doesn't happen when this setting it set to the above sample rate. I've double checked this with my main 5.1 speakers also, setting the sample rate down to that which appears to be locked when the Corsair app is installed and it produces the same static-y result. So, in summary, the Corsair app seems to be locking the VOID sample rate very low and it cannot be manually altered unless the Corsair app is uninstalled, at which point you're left with a 2 channel VOID. This causes the noise. As some background to my situation, I installed Windows 10 completely afresh after upgrading my PC hardware at which point this issue became immediately apparent. It was not apparent on my prior setup but I can't say what version of the Corsair app I was using. It will have have been an older version, as I recall it throwing an error when looking for updates. This in turn could mean that me grabbing the latest version of the Corsair app, thus newer code, is looking to be the root of the issue. Hope this helps, as running games in 2 channel stereo is not why I spent so much money on these.
  • Create New...