WebMaximus

Haven't had the issue in a long time now but IIRC, changing the degrees of tilt required to trigger the assigned command fixed it.

Found it, many thanks for pointing me in the right direction! I should of course have checked there myself before wasting space in here, sorry 🥴

The device is seen in the screenshot, it's the H150i Elite LCD and I was planning to log the coolant temp but I don't get any dialogue box when enabling the option to choose name nor location of the log file.

Where can I find the log file when enabling this option? Would have been nice with a pop-up when hovering with the mouse cursor over the option.

Today when I started my PC, I suddenly have a very odd problem with my Corsair M65 RGB ULTRA Wireless mouse. As soon as I start moving the mouse, the command I've assigned to right tilt (CTRL-N in my case) is triggered where the result is CTRL-N key presses like a machine gun. Meaning I get a multitude of new tabs if I have Google Chrome open/in focus or if I'm on my desktop, I instead get an equal amount of Windows Explorer windows popping up. Yesterday when I was using my computer, all was working perfectly normal. When I couldn't make this odd behavior stop in any other way, I unassigned the keyboard command from the right tilt gesture and the problem went away. That however isn't a solution because I do like to have this command assigned. I've made sure I'm on the latest version both for firmware and software but to no avail. I've also tried restoring a Windows system image from a few days back when everything was working but still same problem. Which makes me think I all of a sudden have a hardware issue with the mouse. Anyone else experienced the same issue?

Ah, I see.

I'm trying to understand why some have this issue where the keyboard freezes where others such as myself (fingers crossed) haven't had any such issues up to this point. Just thinking out aloud here, if the problem many of you are seeing was with the firmware itself, wouldn't everyone see the same problem when using this same/latest version of the firmware? Right now when checking, my iCUE version is reported as 5.1.1113 and the firmware for my K100 RGB Air Wireless 5.1.1109.

Maybe Jay could bring this topic up, he seems to be doing lots of videos on similar topics lately such as this one https://youtu.be/XA4QH7SO8J4

I've been in this business for a very long time now and have had numerous Corsair products over the years. All in all, I like their products and in my eyes, it's the kind of brand I expect quality products from with lots of innovation and smart tech. What I'm not equally impressed by is their customer service and support. I just don't get it, why are they so unresponsive and how can they carry on with the business with this lacking customer support for such a long time. I just don't get it. With that said, I suppose I'm one of those who make it possible by continue investing my money into their products even when I know I shouldn't expect to get any help if I run into issues. Luckily, I so far haven't suffered from this freezing issue with the K100 Air people are discussing here. Not sure if that is because I very recently bought the keyboard and was lucky enough to have it come with a more recent firmware version. Where the issue has already been addressed. Or maybe because I'm only using it with the wired connection? If the issue is related to what connection method you're using. I submitted a support ticket where I was asking why it reports the firmware version check fails when I just got the keyboard. This was probably like a week ago. Where the automatic response I got back said I should expect an answer within the next 48 hours IIRC. Still haven't heard a thing. Not urgent in my case since I luckily don't have any issues. Still, when buying a product in this price range in particular as others already pointed out, it should be nothing but a smooth experience all the way with zero issues. Truly sad how a company with so many good products lack so bad when it comes to what is usually the most important thing for any business, taking good care of their customers. I'm working with Customer Success for another big US company professionally and let me assure you, if we would treat our customers in this way, wow...just the thought of it make me shiver what the result would be. Just ignoring those who pay your salaries. Since I've sadly seen this for so many years now, I don't expect anything to change anytime soon I'm sorry to say. Still felt like "ventilating" my thoughts a bit. Have a good weekend every one in here and for those facing issues with the keyboard, I hope you'll get it fixed one way or the other and sooner rather than later. Or if not, simply return the product and clearly state the reason for it, how you get zero support from the manufacturer. Maybe that is the only thing that will bite in the end.

I just got a K100 and iCUE reports the firmware version is 5.9.68 and when pressing the check for updates button, I'm told Update Failed in red letters. Any idea what could be causing this? I found another thread where it was suggested this could be an issue where the keyboard needs to be replaced. Anyone else in here having the same issue and/or any more information?

I was happy to see how iCUE didn't crash a single time in a very long time...until I updated to version 4.30.162 and back are the crashes...sigh...

Will it also support 3rd party 4090:s such as the MSI Suprim X or just the FE model of the 4090? Also, where in Europe can I get this new cable? Preferably in Sweden.

So does this mean Corsair don't have any plans to release an ATX 3.0 PSU?

Anyone from Corsair who would care to comment?

Yep, same thing here, iCUE keeps crashing left and right. I had my hopes up with the new version which was newly released but nope...here's my latest crash. This time said to be caused by ntdll.dll...seems to be different dlls every time Log Name: Application Source: Application Error Date: 2022-10-06 09:04:33 Event ID: 1000 Task Category: Application Crashing Events Level: Error Keywords: User: THENEST\Richard Computer: TheNest Description: Faulting application name: iCUE.exe, version: 4.28.177.0, time stamp: 0x632822de Faulting module name: ntdll.dll, version: 10.0.22621.608, time stamp: 0xf2e8a5ab Exception code: 0xc0000374 Fault offset: 0x000000000010c1c9 Faulting process id: 0x0x2254 Faulting application start time: 0x0x1D8D95076E97214 Faulting application path: C:\Program Files\Corsair\CORSAIR iCUE 4 Software\iCUE.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: 5facb188-b84f-4197-b432-dfae609120b7 Faulting package full name: Faulting package-relative application ID: Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" Guid="{a0e9b465-b939-57d7-b27d-95d8e925ff57}" /> <EventID>1000</EventID> <Version>0</Version> <Level>2</Level> <Task>100</Task> <Opcode>0</Opcode> <Keywords>0x8000000000000000</Keywords> <TimeCreated SystemTime="2022-10-06T07:04:33.7732823Z" /> <EventRecordID>1734</EventRecordID> <Correlation /> <Execution ProcessID="14280" ThreadID="9008" /> <Channel>Application</Channel> <Computer>TheNest</Computer> <Security UserID="S-1-5-21-133767816-178543-123633953-1001" /> </System> <EventData> <Data Name="AppName">iCUE.exe</Data> <Data Name="AppVersion">4.28.177.0</Data> <Data Name="AppTimeStamp">632822de</Data> <Data Name="ModuleName">ntdll.dll</Data> <Data Name="ModuleVersion">10.0.22621.608</Data> <Data Name="ModuleTimeStamp">f2e8a5ab</Data> <Data Name="ExceptionCode">c0000374</Data> <Data Name="FaultingOffset">000000000010c1c9</Data> <Data Name="ProcessId">0x2254</Data> <Data Name="ProcessCreationTime">0x1d8d95076e97214</Data> <Data Name="AppPath">C:\Program Files\Corsair\CORSAIR iCUE 4 Software\iCUE.exe</Data> <Data Name="ModulePath">C:\WINDOWS\SYSTEM32\ntdll.dll</Data> <Data Name="IntegratorReportId">5facb188-b84f-4197-b432-dfae609120b7</Data> <Data Name="PackageFullName"> </Data> <Data Name="PackageRelativeAppId"> </Data> </EventData> </Event>

Seen this a couple of times now. Here's from the WEV app log: Log Name: Application Source: Application Error Date: 2022-09-27 17:57:18 Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: TheNest Description: Faulting application name: iCUE.exe, version: 4.28.174.0, time stamp: 0x63076e07 Faulting module name: DeviceCommands.dll, version: 0.0.0.0, time stamp: 0x630763b4 Exception code: 0xc0000005 Fault offset: 0x000000000000b4ca Faulting process id: 0x543c Faulting application start time: 0x01d8d257ec44d092 Faulting application path: C:\Program Files\Corsair\CORSAIR iCUE 4 Software\iCUE.exe Faulting module path: C:\Program Files\Corsair\CORSAIR iCUE 4 Software\DeviceCommands.dll Report Id: 6afb105c-4404-4e29-8c6f-1acc908e4d57 Faulting package full name: Faulting package-relative application ID: Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Version>0</Version> <Level>2</Level> <Task>100</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2022-09-27T15:57:18.9413625Z" /> <EventRecordID>4617</EventRecordID> <Correlation /> <Execution ProcessID="24724" ThreadID="0" /> <Channel>Application</Channel> <Computer>TheNest</Computer> <Security /> </System> <EventData> <Data>iCUE.exe</Data> <Data>4.28.174.0</Data> <Data>63076e07</Data> <Data>DeviceCommands.dll</Data> <Data>0.0.0.0</Data> <Data>630763b4</Data> <Data>c0000005</Data> <Data>000000000000b4ca</Data> <Data>543c</Data> <Data>01d8d257ec44d092</Data> <Data>C:\Program Files\Corsair\CORSAIR iCUE 4 Software\iCUE.exe</Data> <Data>C:\Program Files\Corsair\CORSAIR iCUE 4 Software\DeviceCommands.dll</Data> <Data>6afb105c-4404-4e29-8c6f-1acc908e4d57</Data> <Data> </Data> <Data> </Data> </EventData> </Event>

@LeDoyen What would you say about the orientation of the radiator when mounted in the front? I've heard people say you should always make sure the hoses are in the bottom. To avoid air reaching the pump. Where others say it doesn't matter. Given you're using an AIO product where the pump is in the CPU water block. The problem having the hoses in the bottom of course can be they may not be long enough to reach the CPU.

Wow, what an excellent post and thanks for opening my eyes. What you say makes so much sense when I read it, can't believe how I didn't realize this myself before. So, BIG thanks for your input. Meaning I can check one thing off my list! Now I just need to figure out what motherboard I'll go with 😂

Hey guys, need your input and advice. I have a Corsair Obsidian 500D SE case where I'm currently using a Corsair H115i RGB Platinum AIO mounted in the top of the case as an exhaust. In the front, I have 3x120 fans as intake and in the back of the case, I have another 120mm fan as exhaust. My CPU is an 8086K and my GPU is the MSI GeForce RTX 3090 SUPRIM X. Now I'm thinking of replacing my 8086K with the 12900KS. I spend most of my time in MSFS in VR and have found my CPU to be limiting me. I understand the 12900K series of CPU:s and the KS model in particular I guess will get very hot. Why it's important to have good cooling in place. Since I won't be able to use my current AIO with the new socket and CPU, I bought these two and now I'm trying to figure out which one to use and which one to return. https://www.webhallen.com/se/product...150i-Elite-LCD https://www.webhallen.com/se/product...GB-Elite-280mm If you compare the 280 vs the 360 side by side, I assume the 360 will provide better cooling performance. Simply due to it's larger size and for moving more air. However, since I already have a 280 mounted in my case, it would be easier to switch to a new 280 rather than a 360. Also, since I guess I would need to mount the 360 in the front rather than in the top of the case and with hot air moving upwards, maybe the advantage a 360 has over a 280 wouldn't be that huge based on the different location in the case. Maybe it would even perform worse... I've tried to find out if it's possible to mount the 360 in the top but most people seem to say 'Not possible'. While a few claimed they managed to do this. So I'm not really sure. Obviously, the best thing is to give it a try but before I start unboxing stuff over here, I figured I would ask in here. Many thanks in advance for your help input guys!

Good to hear but not of much use to me unfortunately with a H115 in my rig...

So you already tried the version I suggest in was it post 9 I think?

That's great advice, thanks! Was able to figure it out and happily learned the temperatures seen in iCUE and HWiNFO64 matched perfectly. Here's the answer to my own initial question for anyone else who might want to know. Temp #1 in iCUE is MOS in HWiNFO64 Temp #2 in iCUE is System in HWiNFO64 Temp #3 in iCUE is CPU Socket in HWiNFO64 Temp #4 in iCUE is CPU Core in HWiNFO64

I have an MSI Z390 MEG ACE motherboard. Looking in HWiNFO64, I have 4 sensors as seen below Looking in iCUE and scrolling through the list of available sensors, I find 4 sensors all starting with the name 'Microstar International Co., Ltd. MEG Z390 ACE (MS-7B12) and then Temp #1, Temp #2, Temp #3 and Temp #4 as seen below I assume these are the same 4 sensors I see in HWiNFO64. Question is which one corresponds to which. What I would like is to tie the speed of my case fans to the sensor called 'System' in HWiNFO64. Thinking this is the sensor telling what the temperature inside the case is. Anyone knows how to find out?

A follow-up on this one since I wasn't able to find any already created rules for iCUE I could modify, did you create your new own rule for iCUE? For now, I did the same thing pretty much by blocking iCUE in Killer Control Center.

That's great to hear!