Memory enabiling issue, wont boot at 4000hz stuck at 2666hz

Issues & Assistance Unsupported hardware | Dual boot
,
1

Hello, long story short in the bios my ram is set to default 2600hz i have 4000hz ram and when i changed it to D.O.C.P and set it to 4000hz Garuida wont boot.

I am likely missing something very basic as i have had no issues on windows running 4000hz.

Please let me know your thoughts

Thanks in advance

System:
Kernel: 6.9.3-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.1.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=bb0545a2-6262-4460-8bc5-99f6c3414ad1 rw rootflags=subvol=@
quiet loglevel=3 ibt=off
Desktop: KDE Plasma v: 6.0.5 tk: Qt v: N/A info: frameworks v: 6.3.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop System: ASUS product: N/A v: N/A serial:
Mobo: ASUSTeK model: TUF GAMING X570-PRO (WI-FI) v: Rev X.0x
serial: part-nu: SKU uuid:
UEFI: American Megatrends v: 4602 date: 02/23/2023
CPU:
Info: model: AMD Ryzen 9 5900X bits: 64 type: MT MCP arch: Zen 3+ gen: 4
level: v3 note: check built: 2022 process: TSMC n6 (7nm) family: 0x19 (25)
model-id: 0x21 (33) stepping: 0 microcode: 0xA201025
Topology: cpus: 1x cores: 12 tpc: 2 threads: 24 smt: enabled cache:
L1: 768 KiB desc: d-12x32 KiB; i-12x32 KiB L2: 6 MiB desc: 12x512 KiB
L3: 64 MiB desc: 2x32 MiB
Speed (MHz): avg: 3686 high: 3700 min/max: 2200/5073 boost: enabled
scaling: driver: acpi-cpufreq governor: performance cores: 1: 3700 2: 3700
3: 3700 4: 3593 5: 3700 6: 3700 7: 3700 8: 3700 9: 3700 10: 3700 11: 3700
12: 3585 13: 3700 14: 3700 15: 3700 16: 3700 17: 3700 18: 3700 19: 3700
20: 3588 21: 3700 22: 3700 23: 3700 24: 3700 bogomips: 177261
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities:
Graphics:
Device-1: AMD Navi 21 [Radeon RX 6800/6800 XT / 6900 XT]
vendor: Micro-Star MSI driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x
process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4 speed: 16 GT/s
lanes: 16 ports: active: DP-1,DP-3 empty: DP-2,HDMI-A-1,Writeback-1
bus-ID: 0b:00.0 chip-ID: 1002:73bf class-ID: 0300
Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 24.1.0
compositor: kwin_wayland driver: X: loaded: amdgpu
unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi
gpu: amdgpu d-rect: 5120x1440 display-ID: 0
Monitor-1: DP-1 pos: right res: 2560x1440 size: N/A modes: N/A
Monitor-2: DP-3 pos: primary,left res: 2560x1440 size: N/A modes: N/A
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: swrast surfaceless: drv: radeonsi wayland: drv: radeonsi x11:
drv: radeonsi inactive: gbm
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.1.1-arch1.1
glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 6900 XT (radeonsi
navi21 LLVM 17.0.6 DRM 3.57 6.9.3-zen1-1-zen) device-ID: 1002:73bf
memory: 15.62 GiB unified: no display-ID: :1.0
API: Vulkan v: 1.3.279 layers: 13 device: 0 type: discrete-gpu name: AMD
Radeon RX 6900 XT (RADV NAVI21) driver: mesa radv v: 24.1.1-arch1.1
device-ID: 1002:73bf surfaces: xcb,xlib,wayland device: 1 type: cpu
name: llvmpipe (LLVM 17.0.6 256 bits) driver: mesa llvmpipe
v: 24.1.1-arch1.1 (LLVM 17.0.6) device-ID: 10005:0000
surfaces: xcb,xlib,wayland
Audio:
Device-1: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel pcie:
gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 0b:00.1 chip-ID: 1002:ab28
class-ID: 0403
Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 0d:00.4 chip-ID: 1022:1487 class-ID: 0403
API: ALSA v: k6.9.3-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 1.0.7 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: gen: 2
speed: 5 GT/s lanes: 1 bus-ID: 04:00.0 chip-ID: 8086:2723 class-ID: 0280
IF: wlp4s0 state: down mac:
Device-2: Intel Ethernet I225-V vendor: ASUSTeK driver: igc v: kernel
pcie: gen: 2 speed: 5 GT/s lanes: 1 port: N/A bus-ID: 05:00.0
chip-ID: 8086:15f3 class-ID: 0200
IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac:
Info: services: NetworkManager, smbd, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: Intel AX200 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-4:2 chip-ID: 8087:0029
class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: bt-v: 5.2
lmp-v: 11 status: discoverable: no pairing: no class-ID: 6c0104
Drives:
Local Storage: total: 4.19 TiB used: 34.01 GiB (0.8%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
model: MZVLB512HBJQ-00A00 size: 476.94 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial:
fw-rev: EXF7201Q temp: 28.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: A-Data model: SU800 size: 1.86 TiB
block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s tech: SSD
serial: fw-rev: 7A scheme: GPT
ID-3: /dev/sdb maj-min: 8:16 vendor: A-Data model: SU800 size: 1.86 TiB
block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s tech: SSD
serial: fw-rev: 7A scheme: GPT
Partition:
ID-1: / raw-size: 1.86 TiB size: 1.86 TiB (100.00%) used: 34.01 GiB (1.8%)
fs: btrfs dev: /dev/sdb2 maj-min: 8:18
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 588 KiB (0.2%) fs: vfat dev: /dev/sdb1 maj-min: 8:17
ID-3: /home raw-size: 1.86 TiB size: 1.86 TiB (100.00%)
used: 34.01 GiB (1.8%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
ID-4: /var/log raw-size: 1.86 TiB size: 1.86 TiB (100.00%)
used: 34.01 GiB (1.8%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
ID-5: /var/tmp raw-size: 1.86 TiB size: 1.86 TiB (100.00%)
used: 34.01 GiB (1.8%) fs: btrfs dev: /dev/sdb2 maj-min: 8:18
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 62.7 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 24 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 47.5 C mobo: N/A gpu: amdgpu temp: 46.0 C
mem: 44.0 C
Fan Speeds (rpm): N/A gpu: amdgpu fan: 0
Info:
Memory: total: 64 GiB note: est. available: 62.7 GiB used: 4.32 GiB (6.9%)
Processes: 476 Power: uptime: 14m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 25.07 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 255 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 1952 libs: 579 tools: octopi,paru Compilers:
clang: 17.0.6 gcc: 14.1.1 Shell: garuda-inxi default: fish v: 3.7.1
running-in: konsole inxi: 3.3.34
Garuda (2.6.26-1):
System install date: 2024-06-09
Last full system update: 2024-06-10
Is partially upgraded: No
Relevant software: snapper NetworkManager dracut
Windows dual boot: Probably (Run as root to verify)
Failed units:

2

Yes you’re missing your garuda-inxi that the templet you deleted told you is required.

3 Likes
3

Can your windows system handle heavy loads with these ram clocks?

Only recommendation off the top of my head is to try slightly lower clocks.

In some rare cases, the ram or mobo can’t handle the high clocks set by ram. It has happened to me on old intel i5 setup.

NB! Provide the garuda-inxi!

1 Like
4

Also, 2666hz/4000hz is a bit slow.
If only that were MHz… :sweat_smile:

1 Like
5

I added the inxi to the post

6

Yes i have ran it the past few years at 4000Mhz

7

Wait… 4000 Mhz is rather high on DDR4. You could try some other clock, but you might need to set it manually. I’d try 3600 and maybe 3200. I’d be happy if I could run 3.6. The performance is likely identical.

Edit. From linustechtips.com:

"
5000 series Ryzen is usually good up to 3600MHz, there is almost no reason to go for 4000MHz as it will either not work out of the box without some major tweaking in BIOS or it will make your system actually run slower as it will likely force 2:1 ratio for FCLK and UCLK.

Just because motherboard supports 4000MHz+ does not mean that it’s the same case with the CPU.

Just turn on the XMP and try to then manually change speed to 3600MHz.
"

I read through 2 threads and the claim is that 4000 Mhz can be “semi-unstable” on 4 slots and usually recommended to go to 3.6 or 3.2Ghz.

Not sure if this is super useful for OP, but to make the point, every ram generation has a sweet spot. For DDR4 it is mostly 3.2Ghz or 3.6Ghz

2 Likes
8

Linux is not windows. Try other kernels.

2 Likes
9

Thats interesting and good to know. Well I managed to get it to run at 4000MHz, how? No clue all i did was down clock to 3933 and then go back to 4000MHz and its running fine now, booted it up a number of times with no issue so the problem is beyond me but ill have to try 3600 and see if I notice a performance difference.

Thanks for the info!

1 Like
10

That’s great, main thing you have got the system running.

I’d pick a clock and run benchmarks. For example, you can natively run Blender Benchmark and run some games to confirm.

11

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.