![]() ![]() You think it would be better with only the front 140MM being a 3000 one ? I could downgrade the 2 NF F12 which I'm using on the GPU to some 2000 version instead of 3000 easily. Incidentally, the other fan with commonly reported PWM control issues is the PWM BeQuiet Silent Wings 2 and 3 series. ![]() By comparison, the 2000 PWM version draws a pittance and can be more easily managed. You also need to watch the current on the 3000 rpm model and can never use it on a splitter with most controllers. ![]() ![]() Hard to be in the same room, declining cooling benefits on anything but a massively dense custom radiator. Outside of sport overclocking, I am not sure who needs more than 2000 rpm on anything. So you either need a different fan controller that does not have an issue with that specific fan model or I would suggest moving down to the 2000 rpm version. Given the specification and amperage on that motor I am not completely surprised it behaves differently to the 2000 PWM. Interestingly, the 2000 RPM PWM and of course DC motor versions work fine, so it does suggest there is something different with the highest speed motor. It is something with the controller and PWM signal, but you are not going to be able work this out unless you are an electrical engineer and can make your PWM circuit. The two 3000 RPM PWM versions of the Noctua Industrial line (NF12 & A14) have never worked well on the Commander Pro. You likely need to come up with a new plan. Ordering a New Commander (will arrive tomorrow, I can send it back if it's not the problem cause Amazon good return policy) Ordering a New fan (but out of stock so im waiting) Exchange every fans with any of the 6 slots used So maybe some of you experienced something similar or have ideas about that. So for now, I currently ordered a new 'NF F12 IPPC 3000' to replace the one that don't wanna work with the Commander (this one is currently plugged in the manual controller that's given with my case and works fine) but I'm starting to think maybe the fan is completely fine, and the problem comes from the Commander ? I was forced to restart so it worked "properly" again. (-> this issue in particular, maybe it's because I launched HWINFO64 ?) Like just now I was playing and checking the GPU temp on Afterburner, and I found the fans way to loud, and in fact in iCue there was only the front and top fan showing, the RPM was changing randomly (from 514 to 15000+ rpm) and the temperature sensors were completely wrong (it was showing 5 degrees for the one agaisnt the backplate of the GPU). If I unplugged the fan and plug it into the manual controller of my case it would boot up immediatly without the "self restart" thing.Īlso sometimes, and randomly, everything is wrong. Sometimes it's gonna work fine, sometimes it's just not gonna spin at all and show 0 RPM, sometimes it's not gonna show at all in iCue.Īlso this morning when it stopped working with this fan in particular, if the fan was plugged into the Corsair, my computer would light up, start (this fan was spinning), then stop after 2s, and restart (and then the fan wasn't spinning). One of the NF F12 IPPC 3000 is recognized like randomly by the Commander Pro, not depending of which slot I plugged it into the commander. It works with 4 Noctua fans which are the following : I purchased a Corsair Commander Pro to control some fans. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |