kevindd992002

I'm not entirely sure what happened but I'm on-site today and I decided to unplug and replug the two fans to male headers of the H100i Pro and lo and behold that fixed the issue! Before I unplugged them, I made sure that there were no loose connections and all that. So again, this just proves that this is not a Noctua NF-A12 (at least for this particular model) issue.

Yes, I still have the original ML fans. I'll have to test more this weekend and report back. As for the power requirements, I don't understand because the whole kit is connected to a SATA power header which can supply more than enough current to the pump, LED's, and fans. The Noctua NF-A12 draw a mere 140mA @ 12V which is less than the current draw of the Corsair ML fans (219mA @ 12V) so how did you conclude that this is a power requirement issue? My bad. I don't look at everyone's signature. I saw that you're part of the Corsair "BETA" team so I thought you work for Corsair. I'm sure I wasn't the first one that made that mistake with you. I understand that certain fans don't work with systems of their competitors, I really do, but I still need to understand why one of the Noctua fans work fine and the other does not. I have to see if the problem follow the fans or one of the PWM headers.

I still need an answer here. I'm not entirely convinced that it is the Noctua fans that's the issue here. If it were, there'd be loads of people claiming such already. NF-A12's are one of the best fans ever created. Since you're from Corsair, I kinda half-expected that you would give that bias answer but can we not be unfair to your competitors?

I did think of that but how do you explain the weird reading on just fan 2 and not fan 1? Also, I'm trying to research on this potential issue with Noctua fans and I don't find any reference about it. A lot of people change the Corsair fans with Noctua fans with their H100i Pro AIO's and don't experience the same issue as I do. What gives?

Yes, I do have USB drivers installed for my motherboard, which I believe are part of the "AMD Chipset Driver" found here: https://www.gigabyte.com/ph/Motherboard/X570-I-AORUS-PRO-WIFI-rev-10/support#support-dl

Bump! 10char.

@DevBiker A follow-up on this please? Thanks.

No, not at all. This is a fresh OS install and does not have much third-party software yet.

Another weirder screenshot!

I see. Here you go: Both stock fans are replaced with brand new Noctua NF-A12 fans which are rated from 450 - 2000 RPM so I'm not sure why I'm seeing RPM's in the 4000+ range for Fan2. There's got to be something wrong here.

No additional monitoring issues. This is a fresh OS install. Yes, I'm connecting via remote desktop. I didn't know that could be an issue. So that won't work? No issues seen with the driver. EDIT: Ok, accessing the system via Teamviewer instead fixed the issue. So is RDP known to really cause these USB issues? Also, my profile is set to quiet now but I don't understand why fan1 has a low RPM (500 RPM range) while fan2 has a high RPM (4000 range). Why won't they have the same speed when they are both connected to the H100i Pro Y-connector?

Anybody from Corsair can help me please?

I just installed my brand new H100i Pro in my AMD system and plugged in the USB connection from the pump to one of the motherboard headers. Windows 10 was able to detect the connection and all (listed in both Device Manager and USBDevView). I installed the latest version of Corsair iCue and it did install the Corsair drivers (Corsair USBXp Driver) properly too. But when I start the program, it still says No Device Detected. This is the first time I've worked with Corsair AIO's but so far the initial impressions isn't very good. @DevBiker, can you please help here? Thanks.