How to know if ram is working fine

Ask Fedora
, , , ,
1

My laptop had 8GB of ram but recently i upgraded as there were too many issues happening… i added 16Gb of Ram so right now total is 24GB.

The laptop seems to function normally but how can i be sure that the ram i added will not create some issues… and its working properly

 Kernel: 6.0.5-200.fc36.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.37-36.fc36
    parameters: BOOT_IMAGE=(hd1,gpt1)/boot/vmlinuz-6.0.5-200.fc36.x86_64
    root=UUID=c27f5a82-b82b-43cb-9440-e17eac97919e ro rhgb quiet
    rd.driver.blacklist=nouveau modprobe.blacklist=nouveau
    nvidia-drm.modeset=1
  Desktop: GNOME v: 42.5 tk: GTK v: 3.24.34 wm: gnome-shell dm: GDM v: 42.0
    Distro: Fedora release 36 (Thirty Six)
Machine:
  Type: Laptop System: HP product: HP Pavilion Gaming Laptop 15-ec1xxx v: N/A
    serial: <filter> Chassis: type: 10 serial: <filter>
  Mobo: HP model: 87B1 v: 31.23 serial: <filter> UEFI: AMI v: F.25
    date: 08/18/2021
Battery:
  ID-1: BAT0 charge: 40.7 Wh (90.2%) condition: 45.1/45.1 Wh (100.0%)
    volts: 12.9 min: 11.6 model: Hewlett-Packard Primary type: Li-ion
    serial: N/A status: charging cycles: 405
Memory:
  RAM: total: 22.84 GiB used: 4.41 GiB (19.3%)
  Array-1: capacity: 32 GiB slots: 2 EC: None max-module-size: 16 GiB
    note: est.
  Device-1: Bottom - Slot 1 (left) type: DDR4 detail: synchronous unbuffered
    (unregistered) size: 8 GiB speed: 3200 MT/s volts: curr: 1.2 min: 1.2
    max: 1.2 width (bits): data: 64 total: 64 manufacturer: Hynix
    part-no: HMA81GS6CJR8N-XN serial: <filter>
  Device-2: Bottom - Slot 2 (right) type: DDR4 detail: synchronous
    unbuffered (unregistered) size: 16 GiB speed: 3200 MT/s volts: curr: 1.2
    min: 1.2 max: 1.2 width (bits): data: 64 total: 64 manufacturer: Crucial
    part-no: CT16G4SFRA32A.M8FE serial: <filter>
CPU:
  Info: model: AMD Ryzen 5 4600H with Radeon Graphics socket: FP6 bits: 64
    type: MT MCP arch: Zen 2 gen: 3 level: v3 note: check built: 2020-22
    process: TSMC n7 (7nm) family: 0x17 (23) model-id: 0x60 (96) stepping: 1
    microcode: 0x8600106
  Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
    L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB L3: 8 MiB
    desc: 2x4 MiB
  Speed (MHz): avg: 1666 high: 3000 min/max: 1400/3000 boost: enabled
    base/boost: 3000/4000 scaling: driver: acpi-cpufreq governor: schedutil
    volts: 1.2 V ext-clock: 100 MHz cores: 1: 1400 2: 1400 3: 1400 4: 3000
    5: 1400 6: 1400 7: 1400 8: 1400 9: 3000 10: 1400 11: 1400 12: 1400
    bogomips: 71861
  Flags: 3dnowprefetch abm adx aes aperfmperf apic arat avic avx avx2 bmi1
    bmi2 bpext cat_l3 cdp_l3 clflush clflushopt clwb clzero cmov cmp_legacy
    constant_tsc cpb cppc cpuid cqm cqm_llc cqm_mbm_local cqm_mbm_total
    cqm_occup_llc cr8_legacy cx16 cx8 de decodeassists extapic extd_apicid
    f16c flushbyasid fma fpu fsgsbase fxsr fxsr_opt ht hw_pstate ibpb ibrs ibs
    irperf lahf_lm lbrv lm mba mca mce misalignsse mmx mmxext monitor movbe
    msr mtrr mwaitx nonstop_tsc nopl npt nrip_save nx osvw overflow_recov pae
    pat pausefilter pclmulqdq pdpe1gb perfctr_core perfctr_llc perfctr_nb
    pfthreshold pge pni popcnt pse pse36 rapl rdpid rdpru rdrand rdseed rdt_a
    rdtscp rep_good sep sha_ni skinit smap smca smep ssbd sse sse2 sse4_1
    sse4_2 sse4a ssse3 stibp succor svm svm_lock syscall tce topoext tsc
    tsc_scale umip v_spec_ctrl v_vmsave_vmload vgif vmcb_clean vme vmmcall
    wbnoinvd wdt xgetbv1 xsave xsavec xsaveerptr xsaveopt xsaves
  Vulnerabilities:
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: retbleed mitigation: untrained return thunk; SMT enabled with STIBP
    protection
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, STIBP:
    always-on, RSB filling, PBRSB-eIBRS: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA TU117M vendor: Hewlett-Packard driver: nvidia v: 520.56.06
    alternate: nouveau,nvidia_drm non-free: 515.xx+ status: current (as of
    2022-10) arch: Turing code: TUxxx process: TSMC 12nm built: 2018-22 pcie:
    gen: 1 speed: 2.5 GT/s lanes: 8 link-max: gen: 3 speed: 8 GT/s lanes: 16
    ports: active: none off: HDMI-A-1 empty: none bus-ID: 01:00.0
    chip-ID: 10de:1f99 class-ID: 0300
  Device-2: AMD Renoir vendor: Hewlett-Packard driver: amdgpu v: kernel
    arch: GCN-5.1 code: Vega-2 process: TSMC n7 (7nm) built: 2018-21 pcie:
    gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4 speed: 16 GT/s ports:
    active: none off: eDP-1 empty: none bus-ID: 05:00.0 chip-ID: 1002:1636
    class-ID: 0300 temp: 41.0 C
  Device-3: Quanta HP TrueVision HD Camera type: USB driver: uvcvideo
    bus-ID: 3-3:2 chip-ID: 0408:5365 class-ID: 0e02
  Display: server: X.Org v: 1.20.14 with: Xwayland v: 22.1.3
    compositor: gnome-shell driver: X: loaded: amdgpu,nvidia
    unloaded: fbdev,modesetting,nouveau,vesa alternate: nv dri: radeonsi
    gpu: amdgpu,nvidia,nvidia-nvswitch display-ID: :0 screens: 1
  Screen-1: 0 s-res: 2560x1080 s-dpi: 96 s-size: 677x286mm (26.65x11.26")
    s-diag: 735mm (28.93")
  Monitor-1: HDMI-A-1 mapped: HDMI-0 note: disabled pos: primary model: LG
    (GoldStar) HDR WFHD serial: <filter> built: 2022 res: 2560x1080 dpi: 81
    gamma: 1.2 size: 798x334mm (31.42x13.15") diag: 869mm (34.2") modes:
    max: 2560x1080 min: 640x480
  Monitor-2: eDP-1 mapped: eDP-1-0 note: disabled model: ChiMei InnoLux
    0x150d built: 2018 res: 2560x1080 dpi: 142 gamma: 1.2
    size: 344x193mm (13.54x7.6") diag: 394mm (15.5") ratio: 16:9 modes:
    max: 1920x1080 min: 640x480
  OpenGL: renderer: NVIDIA GeForce GTX 1650/PCIe/SSE2 v: 4.6.0 NVIDIA
    520.56.06 direct render: Yes
2

Computer components are very social. They in most cases are respecting the speed/technology of an older device.

In your case this would mean, if the older Ram you had, is a slower ram than the 16GB you bought, it will perform on specifications as your older ram.

If you do a performance test with the 24GB and tests with the 16GB, the 24GB should be faster/better. If not the older Ram is probably slow down your system.

In this case it would make sense to sell your 8GB on the second hand market and organize you a exact same as you bought. This not just increases your amount of Memory it also guaranties that you have same memory units who work perfect together.

Of course, before you do so, you have to check if your hardware supports two 16GB units.

If you already had issues you might let the 8GB extra out of your system, to see if the issues are gone.

1 Like
3

Well both are rated for same speed @3200mhz so i dont think it will run slower, its just that one is 8GB and another is 16GB… so i was thinking if there is way to test for system stability…

4

Ok i saw that just the brand is different. What kind of issues did you relate to the memory?

5

To tell you the truth i dont know…

6

For non-UEFI system you can use memtest86+ from the fedora repository, and it can extensively test the ram memory.

For UEFI systems you may take a look at https://www.memtest86.com/.

There is also a memtester package in the Fedora repository.

I have only ever used the memtest86+ utility, so I can’t comment on the others.

2 Likes
7

The system seems mostly happy with that arrangement, though it may not be able to run in dual channel mode with mismatched memory DIMMs like that.

As already mentioned, I would suggest that either you buy an additional 16 GB DIMM matching the new one you just installed and remove the 8GB one, or just remove the 8GB one and run with 16GB memory. This avoids potential conflicts and using 2 matched DIMMs would enable dual channel RAM if the mobo supports that. Dual channel RAM would beat single channel RAM hands down.

The inxi output shows the system supports a maximum of 32 GB (in 2 16 GB modules)

1 Like
8

I dont have money to buy another 16GB kit and i heared that AMD has something called flex mode where it will run in dual channel for the size of lowest ram module, means in 16GB the 8GB of the space will run in dual channel and other half of will run single channel…

what is your thought on flex mode?

Overall experience from before is really great btw… things are running extra smooth without hang of any kind…

9

Good for you. I do experience this since 2013 with my 16GB (only). It really depends what you try to run and for what you will use your system. So, i guess everything is fine then. The tools available you got an answer already.

1 Like
10

No experience with it. Sounds good though.