F5F Stay Refreshed Hardware Desktop The Gigabyte B550 Aorus Pro AX BIOS update (F14c) caused some issues; fans and CPU tuning are affected.

The Gigabyte B550 Aorus Pro AX BIOS update (F14c) caused some issues; fans and CPU tuning are affected.

The Gigabyte B550 Aorus Pro AX BIOS update (F14c) caused some issues; fans and CPU tuning are affected.

1
1Nuky22skin
Member
140
09-26-2016, 10:22 PM
#1
I changed my motherboard BIOS yesterday and it affected both EasyTune and System Information Viewer. EasyTune can no longer display the SYS FAN4, SYS FAN6 PUMP and SYS FAN5 PUMP headers, which stops its use. When I connect fans to SYS FAN6 PUMP (where they worked before), they keep spinning up and down and briefly return to 1400RPM. It also can’t save the CPU ‘Turbo’ setting after rebooting—though I did enable ‘remember OC after reboot’ in settings. The missing fan headers are still visible in the BIOS, but not in EasyTune, which makes it hard to see them in the app. I tried uninstalling EasyTune, but it didn’t fully remove it and now I can’t reinstall it, which is frustrating. System Information Viewer (SIV) no longer shows my fans correctly; the PWM range is damaged, showing a lower maximum speed than the 90% value (refer to photo). After rebooting, fans spin at 1400RPM, higher than the 14% PWM I set, so I have to load my fan profile each time. They also keep spinning up and down, indicating something is wrong. Even though EasyTune lists missing headers in both BIOS and SIV, this issue persists. I’ve had to move fans to SYS FAN3 and use the BIOS to set a default profile, while Ryzen Master handles the CPU Turbo OC—since those are the only ways Windows will remember them on restart. Should I go back to my older BIOS (I think version 13f)? Have BIOS updates caused these kinds of problems before?
1
1Nuky22skin
09-26-2016, 10:22 PM #1

I changed my motherboard BIOS yesterday and it affected both EasyTune and System Information Viewer. EasyTune can no longer display the SYS FAN4, SYS FAN6 PUMP and SYS FAN5 PUMP headers, which stops its use. When I connect fans to SYS FAN6 PUMP (where they worked before), they keep spinning up and down and briefly return to 1400RPM. It also can’t save the CPU ‘Turbo’ setting after rebooting—though I did enable ‘remember OC after reboot’ in settings. The missing fan headers are still visible in the BIOS, but not in EasyTune, which makes it hard to see them in the app. I tried uninstalling EasyTune, but it didn’t fully remove it and now I can’t reinstall it, which is frustrating. System Information Viewer (SIV) no longer shows my fans correctly; the PWM range is damaged, showing a lower maximum speed than the 90% value (refer to photo). After rebooting, fans spin at 1400RPM, higher than the 14% PWM I set, so I have to load my fan profile each time. They also keep spinning up and down, indicating something is wrong. Even though EasyTune lists missing headers in both BIOS and SIV, this issue persists. I’ve had to move fans to SYS FAN3 and use the BIOS to set a default profile, while Ryzen Master handles the CPU Turbo OC—since those are the only ways Windows will remember them on restart. Should I go back to my older BIOS (I think version 13f)? Have BIOS updates caused these kinds of problems before?

A
adamgames2016
Member
133
09-26-2016, 10:22 PM
#2
Reinstall the same BIOS to verify integrity, then assess whether a rollback to the prior version is necessary. The chances are high this release contains a manufacturing defect.
A
adamgames2016
09-26-2016, 10:22 PM #2

Reinstall the same BIOS to verify integrity, then assess whether a rollback to the prior version is necessary. The chances are high this release contains a manufacturing defect.

W
WaTis
Junior Member
40
09-26-2016, 10:22 PM
#3
Hi, I'm facing the same issue too. Running Win 11 with X470 AORUS ULTRA GAMING (rev. 1.0) alongside F62c and SIV at B21.0504.1 works perfectly on Win 10 with F61. Everything seems fine.
W
WaTis
09-26-2016, 10:22 PM #3

Hi, I'm facing the same issue too. Running Win 11 with X470 AORUS ULTRA GAMING (rev. 1.0) alongside F62c and SIV at B21.0504.1 works perfectly on Win 10 with F61. Everything seems fine.

O
OreoHer0
Member
226
09-26-2016, 10:22 PM
#4
I’ve recreated your problem and verified it remains unresolved in BIOS version f14d. Going back to f13 resolved it for me. Can you find a method to file a formal bug report with Gigabyte?
O
OreoHer0
09-26-2016, 10:22 PM #4

I’ve recreated your problem and verified it remains unresolved in BIOS version f14d. Going back to f13 resolved it for me. Can you find a method to file a formal bug report with Gigabyte?

G
Gustatwgames
Junior Member
10
09-26-2016, 10:22 PM
#5
Thanks for bringing this up. I also switched back to the F13 Firmware last weekend, and it resolved some of the problems I reported on the Gigabyte support site—their phone support there isn’t very helpful. Here are Gigabyte’s answers to my two questions:
G
Gustatwgames
09-26-2016, 10:22 PM #5

Thanks for bringing this up. I also switched back to the F13 Firmware last weekend, and it resolved some of the problems I reported on the Gigabyte support site—their phone support there isn’t very helpful. Here are Gigabyte’s answers to my two questions:

J
JDM23
Junior Member
17
09-26-2016, 10:22 PM
#6
Observed a new "F14d" BIOS available on the Gigabyte site. Uncertain about trying it out.
J
JDM23
09-26-2016, 10:22 PM #6

Observed a new "F14d" BIOS available on the Gigabyte site. Uncertain about trying it out.