[SOLVED] Fans running faster when computer is asleep

Aug 31, 2020
1
0
10
Hi all. Recently I've noticed in the pc I've built that when my computer is idle long enough for the monitor to fall asleep the fans in the computer will run at what sounds like max speed for a few seconds and then stop. They will do this every five minutes or so. I'm not sure what would make this happen or if it is something that can be fixed because it is very loud. If anyone has any info that could help I would really appreciate it.
 
Solution
First, try disabling hibernation, as outlined here. Windows has had issues on desktops with fast startup, hybrid sleep and hibernation for years now.

Hibernation

Disabling Hibernation is very easy.

You do not want to do this if you have a laptop as Hibernation is essential when a laptop's battery loses charge and the system needs to safely save it's state. If you have a laptop skip disabling Hibernation and instead disable Fast Startup and Hybrid Sleep if you are having issues.
To disable Hibernation:

1. The first step is to run the command prompt as administrator. In Windows 10, you can do this by right clicking on the start menu and clicking "Command Prompt (Admin)"

2. Type in "powercfg.exe /h off" without the quotes and press...
My thought is that even if the pc is idle then heat is continuing to build up.

Then at some given temperature the fans start up to cool things down - again....

Some normal cycle perhaps.

If you are still concerned or have other questions then update your post to include full system specs and OS information.

Include case and PSU information.

Someone may recognize a known or potential problem with respect to your build.
 
First, try disabling hibernation, as outlined here. Windows has had issues on desktops with fast startup, hybrid sleep and hibernation for years now.

Hibernation

Disabling Hibernation is very easy.

You do not want to do this if you have a laptop as Hibernation is essential when a laptop's battery loses charge and the system needs to safely save it's state. If you have a laptop skip disabling Hibernation and instead disable Fast Startup and Hybrid Sleep if you are having issues.
To disable Hibernation:

1. The first step is to run the command prompt as administrator. In Windows 10, you can do this by right clicking on the start menu and clicking "Command Prompt (Admin)"

2. Type in "powercfg.exe /h off" without the quotes and press enter. If you typed it in correctly, the cursor will simply start at a new line asking for new input

3. Now, simply close the command prompt window by clicking the X in the top right corner.


Before trying anything else, it would be helpful to know your full hardware specifications and operating system version.
 
Solution
Don't worry about it. Like you said it only does it for a few seconds. Remember, electricity flows through your motherboard and it depends what your computer is trying to do. Plus computer going to sleep needs to save a lot of things that is currently going on in your computer in a small frame of time so 100% Fan% is understandable.
 
Don't worry about it. Like you said it only does it for a few seconds. Remember, electricity flows through your motherboard and it depends what your computer is trying to do. Plus computer going to sleep needs to save a lot of things that is currently going on in your computer in a small frame of time so 100% Fan% is understandable.
This is nonsense. If the computer itself was actually asleep, there shouldn't be ANY fans running, AT ALL. Period. Ever.

But the OP was not talking about the computer going to sleep, they were talking about ONLY the monitor going to sleep. If only the monitor goes to sleep then Windows and other background processes are still running and things like checking for Windows updates, drive optimization trim/defragmenter, file indexing and other tasks might still be running.

I'd recommend that you change your Windows power plan to NOT allow the monitor to go to sleep on it's own, and instead to sleep the entire system, so that the fans cannot come on until the system wakes.

But again, making any actual recommendations are dependent on knowing what hardware is actually in use? Like I asked originally.