F5F Stay Refreshed Power Users Overclocking BIOS issues! Need assistance!

BIOS issues! Need assistance!

BIOS issues! Need assistance!

A
Awembe
Junior Member
7
01-12-2016, 09:00 AM
#1
Hi everyone. I attempted a LIGHT overclock on my desktop PC using the MASSIM0 4.4 GHZ, but after finishing the process, I observed several issues upon restarting. Here are the main concerns:

1. After launching Windows 10, the OS failed to recognize the BIOS-set overclock range (between 3700 and 4400 MHz). No matter what frequency I adjusted in BIOS, the system consistently only saw the processor’s standard speed. Programs like cpu-z and hwmonitor reported speeds between 3.7 and 3.9 GHz. Even during stress tests, the frequency remained stuck at 3.7 GHz, despite a possible setting of 4.2 GHz in BIOS.
2. Under regular usage, the system reached 3.9 GHz, which was unexpected since BIOS usually displayed only 3.7 GHz. This inconsistency caught my attention.
3. Previously, I had disabled three settings to disable the integrated graphics card. These options were removed from BIOS, and now the system only recognizes the third and fourth RAM slots. The issue isn’t with the RAM itself but with the operating system not detecting it after installation.

Despite several attempts—updating BIOS, cleaning CMOS, removing the buffer battery for five hours, and reinstalling Windows 10—I still faced these persistent problems. Outside of these issues, the PC functions normally. I even performed a clean Windows 10 installation (version 1903). I continue to browse the internet and play games without any complications, except for the three mentioned concerns.

Could it be that the BIOS has become corrupted?
A
Awembe
01-12-2016, 09:00 AM #1

Hi everyone. I attempted a LIGHT overclock on my desktop PC using the MASSIM0 4.4 GHZ, but after finishing the process, I observed several issues upon restarting. Here are the main concerns:

1. After launching Windows 10, the OS failed to recognize the BIOS-set overclock range (between 3700 and 4400 MHz). No matter what frequency I adjusted in BIOS, the system consistently only saw the processor’s standard speed. Programs like cpu-z and hwmonitor reported speeds between 3.7 and 3.9 GHz. Even during stress tests, the frequency remained stuck at 3.7 GHz, despite a possible setting of 4.2 GHz in BIOS.
2. Under regular usage, the system reached 3.9 GHz, which was unexpected since BIOS usually displayed only 3.7 GHz. This inconsistency caught my attention.
3. Previously, I had disabled three settings to disable the integrated graphics card. These options were removed from BIOS, and now the system only recognizes the third and fourth RAM slots. The issue isn’t with the RAM itself but with the operating system not detecting it after installation.

Despite several attempts—updating BIOS, cleaning CMOS, removing the buffer battery for five hours, and reinstalling Windows 10—I still faced these persistent problems. Outside of these issues, the PC functions normally. I even performed a clean Windows 10 installation (version 1903). I continue to browse the internet and play games without any complications, except for the three mentioned concerns.

Could it be that the BIOS has become corrupted?

J
jelppa
Junior Member
37
01-12-2016, 10:59 AM
#2
If feasible, attempt to revert to the earlier BIOS version that functioned adequately.
J
jelppa
01-12-2016, 10:59 AM #2

If feasible, attempt to revert to the earlier BIOS version that functioned adequately.

T
Treemily
Member
58
01-13-2016, 07:08 AM
#3
Hello. Thank you for your response.
Here are the details about my motherboard bios:
Bios Asrock Z77 Extreme 4
Initially I used version 2.0, then switched to 2.90 and everything worked for a while.
When issues appeared, I attempted to update from 2.90 to a beta release.
I also tried reinstalling 2.90 but it didn’t work.
The 2.0 version is now unavailable.
T
Treemily
01-13-2016, 07:08 AM #3

Hello. Thank you for your response.
Here are the details about my motherboard bios:
Bios Asrock Z77 Extreme 4
Initially I used version 2.0, then switched to 2.90 and everything worked for a while.
When issues appeared, I attempted to update from 2.90 to a beta release.
I also tried reinstalling 2.90 but it didn’t work.
The 2.0 version is now unavailable.