Aftermarket CPU cooler cpu fan error

jss8b9

Honorable
Sep 6, 2013
6
0
10,510
I am using a noctua after market cpu cooler and I have it plugged into my NZXT sentry-2 fan controller instead of the cpu fan header. First question: is this ok? Should i plug it into the cpu fan header? Second questions: if it is okay then how can i get rid of the error that comes up on start up?
 
Solution
If you have it in the CPU fan header and are getting a post error its because the fan is dropping below the minimum 600RPM for Intel or 800RPM for AMD at post. This doesn't mean the fan is broken or doesn't work - I have a Thermalright 140mm fan that does that on an AMD board. Once you confirm that the fan is running properly once you go into Windows you can either disable the warning in the BIOS or change the alert parameters for it (if you motherboard allows). I just disabled the alert on my Thermalright True Spirit 140. For some reason it stops for a couple seconds right before post and that's why I was getting my error. Runs fine upon boot.

Dogsnake

Distinguished
The cpu fan is best plugged to the MB header..directly. When attached there, the fan speed is monitored by the MB. Also it is adjusted to aid in cooling. There may be a bios setting to disable alerts, you would need to check your documentation. BTW the error message can be a system saver. It is not unheard of for cpu fans to stop working. My suggestion is to plug it into the designated MB header.
 

jeffredo

Distinguished
If you have it in the CPU fan header and are getting a post error its because the fan is dropping below the minimum 600RPM for Intel or 800RPM for AMD at post. This doesn't mean the fan is broken or doesn't work - I have a Thermalright 140mm fan that does that on an AMD board. Once you confirm that the fan is running properly once you go into Windows you can either disable the warning in the BIOS or change the alert parameters for it (if you motherboard allows). I just disabled the alert on my Thermalright True Spirit 140. For some reason it stops for a couple seconds right before post and that's why I was getting my error. Runs fine upon boot.
 
Solution