Parksie
-
Posts
37 -
Joined
Content Type
Forums
Gallery
Release Notes
Corsair Blog
Store
Profiles
Posts posted by Parksie
-
-
1 minute ago, c-attack said:
Can you be more specific about which sensor value? The "coolant temp" on an AIO? CPU temp or GPU temp?
Sorry, should have said this is the amd cpu package temp and/or the motherboard cpu temp and I am setting custom fan curves using either of them but both are just as slow to update in iCue
-
Hi all,
Just wondering if anyone can help with this one… I use iCue to control my fans (QL120’s) but have recently noticed that the temp sensors in the cooling section are really slow to update causing the fans to have a delay in the speed ramping up. Is there anything I can do to help speed the temp sensor updates in iCue up?
Thanks in advance
-
22 hours ago, Khrystyna said:
Hi, can you please help me? You've noted that you have H170i Elite LCD cooler and 7000D case. Do they both fit each other? Because in the web site it's stated that 7000D case has enough room (for upper mounting) up to 420 radiator, but H170i is all 457 mm. Does this cooler fit in the upper lid? or it can be mounted only to the rare panel?
Will appreciate your answer.
Best regards.
420 isn’t the actual size of the radiator (457mm), 420 refers to the fans that are fitted (3x140mm) and the spacing of the mounting screws. Another example would be a 360 radiator which means it has 3x120mm fans.
-
1 hour ago, seikojin said:
It is literally a supported troubleshooting step. So it is a thing.
Item 2 from the initial post:
Strange how mine’s worked absolutely fine with full control of the screen etc for 5 months and through numerous iCue updates using the splitter, whereas I had the red triangle when it was plugged into separate USB ports 🤔
-
1
-
-
1 hour ago, Power2108 said:
and how do i do if i only have a usb port on my motherboard ?
That part isn’t correct, mine didn’t work (red triangle) when it was plugged into two separate usb headers on the motherboard but worked when I used the splitter so that makes absolutely no difference.
-
30 minutes ago, Fractureguy said:
well in my case they didnt and it explained in the RMA process that i would have to pay to return it so i did.
They did for me with the fans that I’ve had to return
-
1
-
-
3 hours ago, Fractureguy said:
unfortunately all they want us to do is create an RMA and send back the "defective part". Even though we've already paid to have it shipped to us now we have to pay to send it back. Something similar happened to me i sent my cooler in and the sent me a refurbished one. Fixed the triangle but did not fix my current issue of no screen control.
You do know they normally send you a shipping label for returns right? 🤔😂
-
9 hours ago, seikojin said:
It isn't there for me and I am on 4.26. The release notes for 4.25 doesn't identify the fix for people trying to get the lcd to show pictures, so it isn't there for everyone.
Where did I or the other person mention not showing pictures? Read what I responded to, it was about rotating images and nothing to do with it fixing not showing pictures
-
4 hours ago, Synomenon said:
It's July and we're on v4.26.110. I just installed the Elite LCD Upgrade Kit on my H100i Elite Capellix. I do not see this option in the software.
Had I known that this Corsir hardware didn't have this basic capability, I would have purchased a NZXT Kraken Z53 instead. I'm a few days outside the return period for the H100i so I'm now stuck with it.
It’s in there, just maybe not the full version that was expected (but never promised). You can rotate images and gifs only.
-
1
-
-
4 hours ago, vagm3 said:
I have the h150 elite lcd with ryzen 5900x and only load and package sensors in dashboard but not cpu temp
anyone with same issue??
That’s all that has ever shown on mine for the 5900x, it’s not an issue, it’s just how it is. Most of the temp readings are shown under the motherboards sensors (ASUSTeK COMPUTER INC. ROG CROSSHAIR VIII DARK HERO)
-
3 hours ago, c-attack said:
I believe you are limited to 5 x 450mm strips. CUE is programmed to allow varying combinations based on length, but I can't get it past 5 x 450mm. So based on that, your idea of using 3x450 on Ch1 and 3x450 on Ch2 should work for lighting link effects as channels 1 and 2 fire sequentially. Visor, color wave, and Type Lighting Link.
For normal effects, it will run as 1-3 and a separate instance for 4-6 in each channel, typical of standard separate lighting groups.
Thanks for the reply. Looks like I’ll be spending some more on the Corsair money pit 🤣
-
I’d like to know if the ls100 controller will run six 450mm strips and work in sequence using lighting link? Can I put all six in a single port or, if I have to put three in port 1 and three in port 2, will they work in sequence eg 1-2-3-4-5-6 or at the same time eg 11-22-33? (I hope my explanation comes through how it’s meant to 🙈)
-
7 hours ago, rGxOfficial said:
Hello everyone,
Today I noticed a problem when I was playing valorant, my lights from my corsair vengeance hung up after a while. when I looked in the corsair app iCUE I saw that I had a question mark on my RAM so I restarted my system, there I got a message from the BIOS that said "Boot failure detected"
At first I thought ok maybe my RAM is damaged. I took my RAM out of my PC. and checked everything. I ran an error analysis of my RAM without any sign of a problem. I also found that when I turned on the XMP profile I had the same problem again that after I played Valorant I got a "Boot failure detected" again.
After that I checked everything again, played other games and did some things on the computer, this problem didn't occur anymore. Now that the problem no longer existed, I was starting Valorant again and it happened again. My RAM hung up in the RGB and was no longer recognized by the ICUE software but I was looking on my PC all my 4 ram sticks were displayed in the system.
I also used the Command on CMD "wmic memorychip get speed" I was also able to see all my speeds from my 4 ram sticks, which refutes my ram failure.
As soon as my RAM was no longer visible in the iCUE software, I restarted my PC. then again "Boot failure detected"
This problem must be with Vanguard, otherwise I can't imagine the problem. because it doesn't happen with other games or other things I do on the computer. and my ram is also running properly, I did error analyzes and checked my RAM, it runs without any problems.
After some time in Valorant, the lighting on my RAM sticks hangs up. then I look into the iCUE software and see that my RAM is no longer recognized. As soon as I restart my PC afterwards, I get an error message from the BIOS "Boot Failure Detected" which leads me to fully reset my BIOS to default thats really annyoing.
Maybe it's because vanguard intervenes a lot in the system and also blocks some things.because in all other games except valorant this doesn't happen and my ram is running fine.
My system properties:
System → Windows 10 64Bit
Case → Thermaltake View 91 TG
Mainboard → Gigabyte Z390 Aorus Xtreme Waterforce, Intel Z390
CPU → Intel Core i9-9900K (Without OC)
CPU Cooler → Gigabyte Z390 Aorus Xtreme Waterforce Monoblock
Graphic Card → Gigabyte GeForce RTX™ 2080 Ti Aorus Xtreme 11G
RAM → Corsair Vengeance RGB, DDR4-3200 Quad-Kit (OC XMP 3200 without 2133)
Power Supply → be quiet! Straight Power 11, Platinum, modular - 1000 Watt
Software I am using:
iCUE on the newest Version v.4.24.19
Try turning off game integrations for the ram in iCue
-
It was the keyboard, I’ve had a replacement from Amazon which is absolutely fine.
-
Just spotted this in the log files and it corresponds with the time that it disconnected:-
2022-06-14 00:22:51.599 C cue.devices.bragi.physical_hid: Main subdevice disconnected! "K100 RGB"
2022-06-14 00:22:51.599 W cue.devices.enum.subdevice: Fail counter for "K100 RGB" reached zero, removing subdevice
2022-06-14 00:22:51.599 C cue.devices.bragi.physical_hid: Main subdevice disconnected! "K100 RGB"
2022-06-14 00:22:51.599 C cue.devices: Write hunk failed. Device: "K100 RGB"
2022-06-14 00:22:51.599 C cue.devices: Exception: Timeout (5807ms) while receiving reply.2022-06-14 00:22:51.599 C cue.devices: Exception while runCommand on device K100 RGB :
Timeout (5807ms) while receiving reply.2022-06-14 00:22:51.599 I cue.devices.bragi.command_queue: Command not send. Subdevice disabled. bragiprotocol::CommandId::WriteBufferBegin
2022-06-14 00:22:51.599 W cue.devices.enum.subdevice: Fail counter for "K100 RGB" reached zero, removing subdevice
2022-06-14 00:22:51.599 C cue.devices.bragi.physical_hid: Main subdevice disconnected! "K100 RGB"
2022-06-14 00:22:51.599 C cue.devices: Write hunk failed. Device: "K100 RGB"
2022-06-14 00:22:51.599 C cue.devices: Exception: IO operation was cancelled.2022-06-14 00:22:51.600 C cue.devices: Exception while runCommand on device K100 RGB :
IO operation was cancelled.2022-06-14 00:22:51.600 I cue.devices.bragi.command_queue: Command not send. Subdevice disabled. bragiprotocol::CommandId::WriteBufferBegin
2022-06-14 00:22:51.600 W qrc:/qml-imports/com/corsair/cue/controls/MouseoverPopup.qml:138: TypeError: Cannot read property 'currentPresetName' of null
2022-06-14 00:22:51.600 W qrc:/qml-imports/com/corsair/cue/controls/MouseoverPopup.qml:77: TypeError: Cannot read property 'toolTipText' of null
2022-06-14 00:22:51.600 W cue.devices.enum.subdevice: Fail counter for "K100 RGB" reached zero, removing subdevice
2022-06-14 00:22:51.600 W qrc:/qml-imports/com/corsair/cue/controls/MouseoverPopup.qml:68: TypeError: Cannot read property 'title' of null
2022-06-14 00:22:51.600 C cue.devices.bragi.physical_hid: Main subdevice disconnected! "K100 RGB"
2022-06-14 00:22:51.600 W qrc:/qml-imports/com/corsair/cue/controls/MouseoverPopup.qml:60: TypeError: Cannot read property 'iconSource' of null
2022-06-14 00:22:51.600 C cue.devices: Write hunk failed. Device: "K100 RGB"
2022-06-14 00:22:51.600 C cue.devices: Exception: IO operation was cancelled.2022-06-14 00:22:51.600 C cue.devices: Exception while runCommand on device K100 RGB :
IO operation was cancelled.2022-06-14 00:22:51.641 I cue.lightings.direct_player: Stopped lighting worker in 0x1f8c
2022-06-14 00:22:51.701 W cue.devices.enum.subdevice: Get property UsbVid failed.
Timeout (100ms) while sending command.2022-06-14 00:22:51.701 C cue.devices.abstact_protocol: stopWorker wasn't called correctly for "K100 RGB"
2022-06-14 00:22:51.701 C cue.devices: Cannot create subdevice for: "K100 RGB"
2022-06-14 00:22:51.701 C cue.devices: Failed to get vid, pid from subdevice id: 02022-06-14 00:22:51.701 W QObject::connect(AbstractProtocol, bragi::LogicalSubdevice): invalid nullptr parameter
2022-06-14 00:22:51.712 C cue.devices: Trying to remove main subdevice for "K100 RGB"
2022-06-14 00:22:56.697 C cue.devices.abstact_protocol: stopWorker wasn't called correctly for "K100 RGB" -
Ok, I’ve now tried a clean install of Win11 and 10 which still hasn’t helped. I thought it might be armoury crate but installed iCue first so armoury crate wasn’t even there and it still did the same.
-
Having a problem with my new k100 keyboard disappearing randomly from iCue. Sometimes goes straight away and others it’ll stay for hours. If I then unplug it and plug it back in it’ll show for a split second then disappear again. I’ve gone through the usb devices and ports etc in device manager and made sure they aren’t allowed to sleep and gone into power to disable the usb sleep options in there, no joy. I’ve done a clean install of the latest iCue, this doesn’t help. I’ve tried it in all the USB ports on the rear and front of my case (all a mix of 3.2 gen 1 and 2) to no avail. I’ve even tried switching legacy on and off for the the USB ports in the bios, nothing is working. Come on Corsair get it together, I’ve spent a small fortune on your products and the least I expect is for them to work together?!?
-
On 5/12/2022 at 10:22 AM, Disane said:
Just fiy:
Apparently a reset of the K100 (pluggin it off, pressing and holding ESC while plugin it back and holding ESC for 5 seconds) seem to solve this issue. I dont't what's the cause of this. But now it works again flawlessly on both machines even with the usb switch.Is it still working ok? I’ve bought a k100 today and have an issue where my k100 keeps disappearing at random from iCue (sometimes after a second and sometimes hours), when it does this the keyboard RGB reverts back to the hardware one rather than the one in iCue.
-
Did you ever solve this? I’ve just bought one and having the same issue. Only had it today and tempted to just return and get the k70 RGB pro instead.
-
I’ve been having a play about with my system today, trying different versions of iCue and GOG in both Win10 and 11 but couldn’t get it to stop randomly crashing anywhere between 1-30mins. Went into the BIOS and disabled c-state and (touch wood) it’s not crashed for the last 3hrs whilst downloading games from GOG. Might be worth a try for others.
AMD 5900x
ASUS X570 Dark Hero
Nvidia 3090FE
Corsair Vengeance Pro 3600 32gb
-
On 1/8/2022 at 3:54 PM, Gabbatek said:
YOU ARE A SAINT! ABSOLUTE LEGEND
I have been battling this issue for almost a year now and you've just saved my stressed out mind from incinerating all my corsair kit.
seriously, thank you so much
No problem, glad I could help
-
Another with the same issue here! Does anyone know how to roll back firmware updates for the H150i Capellix? I updated the firmware to version 2.6.201 as well as iCue to 4.19 and since doing so my otherwise stable system keeps crashing and restarting when trying to play certain games or weirdly when downloading games using GOG galaxy (all worked fine before). I have tried going back to the version of iCue that I was using before (4.12) but am still having the issue which leads me to believe it’s the H150i firmware update that’s causing me trouble.
-
-
My x570 tuf pro is suppose to have icue integration. The only thing it can control are the 6 led onboard that I nearly don't see and the rgb led strip header (not argb, the rgb which are 1 color only). So this is useless for me, I cannot co trol my fans and watercooler that are connected to the argb headers.
I currently have only icue installed, no lighting service or armory crate service. And I just had the triangle problem before I posted. It's been on and off. And that's when it just not decide to forget all my configuration or my ram placement.
Unified is the way to go, and open is the best way to go for everyone. Close sourcing like it's doing right now and with each there own implementation is the worst. It's just argb, we've been controlling these on a lot of other device for decade and all using unified protocole.
Have you had Aura, Armoury Crate or lighting service installed because they are a real PITA to get rid of once you have, believe it or not ASUS themselves recommend a fresh install of windows if you want to get rid of it fully?!? Is the Tuff fully supported by iCue? I can select 4 different IO LED’s, 2 PCH and 2 RGB headers in iCue with my board. Like I say I’m over a month the only way I can get the red triangle error back is by changing the name of those two folders back to their original names, apart from opening armoury crate when I had iCue running which locked up the iCue plug-ins I’ve had no other issues at all.
.png.8752a3be73be92b53bad2dc995406cc1.png)
iCUE 5.8.130 dashboard bugs - one apparently caused by storage widget enablement.
in CORSAIR iCUE
Posted
I have also noticed an issue when I enable the storage widget that could be linked, with it enabled the windows anti-malware service in taskbar constantly bounces between 1-6% cpu usage (normally sits at 0% with the odd lift to 0.5% here and there) and raises cpu idle temps by about 10 degrees C. I’ve also ran cinebench with and without this enabled and lose around 1000 points when it’s enabled.