Sign in with
Sign up | Sign in
Your question
Solved

CPU Fan Error from BIOS - New Build

Tags:
  • BIOS
  • Fan
  • CPUs
  • Systems
Last response: in Systems
Share
April 22, 2014 7:23:23 AM

Hello,

New PC build here, using Hyper 212 EVO with an Intel i5 chip. It goes to the BIOS perfectly fine, but it displays "CPU Fan Error". I go into the BIOS and I leave the PC running for a few minutes (2-3 mins?). CPU Temps hover around 29 C and Fan speeds are around 550 rpm. When I look at the fan physically, it appears to be spinning continuously.

Looking at other threads at Tom's Hardware, I made sure that my EVO's fan is plugged into CPU_FAN (and not CPU_FAN_OPT). I applied heatsink using the pea in the center method. Any thoughts?

Thanks!

Edit: I let it stay on for around 10-15 minutes. Temperatures are up to about 31 C, fan speeds at low 600s.

Edit2: So it turns out that the BIOS' threshold for reporting a fan error is 600 rpm (fan speed displayed in red vs white). Thus, when I reset the PC after letting it run for 10-15 minutes, it is no longer reporting a CPU Fan error (as presumably the fan is running at >600 rpm). In this case, do I still have a problem, or is it fine to just leave it alone?

More about : cpu fan error bios build

April 22, 2014 7:41:25 AM

Use speed fan and prime 95 to stress test it. If your temps stay low then ignore the BIOS its probably just a glitch.
m
0
l

Best solution

April 22, 2014 7:41:43 AM

I had the same issue. The 212 EVO just runs at a lower RPM than the motherboard expects a fan to run. I am running the ASUS Maximum Hero. I just changed the fan rpm sensitivity in the bios to give a warning at a lower RPM. My default fan warning was at 600RPMs, I changed it to give a warning at 500RPMs.
Share
a b à CPUs
April 22, 2014 10:11:18 AM

A lot of Asus boards have that issue from posts I've read in the past, mine included. Following the above advice worked just fine. It will probably spin up above 600 rpm after a few minutes anyway, the BIOS just gets scared because the fan is a bit too lazy starting up. Mine has been at 500 rpm for nearly a year now without issue
m
0
l
!