mandjschorg Posted March 22, 2016 Share Posted March 22, 2016 The latest update on 3-21-2016 is causing my fans on my H100i-GTX to slowdown and speed back up. I have tried a few things, I went to stability and checked corsair link support and that didn't fix and I also tried in hardware monitoring to set asetek fan speed to 100%, that does take it to 100% but the fans still speed up and slow down. For now I just close aida64 and all is good, somehow aida64 is trying to control the fan speed or something in this new update, all was good before. I may also add when I do a cache and memory benchmark it stops doing that and fans on the H100i-GTX run normal, if I do a system stability test tho the fans still go up and down Quote Link to comment Share on other sites More sharing options...
mandjschorg Posted March 22, 2016 Author Share Posted March 22, 2016 I found the issue, I have been using the sensor panel to show on my desktop, I decided to disable that just to see and everything is working as it should now, fans are back to normal. Any reason why this could be causing an issue? Scratch that as soon as went into computer then sensor its acting up again, seems as though when I go into the sensor page or have the sensor panel monitoring is when the issue happens. Also have a new temp showing up as temperature #1 that has never been there before, it stays for a while then disappears then pops back up again Quote Link to comment Share on other sites More sharing options...
Fiery Posted March 23, 2016 Share Posted March 23, 2016 Try to set the Asetek fan speed setting to the value you've configured for your fans in the Corsair Link Software, e.g. 60% or such. BTW, have you tried closing Corsair Link software? 1 Quote Link to comment Share on other sites More sharing options...
mandjschorg Posted March 23, 2016 Author Share Posted March 23, 2016 I just closed corsair Link and went to the sensor page and all is good, I don't know what I would set the asterik fan speed to since corsair link varies the fan speed due to temps, Like if I set to 60% I don't want it to just stay at that, sometimes I put it on say balanced, quiet or performance depending on what I am doing. Corsair link had an update a week or 2 before aida64 but on the previous version of aida64 all was good with the new update. I tried various settings and even setting asterik to 100% and the fans go to 100% and slow way down speed back up, as long as I stay out of the sensor page it all works fine Quote Link to comment Share on other sites More sharing options...
Fiery Posted March 23, 2016 Share Posted March 23, 2016 I just closed corsair Link and went to the sensor page and all is good, I don't know what I would set the asterik fan speed to since corsair link varies the fan speed due to temps, Like if I set to 60% I don't want it to just stay at that, sometimes I put it on say balanced, quiet or performance depending on what I am doing. I have set it to a full 100% and it still does it. Corsair link had an update a week or 2 before aida64 but on the previous version of aida64 all was good with the new update Then I suppose the issue is that AIDA64 sets the fan speed to its default value (or the one you configured as Asetek fan speed), but then Corsair Link software will override that when it is running in the background. That's a collision that we cannot avoid on our end, and is caused by the improper USB API that some Asetek-6 based water coolers use. The problem is that you cannot detect water cooler temperature and fan RPM reading without altering the fan duty cycle (%) setting So you have to send a duty cycle value in order to get sensor readings back. 1 Quote Link to comment Share on other sites More sharing options...
mandjschorg Posted March 23, 2016 Author Share Posted March 23, 2016 Then I suppose the issue is that AIDA64 sets the fan speed to its default value (or the one you configured as Asetek fan speed), but then Corsair Link software will override that when it is running in the background. That's a collision that we cannot avoid on our end, and is caused by the improper USB API that some Asetek-6 based water coolers use. The problem is that you cannot detect water cooler temperature and fan RPM reading without altering the fan duty cycle (%) setting So you have to send a duty cycle value in order to get sensor readings back. It was working just fine before the update, what would change? And do you have any idea what that temperature #1 is? it is showing then will disappear then pop back up again, would a dump help you with that? I believe that temp #1 might be water temp as it is matching exactly what my corsair link water temp is, if we could get rid of that from detecting that we may be ok, because before the update aida64 was not detecting the water temp. Quote Link to comment Share on other sites More sharing options...
Fiery Posted March 23, 2016 Share Posted March 23, 2016 Temperature #1 is the water temperature for your H100i GTX. There should also be a Pump #1 indicating the pump RPM. Before the update I suppose AIDA64 didn't handle your H100i GTX device at all, and so it couldn't collide with Corsair's own software. 1 Quote Link to comment Share on other sites More sharing options...
mandjschorg Posted March 23, 2016 Author Share Posted March 23, 2016 Temperature #1 is the water temperature for your H100i GTX. There should also be a Pump #1 indicating the pump RPM. Before the update I suppose AIDA64 didn't handle your H100i GTX device at all, and so it couldn't collide with Corsair's own software. yep there is a pump #1 as well, I tried to uncheck corsair link sensor support in preferences, stability to see if it would not support the corsair link and it still collides, maybe I can just go back to before the update if you still have that available for download and not do the update till it fully supports it. Thanks Quote Link to comment Share on other sites More sharing options...
Fiery Posted March 23, 2016 Share Posted March 23, 2016 yep there is a pump #1 as well, I tried to uncheck corsair link sensor support in preferences, stability to see if it would not support the corsair link and it still collides, maybe I can just go back to before the update if you still have that available for download and not do the update till it fully supports it. Thanks Your device doesn't use the Corsair Link framework. I know, it's quite confusing, since it still uses the Corsair Link software We cannot make it any better than now, unless Corsair comes up with a special API in the Corsair Link software that would allow us to avoid talking to the H100i GTX, and instead gain the sensor readings from Corsair Link software. What we can do right now is to add a new option to Preferences / Stability, called Asetek LC sensor support, that you can disable to avoid the discussed problems on your system. We will do that in the next AIDA64 beta update. I'll post a message into this topic once the new beta is available for download. 1 Quote Link to comment Share on other sites More sharing options...
Kleidokratoras Posted March 23, 2016 Share Posted March 23, 2016 I am having a similar problem. If I change in the preferences>stability>low-level sensor operations seems to fix it but I lose many readings from osd. When is the beta going to be released? Quote Link to comment Share on other sites More sharing options...
Fiery Posted March 24, 2016 Share Posted March 24, 2016 I am having a similar problem. If I change in the preferences>stability>low-level sensor operations seems to fix it but I lose many readings from osd. When is the beta going to be released? A few days from now. Less than a week Quote Link to comment Share on other sites More sharing options...
Kleidokratoras Posted March 24, 2016 Share Posted March 24, 2016 Ok. I will do my best to wait patiently please reply when the beta is released. Thank you Quote Link to comment Share on other sites More sharing options...
Fiery Posted March 26, 2016 Share Posted March 26, 2016 The mentioned new AIDA64 beta update is available for download at: http://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Quote Link to comment Share on other sites More sharing options...
Kleidokratoras Posted March 26, 2016 Share Posted March 26, 2016 It works just fine. Thanks for the update. Is there a way for the pump readings to "stay" while Asetek LC sensor support is unchecked? Also the PSU readings are lost. But I can live with that. And the psu is corsair. Quote Link to comment Share on other sites More sharing options...
Fiery Posted March 26, 2016 Share Posted March 26, 2016 It works just fine. Thanks for the update. Is there a way for the pump readings to "stay" while Asetek LC sensor support is unchecked? Also the PSU readings are lost. But I can live with that. And the psu is corsair. Asetek LC is the control and monitoring logic inside such water cooling devices like Corsair H100i GTX and H80i GT. It provides the following readings: liquid temperature, fan RPM and pump RPM. If you disable Asetek LC sensor support, there's no way to talk to the device and so it's normal that you lose those readings. What kind of PSU have you got? Corsair is famous for making very different PSUs on the inside In other words, AXi may sound quite similar to HXi, but AIDA64 has to handle them with different code paths. Quote Link to comment Share on other sites More sharing options...
Kleidokratoras Posted March 26, 2016 Share Posted March 26, 2016 I have ax1500i. Quote Link to comment Share on other sites More sharing options...
Fiery Posted March 26, 2016 Share Posted March 26, 2016 I have ax1500i. We can check what's going on around monitoring your AX1500i if you could right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> USB PSU Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. Thank you in advance. Quote Link to comment Share on other sites More sharing options...
Kleidokratoras Posted March 26, 2016 Share Posted March 26, 2016 ------[ AIDA64 Extreme v5.70.3805 Beta ]------------[ Microsoft Windows 10 Pro 10.0.10586.164 (64-bit) ]------------[ Motherboard Info ]------Motherboard ID : 63-0100-000001-00101111-122211-Chipset$1APPW010_BIOS DATE: 12/23/15 08:56:38 VER: 17.02Motherboard Model : Asus Crossblade RangerMotherboard Chipset : AMD A88X, AMD K15.1DMI MB Manufacturer : ASUSTeK COMPUTER INC.DMI MB Product : CROSSBLADE RANGERDMI MB Version : Rev X.0xDMI MB Serial : 140728992802542DMI SYS Manufacturer: System manufacturerDMI SYS Product : System Product NameDMI SYS Version : System VersionDMI SYS Serial : System Serial NumberDMI BIOS Version : 1702------[ DevClass / Human Interface Devices ]------<DESC>HID-compliant consumer control device</DESC><DEVPATH>\\?\hid#vid_1038&pid_1238&mi_03&col01#a&26ae6661&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1038&PID_1238&MI_03&COL01\A&26AE6661&0&0000</INSTANCE><BUSNUM>0000000A</BUSNUM><ADDR>00000006</ADDR><DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_1038&pid_1238&mi_03&col02#a&26ae6661&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1038&PID_1238&MI_03&COL02\A&26AE6661&0&0001</INSTANCE><BUSNUM>0000000A</BUSNUM><ADDR>00000006</ADDR><DESC>HID-compliant mouse</DESC><DEVPATH>\\?\hid#vid_046d&pid_c332&mi_00#a&213fa377&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C332&MI_00\A&213FA377&0&0000</INSTANCE><BUSNUM>00000006</BUSNUM><ADDR>00000003</ADDR><DESC>HID Keyboard Device</DESC><DEVPATH>\\?\hid#vid_1b1c&pid_1b11&mi_01&col01#9&29e15ceb&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1B1C&PID_1B11&MI_01&COL01\9&29E15CEB&0&0000</INSTANCE><BUSNUM>00000003</BUSNUM><ADDR>00000003</ADDR><DESC>HID-compliant consumer control device</DESC><DEVPATH>\\?\hid#vid_1b1c&pid_1b11&mi_01&col02#9&29e15ceb&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1B1C&PID_1B11&MI_01&COL02\9&29E15CEB&0&0001</INSTANCE><BUSNUM>00000003</BUSNUM><ADDR>00000003</ADDR><DESC>HID Keyboard Device</DESC><DEVPATH>\\?\hid#vid_046d&pid_c332&mi_01&col01#a&2979a4b&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C332&MI_01&COL01\A&2979A4B&0&0000</INSTANCE><BUSNUM>00000007</BUSNUM><ADDR>00000004</ADDR><DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_1b1c&pid_1b11&mi_02#9&16b140ad&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1B1C&PID_1B11&MI_02\9&16B140AD&0&0000</INSTANCE><BUSNUM>00000004</BUSNUM><ADDR>00000004</ADDR><DESC>HID-compliant consumer control device</DESC><DEVPATH>\\?\hid#vid_046d&pid_c332&mi_01&col02#a&2979a4b&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C332&MI_01&COL02\A&2979A4B&0&0001</INSTANCE><BUSNUM>00000007</BUSNUM><ADDR>00000004</ADDR><DESC>HID-compliant system controller</DESC><DEVPATH>\\?\hid#vid_046d&pid_c332&mi_01&col03#a&2979a4b&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C332&MI_01&COL03\A&2979A4B&0&0002</INSTANCE><BUSNUM>00000007</BUSNUM><ADDR>00000004</ADDR><DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_046d&pid_c332&mi_01&col04#a&2979a4b&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C332&MI_01&COL04\A&2979A4B&0&0003</INSTANCE><BUSNUM>00000007</BUSNUM><ADDR>00000004</ADDR><DESC>HID-compliant mouse</DESC><DEVPATH>\\?\hid#virtualdevice&10&col01#2&1043fd72&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VIRTUALDEVICE&10&COL01\2&1043FD72&0&0000</INSTANCE><BUSNUM>0000000B</BUSNUM><ADDR></ADDR><DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_1038&pid_1230&mi_00#a&e51179&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1038&PID_1230&MI_00\A&E51179&0&0000</INSTANCE><BUSNUM>00000008</BUSNUM><ADDR>00000002</ADDR><DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_1b1c&pid_0c04#6&3b37d163&1&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1B1C&PID_0C04\6&3B37D163&1&0000</INSTANCE><BUSNUM>00000001</BUSNUM><ADDR>00000005</ADDR><DESC>HID Keyboard Device</DESC><DEVPATH>\\?\hid#virtualdevice&10&col02#2&1043fd72&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VIRTUALDEVICE&10&COL02\2&1043FD72&0&0001</INSTANCE><BUSNUM>0000000B</BUSNUM><ADDR></ADDR><DESC>HID Keyboard Device</DESC><DEVPATH>\\?\hid#virtualdevice&10&col03#2&1043fd72&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VIRTUALDEVICE&10&COL03\2&1043FD72&0&0002</INSTANCE><BUSNUM>0000000B</BUSNUM><ADDR></ADDR><DESC>HID-compliant mouse</DESC><DEVPATH>\\?\hid#virtualdevice&10&col04#2&1043fd72&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VIRTUALDEVICE&10&COL04\2&1043FD72&0&0003</INSTANCE><BUSNUM>0000000B</BUSNUM><ADDR></ADDR><DESC>HID Keyboard Device</DESC><DEVPATH>\\?\hid#vid_1b1c&pid_1b11&mi_00#9&176af22&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1B1C&PID_1B11&MI_00\9&176AF22&0&0000</INSTANCE><BUSNUM>00000002</BUSNUM><ADDR>00000002</ADDR><DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_046d&pid_c332&mi_01&col05#a&2979a4b&0&0004#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C332&MI_01&COL05\A&2979A4B&0&0004</INSTANCE><BUSNUM>00000007</BUSNUM><ADDR>00000004</ADDR><DESC>HID-compliant consumer control device</DESC><DEVPATH>\\?\hid#virtualdevice&10&col05#2&1043fd72&0&0004#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VIRTUALDEVICE&10&COL05\2&1043FD72&0&0004</INSTANCE><BUSNUM>0000000B</BUSNUM><ADDR></ADDR><DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_1038&pid_1230&mi_01#a&22f22c49&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1038&PID_1230&MI_01\A&22F22C49&0&0000</INSTANCE><BUSNUM>00000009</BUSNUM><ADDR>00000003</ADDR><DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_1b1c&pid_1b11&mi_03#9&381246f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1B1C&PID_1B11&MI_03\9&381246F&0&0000</INSTANCE><BUSNUM>00000005</BUSNUM><ADDR>00000005</ADDR>------[ DevClass / USBXpress Devices ]------<DESC>Corsair Hydro Series 7289 USB Device</DESC><DEVPATH>\\?\usb#vid_1b1c&pid_0c03#7289_1.0#{3c5e1462-5695-4e18-876b-f3f3d08aaf18}</DEVPATH><INSTANCE>USB\VID_1B1C&PID_0C03\7289_1.0</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000003</ADDR>------[ TT DPS PSUs ]------< No TT DPS PSU Found >------[ Digifanless PSUs ]------< No Digifanless PSU Found >------[ Corsair HXi/RMi PSUs ]------< No Corsair HXi/RMi PSU Found >------[ Corsair AXi PSUs ]------< No Corsair AXi PSU Found > Quote Link to comment Share on other sites More sharing options...
Kleidokratoras Posted March 26, 2016 Share Posted March 26, 2016 That was with Asetek LC sensor support off. Quote Link to comment Share on other sites More sharing options...
Kleidokratoras Posted March 26, 2016 Share Posted March 26, 2016 ------[ AIDA64 Extreme v5.70.3805 Beta ]------------[ Microsoft Windows 10 Pro 10.0.10586.164 (64-bit) ]------------[ Motherboard Info ]------Motherboard ID : 63-0100-000001-00101111-122211-Chipset$1APPW010_BIOS DATE: 12/23/15 08:56:38 VER: 17.02Motherboard Model : Asus Crossblade RangerMotherboard Chipset : AMD A88X, AMD K15.1DMI MB Manufacturer : ASUSTeK COMPUTER INC.DMI MB Product : CROSSBLADE RANGERDMI MB Version : Rev X.0xDMI MB Serial : 140728992802542DMI SYS Manufacturer: System manufacturerDMI SYS Product : System Product NameDMI SYS Version : System VersionDMI SYS Serial : System Serial NumberDMI BIOS Version : 1702------[ DevClass / Human Interface Devices ]------<DESC>HID-compliant consumer control device</DESC><DEVPATH>\\?\hid#vid_1038&pid_1238&mi_03&col01#a&26ae6661&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1038&PID_1238&MI_03&COL01\A&26AE6661&0&0000</INSTANCE><BUSNUM>0000000A</BUSNUM><ADDR>00000006</ADDR><DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_1038&pid_1238&mi_03&col02#a&26ae6661&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1038&PID_1238&MI_03&COL02\A&26AE6661&0&0001</INSTANCE><BUSNUM>0000000A</BUSNUM><ADDR>00000006</ADDR><DESC>HID-compliant mouse</DESC><DEVPATH>\\?\hid#vid_046d&pid_c332&mi_00#a&213fa377&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C332&MI_00\A&213FA377&0&0000</INSTANCE><BUSNUM>00000006</BUSNUM><ADDR>00000003</ADDR><DESC>HID Keyboard Device</DESC><DEVPATH>\\?\hid#vid_1b1c&pid_1b11&mi_01&col01#9&29e15ceb&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1B1C&PID_1B11&MI_01&COL01\9&29E15CEB&0&0000</INSTANCE><BUSNUM>00000003</BUSNUM><ADDR>00000003</ADDR><DESC>HID-compliant consumer control device</DESC><DEVPATH>\\?\hid#vid_1b1c&pid_1b11&mi_01&col02#9&29e15ceb&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1B1C&PID_1B11&MI_01&COL02\9&29E15CEB&0&0001</INSTANCE><BUSNUM>00000003</BUSNUM><ADDR>00000003</ADDR><DESC>HID Keyboard Device</DESC><DEVPATH>\\?\hid#vid_046d&pid_c332&mi_01&col01#a&2979a4b&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C332&MI_01&COL01\A&2979A4B&0&0000</INSTANCE><BUSNUM>00000007</BUSNUM><ADDR>00000004</ADDR><DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_1b1c&pid_1b11&mi_02#9&16b140ad&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1B1C&PID_1B11&MI_02\9&16B140AD&0&0000</INSTANCE><BUSNUM>00000004</BUSNUM><ADDR>00000004</ADDR><DESC>HID-compliant consumer control device</DESC><DEVPATH>\\?\hid#vid_046d&pid_c332&mi_01&col02#a&2979a4b&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C332&MI_01&COL02\A&2979A4B&0&0001</INSTANCE><BUSNUM>00000007</BUSNUM><ADDR>00000004</ADDR><DESC>HID-compliant system controller</DESC><DEVPATH>\\?\hid#vid_046d&pid_c332&mi_01&col03#a&2979a4b&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C332&MI_01&COL03\A&2979A4B&0&0002</INSTANCE><BUSNUM>00000007</BUSNUM><ADDR>00000004</ADDR><DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_046d&pid_c332&mi_01&col04#a&2979a4b&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C332&MI_01&COL04\A&2979A4B&0&0003</INSTANCE><BUSNUM>00000007</BUSNUM><ADDR>00000004</ADDR><DESC>HID-compliant mouse</DESC><DEVPATH>\\?\hid#virtualdevice&10&col01#2&1043fd72&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VIRTUALDEVICE&10&COL01\2&1043FD72&0&0000</INSTANCE><BUSNUM>0000000B</BUSNUM><ADDR></ADDR><DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_1038&pid_1230&mi_00#a&e51179&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1038&PID_1230&MI_00\A&E51179&0&0000</INSTANCE><BUSNUM>00000008</BUSNUM><ADDR>00000002</ADDR><DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_1b1c&pid_0c04#6&3b37d163&1&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1B1C&PID_0C04\6&3B37D163&1&0000</INSTANCE><BUSNUM>00000001</BUSNUM><ADDR>00000005</ADDR><DESC>HID Keyboard Device</DESC><DEVPATH>\\?\hid#virtualdevice&10&col02#2&1043fd72&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VIRTUALDEVICE&10&COL02\2&1043FD72&0&0001</INSTANCE><BUSNUM>0000000B</BUSNUM><ADDR></ADDR><DESC>HID Keyboard Device</DESC><DEVPATH>\\?\hid#virtualdevice&10&col03#2&1043fd72&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VIRTUALDEVICE&10&COL03\2&1043FD72&0&0002</INSTANCE><BUSNUM>0000000B</BUSNUM><ADDR></ADDR><DESC>HID-compliant mouse</DESC><DEVPATH>\\?\hid#virtualdevice&10&col04#2&1043fd72&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VIRTUALDEVICE&10&COL04\2&1043FD72&0&0003</INSTANCE><BUSNUM>0000000B</BUSNUM><ADDR></ADDR><DESC>HID Keyboard Device</DESC><DEVPATH>\\?\hid#vid_1b1c&pid_1b11&mi_00#9&176af22&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1B1C&PID_1B11&MI_00\9&176AF22&0&0000</INSTANCE><BUSNUM>00000002</BUSNUM><ADDR>00000002</ADDR><DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_046d&pid_c332&mi_01&col05#a&2979a4b&0&0004#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_046D&PID_C332&MI_01&COL05\A&2979A4B&0&0004</INSTANCE><BUSNUM>00000007</BUSNUM><ADDR>00000004</ADDR><DESC>HID-compliant consumer control device</DESC><DEVPATH>\\?\hid#virtualdevice&10&col05#2&1043fd72&0&0004#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VIRTUALDEVICE&10&COL05\2&1043FD72&0&0004</INSTANCE><BUSNUM>0000000B</BUSNUM><ADDR></ADDR><DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_1038&pid_1230&mi_01#a&22f22c49&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1038&PID_1230&MI_01\A&22F22C49&0&0000</INSTANCE><BUSNUM>00000009</BUSNUM><ADDR>00000003</ADDR><DESC>HID-compliant vendor-defined device</DESC><DEVPATH>\\?\hid#vid_1b1c&pid_1b11&mi_03#9&381246f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}</DEVPATH><INSTANCE>HID\VID_1B1C&PID_1B11&MI_03\9&381246F&0&0000</INSTANCE><BUSNUM>00000005</BUSNUM><ADDR>00000005</ADDR>------[ DevClass / USBXpress Devices ]------<DESC>Corsair Hydro Series 7289 USB Device</DESC><DEVPATH>\\?\usb#vid_1b1c&pid_0c03#7289_1.0#{3c5e1462-5695-4e18-876b-f3f3d08aaf18}</DEVPATH><INSTANCE>USB\VID_1B1C&PID_0C03\7289_1.0</INSTANCE><BUSNUM>00000000</BUSNUM><ADDR>00000003</ADDR>------[ TT DPS PSUs ]------< No TT DPS PSU Found >------[ Digifanless PSUs ]------< No Digifanless PSU Found >------[ Corsair HXi/RMi PSUs ]------< No Corsair HXi/RMi PSU Found >------[ Corsair AXi PSUs ]------< No Corsair AXi PSU Found >with Asetek LC sensor support on. With a quick look it seems aida64 can't find my psu. Quote Link to comment Share on other sites More sharing options...
mandjschorg Posted March 27, 2016 Author Share Posted March 27, 2016 Working perfect now, is this only available in portable? I just entered my key into the beta and works fine. Also is there any way I can get the way I had the sensor panel and items I had in it in the stable version to the beta version, like move a config file so I don't have to redo redo the sensor panel items? Thanks Quote Link to comment Share on other sites More sharing options...
Kleidokratoras Posted March 27, 2016 Share Posted March 27, 2016 In sensor panel manager, right-click on sensor panel>sensorpanelmanager, you can export (top right) the sensor panel current configuration wherever you want. And then you can import it from the saved location. Quote Link to comment Share on other sites More sharing options...
Fiery Posted March 28, 2016 Share Posted March 28, 2016 That was with Asetek LC sensor support off. Thank you for the dumps. Please note that you don't need to enable any special options when your AXi Series PSU is connected via the USB dongle. But, when it's connected to a Corsair Link Commander or similar Corsair Link device, then you need to enable Corsair Link sensor support in AIDA64 / main menu / File / Preferences / Stability to make it work. If you still have issues after enabling that option, then please submit a Corsair Link Dump from the Sensor Debug right-click menu. I'm sorry for the confusion about Corsair PSUs. Connection type (directly connected to USB // connected via USB dongle // connected via Corsair Link Commander) makes a big difference in the way AIDA64 has to handle the PSU or water cooler. Quote Link to comment Share on other sites More sharing options...
Fiery Posted March 28, 2016 Share Posted March 28, 2016 Working perfect now, is this only available in portable? I just entered my key into the beta and works fine. Also is there any way I can get the way I had the sensor panel and items I had in it in the stable version to the beta version, like move a config file so I don't have to redo redo the sensor panel items? Thanks Your settings and preferences are stored in the file called AIDA64.INI. Make sure to backup that file before fiddling with AIDA64 upgrades. You can however simply extract the new beta ZIP package content into the existing AIDA64 (stable) installation folder. Let it overwrite any existing files. It will retain your existing settings (it will not overwrite or affect AIDA64.INI) and your entered license as well. Only AIDA64 stable updates are available as self-installer packages. Quote Link to comment Share on other sites More sharing options...
Kleidokratoras Posted March 28, 2016 Share Posted March 28, 2016 Actually I have it to an external usb cause the motherboard didn't have any other usb free and connected to the Link Commander. From what you said it seems I should only keep the usb. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.