Hagbard Celine Posted February 14, 2019 Share Posted February 14, 2019 Running iCUE v3.12.118 on Windows 7 Ultimate with all updates. When I start a benchmark or anything that loads the system considerably, all sensor output exept for the AX860i disappears from iCUE Space after a short time. Stopping and restarting the iCUE tray application gets the readings back. Logs and system-info dump attached(This is not my main system as described in my user info, but a MSI N3050i ECO).LostSensors.zip Link to comment Share on other sites More sharing options...
c-attack Posted February 15, 2019 Share Posted February 15, 2019 Can you be specific what benchmark you;re running? Some of the multi-purpose tools like Aida are sure to cause sensor polling errors - benchmarking or not. Link to comment Share on other sites More sharing options...
Corsair Employee Corsair Calico Jack Posted February 15, 2019 Corsair Employee Share Posted February 15, 2019 That's not entirely odd. 3rd party sensor programs can conflict with ours. It's best just to use the sensors in your benchmarking software if this is occurring. Link to comment Share on other sites More sharing options...
Hagbard Celine Posted February 15, 2019 Author Share Posted February 15, 2019 (edited) Benchmarks was only an example, anything that loads the system considerably gets it to loose the sensors. What I did during the attached log was start the rendering test in GPU-Z plus pressing the Benchmark button in CPU-Z. Edit: On another note having problems running concurrently with other monitoring programs is a BUG in itself, especially since iCUE is a program that controls cooling. I've never experienced a sensor-monitoring-program on windows not behaving due to other sensor-monitoring-program running concurrently. And at times I've had up to at-least 6 running at the same time (open hardware monitor, hwinfo64, siv64, SpeedFan, sidebar diagnostics and GPU-Z, just of the top of my head), and this has never been an issue with any program. Edit2: Attached logs where the same thing happens with no other sensor-reading-programs running. Only started some dx11 samples to to load the system.LostSensorsWithOnlyDX11samples.zip Edited February 15, 2019 by Hagbard Celine Link to comment Share on other sites More sharing options...
Corsair Employee Corsair Calico Jack Posted February 15, 2019 Corsair Employee Share Posted February 15, 2019 Dragon Center causes temp sensors to misread and spins the fans harder and softer when running in conjunction with HWMonitor. iCUE use's CPUID's SDK. It functions basically the same. If there's a monitoring issue on our software, it exists as an issue within their software as well. Similar programs can sometimes conflict with eachother. If it only happens during benchmark, iCUE pulls a lot of data and uses GPU resources to display all those graphs. You might just be stressing your system harder than it can consistently grab data from all the USB devices plugged in. There's a few possibilities. Link to comment Share on other sites More sharing options...
Hagbard Celine Posted February 15, 2019 Author Share Posted February 15, 2019 Dragon Center causes temp sensors to misread and spins the fans harder and softer when running in conjunction with HWMonitor. OK, you got one example of another combination that experience a similar bug. That does not disprove the fact that it is a bug. iCUE use's CPUID's SDK. It functions basically the same. If there's a monitoring issue on our software, it exists as an issue within their software as well. Similar programs can sometimes conflict with eachother. If it only happens during benchmark, iCUE pulls a lot of data and uses GPU resources to display all those graphs. You might just be stressing your system harder than it can consistently grab data from all the USB devices plugged in. There's a few possibilities. USB is certainly not the issue, the sensors that disappear are motherboard temp and fan speeds, CPU temp and load, and the DRAM data(CAS, RAS and so on), and the temp of the PCIE Radeon card if I got that installed. The only sensor connected trough USB is the AX860i, which do not disappear ever. Else there is only a keyboard and two trackballs on USB-bus. Link to comment Share on other sites More sharing options...
TeaTimeJ Posted February 16, 2019 Share Posted February 16, 2019 The same happens to me, I usually lose all disks, motherboard, h100I and oddly sometimes Commander Pro and sometimes not in the dashboard. It happens while gaming. I put it down to HW monitor (with Corsair devices disabled) as it is running in the background too. Double check if you are not running any HW monitoring software at all just to make sure. Link to comment Share on other sites More sharing options...
Hagbard Celine Posted February 16, 2019 Author Share Posted February 16, 2019 This is a cleanly installed system. Only thing running in background is Intel HD Graphics Tray, MSI Live Update 6, Realtek HD Audio Manager, MSI Fast Boot, Logitech SetPoint and AMD Catalyst Control Center. Link to comment Share on other sites More sharing options...
Hagbard Celine Posted February 16, 2019 Author Share Posted February 16, 2019 (edited) iCUE use's CPUID's SDK. It functions basically the same. If there's a monitoring issue on our software, it exists as an issue within their software as well. Well, I just tested this claim, it does not hold up: Been running the following Nvidia DX11 demos (from NVIDIA_SDK11_Direct3D_11.00.0328.2105) in parallel with "Stress CPU" in CPU-Z and "CPUID Hardware monitor PRO"(Trial version) for more than 30 min: Island11, Compute Shader N-Body Simulation, OpacityMapping, FXAA, GregoryACC11, Hair, Multi-View Soft Shadows and DirectCompute Ocean. Result: Not one single glitch from "CPUID Hardware Monitor PRO"-sensor-readings. Log file attached. iCUE sensor readings broke down before 3 minutes passed on same type test in my second post(That was only DX11 samples, no CPU-Z even). Edit: Also, after this last test one thing seems clear to me: This is a bug in the Corsair front-end, not the logging back-end. Because I got the fan on the AX860i set to react to changes in CPU Core0 temperature, and that seems to happen even after the sensor output have disappeared in "iCUE SPACE". Also as mentioned in first post, the workaround is to restart the iCUE program, not the iCUE Service.HWmonPRO.zip Edited February 16, 2019 by Hagbard Celine Discovered that bug is in front-end program, not in logging back-end. Link to comment Share on other sites More sharing options...
Corsair Employee Corsair Calico Jack Posted February 22, 2019 Corsair Employee Share Posted February 22, 2019 Can we get an updated list of your system specs? Link to comment Share on other sites More sharing options...
Hagbard Celine Posted February 22, 2019 Author Share Posted February 22, 2019 (edited) Can we get an updated list of your system specs? The system in question is: Motherboard: MSI N3050I ECO CPU: Celeron N3050 GPU: Integrated Intel HD Brasswell GPU2: CLUB 3D Radeon R5 230 1GB PCIe*1x (CGAX-R5232LX1) (Does not belong in system, but sporadically mounted for testing stuff.) Ram: 2xG.Skill F3-1600C9-4GRSL HardDrive: CRUCIAL MX300 525GB SSD OpticalDrive: ASUS BW-16D1HT PSU: Corsair AX860i OS: Windows 7 Ultimate(With all Windows updates installed) I've also discovered that the disappearing sensors do not happen if I close iCUE SPACE before starting benchmark and open it again when benchmark finished. So it seems the issue is failing to "paint"/"render" the sensor output under high system load. Also another issue with iCUE SPACE with same version on both my systems: iCUE SPACE has a tendency to randomly put itself on top of screen-saver. Edit: Have entered this systems info prepended by "System2:" in forum "System Specs" form. Edited February 22, 2019 by Hagbard Celine More info... Link to comment Share on other sites More sharing options...
ArgonV Posted March 3, 2021 Share Posted March 3, 2021 (edited) Hello all, I hate to necro this thread - but I too am seeing these behaviors with iCUE software and Commander Pro and Lighting Node Core. I have two SP RBG Pro Series case fans up front, H100X CPU cooler, RGB Vengeance Pro mem, and 3 temp sensors all wired up (about to add some LED strips). I boiled it down to running HWiNFO64 in the background while monitoring during benching - so now I don't. Thought I'd let you all know my outcome. Edited March 3, 2021 by ArgonV Link to comment Share on other sites More sharing options...
Recommended Posts