F5F Stay Refreshed Hardware Desktop BIOS search fails for MCLK and FCLK values on ASRock B450M Pro4

BIOS search fails for MCLK and FCLK values on ASRock B450M Pro4

BIOS search fails for MCLK and FCLK values on ASRock B450M Pro4

Pages (2): 1 2 Next
I
IPS10
Senior Member
Find
623
06-10-2025, 07:06 PM
#1
Where exactly are the MCLK adjustments located? You seem to be looking for the settings related to the MCLK signal, not just the FCLK.
Reply
Reply
I
IPS10
06-10-2025, 07:06 PM #1

Where exactly are the MCLK adjustments located? You seem to be looking for the settings related to the MCLK signal, not just the FCLK.

Reply
Reply
H
haczykow
Member
Find
178
06-10-2025, 07:52 PM
#2
Yes, we have DID and FID included in the manual OC process.
Reply
Reply
H
haczykow
06-10-2025, 07:52 PM #2

Yes, we have DID and FID included in the manual OC process.

Reply
Reply
S
seva233
Junior Member
Find
10
06-10-2025, 09:37 PM
#3
The settings aren't listed in BIOS or Ryzen Master.
Reply
Reply
S
seva233
06-10-2025, 09:37 PM #3

The settings aren't listed in BIOS or Ryzen Master.

Reply
Reply
M
mobdeath101
Junior Member
Find
8
06-10-2025, 10:42 PM
#4
Yes, you mentioned not being able to adjust the memory multiplier directly. Have you explored various BIOS updates?
Reply
Reply
M
mobdeath101
06-10-2025, 10:42 PM #4

Yes, you mentioned not being able to adjust the memory multiplier directly. Have you explored various BIOS updates?

Reply
Reply
_
_Guava_
Junior Member
Find
13
06-12-2025, 02:52 PM
#5
Checking memory speed and the infinity fabric clock. I'm testing the ZenTimings app to see if it includes both settings. If not, I'll need to look into a BIOS update or consider using 3600MHz.
Reply
Reply
_
_Guava_
06-12-2025, 02:52 PM #5

Checking memory speed and the infinity fabric clock. I'm testing the ZenTimings app to see if it includes both settings. If not, I'll need to look into a BIOS update or consider using 3600MHz.

Reply
Reply
C
Creeperman3
Senior Member
Find
454
06-14-2025, 10:02 AM
#6
I really wish it hadn't happened. An Asus B450M-A would have been a smarter choice. The bottom panel is there, but it lacks the essential customization options.
Reply
Reply
C
Creeperman3
06-14-2025, 10:02 AM #6

I really wish it hadn't happened. An Asus B450M-A would have been a smarter choice. The bottom panel is there, but it lacks the essential customization options.

Reply
Reply
J
jollysaint
Member
Find
57
06-14-2025, 01:28 PM
#7
Everything appears alright.
Reply
Reply
J
jollysaint
06-14-2025, 01:28 PM #7

Everything appears alright.

Reply
Reply
N
NanoFyre
Member
Find
58
06-14-2025, 02:02 PM
#8
Yes, it seems stable.
Reply
Reply
N
NanoFyre
06-14-2025, 02:02 PM #8

Yes, it seems stable.

Reply
Reply
N
NovaKeo
Junior Member
Find
23
06-14-2025, 02:58 PM
#9
Used memtest86 with full CPU usage; temperatures stayed moderate. For accuracy, repeat testing would help. So far no crashes or failures reported.
Reply
Reply
N
NovaKeo
06-14-2025, 02:58 PM #9

Used memtest86 with full CPU usage; temperatures stayed moderate. For accuracy, repeat testing would help. So far no crashes or failures reported.

Reply
Reply
U
Und3rWorld
Member
Find
133
06-16-2025, 05:05 AM
#10
Prime95 large FFT is a solid way to check memory stability, just ensure your cooling is adequate—it's still demanding on the CPU but not as extreme as a full CPU stress test. Run it for at least 24 hours, preferably longer. If you encounter any issues, restart and compare to previous failures to pinpoint the problem. I realized I made a mistake by placing memory in the wrong slots during a recent build; after running Prime95 stability tests on the whole system and then specifically on memory, I identified the error.
Reply
Reply
U
Und3rWorld
06-16-2025, 05:05 AM #10

Prime95 large FFT is a solid way to check memory stability, just ensure your cooling is adequate—it's still demanding on the CPU but not as extreme as a full CPU stress test. Run it for at least 24 hours, preferably longer. If you encounter any issues, restart and compare to previous failures to pinpoint the problem. I realized I made a mistake by placing memory in the wrong slots during a recent build; after running Prime95 stability tests on the whole system and then specifically on memory, I identified the error.

Reply
Reply
Pages (2): 1 2 Next