Instant tons of memory errors with memtest86+

Hi all!

After a kernel panic crash in the middle of the stable update of 2019-10-10, my system was rendered unusable and I needed to completely reinstall everything. While at it, I randomly ran a memtest scan and I was surprised to instantly get a ton of errors on all tests. The thing is, if my RAM is as damaged as it looks like, I am not experiencing a lot of symptoms... I think.

Here is a screenshot

IMG_20191015_201741

I do get an occasional system crash, but mostly getting firefox tabs crash and rarely system freezes. Been running big games and heavy process with almost no problem! I'd expect to have a totally unusable computer with this kind of error reports wouldn't I? There are a lot of small bugs/irritating stuff on my system, but nothing major.

I know a healthy system should provide 0 errors. But with 1113856 in 3h09, I think there is a problem, but I'm not sure on how to proceed. I can try the RAM sticks one at a time and/or on different slots with no problem. But I want to hear from you first on what you think the gravity of the situation is.

My inxi
System:    Host: manjaro Kernel: 5.3.6-1-MANJARO x86_64 bits: 64 compiler: gcc v: 9.2.0 Desktop: KDE Plasma 5.16.5 
           Distro: Manjaro Linux 
Machine:   Type: Desktop Mobo: Gigabyte model: H270-Gaming 3 v: x.x serial: <filter> UEFI [Legacy]: American Megatrends v: F9d 
           date: 03/09/2018 
Memory:    RAM: total: 15.60 GiB used: 2.75 GiB (17.6%) 
           Array-1: capacity: 64 GiB slots: 4 EC: None max module size: 16 GiB note: est. 
           Device-1: ChannelA-DIMM0 size: No Module Installed 
           Device-2: ChannelA-DIMM1 size: 8 GiB speed: 2400 MT/s type: DDR4 detail: synchronous bus width: 64 bits 
           total: 64 bits manufacturer: 029E part-no: CMK16GX4M2A2400C16 serial: N/A 
           Device-3: ChannelB-DIMM0 size: No Module Installed 
           Device-4: ChannelB-DIMM1 size: 8 GiB speed: 2400 MT/s type: DDR4 detail: synchronous bus width: 64 bits 
           total: 64 bits manufacturer: 029E part-no: CMK16GX4M2A2400C16 serial: N/A 
CPU:       Topology: Quad Core model: Intel Core i7-7700 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 L2 cache: 8192 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 57616 
           Speed: 2560 MHz min/max: 800/4200 MHz Core speeds (MHz): 1: 1537 2: 1305 3: 1457 4: 938 5: 1076 6: 1339 7: 1703 
           8: 915 
Graphics:  Device-1: NVIDIA GP104 [GeForce GTX 1070] vendor: eVga.com. driver: nvidia v: 435.21 bus ID: 01:00.0 
           Display: x11 server: X.Org 1.20.5 driver: nvidia resolution: 1440x900~60Hz, 1280x1024~60Hz, 2560x1440~60Hz 
           OpenGL: renderer: GeForce GTX 1070/PCIe/SSE2 v: 4.6.0 NVIDIA 435.21 direct render: Yes 
Audio:     Device-1: Intel 200 Series PCH HD Audio vendor: Gigabyte driver: snd_hda_intel v: kernel bus ID: 00:1f.3 
           Device-2: NVIDIA GP104 High Definition Audio vendor: eVga.com. driver: snd_hda_intel v: kernel bus ID: 01:00.1 
           Sound Server: ALSA v: k5.3.6-1-MANJARO 
Network:   Device-1: Qualcomm Atheros Killer E2500 Gigabit Ethernet vendor: Gigabyte driver: alx v: kernel port: d000 
           bus ID: 06:00.0 
           IF: enp6s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 1.39 TiB used: 120.49 GiB (8.5%) 
           ID-1: /dev/sda vendor: Crucial model: CT525MX300SSD1 size: 489.05 GiB 
           ID-2: /dev/sdb vendor: Seagate model: ST1000DM010-2EP102 size: 931.51 GiB 
Partition: ID-1: / size: 29.40 GiB used: 10.57 GiB (36.0%) fs: ext4 dev: /dev/sda4 
           ID-2: /home size: 39.12 GiB used: 2.16 GiB (5.5%) fs: ext4 dev: /dev/sda1 
           ID-3: swap-1 size: 10.00 GiB used: 71.8 MiB (0.7%) fs: swap dev: /dev/sdb3 
Sensors:   System Temperatures: cpu: 36.0 C mobo: N/A gpu: nvidia temp: 55 C 
           Fan Speeds (RPM): N/A gpu: nvidia fan: 12% 
Info:      Processes: 242 Uptime: 1h 53m Memory: 15.60 GiB used: 2.69 GiB (17.2%) Init: systemd Compilers: gcc: 9.2.0 
           Shell: bash v: 5.0.11 inxi: 3.0.36 

Also, in BIOS, I enabled XMP profile 1 (enable or disable gave both instant errors in memtest).
What do you think should be my next step?

Thanks in advance,
TT

  • Latest firmware installed?

  • Turn off all of your overclocking (not just XMP) and retest.

Have a look at this ArchWiki page.

3 Likes

Overclocking can cause memory issues. I experienced this myself when I was playing with the BIOS settings. If you rule out overclocking by running the RAM at the lowest possible speed, your only option will be to buy new RAM.

7 Likes

Thanks all! So by default no OC was made and bios was already up to date. I went straight to test each RAM separately and only one of them gave all the errors. The other one shows none up to now (only 1 pass though, will let it run longer).

I'll buy a new stick to replace the other one.
Any clue on why a two year old quality RAM did this?

Last question: Can I simply buy the 8gb x1 that has the same specs as the 16gb 2x8gb? Because their model number is not the same and the 8gb x1 is no listed in my MB support list. I'm pretty sure it is ok, but I'll gladly take your input!
Thanks :slight_smile:

One is 3200Mhz, the other is 2400Mhz. You want to make sure they are both the same speed. And preferably the same timing, but you can adjust the timing yourself (and hopefully it works) in the BIOS.

There are many different things that could have caused this. It just happened to my 2 year old RAM as well a couple days ago... My games keeps crashing once and a while, and Firefox sometimes as well if I have a game running. Sometimes I get a kernel panic or BSOD (on Windows). Had to replace the RAM. Mine had 2 errors per memtest86. 1 Error is already too much for RAM.

1 Like

Yeah, the product title is all messed up, but it is actually 2400Mhz.

I just found the exact same 8gb x1 in red for less $ and faster delivery! Same specs DDR4 SDRAM 2400Mhz, CAS 16, 16-16-16-39, 1.2V.

Right now still no errors after2 pass!
Thanks again :slight_smile:
TT

1 Like

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

Forum kindly sponsored by