F5F Stay Refreshed Hardware Desktop A single case fan pauses for a moment during the startup of Windows.

A single case fan pauses for a moment during the startup of Windows.

A single case fan pauses for a moment during the startup of Windows.

I
iTsMrLuisMC_
Member
224
04-12-2020, 04:52 AM
#1
Hello everyone, I’m dealing with a Gigabyte B660M DS3H motherboard and encountered an odd problem with my case fans. When I power on, the standard short POST beep occurs normally. However, shortly after the Windows logo appears, a prolonged ~3-second beep emanates from the system speaker. After some investigation, it turns out one of my fans stopped completely at that exact moment. Once the boot process begins, it resumes spinning a few seconds later, while the other fans keep running continuously. This behavior is unusual—I’ve tested replacing the faulty fan and disabled the BEEP sound in BIOS, but the issue persists. The long beep seems linked to the cooler cycling on and off during Windows loading. It started after I opened the PC for cleaning and formatting, and even after reformatting, it continues. All connections appear intact. Could this pattern be typical for a case fan during OS transition? Why does only one fan behave this way? Any advice would be greatly appreciated. Thanks ahead!
I
iTsMrLuisMC_
04-12-2020, 04:52 AM #1

Hello everyone, I’m dealing with a Gigabyte B660M DS3H motherboard and encountered an odd problem with my case fans. When I power on, the standard short POST beep occurs normally. However, shortly after the Windows logo appears, a prolonged ~3-second beep emanates from the system speaker. After some investigation, it turns out one of my fans stopped completely at that exact moment. Once the boot process begins, it resumes spinning a few seconds later, while the other fans keep running continuously. This behavior is unusual—I’ve tested replacing the faulty fan and disabled the BEEP sound in BIOS, but the issue persists. The long beep seems linked to the cooler cycling on and off during Windows loading. It started after I opened the PC for cleaning and formatting, and even after reformatting, it continues. All connections appear intact. Could this pattern be typical for a case fan during OS transition? Why does only one fan behave this way? Any advice would be greatly appreciated. Thanks ahead!

C
Char1ie_XD
Senior Member
578
04-12-2020, 03:00 PM
#2
Have you verified your fan configuration in the BIOS? Many BIOS options come with default settings like DC or PWM that often underpower fans, leading them to shut down prematurely. Typically, I adjust the minimum speed manually because fan behavior varies widely.
C
Char1ie_XD
04-12-2020, 03:00 PM #2

Have you verified your fan configuration in the BIOS? Many BIOS options come with default settings like DC or PWM that often underpower fans, leading them to shut down prematurely. Typically, I adjust the minimum speed manually because fan behavior varies widely.

N
NGWessel
Member
160
04-12-2020, 07:05 PM
#3
Hi! Yeah, I checked this part. The BIOS is the same as it always was, on automatic, and before I didn't have this problem with this FAN number 2 (SYS_FAN2), however, after the internal cleaning I did, this problem started...
N
NGWessel
04-12-2020, 07:05 PM #3

Hi! Yeah, I checked this part. The BIOS is the same as it always was, on automatic, and before I didn't have this problem with this FAN number 2 (SYS_FAN2), however, after the internal cleaning I did, this problem started...

W
WF_Catt
Posting Freak
761
04-17-2020, 04:22 PM
#4
The occurrence following the cleaning suggests it might be related to the fan's condition.
W
WF_Catt
04-17-2020, 04:22 PM #4

The occurrence following the cleaning suggests it might be related to the fan's condition.

B
biscuitnator
Junior Member
42
04-22-2020, 04:38 AM
#5
I tried it with a different fan, using the identical connector fan in the MoBo, but the issue remained unresolved...
B
biscuitnator
04-22-2020, 04:38 AM #5

I tried it with a different fan, using the identical connector fan in the MoBo, but the issue remained unresolved...