-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
- HP Community
- Desktops
- Desktop Hardware and Upgrade Questions
- BIOS Error 512 Chassis Fan Not Detected After Replacing Liqu...

Create an account on the HP Community to personalize your profile and ask a question
05-05-2023 05:09 PM - edited 05-09-2023 06:50 PM
I am receiving a BIOS error 512 "Chassis Fan Not Detected" on startup ever since removing the Asetek liquid cooler and replacing it with an Intel fan driven heatsink.
There are 3 fan connections on my motherboard.
CPU FAN - 4 Pin - Previously connected to the 80mm case fan that was mounted to the heat exchanger/radiator from the Asetek cooler. I am still using this same fan but have it mounted to the back of the case without the radiator.
PUMP FAN - 4 Pin - Previously connected to the Asetek water pump.
It seems like regardless of which of these 2 fans (either the 80mm case fan OR the Intel air cooler heatsink fan) the PUMP FAN connection is not detecting the fan. I assume that this 4 pin PUMP FAN port is what is being referred to in the BIOS as the "rear chassis fan."
I currently have my Intel heatsink fan plugged in to the CPU FAN connection, and in the bios it is registering a proper RPM.
There is also a third fan connection on my motherboard, but this is labeled SYS FAN and is a 3 pin arrangement. This was never connected to anything previously and is apparently not monitored by the BIOS.
In my bios there is NO way to ignore any of these fans, so as of right now, my only solution is to press F1 to continue every time I want to boot!
I did notice that the Asetek liquid cooler pump has pins 1 and 4 shorted on the pump plug, which are the outer most connections on the plug. There are only 3 wires which lead from this plug to the Asetek pump. From my brief research it appears that the Asetek fan is jumpering "PWM" and "Ground" for their pump.
Are there any solutions for what I can do to eliminate having to press F1 to continue every single time I want to boot?
Both of my fans which are connected are 4 wire fans as well, plugged in to the 4 pin fan connectors on the motherboard.
Why is my motherboard not detecting an RPM from any of the 2 fans that I have tried connecting to the PUMP FAN connection, yet the CPU FAN port works properly? and displays an RPM?
05-07-2023 12:12 PM
Using the SYS Fan header for a fan may be the way to disable that error message.
I am a volunteer forum member. If my suggestion helped you solve your issue, help others by marking that post as the accepted solution. Say thanks by clicking on the Yes button next to the "was this reply helpful?"
05-07-2023 04:25 PM - edited 05-07-2023 04:26 PM
Good afternoon. Unfortunately the 3-pin SYS_FAN header on the motherboard was NEVER used with the factory setup that I have been using for 8-1/2 years. The Asetek AIO cooler was formerly connected to the 4 pin PUMP_FAN header and the case fan that pulled air through the radiator/heat exchanger was connected to the 4 pin CPU_FAN header.
Nothing was ever connected to the SYS_FAN header, and contrary to what the BIOS labels the CPU and System Fan by name, this SYS_FAN 3 pin header is apparently unmonitored as only 2 fans or cooling devices are listed in the BIOS rather than 3.
05-08-2023 09:44 AM
What I suggested was to try connecting a fan to the header.
"Nothing was ever connected to the SYS_FAN header, and contrary to what the BIOS labels the CPU and System Fan by name, this SYS_FAN 3 pin header is apparently unmonitored as only 2 fans or cooling devices are listed in the BIOS rather than 3."
That may not matter as the BIOs firmware may sense the connection.
SyS_FAN is a label I have seen on DIY boards I used in the past, and it meant chassis fan.
I am a volunteer forum member. If my suggestion helped you solve your issue, help others by marking that post as the accepted solution. Say thanks by clicking on the Yes button next to the "was this reply helpful?"
05-08-2023 06:43 PM - edited 05-08-2023 06:44 PM
I did connect a fan to the 3 pin SYS_FAN header a few days ago, no change. In the BIOS it only monitors 2 fan headers, not 3. And in the 8-1/2 years I have been using this system, nothing has ever been connected to the 3 pin SYS_FAN header, so I do not believe that is the header that is producing this BIOS error. It has to 100% be the PUMP_FAN 4 pin header producing this error. This PUMP_FAN header was previously attached to my Asetek AIO cooler before I removed it. I have a 4 pin case fan connected to the PUMP_FAN header.
I also did another test. I currently have my CPU heatsink fan connected to the CPU_FAN header, which displays an appropriate RPM in the BIOS. I temporarily connected this same exact CPU heatsink fan to the PUMP_FAN header as well. Although the fan works properly, this fan also produces 0 RPM within the bios when connected to this particular PUMP_FAN header.
Lastly, when connecting one of my 4 pin fans to the 3 pin SYS_FAN header (that has never had anything connected to it ever before) that also does not satisfy the BIOS either. I am 100% certain that the SYS_FAN 3 pin header on the motherboard is NOT monitored by the BIOS.
05-09-2023 10:06 AM
Eight years of use is an exceptionally long and superior service life for a desktop PC.
Perhaps you should have led with that. PCs do not last forever.
The motherboard may be approaching the end of its service life.
Seeing that error, if it is the only issue would seem to me to be a very small price to pay to avoid having to source a replacement desktop PC.
I am a volunteer forum member. If my suggestion helped you solve your issue, help others by marking that post as the accepted solution. Say thanks by clicking on the Yes button next to the "was this reply helpful?"
05-09-2023 12:42 PM
I am starting to believe that all of the typing and explanations that I have provided have all been for nothing. Did you read anything that I typed previously at all? I stated very many times now that this bios error does NOT display when the Asetek AIO cooler is installed but rather only appears when I have a case fan plugged into the PUMP_FAN port that the Asetek AIO cooler was previously plugged in to.
I am not sure how I can possibly be more descriptive and/or detailed in my explanations beyond what I have parovided already.
05-09-2023 02:41 PM - edited 05-09-2023 02:55 PM
Did you remove the HP product name and product ID(number) from the thread?
It would certainly help to have that information.
What was the reason that you removed the cooler and decided to go to an air cooling solution?
Did the Asetek AIO cooler no longer function?
I am a volunteer forum member. If my suggestion helped you solve your issue, help others by marking that post as the accepted solution. Say thanks by clicking on the Yes button next to the "was this reply helpful?"
05-09-2023 06:53 PM - edited 05-09-2023 06:54 PM
I do not believe I had ever added the product previously, but I have added it to the main thread now and it is a HP ENVY Phoenix Desktop - 810-430qe CTO. The reason I removed the Asetek AIO cooler was because it began to make a horrid crackling sound about every 30 seconds. For the last few months I'd notice an occasional crackle, which I thought was harddrive related. However I traced it to the AIO cooler. I removed the AIO cooler, cleaned everything really well, applied new thermal compound, and everything was good for maybe 5-7 days or so until the crackling sound returned with a vengeance. So I removed the AIO cooler entirely and replaced it with a fan driven heatsink, because there was no way I was comfortable leaving my system running unattended with the CPU cooler behaving like that.
05-10-2023 10:25 AM
If you want to continue using the venerable desktop without the irritating issue, you might consider replacing the Asetek AIO cooler with a new or "newer" one.
The Asetek AIO Coolers are available, even secondhand on eBay for cheap.
That should eliminate the issue which led you to begin this thread.
I am a volunteer forum member. If my suggestion helped you solve your issue, help others by marking that post as the accepted solution. Say thanks by clicking on the Yes button next to the "was this reply helpful?"